That would be fine. I would just like the problem fixed. The list has gone from being a consistently pretty interesting and content-heavy read to being a trudge to go through and attempt to extract the relevant information from every day.
On Thu, Feb 20, 2014 at 3:01 PM, Andrew Ash <and...@andrewash.com> 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 <ilike...@gmail.com> > > >> wrote: > > >> > > >> > This is due, unfortunately, to Apache policies that all > > >> development-related > > >> > discussion should take place on the dev list. As we are attempting > to > > >> > graduate from an incubating project to an Apache top level project, > > >>there > > >> > were some concerns raised about GitHub, and the fastest solution to > > >>avoid > > >> > conflict related to our graduation was to CC dev@ for all GitHub > > >> messages. > > >> > Once our graduation is complete, we may be able to find a less noisy > > >>way > > >> of > > >> > dealing with these messages. > > >> > > > >> > In the meantime, one simple solution is to filter out all messages > > >>that > > >> > come from g...@git.apache.org and are destined to > > >> > dev@spark.incubator.apache.org. > > >> > > > >> > > > >> > On Tue, Feb 18, 2014 at 10:04 AM, Gerard Maas < > gerard.m...@gmail.com> > > >> > wrote: > > >> > > > >> > > +1 please. > > >> > > > > >> > > > > >> > > On Tue, Feb 18, 2014 at 6:04 PM, Michael Ernest > > >><mfern...@cloudera.com > > >> > > >wrote: > > >> > > > > >> > > > +1 > > >> > > > > > >> > > > > > >> > > > On Tue, Feb 18, 2014 at 8:24 AM, Heiko Braun < > > >> ike.br...@googlemail.com > > >> > > > >wrote: > > >> > > > > > >> > > > > > > >> > > > > > > >> > > > > Wouldn't it be better to move the github messages to a > dedicated > > >> > email > > >> > > > > list? > > >> > > > > > > >> > > > > Regards, Heiko > > >> > > > > > > >> > > > > > >> > > > > > >> > > > > > >> > > > -- > > >> > > > Michael Ernest > > >> > > > Sr. Solutions Consultant > > >> > > > West Coast > > >> > > > > > >> > > > > >> > > > >> > > > > >
