Re: [VOTE] Graduate Apache APISIX (incubating) as a TLP
+1 good luck On Tue, Jun 16, 2020 at 5:22 PM Ming Wen wrote: > Hello all, > > We've got positive feedback on the DISCUSS thread, I'd like to start > an official VOTE thread now. > > Please vote on the resolution pasted below to graduate Apache APISIX from > the > incubator to a Top Level Project. > > [ ] +1 Graduate Apache APISIX from the Incubator. > [ ] +0 > [ ] -1 Don't graduate Apache APISIX from the Incubator because ... > > This vote will open for at least 72 hours. > --- > > Establish the Apache APISIX Project > > WHEREAS, the Board of Directors deems it to be in the best interests of > the Foundation and consistent with the Foundation's purpose to establish > a Project Management Committee charged with the creation and maintenance > of open-source software, for distribution at no charge to the public, > related to Apache APISIX is a cloud-native microservices API gateway, > delivering the ultimate performance, security and scalable platform > for APIs and microservices... > > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee > (PMC), to be known as the "Apache APISIX Project", be and hereby > is established pursuant to Bylaws of the Foundation; and be it further > > RESOLVED, that the Apache APISIX Project be and hereby is > responsible for the creation and maintenance of software related to > Apache APISIX is a cloud-native microservices API gateway, > delivering the ultimate performance, security and scalable platform > for APIs and microservices; and be it further > > RESOLVED, that the office of "Vice President, Apache APISIX" be > and hereby is created, the person holding such office to serve at the > direction of the Board of Directors as the chair of the ApacheAPISIX > Project, and to have primary responsibility for > management of the projects within the scope of responsibility of the > Apache APISIX Project; and be it further > > RESOLVED, that the persons listed immediately below be and hereby are > appointed to serve as the initial members of the Apache APISIX Project: > * agile6v > * Ayeshmantha Perera > * Jarvis.Qiu > * jinwei > * junxu chen > * Justin Mclean > * Kevin Ratnasekera > * Lang Wang > * liling > * linsir > * Ming Wen > * Nirojan Selvanathan > * sheng wu > * spacewander > * Von Gosling > * Willem Ning Jiang > * yousa > * YuanSheng Wang > * Zhiyuan Ju > > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Ming Wen be appointed to > the office of Vice President, Apache APISIX, to serve in > accordance with and subject to the direction of the Board of Directors > and the Bylaws of the Foundation until death, resignation, retirement, > removal or disqualification, or until a successor is appointed; and be > it further > > RESOLVED, that the Apache APISIX Project be and hereby is tasked > with the migration and rationalization of the Apache IncubatorAPISIX > podling; and be it further > > RESOLVED, that all responsibilities pertaining to the Apache > IncubatorAPISIX podling encumbered upon the Apache Incubator PMC are > hereafter discharged. > > --- > > Thanks, > Ming Wen, Apache APISIX & Apache SkyWalking > Twitter: _WenMing >
Re: [VOTE] Accept Pegasus into the Apache incubation
Since my acceptance to mentor was implicit, I am an explicit +1 on this for Pegasus. -- Kevin A. McGrail Member, Apache Software Foundation Chair Emeritus Apache SpamAssassin Project https://www.linkedin.com/in/kmcgrail - 703.798.0171 On Thu, Jun 18, 2020 at 9:07 PM Ming Wen wrote: > +1 non-binding > Good luck. > > Thanks, > Ming Wen, Apache APISIX & Apache SkyWalking > Twitter: _WenMing > > > zhangli...@apache.org 于2020年6月19日周五 上午1:25写道: > > > Hi, > > +1 (not binding) and good luck. > > > > > > -- > > > > Liang Zhang (John) > > Apache ShardingSphere & Dubbo > > > > > > Furkan KAMACI 于2020年6月19日周五 上午12:42写道: > > > > > Hi, > > > > > > +1 (binding). > > > > > > Kind Regards, > > > Furkan KAMACI > > > > > > On Thu, Jun 18, 2020 at 2:55 PM Michael Wall > wrote: > > > > > > > Looks interesting, +1 (binding) > > > > > > > > On Thu, Jun 18, 2020 at 7:28 AM Yu Li wrote: > > > > > > > > > +1 (non-binding) > > > > > > > > > > Good luck! > > > > > > > > > > Best Regards, > > > > > Yu > > > > > > > > > > > > > > > On Thu, 18 Jun 2020 at 19:19, agile6v wrote: > > > > > > > > > > > +1 (non-binding) > > > > > > > > > > > > Good luck. > > > > > > > > > > > > On Tue, Jun 16, 2020 at 5:42 PM Tao Wu < > > > wutao.as.nevercha...@gmail.com > > > > > > > > > > > wrote: > > > > > > > > > > > > > Hi, > > > > > > > > > > > > > > After [the discussion of Pegasus proposal]( > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > https://lists.apache.org/thread.html/d2dc725389e1e6d0b525f85201c6219973a568ed075837601fd6bd0b%40%3Cgeneral.incubator.apache.org%3E > > > > > > > ), > > > > > > > I would like to call a vote to accept this project into the > > Apache > > > > > > > Incubator. > > > > > > > > > > > > > > The proposal is here: > > > > > > > > > > > > https://cwiki.apache.org/confluence/display/INCUBATOR/PegasusProposal > > > > > > > > > > > > > > Please cast your vote: > > > > > > > > > > > > > > [ ] +1, bring Pegasus into Incubator > > > > > > > [ ] +0, I don't care either way > > > > > > > [ ] -1, do not bring Pegasus into Incubator, because... > > > > > > > > > > > > > > The vote will open for at least 72 hours and only votes from > the > > > IPMC > > > > > > > members are considered binding, but other votes are welcome! > > > > > > > > > > > > > > Thanks, > > > > > > > Wu Tao > > > > > > > > > > > > > > > > > > > > > > > > > > > >
[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&focusedCommentId=17141262#comment-17141262 ] Sheng Zha commented on INCUBATOR-253: - Acknowledged. We have been tracking the efforts [https://github.com/apache/incubator-mxnet/issues/18397]. For now I will keep updating that issue until we are close to completion on this JIRA. We are making some progress but due to the complexity, the number of involved parties, slow turnaround with some of them, while trying to minimize the impact to our community while carrying out the changes, we expect that it would take some time before the items complete. Given that we are the only project in Apache we are aware of that invest heavily on GPU acceleration, which is in the blast radius, we also expect that some additional discussions need to be made. > Issues with MXNet releases and their distribution > - > > Key: INCUBATOR-253 > URL: https://issues.apache.org/jira/browse/INCUBATOR-253 > Project: Incubator > Issue Type: Improvement >Reporter: Justin Mclean >Assignee: Justin Mclean >Priority: Major > > The main issues are: > 1. Source and convenance binary releases containing Category X licensed code. > 2. Website giving access to downloads of non released/unapproved code. > 3. Website giving access to releases containing Category X licensed code. > 4. Web site doesn't given enough warning to users of the issues with non > (P)PMC releases or making it clear that these are not ASF releases. > 5. Maven releases containing Category X licensed code. > 6. PiPy releases containing Category X licensed code. > 7. Docker releases containing Category X licensed code. > 8 Docker releases containing unreleased/unapproved code. > 9. Trademark and branding issues with PiPy and Docker releases. > 10. Trademark and brand issues with naming of releases. > 11. Developer releases available to users and public searchable > https://repo.mxnet.io / https://dist.mxnet.io > 12. Releases and other nightly builds on https://repo.mxnet.io / > https://dist.mxnet.io containing category X licensed code. > 13. Lack of clarity on all platforms for what is an ASF release and what is > not. > For PiPy see: > https://pypi.org/project/mxnet/ > For Docker see: > https://hub.docker.com/u/mxnet > For web site pages see: > https://mxnet.apache.org/get_started? > https://mxnet.apache.org/get_started/download > I may of missed something, if so please add it. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Commented] (INCUBATOR-253) Issues with MXNet releases and their distribution
[ https://issues.apache.org/jira/browse/INCUBATOR-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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] [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&focusedCommentId=17141273#comment-17141273 ] Sheng Zha commented on INCUBATOR-253: - Yes, I'm aware and I am updating that issue to reflect them. Also, we obviously missed some issues and I want to make sure that this doesn't happen again, so it would be great if you could help link to the existing previous discussions on each of the issues you listed above so that we could conduct a retrospect. With respect to visibility to the board, I assume they can access the GitHub issues. Alternatively, I can paste back a weekly update on the status here. > Issues with MXNet releases and their distribution > - > > Key: INCUBATOR-253 > URL: https://issues.apache.org/jira/browse/INCUBATOR-253 > Project: Incubator > Issue Type: Improvement >Reporter: Justin Mclean >Assignee: Justin Mclean >Priority: Major > > The main issues are: > 1. Source and convenance binary releases containing Category X licensed code. > 2. Website giving access to downloads of non released/unapproved code. > 3. Website giving access to releases containing Category X licensed code. > 4. Web site doesn't given enough warning to users of the issues with non > (P)PMC releases or making it clear that these are not ASF releases. > 5. Maven releases containing Category X licensed code. > 6. PiPy releases containing Category X licensed code. > 7. Docker releases containing Category X licensed code. > 8 Docker releases containing unreleased/unapproved code. > 9. Trademark and branding issues with PiPy and Docker releases. > 10. Trademark and brand issues with naming of releases. > 11. Developer releases available to users and public searchable > https://repo.mxnet.io / https://dist.mxnet.io > 12. Releases and other nightly builds on https://repo.mxnet.io / > https://dist.mxnet.io containing category X licensed code. > 13. Lack of clarity on all platforms for what is an ASF release and what is > not. > For PiPy see: > https://pypi.org/project/mxnet/ > For Docker see: > https://hub.docker.com/u/mxnet > For web site pages see: > https://mxnet.apache.org/get_started? > https://mxnet.apache.org/get_started/download > I may of missed something, if so please add it. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Commented] (INCUBATOR-253) Issues with MXNet releases and their distribution
[ https://issues.apache.org/jira/browse/INCUBATOR-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17141275#comment-17141275 ] Sheng Zha commented on INCUBATOR-253: - # Source and convenance binary releases containing Category X licensed code. Which source files are you referring to? > Issues with MXNet releases and their distribution > - > > Key: INCUBATOR-253 > URL: https://issues.apache.org/jira/browse/INCUBATOR-253 > Project: Incubator > Issue Type: Improvement >Reporter: Justin Mclean >Assignee: Justin Mclean >Priority: Major > > The main issues are: > 1. Source and convenance binary releases containing Category X licensed code. > 2. Website giving access to downloads of non released/unapproved code. > 3. Website giving access to releases containing Category X licensed code. > 4. Web site doesn't given enough warning to users of the issues with non > (P)PMC releases or making it clear that these are not ASF releases. > 5. Maven releases containing Category X licensed code. > 6. PiPy releases containing Category X licensed code. > 7. Docker releases containing Category X licensed code. > 8 Docker releases containing unreleased/unapproved code. > 9. Trademark and branding issues with PiPy and Docker releases. > 10. Trademark and brand issues with naming of releases. > 11. Developer releases available to users and public searchable > https://repo.mxnet.io / https://dist.mxnet.io > 12. Releases and other nightly builds on https://repo.mxnet.io / > https://dist.mxnet.io containing category X licensed code. > 13. Lack of clarity on all platforms for what is an ASF release and what is > not. > For PiPy see: > https://pypi.org/project/mxnet/ > For Docker see: > https://hub.docker.com/u/mxnet > For web site pages see: > https://mxnet.apache.org/get_started? > https://mxnet.apache.org/get_started/download > I may of missed something, if so please add it. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Commented] (INCUBATOR-253) Issues with MXNet releases and their distribution
[ https://issues.apache.org/jira/browse/INCUBATOR-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17141276#comment-17141276 ] Sheng Zha commented on INCUBATOR-253: - 2. Website giving access to downloads of non released/unapproved code. 4. Web site doesn't given enough warning to users of the issues with non (P)PMC releases or making it clear that these are not ASF releases. 13. Lack of clarity on all platforms for what is an ASF release and what is not. These three items seem to refer to the same issue? > Issues with MXNet releases and their distribution > - > > Key: INCUBATOR-253 > URL: https://issues.apache.org/jira/browse/INCUBATOR-253 > Project: Incubator > Issue Type: Improvement >Reporter: Justin Mclean >Assignee: Justin Mclean >Priority: Major > > The main issues are: > 1. Source and convenance binary releases containing Category X licensed code. > 2. Website giving access to downloads of non released/unapproved code. > 3. Website giving access to releases containing Category X licensed code. > 4. Web site doesn't given enough warning to users of the issues with non > (P)PMC releases or making it clear that these are not ASF releases. > 5. Maven releases containing Category X licensed code. > 6. PiPy releases containing Category X licensed code. > 7. Docker releases containing Category X licensed code. > 8 Docker releases containing unreleased/unapproved code. > 9. Trademark and branding issues with PiPy and Docker releases. > 10. Trademark and brand issues with naming of releases. > 11. Developer releases available to users and public searchable > https://repo.mxnet.io / https://dist.mxnet.io > 12. Releases and other nightly builds on https://repo.mxnet.io / > https://dist.mxnet.io containing category X licensed code. > 13. Lack of clarity on all platforms for what is an ASF release and what is > not. > For PiPy see: > https://pypi.org/project/mxnet/ > For Docker see: > https://hub.docker.com/u/mxnet > For web site pages see: > https://mxnet.apache.org/get_started? > https://mxnet.apache.org/get_started/download > I may of missed something, if so please add it. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [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&focusedCommentId=17141273#comment-17141273 ] Sheng Zha edited comment on INCUBATOR-253 at 6/21/20, 3:18 AM: --- Yes, I'm aware and I am updating that issue to reflect them. Also, we obviously missed some issues and I want to make sure that this doesn't happen again, so it would be great if you could help link to the existing previous discussions on each of the issues you listed above so that we could conduct a retrospect. > It's been serval months now since the project has been aware of most of these > issues We just started realizing the issues as we recently initiate license reviews for binary release as part of https://issues.apache.org/jira/browse/LEGAL-515, https://issues.apache.org/jira/browse/LEGAL-516 both of which we initiated in May. Please don't make it sound as if it's intentional procrastination from us. With respect to visibility to the board, I assume they can access the GitHub issues. Alternatively, I can paste back a weekly update on the status here. was (Author: zhasheng): Yes, I'm aware and I am updating that issue to reflect them. Also, we obviously missed some issues and I want to make sure that this doesn't happen again, so it would be great if you could help link to the existing previous discussions on each of the issues you listed above so that we could conduct a retrospect. With respect to visibility to the board, I assume they can access the GitHub issues. Alternatively, I can paste back a weekly update on the status here. > Issues with MXNet releases and their distribution > - > > Key: INCUBATOR-253 > URL: https://issues.apache.org/jira/browse/INCUBATOR-253 > Project: Incubator > Issue Type: Improvement >Reporter: Justin Mclean >Assignee: Justin Mclean >Priority: Major > > The main issues are: > 1. Source and convenance binary releases containing Category X licensed code. > 2. Website giving access to downloads of non released/unapproved code. > 3. Website giving access to releases containing Category X licensed code. > 4. Web site doesn't given enough warning to users of the issues with non > (P)PMC releases or making it clear that these are not ASF releases. > 5. Maven releases containing Category X licensed code. > 6. PiPy releases containing Category X licensed code. > 7. Docker releases containing Category X licensed code. > 8 Docker releases containing unreleased/unapproved code. > 9. Trademark and branding issues with PiPy and Docker releases. > 10. Trademark and brand issues with naming of releases. > 11. Developer releases available to users and public searchable > https://repo.mxnet.io / https://dist.mxnet.io > 12. Releases and other nightly builds on https://repo.mxnet.io / > https://dist.mxnet.io containing category X licensed code. > 13. Lack of clarity on all platforms for what is an ASF release and what is > not. > For PiPy see: > https://pypi.org/project/mxnet/ > For Docker see: > https://hub.docker.com/u/mxnet > For web site pages see: > https://mxnet.apache.org/get_started? > https://mxnet.apache.org/get_started/download > I may of missed something, if so please add it. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Commented] (INCUBATOR-253) Issues with MXNet releases and their distribution
[ https://issues.apache.org/jira/browse/INCUBATOR-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17141279#comment-17141279 ] Sheng Zha commented on INCUBATOR-253: - 9. Trademark and branding issues with PiPy and Docker releases. 10. Trademark and brand issues with naming of releases. What binary releases other than the pypi and docker releases have trademark and branding issue? If none, I will consider these duplicates. > Issues with MXNet releases and their distribution > - > > Key: INCUBATOR-253 > URL: https://issues.apache.org/jira/browse/INCUBATOR-253 > Project: Incubator > Issue Type: Improvement >Reporter: Justin Mclean >Assignee: Justin Mclean >Priority: Major > > The main issues are: > 1. Source and convenance binary releases containing Category X licensed code. > 2. Website giving access to downloads of non released/unapproved code. > 3. Website giving access to releases containing Category X licensed code. > 4. Web site doesn't given enough warning to users of the issues with non > (P)PMC releases or making it clear that these are not ASF releases. > 5. Maven releases containing Category X licensed code. > 6. PiPy releases containing Category X licensed code. > 7. Docker releases containing Category X licensed code. > 8 Docker releases containing unreleased/unapproved code. > 9. Trademark and branding issues with PiPy and Docker releases. > 10. Trademark and brand issues with naming of releases. > 11. Developer releases available to users and public searchable > https://repo.mxnet.io / https://dist.mxnet.io > 12. Releases and other nightly builds on https://repo.mxnet.io / > https://dist.mxnet.io containing category X licensed code. > 13. Lack of clarity on all platforms for what is an ASF release and what is > not. > For PiPy see: > https://pypi.org/project/mxnet/ > For Docker see: > https://hub.docker.com/u/mxnet > For web site pages see: > https://mxnet.apache.org/get_started? > https://mxnet.apache.org/get_started/download > I may of missed something, if so please add it. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [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&focusedCommentId=17141280#comment-17141280 ] Sheng Zha commented on INCUBATOR-253: - 7. Docker releases containing Category X licensed code. 8 Docker releases containing unreleased/unapproved code. What's an example of our docker release that contains unreleased/unapproved code that doesn't fall into the category X license? If none, I will consider these duplicates. > Issues with MXNet releases and their distribution > - > > Key: INCUBATOR-253 > URL: https://issues.apache.org/jira/browse/INCUBATOR-253 > Project: Incubator > Issue Type: Improvement >Reporter: Justin Mclean >Assignee: Justin Mclean >Priority: Major > > The main issues are: > 1. Source and convenance binary releases containing Category X licensed code. > 2. Website giving access to downloads of non released/unapproved code. > 3. Website giving access to releases containing Category X licensed code. > 4. Web site doesn't given enough warning to users of the issues with non > (P)PMC releases or making it clear that these are not ASF releases. > 5. Maven releases containing Category X licensed code. > 6. PiPy releases containing Category X licensed code. > 7. Docker releases containing Category X licensed code. > 8 Docker releases containing unreleased/unapproved code. > 9. Trademark and branding issues with PiPy and Docker releases. > 10. Trademark and brand issues with naming of releases. > 11. Developer releases available to users and public searchable > https://repo.mxnet.io / https://dist.mxnet.io > 12. Releases and other nightly builds on https://repo.mxnet.io / > https://dist.mxnet.io containing category X licensed code. > 13. Lack of clarity on all platforms for what is an ASF release and what is > not. > For PiPy see: > https://pypi.org/project/mxnet/ > For Docker see: > https://hub.docker.com/u/mxnet > For web site pages see: > https://mxnet.apache.org/get_started? > https://mxnet.apache.org/get_started/download > I may of missed something, if so please add it. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Commented] (INCUBATOR-253) Issues with MXNet releases and their distribution
[ https://issues.apache.org/jira/browse/INCUBATOR-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17141284#comment-17141284 ] Sheng Zha commented on INCUBATOR-253: - 12. Releases and other nightly builds on [https://repo.mxnet.io|https://repo.mxnet.io/] / [https://dist.mxnet.io|https://dist.mxnet.io/] containing category X licensed code. We only have nightly builds on these websites and all binaries on these websites are for development and testing purposes. There is no "Releases" and we have never advertised that people should install convenience binaries of official releases from these websites. I believe nightly builds are allowed to have category X licensed code and thus I'm not sure if this item is a valid issue. > Issues with MXNet releases and their distribution > - > > Key: INCUBATOR-253 > URL: https://issues.apache.org/jira/browse/INCUBATOR-253 > Project: Incubator > Issue Type: Improvement >Reporter: Justin Mclean >Assignee: Justin Mclean >Priority: Major > > The main issues are: > 1. Source and convenance binary releases containing Category X licensed code. > 2. Website giving access to downloads of non released/unapproved code. > 3. Website giving access to releases containing Category X licensed code. > 4. Web site doesn't given enough warning to users of the issues with non > (P)PMC releases or making it clear that these are not ASF releases. > 5. Maven releases containing Category X licensed code. > 6. PiPy releases containing Category X licensed code. > 7. Docker releases containing Category X licensed code. > 8 Docker releases containing unreleased/unapproved code. > 9. Trademark and branding issues with PiPy and Docker releases. > 10. Trademark and brand issues with naming of releases. > 11. Developer releases available to users and public searchable > https://repo.mxnet.io / https://dist.mxnet.io > 12. Releases and other nightly builds on https://repo.mxnet.io / > https://dist.mxnet.io containing category X licensed code. > 13. Lack of clarity on all platforms for what is an ASF release and what is > not. > For PiPy see: > https://pypi.org/project/mxnet/ > For Docker see: > https://hub.docker.com/u/mxnet > For web site pages see: > https://mxnet.apache.org/get_started? > https://mxnet.apache.org/get_started/download > I may of missed something, if so please add it. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Commented] (INCUBATOR-253) Issues with MXNet releases and their distribution
[ https://issues.apache.org/jira/browse/INCUBATOR-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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] [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&focusedCommentId=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#8
[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)