incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sheng Zha (Jira)" <j...@apache.org>
Subject [jira] [Commented] (INCUBATOR-253) Issues with MXNet releases and their distribution
Date Sun, 13 Sep 2020 21:15:00 GMT

    [ https://issues.apache.org/jira/browse/INCUBATOR-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17195126#comment-17195126
] 

Sheng Zha commented on INCUBATOR-253:
-------------------------------------

Summary (WIP)

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 15 issues, with 9 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.

Status on open issues from last update:
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.

5. Maven releases containing Category X licensed code. (pending)
 * Takedown of binary releases on repository.apache.org initiated [1]. The scope depends on
the resolution of LEGAL-516 [2].

6. PyPI releases containing Category X licensed code. (pending)
 * There are no official PyPI releases. 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 official Docker releases. Whether the third-party releases are compliant with
branding guidelines depend on the resolution of LEGAL-516.

9. Trademark and branding issues with PyPI and Docker releases. (pending)
 * There are no official PyPI or Docker releases. 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.

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.

12. Releases and other nightly builds on https://repo.mxnet.io / https://dist.mxnet.io containing
Category X licensed code (resolved)
 * Neither of the two site contains releases. The binaries are only intended for testing pipelines
and are made available only to MXNet developers. As part of the effort to resolve branding
concern, public references to these sites are deleted [4].

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, resolved)
 * PPMC reached out to SourceForge. SourceForge added (incubating) in name. As 1.7.0 release
has completed, we removed release candidate tag from GitHub and the the mirror automatically
deleted the it [3]. As such, the original issue is resolved. The PPMC will follow up with
SourceForge on the functionality of filtering out non-release tags.

AWS Marketplace related links
https://aws.amazon.com/marketplace/pp/B07YW8HVLD?qid=1595741035764&sr=0-4&ref_=srh_res_product_title
(item 22, pending)
 * PPMC reached out to Bitnami directly regarding this listing [5]. Pending reply.

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. Will update in
the next few days.

Reference links
[1]: https://issues.apache.org/jira/browse/INFRA-20442
[2]: https://issues.apache.org/jira/browse/LEGAL-516
[3]: https://sourceforge.net/projects/apache-mxnet.mirror/
[4]: https://issues.apache.org/jira/browse/LEGAL-515?focusedCommentId=17174133&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17174133
[5]: https://lists.apache.org/thread.html/r1fabd3c081286b06b6e9c9283cb5986450f07d52309db3b74bfe3a24%40%3Cprivate.mxnet.apache.org%3E

> 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-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Mime
View raw message