[
https://issues.apache.org/jira/browse/INCUBATOR-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17148108#comment-17148108
]
Sheng Zha commented on INCUBATOR-253:
-------------------------------------
Here's an update on the progress so far. See live version in
https://github.com/apache/incubator-mxnet/issues/18397
Per
https://lists.apache.org/thread.html/r738c102492649c754f49e2195985bc765df07df3c8a1e06942e8872f%40%3Cdev.mxnet.apache.org%3E,
there are several licensing issues that we need to address and below are the
issues as well as action items in each area.
## Developer pre-releases
This section tracks the problems that are related to nightly builds and
developer-only pre-releases. The related issues are:
- Developer releases available to users and public searchable
https://repo.mxnet.io / https://dist.mxnet.io
- The repo.mxnet.io and dist.mxnet.io weren't clear that the binaries there are
for developer testing only and not for public consumption.
**Actions**
- [x] Add disclaimer to repo.mxnet.io and dist.mxnet.io to clarify that the
nightly releases there are not intended for public consumption. (**done**)
- [x] Remove non-Apache releases in github release page.
(**done**)(https://github.com/apache/incubator-mxnet/releases)
- [x] Remove repo.mxnet.io and dist.mxnet.io from search engine index
(**done**)(https://github.com/apache/incubator-mxnet/issues/18397#issuecomment-647075093)
## First-party release
This section tracks the problems that are related to official releases that are
intended to be Apache License v2 compliant. The related issues are:
- convenance binary releases containing Category X licensed code
- Maven releases containing Category X licensed code.
- PiPy releases containing Category X licensed code.
- Docker releases containing Category X licensed code.
- Trademark and branding issues with PiPy and Docker releases.
**Actions**
- [ ] Delete problematic Maven releases. (**Waiting for action from Apache
infra**)
([thread](https://lists.apache.org/thread.html/ra4e9572ac74857a80c64a31e8bf292d353e74cfa87bf457f47450303%40%3Cdev.mxnet.apache.org%3E),
[INFRA-20442](https://issues.apache.org/jira/browse/INFRA-20442))
- [ ] Delete problematic pypi releases.
- [ ] Delete problematic docker releases.
## Third-party release
This section tracks the problems that are related to convenience binary
releases that cannot be Apache License v2 compliant. The related issues are:
- Lack of clarity on all platforms for what is an ASF release and what is not.
- Developer releases available to users and public searchable
https://repo.mxnet.io / https://dist.mxnet.io
- Trademark and branding issues with PiPy and Docker releases.
- NVIDIA's build of MXNet contains unreleased code:
https://docs.nvidia.com/deeplearning/frameworks/mxnet-release-notes/rel_20-03.html
- AWS Deep Learning Container build of MXNet contains unreleased code:
https://github.com/aws/deep-learning-containers/blob/master/mxnet/training/docker/1.6.0/py3/Dockerfile.gpu#L10
**Actions**
- [ ] Review with Apache Trademark on the current third-party binary
distributions of mxnet and make necessary correction. (**In progress**)
- [ ] Review with Apache Legal on the appropriate license for convenience
binary distribution and display it prominently. (**in
progress**)([LEGAL-515](https://issues.apache.org/jira/browse/LEGAL-515))
- [ ] Resolve NVIDIA trademark usage issue for MXNet (**in progress**, engaged
NVIDIA in [LEGAL-516](https://issues.apache.org/jira/browse/LEGAL-516))
- [ ] Resolve Amazon trademark usage issue for MXNet (**in progress**)
- [ ] Replacement Maven binary release as third-party release.
- [ ] Replacement pypi binary releases as third-party release.
## Documentation
This section tracks the problems that are related to documentation for releases
and pre-releases. The related issues are:
- Website giving access to downloads of non released/unapproved code.
- Website giving access to releases containing Category X licensed code.
- Web site doesn't given enough warning to users of the issues with non (P)PMC
releases or making it clear that these are not ASF releases.
- Lack of clarity on all platforms for what is an ASF release and what is not.
**Actions**
- [ ] create separate Apache and non-Apache release sections in downloads page.
- [x] add disclaimer for non-Apache releases in installation selector (**done**)
- [x] remove mentions of nightly builds in pypi page in wheel build pipeline
(**done**, update will happen with next release)
## Longer-term
This section tracks items that are for the purpose of mitigating usability
impact as a result of addressing the issues above.
**Actions**
- [ ] Add source distribution to PyPI package `apache-mxnet` and build
automatically on user machines.
Related:
#18463
https://issues.apache.org/jira/browse/INCUBATOR-253
> Issues with MXNet releases and their distribution
> -------------------------------------------------
>
> Key: INCUBATOR-253
> URL: https://issues.apache.org/jira/browse/INCUBATOR-253
> Project: Incubator
> Issue Type: Improvement
> Reporter: Justin Mclean
> Assignee: Justin Mclean
> Priority: Major
>
> The main issues are:
> 1. Source and convenance binary releases containing Category X licensed code.
> 2. Website giving access to downloads of non released/unapproved code.
> 3. Website giving access to releases containing Category X licensed code.
> 4. Web site doesn't given enough warning to users of the issues with non
> (P)PMC releases or making it clear that these are not ASF releases.
> 5. Maven releases containing Category X licensed code.
> 6. PiPy releases containing Category X licensed code.
> 7. Docker releases containing Category X licensed code.
> 8 Docker releases containing unreleased/unapproved code.
> 9. Trademark and branding issues with PiPy and Docker releases.
> 10. Trademark and brand issues with naming of releases.
> 11. Developer releases available to users and public searchable
> https://repo.mxnet.io / https://dist.mxnet.io
> 12. Releases and other nightly builds on https://repo.mxnet.io /
> https://dist.mxnet.io containing category X licensed code.
> 13. Lack of clarity on all platforms for what is an ASF release and what is
> not.
> 14. Branding and release of 3rd parties containing unreleased code. (e.g.
> https://docs.nvidia.com/deeplearning/frameworks/mxnet-release-notes/rel_20-03.html)
> For PiPy see:
> https://pypi.org/project/mxnet/
> For Docker see:
> https://hub.docker.com/u/mxnet
> For web site pages see:
> https://mxnet.apache.org/get_started?
> https://mxnet.apache.org/get_started/download
> I may of missed something, if so please add it.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
