[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=17195126#comment-17195126 ] Sheng Zha commented on INCUBATOR-253: - Summary (WIP) 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. 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 vote was put on hold for addressing the branding issues in third-party releases and for an IP clearance process. 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 from 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://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. Reference links [1]: https://issues.apache.org/jira/browse/INFRA-20442 [2]: https://issues.apache.org/jira/browse/LEGAL-516 [3]: https://sourceforge.net/projects/apache-mxnet.mirror/ [4]:
[Result] [VOTE] Graduate Apache IoTDB as TLP
Hi all, VOTE for graduation Apache IoTDB (incubating) has passed with 8 binding +1 votes and 9 non-binding +1 votes. Vote thread: https://lists.apache.org/thread.html/r3107fdf8de94a5e62a889fe71a05cff929ca6eda44253dc34c0e7035%40%3Cgeneral.incubator.apache.org%3E Binding vote: - Christofer Dutz - Julian Feinauer - William Jiang - Kevin Ratnasekera - Sheng Wu - Kevin A. McGrail - Tianqi Chen - Ted Liu Non-binding vote: - Jialin Qiao - Ming Wen - Dominik Riemer - Dawei Liu - Patrick Wiener - Zhongyi Tan - William Guo - Zesong Sun - Xiangdong Huang Thank you all for your participation in the vote. We'll submit the resolution to the board. Best, -- Xiangdong Huang On behalf of Apache IoTDB (incubating) PPMC
回覆：Re: [VOTE] Graduate Apache IoTDB as TLP
+1 (binding) Ted Liu 在 2020 年 9月 月 11 日週五，時間：23:47 ， Tianqi Chen 寫道： +1 (binding) TQ On Fri, Sep 11, 2020 at 7:49 AM Kevin A. McGrail wrote: > I vote +1 (binding). KAM > > On 9/10/2020 3:42 AM, Xiangdong Huang wrote: > > Dear all IPMCs: > > > > Following discussions with great support from our mentors, > > committers and community members. > > I would like to call for a formal VOTE for graduating Apache IoTDB > > (Incubating), > > as a Top Level Project. > > > > This is a formal voting thread about Apache IoTDB's graduation, please > Vote: > > [X] +1 - Recommend graduation of Apache IoTDB as a TLP > > [ ] 0 > > [ ] -1 - Do not recommend the graduation of Apache IoTDB because... > > > > The VOTE will open for at least 72 hours. > > > > Apache IoTDB (Incubating) entered the incubator in Nov 2018, the > community > > has grown vibrantly since, with all the design, development happening on > > the Apache infrastructure, the "Apache Way". > > > > To list a few of the community's achievements, > > > > - Apache IoTDB name search has been approved > > - Accepted > 1300 PRs from 75 contributors > > - Migrated developer conversations to the list at d...@iotdb.apache.org > > (more than 3000 mails, without JIRA notifications, and gitbox, are sent > > by more than 160 persons) > > - There are 9 versions (3 major versions) released successfully > conformant > > to Apache release policy by 5 release managers; > > - Invited 12 new committers (all of them accepted) > > - invited 4 of those new committers to join the PMC (all of them > accepted) > > - Our proposed PMC is diverse and consists of members from more than 10 > > organizations > > > > Preparations and discussions history about the graduation: > > > > - The maturity assessment is done [2], > > - The community agreed on starting the graduation process in a formal > vote > > [3] (result see [4]). > > And, I'd like to note that all our mentors also participated in the vote > > with a positive vote! > > - The community also decided about a suggestion for the initial VP, a > > charter [5, 6] and the initial PMC list [7]. > > - We also received positive feedback from the incubator general mailing > > list [8]. > > > > > > The draft of the resolution: > > > > Establish the Apache IoTDB 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 an IoT native database with high > performance > > for data management and analysis, on the edge and the cloud. > > > > NOW, THEREFORE, BE IT RESOLVED, that a Project Management > > Committee (PMC), to be known as the "Apache IoTDB Project", > > be and hereby is established pursuant to Bylaws of the > > Foundation; and be it further > > > > RESOLVED, that the Apache IoTDB Project be and hereby is > > responsible for the creation and maintenance of software > > related to an IoT native database with high performance > > for data management and analysis, on the edge and the cloud. > > and be it further > > > > RESOLVED, that the office of "Vice President, Apache IoTDB 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 Apache IoTDB Project, and to have primary responsibility > > for management of the projects within the scope of > > responsibility of the Apache IoTDB 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 IoTDB Project: > > > > * Chen Wang > > * Christofer Dutz > > * Dawei Liu > > * Gaofei Cao > > * Haonan Hou > > * Jialin Qiao > > * Jianmin Wang > > * Jincheng Sun > > * Jinrui Zhang > > * Julian Feinauer > > * Jun Yuan > > * Justin Mclean > > * Kevin A. McGrail > > * Kun Liu > > * Lei Rui > > * Rong Kang > > * Rui Liu > > * Shuo Zhang > > * Stefanie Zhao > > * Tian Jiang > > * Tianan Li > > * Willem Ning Jiang > > * Xiangdong Huang > > > > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Xiangdong Huang > > be appointed to the office of Vice President, Apache IoTDB, 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
