FWD: [VOTE] graduate Apache Superset from the Apache Incubator
FYI - we just started a VOTE to graduate Apache Superset from the Apache Incubator (!!!) -- Forwarded message - From: Maxime Beauchemin Date: Tue, Sep 15, 2020 at 5:46 PM Subject: [VOTE] graduate Apache Superset from the Apache Incubator To: Hi all! Over the past few months/years, the Apache Superset community has met all the requirements to graduate from the Apache Incubator. Given that, I believe we are ready for graduation and I'm excited to kick off the process with a community vote at this time. For the record, we have been incubating since 2017-05-02, have had 8 official Apache-approved releases, and have voted in 20 PMC members and 11 committers. See our Incubation Status File for more details: https://incubator.apache.org/projects/superset.html For reference, you can find out everything you need to know about the graduation requirements and process here: https://incubator.apache.org/guides/graduation.html Consider this an implicit +1 from me. Cheers! Max
[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=17195126#comment-17195126 ] Sheng Zha edited comment on INCUBATOR-253 at 9/15/20, 9:35 PM: --- *Summary* The PPMC continues to make progress in resolving license and branding issues. During the a recent release vote on 1.7.0, with the help from Justin, a few more source distribution and branding issues were found. Here is the status on the issues, tracked in INCUBATOR-253. As of now, the PPMC resolved 15 issues, with 9 still left. Most of the outstanding issues hinge on one key outstanding question, which is whether the components in MXNet that are produced by CUDA NVCC constitutes Category X code. PPMC member employed by Nvidia helped connect Nvidia's representatives including Michael O'Connor, Director of Deep Learning, who have been supportive in the efforts of clarification. Progress is tracked in LEGAL-516. At the moment, NVIDIA's legal is actively exploring options on resolving this issue. Michael requested extension with MXNet PPMC to not treat the related component as Category-X and delay actions until Oct. board meeting. Also note that there was confusion around MXNet's status around integration with Intel products. In MXNet, there has never been public distribution of MXNet where MKL was included. There was an initial inquiry around whether MKL builds can be enabled but was rejected, so this never came into practice. Also, to my knowledge Intel has not produced custom MXNet builds with closed-source components. MXNet 1.7.0 release has completed. So far, PPMC members from Intel (Tao), Nvidia (Dick), and Amazon (Leonard, Henri, Qing, Sheng) have acted to help resolve the issues. *Status on open issues since last update:* 1. Source and convenance binary releases containing Category X licensed code. (pending) * Source code releases by the PPMC do not contain Category X code, no issue. Takedown of binary releases by the PPMC on repository.apache.org is on hold, see item 5. PyPI releases are made by third-party. See item 8. 5. Maven releases containing Category X licensed code. (pending) * Takedown of binary releases on repository.apache.org initiated [1]. The scope depends on the resolution of LEGAL-516 [2]. 6. PyPI releases containing Category X licensed code. (pending) * There are no official PyPI releases. Whether the third-party releases are compliant with branding guidelines depend on the resolution of LEGAL-516. 7. Docker releases containing Category X licensed code. (pending) * There are no official Docker releases. Whether the third-party releases are compliant with branding guidelines depend on the resolution of LEGAL-516. 9. Trademark and branding issues with PyPI and Docker releases. (pending) * There are no official PyPI or Docker releases. In addition, as they all contain binary from unmodified MXNet code, whether they are compliant in branding now solely depends on whether they contain Category X licensed code. Refer to item 6, 7. 10. Trademark and brand issues with naming of releases. (pending) * There are no binary releases by the PPMC besides the repository.apache.org releases in item 5. 12. Releases and other nightly builds on [https://repo.mxnet.io|https://repo.mxnet.io/] / [https://dist.mxnet.io|https://dist.mxnet.io/] containing Category X licensed code (resolved) * Neither of the two site contains releases. The binaries are only intended for testing pipelines and are made available only to MXNet developers. As part of the effort to resolve branding concern, public references to these sites are deleted [4]. 14. to 23. Branding and release of 3rd parties containing unreleased code. (pending) Known pages with issues: * [https://docs.nvidia.com/deeplearning/frameworks/mxnet-release-notes/rel_20-03.html] (item 14, pending) PPMC reached out to Nvidia. Pending action from Nvidia on branding compliance and replying on whether unreleased code was included. [https://sourceforge.net/projects/apache-mxnet.mirror/] (item 15, resolved) * PPMC reached out to SourceForge. SourceForge added (incubating) in name. As 1.7.0 release has completed, we removed release candidate tag from GitHub and the the mirror automatically deleted the it [3]. As such, the original issue is resolved. The PPMC will follow up with SourceForge on the functionality of filtering out non-release tags. AWS Marketplace related links [https://aws.amazon.com/marketplace/pp/B07YW8HVLD?qid=1595741035764=0-4_=srh_res_product_title] (item 22, pending) * PPMC reached out to Bitnami directly regarding this listing [5]. Bitnami responded and is working on the branding issues. [https://aws.amazon.com/marketplace/search/results?x=0=0=%22MXNet] (item 23, pending) * PPMC reached out to AWS through internal channel to fix branding issue. Will update in the next few
[jira] [Comment Edited] (INCUBATOR-253) Issues with MXNet releases and their distribution
[ https://issues.apache.org/jira/browse/INCUBATOR-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17195126#comment-17195126 ] Sheng Zha edited comment on INCUBATOR-253 at 9/15/20, 9:34 PM: --- *Summary* The PPMC continues to make progress in resolving license and branding issues. During the a recent release vote on 1.7.0, with the help from Justin, a few more source distribution and branding issues were found. Here is the status on the issues, tracked in INCUBATOR-253. As of now, the PPMC resolved 15 issues, with 9 still left. Most of the outstanding issues hinge on one key outstanding question, which is whether the components in MXNet that are produced by CUDA NVCC constitutes Category X code. PPMC member employed by Nvidia helped connect Nvidia's representatives including Michael O'Connor, Director of Deep Learning, who have been supportive in the efforts of clarification. Progress is tracked in LEGAL-516. At the moment, NVIDIA's legal is actively exploring options on resolving this issue. Michael requested extension with MXNet PPMC to not treat the related component as Category-X and delay actions until Oct. board meeting. Also note that there was confusion around MXNet's status around integration with Intel products. In MXNet, there has never been public distribution of MXNet where MKL was included. There was an initial inquiry around whether MKL builds can be enabled but was rejected, so this never came into practice. Also, to my knowledge Intel has not produced custom MXNet builds with closed-source components. MXNet 1.7.0 release has completed. So far, PPMC members from Intel (Tao), Nvidia (Dick), and Amazon (Leonard, Henri, Qing, Sheng) have acted to help resolve the issues. *Status on open issues since last update:* 1. Source and convenance binary releases containing Category X licensed code. (pending) * Source code releases by the PPMC do not contain Category X code, no issue. Takedown of binary releases by the PPMC on repository.apache.org is on hold, see item 5. PyPI releases are made by third-party. See item 8. 5. Maven releases containing Category X licensed code. (pending) * Takedown of binary releases on repository.apache.org initiated [1]. The scope depends on the resolution of LEGAL-516 [2]. 6. PyPI releases containing Category X licensed code. (pending) * There are no official PyPI releases. Whether the third-party releases are compliant with branding guidelines depend on the resolution of LEGAL-516. 7. Docker releases containing Category X licensed code. (pending) * There are no official Docker releases. Whether the third-party releases are compliant with branding guidelines depend on the resolution of LEGAL-516. 9. Trademark and branding issues with PyPI and Docker releases. (pending) * There are no official PyPI or Docker releases. In addition, as they all contain binary from unmodified MXNet code, whether they are compliant in branding now solely depends on whether they contain Category X licensed code. Refer to item 6, 7. 10. Trademark and brand issues with naming of releases. (pending) * There are no binary releases by the PPMC besides the repository.apache.org releases in item 5. 12. Releases and other nightly builds on [https://repo.mxnet.io|https://repo.mxnet.io/] / [https://dist.mxnet.io|https://dist.mxnet.io/] containing Category X licensed code (resolved) * Neither of the two site contains releases. The binaries are only intended for testing pipelines and are made available only to MXNet developers. As part of the effort to resolve branding concern, public references to these sites are deleted [4]. 14. to 23. Branding and release of 3rd parties containing unreleased code. (pending) Known pages with issues: * [https://docs.nvidia.com/deeplearning/frameworks/mxnet-release-notes/rel_20-03.html] (item 14, pending) PPMC reached out to Nvidia. Pending action from Nvidia on branding compliance and replying on whether unreleased code was included. [https://sourceforge.net/projects/apache-mxnet.mirror/] (item 15, resolved) * PPMC reached out to SourceForge. SourceForge added (incubating) in name. As 1.7.0 release has completed, we removed release candidate tag from GitHub and the the mirror automatically deleted the it [3]. As such, the original issue is resolved. The PPMC will follow up with SourceForge on the functionality of filtering out non-release tags. AWS Marketplace related links [https://aws.amazon.com/marketplace/pp/B07YW8HVLD?qid=1595741035764=0-4_=srh_res_product_title] (item 22, pending) * PPMC reached out to Bitnami directly regarding this listing [5]. Pending reply. [https://aws.amazon.com/marketplace/search/results?x=0=0=%22MXNet] (item 23, pending) * PPMC reached out to AWS through internal channel to fix branding issue. Will update in the next few days. In addition, MXNet PPMC identified
Re: [RESULT] [VOTE] Release Apache Superset (incubating) version 0.37.1
(Reposting with correct subject as per guidelines) Thanks to everyone that participated. The vote to release Apache Superset (incubating) version 0.37.1 is now closed. The vote PASSED with 3 binding +1, 2 non binding +1 and 0 -1 votes: Binding votes: - Felix - Jim - Willem Non binding votes: - Max - Aditya We will work to complete the release process. Thanks, The Apache Superset (Incubating) Team > On 15. Sep 2020, at 10.02, Ville Brofeldt wrote: > > Thanks to everyone that participated. The vote to release > Apache Superset (incubating) version 0.37.1 is now closed. > > The vote PASSED with 3 binding +1, 2 non binding +1 and 0 -1 votes: > > Binding votes: > - Felix > - Jim > - Willem > > Non binding votes: > - Max > - Aditya > > We will work to complete the release process. > > Thanks, > The Apache Superset (Incubating) Team smime.p7s Description: S/MIME cryptographic signature
Re: [VOTE] Release Apache Superset (incubating) version 0.37.1
Thanks to everyone that participated. The vote to release Apache Superset (incubating) version 0.37.1 is now closed. The vote PASSED with 3 binding +1, 2 non binding +1 and 0 -1 votes: Binding votes: - Felix - Jim - Willem Non binding votes: - Max - Aditya We will work to complete the release process. Thanks, The Apache Superset (Incubating) Team > On 15. Sep 2020, at 9.56, Willem Jiang wrote: > > +1 （binding) > I checked > 1. Incubating in name > 2. Download links are valid. > 3. Checksums and PGP signatures are valid. > 4. DISCLAIMER included. > 5. LICENSE and NOTICE are fine > 6. License headers > 7. No unexpected binary files > > Willem Jiang > > Twitter: willemjiang > Weibo: 姜宁willem > > > On Wed, Sep 9, 2020 at 11:37 PM Ville Brofeldt > wrote: >> >> Hello IPMC, >> >> The Apache Superset (incubating) community has voted on and approved a >> proposal to >> release Apache Superset (incubating) version 0.37.1. >> The voting thread can be found here: >> https://lists.apache.org/thread.html/r4462440505c3eea8fbfdbad76575d29a6ce23e7fb575d45a66a1e946%40%3Cdev.superset.apache.org%3E >> >> We now kindly request the Incubator PMC members review and vote on this >> incubator release. >> >> Apache Superset (incubating) is a modern, enterprise-ready business >> intelligence web application >> >> The release candidate: >> https://dist.apache.org/repos/dist/dev/incubator/superset/0.37.1rc1/ >> >> Git tag for the release: >> https://github.com/apache/incubator-superset/tree/0.37.1rc1 >> >> The Change Log for the release: >> https://github.com/apache/incubator-superset/blob/0.37.1rc1/CHANGELOG.md >> >> public keys are available at: >> https://www.apache.org/dist/incubator/superset/KEYS >> >> The vote will be open for at least 72 hours or until the necessary number >> of votes are reached. >> >> Please vote accordingly: >> >> [ ] +1 approve >> [ ] +0 no opinion >> [ ] -1 disapprove with the reason >> >> Thanks, >> The Apache Superset (Incubating) Team > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > smime.p7s Description: S/MIME cryptographic signature
Re: [VOTE] Release Apache Superset (incubating) version 0.37.1
+1 （binding) I checked 1. Incubating in name 2. Download links are valid. 3. Checksums and PGP signatures are valid. 4. DISCLAIMER included. 5. LICENSE and NOTICE are fine 6. License headers 7. No unexpected binary files Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Wed, Sep 9, 2020 at 11:37 PM Ville Brofeldt wrote: > > Hello IPMC, > > The Apache Superset (incubating) community has voted on and approved a > proposal to > release Apache Superset (incubating) version 0.37.1. > The voting thread can be found here: > https://lists.apache.org/thread.html/r4462440505c3eea8fbfdbad76575d29a6ce23e7fb575d45a66a1e946%40%3Cdev.superset.apache.org%3E > > We now kindly request the Incubator PMC members review and vote on this > incubator release. > > Apache Superset (incubating) is a modern, enterprise-ready business > intelligence web application > > The release candidate: > https://dist.apache.org/repos/dist/dev/incubator/superset/0.37.1rc1/ > > Git tag for the release: > https://github.com/apache/incubator-superset/tree/0.37.1rc1 > > The Change Log for the release: > https://github.com/apache/incubator-superset/blob/0.37.1rc1/CHANGELOG.md > > public keys are available at: > https://www.apache.org/dist/incubator/superset/KEYS > > The vote will be open for at least 72 hours or until the necessary number > of votes are reached. > > Please vote accordingly: > > [ ] +1 approve > [ ] +0 no opinion > [ ] -1 disapprove with the reason > > Thanks, > The Apache Superset (Incubating) Team - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache Superset (incubating) version 0.37.1
+1 (non-binding) Checked 1. Incubating in name 2. Download links are valid. 3. Checksums and PGP signatures are valid. 4. DISCLAIMER included. 5. LICENSE and NOTICE are fine 6. License headers 7. No unexpected binary files Thanks and Regards, Aditya Sharma On Tue, 15 Sep 2020 at 10:16, Maxime Beauchemin wrote: > +1 (non-binding at the IPCM level) > > and a *gentle ping* as I believe we need an extra vote from an IPMC for us > to publish the release (!) > > On Wed, Sep 9, 2020 at 1:02 PM Felix Cheung > wrote: > > > +1 > > > > - incubating in name > > - signature and hash fine > > - DISCLAIMER is fine > > - LICENSE and NOTICE are fine > > - No unexpected binary files > > - All source files have ASF headers > > > > > > On Wed, Sep 9, 2020 at 8:37 AM Ville Brofeldt < > ville.v.brofe...@gmail.com> > > wrote: > > > > > Hello IPMC, > > > > > > The Apache Superset (incubating) community has voted on and approved a > > > proposal to > > > release Apache Superset (incubating) version 0.37.1. > > > The voting thread can be found here: > > > > > > https://lists.apache.org/thread.html/r4462440505c3eea8fbfdbad76575d29a6ce23e7fb575d45a66a1e946%40%3Cdev.superset.apache.org%3E > > > < > > > https://lists.apache.org/thread.html/r4462440505c3eea8fbfdbad76575d29a6ce23e7fb575d45a66a1e946@%3Cdev.superset.apache.org%3E > > > > > > > > > We now kindly request the Incubator PMC members review and vote on this > > > incubator release. > > > > > > Apache Superset (incubating) is a modern, enterprise-ready business > > > intelligence web application > > > > > > The release candidate: > > > https://dist.apache.org/repos/dist/dev/incubator/superset/0.37.1rc1/ > > > > > > Git tag for the release: > > > https://github.com/apache/incubator-superset/tree/0.37.1rc1 > > > > > > The Change Log for the release: > > > > https://github.com/apache/incubator-superset/blob/0.37.1rc1/CHANGELOG.md > > > > > > public keys are available at: > > > https://www.apache.org/dist/incubator/superset/KEYS > > > > > > The vote will be open for at least 72 hours or until the necessary > number > > > of votes are reached. > > > > > > Please vote accordingly: > > > > > > [ ] +1 approve > > > [ ] +0 no opinion > > > [ ] -1 disapprove with the reason > > > > > > Thanks, > > > The Apache Superset (Incubating) Team > > > > > >
