From general-return-74041-apmail-incubator-general-archive=incubator.apache.org@incubator.apache.org Tue Sep 15 21:36:05 2020 Return-Path: X-Original-To: apmail-incubator-general-archive@www.apache.org Delivered-To: apmail-incubator-general-archive@www.apache.org Received: from mailroute1-lw-us.apache.org (mailroute1-lw-us.apache.org [207.244.88.153]) by minotaur.apache.org (Postfix) with ESMTP id 492FD1A204 for ; Tue, 15 Sep 2020 21:36:05 +0000 (UTC) Received: from mail.apache.org (localhost [127.0.0.1]) by mailroute1-lw-us.apache.org (ASF Mail Server at mailroute1-lw-us.apache.org) with SMTP id 8A52D123207 for ; Tue, 15 Sep 2020 21:36:04 +0000 (UTC) Received: (qmail 23089 invoked by uid 500); 15 Sep 2020 21:36:02 -0000 Delivered-To: apmail-incubator-general-archive@incubator.apache.org Received: (qmail 22906 invoked by uid 500); 15 Sep 2020 21:36:01 -0000 Mailing-List: contact general-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: general@incubator.apache.org Delivered-To: mailing list general@incubator.apache.org Received: (qmail 22876 invoked by uid 99); 15 Sep 2020 21:36:01 -0000 Received: from mailrelay1-us-west.apache.org (HELO mailrelay1-us-west.apache.org) (209.188.14.139) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 15 Sep 2020 21:36:01 +0000 Received: from jira-he-de.apache.org (static.172.67.40.188.clients.your-server.de [188.40.67.172]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id D18FE428A6 for ; Tue, 15 Sep 2020 21:36:00 +0000 (UTC) Received: from jira-he-de.apache.org (localhost.localdomain [127.0.0.1]) by jira-he-de.apache.org (ASF Mail Server at jira-he-de.apache.org) with ESMTP id 494F07802F0 for ; Tue, 15 Sep 2020 21:36:00 +0000 (UTC) Date: Tue, 15 Sep 2020 21:36:00 +0000 (UTC) From: "Sheng Zha (Jira)" To: general@incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Comment Edited] (INCUBATOR-253) Issues with MXNet releases and their distribution MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/INCUBATOR-253?page=3Dcom.atlass= ian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1= 7195126#comment-17195126 ]=20 Sheng Zha edited comment on INCUBATOR-253 at 9/15/20, 9:35 PM: --------------------------------------------------------------- *Summary* The PPMC continues to make progress in resolving license and branding issue= s. 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 st= atus 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 constitu= tes 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. At the moment, NVIDIA's legal is actively exploring options o= n resolving this issue. Michael requested extension with MXNet PPMC to not = treat the related component as Category-X and delay actions until Oct. boar= d meeting. Also note that there was confusion around MXNet's status around integration= with Intel products.=C2=A0In MXNet, there has never been public distributi= on of MXNet where MKL was included. There was an initial inquiry around whe= ther MKL builds can be enabled but was rejected, so this never came into pr= actice. Also, to my knowledge Intel has not produced custom MXNet builds wi= th closed-source components. MXNet 1.7.0 release has completed. 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 since last update:* 1. Source and convenance binary releases containing Category X licensed co= de. (pending) * Source code releases by the PPMC do not contain Category X code, no issu= e. Takedown of binary releases by the PPMC on repository.apache.org is on hol= d, 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 ar= e 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-51= 6. 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 br= anding 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.o= rg releases in item 5. 12. Releases and other nightly builds on [https://repo.mxnet.io|https://rep= o.mxnet.io/] / [https://dist.mxnet.io|https://dist.mxnet.io/] containing Ca= tegory X licensed code (resolved) * Neither of the two site contains releases. The binaries are only intende= d 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 complia= nce 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 GitH= ub and the the mirror automatically deleted the it [3]. As such, the origin= al issue is resolved. The PPMC will follow up with SourceForge on the funct= ionality of filtering out non-release tags. AWS Marketplace related links [https://aws.amazon.com/marketplace/pp/B07YW8HVLD?qid=3D1595741035764&sr= =3D0-4&ref_=3Dsrh_res_product_title] (item 22, pending) * PPMC reached out to Bitnami directly regarding this listing [5]. Bitnami= responded and is working on the branding issues. [https://aws.amazon.com/marketplace/search/results?x=3D0&y=3D0&searchTerms= =3D%22MXNet] (item 23, pending) * PPMC reached out to AWS through internal channel to fix branding issue. = Will update in the next few days. In addition, MXNet PPMC identified several more listings that require corre= ction according to the branding guideline on AWS marketplace that are relat= ed to AWS Deep Learning Container/DLAMI [6], and are actively working on ad= dressing them.=C2=A0 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=3D17= 174133&page=3Dcom.atlassian.jira.plugin.system.issuetabpanels:comment-tabpa= nel#comment-17174133 [5]: [https://lists.apache.org/thread.html/r1fabd3c081286b06b6e9c9283cb598= 6450f07d52309db3b74bfe3a24%40%3Cprivate.mxnet.apache.org%3E] [6]:=C2=A0[https://lists.apache.org/thread.html/r3f95f5766e8f1ee8fbd8183720= 804afdc1678f0149f56144da45f619%40%3Cprivate.mxnet.apache.org%3E] was (Author: zhasheng): *Summary* The PPMC continues to make progress in resolving license and branding issue= s. 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 st= atus 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 constitu= tes 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. At the moment, NVIDIA's legal is actively exploring options o= n resolving this issue. Michael requested extension with MXNet PPMC to not = treat the related component as Category-X and delay actions until Oct. boar= d meeting. Also note that there was confusion around MXNet's status around integration= with Intel products.=C2=A0In MXNet, there has never been public distributi= on of MXNet where MKL was included. There was an initial inquiry around whe= ther MKL builds can be enabled but was rejected, so this never came into pr= actice. Also, to my knowledge Intel has not produced custom MXNet builds wi= th closed-source components. MXNet 1.7.0 release has completed. 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 since last update:* 1. Source and convenance binary releases containing Category X licensed co= de. (pending) * Source code releases by the PPMC do not contain Category X code, no issu= e. Takedown of binary releases by the PPMC on repository.apache.org is on hol= d, 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 ar= e 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-51= 6. 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 br= anding 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.o= rg releases in item 5. 12. Releases and other nightly builds on [https://repo.mxnet.io|https://rep= o.mxnet.io/] / [https://dist.mxnet.io|https://dist.mxnet.io/] containing Ca= tegory X licensed code (resolved) * Neither of the two site contains releases. The binaries are only intende= d 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 complia= nce 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 GitH= ub and the the mirror automatically deleted the it [3]. As such, the origin= al issue is resolved. The PPMC will follow up with SourceForge on the funct= ionality of filtering out non-release tags. AWS Marketplace related links [https://aws.amazon.com/marketplace/pp/B07YW8HVLD?qid=3D1595741035764&sr= =3D0-4&ref_=3Dsrh_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=3D0&y=3D0&searchTerms= =3D%22MXNet] (item 23, pending) * PPMC reached out to AWS through internal channel to fix branding issue. = Will update in the next few days. In addition, MXNet PPMC identified several more listings that require corre= ction according to the branding guideline on AWS marketplace that are relat= ed to AWS Deep Learning Container/DLAMI [6], and are actively working on ad= dressing them.=C2=A0 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=3D17= 174133&page=3Dcom.atlassian.jira.plugin.system.issuetabpanels:comment-tabpa= nel#comment-17174133 [5]: [https://lists.apache.org/thread.html/r1fabd3c081286b06b6e9c9283cb598= 6450f07d52309db3b74bfe3a24%40%3Cprivate.mxnet.apache.org%3E] [6]:=C2=A0https://lists.apache.org/thread.html/r3f95f5766e8f1ee8fbd81837208= 04afdc1678f0149f56144da45f619%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 c= ode. > 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.=20 > 10. Trademark and brand issues with naming of releases.=20 > 11. Developer releases available to users and public searchable https://r= epo.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