[
https://issues.apache.org/jira/browse/INCUBATOR-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17173724#comment-17173724
]
Sheng Zha edited comment on INCUBATOR-253 at 8/9/20, 2:09 AM:
--------------------------------------------------------------
h3. Summary
The PPMC continues to make progress in resolving license and branding issues.
During the a recent release vote on 1.7.0, with the help from Justin, a few
more source distribution and branding issues were found. Here is the status on
the issues, tracked in INCUBATOR-253. As of now, the PPMC *resolved 12 issues,
with 11 still left*.
Most of the outstanding issues hinge on one key outstanding question, which is
whether the components in MXNet that are produced by CUDA NVCC constitutes
Category X code. PPMC member employed by Nvidia helped connect Nvidia's
representatives including Michael O'Connor, Director of Deep Learning, who have
been supportive in the efforts of clarification. Progress is tracked in
LEGAL-516. Also note that there was confusion around MXNet's status around
integration with Intel products. In MXNet, there has never been public
distribution of MXNet where MKL was included. There was an initial inquiry
around whether MKL builds can be enabled but was rejected, so this never came
into practice. Also, to my knowledge Intel has not produced custom MXNet builds
with closed-source components.
MXNet 1.7.0 release vote was put on hold for addressing the branding issues in
third-party releases and for an IP clearance process.
So far, PPMC members from Intel (*Tao*), Nvidia (*Dick*), and Amazon
(*Leonard*, *Henri*, *Qing*, *Sheng*) have acted to help resolve the issues.
h3. Status
1. Source and convenance binary releases containing Category X licensed code.
(pending)
- Source code releases by the PPMC do not contain Category X code, no issue.
- Takedown of binary releases by the PPMC on repository.apache.org is on hold,
see item 5.
- PyPI releases are made by third-party. See item 8.
2. Website giving access to downloads of non released/unapproved code.
(resolved)
- Website contained links to nightly development builds which have been
removed [5];
3. Website giving access to releases containing Category X licensed code.
(resolved)
- Website contained links to third-party distributions. Disclaimers were added
to the website clarifying the third-party status of the releases and their
licenses. [5]
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. (resolved)
- Website contained links to third-party distributions. Disclaimers were added
to the website clarifying the third-party status of the releases and their
licenses. [5]
5. Maven releases containing Category X licensed code. (pending)
- Takedown of binary releases on repository.apache.org initiated [6]. The
scope depends on the resolution of LEGAL-516.
6. PyPI releases containing Category X licensed code. (pending)
- There are no PyPI releases by the PPMC. Whether the third-party releases are
compliant with branding guidelines depend on the resolution of LEGAL-516.
7. Docker releases containing Category X licensed code. (pending)
- There are no Docker releases by the PPMC. Whether the third-party releases
are compliant with branding guidelines depend on the resolution of LEGAL-516.
8. Docker releases containing unreleased/unapproved code. (resolved)
- There are no Docker releases by the PPMC. The PPMC verified the third-party
releases that all are based on unmodified commits in MXNet, which is approved
from brand management [3].
9. Trademark and branding issues with PyPI and Docker releases. (pending)
- There are no PyPI or Docker releases by the PPMC. In addition, as they all
contain binary from unmodified MXNet code, whether they are compliant in
branding now solely depends on whether they contain Category X licensed code.
Refer to item 6, 7, 8.
10. Trademark and brand issues with naming of releases. (pending)
- There are no binary releases by the PPMC besides the repository.apache.org
releases in item 5.
11. Developer releases available to users and public searchable
[https://repo.mxnet.io|https://repo.mxnet.io/] /
[https://dist.mxnet.io|https://dist.mxnet.io/] (resolved)
- Links to the nightly development builds were removed from the MXNet website
and a robot.txt file was added to prevent indexing of the sites. These websites
are removed from Google search index.
12. Releases and other nightly builds on
[https://repo.mxnet.io|https://repo.mxnet.io/] /
[https://dist.mxnet.io|https://dist.mxnet.io/] containing Category X licensed
code (pending)
- Neither of the two site contains releases. Whether the binaries there
contain Category X components depends on the resolution of LEGAL-516.
13. Lack of clarity on all platforms for what is an ASF release and what is
not. (resolved)
- [https://github.com/apache/incubator-mxnet/releases?after=1.2.0] previously
did not distinguish MXNet releases prior to MXNet joining the Incubator.
Disclaimers were added. Other PPMC platforms do not contain references to
non-ASF releases (MXNet releases made prior to MXNet joining the ASF). The PPMC
is aware of old third-party releases created prior to MXNet joining the ASF
which are still available, but can be clearly separated from the ASF MXNet
releases due to the lack of reference to the Apache foundation. PPMC was able
to find an exemplar such release at [7]. If there are concerns from the
Incubator, PPMC can request the third-parties to take down these releases, as
editing their Description to include references to events (MXNet joining
Apache) is not supported due to immutability constraints. [8]
14. to 23. Branding and release of 3rd parties containing unreleased code.
(pending)
Known pages with issues:
-
[https://docs.nvidia.com/deeplearning/frameworks/mxnet-release-notes/rel_20-03.html]
(item 14, pending)
- PPMC reached out to Nvidia. Pending action from Nvidia on branding
compliance and replying on whether unreleased code was included.
- [https://sourceforge.net/projects/apache-mxnet.mirror/] (item 15, pending)
- PPMC reached out to SourceForge. SourceForge added (incubating) in name.
- The mirror is automatic, which happens to contain MXNet release candidate in
voting which is an artifact of MXNet's release process [9]
- PPMC granted SourceForge's request for more time for engineering to filter
out non-release tags. In any case, after completion of release process, the RC
will be automatically removed.
- DJL related links.
- The following constitutes nominative use of MXNet and is approved by brand
management committee [10]:
-
[https://repo.gradle.org/gradle/simple/repo/ai/djl/mxnet/mxnet-native-mkl/1.7.0-b/]
(item 16, resolved)
- [https://mvnrepository.com/artifact/ai.djl.mxnet] (item 17, resolved)
-
[https://aur.archlinux.org/packages/?O=0&SeB=nd&K=mxnet&SB=v&SO=d&PP=50&do_Search=Go]
(item 18, resolved)
- [https://djl.ai|https://djl.ai/] (item 19, resolved)
- the DJL project have updated their language with regards to Apache MXNet [11]
- AWS Marketplace related links
- [https://aws.amazon.com/marketplace/pp/NVIDIA-MXNet-by-NVIDIA/B07KLFW54D]
(item 20, resolved)
- Per request from PPMC, NVIDIA removed this listing.
-
[https://aws.amazon.com/marketplace/pp/prodview-yex2xx5kgdhea?qid=1595741035764&sr=0-1&ref_=srh_res_product_title]
(item 21, resolved)
- Per request from PPMC, Intel removed this listing.
-
[https://aws.amazon.com/marketplace/pp/B07YW8HVLD?qid=1595741035764&sr=0-4&ref_=srh_res_product_title]
(item 22, pending)
- PPMC reached out to AWS through internal channel to fix branding issue with
Bitnami
-
[https://aws.amazon.com/marketplace/search/results?x=0&y=0&searchTerms=%22MXNet]
(item 23, pending)
- PPMC reached out to AWS through internal channel to fix branding issue.
h3. Reference links
[1]: https://issues.apache.org/jira/browse/LEGAL-515
[2]: https://issues.apache.org/jira/browse/LEGAL-516
[3]: [https://s.apache.org/flvug]
[4]: [http://www.apache.org/legal/release-policy.html#publication]
[5]:
[https://github.com/apache/incubator-mxnet/commit/b6b40878f0aba2ba5509f3f3a4cd517a654847ce#diff-19bc831c1dab6d92d2efc3b87ec5c740]
[6]: https://issues.apache.org/jira/browse/INFRA-20442
[7]: [https://pypi.org/project/mxnet/0.9.5/]
[8]:
[https://mail.python.org/pipermail/distutils-sig/2017-December/031826.html]
[9]: [https://cwiki.apache.org/confluence/display/MXNET/Release+Process]
[10]:
[https://lists.apache.org/thread.html/r3171eadc746ae1690c298a852321a7977a9bf98d651cf426f07af990%40%3Cgeneral.incubator.apache.org%3E]
[11]:
https://issues.apache.org/jira/browse/INCUBATOR-253?focusedCommentId=17172716&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17172716
was (Author: zhasheng):
h3. Summary
The PPMC continues to make progress in resolving license and branding issues.
During the a recent release vote on 1.7.0, with the help from Justin, a few
more source distribution and branding issues were found. Here is the status on
the issues, tracked in INCUBATOR-253. As of now, the PPMC *resolved 12 issues,
with 11 still left*.
Most of the outstanding issues hinge on one key outstanding question, which is
whether the components in MXNet that are produced by CUDA NVCC constitutes
Category X code. PPMC member employed by Nvidia helped connect Nvidia's
representatives including Michael O'Connor, Director of Deep Learning, who have
been supportive in the efforts of clarification. Progress is tracked in
LEGAL-516.
MXNet 1.7.0 release vote was put on hold for addressing the branding issues in
third-party releases and for an IP clearance process.
So far, PPMC members from Intel (*Tao*), Nvidia (*Dick*), and Amazon
(*Leonard*, *Henri*, *Qing*, *Sheng*) have acted to help resolve the issues.
h3. Status
1. Source and convenance binary releases containing Category X licensed code.
(pending)
- Source code releases by the PPMC do not contain Category X code, no issue.
- Takedown of binary releases by the PPMC on repository.apache.org is on hold,
see item 5.
- PyPI releases are made by third-party. See item 8.
2. Website giving access to downloads of non released/unapproved code.
(resolved)
- Website contained links to nightly development builds which have been
removed [5];
3. Website giving access to releases containing Category X licensed code.
(resolved)
- Website contained links to third-party distributions. Disclaimers were added
to the website clarifying the third-party status of the releases and their
licenses. [5]
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. (resolved)
- Website contained links to third-party distributions. Disclaimers were added
to the website clarifying the third-party status of the releases and their
licenses. [5]
5. Maven releases containing Category X licensed code. (pending)
- Takedown of binary releases on repository.apache.org initiated [6]. The
scope depends on the resolution of LEGAL-516.
6. PyPI releases containing Category X licensed code. (pending)
- There are no PyPI releases by the PPMC. Whether the third-party releases are
compliant with branding guidelines depend on the resolution of LEGAL-516.
7. Docker releases containing Category X licensed code. (pending)
- There are no Docker releases by the PPMC. Whether the third-party releases
are compliant with branding guidelines depend on the resolution of LEGAL-516.
8. Docker releases containing unreleased/unapproved code. (resolved)
- There are no Docker releases by the PPMC. The PPMC verified the third-party
releases that all are based on unmodified commits in MXNet, which is approved
from brand management [3].
9. Trademark and branding issues with PyPI and Docker releases. (pending)
- There are no PyPI or Docker releases by the PPMC. In addition, as they all
contain binary from unmodified MXNet code, whether they are compliant in
branding now solely depends on whether they contain Category X licensed code.
Refer to item 6, 7, 8.
10. Trademark and brand issues with naming of releases. (pending)
- There are no binary releases by the PPMC besides the repository.apache.org
releases in item 5.
11. Developer releases available to users and public searchable
[https://repo.mxnet.io|https://repo.mxnet.io/] /
[https://dist.mxnet.io|https://dist.mxnet.io/] (resolved)
- Links to the nightly development builds were removed from the MXNet website
and a robot.txt file was added to prevent indexing of the sites. These websites
are removed from Google search index.
12. Releases and other nightly builds on
[https://repo.mxnet.io|https://repo.mxnet.io/] /
[https://dist.mxnet.io|https://dist.mxnet.io/] containing Category X licensed
code (pending)
- Neither of the two site contains releases. Whether the binaries there
contain Category X components depends on the resolution of LEGAL-516.
13. Lack of clarity on all platforms for what is an ASF release and what is
not. (resolved)
- [https://github.com/apache/incubator-mxnet/releases?after=1.2.0] previously
did not distinguish MXNet releases prior to MXNet joining the Incubator.
Disclaimers were added. Other PPMC platforms do not contain references to
non-ASF releases (MXNet releases made prior to MXNet joining the ASF). The PPMC
is aware of old third-party releases created prior to MXNet joining the ASF
which are still available, but can be clearly separated from the ASF MXNet
releases due to the lack of reference to the Apache foundation. PPMC was able
to find an exemplar such release at [7]. If there are concerns from the
Incubator, PPMC can request the third-parties to take down these releases, as
editing their Description to include references to events (MXNet joining
Apache) is not supported due to immutability constraints. [8]
14. to 23. Branding and release of 3rd parties containing unreleased code.
(pending)
Known pages with issues:
-
[https://docs.nvidia.com/deeplearning/frameworks/mxnet-release-notes/rel_20-03.html]
(item 14, pending)
- PPMC reached out to Nvidia. Pending action from Nvidia on branding
compliance and replying on whether unreleased code was included.
- [https://sourceforge.net/projects/apache-mxnet.mirror/] (item 15, pending)
- PPMC reached out to SourceForge. SourceForge added (incubating) in name.
- The mirror is automatic, which happens to contain MXNet release candidate in
voting which is an artifact of MXNet's release process [9]
- PPMC granted SourceForge's request for more time for engineering to filter
out non-release tags. In any case, after completion of release process, the RC
will be automatically removed.
- DJL related links.
- The following constitutes nominative use of MXNet and is approved by brand
management committee [10]:
-
[https://repo.gradle.org/gradle/simple/repo/ai/djl/mxnet/mxnet-native-mkl/1.7.0-b/]
(item 16, resolved)
- [https://mvnrepository.com/artifact/ai.djl.mxnet] (item 17, resolved)
-
[https://aur.archlinux.org/packages/?O=0&SeB=nd&K=mxnet&SB=v&SO=d&PP=50&do_Search=Go]
(item 18, resolved)
- [https://djl.ai|https://djl.ai/] (item 19, resolved)
- the DJL project have updated their language with regards to Apache MXNet [11]
- AWS Marketplace related links
- [https://aws.amazon.com/marketplace/pp/NVIDIA-MXNet-by-NVIDIA/B07KLFW54D]
(item 20, resolved)
- Per request from PPMC, NVIDIA removed this listing.
-
[https://aws.amazon.com/marketplace/pp/prodview-yex2xx5kgdhea?qid=1595741035764&sr=0-1&ref_=srh_res_product_title]
(item 21, resolved)
- Per request from PPMC, Intel removed this listing.
-
[https://aws.amazon.com/marketplace/pp/B07YW8HVLD?qid=1595741035764&sr=0-4&ref_=srh_res_product_title]
(item 22, pending)
- PPMC reached out to AWS through internal channel to fix branding issue with
Bitnami
-
[https://aws.amazon.com/marketplace/search/results?x=0&y=0&searchTerms=%22MXNet]
(item 23, pending)
- PPMC reached out to AWS through internal channel to fix branding issue.
h3. Reference links
[1]: https://issues.apache.org/jira/browse/LEGAL-515
[2]: https://issues.apache.org/jira/browse/LEGAL-516
[3]: [https://s.apache.org/flvug]
[4]: [http://www.apache.org/legal/release-policy.html#publication]
[5]:
[https://github.com/apache/incubator-mxnet/commit/b6b40878f0aba2ba5509f3f3a4cd517a654847ce#diff-19bc831c1dab6d92d2efc3b87ec5c740]
[6]: https://issues.apache.org/jira/browse/INFRA-20442
[7]: [https://pypi.org/project/mxnet/0.9.5/]
[8]:
[https://mail.python.org/pipermail/distutils-sig/2017-December/031826.html]
[9]: [https://cwiki.apache.org/confluence/display/MXNET/Release+Process]
[10]:
[https://lists.apache.org/thread.html/r3171eadc746ae1690c298a852321a7977a9bf98d651cf426f07af990%40%3Cgeneral.incubator.apache.org%3E]
[11]:
https://issues.apache.org/jira/browse/INCUBATOR-253?focusedCommentId=17172716&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17172716
> 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
