mxnet-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Timur Shenkao <...@timshenkao.su>
Subject Re: [DISCUSS] Subscribe dev@ to Github Activities?
Date Thu, 12 Jul 2018 22:20:44 GMT
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.aws@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.lists@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 <apeforest@gmail.com> wrote:
> >
> > > +1
> > >
> > > On Thu, Jul 12, 2018 at 12:26 PM Anirudh Acharya <
> anirudhkrec@gmail.com>
> > > wrote:
> > >
> > > > +1
> > > >
> > > > On Thu, Jul 12, 2018 at 11:51 AM Piyush Ghai <ghai.piyush@gmail.com>
> > > > wrote:
> > > >
> > > > > +1
> > > > > > On Jul 12, 2018, at 11:50 AM, Tianqi Chen <
> > tqchen@cs.washington.edu>
> > > > > wrote:
> > > > > >
> > > > > > +1
> > > > > >
> > > > > > On Thu, Jul 12, 2018 at 11:10 AM, Sheng Zha <szha.pvg@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
> > > > > >>
> > > > >
> > > > >
> > > >
> > >
> >
>

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