Re: [DISCUSS] Subscribe dev@ to Github Activities?
Thanks all for the discussion. Since there hasn't been more negative feedback on this, I will start a vote. -sz On Thu, Jul 12, 2018 at 3:37 PM, Anirudh Acharya wrote: > For concerns regarding signal and noise, I think we can get around that by > setting up the right kind of filters in the mail client. > Signal and Noise can be different for different people. > > > Regards, > Anirudh > > On Thu, Jul 12, 2018 at 3:34 PM Haibin Lin > wrote: > > > Agree. +1 for more transparency > > > > On Thu, Jul 12, 2018 at 3:27 PM, Zha, Sheng > > > wrote: > > > > > My intention is really just to bridge the gap between so much happening > > on > > > github v.s. "whatever didn't happen on dev list didn't happen". > > > > > > Also, since dev@ is intended to be an asynchronous way for community > to > > > follow technical conversations, there wasn't really a requirement for > > > anyone to read all of them in the first place. > > > > > > Best regards, > > > -sz > > > > > > On 7/12/18, 3:20 PM, "Timur Shenkao" wrote: > > > > > > Flink - yes > > > Spark - it was previously but not now > > > > > > Yeah, amount of messages would be tripled at least: Jira + Github > > > issue + PR > > > > > > On Thu, Jul 12, 2018 at 11:13 PM, Haibin Lin < > > haibin.lin@gmail.com > > > > > > > wrote: > > > > > > > I'm a bit concerned with the amount of emails flooding in. In the > > > past week > > > > there're 32 new issues and 35 new pull requests. This means on > avg > > > 10 email > > > > per day and I doubt I'll read all of them.. Does the Spark > > community > > > > subscribe dev@ to github? > > > > > > > > Best, > > > > Haibin > > > > > > > > On Thu, Jul 12, 2018 at 3:08 PM, Pedro Larroy < > > > > pedro.larroy.li...@gmail.com> > > > > wrote: > > > > > > > > > -1 It's a lot of traffic, whomever wants to subscribe can do > it > > > in > > > > > github. I'm afraid it will decrease signal to noise ratio in > the > > > list. > > > > > > > > > > On Thu, Jul 12, 2018 at 11:32 PM Lin Yuan > > > > wrote: > > > > > > > > > > > +1 > > > > > > > > > > > > On Thu, Jul 12, 2018 at 12:26 PM Anirudh Acharya < > > > > anirudhk...@gmail.com> > > > > > > wrote: > > > > > > > > > > > > > +1 > > > > > > > > > > > > > > On Thu, Jul 12, 2018 at 11:51 AM Piyush Ghai < > > > ghai.piy...@gmail.com> > > > > > > > wrote: > > > > > > > > > > > > > > > +1 > > > > > > > > > On Jul 12, 2018, at 11:50 AM, Tianqi Chen < > > > > > tqc...@cs.washington.edu> > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > +1 > > > > > > > > > > > > > > > > > > On Thu, Jul 12, 2018 at 11:10 AM, Sheng Zha < > > > szha@gmail.com> > > > > > > > wrote: > > > > > > > > > > > > > > > > > >> Hi all, > > > > > > > > >> > > > > > > > > >> Should we subscribe dev list to github updates on > mxnet > > > repo? > > > > Both > > > > > > > > github > > > > > > > > >> issues/PRs and the dev list are intended for technical > > > > discussions > > > > > > and > > > > > > > > in > > > > > > > > >> that aspect largely share the same goal. Since MXNet > has > > > most > > > > > > activity > > > > > > > > >> github, this could help dev@ to become more active. > > Some > > > pros > > > > and > > > > > > > cons: > > > > > > > > >> > > > > > > > > >> Pros: > > > > > > > > >> - There have been many high quality discussions that > > > happen on > > > > > > github > > > > > > > to > > > > > > > > >> which the dev list can benefit. > > > > > > > > >> - Replies on update emails are reflected on the > specific > > > > issue/PR. > > > > > > > > >> - Users can also choose to click on the link and go to > > > github to > > > > > > > > >> participate in discussion. > > > > > > > > >> - We still have the ability to carry out dev@ only > > > > conversation. > > > > > > > > >> > > > > > > > > >> Cons: > > > > > > > > >> - Higher volume on dev list. > > > > > > > > >> - Some discussions might not be suitable for dev@. > > > (though I > > > > > can't > > > > > > > > think > > > > > > > > >> of > > > > > > > > >> why such conversation should happen on github either) > > > > > > > > >> > > > > > > > > >> -sz > > > > > > > > >> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
Re: [DISCUSS] Subscribe dev@ to Github Activities?
For concerns regarding signal and noise, I think we can get around that by setting up the right kind of filters in the mail client. Signal and Noise can be different for different people. Regards, Anirudh On Thu, Jul 12, 2018 at 3:34 PM Haibin Lin wrote: > Agree. +1 for more transparency > > On Thu, Jul 12, 2018 at 3:27 PM, Zha, Sheng > wrote: > > > My intention is really just to bridge the gap between so much happening > on > > github v.s. "whatever didn't happen on dev list didn't happen". > > > > Also, since dev@ is intended to be an asynchronous way for community to > > follow technical conversations, there wasn't really a requirement for > > anyone to read all of them in the first place. > > > > Best regards, > > -sz > > > > On 7/12/18, 3:20 PM, "Timur Shenkao" wrote: > > > > Flink - yes > > Spark - it was previously but not now > > > > Yeah, amount of messages would be tripled at least: Jira + Github > > issue + PR > > > > On Thu, Jul 12, 2018 at 11:13 PM, Haibin Lin < > haibin.lin@gmail.com > > > > > wrote: > > > > > I'm a bit concerned with the amount of emails flooding in. In the > > past week > > > there're 32 new issues and 35 new pull requests. This means on avg > > 10 email > > > per day and I doubt I'll read all of them.. Does the Spark > community > > > subscribe dev@ to github? > > > > > > Best, > > > Haibin > > > > > > On Thu, Jul 12, 2018 at 3:08 PM, Pedro Larroy < > > > pedro.larroy.li...@gmail.com> > > > wrote: > > > > > > > -1 It's a lot of traffic, whomever wants to subscribe can do it > > in > > > > github. I'm afraid it will decrease signal to noise ratio in the > > list. > > > > > > > > On Thu, Jul 12, 2018 at 11:32 PM Lin Yuan > > wrote: > > > > > > > > > +1 > > > > > > > > > > On Thu, Jul 12, 2018 at 12:26 PM Anirudh Acharya < > > > anirudhk...@gmail.com> > > > > > wrote: > > > > > > > > > > > +1 > > > > > > > > > > > > On Thu, Jul 12, 2018 at 11:51 AM Piyush Ghai < > > ghai.piy...@gmail.com> > > > > > > wrote: > > > > > > > > > > > > > +1 > > > > > > > > On Jul 12, 2018, at 11:50 AM, Tianqi Chen < > > > > tqc...@cs.washington.edu> > > > > > > > wrote: > > > > > > > > > > > > > > > > +1 > > > > > > > > > > > > > > > > On Thu, Jul 12, 2018 at 11:10 AM, Sheng Zha < > > szha@gmail.com> > > > > > > wrote: > > > > > > > > > > > > > > > >> Hi all, > > > > > > > >> > > > > > > > >> Should we subscribe dev list to github updates on mxnet > > repo? > > > Both > > > > > > > github > > > > > > > >> issues/PRs and the dev list are intended for technical > > > discussions > > > > > and > > > > > > > in > > > > > > > >> that aspect largely share the same goal. Since MXNet has > > most > > > > > activity > > > > > > > >> github, this could help dev@ to become more active. > Some > > pros > > > and > > > > > > cons: > > > > > > > >> > > > > > > > >> Pros: > > > > > > > >> - There have been many high quality discussions that > > happen on > > > > > github > > > > > > to > > > > > > > >> which the dev list can benefit. > > > > > > > >> - Replies on update emails are reflected on the specific > > > issue/PR. > > > > > > > >> - Users can also choose to click on the link and go to > > github to > > > > > > > >> participate in discussion. > > > > > > > >> - We still have the ability to carry out dev@ only > > > conversation. > > > > > > > >> > > > > > > > >> Cons: > > > > > > > >> - Higher volume on dev list. > > > > > > > >> - Some discussions might not be suitable for dev@. > > (though I > > > > can't > > > > > > > think > > > > > > > >> of > > > > > > > >> why such conversation should happen on github either) > > > > > > > >> > > > > > > > >> -sz > > > > > > > >> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
Re: [DISCUSS] Subscribe dev@ to Github Activities?
Agree. +1 for more transparency On Thu, Jul 12, 2018 at 3:27 PM, Zha, Sheng wrote: > My intention is really just to bridge the gap between so much happening on > github v.s. "whatever didn't happen on dev list didn't happen". > > Also, since dev@ is intended to be an asynchronous way for community to > follow technical conversations, there wasn't really a requirement for > anyone to read all of them in the first place. > > Best regards, > -sz > > On 7/12/18, 3:20 PM, "Timur Shenkao" wrote: > > Flink - yes > Spark - it was previously but not now > > Yeah, amount of messages would be tripled at least: Jira + Github > issue + PR > > On Thu, Jul 12, 2018 at 11:13 PM, Haibin Lin > > wrote: > > > I'm a bit concerned with the amount of emails flooding in. In the > past week > > there're 32 new issues and 35 new pull requests. This means on avg > 10 email > > per day and I doubt I'll read all of them.. Does the Spark community > > subscribe dev@ to github? > > > > Best, > > Haibin > > > > On Thu, Jul 12, 2018 at 3:08 PM, Pedro Larroy < > > pedro.larroy.li...@gmail.com> > > wrote: > > > > > -1 It's a lot of traffic, whomever wants to subscribe can do it > in > > > github. I'm afraid it will decrease signal to noise ratio in the > list. > > > > > > On Thu, Jul 12, 2018 at 11:32 PM Lin Yuan > wrote: > > > > > > > +1 > > > > > > > > On Thu, Jul 12, 2018 at 12:26 PM Anirudh Acharya < > > anirudhk...@gmail.com> > > > > wrote: > > > > > > > > > +1 > > > > > > > > > > On Thu, Jul 12, 2018 at 11:51 AM Piyush Ghai < > ghai.piy...@gmail.com> > > > > > wrote: > > > > > > > > > > > +1 > > > > > > > On Jul 12, 2018, at 11:50 AM, Tianqi Chen < > > > tqc...@cs.washington.edu> > > > > > > wrote: > > > > > > > > > > > > > > +1 > > > > > > > > > > > > > > On Thu, Jul 12, 2018 at 11:10 AM, Sheng Zha < > szha@gmail.com> > > > > > wrote: > > > > > > > > > > > > > >> Hi all, > > > > > > >> > > > > > > >> Should we subscribe dev list to github updates on mxnet > repo? > > Both > > > > > > github > > > > > > >> issues/PRs and the dev list are intended for technical > > discussions > > > > and > > > > > > in > > > > > > >> that aspect largely share the same goal. Since MXNet has > most > > > > activity > > > > > > >> github, this could help dev@ to become more active. Some > pros > > and > > > > > cons: > > > > > > >> > > > > > > >> Pros: > > > > > > >> - There have been many high quality discussions that > happen on > > > > github > > > > > to > > > > > > >> which the dev list can benefit. > > > > > > >> - Replies on update emails are reflected on the specific > > issue/PR. > > > > > > >> - Users can also choose to click on the link and go to > github to > > > > > > >> participate in discussion. > > > > > > >> - We still have the ability to carry out dev@ only > > conversation. > > > > > > >> > > > > > > >> Cons: > > > > > > >> - Higher volume on dev list. > > > > > > >> - Some discussions might not be suitable for dev@. > (though I > > > can't > > > > > > think > > > > > > >> of > > > > > > >> why such conversation should happen on github either) > > > > > > >> > > > > > > >> -sz > > > > > > >> > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
Re: [DISCUSS] Subscribe dev@ to Github Activities?
My intention is really just to bridge the gap between so much happening on github v.s. "whatever didn't happen on dev list didn't happen". Also, since dev@ is intended to be an asynchronous way for community to follow technical conversations, there wasn't really a requirement for anyone to read all of them in the first place. Best regards, -sz On 7/12/18, 3:20 PM, "Timur Shenkao" wrote: Flink - yes Spark - it was previously but not now Yeah, amount of messages would be tripled at least: Jira + Github issue + PR On Thu, Jul 12, 2018 at 11:13 PM, Haibin Lin wrote: > I'm a bit concerned with the amount of emails flooding in. In the past week > there're 32 new issues and 35 new pull requests. This means on avg 10 email > per day and I doubt I'll read all of them.. Does the Spark community > subscribe dev@ to github? > > Best, > Haibin > > On Thu, Jul 12, 2018 at 3:08 PM, Pedro Larroy < > pedro.larroy.li...@gmail.com> > wrote: > > > -1 It's a lot of traffic, whomever wants to subscribe can do it in > > github. I'm afraid it will decrease signal to noise ratio in the list. > > > > On Thu, Jul 12, 2018 at 11:32 PM Lin Yuan wrote: > > > > > +1 > > > > > > On Thu, Jul 12, 2018 at 12:26 PM Anirudh Acharya < > anirudhk...@gmail.com> > > > wrote: > > > > > > > +1 > > > > > > > > On Thu, Jul 12, 2018 at 11:51 AM Piyush Ghai > > > > wrote: > > > > > > > > > +1 > > > > > > On Jul 12, 2018, at 11:50 AM, Tianqi Chen < > > tqc...@cs.washington.edu> > > > > > wrote: > > > > > > > > > > > > +1 > > > > > > > > > > > > On Thu, Jul 12, 2018 at 11:10 AM, Sheng Zha > > > > wrote: > > > > > > > > > > > >> Hi all, > > > > > >> > > > > > >> Should we subscribe dev list to github updates on mxnet repo? > Both > > > > > github > > > > > >> issues/PRs and the dev list are intended for technical > discussions > > > and > > > > > in > > > > > >> that aspect largely share the same goal. Since MXNet has most > > > activity > > > > > >> github, this could help dev@ to become more active. Some pros > and > > > > cons: > > > > > >> > > > > > >> Pros: > > > > > >> - There have been many high quality discussions that happen on > > > github > > > > to > > > > > >> which the dev list can benefit. > > > > > >> - Replies on update emails are reflected on the specific > issue/PR. > > > > > >> - Users can also choose to click on the link and go to github to > > > > > >> participate in discussion. > > > > > >> - We still have the ability to carry out dev@ only > conversation. > > > > > >> > > > > > >> Cons: > > > > > >> - Higher volume on dev list. > > > > > >> - Some discussions might not be suitable for dev@. (though I > > can't > > > > > think > > > > > >> of > > > > > >> why such conversation should happen on github either) > > > > > >> > > > > > >> -sz > > > > > >> > > > > > > > > > > > > > > > > > > > >
Re: [DISCUSS] Subscribe dev@ to Github Activities?
Flink - yes Spark - it was previously but not now Yeah, amount of messages would be tripled at least: Jira + Github issue + PR On Thu, Jul 12, 2018 at 11:13 PM, Haibin Lin wrote: > I'm a bit concerned with the amount of emails flooding in. In the past week > there're 32 new issues and 35 new pull requests. This means on avg 10 email > per day and I doubt I'll read all of them.. Does the Spark community > subscribe dev@ to github? > > Best, > Haibin > > On Thu, Jul 12, 2018 at 3:08 PM, Pedro Larroy < > pedro.larroy.li...@gmail.com> > wrote: > > > -1 It's a lot of traffic, whomever wants to subscribe can do it in > > github. I'm afraid it will decrease signal to noise ratio in the list. > > > > On Thu, Jul 12, 2018 at 11:32 PM Lin Yuan wrote: > > > > > +1 > > > > > > On Thu, Jul 12, 2018 at 12:26 PM Anirudh Acharya < > anirudhk...@gmail.com> > > > wrote: > > > > > > > +1 > > > > > > > > On Thu, Jul 12, 2018 at 11:51 AM Piyush Ghai > > > > wrote: > > > > > > > > > +1 > > > > > > On Jul 12, 2018, at 11:50 AM, Tianqi Chen < > > tqc...@cs.washington.edu> > > > > > wrote: > > > > > > > > > > > > +1 > > > > > > > > > > > > On Thu, Jul 12, 2018 at 11:10 AM, Sheng Zha > > > > wrote: > > > > > > > > > > > >> Hi all, > > > > > >> > > > > > >> Should we subscribe dev list to github updates on mxnet repo? > Both > > > > > github > > > > > >> issues/PRs and the dev list are intended for technical > discussions > > > and > > > > > in > > > > > >> that aspect largely share the same goal. Since MXNet has most > > > activity > > > > > >> github, this could help dev@ to become more active. Some pros > and > > > > cons: > > > > > >> > > > > > >> Pros: > > > > > >> - There have been many high quality discussions that happen on > > > github > > > > to > > > > > >> which the dev list can benefit. > > > > > >> - Replies on update emails are reflected on the specific > issue/PR. > > > > > >> - Users can also choose to click on the link and go to github to > > > > > >> participate in discussion. > > > > > >> - We still have the ability to carry out dev@ only > conversation. > > > > > >> > > > > > >> Cons: > > > > > >> - Higher volume on dev list. > > > > > >> - Some discussions might not be suitable for dev@. (though I > > can't > > > > > think > > > > > >> of > > > > > >> why such conversation should happen on github either) > > > > > >> > > > > > >> -sz > > > > > >> > > > > > > > > > > > > > > > > > > > >
Re: [DISCUSS] Subscribe dev@ to Github Activities?
I'm a bit concerned with the amount of emails flooding in. In the past week there're 32 new issues and 35 new pull requests. This means on avg 10 email per day and I doubt I'll read all of them.. Does the Spark community subscribe dev@ to github? Best, Haibin On Thu, Jul 12, 2018 at 3:08 PM, Pedro Larroy wrote: > -1 It's a lot of traffic, whomever wants to subscribe can do it in > github. I'm afraid it will decrease signal to noise ratio in the list. > > On Thu, Jul 12, 2018 at 11:32 PM Lin Yuan wrote: > > > +1 > > > > On Thu, Jul 12, 2018 at 12:26 PM Anirudh Acharya > > wrote: > > > > > +1 > > > > > > On Thu, Jul 12, 2018 at 11:51 AM Piyush Ghai > > > wrote: > > > > > > > +1 > > > > > On Jul 12, 2018, at 11:50 AM, Tianqi Chen < > tqc...@cs.washington.edu> > > > > wrote: > > > > > > > > > > +1 > > > > > > > > > > On Thu, Jul 12, 2018 at 11:10 AM, Sheng Zha > > > wrote: > > > > > > > > > >> Hi all, > > > > >> > > > > >> Should we subscribe dev list to github updates on mxnet repo? Both > > > > github > > > > >> issues/PRs and the dev list are intended for technical discussions > > and > > > > in > > > > >> that aspect largely share the same goal. Since MXNet has most > > activity > > > > >> github, this could help dev@ to become more active. Some pros and > > > cons: > > > > >> > > > > >> Pros: > > > > >> - There have been many high quality discussions that happen on > > github > > > to > > > > >> which the dev list can benefit. > > > > >> - Replies on update emails are reflected on the specific issue/PR. > > > > >> - Users can also choose to click on the link and go to github to > > > > >> participate in discussion. > > > > >> - We still have the ability to carry out dev@ only conversation. > > > > >> > > > > >> Cons: > > > > >> - Higher volume on dev list. > > > > >> - Some discussions might not be suitable for dev@. (though I > can't > > > > think > > > > >> of > > > > >> why such conversation should happen on github either) > > > > >> > > > > >> -sz > > > > >> > > > > > > > > > > > > > >
Re: [DISCUSS] Subscribe dev@ to Github Activities?
+0.5 Is there a @dev-apache option we can have? So we can decide whether to share the discussion on this mailing list. Thanks, Qing On 7/12/18, 3:08 PM, "Pedro Larroy" wrote: -1 It's a lot of traffic, whomever wants to subscribe can do it in github. I'm afraid it will decrease signal to noise ratio in the list. On Thu, Jul 12, 2018 at 11:32 PM Lin Yuan wrote: > +1 > > On Thu, Jul 12, 2018 at 12:26 PM Anirudh Acharya > wrote: > > > +1 > > > > On Thu, Jul 12, 2018 at 11:51 AM Piyush Ghai > > wrote: > > > > > +1 > > > > On Jul 12, 2018, at 11:50 AM, Tianqi Chen > > > wrote: > > > > > > > > +1 > > > > > > > > On Thu, Jul 12, 2018 at 11:10 AM, Sheng Zha > > wrote: > > > > > > > >> Hi all, > > > >> > > > >> Should we subscribe dev list to github updates on mxnet repo? Both > > > github > > > >> issues/PRs and the dev list are intended for technical discussions > and > > > in > > > >> that aspect largely share the same goal. Since MXNet has most > activity > > > >> github, this could help dev@ to become more active. Some pros and > > cons: > > > >> > > > >> Pros: > > > >> - There have been many high quality discussions that happen on > github > > to > > > >> which the dev list can benefit. > > > >> - Replies on update emails are reflected on the specific issue/PR. > > > >> - Users can also choose to click on the link and go to github to > > > >> participate in discussion. > > > >> - We still have the ability to carry out dev@ only conversation. > > > >> > > > >> Cons: > > > >> - Higher volume on dev list. > > > >> - Some discussions might not be suitable for dev@. (though I can't > > > think > > > >> of > > > >> why such conversation should happen on github either) > > > >> > > > >> -sz > > > >> > > > > > > > > >
Re: [DISCUSS] Subscribe dev@ to Github Activities?
-1 It's a lot of traffic, whomever wants to subscribe can do it in github. I'm afraid it will decrease signal to noise ratio in the list. On Thu, Jul 12, 2018 at 11:32 PM Lin Yuan wrote: > +1 > > On Thu, Jul 12, 2018 at 12:26 PM Anirudh Acharya > wrote: > > > +1 > > > > On Thu, Jul 12, 2018 at 11:51 AM Piyush Ghai > > wrote: > > > > > +1 > > > > On Jul 12, 2018, at 11:50 AM, Tianqi Chen > > > wrote: > > > > > > > > +1 > > > > > > > > On Thu, Jul 12, 2018 at 11:10 AM, Sheng Zha > > wrote: > > > > > > > >> Hi all, > > > >> > > > >> Should we subscribe dev list to github updates on mxnet repo? Both > > > github > > > >> issues/PRs and the dev list are intended for technical discussions > and > > > in > > > >> that aspect largely share the same goal. Since MXNet has most > activity > > > >> github, this could help dev@ to become more active. Some pros and > > cons: > > > >> > > > >> Pros: > > > >> - There have been many high quality discussions that happen on > github > > to > > > >> which the dev list can benefit. > > > >> - Replies on update emails are reflected on the specific issue/PR. > > > >> - Users can also choose to click on the link and go to github to > > > >> participate in discussion. > > > >> - We still have the ability to carry out dev@ only conversation. > > > >> > > > >> Cons: > > > >> - Higher volume on dev list. > > > >> - Some discussions might not be suitable for dev@. (though I can't > > > think > > > >> of > > > >> why such conversation should happen on github either) > > > >> > > > >> -sz > > > >> > > > > > > > > >
Re: [DISCUSS] Subscribe dev@ to Github Activities?
+1 On Thu, Jul 12, 2018 at 12:26 PM Anirudh Acharya wrote: > +1 > > On Thu, Jul 12, 2018 at 11:51 AM Piyush Ghai > wrote: > > > +1 > > > On Jul 12, 2018, at 11:50 AM, Tianqi Chen > > wrote: > > > > > > +1 > > > > > > On Thu, Jul 12, 2018 at 11:10 AM, Sheng Zha > wrote: > > > > > >> Hi all, > > >> > > >> Should we subscribe dev list to github updates on mxnet repo? Both > > github > > >> issues/PRs and the dev list are intended for technical discussions and > > in > > >> that aspect largely share the same goal. Since MXNet has most activity > > >> github, this could help dev@ to become more active. Some pros and > cons: > > >> > > >> Pros: > > >> - There have been many high quality discussions that happen on github > to > > >> which the dev list can benefit. > > >> - Replies on update emails are reflected on the specific issue/PR. > > >> - Users can also choose to click on the link and go to github to > > >> participate in discussion. > > >> - We still have the ability to carry out dev@ only conversation. > > >> > > >> Cons: > > >> - Higher volume on dev list. > > >> - Some discussions might not be suitable for dev@. (though I can't > > think > > >> of > > >> why such conversation should happen on github either) > > >> > > >> -sz > > >> > > > > >
Re: [DISCUSS] Subscribe dev@ to Github Activities?
+1 On Thu, Jul 12, 2018 at 11:51 AM Piyush Ghai wrote: > +1 > > On Jul 12, 2018, at 11:50 AM, Tianqi Chen > wrote: > > > > +1 > > > > On Thu, Jul 12, 2018 at 11:10 AM, Sheng Zha wrote: > > > >> Hi all, > >> > >> Should we subscribe dev list to github updates on mxnet repo? Both > github > >> issues/PRs and the dev list are intended for technical discussions and > in > >> that aspect largely share the same goal. Since MXNet has most activity > >> github, this could help dev@ to become more active. Some pros and cons: > >> > >> Pros: > >> - There have been many high quality discussions that happen on github to > >> which the dev list can benefit. > >> - Replies on update emails are reflected on the specific issue/PR. > >> - Users can also choose to click on the link and go to github to > >> participate in discussion. > >> - We still have the ability to carry out dev@ only conversation. > >> > >> Cons: > >> - Higher volume on dev list. > >> - Some discussions might not be suitable for dev@. (though I can't > think > >> of > >> why such conversation should happen on github either) > >> > >> -sz > >> > >
Re: [DISCUSS] Subscribe dev@ to Github Activities?
+1 > On Jul 12, 2018, at 11:50 AM, Tianqi Chen wrote: > > +1 > > On Thu, Jul 12, 2018 at 11:10 AM, Sheng Zha wrote: > >> Hi all, >> >> Should we subscribe dev list to github updates on mxnet repo? Both github >> issues/PRs and the dev list are intended for technical discussions and in >> that aspect largely share the same goal. Since MXNet has most activity >> github, this could help dev@ to become more active. Some pros and cons: >> >> Pros: >> - There have been many high quality discussions that happen on github to >> which the dev list can benefit. >> - Replies on update emails are reflected on the specific issue/PR. >> - Users can also choose to click on the link and go to github to >> participate in discussion. >> - We still have the ability to carry out dev@ only conversation. >> >> Cons: >> - Higher volume on dev list. >> - Some discussions might not be suitable for dev@. (though I can't think >> of >> why such conversation should happen on github either) >> >> -sz >>
Re: [DISCUSS] Subscribe dev@ to Github Activities?
+1 On Thu, Jul 12, 2018 at 11:10 AM, Sheng Zha wrote: > Hi all, > > Should we subscribe dev list to github updates on mxnet repo? Both github > issues/PRs and the dev list are intended for technical discussions and in > that aspect largely share the same goal. Since MXNet has most activity > github, this could help dev@ to become more active. Some pros and cons: > > Pros: > - There have been many high quality discussions that happen on github to > which the dev list can benefit. > - Replies on update emails are reflected on the specific issue/PR. > - Users can also choose to click on the link and go to github to > participate in discussion. > - We still have the ability to carry out dev@ only conversation. > > Cons: > - Higher volume on dev list. > - Some discussions might not be suitable for dev@. (though I can't think > of > why such conversation should happen on github either) > > -sz >
[DISCUSS] Subscribe dev@ to Github Activities?
Hi all, Should we subscribe dev list to github updates on mxnet repo? Both github issues/PRs and the dev list are intended for technical discussions and in that aspect largely share the same goal. Since MXNet has most activity github, this could help dev@ to become more active. Some pros and cons: Pros: - There have been many high quality discussions that happen on github to which the dev list can benefit. - Replies on update emails are reflected on the specific issue/PR. - Users can also choose to click on the link and go to github to participate in discussion. - We still have the ability to carry out dev@ only conversation. Cons: - Higher volume on dev list. - Some discussions might not be suitable for dev@. (though I can't think of why such conversation should happen on github either) -sz
