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

To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Reply via email to