'[jira] [Commented] (INCUBATOR-253) Issues with MXNet releases and their distribution'

[prev in list] [next in list] [prev in thread] [next in thread] 

List:       incubator-general
Subject:    [jira] [Commented] (INCUBATOR-253) Issues with MXNet releases and their distribution
From:       "Sheng Zha (Jira)" <jira () apache ! org>
Date:       2021-01-05 19:37:02
Message-ID: JIRA.13312094.1592447319000.408740.1609875422959 () Atlassian ! JIRA
[Download RAW message or body]


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

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

*Summary*
Most of the issues from last update hinged on the resolution of LEGAL-516. We are \
very glad that LEGAL-516 concluded that ASF projects compiled using NVIDIA's CUDA \
compiler may be distributed under the Apache License 2.0, which unblocks many of the \
distribution practices that are essential to the wide adoption of software that \
utilizes GPU. We would like to thank for the help, the patience, and the leniency and \
flexibility that the incubator and legal granted us, and the numerous helps we \
received along the way from the ASF members and our community members from NVIDIA. \
Especially, I would like to thank Michael O'Conner and Triston Cao from NVIDIA for \
pushing this through within their organization.  
Based on the conclusion of LEGAL-516, binary distribution of CUDA-compiled Apache \
projects can be properly licensed as ALv2. In addition, the branding issues from \
distribution pages from Amazon, NVIDIA, and Intel have all been acted on. As a \
result, among the 9 pending issues from last update, 5 can be resolved. We are \
following up on the remaining items to resolve all issues in INCUBATOR-253.  
As part of our improvement in brand management, we are including third-party brand \
usage review in our quarterly reports and we will keep it as part of our regular \
practice beyond graduation.  
*Status on open issues since last update:*
1. Source and convenance binary releases containing Category X licensed code. \
(pending item 5) * Source code releases by the PPMC do not contain Category X \
code.  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 (i.e. INFRA-20442). Based on the \
resolution of LEGAL-516, the takedown (and backfill) includes those that include GPL \
licensed components. We are working on this in the infra issue.

6. PyPI releases containing Category X licensed code. (Resolved) * The third-party \
releases are compliant with branding guidelines since the releases are from official \
source code releases and are properly licensed with ALv2.

7. Docker releases containing Category X licensed code. (Resolved) * Tthe third-party \
releases are compliant with branding guidelines  since the releases are  from \
official source code releases and are  properly licensed with ALv2.

9. Trademark and branding issues with PyPI and Docker releases. (Resolved) * These \
release are compliant with trademark and branding requirements since they don't \
contain Category X licensed code and are licensed with ALv2 based on item 6 and 7.

10. Trademark and brand issues with naming of releases. (Resolved) * There are no \
binary releases by the PPMC besides the repository.apache.org releases in item 5.

14, 22, 23. Branding and release of 3rd parties containing unreleased code.
Known pages with issues: * \
+https://docs.nvidia.com/deeplearning/frameworks/mxnet-release-notes/rel_20-03.html+ \
(item 14, Resolved)  NVIDIA switched to "NVIDIA Optimized Deep Learning Framework, \
                powered by Apache MXNet" for naming.
 * +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 [1]. \
Bitnami responded but the page still needs update. We followed up again with Bitnami \
                this week.
 * +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. Amazon intends to use AWS MX powered by Apache MXNet naming convention [2]. \
                The naming change is in progress.
 * After last update, for item 15, SourceForge further added a disclaimer that the \
page is an automatic mirror of MXNet's GitHub tags: \
+https://sourceforge.net/projects/apache-mxnet.mirror/+.

In addition, MXNet PPMC identified several more listings that require correction \
according to the branding guideline on AWS marketplace that are related to AWS Deep \
Learning Container/DLAMI [3], and they have all been resolved.  
Reference links 
[1]: https://lists.apache.org/thread.html/r1fabd3c081286b06b6e9c9283cb5986450f07d52309db3b74bfe3a24%40%3Cprivate.mxnet.apache.org%3E
 [2]  https://lists.apache.org/thread.html/rad72c3b39170da16e34e77536c0e3134f93ed429b07ddd643a6fa5ba%40%3Cprivate.mxnet.apache.org%3E
 [3]  https://lists.apache.org/thread.html/r3f95f5766e8f1ee8fbd8183720804afdc1678f0149f56144da45f619%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


[prev in list] [next in list] [prev in thread] [next in thread]
Configure | About | News | Add a list | Sponsored by KoreLogic