[
https://issues.apache.org/jira/browse/INCUBATOR-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17141307#comment-17141307
]
Justin Mclean edited comment on INCUBATOR-253 at 6/21/20, 8:11 AM:
---
Re 1 there was discussion about Category X headers included in the source code.
2, 4, 13 are seperate issues. For the trade marks issue you cannot call a
release "Apache MXNet" if it contains something from category X, but there are
also separate trademark/branding issues with both the PiPy and Docker download
pages. 7 and 8 are seperate issues. Re 12 a Google search shows these artefacts
to users to download. 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. Re category X code in releases I also believe there was multiple category
X issues including one with Intel and one with CUDA.
The board or Incubator PMC is unlikely to search though GitHub issues to see
what is being done, but they would look at your mailing list(s) for discussion
about these items. I don't see any discussion about changing the CUDA license
or what's involved there. Is this conversation taking place and if so where?
It's up to PPMC to correct these issues. At some point the project needs to do
this for itself and shows it understand ASF policy before it can graduate. So
it would be great if the project can gp ahead and do this on it own and show
it's making progress towards that goal. However if you need help please ask
your mentors or if for some reason they can't help then bring it up here or on
the general@ or relevant mailing list.
was (Author: jmclean):
Re 1 there was discussion about Category X headers included in the source code.
2, 4, 13 are seperate issues. For the trade marks issue you cannot call a
release "Apache MXNet" if it contains something from category X, but there are
also separate trademark issues with both the PiPy and Docker download pages. 7
and 8 are seperate issues. Re 12 a Google search shows these artefacts to users
to download. 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. Re
category X code in releases I also believe there was multiple category X issues
including one with Intel and one with CUDA.
The board or Incubator PMC is unlikely to search though GitHub issues to see
what is being done, but they would look at your mailing list(s) for discussion
about these items. I don't see any discussion about changing the CUDA license
or what's involved there. Is this conversation taking place and if so where?
It's up to PPMC to correct these issues. At some point the project needs to do
this for itself and shows it understand ASF policy before it can graduate. So
it would be great if the project can gp ahead and do this on it own and show
it's making progress towards that goal. However if you need help please ask
your mentors or if for some reason they can't help then bring it up here or on
the general@ or relevant mailing list.
> 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
