[jira] [Commented] (INCUBATOR-281) Broken link
[ https://issues.apache.org/jira/browse/INCUBATOR-281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17787384#comment-17787384 ] Justin Mclean commented on INCUBATOR-281: - It did exist at one point: https://web.archive.org/web/20200428010425/https://incubator.apache.org/guides/retirement.html And the file is still here: https://github.com/apache/incubator/blob/master/pages/guides/retirement.ad So perhaps something is going wrong with the build? > Broken link > --- > > Key: INCUBATOR-281 > URL: https://issues.apache.org/jira/browse/INCUBATOR-281 > Project: Incubator > Issue Type: Bug >Reporter: Sebb >Priority: Major > > https://cwiki.apache.org/confluence/display/incubator/RetiringPodlings > links to > https://incubator.apache.org/guides/retirement.html > which does not exist. > Not sure whether it ever did exist. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Closed] (INCUBATOR-267) Update the podling retirement guide
[
https://issues.apache.org/jira/browse/INCUBATOR-267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Mclean closed INCUBATOR-267.
---
Resolution: Fixed
completed
> Update the podling retirement guide
> ---
>
> Key: INCUBATOR-267
> URL: https://issues.apache.org/jira/browse/INCUBATOR-267
> Project: Incubator
> Issue Type: Improvement
>Reporter: Willem Jiang
>Priority: Major
>
> We need to ask Infra to remove the LDAP entry of the retired project.
> As we can update retired website by adding empty index.html file into the
> director of retired project like this
> [https://github.com/apache/incubator/tree/master/assets/retired/\{podling}
> |https://github.com/apache/incubator/tree/master/assets/retired]
> according to [this
> discussion|https://lists.apache.org/thread.html/re412c99987badb24c9d50976211346b3775aa42a19900b442f920e75%40%3Cgeneral.incubator.apache.org%3E]
> We need to update the [steps to retirement |
> https://incubator.apache.org/guides/retirement.html#steps_to_retirement]
> about it.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Closed] (INCUBATOR-275) Need to update Incubator statistics on the website landing page
[ https://issues.apache.org/jira/browse/INCUBATOR-275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Mclean closed INCUBATOR-275. --- Resolution: Fixed stats have been updated > Need to update Incubator statistics on the website landing page > --- > > Key: INCUBATOR-275 > URL: https://issues.apache.org/jira/browse/INCUBATOR-275 > Project: Incubator > Issue Type: Improvement > Components: site >Reporter: Andrew Wetmore >Priority: Major > > h3. The index page for the Incubator website has a brief history that seems > to be three or four years out of date. I would be glad to update it, but need > the current figures: > * Total number of podlings > * Number that have graduated > * Total number of mentors > * Average # of podlings in incubation at any one time > * Typical incubation period > h3. Incubator History > The Incubator was created [in > 2002|https://www.apache.org/foundation/records/minutes/2002/board_minutes_2002_10_16.txt]. > As of November 2019 it has helped 315 podlings, of which more than 200 have > graduated. More than 300 mentors have guided and supported podlings. There > are around 45 or 50 podlings in incubation at any one time, and incubation > typically takes 1 1/2 years. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Closed] (INCUBATOR-277) Allow GitHub Actions to create PRs
[ https://issues.apache.org/jira/browse/INCUBATOR-277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Mclean closed INCUBATOR-277. --- Resolution: Invalid > Allow GitHub Actions to create PRs > -- > > Key: INCUBATOR-277 > URL: https://issues.apache.org/jira/browse/INCUBATOR-277 > Project: Incubator > Issue Type: Wish >Reporter: Junren Yu >Priority: Major > Labels: TOBECLOSED > > I am a committer of [DevLake|https://github.com/apache/incubator-devlake]. > Since we are still in the initial iteration, we need to cherry-pick the > previous version after submitting the pr repair. I created a GitHub action > named "Auto Cherry Pick" in our repository. Currently, this action cannot be > used because the repository has not enabled the permission to allow the > action to submit pr. We want to be able to enable this permission in the > repository. > > !https://user-images.githubusercontent.com/37237996/240861206-65885923-830e-47a3-866c-472f381267d6.jpeg! -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Closed] (INCUBATOR-270) Install osschat GitHub app
[ https://issues.apache.org/jira/browse/INCUBATOR-270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Mclean closed INCUBATOR-270. --- Resolution: Invalid > Install osschat GitHub app > -- > > Key: INCUBATOR-270 > URL: https://issues.apache.org/jira/browse/INCUBATOR-270 > Project: Incubator > Issue Type: Task > Components: git >Reporter: Heping Wang >Priority: Major > Labels: TOBECLOSED > > Dear Infra team, > Can you please install GitHub osschat([https://github.com/apps/osschat]) > application for our apache/incubator-linkis GitHub repo ? > Thanks -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Closed] (INCUBATOR-273) remove jul...@apache.org from moderators of heron and toree podlings mailing lists
[ https://issues.apache.org/jira/browse/INCUBATOR-273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Mclean closed INCUBATOR-273. --- Resolution: Invalid > remove jul...@apache.org from moderators of heron and toree podlings mailing > lists > -- > > Key: INCUBATOR-273 > URL: https://issues.apache.org/jira/browse/INCUBATOR-273 > Project: Incubator > Issue Type: Task >Reporter: Julien Le Dem >Priority: Major > Labels: TOBECLOSED > > * > [comm...@heron.apache.org|https://lists.apache.org/list.html?comm...@heron.apache.org] > as jul...@apache.org > * > [d...@heron.apache.org|https://lists.apache.org/list.html?d...@heron.apache.org] > as jul...@apache.org > * > [iss...@heron.apache.org|https://lists.apache.org/list.html?iss...@heron.apache.org] > as jul...@apache.org > * > [priv...@heron.apache.org|https://lists.apache.org/list.html?priv...@heron.apache.org] > as jul...@apache.org > * > [u...@heron.apache.org|https://lists.apache.org/list.html?u...@heron.apache.org] > as jul...@apache.org > * > [comm...@toree.apache.org|https://lists.apache.org/list.html?comm...@toree.apache.org] > as jul...@apache.org > * > [d...@toree.apache.org|https://lists.apache.org/list.html?d...@toree.apache.org] > as jul...@apache.org > * > [priv...@toree.apache.org|https://lists.apache.org/list.html?priv...@toree.apache.org] > as jul...@apache.org -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Closed] (INCUBATOR-274) Gives Orbit (orbit.love) access to GitHub repos
[ https://issues.apache.org/jira/browse/INCUBATOR-274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Mclean closed INCUBATOR-274. --- Resolution: Invalid > Gives Orbit (orbit.love) access to GitHub repos > --- > > Key: INCUBATOR-274 > URL: https://issues.apache.org/jira/browse/INCUBATOR-274 > Project: Incubator > Issue Type: Task > Components: git >Reporter: Hezheng Yin >Priority: Major > Labels: TOBECLOSED > > *Update:* I just realized that I should open this issue at > [https://issues.apache.org/jira/projects/INFRA.] Please feel free to close > this issue. Sorry for the trouble. > > Dear Infra Team, > > I'm looking to set up Orbit (orbit.love, a community growth platform) for > DevLake. I ran into a permission issue when I tried to give Orbit access to > DevLake's repos as shown in this > [screenshot|https://user-images.githubusercontent.com/2908155/206342490-32d84f00-15df-49d3-b3d4-0b758c4ed3ac.png]. > > Is there any workaround that may get this integration working? Thanks in > advance for your guidance! -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Commented] (INCUBATOR-277) Allow GitHub Actions to create PRs
[ https://issues.apache.org/jira/browse/INCUBATOR-277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17726120#comment-17726120 ] Justin Mclean commented on INCUBATOR-277: - You'll need to raise a ticket with Infra to help with this. > Allow GitHub Actions to create PRs > -- > > Key: INCUBATOR-277 > URL: https://issues.apache.org/jira/browse/INCUBATOR-277 > Project: Incubator > Issue Type: Wish >Reporter: Junren Yu >Priority: Major > > I am a committer of [DevLake|https://github.com/apache/incubator-devlake]. > Since we are still in the initial iteration, we need to cherry-pick the > previous version after submitting the pr repair. I created a GitHub action > named "Auto Cherry Pick" in our repository. Currently, this action cannot be > used because the repository has not enabled the permission to allow the > action to submit pr. We want to be able to enable this permission in the > repository. > > !https://user-images.githubusercontent.com/37237996/240861206-65885923-830e-47a3-866c-472f381267d6.jpeg! -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Closed] (INCUBATOR-271) SeaTunnel Incubator project request for the GitHub repositories moving service
[ https://issues.apache.org/jira/browse/INCUBATOR-271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Mclean closed INCUBATOR-271. --- Resolution: Won't Fix Moved to INFRA. > SeaTunnel Incubator project request for the GitHub repositories moving service > -- > > Key: INCUBATOR-271 > URL: https://issues.apache.org/jira/browse/INCUBATOR-271 > Project: Incubator > Issue Type: Task > Components: git >Reporter: Calvin Kirs >Assignee: Justin Mclean >Priority: Major > > The vote result of *Accept SeaTunnel into the Apache Incubator* can be found > here: > https://lists.apache.org/thread/70yywsx4r8y5o91twnp13s671q8j4dng > We have completed the submission and confirmation of SGA > Please help us to move the SeaTunnel repos: > https://github.com/InterestingLab/seatunnel to > https://github.com/apache/incubator-seatunnel > Deeply thanks for your help -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Assigned] (INCUBATOR-271) SeaTunnel Incubator project request for the GitHub repositories moving service
[ https://issues.apache.org/jira/browse/INCUBATOR-271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Mclean reassigned INCUBATOR-271: --- Assignee: Justin Mclean > SeaTunnel Incubator project request for the GitHub repositories moving service > -- > > Key: INCUBATOR-271 > URL: https://issues.apache.org/jira/browse/INCUBATOR-271 > Project: Incubator > Issue Type: Task > Components: git >Reporter: Calvin Kirs >Assignee: Justin Mclean >Priority: Major > > The vote result of *Accept SeaTunnel into the Apache Incubator* can be found > here: > https://lists.apache.org/thread/70yywsx4r8y5o91twnp13s671q8j4dng > We have completed the submission and confirmation of SGA > Please help us to move the SeaTunnel repos: > https://github.com/InterestingLab/seatunnel to > https://github.com/apache/incubator-seatunnel > Deeply thanks for your help -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Commented] (INCUBATOR-271) SeaTunnel Incubator project request for the GitHub repositories moving service
[ https://issues.apache.org/jira/browse/INCUBATOR-271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17464307#comment-17464307 ] Justin Mclean commented on INCUBATOR-271: - You'll need to raise an INFRA JIRA for this. > SeaTunnel Incubator project request for the GitHub repositories moving service > -- > > Key: INCUBATOR-271 > URL: https://issues.apache.org/jira/browse/INCUBATOR-271 > Project: Incubator > Issue Type: Task > Components: git >Reporter: Calvin Kirs >Priority: Major > > The vote result of *Accept SeaTunnel into the Apache Incubator* can be found > here: > https://lists.apache.org/thread/70yywsx4r8y5o91twnp13s671q8j4dng > We have completed the submission and confirmation of SGA > Please help us to move the SeaTunnel repos: > https://github.com/InterestingLab/seatunnel to > https://github.com/apache/incubator-seatunnel > Deeply thanks for your help -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Updated] (INCUBATOR-253) Issues with MXNet releases and their distribution
[ https://issues.apache.org/jira/browse/INCUBATOR-253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Mclean updated INCUBATOR-253: Attachment: (was: commons-logging-1.2-bin.tar.gz) > 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-10) Incubation_Policy.html should specify to use the Incubator PMC
[ https://issues.apache.org/jira/browse/INCUBATOR-10?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17315146#comment-17315146 ] Justin Mclean commented on INCUBATOR-10: There's probably a reason for this - i.e. What happened to the Jakarta project. Not that precludes other TLP being sponsors but we don't want umbrella projects. > Incubation_Policy.html should specify to use the Incubator PMC > -- > > Key: INCUBATOR-10 > URL: https://issues.apache.org/jira/browse/INCUBATOR-10 > Project: Incubator > Issue Type: Improvement > Components: site >Reporter: David Welton >Priority: Minor > > This page http://incubator.apache.org/incubation/Incubation_Policy.html > says: > "Approval by a Sponsor will generally occur only after a vote within the > Entity, and will require that the Entity be convinced that the Candidate is > appropriate for Incubation. A Sponsor may be one of: > * the Board of the Apache Software Foundation; > * a Top Level Project (TLP) within the Apache Software Foundation (where > the TLP considers the Candidate to be a suitable sub-project); or > * the Incubator PMC." > Although in practice it appears that the Incubator PMC is the preferred > sponsor for projects that would end up a TLP. The site could say something > like this: > Where a top level project is not an appropriate sponsor, the Incubator PMC is > the preferred sponsor. Requests should be sent to the general (AT) > incubator.apache.org mailing list. -- 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
[ https://issues.apache.org/jira/browse/INCUBATOR-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17258034#comment-17258034 ] Justin Mclean commented on INCUBATOR-253: - LEGAL-516 has been resolved it would be good to see a summary of what is still outstanding. > 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
[ https://issues.apache.org/jira/browse/INCUBATOR-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17173644#comment-17173644 ] Justin Mclean edited comment on INCUBATOR-253 at 8/8/20, 12:34 PM: --- That information doesn't belong there and as mentioned many times previously the board needs a short concise summary. You are also confusing ASF policy with licensing issues, and what 3rd parties ignore is not of relevance. I also see no mention of the Intel licensing issues. was (Author: jmclean): That information doesn't belong there and as mentioned many times previously the boards needs a short concise summary. You are also confusing ASF policy with licensing issues, what 3rd parties ignore is not of relevance. I also see no mention of the Intel licensing issues. > 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
[ https://issues.apache.org/jira/browse/INCUBATOR-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17173644#comment-17173644 ] Justin Mclean commented on INCUBATOR-253: - That information doesn't belong there and as mentioned many times previously the boards needs a short concise summary. You are also confusing ASF policy with licensing issues, what 3rd parties ignore is not of relevance. I also see no mention of the Intel licensing issues. > 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
[ https://issues.apache.org/jira/browse/INCUBATOR-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17165145#comment-17165145 ] Justin Mclean edited comment on INCUBATOR-253 at 7/26/20, 12:40 PM: It also seems that this code may have been released before the PPMC/IPMC vote is over see [1][2][3][4] There are also branding and trademark issue with this site [5] This is in addition to the issues previously noted with releases, branding and trademarks.[6] Thanks, Justin There seems to be more release, branding and trademark issues here: 15. https://sourceforge.net/projects/apache-mxnet.mirror/ 16. https://repo.gradle.org/gradle/simple/repo/ai/djl/mxnet/mxnet-native-mkl/1.7.0-b/ 17. https://mvnrepository.com/artifact/ai.djl.mxnet 18. https://aur.archlinux.org/packages/?O=0=nd=mxnet=v=d=50_Search=Go 19. https://djl.ai was (Author: jmclean): It also seems that this code may have been released before the PPMC/IPMC vote is over see [1][2][3][4] There are also branding and trademark issue with this site [5] This is in addition to the issues previously noted with releases, branding and trademarks.[6] Thanks, Justin There seem to be more release, branding and trademark issues here: 15. https://sourceforge.net/projects/apache-mxnet.mirror/ 16. https://repo.gradle.org/gradle/simple/repo/ai/djl/mxnet/mxnet-native-mkl/1.7.0-b/ 17. https://mvnrepository.com/artifact/ai.djl.mxnet 18. https://aur.archlinux.org/packages/?O=0=nd=mxnet=v=d=50_Search=Go 19. https://djl.ai > 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
[ https://issues.apache.org/jira/browse/INCUBATOR-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17165206#comment-17165206 ] Justin Mclean commented on INCUBATOR-253: - Other branding/trademark issues: 20. https://aws.amazon.com/marketplace/pp/NVIDIA-MXNet-by-NVIDIA/B07KLFW54D 21. https://aws.amazon.com/marketplace/pp/prodview-yex2xx5kgdhea?qid=1595741035764=0-1_=srh_res_product_title 22. https://aws.amazon.com/marketplace/pp/B07YW8HVLD?qid=1595741035764=0-4_=srh_res_product_title 23. https://aws.amazon.com/marketplace/search/results?x=0=0=%22MXNet > 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
[ https://issues.apache.org/jira/browse/INCUBATOR-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17165145#comment-17165145 ] Justin Mclean commented on INCUBATOR-253: - It also seems that this code may have been released before the PPMC/IPMC vote is over see [1][2][3][4] There are also branding and trademark issue with this site [5] This is in addition to the issues previously noted with releases, branding and trademarks.[6] Thanks, Justin There seem to be more release, branding and trademark issues here: 15. https://sourceforge.net/projects/apache-mxnet.mirror/ 16. https://repo.gradle.org/gradle/simple/repo/ai/djl/mxnet/mxnet-native-mkl/1.7.0-b/ 17. https://mvnrepository.com/artifact/ai.djl.mxnet 18. https://aur.archlinux.org/packages/?O=0=nd=mxnet=v=d=50_Search=Go 19. https://djl.ai > 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
[ https://issues.apache.org/jira/browse/INCUBATOR-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17156491#comment-17156491 ] Justin Mclean commented on INCUBATOR-253: - It's really going to depend on the details and intent. Basically just because it allowed doesn't mean you should do to avoid other aspects of ASF policy on releases. These 3rd party releases could also bring along with them an increased possible risk with licensing, security, user confusion who owns the project, damage to the ASF brand and and a number of other issues. They would also probably mean more work for the (P)PMC on managing it's brand. > 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
[ https://issues.apache.org/jira/browse/INCUBATOR-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17149898#comment-17149898 ] Justin Mclean commented on INCUBATOR-253: - A summary and a link to report would be better as a) the text may change before the board meeting and b) people would like a nice concise summary. If they need more detail they can go to the link. > 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
[ https://issues.apache.org/jira/browse/INCUBATOR-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17148268#comment-17148268 ] Justin Mclean commented on INCUBATOR-253: - Please refer to the conversation on your private 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.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] [Issue Comment Deleted] (INCUBATOR-253) Issues with MXNet releases and their distribution
[ https://issues.apache.org/jira/browse/INCUBATOR-253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Mclean updated INCUBATOR-253: Comment: was deleted (was: 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
[ https://issues.apache.org/jira/browse/INCUBATOR-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17142742#comment-17142742 ] Justin Mclean commented on INCUBATOR-253: - The incubator has every right to ask podlings to comply with ASF policy. ASF policy is on top of what the Apache License allows. The incubator also has the right to terminate a project if it doesn't comply with policy. See https://incubator.apache.org/policy/incubation.html#termination Again I suggest you read https://issues.apache.org/jira/browse/LEGAL-515 > 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
[ https://issues.apache.org/jira/browse/INCUBATOR-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17142473#comment-17142473 ] Justin Mclean commented on INCUBATOR-253: - See https://issues.apache.org/jira/browse/LEGAL-515 for more info, but in short if it a channel controlled by the (P)PMC then it would not be considered an 3rd party release. > 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
[ https://issues.apache.org/jira/browse/INCUBATOR-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17142464#comment-17142464 ] Justin Mclean commented on INCUBATOR-253: - 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. > 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
[ https://issues.apache.org/jira/browse/INCUBATOR-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17141602#comment-17141602 ] Justin Mclean commented on INCUBATOR-253: - In relation to 14 as it seems you already have a 3rd party that is making builds (although they need a little help/modification) would it not be better to work with them than creating the builds yourself? Here another page with branding/tradmark issues https://ngc.nvidia.com/catalog/containers/nvidia:mxnet > 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
[ https://issues.apache.org/jira/browse/INCUBATOR-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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: >
[jira] [Updated] (INCUBATOR-253) Issues with MXNet releases and their distribution
[ https://issues.apache.org/jira/browse/INCUBATOR-253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Mclean updated INCUBATOR-253: Description: 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. was: 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. > 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)
[jira] [Comment Edited] (INCUBATOR-253) Issues with MXNet releases and their distribution
[ https://issues.apache.org/jira/browse/INCUBATOR-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17141307#comment-17141307 ] Justin Mclean edited comment on INCUBATOR-253 at 6/21/20, 6:07 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 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 how 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. > 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)
[jira] [Commented] (INCUBATOR-253) Issues with MXNet releases and their distribution
[ https://issues.apache.org/jira/browse/INCUBATOR-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17141307#comment-17141307 ] Justin Mclean commented on INCUBATOR-253: - 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 how 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. > 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
[ https://issues.apache.org/jira/browse/INCUBATOR-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17141270#comment-17141270 ] Justin Mclean commented on INCUBATOR-253: - There are more issues mentioned above than in your GitHub issue. As this has been requested by the board please track progress here as the IPMC and board need visibility on progress, but you're welcome to track them internal as well. Some of these issues are very easily dealt with and could be resolved quickly. It's been serval months now since the project has been aware of most of these issues or could of taken it upon itself to fix them. > 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] [Updated] (INCUBATOR-253) Issues with MXNet releases and their distribution
[ https://issues.apache.org/jira/browse/INCUBATOR-253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Mclean updated INCUBATOR-253: Description: 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. was: 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 dent 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 from 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. > 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] [Updated] (INCUBATOR-253) Issues with MXNet releases and their distribution
[ https://issues.apache.org/jira/browse/INCUBATOR-253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Mclean updated INCUBATOR-253: Description: 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 dent 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 from 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. was: 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 dent 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 from public searchable https://repo.mxnet.io / https://dist.mxnet.io 12. Releases and other nightly builds on https://repo.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. > 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 dent 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 from 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] [Updated] (INCUBATOR-253) Issues with MXNet releases and their distribution
[ https://issues.apache.org/jira/browse/INCUBATOR-253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Mclean updated INCUBATOR-253: Description: 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 dent 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 from public searchable https://repo.mxnet.io / https://dist.mxnet.io 12. Releases and other nightly builds on https://repo.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. was: 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 dent 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 from public searchable https://repo.mxnet.io 12. Releases and other nightly builds on https://repo.mxnet.io containing category X licensed code. 13. Lack of clarity on all platforms for what is an ASF release and what is not. I may of missed something, if so please add it. > 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 dent 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 from public searchable https://repo.mxnet.io > / https://dist.mxnet.io > 12. Releases and other nightly builds on https://repo.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] [Created] (INCUBATOR-253) Issues with MXNet releases and their distribution
Justin Mclean created INCUBATOR-253: --- Summary: 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 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 dent 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 from public searchable https://repo.mxnet.io 12. Releases and other nightly builds on https://repo.mxnet.io containing category X licensed code. 13. Lack of clarity on all platforms for what is an ASF release and what is not. 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] [Resolved] (INCUBATOR-249) create cwiki home space for Apache APISIX
[ https://issues.apache.org/jira/browse/INCUBATOR-249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Mclean resolved INCUBATOR-249. - Resolution: Fixed has been created > create cwiki home space for Apache APISIX > - > > Key: INCUBATOR-249 > URL: https://issues.apache.org/jira/browse/INCUBATOR-249 > Project: Incubator > Issue Type: Task > Components: wiki >Reporter: Ming Wen >Priority: Major > > please create cwiki home space for Apache APISIX: > [https://cwiki.apache.org/confluence/display/APISIX] > thx. -- 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-204) Create a Creating Releases section
[ https://issues.apache.org/jira/browse/INCUBATOR-204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16881672#comment-16881672 ] Justin Mclean commented on INCUBATOR-204: - I see no issues with link to my incubator talks. I've been meaning to gather the links of incubator talks (not just mine) and put them somewhere useful for a while. > Create a Creating Releases section > -- > > Key: INCUBATOR-204 > URL: https://issues.apache.org/jira/browse/INCUBATOR-204 > Project: Incubator > Issue Type: Improvement > Components: guides >Reporter: John D. Ament >Priority: Major > > While we have a stripped down pointer to the ASF policy for releases, it > would be good to provide some knowledge share on how to create good releases. > - Can we link to Justin's videos? > - Can we point to examples on how to do this for common languages (Java, C++, > Python come to mind)? -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Updated] (INCUBATOR-204) Create a Creating Releases section
[ https://issues.apache.org/jira/browse/INCUBATOR-204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Mclean updated INCUBATOR-204: Attachment: (was: mobfox-audiences.csv) > Create a Creating Releases section > -- > > Key: INCUBATOR-204 > URL: https://issues.apache.org/jira/browse/INCUBATOR-204 > Project: Incubator > Issue Type: Improvement > Components: guides >Reporter: John D. Ament >Priority: Major > > While we have a stripped down pointer to the ASF policy for releases, it > would be good to provide some knowledge share on how to create good releases. > - Can we link to Justin's videos? > - Can we point to examples on how to do this for common languages (Java, C++, > Python come to mind)? -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Updated] (INCUBATOR-204) Create a Creating Releases section
[ https://issues.apache.org/jira/browse/INCUBATOR-204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Mclean updated INCUBATOR-204: Attachment: (was: epayments_card_fees_en.pdf) > Create a Creating Releases section > -- > > Key: INCUBATOR-204 > URL: https://issues.apache.org/jira/browse/INCUBATOR-204 > Project: Incubator > Issue Type: Improvement > Components: guides >Reporter: John D. Ament >Priority: Major > > While we have a stripped down pointer to the ASF policy for releases, it > would be good to provide some knowledge share on how to create good releases. > - Can we link to Justin's videos? > - Can we point to examples on how to do this for common languages (Java, C++, > Python come to mind)? -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Commented] (INCUBATOR-231) Cleanup Git-generated Incubator website
[ https://issues.apache.org/jira/browse/INCUBATOR-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16788384#comment-16788384 ] Justin Mclean commented on INCUBATOR-231: - I need to edit the file every month to fix up podlings that need to report monthly, and new puddings edit it to add them selves - both of these tasks wouldn't be too hard to generate rather than hand editing. I use an editor that understand and validates the XML so that reduces the risk of making errors. > Cleanup Git-generated Incubator website > --- > > Key: INCUBATOR-231 > URL: https://issues.apache.org/jira/browse/INCUBATOR-231 > Project: Incubator > Issue Type: Task >Reporter: Bertrand Delacretaz >Priority: Major > Attachments: clutch2data.txt, gitbox.clutch.data.txt, > gitbox.svn.diff.txt > > > [http://incubator.apache.org/] is generated from > [https://github.com/apache/incubator] but a few things (clutch, project > pages) are still maintained under > [http://svn.apache.org/repos/asf/incubator/public/trunk/] > We should cleanup and unify for consistency, and there's a number of folders > in svn that are not used anymore. Everything should move to Git to avoid > confusion. > Also, a lot of the projects information in the XML files found under > [http://svn.apache.org/repos/asf/incubator/public/trunk/content/projects/] is > duplicated in other places, LDAP, podlings websites etc - it would be good to > clean that up and simplify those pages to adapt to our current workflows, > while preserving history where it makes sense. > There are also YAML files with yet more duplicated information at > [http://svn.apache.org/repos/asf/incubator/public/trunk/content/podlings/] , > not sure if that's used or useful. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
