spark-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kay Ousterhout <...@eecs.berkeley.edu>
Subject Re: Signal/Noise Ratio
Date Sat, 22 Feb 2014 03:54:19 GMT
It looks like there's at least one other apache project, jclouds, that
sends the github notifications to a separate notifications@ list (see
http://mail-archives.apache.org/mod_mbox/incubator-general/201402.mbox/%3C1391721862.67613.YahooMailNeo%40web172602.mail.ir2.yahoo.com%3E).
 Given that many people are annoyed by getting the messages on this list,
and that there is some precedent for sending them to a different list, I'd
be in favor of doing that.


On Fri, Feb 21, 2014 at 6:18 PM, Mattmann, Chris A (3980) <
chris.a.mattmann@jpl.nasa.gov> wrote:

> Sweet great job Reynold.
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Chris Mattmann, Ph.D.
> Chief Architect
> Instrument Software and Science Data Systems Section (398)
> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
> Office: 171-283, Mailstop: 171-246
> Email: chris.a.mattmann@nasa.gov
> WWW:  http://sunset.usc.edu/~mattmann/
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Adjunct Associate Professor, Computer Science Department
> University of Southern California, Los Angeles, CA 90089 USA
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
>
>
>
>
>
> -----Original Message-----
> From: Reynold Xin <rxin@databricks.com>
> Reply-To: "dev@spark.incubator.apache.org" <dev@spark.incubator.apache.org
> >
> Date: Friday, February 21, 2014 6:08 PM
> To: "dev@spark.incubator.apache.org" <dev@spark.incubator.apache.org>
> Subject: Re: Signal/Noise Ratio
>
> >FYI I submitted an ASF INFRA ticket on granting the AMPLab Jenkins
> >permission to use the github commit status API.
> >
> >If that goes through, we can configure Jenkins to use the commit status
> >API
> >without leaving comments on the pull requests.
> >
> >https://issues.apache.org/jira/browse/INFRA-7367
> >
> >
> >
> >On Fri, Feb 21, 2014 at 11:14 AM, Ethan Jewett <esjewett@gmail.com>
> wrote:
> >
> >> Thanks for the pointer Aaron. Very helpful.
> >>
> >> I won't harp on this any more after this email: my reading is that the
> >>main
> >> concern is archiving discussion, which could be achieved using a
> >>separate
> >> mailing list. Major decisions should clearly happen on the dev list so
> >> everyone is informed, but I don't see a situation where that hadn't been
> >> happening anyway (which is why I read the dev list regularly, sometimes
> >> look at the archives, and am struggling with the Github messages and
> >> pitying those not using Gmail filters).
> >>
> >>
> >> On Fri, Feb 21, 2014 at 12:51 PM, Aaron Davidson <ilikerps@gmail.com>
> >> wrote:
> >>
> >> > I don't have an official policy to point you to, but Chris Mattmann
> >>(our
> >> > Apache project mentor) summarized some of the points in this thread,
> >>and
> >> > here is the original concern that caused us to make this change:
> >> >
> >> >
> >> >
> >>
> >>
> http://mail-archives.apache.org/mod_mbox/incubator-general/201402.mbox/%3
> >>CCAAS6=7hkCiT093nXVMcUus8Z-5XCDn=cQ5trjN_Kz9ARe9H=RA@mail.gmail.com%3E
> >> >
> >> >
> >> > On Fri, Feb 21, 2014 at 8:08 AM, Ethan Jewett <esjewett@gmail.com>
> >> wrote:
> >> >
> >> > > Or not off-list. Sorry folks :-) Anyone should feel free to educate
> >>me
> >> > > either on the policy or on mailing list use ;-)
> >> > >
> >> > > On Friday, February 21, 2014, Ethan Jewett <esjewett@gmail.com>
> >>wrote:
> >> > >
> >> > > > Hi Aaron,
> >> > > >
> >> > > > Off-list message here. Can you point me to this policy? Due to
> >>some
> >> > > > previous experiences here, I'm under the impression that it
> >>doesn't
> >> > > exist.
> >> > > > I can't find it on the Apache website.
> >> > > >
> >> > > > Thanks,
> >> > > > Ethan
> >> > > >
> >> > > > On Tuesday, February 18, 2014, Aaron Davidson <ilikerps@gmail.com
> >> > > <javascript:_e(%7B%7D,'cvml','ilikerps@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 git@git.apache.org and are destined to
> >> > > >> dev@spark.incubator.apache.org.
> >> > > >>
> >> > > >>
> >> > > >> On Tue, Feb 18, 2014 at 10:04 AM, Gerard Maas <
> >> gerard.maas@gmail.com>
> >> > > >> wrote:
> >> > > >>
> >> > > >> > +1 please.
> >> > > >> >
> >> > > >> >
> >> > > >> > On Tue, Feb 18, 2014 at 6:04 PM, Michael Ernest <
> >> > > mfernest@cloudera.com
> >> > > >> > >wrote:
> >> > > >> >
> >> > > >> > > +1
> >> > > >> > >
> >> > > >> > >
> >> > > >> > > On Tue, Feb 18, 2014 at 8:24 AM, Heiko Braun <
> >> > > >> ike.braun@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
> >> > > >> > >
> >> > > >> >
> >> > > >>
> >> > > >
> >> > >
> >> >
> >>
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message