Re: [VOTE] Subscribe dev@ to Github Activities

+1 Both GitHub issues and dev@ are aimed for development-related topics. It will be great if we could have a all-in-one place for discussion, and I believe Sheng's proposal is the answer. On 2018/07/16 03:32:06, Sheng Zha wrote: > Hi, > > I'm starting a vote on subscribing dev@ to Github

[RESULT][VOTE] Subscribe dev@ to Github Activities

Hi, The vote concluded at 9PM today (2018/07/18), and here are the results: +1 Timur Shenkao Aaron Markham Lin Yuan Anirudh Acharya Junru Shao Yizhi Liu (committer) Zhi Zhang (committer) Tianqi Chen (committer) Sheng Zha (committer) -1 Qing Lan Rahul Huilgol K, S Anirudh (committer) Chris

Re: [VOTE] Subscribe dev@ to Github Activities

While I do agree that the GitHub issue triaging should be improved, possibly by moving more user discussions to the discuss forum/user list. I already see there is a good effort on triaging the issues. I do think forwarding GitHub activities are a good first step to make people aware of what is

Re: [VOTE] Subscribe dev@ to Github Activities

The point is not that valuable discussion does not happen on Github. The point is that mails about it will be dwarfed by the other activity on Github. On Wed, Jul 18, 2018 at 10:30 AM, Tianqi Chen wrote: > Being Apache is about being inclusive to the new contributors. Apache > encourages the

Re: [VOTE] Subscribe dev@ to Github Activities

You should explicitly tell potential contributors what you expect of them. Here is what you document: https://github.com/apache/incubator-mxnet/blob/master/docs/community/contribute.md There is nothing there that tells contributors to discuss proposals on dev first. It sounds like that needs

Re: [VOTE] Subscribe dev@ to Github Activities

Being Apache is about being inclusive to the new contributors. Apache encourages the use of Github, and currently, the community is doing so. I don't think it is a good idea to use political terms to force proliferate our contributors --- we are all Apache contributors. Instead, we should make

Re: [VOTE] Subscribe dev@ to Github Activities

to know about github discussions, you’d need to scan all issues and prs constantly which isn’t a reasonable expectation. dev is where discussions are supposed to happen in a apache, PERIOD. Apache isn’t dmlc. I wish some people would stop trying to turn Apache conventions into dmlc conventions.

Re: [VOTE] Subscribe dev@ to Github Activities

Discussions happened on Github are highly valuable, as a matter of fact, we have quite a lot of proliferating contributors who discuss things on GitHub when they contribute. We need to be inclusive to these contributors, to welcome and recognize these discussions. The filtering solutions seem to

Re: [VOTE] Subscribe dev@ to Github Activities

Thanks, I hear the concerns and it's not my intention to push people off the list. On the other hand, I think github discussions are no more "artificial" than discussions on dev list, and the good and important discussions warrant the same amount of attention. With this vote, I intend to make

Re: [VOTE] Subscribe dev@ to Github Activities

A discussion is a discussion, and in the case of MXNet I’d say a lot more high quality discussion has happened on GitHub than on dev@. Github issues have plenty of discussions before code change. The reason is simply because MXNet has longer history on Github than the existence of dev list, and

Re: [VOTE] Subscribe dev@ to Github Activities

Can't you simply tell contributors to discuss changes on dev before submitting a PR? Since the contribution guidelines don't tell developers to post to dev, why would you expect them to do that? Is there an easy way to just subscribe to PR notifications or will someone have to write a filter

Re: [VOTE] Subscribe dev@ to Github Activities

Some mentors/contributors/committees feel that the amount of discussions in dev list is too less given the amount of commits that happen and more discussions need to happen in the dev list to grow the community. In response some committees feel discussions actually happen in GitHub PRs. If the

Re: [VOTE] Subscribe dev@ to Github Activities

Can't people already subscribe to github notifications? I think it is safe to assume that developers are already smart enough to figure out how to do that if they want. What problem are you really trying to solve here? On 7/18/18, 4:49 AM, "Chris Olivier" wrote: -1. (changed from -0.9)

Re: [VOTE] Subscribe dev@ to Github Activities

-1. (changed from -0.9) seems more like a strategy (whether intentional or on accident) to *not* have design discussions on dev by flooding it with noise and then later claim it was discussed, even though you would have to sift through thousands of emails to find it. On Wed, Jul 18, 2018 at

Re: [VOTE] Subscribe dev@ to Github Activities

I pulled up some more stats so we can make an informed decision. Here are some popular Apache projects and the number of emails to their dev@ list in the last 30 days Apache Flink: 540 mails ​Apache Spark: 249 mails Apache Hive: 481 mails Apache HBase: 300 mails Current dev list for MXNet: 348

Re: [VOTE] Subscribe dev@ to Github Activities

cular PR, >> those >>>>> emails will also come from "notificati...@github.com". There are >> ways >>>>> around that though. >>>>> >>>>> >>>>> It might be good to mention this filter in some wiki/webpage

Re: [VOTE] Subscribe dev@ to Github Activities

eople trying to find the right set of > > filters. > > > It > > > > could even be in the welcome email when one subscribes to this > > > email-list. > > > > > > > > > > > > Another alternate option: How about choosin

Re: [VOTE] Subscribe dev@ to Github Activities

s > > email-list. > > > > > > > > > Another alternate option: How about choosing an opt-in model rather > than > > > an opt-out model? Having another email list and anyone can subscribe to > > it > > > if they wish. > > > > >

Re: [VOTE] Subscribe dev@ to Github Activities

gt; could even be in the welcome email when one subscribes to this > > email-list. > > > > > > > > > Another alternate option: How about choosing an opt-in model > rather than > > > an opt-out model? Having another email list and any

Re: [VOTE] Subscribe dev@ to Github Activities

opt-out model? Having another email list and anyone can subscribe to > it > > if they wish. > > > > > > Not sure if there is a perfect answer out there for this but in principle > > I agree that it will be good to have "push notifications" for all

Re: [VOTE] Subscribe dev@ to Github Activities

> > if they wish. > > > > > > Not sure if there is a perfect answer out there for this but in principle > > I agree that it will be good to have "push notifications" for all > PRs/issue. > > > > > > -Pracheer > > > > >

Re: [VOTE] Subscribe dev@ to Github Activities

+1 On Tue, Jul 17, 2018 at 12:55 PM Joshua Z. Zhang wrote: > > +1 > > We NEED to bring valuable discussions to a centralized place (@dev for > example) rather than scattered single threads. > Per filter options, there are a lot we can do to improve the SNR. > > Zhi > > On 2018/07/17 16:26:01,

Re: [VOTE] Subscribe dev@ to Github Activities

+1 We NEED to bring valuable discussions to a centralized place (@dev for example) rather than scattered single threads. Per filter options, there are a lot we can do to improve the SNR. Zhi On 2018/07/17 16:26:01, Sheng Zha wrote: > Hi Anirudh, > > 1. You need exactly one filter to filter

Re: [VOTE] Subscribe dev@ to Github Activities

___ > From: Junru Shao > Sent: Tuesday, July 17, 2018 10:58:33 AM > To: d...@mxnet.apache.org > Subject: Re: [VOTE] Subscribe dev@ to Github Activities > > +1 > > Both GitHub activities and dev list are places for development. It will be > great if we

Re: [VOTE] Subscribe dev@ to Github Activities

_ From: Junru Shao Sent: Tuesday, July 17, 2018 10:58:33 AM To: d...@mxnet.apache.org Subject: Re: [VOTE] Subscribe dev@ to Github Activities +1 Both GitHub activities and dev list are places for development. It will be great if we could have a all-in-one place for such discussion

Re: [VOTE] Subscribe dev@ to Github Activities

+1 Both GitHub activities and dev list are places for development. It will be great if we could have a all-in-one place for such discussions. I believe Sheng's proposal is a perfect solution. On 2018/07/16 03:32:06, Sheng Zha wrote: > Hi, > > I'm starting a vote on subscribing dev@ to

Re: [VOTE] Subscribe dev@ to Github Activities

+1 Both GitHub activities and dev list are places for development. It will be great if we could have a all-in-one place for such discussions. I believe Sheng's proposal is a perfect solution. On 2018/07/16 03:32:06, Sheng Zha wrote: > Hi, > > I'm starting a vote on subscribing dev@ to Github

Re: [VOTE] Subscribe dev@ to Github Activities

+1 On Tue, Jul 17, 2018 at 9:58 AM Anirudh wrote: > Its not foregoing transparency since people can easily subscribe to the > github activities individually. dev@ has been used till now for design > discussions, other project discussions, > votes etc. After we subscribe dev@ to all activities,

Re: [VOTE] Subscribe dev@ to Github Activities

Its not foregoing transparency since people can easily subscribe to the github activities individually. dev@ has been used till now for design discussions, other project discussions, votes etc. After we subscribe dev@ to all activities, I am afraid dev@ will be reduced to a forwarded mail box and

Re: [VOTE] Subscribe dev@ to Github Activities

-1, unless we can keep this under control. It's not all of the PRs or Issues worthwhile to be involved into discussion. I hope we can put this under control such as @subscribe_dev as a bot to spread the information to dev@. Thanks, Qing On 7/17/18, 9:26 AM, "Lin Yuan" wrote: +1, I

Re: [VOTE] Subscribe dev@ to Github Activities

+1, I think they are very relevant to dev and as Aaron said we can always set up personalized filter. On Tue, Jul 17, 2018 at 9:21 AM Aaron Markham wrote: > +1, I don't read your emails anyways. Just kidding. I think it would be > good to see the action, even if I eventually have to setup

Re: [VOTE] Subscribe dev@ to Github Activities

Hi Anirudh, 1. You need exactly one filter to filter out all the github notifications on PRs and issues: "from:notificati...@github.com", and you'd get your S/N ratio back. 2. Having the option to do design discussion on an issue or PR is actually a good thing as many discussions are quite small

Re: [VOTE] Subscribe dev@ to Github Activities

+1, I don't read your emails anyways. Just kidding. I think it would be good to see the action, even if I eventually have to setup filters if it gets overwhelming. On Tue, Jul 17, 2018 at 9:15 AM, Tianqi Chen wrote: > +1, most of issue and PR activities are about development, and they belong >

Re: [VOTE] Subscribe dev@ to Github Activities

+1, most of issue and PR activities are about development, and they belong to dev. It also helps us to recognizes contributors who are actively contributing but less vocal via emails -- there are many of them. Tianqi On Tue, Jul 17, 2018 at 8:47 AM, Anirudh wrote: > -1 > > The low signal to

Re: [VOTE] Subscribe dev@ to Github Activities

+1 if my vote can be taken into account On Mon, Jul 16, 2018 at 4:32 AM, Sheng Zha wrote: > Hi, > > I'm starting a vote on subscribing dev@ to Github activities. See previous > discussion thread here >

[VOTE] Subscribe dev@ to Github Activities

Hi, I'm starting a vote on subscribing dev@ to Github activities. See previous discussion thread here . The vote lasts for three days and ends on 7/18/2018 at 9pm pst. -sz