from:"Sheng Zha \(Jira\)"

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

2021-04-07 Thread Sheng Zha (Jira)



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

Sheng Zha commented on INCUBATOR-253:
-

Dear IPMC,

After reviewing the open issues (1, 5, 22, 23), I believe with the exception of 
some listings in 23, all remaining items have been resolved. We will track any 
recurring issue in 23 as part of regular trademark and branding review.

Thanks,

Sheng

> 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

[jira] [Comment Edited] (INCUBATOR-253) Issues with MXNet releases and their distribution

2021-01-06 Thread Sheng Zha (Jira)

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

Sheng Zha edited comment on INCUBATOR-253 at 1/7/21, 3:57 AM:
--

*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 and backfill of compliant binary releases by the PPMC on
repository.apache.org is in progress, 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) * The
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=0-4_=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=0=%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]

was (Author: zhasheng):
*Summary*
Most of the issues from last

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

2021-01-05 Thread Sheng Zha (Jira)

[
https://issues.apache.org/jira/browse/INCUBATOR-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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.

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.

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=0-4_=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=0=%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:

[jira] [Comment Edited] (INCUBATOR-253) Issues with MXNet releases and their distribution

2020-09-15 Thread Sheng Zha (Jira)

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

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 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. At the moment, NVIDIA's legal is actively exploring options on
resolving this issue. Michael requested extension with MXNet PPMC to not treat
the related component as Category-X and delay actions until Oct. board meeting.

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 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 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://repo.mxnet.io/] /
[https://dist.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=0-4_=srh_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=0=0=%22MXNet]
(item 23, pending)
* PPMC reached out to AWS through internal channel to fix branding issue. Will
update in the next few

[jira] [Comment Edited] (INCUBATOR-253) Issues with MXNet releases and their distribution

2020-09-15 Thread Sheng Zha (Jira)

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

Sheng Zha edited comment on INCUBATOR-253 at 9/15/20, 9:34 PM:
---

*Summary*

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.

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].

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.

14. to 23. Branding and release of 3rd parties containing unreleased code.
(pending)

AWS Marketplace related links

[https://aws.amazon.com/marketplace/pp/B07YW8HVLD?qid=1595741035764=0-4_=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=0=%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

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

2020-09-13 Thread Sheng Zha (Jira)

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

Sheng Zha commented on INCUBATOR-253:
-

Summary (WIP)

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].

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=0-4_=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=0=%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]:

[jira] [Comment Edited] (INCUBATOR-253) Issues with MXNet releases and their distribution

2020-08-08 Thread Sheng Zha (Jira)

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

Sheng Zha edited comment on INCUBATOR-253 at 8/9/20, 2:09 AM:
--

h3. Summary

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)
-

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

2020-08-08 Thread Sheng Zha (Jira)

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

Sheng Zha commented on INCUBATOR-253:
-

h3. Summary

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

2. Website giving access to downloads of non released/unapproved code.
(resolved)
- Website contained links to nightly development builds which have been
removed [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.

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://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

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

2020-08-08 Thread Sheng Zha (Jira)



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

Sheng Zha commented on INCUBATOR-253:
-

I added an update in the legal/trademarks section 
https://cwiki.apache.org/confluence/display/INCUBATOR/August2020#legal--trademarks

> 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

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

2020-07-12 Thread Sheng Zha (Jira)



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

Sheng Zha commented on INCUBATOR-253:
-

[~jmclean] you added some notes to it and I'd like to continue the discussion 
here. You wrote:

> But I have two concerns ... b) branding all release as "3rd party" may not be 
> the best way to solve the issue.

First, I'd like to clarify that the claim is inaccurate in that we are not 
classifying all releases as "3rd party". For example, the source releases are 
still very much first party and we only make official source releases. In 
addition, assuming that you actually referred to convenience binary releases, 
I'd like to understand more on why having third-party handle the binary 
releases for our releases is "not the best". It serves the needs of our 
community for faster installation and the fact of having third-party releases 
does not appear to be forbidden in the overall policies in Apache. Could you be 
more specific on what your concerns are?

> 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

[jira] [Comment Edited] (INCUBATOR-253) Issues with MXNet releases and their distribution

2020-06-29 Thread Sheng Zha (Jira)



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

Sheng Zha edited comment on INCUBATOR-253 at 6/29/20, 11:28 PM:


Justin, on what ground did you delete my comment? I believe anyone in Apache 
should be able to make any comments that are related to the topic as long as 
the conversation is civilized. So I find the deletion inappropriate and rude.

Link to the related conversation on why the updates are organized the way I was 
providing it: 
https://lists.apache.org/thread.html/r0446adfbbed24b016338b2cfa6dcef90066b203162e464ae0088da08%40%3Cprivate.mxnet.apache.org%3E


was (Author: zhasheng):
Justin, why did you delete my comment?

> 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

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

2020-06-29 Thread Sheng Zha (Jira)



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

Sheng Zha commented on INCUBATOR-253:
-

Justin, why did you delete my comment?

> 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

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

2020-06-29 Thread Sheng Zha (Jira)



[ 
https://issues.apache.org/jira/browse/INCUBATOR-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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
>

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

2020-06-24 Thread Sheng Zha (Jira)



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

Sheng Zha commented on INCUBATOR-253:
-

By the way, I have of course read the LEGAL-515 that we created, and we are 
discussing the CUDA licensing and distribution requirements in LEGAL-516.

> 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

[jira] [Comment Edited] (INCUBATOR-253) Issues with MXNet releases and their distribution

2020-06-24 Thread Sheng Zha (Jira)



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

Sheng Zha edited comment on INCUBATOR-253 at 6/24/20, 8:26 PM:
---

> Justin: 3rd party distribution also have different branding and trademark 
> policies they need to comply with. In general they would also need to be 
> based on released code.

> Sheng: I don't think the incubator has the right to require this given that 
> the apache license v2 allows redistribution with or without modification as 
> long as the conditions are met.

> Justin: The incubator has every right to ask podlings to comply with ASF 
> policy. ASF policy is on top of what the Apache License allows.

Agreed on the last comment. This is truism and (I believe) not relevant here, 
given that we were talking about third-party releases. I included the full 
context above for your convenience.

The responsibility of the PPMC in this case would be to make sure users of our 
project are sufficiently notified that these are not first-party releases and 
that they contain additional components that pose further restriction than what 
ALv2 license grants, and the third-party use complies with legal and trademark 
requirements. And we the PPMC fully intend to do so. As mentioned, we will 
propose the option we want to pursue in full observation of the Apache's 
policies and we can continue the discussion on how to do this properly.

 

> The incubator also has the right to terminate a project if it doesn't comply 
>with policy.

Please realize that if certain constraints affect the viability of our 
ecosystem, a threat to terminate carries little weight to us. Also, one 
difficulty we've been having is caused by individuals imposing their opinions 
as policies on us. Examples include draft release policies that haven't 
sufficiently considered podling's release needs or passed proper Apache 
processes.

That said, we are still working hard to find a way to make MXNet viable in 
Apache incubator. In the unfortunate circumstances in which this is no longer 
possible, or that we have policy violations that the incubator can no longer 
tolerate to the extent that termination is warranted, let us know.

 

At the core, the problem is that GPU acceleration, one of the two pillars of 
modern deep learning frameworks (w/ the other pillar being 
auto-differentiation) only receives the status of category-X optional features 
at Apache. As a result, MXNet has no choice but to seek ways to accommodate 
both the goal of protecting the freedom for the use of our software and the 
goal of having a useful deep learning framework. Thus, we test many unclear 
definitions in the scope of category-X optional features. We also do not expect 
the situation to change as new hardware accelerator vendors are unlikely to 
allow reverse engineering which is incompatible with ALv2. There have been 
several generations of popular deep learning frameworks and we realize now that 
it's no coincidence that none was in Apache before MXNet.

As PPMC, we fully intend to uphold our responsibility of protecting our users 
from legal risks as part of Apache and we are learning our lessons for this. 
Keep in mind that we also have the responsibility to be a useful modern deep 
learning framework. We will not compromise one responsibility for the other. My 
hope is that the incubator is willing to work with us through rational 
discussion, and help guide us to our goal in the welcoming way of Apache.


was (Author: zhasheng):
> Justin: 3rd party distribution also have different branding and trademark 
> policies they need to comply with. In general they would also need to be 
> based on released code.

> Sheng: I don't think the incubator has the right to require this given that 
> the apache license v2 allows redistribution with or without modification as 
> long as the conditions are met.

> Justin: The incubator has every right to ask podlings to comply with ASF 
> policy. ASF policy is on top of what the Apache License allows.

Agreed on the last comment. This is truism and (I believe) not relevant here, 
given that we were talking about third-party releases. I included the full 
context above for your convenience.

The responsibility of the PPMC in this case would be to make sure users of our 
project are sufficiently notified that these are not first-party releases and 
that they contain additional components that pose further restriction than what 
ALv2 license grants. And we the PPMC fully intend to do so. As mentioned, we 
will propose the option we want to pursue in full observation of the Apache's 
policies and we can continue the discussion on how to do this properly.

 

> The incubator also has the right to terminate a project if it doesn't comply 
>with policy.

Please realize that if certain constraints affect the viability of our 
ecosystem, a

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

2020-06-24 Thread Sheng Zha (Jira)



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

Sheng Zha commented on INCUBATOR-253:
-

> Justin: 3rd party distribution also have different branding and trademark 
> policies they need to comply with. In general they would also need to be 
> based on released code.

> Sheng: I don't think the incubator has the right to require this given that 
> the apache license v2 allows redistribution with or without modification as 
> long as the conditions are met.

> Justin: The incubator has every right to ask podlings to comply with ASF 
> policy. ASF policy is on top of what the Apache License allows.

Agreed on the last comment. This is truism and (I believe) not relevant here, 
given that we were talking about third-party releases. I included the full 
context above for your convenience.

The responsibility of the PPMC in this case would be to make sure users of our 
project are sufficiently notified that these are not first-party releases and 
that they contain additional components that pose further restriction than what 
ALv2 license grants. And we the PPMC fully intend to do so. As mentioned, we 
will propose the option we want to pursue in full observation of the Apache's 
policies and we can continue the discussion on how to do this properly.

 

> The incubator also has the right to terminate a project if it doesn't comply 
>with policy.

Please realize that if certain constraints affect the viability of our 
ecosystem, a threat to terminate carries little weight to us. Also, one 
difficulty we've been having is caused by individuals imposing their opinions 
as policies on us. Examples include draft release policies that haven't 
sufficiently considered podling's release needs or passed proper Apache 
processes.

That said, we are still working hard to find a way to make MXNet viable in 
Apache incubator. In the unfortunate circumstances in which this is no longer 
possible, or that we have policy violations that the incubator can no longer 
tolerate to the extent that termination is warranted, let us know.

 

At the core, the problem is that GPU acceleration, one of the two pillars of 
modern deep learning frameworks (w/ the other pillar being 
auto-differentiation) only receives the status of category-X optional features 
at Apache. As a result, MXNet has no choice but to seek ways to accommodate 
both the goal of protecting the freedom for the use of our software and the 
goal of having a useful deep learning framework. Thus, we test many unclear 
definitions in the scope of category-X optional features. We also do not expect 
the situation to change as new hardware accelerator vendors are unlikely to 
allow reverse engineering which is incompatible with ALv2. There have been 
several generations of popular deep learning frameworks and we realize now that 
it's no coincidence that none was in Apache before MXNet.

As PPMC, we fully intend to uphold our responsibility of protecting our users 
from legal risks as part of Apache and we are learning our lessons for this. 
Keep in mind that we also have the responsibility to be a useful modern deep 
learning framework. We will not compromise one responsibility for the other. My 
hope is that the incubator is willing to work with us through rational 
discussion, and help guide us to our goal in the welcoming way of Apache.

> 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

[jira] [Comment Edited] (INCUBATOR-253) Issues with MXNet releases and their distribution

2020-06-22 Thread Sheng Zha (Jira)



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

Sheng Zha edited comment on INCUBATOR-253 at 6/23/20, 12:09 AM:


> Anyone including PPMC members (with hat off) can build a third party artifact 
>but it needs to be clear to potential downloaders/users that said artifact is 
>a third party artifact.

> 3rd party distribution also have different branding and trademark policies 
>they need to comply with.

This makes sense. We plan to make a proposal on how our community will provide 
pre-built binary as third-party releases and review its adherence to the 
branding and trademark policies.

> In general they would also need to be based on released code.

I don't think the incubator has the right to require this given that the apache 
license v2 allows redistribution with or without modification as long as the 
conditions are met.

> in short if it a channel controlled by the (P)PMC then it would not be 
>considered an 3rd party release.

The definition of "control" is ambiguous. As long as the PPMC hat can be on or 
off at will, any declaration of "controlled by the (P)PMC" can be true and 
false at the same time.


was (Author: zhasheng):
> Anyone including PPMC members (with hat off) can build a third party artifact 
>but it needs to be clear to potential downloaders/users that said artifact is 
>a third party artifact.

> 3rd party distribution also have different branding and trademark policies 
>they need to comply with.

This makes sense. We plan to make a proposal on how our community will provide 
pre-built binary as third-party releases that adhere to the branding and 
trademark policies.

> In general they would also need to be based on released code.

I don't think the incubator has the right to require this given that the apache 
license v2 allows redistribution with or without modification as long as the 
conditions are met.

> in short if it a channel controlled by the (P)PMC then it would not be 
>considered an 3rd party release.

The definition of "control" is ambiguous. As long as the PPMC hat can be on or 
off at will, any declaration of "controlled by the (P)PMC" can be true and 
false at the same time.

> 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

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

2020-06-22 Thread Sheng Zha (Jira)



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

Sheng Zha commented on INCUBATOR-253:
-

> Anyone including PPMC members (with hat off) can build a third party artifact 
>but it needs to be clear to potential downloaders/users that said artifact is 
>a third party artifact.

> 3rd party distribution also have different branding and trademark policies 
>they need to comply with.

This makes sense. We plan to make a proposal on how our community will provide 
pre-built binary as third-party releases that adhere to the branding and 
trademark policies.

> In general they would also need to be based on released code.

I don't think the incubator has the right to require this given that the apache 
license v2 allows redistribution with or without modification as long as the 
conditions are met.

> in short if it a channel controlled by the (P)PMC then it would not be 
>considered an 3rd party release.

The definition of "control" is ambiguous. As long as the PPMC hat can be on or 
off at will, any declaration of "controlled by the (P)PMC" can be true and 
false at the same time.

> 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

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

2020-06-22 Thread Sheng Zha (Jira)



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

Sheng Zha commented on INCUBATOR-253:
-

> I would be of the opinion that nightly builds (or in fact any build) created 
> by the PPMC are NOT allowed to have category X licensed code.

I'd like to clarify on this. What's the definition of a build that's created by 
the PPMC? Can I, a PPMC member, take my PPMC hat off and make a build? If not, 
does it mean that making a build as an independent individual is a right that 
one waives when joining an apache project as a committer/PPMC?

The viability of the growth of MXNet ecosystem hinges on this point so I'd 
appreciate clear answers on the my questions.

> 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

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

2020-06-20 Thread Sheng Zha (Jira)



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

Sheng Zha commented on INCUBATOR-253:
-

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.

We only have nightly builds on these websites and all binaries on these 
websites are for development and testing purposes. There is no "Releases" and 
we have never advertised that people should install convenience binaries of 
official releases from these websites. I believe nightly builds are allowed to 
have category X licensed code and thus I'm not sure if this item is a valid 
issue.

> 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.
> 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

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

2020-06-20 Thread Sheng Zha (Jira)



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

Sheng Zha commented on INCUBATOR-253:
-

7. Docker releases containing Category X licensed code.
8 Docker releases containing unreleased/unapproved code.

What's an example of our docker release that contains unreleased/unapproved 
code that doesn't fall into the category X license? If none, I will consider 
these duplicates.

 

> 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.
> 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

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

2020-06-20 Thread Sheng Zha (Jira)



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

Sheng Zha commented on INCUBATOR-253:
-

9. Trademark and branding issues with PiPy and Docker releases.
10. Trademark and brand issues with naming of releases.

What binary releases other than the pypi and docker releases have trademark and 
branding issue? If none, I will consider these duplicates.

> 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.
> 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

[jira] [Comment Edited] (INCUBATOR-253) Issues with MXNet releases and their distribution

2020-06-20 Thread Sheng Zha (Jira)



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

Sheng Zha edited comment on INCUBATOR-253 at 6/21/20, 3:18 AM:
---

Yes, I'm aware and I am updating that issue to reflect them. Also, we obviously 
missed some issues and I want to make sure that this doesn't happen again, so 
it would be great if you could help link to the existing previous discussions 
on each of the issues you listed above so that we could conduct a retrospect.

> It's been serval months now since the project has been aware of most of these 
> issues

We just started realizing the issues as we recently initiate license reviews 
for binary release as part of https://issues.apache.org/jira/browse/LEGAL-515, 
https://issues.apache.org/jira/browse/LEGAL-516 both of which we initiated in 
May. Please don't make it sound as if it's intentional procrastination from us.

With respect to visibility to the board, I assume they can access the GitHub 
issues. Alternatively, I can paste back a weekly update on the status here.


was (Author: zhasheng):
Yes, I'm aware and I am updating that issue to reflect them. Also, we obviously 
missed some issues and I want to make sure that this doesn't happen again, so 
it would be great if you could help link to the existing previous discussions 
on each of the issues you listed above so that we could conduct a retrospect.

With respect to visibility to the board, I assume they can access the GitHub 
issues. Alternatively, I can paste back a weekly update on the status here.

> 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.
> 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

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

2020-06-20 Thread Sheng Zha (Jira)



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

Sheng Zha commented on INCUBATOR-253:
-

2. Website giving access to downloads of non released/unapproved 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.

13. Lack of clarity on all platforms for what is an ASF release and what is not.

 

These three items seem to refer to the same issue?

> 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.
> 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

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

2020-06-20 Thread Sheng Zha (Jira)



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

Sheng Zha commented on INCUBATOR-253:
-

# Source and convenance binary releases containing Category X licensed code.

Which source files are you referring to?

> 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.
> 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

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

2020-06-20 Thread Sheng Zha (Jira)



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

Sheng Zha commented on INCUBATOR-253:
-

Yes, I'm aware and I am updating that issue to reflect them. Also, we obviously 
missed some issues and I want to make sure that this doesn't happen again, so 
it would be great if you could help link to the existing previous discussions 
on each of the issues you listed above so that we could conduct a retrospect.

With respect to visibility to the board, I assume they can access the GitHub 
issues. Alternatively, I can paste back a weekly update on the status here.

> 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.
> 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

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

2020-06-20 Thread Sheng Zha (Jira)



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

Sheng Zha commented on INCUBATOR-253:
-

Acknowledged. We have been tracking the efforts 
[https://github.com/apache/incubator-mxnet/issues/18397]. For now I will keep 
updating that issue until we are close to completion on this JIRA.

We are making some progress but due to the complexity, the number of involved 
parties, slow turnaround with some of them, while trying to minimize the impact 
to our community while carrying out the changes, we expect that it would take 
some time before the items complete. Given that we are the only project in 
Apache we are aware of that invest heavily on GPU acceleration, which is in the 
blast radius, we also expect that some additional discussions need to be made.

> 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.
> 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

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

[jira] [Comment Edited] (INCUBATOR-253) Issues with MXNet releases and their distribution

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

[jira] [Comment Edited] (INCUBATOR-253) Issues with MXNet releases and their distribution

[jira] [Comment Edited] (INCUBATOR-253) Issues with MXNet releases and their distribution

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

[jira] [Comment Edited] (INCUBATOR-253) Issues with MXNet releases and their distribution

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

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

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

[jira] [Comment Edited] (INCUBATOR-253) Issues with MXNet releases and their distribution

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

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

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

[jira] [Comment Edited] (INCUBATOR-253) Issues with MXNet releases and their distribution

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

[jira] [Comment Edited] (INCUBATOR-253) Issues with MXNet releases and their distribution

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

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

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

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

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

[jira] [Comment Edited] (INCUBATOR-253) Issues with MXNet releases and their distribution

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

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

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

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

27 matches

Site Navigation

Mail list logo

Footer information