You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kvrocks.apache.org by tison <wa...@gmail.com> on 2022/05/30 00:54:19 UTC
Dedicated mailing list for issue and commit?
Hi rockers,
Do you notice that GitHub activities overwhelm the dev@ mailing list? I
invited several potential participant to subscribe the dev@ list and they
all feedback that GH activities noisy.
Although it's fair that any subscriber can create filters on their mailbox,
__we may require dedicated mailing lists for issues(issues@) and
commits(commits@)__. For example, Flink[1] has notification settings as
below:
notifications:
commits: commits@flink.apache.org
issues: issues@flink.apache.org
pullrequests: issues@flink.apache.org
Logging all development activities on mailing list is a requirement of the
Apache way[2], but we can separate automatic notification from general
discussions. Also, ppl used to receive notification by watching GH repos
can keep their way.
What do you think?
Best,
tison.
[1]
https://github.com/apache/flink/blob/e7834d8b56a7b4b1c2674ab399032e21e76d9e63/.asf.yaml
[2] Open Communications https://www.apache.org/theapacheway/index.html
Re: Dedicated mailing list for issue and commit?
Posted by hulk <hu...@gmail.com>.
+1
On Mon, 30 May 2022 at 09:42, Yuan Wang <wa...@apache.org> wrote:
> Hi,
>
> Yes, i think it is a good idea to separate automatic notification from
> general discussions,
> I receive two notifications of the same topic.
>
> And i think it is noisy for people who are only interested in our new
> changes or big progress.
>
> Best,
> Yuan Wang
>
> tison <wa...@gmail.com> 于2022年5月30日周一 08:54写道：
>
> > Hi rockers,
> >
> > Do you notice that GitHub activities overwhelm the dev@ mailing list? I
> > invited several potential participant to subscribe the dev@ list and
> they
> > all feedback that GH activities noisy.
> >
> > Although it's fair that any subscriber can create filters on their
> mailbox,
> > __we may require dedicated mailing lists for issues(issues@) and
> > commits(commits@)__. For example, Flink[1] has notification settings as
> > below:
> >
> > notifications:
> > commits: commits@flink.apache.org
> > issues: issues@flink.apache.org
> > pullrequests: issues@flink.apache.org
> >
> > Logging all development activities on mailing list is a requirement of
> the
> > Apache way[2], but we can separate automatic notification from general
> > discussions. Also, ppl used to receive notification by watching GH repos
> > can keep their way.
> >
> > What do you think?
> >
> > Best,
> > tison.
> >
> > [1]
> >
> >
> https://github.com/apache/flink/blob/e7834d8b56a7b4b1c2674ab399032e21e76d9e63/.asf.yaml
> > [2] Open Communications https://www.apache.org/theapacheway/index.html
> >
>
--
Best Regards,
- *Hulk Lin*
Re: Dedicated mailing list for issue and commit?
Posted by tison <wa...@gmail.com>.
FYI https://github.com/apache/incubator-kvrocks/pull/619
Best,
tison.
tison <wa...@gmail.com> 于2022年6月4日周六 09:30写道：
> Thank you! Now we build these mailing lists and I'll create a patch to
> update the notifications setting.
>
> Best,
> tison.
>
>
> Jean-Baptiste Onofré <jb...@nanthrax.net> 于2022年6月3日周五 16:04写道：
>
>> I just created both issues and commits mailing lists.
>>
>> It should be active soon.
>>
>> Regards
>> JB
>>
>> On Fri, Jun 3, 2022 at 4:40 AM tison <wa...@gmail.com> wrote:
>> >
>> > Thanks for your feedbacks! I created an INFRA ticket
>> > https://issues.apache.org/jira/browse/INFRA-23336.
>> >
>> > Best,
>> > tison.
>> >
>> >
>> > Jean-Baptiste Onofré <jb...@nanthrax.net> 于2022年6月2日周四 01:04写道：
>> >
>> > > Fully agree,
>> > >
>> > > Usually, we have a dedicated mailing list like commits or github.
>> > >
>> > > Regards
>> > > JB
>> > >
>> > > On Mon, May 30, 2022 at 3:42 AM Yuan Wang <wa...@apache.org>
>> wrote:
>> > > >
>> > > > Hi,
>> > > >
>> > > > Yes, i think it is a good idea to separate automatic notification
>> from
>> > > > general discussions,
>> > > > I receive two notifications of the same topic.
>> > > >
>> > > > And i think it is noisy for people who are only interested in our
>> new
>> > > > changes or big progress.
>> > > >
>> > > > Best,
>> > > > Yuan Wang
>> > > >
>> > > > tison <wa...@gmail.com> 于2022年5月30日周一 08:54写道：
>> > > >
>> > > > > Hi rockers,
>> > > > >
>> > > > > Do you notice that GitHub activities overwhelm the dev@ mailing
>> list?
>> > > I
>> > > > > invited several potential participant to subscribe the dev@ list
>> and
>> > > they
>> > > > > all feedback that GH activities noisy.
>> > > > >
>> > > > > Although it's fair that any subscriber can create filters on their
>> > > mailbox,
>> > > > > __we may require dedicated mailing lists for issues(issues@) and
>> > > > > commits(commits@)__. For example, Flink[1] has notification
>> settings
>> > > as
>> > > > > below:
>> > > > >
>> > > > > notifications:
>> > > > > commits: commits@flink.apache.org
>> > > > > issues: issues@flink.apache.org
>> > > > > pullrequests: issues@flink.apache.org
>> > > > >
>> > > > > Logging all development activities on mailing list is a
>> requirement of
>> > > the
>> > > > > Apache way[2], but we can separate automatic notification from
>> general
>> > > > > discussions. Also, ppl used to receive notification by watching GH
>> > > repos
>> > > > > can keep their way.
>> > > > >
>> > > > > What do you think?
>> > > > >
>> > > > > Best,
>> > > > > tison.
>> > > > >
>> > > > > [1]
>> > > > >
>> > > > >
>> > >
>> https://github.com/apache/flink/blob/e7834d8b56a7b4b1c2674ab399032e21e76d9e63/.asf.yaml
>> > > > > [2] Open Communications
>> https://www.apache.org/theapacheway/index.html
>> > > > >
>> > >
>>
>
Re: Dedicated mailing list for issue and commit?
Posted by tison <wa...@gmail.com>.
Thank you! Now we build these mailing lists and I'll create a patch to
update the notifications setting.
Best,
tison.
Jean-Baptiste Onofré <jb...@nanthrax.net> 于2022年6月3日周五 16:04写道：
> I just created both issues and commits mailing lists.
>
> It should be active soon.
>
> Regards
> JB
>
> On Fri, Jun 3, 2022 at 4:40 AM tison <wa...@gmail.com> wrote:
> >
> > Thanks for your feedbacks! I created an INFRA ticket
> > https://issues.apache.org/jira/browse/INFRA-23336.
> >
> > Best,
> > tison.
> >
> >
> > Jean-Baptiste Onofré <jb...@nanthrax.net> 于2022年6月2日周四 01:04写道：
> >
> > > Fully agree,
> > >
> > > Usually, we have a dedicated mailing list like commits or github.
> > >
> > > Regards
> > > JB
> > >
> > > On Mon, May 30, 2022 at 3:42 AM Yuan Wang <wa...@apache.org> wrote:
> > > >
> > > > Hi,
> > > >
> > > > Yes, i think it is a good idea to separate automatic notification
> from
> > > > general discussions,
> > > > I receive two notifications of the same topic.
> > > >
> > > > And i think it is noisy for people who are only interested in our new
> > > > changes or big progress.
> > > >
> > > > Best,
> > > > Yuan Wang
> > > >
> > > > tison <wa...@gmail.com> 于2022年5月30日周一 08:54写道：
> > > >
> > > > > Hi rockers,
> > > > >
> > > > > Do you notice that GitHub activities overwhelm the dev@ mailing
> list?
> > > I
> > > > > invited several potential participant to subscribe the dev@ list
> and
> > > they
> > > > > all feedback that GH activities noisy.
> > > > >
> > > > > Although it's fair that any subscriber can create filters on their
> > > mailbox,
> > > > > __we may require dedicated mailing lists for issues(issues@) and
> > > > > commits(commits@)__. For example, Flink[1] has notification
> settings
> > > as
> > > > > below:
> > > > >
> > > > > notifications:
> > > > > commits: commits@flink.apache.org
> > > > > issues: issues@flink.apache.org
> > > > > pullrequests: issues@flink.apache.org
> > > > >
> > > > > Logging all development activities on mailing list is a
> requirement of
> > > the
> > > > > Apache way[2], but we can separate automatic notification from
> general
> > > > > discussions. Also, ppl used to receive notification by watching GH
> > > repos
> > > > > can keep their way.
> > > > >
> > > > > What do you think?
> > > > >
> > > > > Best,
> > > > > tison.
> > > > >
> > > > > [1]
> > > > >
> > > > >
> > >
> https://github.com/apache/flink/blob/e7834d8b56a7b4b1c2674ab399032e21e76d9e63/.asf.yaml
> > > > > [2] Open Communications
> https://www.apache.org/theapacheway/index.html
> > > > >
> > >
>
Re: Dedicated mailing list for issue and commit?
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
I just created both issues and commits mailing lists.
It should be active soon.
Regards
JB
On Fri, Jun 3, 2022 at 4:40 AM tison <wa...@gmail.com> wrote:
>
> Thanks for your feedbacks! I created an INFRA ticket
> https://issues.apache.org/jira/browse/INFRA-23336.
>
> Best,
> tison.
>
>
> Jean-Baptiste Onofré <jb...@nanthrax.net> 于2022年6月2日周四 01:04写道：
>
> > Fully agree,
> >
> > Usually, we have a dedicated mailing list like commits or github.
> >
> > Regards
> > JB
> >
> > On Mon, May 30, 2022 at 3:42 AM Yuan Wang <wa...@apache.org> wrote:
> > >
> > > Hi,
> > >
> > > Yes, i think it is a good idea to separate automatic notification from
> > > general discussions,
> > > I receive two notifications of the same topic.
> > >
> > > And i think it is noisy for people who are only interested in our new
> > > changes or big progress.
> > >
> > > Best,
> > > Yuan Wang
> > >
> > > tison <wa...@gmail.com> 于2022年5月30日周一 08:54写道：
> > >
> > > > Hi rockers,
> > > >
> > > > Do you notice that GitHub activities overwhelm the dev@ mailing list?
> > I
> > > > invited several potential participant to subscribe the dev@ list and
> > they
> > > > all feedback that GH activities noisy.
> > > >
> > > > Although it's fair that any subscriber can create filters on their
> > mailbox,
> > > > __we may require dedicated mailing lists for issues(issues@) and
> > > > commits(commits@)__. For example, Flink[1] has notification settings
> > as
> > > > below:
> > > >
> > > > notifications:
> > > > commits: commits@flink.apache.org
> > > > issues: issues@flink.apache.org
> > > > pullrequests: issues@flink.apache.org
> > > >
> > > > Logging all development activities on mailing list is a requirement of
> > the
> > > > Apache way[2], but we can separate automatic notification from general
> > > > discussions. Also, ppl used to receive notification by watching GH
> > repos
> > > > can keep their way.
> > > >
> > > > What do you think?
> > > >
> > > > Best,
> > > > tison.
> > > >
> > > > [1]
> > > >
> > > >
> > https://github.com/apache/flink/blob/e7834d8b56a7b4b1c2674ab399032e21e76d9e63/.asf.yaml
> > > > [2] Open Communications https://www.apache.org/theapacheway/index.html
> > > >
> >
Re: Dedicated mailing list for issue and commit?
Posted by tison <wa...@gmail.com>.
I just learn that it's a self-service :P
Will handle this ticket today.
Best,
tison.
tison <wa...@gmail.com> 于2022年6月3日周五 10:40写道：
> Thanks for your feedbacks! I created an INFRA ticket
> https://issues.apache.org/jira/browse/INFRA-23336.
>
> Best,
> tison.
>
>
> Jean-Baptiste Onofré <jb...@nanthrax.net> 于2022年6月2日周四 01:04写道：
>
>> Fully agree,
>>
>> Usually, we have a dedicated mailing list like commits or github.
>>
>> Regards
>> JB
>>
>> On Mon, May 30, 2022 at 3:42 AM Yuan Wang <wa...@apache.org> wrote:
>> >
>> > Hi,
>> >
>> > Yes, i think it is a good idea to separate automatic notification from
>> > general discussions,
>> > I receive two notifications of the same topic.
>> >
>> > And i think it is noisy for people who are only interested in our new
>> > changes or big progress.
>> >
>> > Best,
>> > Yuan Wang
>> >
>> > tison <wa...@gmail.com> 于2022年5月30日周一 08:54写道：
>> >
>> > > Hi rockers,
>> > >
>> > > Do you notice that GitHub activities overwhelm the dev@ mailing
>> list? I
>> > > invited several potential participant to subscribe the dev@ list and
>> they
>> > > all feedback that GH activities noisy.
>> > >
>> > > Although it's fair that any subscriber can create filters on their
>> mailbox,
>> > > __we may require dedicated mailing lists for issues(issues@) and
>> > > commits(commits@)__. For example, Flink[1] has notification settings
>> as
>> > > below:
>> > >
>> > > notifications:
>> > > commits: commits@flink.apache.org
>> > > issues: issues@flink.apache.org
>> > > pullrequests: issues@flink.apache.org
>> > >
>> > > Logging all development activities on mailing list is a requirement
>> of the
>> > > Apache way[2], but we can separate automatic notification from general
>> > > discussions. Also, ppl used to receive notification by watching GH
>> repos
>> > > can keep their way.
>> > >
>> > > What do you think?
>> > >
>> > > Best,
>> > > tison.
>> > >
>> > > [1]
>> > >
>> > >
>> https://github.com/apache/flink/blob/e7834d8b56a7b4b1c2674ab399032e21e76d9e63/.asf.yaml
>> > > [2] Open Communications
>> https://www.apache.org/theapacheway/index.html
>> > >
>>
>
Re: Dedicated mailing list for issue and commit?
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Actually, I can create the mailing list directly (we don't need the
INFRA for that).
I will do that.
Regards
JB
On Fri, Jun 3, 2022 at 4:40 AM tison <wa...@gmail.com> wrote:
>
> Thanks for your feedbacks! I created an INFRA ticket
> https://issues.apache.org/jira/browse/INFRA-23336.
>
> Best,
> tison.
>
>
> Jean-Baptiste Onofré <jb...@nanthrax.net> 于2022年6月2日周四 01:04写道：
>
> > Fully agree,
> >
> > Usually, we have a dedicated mailing list like commits or github.
> >
> > Regards
> > JB
> >
> > On Mon, May 30, 2022 at 3:42 AM Yuan Wang <wa...@apache.org> wrote:
> > >
> > > Hi,
> > >
> > > Yes, i think it is a good idea to separate automatic notification from
> > > general discussions,
> > > I receive two notifications of the same topic.
> > >
> > > And i think it is noisy for people who are only interested in our new
> > > changes or big progress.
> > >
> > > Best,
> > > Yuan Wang
> > >
> > > tison <wa...@gmail.com> 于2022年5月30日周一 08:54写道：
> > >
> > > > Hi rockers,
> > > >
> > > > Do you notice that GitHub activities overwhelm the dev@ mailing list?
> > I
> > > > invited several potential participant to subscribe the dev@ list and
> > they
> > > > all feedback that GH activities noisy.
> > > >
> > > > Although it's fair that any subscriber can create filters on their
> > mailbox,
> > > > __we may require dedicated mailing lists for issues(issues@) and
> > > > commits(commits@)__. For example, Flink[1] has notification settings
> > as
> > > > below:
> > > >
> > > > notifications:
> > > > commits: commits@flink.apache.org
> > > > issues: issues@flink.apache.org
> > > > pullrequests: issues@flink.apache.org
> > > >
> > > > Logging all development activities on mailing list is a requirement of
> > the
> > > > Apache way[2], but we can separate automatic notification from general
> > > > discussions. Also, ppl used to receive notification by watching GH
> > repos
> > > > can keep their way.
> > > >
> > > > What do you think?
> > > >
> > > > Best,
> > > > tison.
> > > >
> > > > [1]
> > > >
> > > >
> > https://github.com/apache/flink/blob/e7834d8b56a7b4b1c2674ab399032e21e76d9e63/.asf.yaml
> > > > [2] Open Communications https://www.apache.org/theapacheway/index.html
> > > >
> >
Re: Dedicated mailing list for issue and commit?
Posted by tison <wa...@gmail.com>.
Thanks for your feedbacks! I created an INFRA ticket
https://issues.apache.org/jira/browse/INFRA-23336.
Best,
tison.
Jean-Baptiste Onofré <jb...@nanthrax.net> 于2022年6月2日周四 01:04写道：
> Fully agree,
>
> Usually, we have a dedicated mailing list like commits or github.
>
> Regards
> JB
>
> On Mon, May 30, 2022 at 3:42 AM Yuan Wang <wa...@apache.org> wrote:
> >
> > Hi,
> >
> > Yes, i think it is a good idea to separate automatic notification from
> > general discussions,
> > I receive two notifications of the same topic.
> >
> > And i think it is noisy for people who are only interested in our new
> > changes or big progress.
> >
> > Best,
> > Yuan Wang
> >
> > tison <wa...@gmail.com> 于2022年5月30日周一 08:54写道：
> >
> > > Hi rockers,
> > >
> > > Do you notice that GitHub activities overwhelm the dev@ mailing list?
> I
> > > invited several potential participant to subscribe the dev@ list and
> they
> > > all feedback that GH activities noisy.
> > >
> > > Although it's fair that any subscriber can create filters on their
> mailbox,
> > > __we may require dedicated mailing lists for issues(issues@) and
> > > commits(commits@)__. For example, Flink[1] has notification settings
> as
> > > below:
> > >
> > > notifications:
> > > commits: commits@flink.apache.org
> > > issues: issues@flink.apache.org
> > > pullrequests: issues@flink.apache.org
> > >
> > > Logging all development activities on mailing list is a requirement of
> the
> > > Apache way[2], but we can separate automatic notification from general
> > > discussions. Also, ppl used to receive notification by watching GH
> repos
> > > can keep their way.
> > >
> > > What do you think?
> > >
> > > Best,
> > > tison.
> > >
> > > [1]
> > >
> > >
> https://github.com/apache/flink/blob/e7834d8b56a7b4b1c2674ab399032e21e76d9e63/.asf.yaml
> > > [2] Open Communications https://www.apache.org/theapacheway/index.html
> > >
>
Re: Dedicated mailing list for issue and commit?
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Fully agree,
Usually, we have a dedicated mailing list like commits or github.
Regards
JB
On Mon, May 30, 2022 at 3:42 AM Yuan Wang <wa...@apache.org> wrote:
>
> Hi,
>
> Yes, i think it is a good idea to separate automatic notification from
> general discussions,
> I receive two notifications of the same topic.
>
> And i think it is noisy for people who are only interested in our new
> changes or big progress.
>
> Best,
> Yuan Wang
>
> tison <wa...@gmail.com> 于2022年5月30日周一 08:54写道：
>
> > Hi rockers,
> >
> > Do you notice that GitHub activities overwhelm the dev@ mailing list? I
> > invited several potential participant to subscribe the dev@ list and they
> > all feedback that GH activities noisy.
> >
> > Although it's fair that any subscriber can create filters on their mailbox,
> > __we may require dedicated mailing lists for issues(issues@) and
> > commits(commits@)__. For example, Flink[1] has notification settings as
> > below:
> >
> > notifications:
> > commits: commits@flink.apache.org
> > issues: issues@flink.apache.org
> > pullrequests: issues@flink.apache.org
> >
> > Logging all development activities on mailing list is a requirement of the
> > Apache way[2], but we can separate automatic notification from general
> > discussions. Also, ppl used to receive notification by watching GH repos
> > can keep their way.
> >
> > What do you think?
> >
> > Best,
> > tison.
> >
> > [1]
> >
> > https://github.com/apache/flink/blob/e7834d8b56a7b4b1c2674ab399032e21e76d9e63/.asf.yaml
> > [2] Open Communications https://www.apache.org/theapacheway/index.html
> >
Re: Dedicated mailing list for issue and commit?
Posted by Yuan Wang <wa...@apache.org>.
Hi,
Yes, i think it is a good idea to separate automatic notification from
general discussions,
I receive two notifications of the same topic.
And i think it is noisy for people who are only interested in our new
changes or big progress.
Best,
Yuan Wang
tison <wa...@gmail.com> 于2022年5月30日周一 08:54写道：
> Hi rockers,
>
> Do you notice that GitHub activities overwhelm the dev@ mailing list? I
> invited several potential participant to subscribe the dev@ list and they
> all feedback that GH activities noisy.
>
> Although it's fair that any subscriber can create filters on their mailbox,
> __we may require dedicated mailing lists for issues(issues@) and
> commits(commits@)__. For example, Flink[1] has notification settings as
> below:
>
> notifications:
> commits: commits@flink.apache.org
> issues: issues@flink.apache.org
> pullrequests: issues@flink.apache.org
>
> Logging all development activities on mailing list is a requirement of the
> Apache way[2], but we can separate automatic notification from general
> discussions. Also, ppl used to receive notification by watching GH repos
> can keep their way.
>
> What do you think?
>
> Best,
> tison.
>
> [1]
>
> https://github.com/apache/flink/blob/e7834d8b56a7b4b1c2674ab399032e21e76d9e63/.asf.yaml
> [2] Open Communications https://www.apache.org/theapacheway/index.html
>