mxnet-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Henri Yandell <>
Subject Ready to move the source code over to Apache?
Date Tue, 21 Feb 2017 07:43:14 GMT
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 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, they
will then do the transfer to, 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:

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
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

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)?


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