Re: Message Lists
Infra says that Jira emails should now be going to iss...@flume.apache.org <mailto:iss...@flume.apache.org>. Ralph > On Dec 27, 2017, at 10:25 PM, Ralph Goers wrote: > > Ping > > Ralph > >> On Dec 22, 2017, at 1:23 PM, Ralph Goers wrote: >> >> I created https://issues.apache.org/jira/browse/INFRA-15710 >> <https://issues.apache.org/jira/browse/INFRA-15710>. It seems that creating >> mailing lists is now self service but is restricted to PMC chairs. Since I >> am no longer a PMC chair I can’t access the application. >> https://selfserve.apache.org <https://selfserve.apache.org/>. >> >> Hari, can you please create iss...@flume.apache.org and update the Jira >> issue when it is completed? >> >> Ralph >> >> >>> On Dec 19, 2017, at 1:35 PM, Mike Percy wrote: >>> >>> Hi Ralph, >>> My opinion is that we should move JIRA traffic to issues@flume.a.o and keep >>> review traffic (Reviewboard, GitHub PRs) on the dev list for now, because >>> the code review requests are relatively low volume and they are certainly >>> relevant to Flume developers - more so than much of the issue traffic. >>> FWIW, the commits already go to commits@. >>> >>> We could try that out for a few months, and if automated traffic is still >>> interfering with our ability to have email conversations between human >>> individuals then we could also split that out into reviews@flume.a.o. >>> That's what we do in Apache Kudu but it seems like overkill for a project >>> with the volume of pull requests that Flume has right now. >>> >>> My 2 cents, >>> Mike >>> >>> On Tue, Dec 19, 2017 at 7:48 AM, Ralph Goers >>> wrote: >>> >>>> I’ll give this another day and if there are no objections I will go ahead >>>> and create Infra issues to do this. >>>> >>>> Ralph >>>> >>>>> On Dec 12, 2017, at 9:46 PM, Ralph Goers >>>> wrote: >>>>> >>>>> I am proposing that we create a new list for automated messages. I am >>>> forwarding it here since it has only gotten replies from Hari and Mike on >>>> the dev list. The discussion really belongs on the dev list but you may not >>>> be seeing it due to the noise. >>>>> >>>>> Ralph >>>>> >>>>>> Begin forwarded message: >>>>>> >>>>>> From: Hari Shreedharan >>>>>> Subject: Re: Message Lists >>>>>> Date: December 11, 2017 at 1:41:11 PM MST >>>>>> To: dev@flume.apache.org >>>>>> Reply-To: dev@flume.apache.org >>>>>> >>>>>> +1. I agree, we should move the private messages out. >>>>>> >>>>>> On Sun, Dec 10, 2017 at 12:14 PM, Mike Percy wrote: >>>>>> >>>>>>> If necessary due to noise we can take this discussion back to private@ >>>>>>> for a check-in. >>>>>>> >>>>>>> Mike >>>>>>> >>>>>>> Sent from my iPhone >>>>>>> >>>>>>>> On Dec 10, 2017, at 9:15 AM, Ralph Goers >>>>>>> wrote: >>>>>>>> >>>>>>>> Thanks Mike. Yours is the only feedback in a month. I am uncomfortable >>>>>>> contacting infra to make the changes based on so little input. >>>>>>>> >>>>>>>> Ralph >>>>>>>> >>>>>>>>> On Dec 8, 2017, at 9:03 PM, Mike Percy wrote: >>>>>>>>> >>>>>>>>> Sorry, I didn't see this message because of all the automated emails! >>>>>>>>> >>>>>>>>> +1 from me. >>>>>>>>> >>>>>>>>> Mike >>>>>>>>> >>>>>>>>> On Sat, Nov 11, 2017 at 9:43 PM, Ralph Goers < >>>>>>> ralph.go...@dslextreme.com> >>>>>>>>> wrote: >>>>>>>>> >>>>>>>>>> Currently all the messages from Jenkins, Jira and GitHub land in >>>> this >>>>>>>>>> mailing list. That makes this mailing list very cluttered and it is >>>>>>> easy to >>>>>>>>>> miss discussions. Other projects use a “notifications” list to >>>> accept >>>>>>>>>> emails from those sources so the dev list can be left for >>>>>>> person-to-person >>>>>>>>>> discussions. I would like to propose that Flume switch to this >>>> model. >>>>>>>>>> Another alternative would be to have separate lists for each of >>>> those >>>>>>>>>> sources. My personal viewpoint is simply separating the automated >>>>>>> emails is >>>>>>>>>> enough but I’d be willing to go along with any plan that moves the >>>>>>>>>> automated emails to another list. I also think that doing this >>>> might >>>>>>>>>> increase the number of subscribers on the Flume dev list as lots of >>>>>>> people >>>>>>>>>> don’t like to deal with all the extra email. >>>>>>>>>> >>>>>>>>>> All that said, it would be expected that all committers would >>>>>>> subscribe to >>>>>>>>>> these new lists. >>>>>>>>>> >>>>>>>>>> Thoughts? >>>>>>>>>> >>>>>>>>>> Ralph >>>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >>>>> >>>> >>>> >>>> >> > > >
Re: Message Lists
Ping Ralph > On Dec 22, 2017, at 1:23 PM, Ralph Goers wrote: > > I created https://issues.apache.org/jira/browse/INFRA-15710 > <https://issues.apache.org/jira/browse/INFRA-15710>. It seems that creating > mailing lists is now self service but is restricted to PMC chairs. Since I am > no longer a PMC chair I can’t access the application. > https://selfserve.apache.org <https://selfserve.apache.org/>. > > Hari, can you please create iss...@flume.apache.org and update the Jira issue > when it is completed? > > Ralph > > >> On Dec 19, 2017, at 1:35 PM, Mike Percy wrote: >> >> Hi Ralph, >> My opinion is that we should move JIRA traffic to issues@flume.a.o and keep >> review traffic (Reviewboard, GitHub PRs) on the dev list for now, because >> the code review requests are relatively low volume and they are certainly >> relevant to Flume developers - more so than much of the issue traffic. >> FWIW, the commits already go to commits@. >> >> We could try that out for a few months, and if automated traffic is still >> interfering with our ability to have email conversations between human >> individuals then we could also split that out into reviews@flume.a.o. >> That's what we do in Apache Kudu but it seems like overkill for a project >> with the volume of pull requests that Flume has right now. >> >> My 2 cents, >> Mike >> >> On Tue, Dec 19, 2017 at 7:48 AM, Ralph Goers >> wrote: >> >>> I’ll give this another day and if there are no objections I will go ahead >>> and create Infra issues to do this. >>> >>> Ralph >>> >>>> On Dec 12, 2017, at 9:46 PM, Ralph Goers >>> wrote: >>>> >>>> I am proposing that we create a new list for automated messages. I am >>> forwarding it here since it has only gotten replies from Hari and Mike on >>> the dev list. The discussion really belongs on the dev list but you may not >>> be seeing it due to the noise. >>>> >>>> Ralph >>>> >>>>> Begin forwarded message: >>>>> >>>>> From: Hari Shreedharan >>>>> Subject: Re: Message Lists >>>>> Date: December 11, 2017 at 1:41:11 PM MST >>>>> To: dev@flume.apache.org >>>>> Reply-To: dev@flume.apache.org >>>>> >>>>> +1. I agree, we should move the private messages out. >>>>> >>>>> On Sun, Dec 10, 2017 at 12:14 PM, Mike Percy wrote: >>>>> >>>>>> If necessary due to noise we can take this discussion back to private@ >>>>>> for a check-in. >>>>>> >>>>>> Mike >>>>>> >>>>>> Sent from my iPhone >>>>>> >>>>>>> On Dec 10, 2017, at 9:15 AM, Ralph Goers >>>>>> wrote: >>>>>>> >>>>>>> Thanks Mike. Yours is the only feedback in a month. I am uncomfortable >>>>>> contacting infra to make the changes based on so little input. >>>>>>> >>>>>>> Ralph >>>>>>> >>>>>>>> On Dec 8, 2017, at 9:03 PM, Mike Percy wrote: >>>>>>>> >>>>>>>> Sorry, I didn't see this message because of all the automated emails! >>>>>>>> >>>>>>>> +1 from me. >>>>>>>> >>>>>>>> Mike >>>>>>>> >>>>>>>> On Sat, Nov 11, 2017 at 9:43 PM, Ralph Goers < >>>>>> ralph.go...@dslextreme.com> >>>>>>>> wrote: >>>>>>>> >>>>>>>>> Currently all the messages from Jenkins, Jira and GitHub land in >>> this >>>>>>>>> mailing list. That makes this mailing list very cluttered and it is >>>>>> easy to >>>>>>>>> miss discussions. Other projects use a “notifications” list to >>> accept >>>>>>>>> emails from those sources so the dev list can be left for >>>>>> person-to-person >>>>>>>>> discussions. I would like to propose that Flume switch to this >>> model. >>>>>>>>> Another alternative would be to have separate lists for each of >>> those >>>>>>>>> sources. My personal viewpoint is simply separating the automated >>>>>> emails is >>>>>>>>> enough but I’d be willing to go along with any plan that moves the >>>>>>>>> automated emails to another list. I also think that doing this >>> might >>>>>>>>> increase the number of subscribers on the Flume dev list as lots of >>>>>> people >>>>>>>>> don’t like to deal with all the extra email. >>>>>>>>> >>>>>>>>> All that said, it would be expected that all committers would >>>>>> subscribe to >>>>>>>>> these new lists. >>>>>>>>> >>>>>>>>> Thoughts? >>>>>>>>> >>>>>>>>> Ralph >>>>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>>> >>>> >>> >>> >>> >
Re: Message Lists
I created https://issues.apache.org/jira/browse/INFRA-15710 <https://issues.apache.org/jira/browse/INFRA-15710>. It seems that creating mailing lists is now self service but is restricted to PMC chairs. Since I am no longer a PMC chair I can’t access the application. https://selfserve.apache.org <https://selfserve.apache.org/>. Hari, can you please create iss...@flume.apache.org and update the Jira issue when it is completed? Ralph > On Dec 19, 2017, at 1:35 PM, Mike Percy wrote: > > Hi Ralph, > My opinion is that we should move JIRA traffic to issues@flume.a.o and keep > review traffic (Reviewboard, GitHub PRs) on the dev list for now, because > the code review requests are relatively low volume and they are certainly > relevant to Flume developers - more so than much of the issue traffic. > FWIW, the commits already go to commits@. > > We could try that out for a few months, and if automated traffic is still > interfering with our ability to have email conversations between human > individuals then we could also split that out into reviews@flume.a.o. > That's what we do in Apache Kudu but it seems like overkill for a project > with the volume of pull requests that Flume has right now. > > My 2 cents, > Mike > > On Tue, Dec 19, 2017 at 7:48 AM, Ralph Goers > wrote: > >> I’ll give this another day and if there are no objections I will go ahead >> and create Infra issues to do this. >> >> Ralph >> >>> On Dec 12, 2017, at 9:46 PM, Ralph Goers >> wrote: >>> >>> I am proposing that we create a new list for automated messages. I am >> forwarding it here since it has only gotten replies from Hari and Mike on >> the dev list. The discussion really belongs on the dev list but you may not >> be seeing it due to the noise. >>> >>> Ralph >>> >>>> Begin forwarded message: >>>> >>>> From: Hari Shreedharan >>>> Subject: Re: Message Lists >>>> Date: December 11, 2017 at 1:41:11 PM MST >>>> To: dev@flume.apache.org >>>> Reply-To: dev@flume.apache.org >>>> >>>> +1. I agree, we should move the private messages out. >>>> >>>> On Sun, Dec 10, 2017 at 12:14 PM, Mike Percy wrote: >>>> >>>>> If necessary due to noise we can take this discussion back to private@ >>>>> for a check-in. >>>>> >>>>> Mike >>>>> >>>>> Sent from my iPhone >>>>> >>>>>> On Dec 10, 2017, at 9:15 AM, Ralph Goers >>>>> wrote: >>>>>> >>>>>> Thanks Mike. Yours is the only feedback in a month. I am uncomfortable >>>>> contacting infra to make the changes based on so little input. >>>>>> >>>>>> Ralph >>>>>> >>>>>>> On Dec 8, 2017, at 9:03 PM, Mike Percy wrote: >>>>>>> >>>>>>> Sorry, I didn't see this message because of all the automated emails! >>>>>>> >>>>>>> +1 from me. >>>>>>> >>>>>>> Mike >>>>>>> >>>>>>> On Sat, Nov 11, 2017 at 9:43 PM, Ralph Goers < >>>>> ralph.go...@dslextreme.com> >>>>>>> wrote: >>>>>>> >>>>>>>> Currently all the messages from Jenkins, Jira and GitHub land in >> this >>>>>>>> mailing list. That makes this mailing list very cluttered and it is >>>>> easy to >>>>>>>> miss discussions. Other projects use a “notifications” list to >> accept >>>>>>>> emails from those sources so the dev list can be left for >>>>> person-to-person >>>>>>>> discussions. I would like to propose that Flume switch to this >> model. >>>>>>>> Another alternative would be to have separate lists for each of >> those >>>>>>>> sources. My personal viewpoint is simply separating the automated >>>>> emails is >>>>>>>> enough but I’d be willing to go along with any plan that moves the >>>>>>>> automated emails to another list. I also think that doing this >> might >>>>>>>> increase the number of subscribers on the Flume dev list as lots of >>>>> people >>>>>>>> don’t like to deal with all the extra email. >>>>>>>> >>>>>>>> All that said, it would be expected that all committers would >>>>> subscribe to >>>>>>>> these new lists. >>>>>>>> >>>>>>>> Thoughts? >>>>>>>> >>>>>>>> Ralph >>>>>>>> >>>>>> >>>>>> >>>>> >>>>> >>> >> >> >>
Re: Message Lists
Hi Ralph, My opinion is that we should move JIRA traffic to issues@flume.a.o and keep review traffic (Reviewboard, GitHub PRs) on the dev list for now, because the code review requests are relatively low volume and they are certainly relevant to Flume developers - more so than much of the issue traffic. FWIW, the commits already go to commits@. We could try that out for a few months, and if automated traffic is still interfering with our ability to have email conversations between human individuals then we could also split that out into reviews@flume.a.o. That's what we do in Apache Kudu but it seems like overkill for a project with the volume of pull requests that Flume has right now. My 2 cents, Mike On Tue, Dec 19, 2017 at 7:48 AM, Ralph Goers wrote: > I’ll give this another day and if there are no objections I will go ahead > and create Infra issues to do this. > > Ralph > > > On Dec 12, 2017, at 9:46 PM, Ralph Goers > wrote: > > > > I am proposing that we create a new list for automated messages. I am > forwarding it here since it has only gotten replies from Hari and Mike on > the dev list. The discussion really belongs on the dev list but you may not > be seeing it due to the noise. > > > > Ralph > > > >> Begin forwarded message: > >> > >> From: Hari Shreedharan > >> Subject: Re: Message Lists > >> Date: December 11, 2017 at 1:41:11 PM MST > >> To: dev@flume.apache.org > >> Reply-To: dev@flume.apache.org > >> > >> +1. I agree, we should move the private messages out. > >> > >> On Sun, Dec 10, 2017 at 12:14 PM, Mike Percy wrote: > >> > >>> If necessary due to noise we can take this discussion back to private@ > >>> for a check-in. > >>> > >>> Mike > >>> > >>> Sent from my iPhone > >>> > >>>> On Dec 10, 2017, at 9:15 AM, Ralph Goers > >>> wrote: > >>>> > >>>> Thanks Mike. Yours is the only feedback in a month. I am uncomfortable > >>> contacting infra to make the changes based on so little input. > >>>> > >>>> Ralph > >>>> > >>>>> On Dec 8, 2017, at 9:03 PM, Mike Percy wrote: > >>>>> > >>>>> Sorry, I didn't see this message because of all the automated emails! > >>>>> > >>>>> +1 from me. > >>>>> > >>>>> Mike > >>>>> > >>>>> On Sat, Nov 11, 2017 at 9:43 PM, Ralph Goers < > >>> ralph.go...@dslextreme.com> > >>>>> wrote: > >>>>> > >>>>>> Currently all the messages from Jenkins, Jira and GitHub land in > this > >>>>>> mailing list. That makes this mailing list very cluttered and it is > >>> easy to > >>>>>> miss discussions. Other projects use a “notifications” list to > accept > >>>>>> emails from those sources so the dev list can be left for > >>> person-to-person > >>>>>> discussions. I would like to propose that Flume switch to this > model. > >>>>>> Another alternative would be to have separate lists for each of > those > >>>>>> sources. My personal viewpoint is simply separating the automated > >>> emails is > >>>>>> enough but I’d be willing to go along with any plan that moves the > >>>>>> automated emails to another list. I also think that doing this > might > >>>>>> increase the number of subscribers on the Flume dev list as lots of > >>> people > >>>>>> don’t like to deal with all the extra email. > >>>>>> > >>>>>> All that said, it would be expected that all committers would > >>> subscribe to > >>>>>> these new lists. > >>>>>> > >>>>>> Thoughts? > >>>>>> > >>>>>> Ralph > >>>>>> > >>>> > >>>> > >>> > >>> > > > > >
Re: Message Lists
I’ll give this another day and if there are no objections I will go ahead and create Infra issues to do this. Ralph > On Dec 12, 2017, at 9:46 PM, Ralph Goers wrote: > > I am proposing that we create a new list for automated messages. I am > forwarding it here since it has only gotten replies from Hari and Mike on the > dev list. The discussion really belongs on the dev list but you may not be > seeing it due to the noise. > > Ralph > >> Begin forwarded message: >> >> From: Hari Shreedharan >> Subject: Re: Message Lists >> Date: December 11, 2017 at 1:41:11 PM MST >> To: dev@flume.apache.org >> Reply-To: dev@flume.apache.org >> >> +1. I agree, we should move the private messages out. >> >> On Sun, Dec 10, 2017 at 12:14 PM, Mike Percy wrote: >> >>> If necessary due to noise we can take this discussion back to private@ >>> for a check-in. >>> >>> Mike >>> >>> Sent from my iPhone >>> >>>> On Dec 10, 2017, at 9:15 AM, Ralph Goers >>> wrote: >>>> >>>> Thanks Mike. Yours is the only feedback in a month. I am uncomfortable >>> contacting infra to make the changes based on so little input. >>>> >>>> Ralph >>>> >>>>> On Dec 8, 2017, at 9:03 PM, Mike Percy wrote: >>>>> >>>>> Sorry, I didn't see this message because of all the automated emails! >>>>> >>>>> +1 from me. >>>>> >>>>> Mike >>>>> >>>>> On Sat, Nov 11, 2017 at 9:43 PM, Ralph Goers < >>> ralph.go...@dslextreme.com> >>>>> wrote: >>>>> >>>>>> Currently all the messages from Jenkins, Jira and GitHub land in this >>>>>> mailing list. That makes this mailing list very cluttered and it is >>> easy to >>>>>> miss discussions. Other projects use a “notifications” list to accept >>>>>> emails from those sources so the dev list can be left for >>> person-to-person >>>>>> discussions. I would like to propose that Flume switch to this model. >>>>>> Another alternative would be to have separate lists for each of those >>>>>> sources. My personal viewpoint is simply separating the automated >>> emails is >>>>>> enough but I’d be willing to go along with any plan that moves the >>>>>> automated emails to another list. I also think that doing this might >>>>>> increase the number of subscribers on the Flume dev list as lots of >>> people >>>>>> don’t like to deal with all the extra email. >>>>>> >>>>>> All that said, it would be expected that all committers would >>> subscribe to >>>>>> these new lists. >>>>>> >>>>>> Thoughts? >>>>>> >>>>>> Ralph >>>>>> >>>> >>>> >>> >>> >
Re: Message Lists
+1. I agree, we should move the private messages out. On Sun, Dec 10, 2017 at 12:14 PM, Mike Percy wrote: > If necessary due to noise we can take this discussion back to private@ > for a check-in. > > Mike > > Sent from my iPhone > > > On Dec 10, 2017, at 9:15 AM, Ralph Goers > wrote: > > > > Thanks Mike. Yours is the only feedback in a month. I am uncomfortable > contacting infra to make the changes based on so little input. > > > > Ralph > > > >> On Dec 8, 2017, at 9:03 PM, Mike Percy wrote: > >> > >> Sorry, I didn't see this message because of all the automated emails! > >> > >> +1 from me. > >> > >> Mike > >> > >> On Sat, Nov 11, 2017 at 9:43 PM, Ralph Goers < > ralph.go...@dslextreme.com> > >> wrote: > >> > >>> Currently all the messages from Jenkins, Jira and GitHub land in this > >>> mailing list. That makes this mailing list very cluttered and it is > easy to > >>> miss discussions. Other projects use a “notifications” list to accept > >>> emails from those sources so the dev list can be left for > person-to-person > >>> discussions. I would like to propose that Flume switch to this model. > >>> Another alternative would be to have separate lists for each of those > >>> sources. My personal viewpoint is simply separating the automated > emails is > >>> enough but I’d be willing to go along with any plan that moves the > >>> automated emails to another list. I also think that doing this might > >>> increase the number of subscribers on the Flume dev list as lots of > people > >>> don’t like to deal with all the extra email. > >>> > >>> All that said, it would be expected that all committers would > subscribe to > >>> these new lists. > >>> > >>> Thoughts? > >>> > >>> Ralph > >>> > > > > > >
Re: Message Lists
If necessary due to noise we can take this discussion back to private@ for a check-in. Mike Sent from my iPhone > On Dec 10, 2017, at 9:15 AM, Ralph Goers wrote: > > Thanks Mike. Yours is the only feedback in a month. I am uncomfortable > contacting infra to make the changes based on so little input. > > Ralph > >> On Dec 8, 2017, at 9:03 PM, Mike Percy wrote: >> >> Sorry, I didn't see this message because of all the automated emails! >> >> +1 from me. >> >> Mike >> >> On Sat, Nov 11, 2017 at 9:43 PM, Ralph Goers >> wrote: >> >>> Currently all the messages from Jenkins, Jira and GitHub land in this >>> mailing list. That makes this mailing list very cluttered and it is easy to >>> miss discussions. Other projects use a “notifications” list to accept >>> emails from those sources so the dev list can be left for person-to-person >>> discussions. I would like to propose that Flume switch to this model. >>> Another alternative would be to have separate lists for each of those >>> sources. My personal viewpoint is simply separating the automated emails is >>> enough but I’d be willing to go along with any plan that moves the >>> automated emails to another list. I also think that doing this might >>> increase the number of subscribers on the Flume dev list as lots of people >>> don’t like to deal with all the extra email. >>> >>> All that said, it would be expected that all committers would subscribe to >>> these new lists. >>> >>> Thoughts? >>> >>> Ralph >>> > >
Re: Message Lists
Thanks Mike. Yours is the only feedback in a month. I am uncomfortable contacting infra to make the changes based on so little input. Ralph > On Dec 8, 2017, at 9:03 PM, Mike Percy wrote: > > Sorry, I didn't see this message because of all the automated emails! > > +1 from me. > > Mike > > On Sat, Nov 11, 2017 at 9:43 PM, Ralph Goers > wrote: > >> Currently all the messages from Jenkins, Jira and GitHub land in this >> mailing list. That makes this mailing list very cluttered and it is easy to >> miss discussions. Other projects use a “notifications” list to accept >> emails from those sources so the dev list can be left for person-to-person >> discussions. I would like to propose that Flume switch to this model. >> Another alternative would be to have separate lists for each of those >> sources. My personal viewpoint is simply separating the automated emails is >> enough but I’d be willing to go along with any plan that moves the >> automated emails to another list. I also think that doing this might >> increase the number of subscribers on the Flume dev list as lots of people >> don’t like to deal with all the extra email. >> >> All that said, it would be expected that all committers would subscribe to >> these new lists. >> >> Thoughts? >> >> Ralph >>
Re: Message Lists
Sorry, I didn't see this message because of all the automated emails! +1 from me. Mike On Sat, Nov 11, 2017 at 9:43 PM, Ralph Goers wrote: > Currently all the messages from Jenkins, Jira and GitHub land in this > mailing list. That makes this mailing list very cluttered and it is easy to > miss discussions. Other projects use a “notifications” list to accept > emails from those sources so the dev list can be left for person-to-person > discussions. I would like to propose that Flume switch to this model. > Another alternative would be to have separate lists for each of those > sources. My personal viewpoint is simply separating the automated emails is > enough but I’d be willing to go along with any plan that moves the > automated emails to another list. I also think that doing this might > increase the number of subscribers on the Flume dev list as lots of people > don’t like to deal with all the extra email. > > All that said, it would be expected that all committers would subscribe to > these new lists. > > Thoughts? > > Ralph >
Message Lists
Currently all the messages from Jenkins, Jira and GitHub land in this mailing list. That makes this mailing list very cluttered and it is easy to miss discussions. Other projects use a “notifications” list to accept emails from those sources so the dev list can be left for person-to-person discussions. I would like to propose that Flume switch to this model. Another alternative would be to have separate lists for each of those sources. My personal viewpoint is simply separating the automated emails is enough but I’d be willing to go along with any plan that moves the automated emails to another list. I also think that doing this might increase the number of subscribers on the Flume dev list as lots of people don’t like to deal with all the extra email. All that said, it would be expected that all committers would subscribe to these new lists. Thoughts? Ralph
