Goal of the project is to migration user and developer community from https://github.com/dmlc/mxnet and http://mxnet.io/ to ASF.

Action items

Before repo migration:

  • Add committers to apache mxnet ldap, connect Apache account to GitHub account
  • Migrate Jenkins server - Updates on https://github.com/dmlc/mxnet/projects/6
    • Add Pono as owner
    • Pono adds Apache git hooks to MXNet repo
    • Change source control of Apache Jenkins jobs to point to MXNet repo, verify merges & pr builds are successful
  • Migrate git repo - apache/incubator-mxnet instead of dmlc/mxnet

After repo migration:

  • Migrate http://mxnet.io/ website
    • Phase 1: Manually build mxnet.incubator.apache.org with v0.10 and master docs into separate repo under Apache. master docs redirect to mxnet.io
      • Completion of phase 1 means we can start an RC.
    • Phase 2: Build automated versioned docs on mxnet.incubator.apache.org



  1. How do I gain write access to the repo?

    1. First, you need to be a committer. 

    2. Then use https://gitbox.apache.org/setup/ to associate the Apache and GitHub accounts. Note that all committers will need to enable 2-factor authentication on GitHub.

      Note: You will lose access to the repo if you don't do the above.

  2. Why are we migrating the code base to Apache ownership?

    1. This is one of the steps on graduating from Apache incubation.

  3. When is this happening?

    1. We are aiming for migration to complete by July 10th.

  4. Will my commits/contributions still exist after migration?

    1. Yes. Existing commits will still appear under your existing github id, and stats will carry over. New commits will also appear under your existing github id, so long as you’ve configured your ~/.gitconfig with an email address which you’ve linked in your github profile.

    2. Committers will also need to link their Apache ids with the github ids to gain write access, in which case, the above answer still applies. See #9 on how to link your Apache id.

  5. What will happen to my in flight pull requests?

    1. It will remain intact

  6. Will I still be a member/owner after migration?

    1. Current list of Apache MXNet committers: https://wiki.apache.org/incubator/MXNetProposal

    2. If you’re not an Apache committer, you lose membership/ownership rights

    3. Apache Infra are the only people with Owner/Admin permissions there

    4. Apache committers will have write access

  7. What other things will be transferred with the repository?

    1. Wiki, stars, watchers, webhooks, services, deploy keys

  8. What will my fork be associated with after migration?

    1. It will remain associated with the transferred repository

  9. Will I have to change all references to http://github.com/dmlc/mxnet ?

    1. All links to http://github.com/dmlc/mxnet will automatically be redirected to new location when issuing `git clone`, `git fetch`, `git push`, etc, (as long as we don’t create another “mxnet” repository under DMLC). However, to avoid confusion, you can change the links where possible, and change remote: `git remote set-url origin new_url`

  10. Are we also moving mxnet CI? If so, what is the new location? Will nightly tests continue to run? How can I add new tests?

    1. We will rely on Apache’s build server to run our builds.

    2. It will first only run unit tests for PRs and merges. Tests can be added following the structure setup in https://github.com/dmlc/mxnet/blob/master/Jenkinsfile .

    3. Nightly tests are currently running at http://jenkins-master-elb-1979848568.us-east-1.elb.amazonaws.com/ and will gradually run in Apache’s build server too. There, we will provide artifacts such as pip wheels and source packages for the community to test.

      1. Automated releases will happen on http://jenkins-master-elb-1979848568.us-east-1.elb.amazonaws.com/ as Apache’s build doesn’t support key storage.

  11. Is mxnet.io moving too?

    1. For some time we will have both mxnet.apache.org and mxnet.io hosting the docs. When we are confident that mxnet.apache.org is stable, we will redirect mxnet.io to there.


Link on GitHub repo transfers:





  • No labels