It would help but wouldn't solve the formatting problem or the one-way communication problem.
On Thursday, February 20, 2014, Henry Saputra <henry.sapu...@gmail.com> wrote: > Daniel Gruno from ASF infra mentioned this when adding Github plugin > to dev@ list support : > "We may, in the future, add the possibility to filter out certain > comments from being relayed to the ML (such as jenkins workflows etc), > but this will all depend on how this initial phase goes along." > > Looks like for Apache Spark we need ability to filter comments from > Jenkins. > > So if we could "filter" the Jenkins comment fro being sent to dev@ > list would this help reduce the noise? > > - Henry > > On Thu, Feb 20, 2014 at 1:01 PM, Andrew Ash > <and...@andrewash.com<javascript:;>> > wrote: > > I'm fine with keeping the GitHub traffic if we can > > > > a) take away the Jenkins build started / build finished / build > succeeded / > > build failed messages. Those aren't "dev discussion" and are very noisy. > > I don't think they help anyone, and people who care about those for a > > particular PR (because they're a reviewer or author on it) are already > > subscribed through GitHub. > > b) change the format of the emails that are sent out; I find them very > > poorly formatted. I'd prefer no deep tab for the message. > > > > > http://mail-archives.apache.org/mod_mbox/incubator-spark-dev/201402.mbox/%3c20140210192901.ce834922...@tyr.zones.apache.org%3E > > > > FWIW I'm filtering all emails from g...@git.apache.org straight to trash > > right now because of the noise. > > > > > > On Thu, Feb 20, 2014 at 12:51 PM, Mattmann, Chris A (3980) < > > chris.a.mattm...@jpl.nasa.gov> wrote: > > > >> Guys, > >> > >> Whether you are a TLP or not the big key here is making sure that > >> dev discussion does not happen elsewhere outside of the list. You > >> can create e.g., a github-dev@spark.a.o list, but you will need > >> to make sure that: > >> > >> a) if dev discussion is happening there that it gets flowed up to > >> dev@spark.a.o. All development discussion must appear on the dev > >> list and must be traceable as a project discussion and decisions > >> appear on the list(s). > >> > >> b) automated/etc. email is simply that, and there isn't a ton of > >> discussion going on on those github emails, and that it's mostly > >> going on on the dev@spark.a.o list. > >> > >> If you can meet those 2 criteria/litmus test, I think it's fine. > >> The big concern is that if the discussion is not happening elsewhere, > >> then the decisions make for Apache Spark are based on information > >> that isn't co-located with the Apache Spark project. So that's the > >> thing that the PMC needs to keep in mind (note I said PMC now, yay!) :) > >> > >> Cheers and just keep the above in mind and you'll be good. > >> > >> Cheers, > >> Chris > >> > >> > >> > >> > >> -----Original Message----- > >> From: Andy Konwinski <andykonwin...@gmail.com> > >> Reply-To: "dev@spark.incubator.apache.org" < > dev@spark.incubator.apache.org > >> > > >> Date: Thursday, February 20, 2014 12:36 PM > >> To: "dev@spark.incubator.apache.org" <dev@spark.incubator.apache.org> > >> Subject: Re: Signal/Noise Ratio > >> > >> >That is a very valid point about the list archives (which a mail filter > >> >doesn't address and which impacts the community in a negative way). > >> > > >> >As of today we are a Top Level Project so I think we have a little more > >> >autonomy for this sort of dev vs separate list decision. > >> > > >> > > >> >On Thu, Feb 20, 2014 at 12:15 PM, Ethan Jewett <esjew...@gmail.com> > >> wrote: > >> > > >> >> Is there anything stopping us from using a different list, segregated > >> >>from > >> >> the dev list? The Github emails significantly reduce the signal-noise > >> >>ratio > >> >> of this list, and while it is possible (but annoying) to filter them > >> >>out in > >> >> our individual inboxes, it makes the archives of the list much less > >> >>usable > >> >> in many ways. > >> >> > >> >> > >> >> On Tue, Feb 18, 2014 at 2:20 PM, Aaron Davidson <ili
