+1 On Tue, Jul 17, 2018 at 12:55 PM Joshua Z. Zhang <cheungc...@gmail.com> 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, Sheng Zha <szha....@gmail.com> wrote: > > 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 and better accompanied by > > code. If for some reason a merged design needs revisiting, there's still > > the option of sending an email to dev@ and discuss about it. > > 3. About votes, commit vote (and veto) can already happen on PR per past > > agreement. The discussion for procedural vote IMO should be allowed to > > happen on Github if it's development related. Procedural votes themselves > > should and can still happen on dev@. > > > > About "you don't really have to do anything explicitly on the dev@ list", > > besides the above arguments, we don't send emails to dev@ just for the > > purpose of sending it. On the other hand, since "whatever didn't happen on > > dev list didn't happen", we'd need better arguments on why we'd choose to > > forego the transparency. > > > > -sz > > > > On Tue, Jul 17, 2018 at 8:47 AM, Anirudh <anirudh2...@gmail.com> wrote: > > > > > -1 > > > > > > The low signal to noise ratio would mean that we may miss important > > > emails. > > > Even with the different filters that we may setup for dev@, the emails > > > would be too many to not miss the important ones. We would see more and > > > more people starting a design discussion on an issue or PR. Because of the > > > low signal to noise ratio on the dev@ list, many may miss these > > > discussions. > > > > > > Slowly, this would erode the purpose of the dev@ list as this means that > > > you don't really have to do anything explicitly on the dev@ list. > > > You can start a design discussion on a github issue. You can start a > > > vote/discussion on a github issue. > > > > > > Anirudh > > > > > > On Mon, Jul 16, 2018 at 4:35 AM, Timur Shenkao <t...@timshenkao.su> wrote: > > > > > > > +1 if my vote can be taken into account > > > > > > > > On Mon, Jul 16, 2018 at 4:32 AM, Sheng Zha <szha....@gmail.com> wrote: > > > > > > > > > Hi, > > > > > > > > > > I'm starting a vote on subscribing dev@ to Github activities. See > > > > previous > > > > > discussion thread here > > > > > <https://lists.apache.org/thread.html/3d883f6a3cbc8e81e810962e0c0fe7 > > > > > bfd01f0b78d3cb44034f566442@%3Cdev.mxnet.apache.org%3E> > > > > > . > > > > > > > > > > The vote lasts for three days and ends on 7/18/2018 at 9pm pst. > > > > > > > > > > -sz > > > > > > > > > > > > > >
-- Yizhi Liu DMLC member Amazon Web Services Vancouver, Canada
