You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mxnet.apache.org by Henri Yandell <fl...@gmail.com> on 2017/03/02 07:25:16 UTC

Re: Ready to move the source code over to Apache?

Thanks Chiyuan.

I've sent an email connecting one of the Apache Infra members with them,
asking them to coordinate the GitHub repository move.

Hen

On Tue, Feb 21, 2017 at 10:21 AM, Chiyuan Zhang <pl...@gmail.com> wrote:

> I believe at least Mu, Tianqi and Eric all have owner permission on the
> dmlc org on github.
>
>
> On Tue, Feb 21, 2017 at 2:43 AM, Henri Yandell <ba...@apache.org> wrote:
>
> > Apologies for slowness on my part (busy home/work time of year).
> >
> > We have 23 committers with ICLAs/accounts.
> >
> > Currently we only have 4 people on the PPMC (per
> > https://whimsy.apache.org/roster/ppmc/mxnet). 14 are subscribed to the
> > private list, so that suggests there is something else that needs
> changing.
> > Will get that fixed (I've mailed general@incubator asking for assistance
> > in
> > how to fix).
> >
> > The next step is to move the source code to Apache. The change involves
> > giving an Apache Infra member Owner permissions on github.com/dmlc, they
> > will then do the transfer to github.com/apache, and then a name change
> of
> > mxnet to apache-mxnet. Everything else should 'just work'. We'll then
> need
> > to do some cleanup on licensing.
> >
> > The main change I then see happening is that releases need to follow the
> > Apache  rules. Releasing the Apache way is one of the primary items for a
> > community to learn about while in Incubation. This document talks more
> > about it: http://incubator.apache.org/guides/releasemanagement.html
> >
> > I would high-level summarize it as:
> >
> > 1) Must make a decision to release on the lists (i.e. a vote); and
> > subsequently have the Incubator PMC approve on general@incubator
> (another
> > vote).
> > 2) Must be in source form, and obey Apache policies (for example third
> > party library licensing).
> > 3) Additional Incubator items around flagging to users that mxnet is in
> the
> > Incubator.
> >
> > The biggest blocker, I believe, will be the zeromq licensing. There is
> > acceptance to do releases with issues while in the Incubator, so that's
> > something to raise on general@incubator.
> >
> > Who on the DMLC side should I put in contact with Apache Infrastructure
> to
> > plan the source migration (i.e. who has Owner permissions on DMLC and can
> > work with them)?
> >
> > Hen
> >
>