You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@spark.apache.org by Dean Wampler <de...@gmail.com> on 2014/02/08 01:55:25 UTC
Re: [GitHub] incubator-spark pull request:
This SPAM is not doing anyone any good. How about another mailing list for people who want to see this?
Sent from my rotary phone.
> On Feb 7, 2014, at 10:33 AM, mridulm <gi...@git.apache.org> wrote:
>
> Github user mridulm commented on the pull request:
>
> https://github.com/apache/incubator-spark/pull/517#issuecomment-34484468
>
> I am hoping that the PR Prashant Sharma submitted would also include
> ability to check these things once committed !
> Thanks Kay
>
>
> On Sat, Feb 8, 2014 at 12:01 AM, Kay Ousterhout <no...@github.com>wrote:
>
>> I don't know of any precommit scripts (I think there's been talk of adding
>> a general style checker script but AFAIK it hasn't been done yet); I just
>> add highlighting in my editor so it's obvious when I'm writing lines that
>> are longer than 100 characters.
>>
>> --
>> Reply to this email directly or view it on GitHub<https://github.com/apache/incubator-spark/pull/517#issuecomment-34484190>
>> .
>
答复：[GitHub] incubator-spark pull request:
Posted by "欧阳晋(欧阳晋)" <ji...@alibaba-inc.com>.
I think may be like yarn , any JIRA creation will be forward to dev@ list , dev list also include discussion of new features and bugs , and all Jenkins build message for Pre commit . And any update of a specific JIRA, like assigne or comment will be forward to issues@ list. yarn also have a commit@ list if any svn ci happens . Maybe we can use some of it , it's just a advice ^_^
------------------------------------------------------------------
发件人：Xuefeng Wu <be...@gmail.com>
发送时间：2014年2月8日(星期六) 14:34
收件人：dev@spark.incubator.apache.org <de...@spark.incubator.apache.org>
主 题：Re: [GitHub] incubator-spark pull request:
github have this feature, but these mails are from git@git.apache.org. I
think some github information are filtered.
https://github.com/blog/811-reply-to-comments-from-email
On Sat, Feb 8, 2014 at 2:21 PM, Reynold Xin <rx...@databricks.com> wrote:
> I don't think it does.
>
>
> On Fri, Feb 7, 2014 at 8:58 PM, Nan Zhu <zh...@gmail.com> wrote:
>
> > If we reply these emails, will the reply be posted on pull request
> > discussion board automatically?
> >
> > if yes, that would be very nice
> >
> > --
> > Nan Zhu
> >
> >
> >
> > On Friday, February 7, 2014 at 9:23 PM, Henry Saputra wrote:
> >
> > > I am with Chris on this one.
> > >
> > > These github notifications are similar to JIRA updates that in most
> > > ASF projects are sent to dev@ list, and these are valid messages that
> > > contributors in the project should concern about.
> > >
> > > Especially the PPMCs (which willl be PMCs hopefully soon) need to know
> > > about them and become audit trail/ archive of development discussions
> > > for ASF.
> > >
> > > We already have user@ list which targeted for people interested to ask
> > > for questions using Spark and should be the proper list for people
> > > interested on using Spark.
> > >
> > > As Matei have said, you can filter these github notifications email
> > easily.
> > >
> > > Thanks,
> > >
> > >
> > > - Henry
> > >
> > >
> > > On Fri, Feb 7, 2014 at 6:02 PM, Chris Mattmann <mattmann@apache.org
> (mailto:
> > mattmann@apache.org)> wrote:
> > > > Guys this Github discussion seems like dev discussion in which case
> it
> > > > must be
> > > > on dev list and not moved - the whole point of this is that
> > development,
> > > > including
> > > > conversations related to it, which are the lifeblood of the project
> > should
> > > > occur
> > > > on the ASF mailing lists.
> > > >
> > > > Refactoring the lists is one thing for the more automated messages,
> > but the
> > > > comments below look like Kay commenting on some relevant stuff in
> which
> > > > case
> > > > I would argue against (paraphrased) "moving it to some ASF list that
> > those
> > > > who
> > > > care can subscribe to". "Those who care" in this case should be
> people
> > who
> > > > care about Kay's comments (which aren't automated commit messages
> from
> > > > some bot;
> > > > they are relevant dev comments) in which case "those who care" should
> > be
> > > > the
> > > > PMC.
> > > >
> > > > My suggestion is if there is a notifications list set up, it can be
> > like
> > > > for
> > > > automated stuff - but *NOT* for dev discussion -- that needs to
> happen
> > on
> > > > the
> > > > dev lists. If it's on another list, then I would expect periodically
> > > > (frequently;
> > > > with enough diligence to VOTE on and discuss and contribute to) to
> see
> > that
> > > > flushed or summarized on the dev list.
> > > >
> > > > Cheers,
> > > > Chris
> > > >
> > > >
> > > >
> > > >
> > > > -----Original Message-----
> > > > From: Andrew Ash <andrew@andrewash.com (mailto:andrew@andrewash.com
> )>
> > > > Reply-To: "dev@spark.incubator.apache.org (mailto:
> > dev@spark.incubator.apache.org)" <dev@spark.incubator.apache.org(mailto:
> > dev@spark.incubator.apache.org)>
> > > > Date: Friday, February 7, 2014 5:43 PM
> > > > To: "dev@spark.incubator.apache.org (mailto:
> > dev@spark.incubator.apache.org)" <dev@spark.incubator.apache.org(mailto:
> > dev@spark.incubator.apache.org)>
> > > > Subject: Re: [GitHub] incubator-spark pull request:
> > > >
> > > > > +1 on moving this stuff to a separate mailing list. It's Apache
> > policy
> > > > > that discussion is archived, but it's not policy that it must be
> > > > > interleaved with other dev discussion. Let's move it to a
> > > > > spark-github-discuss list (or a different name) and people who care
> > to see
> > > > > it can subscribe.
> > > > >
> > > > >
> > > > > On Fri, Feb 7, 2014 at 5:19 PM, Reynold Xin <rxin@databricks.com
> (mailto:
> > rxin@databricks.com)> wrote:
> > > > >
> > > > > > I concur wholeheartedly ...
> > > > > >
> > > > > >
> > > > > > On Fri, Feb 7, 2014 at 4:55 PM, Dean Wampler <
> > deanwampler@gmail.com (mailto:deanwampler@gmail.com)>
> > > > > > wrote:
> > > > > >
> > > > > > > This SPAM is not doing anyone any good. How about another
> > mailing list
> > > > > > for
> > > > > > > people who want to see this?
> > > > > > >
> > > > > > > Sent from my rotary phone.
> > > > > > >
> > > > > > >
> > > > > > > > On Feb 7, 2014, at 10:33 AM, mridulm <git@git.apache.org
> (mailto:
> > git@git.apache.org)> wrote:
> > > > > > > >
> > > > > > > > Github user mridulm commented on the pull request:
> > > > > >
> > https://github.com/apache/incubator-spark/pull/517#issuecomment-34484468
> > > > > > > >
> > > > > > > > I am hoping that the PR Prashant Sharma submitted would also
> > > > > > include
> > > > > > > > ability to check these things once committed !
> > > > > > > > Thanks Kay
> > > > > > > >
> > > > > > > >
> > > > > > > > On Sat, Feb 8, 2014 at 12:01 AM, Kay Ousterhout <
> > > > > > > notifications@github.com (mailto:notifications@github.com
> > )>wrote:
> > > > > > > >
> > > > > > > > > I don't know of any precommit scripts (I think there's been
> > talk of
> > > > > > > adding
> > > > > > > > > a general style checker script but AFAIK it hasn't been
> done
> > yet);
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > > > I
> > > > > > > just
> > > > > > > > > add highlighting in my editor so it's obvious when I'm
> > writing
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > > > lines
> > > > > > > that
> > > > > > > > > are longer than 100 characters.
> > > > > > > > >
> > > > > > > > > --
> > > > > > > > > Reply to this email directly or view it on GitHub<
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > https://github.com/apache/incubator-spark/pull/517#issuecomment-34484190
> > > > > > >
> > > > > > > > > .
> >
> >
>
--
~Yours, Xuefeng Wu/吴雪峰 敬上
Re: [GitHub] incubator-spark pull request:
Posted by Xuefeng Wu <be...@gmail.com>.
github have this feature, but these mails are from git@git.apache.org. I
think some github information are filtered.
https://github.com/blog/811-reply-to-comments-from-email
On Sat, Feb 8, 2014 at 2:21 PM, Reynold Xin <rx...@databricks.com> wrote:
> I don't think it does.
>
>
> On Fri, Feb 7, 2014 at 8:58 PM, Nan Zhu <zh...@gmail.com> wrote:
>
> > If we reply these emails, will the reply be posted on pull request
> > discussion board automatically?
> >
> > if yes, that would be very nice
> >
> > --
> > Nan Zhu
> >
> >
> >
> > On Friday, February 7, 2014 at 9:23 PM, Henry Saputra wrote:
> >
> > > I am with Chris on this one.
> > >
> > > These github notifications are similar to JIRA updates that in most
> > > ASF projects are sent to dev@ list, and these are valid messages that
> > > contributors in the project should concern about.
> > >
> > > Especially the PPMCs (which willl be PMCs hopefully soon) need to know
> > > about them and become audit trail/ archive of development discussions
> > > for ASF.
> > >
> > > We already have user@ list which targeted for people interested to ask
> > > for questions using Spark and should be the proper list for people
> > > interested on using Spark.
> > >
> > > As Matei have said, you can filter these github notifications email
> > easily.
> > >
> > > Thanks,
> > >
> > >
> > > - Henry
> > >
> > >
> > > On Fri, Feb 7, 2014 at 6:02 PM, Chris Mattmann <mattmann@apache.org
> (mailto:
> > mattmann@apache.org)> wrote:
> > > > Guys this Github discussion seems like dev discussion in which case
> it
> > > > must be
> > > > on dev list and not moved - the whole point of this is that
> > development,
> > > > including
> > > > conversations related to it, which are the lifeblood of the project
> > should
> > > > occur
> > > > on the ASF mailing lists.
> > > >
> > > > Refactoring the lists is one thing for the more automated messages,
> > but the
> > > > comments below look like Kay commenting on some relevant stuff in
> which
> > > > case
> > > > I would argue against (paraphrased) "moving it to some ASF list that
> > those
> > > > who
> > > > care can subscribe to". "Those who care" in this case should be
> people
> > who
> > > > care about Kay's comments (which aren't automated commit messages
> from
> > > > some bot;
> > > > they are relevant dev comments) in which case "those who care" should
> > be
> > > > the
> > > > PMC.
> > > >
> > > > My suggestion is if there is a notifications list set up, it can be
> > like
> > > > for
> > > > automated stuff - but *NOT* for dev discussion -- that needs to
> happen
> > on
> > > > the
> > > > dev lists. If it's on another list, then I would expect periodically
> > > > (frequently;
> > > > with enough diligence to VOTE on and discuss and contribute to) to
> see
> > that
> > > > flushed or summarized on the dev list.
> > > >
> > > > Cheers,
> > > > Chris
> > > >
> > > >
> > > >
> > > >
> > > > -----Original Message-----
> > > > From: Andrew Ash <andrew@andrewash.com (mailto:andrew@andrewash.com
> )>
> > > > Reply-To: "dev@spark.incubator.apache.org (mailto:
> > dev@spark.incubator.apache.org)" <dev@spark.incubator.apache.org(mailto:
> > dev@spark.incubator.apache.org)>
> > > > Date: Friday, February 7, 2014 5:43 PM
> > > > To: "dev@spark.incubator.apache.org (mailto:
> > dev@spark.incubator.apache.org)" <dev@spark.incubator.apache.org(mailto:
> > dev@spark.incubator.apache.org)>
> > > > Subject: Re: [GitHub] incubator-spark pull request:
> > > >
> > > > > +1 on moving this stuff to a separate mailing list. It's Apache
> > policy
> > > > > that discussion is archived, but it's not policy that it must be
> > > > > interleaved with other dev discussion. Let's move it to a
> > > > > spark-github-discuss list (or a different name) and people who care
> > to see
> > > > > it can subscribe.
> > > > >
> > > > >
> > > > > On Fri, Feb 7, 2014 at 5:19 PM, Reynold Xin <rxin@databricks.com
> (mailto:
> > rxin@databricks.com)> wrote:
> > > > >
> > > > > > I concur wholeheartedly ...
> > > > > >
> > > > > >
> > > > > > On Fri, Feb 7, 2014 at 4:55 PM, Dean Wampler <
> > deanwampler@gmail.com (mailto:deanwampler@gmail.com)>
> > > > > > wrote:
> > > > > >
> > > > > > > This SPAM is not doing anyone any good. How about another
> > mailing list
> > > > > > for
> > > > > > > people who want to see this?
> > > > > > >
> > > > > > > Sent from my rotary phone.
> > > > > > >
> > > > > > >
> > > > > > > > On Feb 7, 2014, at 10:33 AM, mridulm <git@git.apache.org
> (mailto:
> > git@git.apache.org)> wrote:
> > > > > > > >
> > > > > > > > Github user mridulm commented on the pull request:
> > > > > >
> > https://github.com/apache/incubator-spark/pull/517#issuecomment-34484468
> > > > > > > >
> > > > > > > > I am hoping that the PR Prashant Sharma submitted would also
> > > > > > include
> > > > > > > > ability to check these things once committed !
> > > > > > > > Thanks Kay
> > > > > > > >
> > > > > > > >
> > > > > > > > On Sat, Feb 8, 2014 at 12:01 AM, Kay Ousterhout <
> > > > > > > notifications@github.com (mailto:notifications@github.com
> > )>wrote:
> > > > > > > >
> > > > > > > > > I don't know of any precommit scripts (I think there's been
> > talk of
> > > > > > > adding
> > > > > > > > > a general style checker script but AFAIK it hasn't been
> done
> > yet);
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > > > I
> > > > > > > just
> > > > > > > > > add highlighting in my editor so it's obvious when I'm
> > writing
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > > > lines
> > > > > > > that
> > > > > > > > > are longer than 100 characters.
> > > > > > > > >
> > > > > > > > > --
> > > > > > > > > Reply to this email directly or view it on GitHub<
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > https://github.com/apache/incubator-spark/pull/517#issuecomment-34484190
> > > > > > >
> > > > > > > > > .
> >
> >
>
--
~Yours, Xuefeng Wu/吴雪峰 敬上
Re: [GitHub] incubator-spark pull request:
Posted by Reynold Xin <rx...@databricks.com>.
I don't think it does.
On Fri, Feb 7, 2014 at 8:58 PM, Nan Zhu <zh...@gmail.com> wrote:
> If we reply these emails, will the reply be posted on pull request
> discussion board automatically?
>
> if yes, that would be very nice
>
> --
> Nan Zhu
>
>
>
> On Friday, February 7, 2014 at 9:23 PM, Henry Saputra wrote:
>
> > I am with Chris on this one.
> >
> > These github notifications are similar to JIRA updates that in most
> > ASF projects are sent to dev@ list, and these are valid messages that
> > contributors in the project should concern about.
> >
> > Especially the PPMCs (which willl be PMCs hopefully soon) need to know
> > about them and become audit trail/ archive of development discussions
> > for ASF.
> >
> > We already have user@ list which targeted for people interested to ask
> > for questions using Spark and should be the proper list for people
> > interested on using Spark.
> >
> > As Matei have said, you can filter these github notifications email
> easily.
> >
> > Thanks,
> >
> >
> > - Henry
> >
> >
> > On Fri, Feb 7, 2014 at 6:02 PM, Chris Mattmann <mattmann@apache.org(mailto:
> mattmann@apache.org)> wrote:
> > > Guys this Github discussion seems like dev discussion in which case it
> > > must be
> > > on dev list and not moved - the whole point of this is that
> development,
> > > including
> > > conversations related to it, which are the lifeblood of the project
> should
> > > occur
> > > on the ASF mailing lists.
> > >
> > > Refactoring the lists is one thing for the more automated messages,
> but the
> > > comments below look like Kay commenting on some relevant stuff in which
> > > case
> > > I would argue against (paraphrased) "moving it to some ASF list that
> those
> > > who
> > > care can subscribe to". "Those who care" in this case should be people
> who
> > > care about Kay's comments (which aren't automated commit messages from
> > > some bot;
> > > they are relevant dev comments) in which case "those who care" should
> be
> > > the
> > > PMC.
> > >
> > > My suggestion is if there is a notifications list set up, it can be
> like
> > > for
> > > automated stuff - but *NOT* for dev discussion -- that needs to happen
> on
> > > the
> > > dev lists. If it's on another list, then I would expect periodically
> > > (frequently;
> > > with enough diligence to VOTE on and discuss and contribute to) to see
> that
> > > flushed or summarized on the dev list.
> > >
> > > Cheers,
> > > Chris
> > >
> > >
> > >
> > >
> > > -----Original Message-----
> > > From: Andrew Ash <andrew@andrewash.com (mailto:andrew@andrewash.com)>
> > > Reply-To: "dev@spark.incubator.apache.org (mailto:
> dev@spark.incubator.apache.org)" <dev@spark.incubator.apache.org (mailto:
> dev@spark.incubator.apache.org)>
> > > Date: Friday, February 7, 2014 5:43 PM
> > > To: "dev@spark.incubator.apache.org (mailto:
> dev@spark.incubator.apache.org)" <dev@spark.incubator.apache.org (mailto:
> dev@spark.incubator.apache.org)>
> > > Subject: Re: [GitHub] incubator-spark pull request:
> > >
> > > > +1 on moving this stuff to a separate mailing list. It's Apache
> policy
> > > > that discussion is archived, but it's not policy that it must be
> > > > interleaved with other dev discussion. Let's move it to a
> > > > spark-github-discuss list (or a different name) and people who care
> to see
> > > > it can subscribe.
> > > >
> > > >
> > > > On Fri, Feb 7, 2014 at 5:19 PM, Reynold Xin <rxin@databricks.com(mailto:
> rxin@databricks.com)> wrote:
> > > >
> > > > > I concur wholeheartedly ...
> > > > >
> > > > >
> > > > > On Fri, Feb 7, 2014 at 4:55 PM, Dean Wampler <
> deanwampler@gmail.com (mailto:deanwampler@gmail.com)>
> > > > > wrote:
> > > > >
> > > > > > This SPAM is not doing anyone any good. How about another
> mailing list
> > > > > for
> > > > > > people who want to see this?
> > > > > >
> > > > > > Sent from my rotary phone.
> > > > > >
> > > > > >
> > > > > > > On Feb 7, 2014, at 10:33 AM, mridulm <git@git.apache.org(mailto:
> git@git.apache.org)> wrote:
> > > > > > >
> > > > > > > Github user mridulm commented on the pull request:
> > > > >
> https://github.com/apache/incubator-spark/pull/517#issuecomment-34484468
> > > > > > >
> > > > > > > I am hoping that the PR Prashant Sharma submitted would also
> > > > > include
> > > > > > > ability to check these things once committed !
> > > > > > > Thanks Kay
> > > > > > >
> > > > > > >
> > > > > > > On Sat, Feb 8, 2014 at 12:01 AM, Kay Ousterhout <
> > > > > > notifications@github.com (mailto:notifications@github.com
> )>wrote:
> > > > > > >
> > > > > > > > I don't know of any precommit scripts (I think there's been
> talk of
> > > > > > adding
> > > > > > > > a general style checker script but AFAIK it hasn't been done
> yet);
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > > > I
> > > > > > just
> > > > > > > > add highlighting in my editor so it's obvious when I'm
> writing
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > > > lines
> > > > > > that
> > > > > > > > are longer than 100 characters.
> > > > > > > >
> > > > > > > > --
> > > > > > > > Reply to this email directly or view it on GitHub<
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > > >
> https://github.com/apache/incubator-spark/pull/517#issuecomment-34484190
> > > > > >
> > > > > > > > .
>
>
Re: [GitHub] incubator-spark pull request:
Posted by Nan Zhu <zh...@gmail.com>.
If we reply these emails, will the reply be posted on pull request discussion board automatically?
if yes, that would be very nice
--
Nan Zhu
On Friday, February 7, 2014 at 9:23 PM, Henry Saputra wrote:
> I am with Chris on this one.
>
> These github notifications are similar to JIRA updates that in most
> ASF projects are sent to dev@ list, and these are valid messages that
> contributors in the project should concern about.
>
> Especially the PPMCs (which willl be PMCs hopefully soon) need to know
> about them and become audit trail/ archive of development discussions
> for ASF.
>
> We already have user@ list which targeted for people interested to ask
> for questions using Spark and should be the proper list for people
> interested on using Spark.
>
> As Matei have said, you can filter these github notifications email easily.
>
> Thanks,
>
>
> - Henry
>
>
> On Fri, Feb 7, 2014 at 6:02 PM, Chris Mattmann <mattmann@apache.org (mailto:mattmann@apache.org)> wrote:
> > Guys this Github discussion seems like dev discussion in which case it
> > must be
> > on dev list and not moved - the whole point of this is that development,
> > including
> > conversations related to it, which are the lifeblood of the project should
> > occur
> > on the ASF mailing lists.
> >
> > Refactoring the lists is one thing for the more automated messages, but the
> > comments below look like Kay commenting on some relevant stuff in which
> > case
> > I would argue against (paraphrased) "moving it to some ASF list that those
> > who
> > care can subscribe to". "Those who care" in this case should be people who
> > care about Kay's comments (which aren't automated commit messages from
> > some bot;
> > they are relevant dev comments) in which case "those who care" should be
> > the
> > PMC.
> >
> > My suggestion is if there is a notifications list set up, it can be like
> > for
> > automated stuff - but *NOT* for dev discussion -- that needs to happen on
> > the
> > dev lists. If it's on another list, then I would expect periodically
> > (frequently;
> > with enough diligence to VOTE on and discuss and contribute to) to see that
> > flushed or summarized on the dev list.
> >
> > Cheers,
> > Chris
> >
> >
> >
> >
> > -----Original Message-----
> > From: Andrew Ash <andrew@andrewash.com (mailto:andrew@andrewash.com)>
> > Reply-To: "dev@spark.incubator.apache.org (mailto:dev@spark.incubator.apache.org)" <dev@spark.incubator.apache.org (mailto:dev@spark.incubator.apache.org)>
> > Date: Friday, February 7, 2014 5:43 PM
> > To: "dev@spark.incubator.apache.org (mailto:dev@spark.incubator.apache.org)" <dev@spark.incubator.apache.org (mailto:dev@spark.incubator.apache.org)>
> > Subject: Re: [GitHub] incubator-spark pull request:
> >
> > > +1 on moving this stuff to a separate mailing list. It's Apache policy
> > > that discussion is archived, but it's not policy that it must be
> > > interleaved with other dev discussion. Let's move it to a
> > > spark-github-discuss list (or a different name) and people who care to see
> > > it can subscribe.
> > >
> > >
> > > On Fri, Feb 7, 2014 at 5:19 PM, Reynold Xin <rxin@databricks.com (mailto:rxin@databricks.com)> wrote:
> > >
> > > > I concur wholeheartedly ...
> > > >
> > > >
> > > > On Fri, Feb 7, 2014 at 4:55 PM, Dean Wampler <deanwampler@gmail.com (mailto:deanwampler@gmail.com)>
> > > > wrote:
> > > >
> > > > > This SPAM is not doing anyone any good. How about another mailing list
> > > > for
> > > > > people who want to see this?
> > > > >
> > > > > Sent from my rotary phone.
> > > > >
> > > > >
> > > > > > On Feb 7, 2014, at 10:33 AM, mridulm <git@git.apache.org (mailto:git@git.apache.org)> wrote:
> > > > > >
> > > > > > Github user mridulm commented on the pull request:
> > > > https://github.com/apache/incubator-spark/pull/517#issuecomment-34484468
> > > > > >
> > > > > > I am hoping that the PR Prashant Sharma submitted would also
> > > > include
> > > > > > ability to check these things once committed !
> > > > > > Thanks Kay
> > > > > >
> > > > > >
> > > > > > On Sat, Feb 8, 2014 at 12:01 AM, Kay Ousterhout <
> > > > > notifications@github.com (mailto:notifications@github.com)>wrote:
> > > > > >
> > > > > > > I don't know of any precommit scripts (I think there's been talk of
> > > > > adding
> > > > > > > a general style checker script but AFAIK it hasn't been done yet);
> > > > > >
> > > > >
> > > > >
> > > >
> > > > I
> > > > > just
> > > > > > > add highlighting in my editor so it's obvious when I'm writing
> > > > > >
> > > > >
> > > > >
> > > >
> > > > lines
> > > > > that
> > > > > > > are longer than 100 characters.
> > > > > > >
> > > > > > > --
> > > > > > > Reply to this email directly or view it on GitHub<
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > > > https://github.com/apache/incubator-spark/pull/517#issuecomment-34484190
> > > > >
> > > > > > > .
Re: [GitHub] incubator-spark pull request:
Posted by Henry Saputra <he...@gmail.com>.
I am with Chris on this one.
These github notifications are similar to JIRA updates that in most
ASF projects are sent to dev@ list, and these are valid messages that
contributors in the project should concern about.
Especially the PPMCs (which willl be PMCs hopefully soon) need to know
about them and become audit trail/ archive of development discussions
for ASF.
We already have user@ list which targeted for people interested to ask
for questions using Spark and should be the proper list for people
interested on using Spark.
As Matei have said, you can filter these github notifications email easily.
Thanks,
- Henry
On Fri, Feb 7, 2014 at 6:02 PM, Chris Mattmann <ma...@apache.org> wrote:
> Guys this Github discussion seems like dev discussion in which case it
> must be
> on dev list and not moved - the whole point of this is that development,
> including
> conversations related to it, which are the lifeblood of the project should
> occur
> on the ASF mailing lists.
>
> Refactoring the lists is one thing for the more automated messages, but the
> comments below look like Kay commenting on some relevant stuff in which
> case
> I would argue against (paraphrased) "moving it to some ASF list that those
> who
> care can subscribe to". "Those who care" in this case should be people who
> care about Kay's comments (which aren't automated commit messages from
> some bot;
> they are relevant dev comments) in which case "those who care" should be
> the
> PMC.
>
> My suggestion is if there is a notifications list set up, it can be like
> for
> automated stuff - but *NOT* for dev discussion -- that needs to happen on
> the
> dev lists. If it's on another list, then I would expect periodically
> (frequently;
> with enough diligence to VOTE on and discuss and contribute to) to see that
> flushed or summarized on the dev list.
>
> Cheers,
> Chris
>
>
>
>
> -----Original Message-----
> From: Andrew Ash <an...@andrewash.com>
> Reply-To: "dev@spark.incubator.apache.org" <de...@spark.incubator.apache.org>
> Date: Friday, February 7, 2014 5:43 PM
> To: "dev@spark.incubator.apache.org" <de...@spark.incubator.apache.org>
> Subject: Re: [GitHub] incubator-spark pull request:
>
>>+1 on moving this stuff to a separate mailing list. It's Apache policy
>>that discussion is archived, but it's not policy that it must be
>>interleaved with other dev discussion. Let's move it to a
>>spark-github-discuss list (or a different name) and people who care to see
>>it can subscribe.
>>
>>
>>On Fri, Feb 7, 2014 at 5:19 PM, Reynold Xin <rx...@databricks.com> wrote:
>>
>>> I concur wholeheartedly ...
>>>
>>>
>>> On Fri, Feb 7, 2014 at 4:55 PM, Dean Wampler <de...@gmail.com>
>>> wrote:
>>>
>>> > This SPAM is not doing anyone any good. How about another mailing list
>>> for
>>> > people who want to see this?
>>> >
>>> > Sent from my rotary phone.
>>> >
>>> >
>>> > > On Feb 7, 2014, at 10:33 AM, mridulm <gi...@git.apache.org> wrote:
>>> > >
>>> > > Github user mridulm commented on the pull request:
>>> > >
>>> > >
>>> >
>>>https://github.com/apache/incubator-spark/pull/517#issuecomment-34484468
>>> > >
>>> > > I am hoping that the PR Prashant Sharma submitted would also
>>>include
>>> > > ability to check these things once committed !
>>> > > Thanks Kay
>>> > >
>>> > >
>>> > > On Sat, Feb 8, 2014 at 12:01 AM, Kay Ousterhout <
>>> > notifications@github.com>wrote:
>>> > >
>>> > >> I don't know of any precommit scripts (I think there's been talk of
>>> > adding
>>> > >> a general style checker script but AFAIK it hasn't been done yet);
>>>I
>>> > just
>>> > >> add highlighting in my editor so it's obvious when I'm writing
>>>lines
>>> > that
>>> > >> are longer than 100 characters.
>>> > >>
>>> > >> --
>>> > >> Reply to this email directly or view it on GitHub<
>>> >
>>>https://github.com/apache/incubator-spark/pull/517#issuecomment-34484190
>>> >
>>> > >> .
>>> > >
>>> >
>>>
>
>
Re: [GitHub] incubator-spark pull request:
Posted by Chris Mattmann <ma...@apache.org>.
Guys this Github discussion seems like dev discussion in which case it
must be
on dev list and not moved - the whole point of this is that development,
including
conversations related to it, which are the lifeblood of the project should
occur
on the ASF mailing lists.
Refactoring the lists is one thing for the more automated messages, but the
comments below look like Kay commenting on some relevant stuff in which
case
I would argue against (paraphrased) "moving it to some ASF list that those
who
care can subscribe to". "Those who care" in this case should be people who
care about Kay's comments (which aren't automated commit messages from
some bot;
they are relevant dev comments) in which case "those who care" should be
the
PMC.
My suggestion is if there is a notifications list set up, it can be like
for
automated stuff - but *NOT* for dev discussion -- that needs to happen on
the
dev lists. If it's on another list, then I would expect periodically
(frequently;
with enough diligence to VOTE on and discuss and contribute to) to see that
flushed or summarized on the dev list.
Cheers,
Chris
-----Original Message-----
From: Andrew Ash <an...@andrewash.com>
Reply-To: "dev@spark.incubator.apache.org" <de...@spark.incubator.apache.org>
Date: Friday, February 7, 2014 5:43 PM
To: "dev@spark.incubator.apache.org" <de...@spark.incubator.apache.org>
Subject: Re: [GitHub] incubator-spark pull request:
>+1 on moving this stuff to a separate mailing list. It's Apache policy
>that discussion is archived, but it's not policy that it must be
>interleaved with other dev discussion. Let's move it to a
>spark-github-discuss list (or a different name) and people who care to see
>it can subscribe.
>
>
>On Fri, Feb 7, 2014 at 5:19 PM, Reynold Xin <rx...@databricks.com> wrote:
>
>> I concur wholeheartedly ...
>>
>>
>> On Fri, Feb 7, 2014 at 4:55 PM, Dean Wampler <de...@gmail.com>
>> wrote:
>>
>> > This SPAM is not doing anyone any good. How about another mailing list
>> for
>> > people who want to see this?
>> >
>> > Sent from my rotary phone.
>> >
>> >
>> > > On Feb 7, 2014, at 10:33 AM, mridulm <gi...@git.apache.org> wrote:
>> > >
>> > > Github user mridulm commented on the pull request:
>> > >
>> > >
>> >
>>https://github.com/apache/incubator-spark/pull/517#issuecomment-34484468
>> > >
>> > > I am hoping that the PR Prashant Sharma submitted would also
>>include
>> > > ability to check these things once committed !
>> > > Thanks Kay
>> > >
>> > >
>> > > On Sat, Feb 8, 2014 at 12:01 AM, Kay Ousterhout <
>> > notifications@github.com>wrote:
>> > >
>> > >> I don't know of any precommit scripts (I think there's been talk of
>> > adding
>> > >> a general style checker script but AFAIK it hasn't been done yet);
>>I
>> > just
>> > >> add highlighting in my editor so it's obvious when I'm writing
>>lines
>> > that
>> > >> are longer than 100 characters.
>> > >>
>> > >> --
>> > >> Reply to this email directly or view it on GitHub<
>> >
>>https://github.com/apache/incubator-spark/pull/517#issuecomment-34484190
>> >
>> > >> .
>> > >
>> >
>>
Re: [GitHub] incubator-spark pull request:
Posted by Matei Zaharia <ma...@gmail.com>.
Sorry for the spam, guys. I’m going to work on getting a separate mailing list, but we needed to have an initial version of this quickly. Note that you can filter all these emails as they come from git@git.apache.org.
Matei
On Feb 7, 2014, at 5:43 PM, Andrew Ash <an...@andrewash.com> wrote:
> +1 on moving this stuff to a separate mailing list. It's Apache policy
> that discussion is archived, but it's not policy that it must be
> interleaved with other dev discussion. Let's move it to a
> spark-github-discuss list (or a different name) and people who care to see
> it can subscribe.
>
>
> On Fri, Feb 7, 2014 at 5:19 PM, Reynold Xin <rx...@databricks.com> wrote:
>
>> I concur wholeheartedly ...
>>
>>
>> On Fri, Feb 7, 2014 at 4:55 PM, Dean Wampler <de...@gmail.com>
>> wrote:
>>
>>> This SPAM is not doing anyone any good. How about another mailing list
>> for
>>> people who want to see this?
>>>
>>> Sent from my rotary phone.
>>>
>>>
>>>> On Feb 7, 2014, at 10:33 AM, mridulm <gi...@git.apache.org> wrote:
>>>>
>>>> Github user mridulm commented on the pull request:
>>>>
>>>>
>>> https://github.com/apache/incubator-spark/pull/517#issuecomment-34484468
>>>>
>>>> I am hoping that the PR Prashant Sharma submitted would also include
>>>> ability to check these things once committed !
>>>> Thanks Kay
>>>>
>>>>
>>>> On Sat, Feb 8, 2014 at 12:01 AM, Kay Ousterhout <
>>> notifications@github.com>wrote:
>>>>
>>>>> I don't know of any precommit scripts (I think there's been talk of
>>> adding
>>>>> a general style checker script but AFAIK it hasn't been done yet); I
>>> just
>>>>> add highlighting in my editor so it's obvious when I'm writing lines
>>> that
>>>>> are longer than 100 characters.
>>>>>
>>>>> --
>>>>> Reply to this email directly or view it on GitHub<
>>> https://github.com/apache/incubator-spark/pull/517#issuecomment-34484190
>>>
>>>>> .
>>>>
>>>
>>
Re: [GitHub] incubator-spark pull request:
Posted by Andrew Ash <an...@andrewash.com>.
+1 on moving this stuff to a separate mailing list. It's Apache policy
that discussion is archived, but it's not policy that it must be
interleaved with other dev discussion. Let's move it to a
spark-github-discuss list (or a different name) and people who care to see
it can subscribe.
On Fri, Feb 7, 2014 at 5:19 PM, Reynold Xin <rx...@databricks.com> wrote:
> I concur wholeheartedly ...
>
>
> On Fri, Feb 7, 2014 at 4:55 PM, Dean Wampler <de...@gmail.com>
> wrote:
>
> > This SPAM is not doing anyone any good. How about another mailing list
> for
> > people who want to see this?
> >
> > Sent from my rotary phone.
> >
> >
> > > On Feb 7, 2014, at 10:33 AM, mridulm <gi...@git.apache.org> wrote:
> > >
> > > Github user mridulm commented on the pull request:
> > >
> > >
> > https://github.com/apache/incubator-spark/pull/517#issuecomment-34484468
> > >
> > > I am hoping that the PR Prashant Sharma submitted would also include
> > > ability to check these things once committed !
> > > Thanks Kay
> > >
> > >
> > > On Sat, Feb 8, 2014 at 12:01 AM, Kay Ousterhout <
> > notifications@github.com>wrote:
> > >
> > >> I don't know of any precommit scripts (I think there's been talk of
> > adding
> > >> a general style checker script but AFAIK it hasn't been done yet); I
> > just
> > >> add highlighting in my editor so it's obvious when I'm writing lines
> > that
> > >> are longer than 100 characters.
> > >>
> > >> --
> > >> Reply to this email directly or view it on GitHub<
> > https://github.com/apache/incubator-spark/pull/517#issuecomment-34484190
> >
> > >> .
> > >
> >
>
Re: [GitHub] incubator-spark pull request:
Posted by Reynold Xin <rx...@databricks.com>.
I concur wholeheartedly ...
On Fri, Feb 7, 2014 at 4:55 PM, Dean Wampler <de...@gmail.com> wrote:
> This SPAM is not doing anyone any good. How about another mailing list for
> people who want to see this?
>
> Sent from my rotary phone.
>
>
> > On Feb 7, 2014, at 10:33 AM, mridulm <gi...@git.apache.org> wrote:
> >
> > Github user mridulm commented on the pull request:
> >
> >
> https://github.com/apache/incubator-spark/pull/517#issuecomment-34484468
> >
> > I am hoping that the PR Prashant Sharma submitted would also include
> > ability to check these things once committed !
> > Thanks Kay
> >
> >
> > On Sat, Feb 8, 2014 at 12:01 AM, Kay Ousterhout <
> notifications@github.com>wrote:
> >
> >> I don't know of any precommit scripts (I think there's been talk of
> adding
> >> a general style checker script but AFAIK it hasn't been done yet); I
> just
> >> add highlighting in my editor so it's obvious when I'm writing lines
> that
> >> are longer than 100 characters.
> >>
> >> --
> >> Reply to this email directly or view it on GitHub<
> https://github.com/apache/incubator-spark/pull/517#issuecomment-34484190>
> >> .
> >
>