Re: [DISCUSS] Incubating Proposal for OzHera
After reading these responses, I feel that this project is not ready to enter the Apache Incubator, especially considering that you have received support from 6 mentors and communicated with them. There is no magic in the Apache incubator. Don't expect the incubator will make your project international and successful. For example, I noticed the issues were all in Chinese, and no one reviewed PRs before merged. Thanks, Ming Wen, Apache APISIX PMC Chair Twitter: _WenMing Zhiyong Zhang 于2023年9月5日周二 22:33写道： > > > On 2023/09/05 05:56:51 Sheng Wu wrote: > > Several important things > > The entire project https://github.com/XiaoMi/mone has passed the internal > audit of Xiaomi, and the owners and leaders of the entire project are > consistent with the initiators of the ozhera project. The main donation to > ASF this time is ozhera-all, and other modules follow the Apache protocol, > which will not cause protocol or ownership ambiguity. > > 1. You are mentioning the donation is about > > `https://github.com/XiaoMi/mone/tree/master/ozhera-all` > <https://github.com/XiaoMi/mone/tree/master/ozhera-all>, It is a part > > of the repository, so will others stay out of the ASF? If so, have the > > project been going through Xiaomi's internal audit about the sharing > > codes between this part of the whole project? Who owns that? > > We hope to complete the internationalization transformation with the help > of ASF; we are preparing the English documents, and a version will be > completed by tomorrow; > > 2. I can't see any English document for the project. Is the community > > for a global foundation incubating journey? > > The user interface currently only has Chinese, and the > internationalization of the page requires a longer time to iterate, but we > will complete the transformation of this function in the early stage of > incubation; > > 3. More importantly, all screenshots and UIs are only in Chinese as well? > > a.We have received full support from Xiaomi's legal affairs and are able > to submit the SGA; > b.The project has gradually recruited partners outside of Xiaomi, and the > initial committers from Xiaomi are also actively participating in the > construction of other open source communities. These are a group of > partners who are passionate about open source. I believe that this group of > partners can continue the project in the long term. > > 4. Have Xiaomi Inc. agreed on this? Will they submit a SGA? Are the > > initial committers still working on Xiaomi and going to continue work > > this project? Will Xiaomi permit their CCLAs? > > We have checked in advance, and we hope to do the replacement and upgrade > during the future incubation period. > > 5. I can see several incompatible licenses of dependencies existing, > > including GPLs. Do you have plans to remove or replace them? Have you > > worked with your mentors to go through licenses of dependencies check? > > There is a relatively clear division of labor among the mentors, and the > mentors will regularly assign us corresponding tasks. Through efficient > project collaboration, we ensure the activity of the community; > At the same time, we can gain more experience and guidance from multiple > mentors, which will further promote the positive cycle development of the > community. > > 6. Why a 10 people PPMC initial team has a mentor team of 6 people? > > Typically, I don't think this is a good practice. Instead, mentors are > > most likely counting on others and will become inactive. > > I hope that ozhera can play its value in the observability of cloud-native > applications. Many components in ozhera (Opentelemetry, Grafana, > Prometheus, MQ, etc.) come from the open source community. We hope to feed > back our experience in the field of application observation to the > community through this platform. The UI design will actively embrace open > source like the backend, but we hope to implement mature solutions from the > community for chart display, currently it is Grafana. > > 7. How would you process the branding? Including you are sharing UI > > design. I have concerns this would be another issues with the main > > project. > > a. We have chosen MySQL and Elasticsearch as the project's storage > solutions based on their excellent performance in their respective fields. > The versions we have chosen strictly comply with the GPL and Apache2.0 > agreements. > b. While Elasticsearch has changed from Apache 2.0 to the Server Side > Public License (SSPL), although SSPL is no longer an OSI-approved open > source license, it still allows free use, modification, and distribution, > but imposes some restrictions on commercial use. > c. We are also wo
Re: [VOTE] graduate Apache Doris (Incubating) as a Top Level Project
+1 binding good luck Thanks, Ming Wen, Apache APISIX PMC Chair Twitter: _WenMing Wang Weibing 于2022年4月24日周日 13:54写道： > +1 (non binding) > > I think the Doris Community have done a good job! > > Weibing Wang > from Apache bRPC Community > > On 2022/04/24 02:25:46 陈明雨 wrote: > > Dear Incubator Community, > > > > After having the discussion in Doris community[1][2], we have passed the > community vote[3]. > > > > And then made a discussion in general@incubator[4]. We got a lot of > positive responses. > > > > And have responded and addressed all suggestions and comments raised. > > > > > > > > > > I would like to start this voting thread to request graduating the Doris > project from the incubator as a TLP. > > > > Please provide your vote as one of the following options: > > > > > > > > > > [ ] +1 - Recommend graduation of Apache Doris as a TLP > > > > [ ] 0 - I don't feel strongly about it, but don't object > > > > [ ] -1 - Do not recommend the graduation of Apache Doris because… > > > > > > > > > > The VOTE will remain open for at least 72 hours. > > > > > > > > > > The following is a brief overview of the progress of the Doris project > and community since entering the incubator: > > > > 1. Community > > > > - 9 new PPMC members were added, from five different companies, bringing > the total number of PPMC members to 22. > > > > - 20 new Committers were added (including the new PPMC members), > bringing the total number of Committers to 33. > > > > - The number of Contributors is now 305 and growing[5]. > > > > - The dev@doris mailing list currently has 328 subscribers, and all > major project discussions are happening in the dev@doris. > > > > > > > > > > 2. Project > > > > - 7 releases by 6 release managers. All compliance issues have been > resolved. > > > > - Doris official website[6] is compliant with Apache Foundation > requirements[7]. > > > > - Project maturity model is detailed in [8]. > > > > - See Doris Project Incubation Status[9] for more info. > > > > > > > > > > [1] https://lists.apache.org/thread/90fd2pd3r6wgn4hnfdo3rd0wqkv23cgr > > > > [2] https://lists.apache.org/thread/xc5qj7m2k1ph0mc97otj0nf8vskdfrzv > > > > [3] https://lists.apache.org/thread/9yklv4vbp39jhrzbcx3qgpcs1osk3lyf > > > > [4] https://lists.apache.org/thread/nbncjl8fdq0bcjop6l4747c8x9c06q00 > > > > [5] https://github.com/apache/incubator-doris > > > > [6] http://doris.incubator.apache.org/ > > > > [7] https://whimsy.apache.org/pods/project/doris > > > > [8] > https://cwiki.apache.org/confluence/display/DORIS/Maturity+Assessment+for+Doris > > > > [9] https://incubator.apache.org/projects/doris.html > > > > > > > > > > > == > > > > Establish the Apache Doris 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 a MPP-based interactive SQL data warehousing for reporting > > > > and analysis. > > > > > > > > > > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee > > > > (PMC), to be known as the "Apache Doris Project", be and hereby is > > > > established pursuant to Bylaws of the Foundation; and be it further > > > > > > > > > > RESOLVED, that the Apache Doris Project be and hereby is responsible for > > > > the creation and maintenance of software related to a MPP-based > > > > interactive SQL data warehousing for reporting and analysis; and be it > > > > further > > > > > > > > > > RESOLVED, that the office of "Vice President, Apache Doris" 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 Doris > > > > Project, and to have primary responsibility for management of the > > > > projects within the scope of responsibility of the Apache Doris Project; > > >
Re: [DISCUSS] Graduate Apache Doris (Incubating) as TLP
As Doris' mentor, I have seen Doris' efforts in protecting and solving brand issues; during the incubation process, Doris released multiple Apache releases and attracted many new committers. I think Doris is ready to graduate, good luck:) Thanks, Ming Wen, Apache APISIX PMC Chair Twitter: _WenMing Juan Pan 于2022年4月20日周三 14:47写道： > Hello, > > > [1] shows me the efforts and commitments from Doris community. More PMCs, > committers, contributors joined; More releases are available under the > supervising and guiding of the committee. Hope it’s better and my support > for this discussion. > > > [1] https://incubator.apache.org/clutch/doris.html > > -- > Trista Pan > Twitter & Github: tristaZero > > > > > On 04/10/2022 23:50，陈明雨 wrote： > Dear Incubator Community, > > After a discussion[1][2] and vote[3] with the community, we believe Apache > Doris (Incubating) is ready for graduation to a TLP, and we'd like to make > a discussion with the IPMC. > > Doris is an MPP-based interactive SQL data warehousing for reporting and > analysis and entering the incubator in Sep, 2018. > > The following is a brief overview of the progress of the Doris project and > community since entering the incubator: > > 1. Community > > - 9 new PPMC members were added, from five different companies, bringing > the total number of PPMC members to 22. > > - 20 new Committers were added (including the new PPMC members), bringing > the total number of Committers to 33. > > - The number of Contributors is now 289 and growing[4]. > > - The dev@doris mailing list currently has 328 subscribers, and all major > project discussions are happening in the dev@doris. > > 2. Project > > - 7 releases by 6 release managers. All compliance issues have been > resolved. > > - Doris official website[5] is compliant with Apache Foundation > requirements[6]. > > - Project maturity model is detailed in [7]. > > - We have also created a pre-graduation Check List[8] following the Apache > official website guidelines and are currently moving forward. > > - See Doris Project Incubation Status[9] for more info > > > > > [1] https://lists.apache.org/thread/90fd2pd3r6wgn4hnfdo3rd0wqkv23cgr > > [2] https://lists.apache.org/thread/xc5qj7m2k1ph0mc97otj0nf8vskdfrzv > > [3] https://lists.apache.org/thread/9yklv4vbp39jhrzbcx3qgpcs1osk3lyf > > [4] https://github.com/apache/incubator-doris > > [5] http://doris.incubator.apache.org/ > > [6] https://whimsy.apache.org/pods/project/doris > > [7] > https://cwiki.apache.org/confluence/display/DORIS/Maturity+Assessment+for+Doris > > [8] > https://cwiki.apache.org/confluence/display/DORIS/Graduation+Check+List > > [9] https://incubator.apache.org/projects/doris.html > > > > > Please see the proposed board resolution below and let us know what you > think. > > The discussion will remain open for at least 72 hours. > > > - > > Establish the Apache Doris 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 a MPP-based interactive SQL data warehousing for reporting > > and analysis. > > > > > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee > > (PMC), to be known as the "Apache Doris Project", be and hereby is > > established pursuant to Bylaws of the Foundation; and be it further > > > > > RESOLVED, that the Apache Doris Project be and hereby is responsible for > > the creation and maintenance of software related to a MPP-based > > interactive SQL data warehousing for reporting and analysis; and be it > > further > > > > > RESOLVED, that the office of "Vice President, Apache Doris" 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 Doris > > Project, and to have primary responsibility for management of the > > projects within the scope of responsibility of the Apache Doris 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 Doris Project: > > > > > * Bin Ling > > * Bo Wang
Re: Re: Re: Re: [VOTE] Vote for releasing Apache Doris 1.0.0-incubating-rc03
+1 binding I checked: - All the download links work. - The License and Notice files are in the source file. - The incubating disclaim in the source file. Thanks, Ming Wen, Apache APISIX PMC Chair Twitter: _WenMing 陈明雨 于2022年4月16日周六 14:16写道： > Oh, I see, thanks you! > We will modify it in next relaese. > > -- > > 此致！Best Regards > 陈明雨 Mingyu Chen > > Email: > chenmin...@apache.org > > > > > > At 2022-04-16 13:59:47, "li gang" wrote: > >Hi, Mingyu,if iceberg NOTICE is not standard NOTICE file,I think it's > >necessary to modify it. > > > >The Apache standard NOTICE could be removed in the NOTICE, > > > >Such as the following text,if they are the ASF products,they can be > removed > >to reduce the NOTICE file. > > > > > >``` > > > > > >= > > > > Notice file for: spark-core_2.12-2.4.6 > > > >= > > > > > > > >Spark Project Core > > > >Copyright 2020 The Apache Software Foundation > > > > > >This product includes software developed at > > > >The Apache Software Foundation (http://www.apache.org/). > > > >= > > > > Notice file for: httpcore-4.4.15 > > > >= > > > > > > > >Apache HttpCore > > > >Copyright 2005-2021 The Apache Software Foundation > > > > > >This product includes software developed at > > > >The Apache Software Foundation (http://www.apache.org/). > > > >``` > > > > > > > >陈明雨 于2022年4月16日周六 13:06写道： > > > >> Hi Li, > >> Thanks for your suggestion. I have read the content of [1] and it said: > >> > >> > >> > though the ASF copyright line and any other portions of NOTICE must be > >> considered for propagation. > >> > >> > >> For example, the NOTICE file of iceberg[2], I found that the only > content > >> that I can remove is: > >> > >> > >> > This product includes software developed at > >> > The Apache Software Foundation (http://www.apache.org/). > >> > >> > >> Am I right? > >> > >> > >> [1] https://infra.apache.org/licensing-howto.html#bundle-asf-product > >> [2] https://github.com/apache/iceberg/blob/master/NOTICE > >> > >> > >> > >> > >> -- > >> > >> 此致！Best Regards > >> 陈明雨 Mingyu Chen > >> > >> Email: > >> chenmin...@apache.org > >> > >> > >> > >> > >> > >> 在 2022-04-16 12:47:08，"li gang" 写道： > >> >Hi Mingyu,you can review the content of [1],it introduces how to reduce > >> the > >> >notice file, Netty is not asf product,so it can't be removed,I checked > the > >> >NOTICE-dist.txt under the binary package,Such as Iceberg and spark,they > >> are > >> >ASF products and the notice of them are standard notice,I suggest to > >> remove > >> >them to reduce the notice file. > >> >1. https://infra.apache.org/licensing-howto.html#bundle-asf-product > >> > > >> >陈明雨 于2022年4月15日周五 15:11写道： > >> > > >> >> Thanks for your vote! > >> >> >1、Suggest to reduce the notice file,It is not necessary to duplicate > >> the > >> >> >line "This product includes software developed at the Apache > Software > >> >> >Foundation...". > >> >> We discussed this issue before, because these licenses are > referenced in > >> >> some third-party libraries' own NOTICE files (such as Netty). > >> >> If we delete them, then we need to modify the contents of the > >> third-party > >> >> NOTICE files, otherwise invalid file references will be generated. > So we > >> >> chose to keep these files containing the APLv2 protocol as is. > >> >> > >> >> -- > >> >> > >> >> 此致！Best Regards > >> >> 陈明雨 Mingyu Chen > >> >> > >> >> Email: > >> >> chenmin...@apache.org > >> >> > >> >> > >> >> > >> >> > >> >> > >> >> 在 2022-04-14 13:21:36，"li gang" 写道： > >> >>
Re: [VOTE] Release Flink Connectors v1.0.3 for Apache Doris(Incubating)
+1 binding I checked: - the signature and sha512 are correct - the LICENSE file and NOTICE file are there - incubating in the source file Thanks, Ming Wen, Apache APISIX PMC Chair Twitter: _WenMing Zhang Yonglun 于2022年3月15日周二 14:26写道： > Hi, > > +1 (non binding) > > I checked: > - incubating in name > - signatures and hashes are fine > - Disclaimer exists > - LICENSE and NOTICE exist > - No unexpected binary files > > -- > > Zhang Yonglun > Apache ShenYu (Incubating) > Apache ShardingSphere > > 陈明雨 于2022年3月11日周五 21:27写道： > > > > Hi All, > > This is a call for vote to release Flink Connectors v1.0.3 for Apache > Doris(Incubating). > > There are 4 outputs for different Flink versions: > > > > - apache-doris-flink-connector-1.11_2.12-1.0.3-incubating > > - apache-doris-flink-connector-1.12_2.12-1.0.3-incubating > > - apache-doris-flink-connector-1.13_2.12-1.0.3-incubating > > - apache-doris-flink-connector-1.14_2.12-1.0.3-incubating > > > > This is the first version of flink connector, we have just moved the > code from[1] to [2]. > > > > Vote result at dev@doris: > > https://lists.apache.org/thread/2khyom5d16mpldkyh398vz1bb7wvfwgp > > > > The release candidates: > > > > > https://dist.apache.org/repos/dist/dev/incubator/doris/flink-connector/1.0.3/ > > Maven 2 staging repository: > > > https://repository.apache.org/content/repositories/orgapachedoris-1007/org/apache/doris/flink-doris-connector-1.11_2.12/1.0.3/ > > > https://repository.apache.org/content/repositories/orgapachedoris-1007/org/apache/doris/flink-doris-connector-1.12_2.12/1.0.3/ > > > https://repository.apache.org/content/repositories/orgapachedoris-1007/org/apache/doris/flink-doris-connector-1.13_2.12/1.0.3/ > > > https://repository.apache.org/content/repositories/orgapachedoris-1007/org/apache/doris/flink-doris-connector-1.14_2.12/1.0.3/ > > > > Git tag for the release: > > > https://github.com/apache/incubator-doris-flink-connector/tree/1.11_2.12-1.0.3 > > > https://github.com/apache/incubator-doris-flink-connector/tree/1.12_2.12-1.0.3 > > > https://github.com/apache/incubator-doris-flink-connector/tree/1.13_2.12-1.0.3 > > > https://github.com/apache/incubator-doris-flink-connector/tree/1.14_2.12-1.0.3 > > > > Keys to verify the Release Candidate: > > https://downloads.apache.org/incubator/doris/KEYS > > > > Look at here for how to verify this release candidate: > > > http://doris.incubator.apache.org/community/release-and-verify/release-verify.html > > > > The vote will be open for at least 72 hours or until necessary number of > votes are reached. > > Please vote accordingly: > > [ ] +1 approve > > [ ] +0 no opinion > > [ ] -1 disapprove with the reason > > > > [1] https://github.com/apache/incubator-doris > > [2] https://github.com/apache/incubator-doris-flink-connector > > > > -- > > > > 此致！Best Regards > > 陈明雨 Mingyu Chen > > > > Email: > > chenmin...@apache.org > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [VOTE] Release Spark Connectors v1.0.1 for Apache Doris(Incubating)
+1 binding I checked: - the signature and sha512 are correct - the LICENSE file and NOTICE file are there - incubating in the source file BTW, the title in the Gmail thread is `[Result][VOTE]`, so I ignored this email Thanks, Ming Wen, Apache APISIX PMC Chair Twitter: _WenMing ShaoFeng Shi 于2022年3月15日周二 10:27写道： > +1 (binding) > > Checked: > - the signature and sha512 are correct > - the LICENSE file and NOTICE file are there > - 'mvn clean package' and 'mvn test' get success > > Best regards, > > Shaofeng Shi 史少锋 > Apache Kylin PMC, > Apache Incubator PMC, > Email: shaofeng...@apache.org > > Apache Kylin FAQ: https://kylin.apache.org/docs/gettingstarted/faq.html > Join Kylin user mail group: user-subscr...@kylin.apache.org > Join Kylin dev mail group: dev-subscr...@kylin.apache.org > > > > > 陈明雨 于2022年3月11日周五 21:25写道： > > > Hi All, > > > > > > > > > > This is a call for vote to release Spark Connectors v1.0.1 for Apache > > Doris(Incubating). > > And this is the first release of spark-doris-connector, we just move the > > code base from [1] to [2]. > > > > There are 2 outputs for different Spark and Scala version: > > > > > > > > > > - apache-doris-spark-connector-2.3_2.11-1.0.1-incubating > > > > - apache-doris-spark-connector-3.1_2.12-1.0.1-incubating > > > > > > > > Vote Result at dev@doris: > > https://lists.apache.org/thread/2lcl515n359ffpkf8vtdfykl19low022 > > > > > > > > The release candidates: > > > > > > > https://dist.apache.org/repos/dist/dev/incubator/doris/spark-connector/1.0.1/ > > > > > > > > > > Maven 2 staging repository: > > > > > > > https://repository.apache.org/content/repositories/orgapachedoris-1007/org/apache/doris/spark-doris-connector-2.3_2.11/1.0.1/ > > > > > https://repository.apache.org/content/repositories/orgapachedoris-1007/org/apache/doris/spark-doris-connector-3.1_2.12/1.0.1/ > > > > > > > > > > Git tag for the release: > > > > > > > https://github.com/apache/incubator-doris-spark-connector/releases/tag/2.3_2.11-1.0.1 > > > > > > > https://github.com/apache/incubator-doris-spark-connector/releases/tag/3.1_2.12-1.0.1 > > > > > > > > > > Keys to verify the Release Candidate: > > > > https://downloads.apache.org/incubator/doris/KEYS > > > > > > > > > > Look at here for how to verify this release candidate: > > > > > > > http://doris.incubator.apache.org/community/release-and-verify/release-verify.html > > > > > > > > > > The vote will be open for at least 72 hours or until necessary number of > > votes are reached. > > > > Please vote accordingly: > > > > > > > > [ ] +1 approve > > > > [ ] +0 no opinion > > > > [ ] -1 disapprove with the reason > > > > > > > > [1] https://github.com/apache/incubator-doris > > [2] https://github.com/apache/incubator-doris-spark-connector > > > > -- > > > > 此致！Best Regards > > 陈明雨 Mingyu Chen > > > > Email: > > chenmin...@apache.org >
Re: [VOTE] Release Apache Doris 0.15.0-incubating-rc04
+1 binding I checked, - incubating in name. - Download links. - Checksum and signature. - the License and Notice file. - all ASF files have ASF headers. Thanks, Ming Wen, Apache APISIX PMC Chair Twitter: _WenMing Craig Russell 于2021年11月28日周日 上午1:58写道： > Hi Mingyu, > > > > On Nov 27, 2021, at 12:09 AM, 陈明雨 wrote: > > > > Hi Shaofeng: > > Thanks for your vote. > > > > > > And dear Incubator PMC, we are still looking for one more vote! Thank > you! > > > Have you asked your mentors for their votes? > > Warm regards, > Craig > > > > > 此致！Best Regards > > 陈明雨 Mingyu Chen > > > > Email: > > morning...@163.com; > > morningman@gmail.com > > > > > > > > > > > > 在 2021-11-26 14:47:01，"ShaoFeng Shi" 写道： > >> +1 binding > >> > >> I checked the source package, License, Notice, signature, etc. Looks > good > >> to me. > >> > >> Just one question, when will the Doris community switch to JIRA for > issue > >> tracking and release management? > >> > >> Best regards, > >> > >> Shaofeng Shi 史少锋 > >> Apache Kylin PMC, > >> Apache Incubator PMC, > >> Email: shaofeng...@apache.org > >> > >> Apache Kylin FAQ: https://kylin.apache.org/docs/gettingstarted/faq.html > >> Join Kylin user mail group: user-subscr...@kylin.apache.org > >> Join Kylin dev mail group: dev-subscr...@kylin.apache.org > >> > >> > >> > >> > >> 陈明雨 于2021年11月24日周三 下午10:24写道： > >> > >>> Hi Willem, > >>> Thanks for your review! > >>> > >>> > >>> > >>> > >>> -- > >>> > >>> 此致！Best Regards > >>> 陈明雨 Mingyu Chen > >>> > >>> Email: > >>> chenmin...@apache.org > >>> > >>> > >>> > >>> > >>> > >>> 在 2021-11-24 09:10:53，"Willem Jiang" 写道： > >>>> +1 bing > >>>> > >>>> I checked, > >>>> > >>>> - incubating in name > >>>> > >>>> - signed key and checksum. > >>>> > >>>> - the License and Notice file. > >>>> > >>>> - There is no binary file in the source Kit. > >>>> > >>>> - all ASF files have ASF headers > >>>> > >>>> - I didn’t compile the code in Mac OSX > >>>> > >>>> > >>>> Willem Jiang > >>>> > >>>> Twitter: willemjiang > >>>> Weibo: 姜宁willem > >>>> > >>>> On Mon, Nov 22, 2021 at 5:25 PM 陈明雨 wrote: > >>>>> > >>>>> Hi all, > >>>>> > >>>>> > >>>>> > >>>>> > >>>>> Please review and vote on Apache Doris 0.15.0-incubating-rc04 > release. > >>>>> > >>>>> > >>>>> > >>>>> > >>>>> Apache Doris is an MPP-based interactive SQL data warehousing for > >>> reporting and analysis. The official website is: > >>>>> http://doris.incubator.apache.org/ > >>>>> > >>>>> > >>>>> > >>>>> > >>>>> The Apache Doris community has voted on and approved this release: > >>>>> > >>>>> > >>> > https://lists.apache.org/thread.html/d70f7c8a8ae448bf6680a15914646005c6483564464cfa15f4ddc2fc@%3Cdev.doris.apache.org%3E > >>>>> > >>>>> > >>>>> > >>>>> > >>>>> The vote result email thread: > >>>>> > >>>>> https://lists.apache.org/thread/lhnp6fnfddzc44hm1wmo2x5sqpp2by4k > >>>>> > >>>>> > >>>>> > >>>>> > >>>>> The release candidate has been tagged in GitHub as 0.15.0-rc04, > >>> available here: > >>>>> > >>>>> https://github.com/apache/incubator-doris/tree/0.15.0-rc04 > >>>>> > >>>>> > >>>>> > >>>>> > >>>>> Thanks to everyone who has contributed to this release, and the > CHANGE > >>> LOG can be found here: > >>>>> > >>>>> https://github.com/apache/incubator-doris/issues
Re: [DISCUSS] Incubating Proposal of Kyuubi
You can see the trend chart from https://www.apiseven.com/zh/contributor-graph?chart=contributorMonthlyActivity=NetEase/kyuubi Ming Wen 于2021年6月6日 周日上午7:28写道： > hi, Kent, > > From 2018 to 2020, kuyybi is not an active project, most of the time there > is only one contributor per month. But in 2021, there will be 8 active > contributors every month. What is the reason for this? > > Willem Jiang 于2021年6月3日 周四下午12:53写道： > >> I think we can revisit the PPMC part and have more discussion with the >> initial committers. >> It's a good chance to let them know better about how to run an open >> source project in Apache Way. >> >> >> Willem Jiang >> >> Twitter: willemjiang >> Weibo: 姜宁willem >> >> On Thu, Jun 3, 2021 at 11:52 AM Atri Sharma wrote: >> > >> > I would like to hear from Kyuubi's mentors on the topic before reaching >> a >> > conclusion. >> > >> > On Thu, 3 Jun 2021, 05:40 Sheng Wu, wrote: >> > >> > > Kent >> > > >> > > Thanks. >> > > The proposal is generally better this time. >> > > >> > > If your initial committers and your mentors agree, you are ready to >> embrace >> > > the ASF culture, I am good with that. >> > > Just from my experience, your community looks a little too young, like >> > > Atri's concern, which is reasonable. >> > > But I would like to trust you and your mentors' judgment and >> determination. >> > > >> > > Sheng Wu 吴晟 >> > > Twitter, wusheng1108 >> > > >> > > >> > > Kent Yao 于2021年6月3日周四 上午12:54写道： >> > > >> > > > Hi Sheng, >> > > > >> > > > Truly sorry for the format issue. >> > > > >> > > > Please trust me I did not mean to hurt anybody and push any >> contributor >> > > > away. We drafted this proposal together based on the New Podling >> > > Proposal. >> > > > We never tried to use PPMC and committer to measure whose >> contribution is >> > > > higher. This mistake has been fixed in the proposal. >> > > > >> > > > About releases, we will follow >> > > > https://www.apache.org/legal/release-policy.html and the guide of >> our >> > > > mentors. We will also take the initiative to learn other documents. >> > > > >> > > > > This is not a block, the point I mentioned this is, you will need >> more >> > > > people. >> > > > >> > > > We will keep working on this. >> > > > >> > > > Bests, >> > > > >> > > > Kent Yao >> > > > >> > > > >> > > > Sheng Wu 于2021年6月2日周三 下午10:53写道： >> > > > >> > > > > Hi Kent >> > > > > >> > > > > Thanks for replying, but to be honest, your mail format is chaos. >> > > > > Take a look at bellowing, which is what I saw in the gmail. >> > > > > >> > > > > This may be an issue of your mail client or some else. >> > > > > >> > > > > > The current #.2 - 5 top >> > > > > > contributors will stay as committers, and they will join the >> PPMC >> > > > during >> > > > > > incubation. >> > > > > >> > > > > PPMC usually is the default for all initial committers, >> considering >> > > your >> > > > > community is still small and not very active. >> > > > > You should invite all people you trusted to join, rather than >> pushing >> > > > them >> > > > > away. >> > > > > This is not just a too-high bar issue. Excluding 4 out of 5 is >> strange. >> > > > > I can't guess what is the root cause, why the other 4 PPMC members >> > > don't >> > > > > touch codes but are trusted completely. Meanwhile, people with >> easily >> > > > > measurable code contributions are just as committers? >> > > > > We(ASF) always remind the community to recognize no-code >> contribution, >> > > > but >> > > > > in this case, it seems the opposite? Don't recognize code >> contributors >> > > > > enough? >> > > > > Please reach your mentors, this seems not a typical ASF style. If >
Re: [DISCUSS] Incubating Proposal of Kyuubi
> > > > > > > > Thanks for your interest and +1 for Kyuubi. > > > > > > > > > > > > > > > > > > > > > > Not being very familiar with Dremel, I just took a > quick > > > look > > > > > at > > > > > > > the > > > > > > > > > > > profile of a very similar and exciting project, Apache > > > Drill. > > > > > If > > > > > > I > > > > > > > > > > > understand correctly, Kyuubi is built on top of the > compute > > > > > layer > > > > > > > > > > > (Apache Spark), while Apache Drill is built on top of > the > > > > > storage > > > > > > > > > > > layer. > > > > > > > > > > > > > > > > > > > > > > Apache Spark has a large user base and usage scenarios > all > > > > over > > > > > > the > > > > > > > > > > > world. When users have some basic Spark programming and > > > > tuning > > > > > > > > skills, > > > > > > > > > > > things are easy for them. But many times, most users > do not > > > > > have > > > > > > > all > > > > > > > > > > > of these abilities when they use Spark directly or > > > > indirectly. > > > > > We > > > > > > > > want > > > > > > > > > > > to build a more easy-to-use platform on top of it to > help > > > > these > > > > > > > > users. > > > > > > > > > > > On the one hand, we will work on the interface layer to > > > make > > > > it > > > > > > > easy > > > > > > > > > > > to access (of course, this effort will make our project > > > look > > > > > very > > > > > > > > > > > similar to other projects, such as HiveServer2). On the > > > other > > > > > > hand, > > > > > > > > we > > > > > > > > > > > will work under Kyuubi's multi-tenant architecture to > > > extend > > > > > our > > > > > > > > > > > on-prem Spark SQL engine(a.k.a Kyuubi engine) to make > it > > > more > > > > > > > stable > > > > > > > > > > > and efficient in our scenario. > > > > > > > > > > > > > > > > > > > > > > What's more, we are going to add more on-prem Kyuubi > engine > > > > > > types, > > > > > > > > e.g. > > > > > > > > > > > Flink. > > > > > > > > > > > > > > > > > > > > > > Alexander Alten 于2021年5月31日周一 > 下午2:35写道： > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Hey, > > > > > > > > > > > > > > > > > > > > > > > > Looks like an interesting project, competition to > > > > Starburst. > > > > > > How > > > > > > > > > does it > > > > > > > > > > > > compare to Apache Dremel? > > > > > > > > > > > > > > > > > > > > > > > > +1 (non-binding) for incubation. > > > > > > > > > > > > > > > > > > > > > > > > Thanks and stay safe, > > > > > > > > > > > > --alex > > > > > > > > > > > > > > > > > > > > > > > > On Mon, May 31, 2021, 08:21 Kent Yao > > > > > wrote: > > > > > > > > > > > > > > > > > > > > > > > > > Dear all, > > > > > > > > > > > > > > > > > > > > > > > > > > We want to propose Kyuubi as a new Apache Incubator > > > > > project. > > > > > > > > > > > > > > > > > > > > > > > > > > Kyuubi is a distributed multi-tenant Thrift > JDBC/ODBC > > > > > server > > > > > > > for > > > > > > > > > > > > > large-scale data management, processing, and > analytics, > > > > > built > > > > > > > on > > > > > > > > > top > > > > > > > > > > > > > of Apache Spark and designed to support more > engines > > > > (i.e., > > > > > > > > Apache > > > > > > > > > > > > > Flink). We are aiming to make Kyuubi an > > > "out-of-the-box" > > > > > tool > > > > > > > for > > > > > > > > > data > > > > > > > > > > > > > warehouses and data lakes. Kyuubi concentrates on > > > > improving > > > > > > the > > > > > > > > > > > > > experience for non-Spark users, making it easy for > them > > > > to > > > > > > use > > > > > > > > > Spark > > > > > > > > > > > > > as a service and focus on business data of their > own, > > > not > > > > > > where > > > > > > > > it > > > > > > > > > > > > > stores, how it computes. NetEase has open-sourced > > > Kyuubi > > > > > > since > > > > > > > > > 2018, > > > > > > > > > > > > > https://github.com/NetEase/kyuubi. > > > > > > > > > > > > > > > > > > > > > > > > > > Many thanks to Willem Jiang (Champion), Jeff > Zhang, Duo > > > > > > Zhang, > > > > > > > > > Akira > > > > > > > > > > > > > Ajisaka for being the mentors of the Kyuubi > project and > > > > > > helping > > > > > > > > us > > > > > > > > > set > > > > > > > > > > > > > up this proposal. The proposal can be found at > > > > > > > > > > > > > > > > > > > > > > > > > > > > https://cwiki.apache.org/confluence/display/INCUBATOR/KyuubiProposal > > > > > > . > > > > > > > > > > > > > > > > > > > > > > > > > > Looking forward to your feedback and thank you very > > > much. > > > > > > > > > > > > > > > > > > > > > > > > > > Best regards, > > > > > > > > > > > > > Kent Yao > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > - > > > > > > > > > > > > > To unsubscribe, e-mail: > > > > > > > general-unsubscr...@incubator.apache.org > > > > > > > > > > > > > For additional commands, e-mail: > > > > > > > > general-h...@incubator.apache.org > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > > > > > > > > > > > > > > > > Kent Yao > > > > > > > > > > > @ Data Science Center, Hangzhou Research Institute, > NetEase > > > > > Corp. > > > > > > > > > > > a spark enthusiast > > > > > > > > > > > kyuubiis a unified multi-tenant JDBC interface for > > > > large-scale > > > > > > data > > > > > > > > > > > processing and analytics, built on top of Apache Spark. > > > > > > > > > > > > > > > > > > > > > > spark-authorizerA Spark SQL extension which provides > SQL > > > > > Standard > > > > > > > > > > > Authorization for Apache Spark. > > > > > > > > > > > spark-postgres A library for reading data from and > > > > transferring > > > > > > > data > > > > > > > > > > > to Postgres / Greenplum with Spark SQL and DataFrames, > > > > 10~100x > > > > > > > > faster. > > > > > > > > > > > itatchiA library that brings useful functions from > various > > > > > modern > > > > > > > > > > > database management systems to Apache Spark. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > - > > > > > > > > > > > To unsubscribe, e-mail: > > > > > general-unsubscr...@incubator.apache.org > > > > > > > > > > > For additional commands, e-mail: > > > > > > general-h...@incubator.apache.org > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > - > > > > > > > > > To unsubscribe, e-mail: > > > general-unsubscr...@incubator.apache.org > > > > > > > > > For additional commands, e-mail: > > > > general-h...@incubator.apache.org > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > > > > > > *Kent Yao * > > > > > > @ Data Science Center, Hangzhou Research Institute, NetEase Corp. > > > > > > a spark enthusiast > > > > > > kyuubi <https://github.com/yaooqinn/kyuubi>is a unified > multi-tenant > > > > > JDBC > > > > > > interface for large-scale data processing and analytics, built > on top > > > > of > > > > > > Apache > > > > > > Spark <http://spark.apache.org/>. > > > > > > spark-authorizer <https://github.com/yaooqinn/spark-authorizer>A > > > Spark > > > > > SQL > > > > > > extension which provides SQL Standard Authorization for Apache > Spark > > > > > > <http://spark.apache.org/>. > > > > > > spark-postgres <https://github.com/yaooqinn/spark-postgres> A > > > library > > > > > for > > > > > > reading data from and transferring data to Postgres / Greenplum > with > > > > > Spark > > > > > > SQL and DataFrames, 10~100x faster. > > > > > > itatchi <https://github.com/yaooqinn/spark-func-extras>A library > > > that > > > > > > brings useful functions from various modern database management > > > > > > systems to Apache > > > > > > Spark <http://spark.apache.org/>. > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > > *Kent Yao * > > > > @ Data Science Center, Hangzhou Research Institute, NetEase Corp. > > > > a spark enthusiast > > > > kyuubi <https://github.com/yaooqinn/kyuubi>is a unified multi-tenant > > > JDBC > > > > interface for large-scale data processing and analytics, built on > top of > > > > Apache > > > > Spark <http://spark.apache.org/>. > > > > spark-authorizer <https://github.com/yaooqinn/spark-authorizer>A > Spark > > > SQL > > > > extension which provides SQL Standard Authorization for Apache Spark > > > > <http://spark.apache.org/>. > > > > spark-postgres <https://github.com/yaooqinn/spark-postgres> A > library > > > for > > > > reading data from and transferring data to Postgres / Greenplum with > > > Spark > > > > SQL and DataFrames, 10~100x faster. > > > > itatchi <https://github.com/yaooqinn/spark-func-extras>A library > that > > > > brings useful functions from various modern database management > > > > systems to Apache > > > > Spark <http://spark.apache.org/>. > > > > > > > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > -- Thanks, Ming Wen, Apache APISIX PMC Chair Twitter: _WenMing
Re: Heron: Need help from IPMC
hi, josh, I will check the release tomorrow Sorry for delay Josh Fischer 于2021年5月18日 周二下午11:10写道： > Kevin & Ming, > > In response to an earlier email on this thread: Do I need to > do anything additional for you all to be added as mentors to Heron? We > started a vote about 5 days ago and are still needing at least one binding > vote on the release candidate to bring it over to general@. > > On Sat, Feb 6, 2021 at 7:22 AM Josh Fischer wrote: > > > Kevin & Ming, > > > > This is fantastic news. Thank you for the help. I will get you added to > > the group today. > > > > - Josh > > > > On Sat, Feb 6, 2021 at 4:13 AM Ning Wang wrote: > > > >> Thanks! > >> > >> On Fri, Feb 5, 2021 at 11:04 PM Kevin Ratnasekera < > >> djkevincr1...@gmail.com> > >> wrote: > >> > >> > Hi Josh, > >> > > >> > I am also willing to help as a mentor. > >> > > >> > Regards > >> > Kevin > >> > > >> > On Sat, Feb 6, 2021 at 6:06 AM Ming Wen wrote: > >> > > >> > > hello, Josh, > >> > > > >> > > I am willing to help as a mentor. > >> > > > >> > > Josh Fischer 于2021年2月3日 周三上午6:04写道： > >> > > > >> > > > Hi, > >> > > > > >> > > > Heron only has one active mentor. We could use the assistance of > a > >> few > >> > > > more if someone is willing to help. > >> > > > > >> > > > - Josh > >> > > > > >> > > -- > >> > > Thanks, > >> > > Ming Wen, Apache APISIX PMC Chair > >> > > Twitter: _WenMing > >> > > > >> > > >> > > -- > > Sent from A Mobile Device > > > -- Thanks, Ming Wen, Apache APISIX PMC Chair Twitter: _WenMing
Re: [VOTE] Retirement of Weex
+1 binding kezhenxu94@apache 于2021年5月9日 周日下午6:28写道： > +1 binding > > > On May 9, 2021, at 18:06, Willem Jiang wrote: > > > > Hi, > > > > According to the retirement guide[1] of incubator, we started the > > public discussion in the weex dev mailing list and got the > > conclusion[2] to go to the retirement process. > > > > Now we just start a LAZY consensus vote in the IPMC. > > > > [ ] +1 Support to retire Weex from Apache Incubator > > [ ] -1 Do not Support to retire Weex from Apache Incubator (please > > provide specific comments) > > > > This vote will be open for at least 72 hours. > > > > [1]https://incubator.apache.org/guides/retirement.html > > [2] > https://lists.apache.org/thread.html/rcaf67836a77ad3bebcafffc9e853bcd043a844e123e06ac8e71c9f4d%40%3Cdev.weex.apache.org%3E > > > > Willem Jiang > > > > Twitter: willemjiang > > Weibo: 姜宁willem > > > > - > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > — > Zhenxu Ke (柯振旭) > GitHub @kezhenxu94 > > > --------- > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > -- Thanks, Ming Wen, Apache APISIX PMC Chair Twitter: _WenMing
Re: [VOTE] Release Apache Doris 0.14.0-incubating-rc04
That seems to be a brand issue. Doris is an Apache incubator project, so the name of the project `Baidu Doris` will confuse users. Thanks, Ming Wen, Apache APISIX PMC Chair Twitter: _WenMing ling miao 于2021年4月12日周一 上午10:23写道： > Hi Ming Wen, > > > When I searched for `Doris 0.14` on Google, I found an article[1] > mentioning that Doris 0.14.7 has been released. > Doris 0.14.7 is an internal version of our baidu doris. It is not the > version of apache doris, so apache doris has not released version 0.14. > [1] The article is actually a release of the internal version. > > > But I checked the historical release[2] and did not have this version. > Since the community has not formally voted for the release, the > documentation of our community has not yet been updated [2]. We will update > the community documentation after the community has completed the release. > > Shouldn't it be a problem? > > Ling Miao > > Ming Wen 于2021年4月12日周一 上午9:27写道： > >> Hello, >> When I searched for `Doris 0.14` on Google, I found an article[1] >> mentioning that Doris 0.14.7 has been released. >> But I checked the historical release[2] and did not have this version. >> In my understanding, 0.14.0 has not been released. Why does 0.14.7 exist? >> >> [1] https://www.modb.pro/db/49638 >> [2] https://doris.apache.org/master/en/downloads/downloads.html >> >> Thanks, >> Ming Wen, Apache APISIX PMC Chair >> Twitter: _WenMing >> >> >> Xun Liu 于2021年4月11日周日 下午11:05写道： >> >> > +1 (non-binding) >> > >> > I checked: >> > [√] Download links are valid. >> > [√] Checksums and PGP signatures are valid. >> > [√] LICENSE, NOTICE and DISCLAIMER files exist. >> > [√] All files have license headers if necessary. >> > >> > Thanks, >> > Xun Liu >> > >> > On Sun, Apr 11, 2021 at 10:13 PM Willem Jiang >> > wrote: >> > >> > > I’m +1, I checked >> > > >> > > - LICENSE, DISCLAIM and NOTICE files exist; >> > > - Release candidate tar is signed, the Shasum. >> > > - “incubating” exists in tar file name and documentation; >> > > - License headers exist in files if necessary. >> > > >> > > Willem Jiang >> > > >> > > Twitter: willemjiang >> > > Weibo: 姜宁willem >> > > >> > > On Wed, Apr 7, 2021 at 1:37 PM 寒江雪 wrote: >> > > > >> > > > Hi all, >> > > > >> > > > Please review and vote on Apache Doris 0.14.0-incubating-rc04 >> release. >> > > > >> > > > Apache Doris is an MPP-based interactive SQL data warehousing for >> > > reporting >> > > > and analysis. >> > > > >> > > > The Apache Doris community has voted on and approved this release: >> > > > >> > > >> > >> https://lists.apache.org/thread.html/rc95a58e64b926dc89b61e747fd11f8cb7bb173d95395fa26d02d2c00%40%3Cdev.doris.apache.org%3E >> > > > >> > > > The vote result email thread: >> > > > >> > > >> > >> https://lists.apache.org/thread.html/r14fc4ffeb31046343570a226dd7870ca74b0f15fbad492b09f0bb69f%40%3Cdev.doris.apache.org%3E >> > > > >> > > > The release candidate has been tagged in GitHub as 0.14.0-rc04, >> > available >> > > > here: >> > > > https://github.com/apache/incubator-doris/releases/tag/0.14.0-rc04 >> > > > >> > > > Thanks to everyone who has contributed to this release, and there >> is a >> > > > simple release notes can be found here: >> > > > https://github.com/apache/incubator-doris/issues/5374 >> > > > >> > > > The artifacts (source, signature and checksum) corresponding to this >> > > release >> > > > candidate can be found here: >> > > > >> > >> https://dist.apache.org/repos/dist/dev/incubator/doris/0.14/0.14.0-rc04/ >> > > > >> > > > This has been signed with PGP key 59F2ACED, corresponding to >> > > > yang...@apache.org. >> > > > KEYS file is available here: >> > > > https://dist.apache.org/repos/dist/dev/incubator/doris/KEYS >> > > > It is also listed here: >> > > > https://people.apache.org/keys/committer/yangzhg.asc >> > > > >> > > > The vote will be open for at least 72 hours. >> > > > [ ] +1 Approve the release &g
Re: [VOTE] Release Apache Doris 0.14.0-incubating-rc04
Hello, When I searched for `Doris 0.14` on Google, I found an article[1] mentioning that Doris 0.14.7 has been released. But I checked the historical release[2] and did not have this version. In my understanding, 0.14.0 has not been released. Why does 0.14.7 exist? [1] https://www.modb.pro/db/49638 [2] https://doris.apache.org/master/en/downloads/downloads.html Thanks, Ming Wen, Apache APISIX PMC Chair Twitter: _WenMing Xun Liu 于2021年4月11日周日 下午11:05写道： > +1 (non-binding) > > I checked: > [√] Download links are valid. > [√] Checksums and PGP signatures are valid. > [√] LICENSE, NOTICE and DISCLAIMER files exist. > [√] All files have license headers if necessary. > > Thanks, > Xun Liu > > On Sun, Apr 11, 2021 at 10:13 PM Willem Jiang > wrote: > > > I’m +1, I checked > > > > - LICENSE, DISCLAIM and NOTICE files exist; > > - Release candidate tar is signed, the Shasum. > > - “incubating” exists in tar file name and documentation; > > - License headers exist in files if necessary. > > > > Willem Jiang > > > > Twitter: willemjiang > > Weibo: 姜宁willem > > > > On Wed, Apr 7, 2021 at 1:37 PM 寒江雪 wrote: > > > > > > Hi all, > > > > > > Please review and vote on Apache Doris 0.14.0-incubating-rc04 release. > > > > > > Apache Doris is an MPP-based interactive SQL data warehousing for > > reporting > > > and analysis. > > > > > > The Apache Doris community has voted on and approved this release: > > > > > > https://lists.apache.org/thread.html/rc95a58e64b926dc89b61e747fd11f8cb7bb173d95395fa26d02d2c00%40%3Cdev.doris.apache.org%3E > > > > > > The vote result email thread: > > > > > > https://lists.apache.org/thread.html/r14fc4ffeb31046343570a226dd7870ca74b0f15fbad492b09f0bb69f%40%3Cdev.doris.apache.org%3E > > > > > > The release candidate has been tagged in GitHub as 0.14.0-rc04, > available > > > here: > > > https://github.com/apache/incubator-doris/releases/tag/0.14.0-rc04 > > > > > > Thanks to everyone who has contributed to this release, and there is a > > > simple release notes can be found here: > > > https://github.com/apache/incubator-doris/issues/5374 > > > > > > The artifacts (source, signature and checksum) corresponding to this > > release > > > candidate can be found here: > > > > https://dist.apache.org/repos/dist/dev/incubator/doris/0.14/0.14.0-rc04/ > > > > > > This has been signed with PGP key 59F2ACED, corresponding to > > > yang...@apache.org. > > > KEYS file is available here: > > > https://dist.apache.org/repos/dist/dev/incubator/doris/KEYS > > > It is also listed here: > > > https://people.apache.org/keys/committer/yangzhg.asc > > > > > > The vote will be open for at least 72 hours. > > > [ ] +1 Approve the release > > > [ ] +0 No opinion > > > [ ] -1 Do not release this package because ... > > > > > > To verify and build, you can refer to the following wiki: > > > > > > https://github.com/apache/incubator-doris/wiki/How-to-verify-Apache-Release > > > https://wiki.apache.org/incubator/Incubator+Release+Checklist > > > > > > You can also refer to instruction: > > > > > > Firstly, you must install and start docker service, and then you could > > > build Doris as the following steps: > > > > > > Step1: Pull the docker image with Doris building environment > > > $ docker pull apachedoris/doris-dev:build-env-1.2 > > > You can check it by listing images, its IMAGE ID is d854b488afaf > > > > > > Step2: Run the Docker image > > > You can run the image directly: > > > $ docker run -it apachedoris/doris-dev:build-env1.2 > > > > > > Step3: Download Doris source > > > Now you should in the docker environment, and you can download the > Doris > > > source package. > > > (If you have downloaded the source and it is not in image, you can map > > its > > > path to image in Step2.) > > > $ wget > > > > > > https://dist.apache.org/repos/dist/dev/incubator/doris/0.14/0.14.0-rc04/apache-doris-0.14.0-incubating-src.tar.gz > > > > > > Step4: Build Doris > > > Now you can decompress and enter Doris source path and build Doris. > > > $ tar -zxvf apache-doris-0.14.0-incubating-src.tar.gz > > > $ cd apache-doris-0.14.0-incubating-src > > > $ sh build.sh > > > > > > Best Regards, > > > Yang Zhengguo > > > > - > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > >
Re: Re: [VOTE] Release Apache Doris 0.14.0-incubating-rc03
yes, looks good to me. Thanks, Ming Wen, Apache APISIX PMC Chair Twitter: _WenMing 寒江雪 于2021年3月29日周一 下午3:38写道： > Hi ming wen， > Is it possible to exclude all the unit tests in our project source code > when packaging the release tarball ? > > Ming Wen 于2021年3月29日周一 上午10:59写道： > > > hello, mingyu, > > These files can be in the GitHub repo, but should not be in the released > > source package. > > You can remove the test-related files when packaging, this is also the > > usual practice. > > > > Thanks, > > Ming Wen, Apache APISIX PMC Chair > > Twitter: _WenMing > > > > > > 陈明雨 于2021年3月29日周一 上午10:48写道： > > > > > Hi kezhenxu94: > > > > > > > > > Thanks for your apply. > > > > > > > > > We have such a scenario, such as the need to test a file decompression > > > code in a unit test. > > > I think a reasonable way is to directly provide some small zip files > for > > > the unit test to test the > > > decompression logic without writing a set of compression code to > generate > > > these zip files at runtime. > > > > > > > > > And in fact, we also refer to the practices of some top-level projects, > > > such as [1], [2]. > > > > > > > > > In addition, I only found instructions on the Release that the main > > > running code cannot contain binary, > > > but the instructions for unit testing are rather vague, so we are not > > > completely sure how to deal with these problems reasonably. > > > If there are related links, could you please provide us for reference? > > > > > > > > > [1] > > > > > > https://github.com/apache/spark/tree/v3.1.1/sql/hive/src/test/resources/regression-test-SPARK-8489 > > > [2] https://github.com/apache/impala/tree/3.4.0/testdata/tzdb > > > > > > > > > > > > > > > -- > > > > > > 此致！Best Regards > > > 陈明雨 Mingyu Chen > > > > > > Email: > > > morning...@163.com; > > > morningman@gmail.com > > > > > > > > > > > > > > > > > > 在 2021-03-28 22:55:11，"kezhenxu94" 写道： > > > > > > > > > > > >> On Mar 28, 2021, at 18:40, 陈明雨 wrote: > > > >> > > > >> Hi kezhenxu94: > > > >> > > > >> > > > >> These files are for unit tests to test the java dynamic library > > > loading, not some kind of "test tools". > > > > > > > >I have some further questions, where are these files come from, if > their > > > source codes are in the same repo, why not just build them from the > > source > > > codes before using them, if the files’ source codes are not in the same > > > repo, there a bunch of ways to depend on them, but including the binary > > > files is not the first choice, if worse, the files’ source codes are > not > > > accessible, the PMC has no way to review the content and it’s a > > potential > > > security problem. > > > > > > > >> These files are in the code repo for a long time and also contained > in > > > our previous releases, and no one disagrees with it. > > > >> So I believe it is ok for a source release. > > > > > > > >The previous releases including them does not mean it’s ok IMO, it > might > > > be overlooked , that’s one of the reasons why we need several releases > > > before graduation to give the IPMC more time to review the release > > process > > > as well as their contents. > > > > > > > >> > > > >> > > > >> > > > >> -- > > > >> > > > >> 此致！Best Regards > > > >> 陈明雨 Mingyu Chen > > > >> > > > >> Email: > > > >> chenmin...@apache.org > > > >> > > > >> > > > >> > > > >> > > > >> > > > >>> 在 2021-03-27 22:53:49，"kezhenxu94@apache" > > 写道： > > > >>> Sorry my -1, I saw there are binary files in the source tar, > although > > > they’re test tools, but this is not allowed in the source release. > > > >>> > > > >>> ./fe/fe-core/src/test/resources/plugin_test/plugin_test.jar > > > >>> > > > > > > ./fe/fe-core/src/test/resources/plugin_test/test_local_p
Re: Re: [VOTE] Release Apache Doris 0.14.0-incubating-rc03
hello, mingyu, These files can be in the GitHub repo, but should not be in the released source package. You can remove the test-related files when packaging, this is also the usual practice. Thanks, Ming Wen, Apache APISIX PMC Chair Twitter: _WenMing 陈明雨 于2021年3月29日周一 上午10:48写道： > Hi kezhenxu94: > > > Thanks for your apply. > > > We have such a scenario, such as the need to test a file decompression > code in a unit test. > I think a reasonable way is to directly provide some small zip files for > the unit test to test the > decompression logic without writing a set of compression code to generate > these zip files at runtime. > > > And in fact, we also refer to the practices of some top-level projects, > such as [1], [2]. > > > In addition, I only found instructions on the Release that the main > running code cannot contain binary, > but the instructions for unit testing are rather vague, so we are not > completely sure how to deal with these problems reasonably. > If there are related links, could you please provide us for reference? > > > [1] > https://github.com/apache/spark/tree/v3.1.1/sql/hive/src/test/resources/regression-test-SPARK-8489 > [2] https://github.com/apache/impala/tree/3.4.0/testdata/tzdb > > > > > -- > > 此致！Best Regards > 陈明雨 Mingyu Chen > > Email: > morning...@163.com; > morningman@gmail.com > > > > > > 在 2021-03-28 22:55:11，"kezhenxu94" 写道： > > > > > >> On Mar 28, 2021, at 18:40, 陈明雨 wrote: > >> > >> Hi kezhenxu94: > >> > >> > >> These files are for unit tests to test the java dynamic library > loading, not some kind of "test tools". > > > >I have some further questions, where are these files come from, if their > source codes are in the same repo, why not just build them from the source > codes before using them, if the files’ source codes are not in the same > repo, there a bunch of ways to depend on them, but including the binary > files is not the first choice, if worse, the files’ source codes are not > accessible, the PMC has no way to review the content and it’s a potential > security problem. > > > >> These files are in the code repo for a long time and also contained in > our previous releases, and no one disagrees with it. > >> So I believe it is ok for a source release. > > > >The previous releases including them does not mean it’s ok IMO, it might > be overlooked , that’s one of the reasons why we need several releases > before graduation to give the IPMC more time to review the release process > as well as their contents. > > > >> > >> > >> > >> -- > >> > >> 此致！Best Regards > >> 陈明雨 Mingyu Chen > >> > >> Email: > >> chenmin...@apache.org > >> > >> > >> > >> > >> > >>> 在 2021-03-27 22:53:49，"kezhenxu94@apache" 写道： > >>> Sorry my -1, I saw there are binary files in the source tar, although > they’re test tools, but this is not allowed in the source release. > >>> > >>> ./fe/fe-core/src/test/resources/plugin_test/plugin_test.jar > >>> > ./fe/fe-core/src/test/resources/plugin_test/test_local_plugin/auditdemo.jar > >>> > >>>>> On Mar 26, 2021, at 12:36, 寒江雪 wrote: > >>>> > >>>> Hi all, > >>>> > >>>> Please review and vote on Apache Doris 0.14.0-incubating-rc03 release. > >>>> > >>>> Apache Doris is an MPP-based interactive SQL data warehousing for > reporting > >>>> and analysis. > >>>> > >>>> The Apache Doris community has voted on and approved this release: > >>>> > https://lists.apache.org/thread.html/r1d3728b02b4f7b56413d3bf334b94fbc9c8406bf2d78aa01fea60a77%40%3Cdev.doris.apache.org%3E > >>>> > >>>> The vote result email thread: > >>>> > https://lists.apache.org/thread.html/re1eb419d0eb4689d77e82727811facef08f3c2498f64ad2ea812d42a%40%3Cdev.doris.apache.org%3E > >>>> > >>>> The release candidate has been tagged in GitHub as 0.14.0-rc03, > available > >>>> here: > >>>> https://github.com/apache/incubator-doris/releases/tag/0.14.0-rc03 > >>>> > >>>> Thanks to everyone who has contributed to this release, and there is a > >>>> simple release notes can be found here: > >>>> https://github.com/apache/incubator-doris/issues/5374 > >>>> > >>>> The artifacts (source, si
Re: Question: How can I know how many users subscribe my email list like d...@bluemarlin.apache.org?
Hi, Xun, You can get the subscribe data from https://whimsy.apache.org/committers/moderationhelper if you are the moderator. Thanks, Ming Wen, Apache APISIX PMC Chair Twitter: _WenMing Xun Hu 于2021年3月2日周二 上午8:23写道： > EOM. >
Re: Re: [Proposal] lxdb - proposal for Apache Incubation
Hi, fp, Your email is hard to read. Please change to a normal mail client first. Back to your proposal, the key concern is not technology, but IPMC can not evaluate a project when we can see anything. Thanks, Ming Wen, Apache APISIX PMC Chair Twitter: _WenMing f...@lucene.cn 于2021年2月28日周日 下午9:02写道： > Hi Furkan Kamaci > > > Thank you for your proposal, I will start to improve and prepare > > > > > 1.Find an experienced mentor to guide you. > > > > todo > > > > 2.Start to translate your documentation to English. > > > > 3.Open source your project. How can we have a comment on your project if > > > > we cannot see anything about it? > > > > > > > > give me some time,I discussed with my team, my English is too poor. > > > > > > > > 4) Gain contributors to your project. At least you should show your > > > > intention to have committers/contributors out of your company. Eliminate > > > > the risk of being non-meritocratic management of the project. > > > > > > > > That's what I have to do > > > > > > > > 5) Structure your proposal. Explain why people need this project, which > > > > problems do current projects have and how you managed to handle them. We > > > > should understand is it a bundle of other projects, a completely new > > > > project, or a wrapper of other projects which eliminates the shortcomings > > > > of them. > > > > 6) Find a suitable name for your project in order to not try to solve > > > > trademark problems that may lose your time if you enter the incubation. > > > > > > > > ok i thike a new name ,for example like hydrogen sql > > > > > > > > > > > > > > > > f...@lucene.cn yannian mu > > > > > > > > From: Furkan KAMACI > > > > Date: 2021-02-28 18:51 > > > > To: general > > > > Subject: Re: [Proposal] lxdb - proposal for Apache Incubation > > > > Hi, > > > > > > > > Actually you have a detailed documentation which explains which approach > > > > you have compared to similar systems and performance metrics of following > > > > them i.e. reducing storage 10 to the 100 times or having low latency > > > > queries. > > > > > > > > My advices are (some of them are same with Sheng's and Liang's ): > > > > > > > > 1) Find an experienced mentor to guide you. > > > > > > > > 2) Start to translate your documentation to English. > > > > > > > > 3) Open source your project. How can we have a comment on your project if > > > > we cannot see anything about it? > > > > > > > > 4) Gain contributors to your project. At least you should show your > > > > intention to have committers/contributors out of your company. Eliminate > > > > the risk of being non-meritocratic management of the project. > > > > > > > > 5) Structure your proposal. Explain why people need this project, which > > > > problems do current projects have and how you managed to handle them. We > > > > should understand is it a bundle of other projects, a completely new > > > > project, or a wrapper of other projects which eliminates the shortcomings > > > > of them. > > > > > > > > 6) Find a suitable name for your project in order to not try to solve > > > > trademark problems that may lose your time if you enter the incubation. > > > > > > > > Kind Regards, > > > > Furkan KAMACI > > > > > > > > > > > > On Sun, Feb 28, 2021 at 1:02 PM Liang Chen > wrote: > > > > > > > > > Hi > > > > > > > > > > It would be better if you could find an experienced IPMC member to help > you > > > > > for preparing the proposal. > > > > > Based on Sheng Wu input, i have one more comment : can you please explain > > > > > what are the different with other similar data analysis DB? you can > > > > > consider explaining from use cases perspective. > > > > > > > > > > Regards > > > > > Liang > > > > > > > > > > > > > > > fp wrote > > > > > > Dear Apache Incubator Community, > > > > > > > > > > > > > > > > > > Please accept the following proposal for presentation and discus
Re: [VOTE] Graduate Apache DolphinScheduler (incubating) as a TLP
+1 binding Sheng Wu 于2021年2月14日 周日下午7:21写道： > +1 binding > > > Sheng Wu 吴晟 > Twitter, wusheng1108 > > > Liang Chen 于2021年2月14日周日 下午7:16写道： > > > +1(binding) > > > > Regards > > Liang > > > > 在 2021年2月14日星期日，Kevin Ratnasekera 写道： > > > > > +1 ( binding ) > > > > > > On Sun, Feb 14, 2021 at 4:19 PM lidong dai > > wrote: > > > > > > > Hello all, > > > > > > > > We've got positive feedback on the DISCUSS thread [1], I'd like to > > start > > > an > > > > official VOTE thread now. > > > > > > > > Please vote on the resolution pasted below to graduate Apache > > > > DolphinScheduler from the incubator to the Top Level Project. > > > > > > > > [ ] +1 Graduate Apache DolphinScheduler from the Incubator. > > > > [ ] +0 Don't care. > > > > [ ] -1 Don't graduate Apache DolphinScheduler from the Incubator > > because > > > > ... > > > > > > > > This vote will open for at least 72 hours. > > > > > > > > Many thanks to our mentors and everyone else for their support. > > > > > > > > [1] > > > > > > > > https://lists.apache.org/thread.html/r1d5f4e122c914b39a49a9ae5c3960 > > > 5e17c0b82b20de3966e989a9f21%40%3Cgeneral.incubator.apache.org%3E > > > > > > > > > > > > > > > - > > > > > > > > Establish the Apache DolphinScheduler 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 a distributed and extensible workflow scheduler platform > > with > > > > powerful DAG visual interfaces. > > > > > > > > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee > > > > (PMC), to be known as the "Apache DolphinScheduler Project", be and > > > > hereby is established pursuant to Bylaws of the Foundation; and be it > > > > further > > > > > > > > RESOLVED, that the Apache DolphinScheduler Project be and hereby is > > > > responsible for the creation and maintenance of software related to a > > > > distributed and extensible workflow scheduler platform with powerful > > DAG > > > > visual interfaces.; and be it further > > > > > > > > RESOLVED, that the office of "Vice President, Apache > DolphinScheduler" > > > > 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 > > > > DolphinScheduler Project, and to have primary responsibility for > > > > management of the projects within the scope of responsibility of the > > > > Apache DolphinScheduler 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 > > DolphinScheduler > > > > Project: > > > > > > > > * Furkan Kamaci > > > > * Gang Li > > > > * Guo Jiwei > > > > * Guo William > > > > * Jun Gao > > > > * Kevin Ratnasekera > > > > * Leon Bao > > > > * Liang Chen > > > > * Lidong Dai > > > > * Qiao Zhanwei > > > > * Shao Feng Shi > > > > * Sheng Wu > > > > * Wu Baoqi > > > > * Xiaochun Liu > > > > * ZijJian Gong > > > > > > > > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Lidong Dai be appointed > to > > > > the office of Vice President, Apache DolphinScheduler, 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 DolphinScheduler Project be and hereby is > > > > tasked with the migration and rationalization of the Apache Incubator > > > > DolphinScheduler podling; and be it further > > > > > > > > RESOLVED, that all responsibilities pertaining to the Apache > Incubator > > > > DolphinScheduler podling encumbered upon the Apache Incubator PMC are > > > > hereafter discharged. > > > > > > > > > > > > > > > > Best Regards > > > > --- > > > > DolphinScheduler(Incubator) PPMC > > > > Lidong Dai > > > > dailidon...@gmail.com > > > > --- > > > > > > > > > > -- Thanks, Ming Wen, Apache APISIX PMC Chair Twitter: _WenMing
Re: [VOTE] Graduate Apache DolphinScheduler (incubating) as a TLP
+1 binding good luck Mingshen Sun 于2021年2月14日 周日下午12:46写道： > +1 (non-binding). > > Good luck. > > On Sat, Feb 13, 2021 at 7:46 PM Xiangdong Huang wrote: > > > > +1 (non-binding). Congrats! > > > > > > On 2021/02/12 14:18:45, Gang Li wrote: > > > Hello all, > > > > > > We've got positive feedback on the DISCUSS thread [1], I'd like to > start an > > > official VOTE thread now. > > > > > > Please vote on the resolution pasted below to graduate Apache > > > DolphinScheduler from the incubator to the Top Level Project. > > > > > > [ ] +1 Graduate Apache DolphinScheduler from the Incubator. > > > [ ] +0 Don't care. > > > [ ] -1 Don't graduate Apache DolphinScheduler from the Incubator > because ... > > > > > > This vote will open for at least 72 hours. > > > > > > Many thanks to our mentors and everyone else for their support. > > > > > > [1] > https://lists.apache.org/thread.html/r1d5f4e122c914b39a49a9ae5c39605e17c0b82b20de3966e989a9f21%40%3Cgeneral.incubator.apache.org%3E > > > > > > > > > > - > > > > > > Establish the Apache DolphinScheduler 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 a distributed and extensible workflow scheduler platform > with > > > powerful DAG visual interfaces. > > > > > > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee > > > (PMC), to be known as the "Apache DolphinScheduler Project", be and > > > hereby is established pursuant to Bylaws of the Foundation; and be it > > > further > > > > > > RESOLVED, that the Apache DolphinScheduler Project be and hereby is > > > responsible for the creation and maintenance of software related to a > > > distributed and extensible workflow scheduler platform with powerful > DAG > > > visual interfaces.; and be it further > > > > > > RESOLVED, that the office of "Vice President, Apache DolphinScheduler" > > > 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 > > > DolphinScheduler Project, and to have primary responsibility for > > > management of the projects within the scope of responsibility of the > > > Apache DolphinScheduler 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 > DolphinScheduler > > > Project: > > > > > > * Furkan Kamaci > > > * Gang Li > > > * Guo Jiwei > > > * Guo William > > > * Jun Gao > > > * Kevin Ratnasekera > > > * Leon Bao > > > * Liang Chen > > > * Lidong Dai > > > * Qiao Zhanwei > > > * Shao Feng Shi > > > * Sheng Wu > > > * Wu Baoqi > > > * Xiaochun Liu > > > * ZijJian Gong > > > > > > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Lidong Dai be appointed to > > > the office of Vice President, Apache DolphinScheduler, 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 DolphinScheduler Project be and hereby is > > > tasked with the migration and rationalization of the Apache Incubator > > > DolphinScheduler podling; and be it further > > > > > > RESOLVED, that all responsibilities pertaining to the Apache Incubator > > > DolphinScheduler podling encumbered upon the Apache Incubator PMC are > > > hereafter discharged. > > > > > > > > > > > > > > > > Best Regards > > > > > > -- > > > DolphinScheduler(Incubator) PPMC > > > Gang Li 李岗 > > > > > > lgcar...@apache.org > > > > > > > > > > > > > > > > > > > - > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > -- Thanks, Ming Wen, Apache APISIX PMC Chair Twitter: _WenMing
Re: Finding a mentor for Doris(Incubating)
I am willing to help as a mentor 陈明雨 于2021年2月6日 周六下午10:34写道： > Hi All: > > > I'm the member of Doris PPMC. > Our former mentor Dave resigned from Doris' mentor position for some > reason. > We respect Dave's decision very much and thank Dave for his help during > the Doris incubation process. > > > We currently only have two mentors, so we seek a third mentor to help us > continue to complete the incubation work. > Any suggestions and discussions are welcome. > > > - > Doris is "A fast MPP database for all modern analytics on big data", > It has been widely used in more than 100 companies. > You can visit our website[1] for more information. > > > [1] http://doris.incubator.apache.org/master/en/ > > > > -- > > 此致！Best Regards > 陈明雨 Mingyu Chen > > Email: > chenmin...@apache.org -- Thanks, Ming Wen, Apache APISIX PMC Chair Twitter: _WenMing
Re: Heron: Need help from IPMC
hello, Josh, I am willing to help as a mentor. Josh Fischer 于2021年2月3日 周三上午6:04写道： > Hi, > > Heron only has one active mentor. We could use the assistance of a few > more if someone is willing to help. > > - Josh > -- Thanks, Ming Wen, Apache APISIX PMC Chair Twitter: _WenMing
Re: [DISCUSS] Graduate Apache DolphinScheduler (incubating) as a TLP
+1 binding Congratulations, the community has grown very well Paul King 于2021年2月6日 周六上午7:08写道： > +1 (binding) > > Cheers, Paul. > > On Fri, Feb 5, 2021 at 9:36 PM Gang Li wrote: > > > Hi all, > > After discussion with the community [1] and [2], and a positive vote > > result [3]. > > We'd like to bring this to a discussing at the IPMC. > > > > Please see the proposed resolution below and let us know what do you > think. > > > > A few status to help with the discussion: > > > > - Released 8 Apache releases, through 5 different release managers > > - Invited 14 new committers (all accepted) > > - Invited 2 new PPMC members (all accepted) > > - Apache DolphinScheduler name search has been approved [4] > > - Finished the Podling Maturity Assessment for DolphinScheduler [5], all > > items are passed > > - There are 169 contributors for now > > - There are 1904 emails sent by 197 people in dev mailing-list excepted > > GitBox forwarded > > - Resolved 1500+ issues and 2000+ pull requests during ASF incubating > > > > We've resolved all branding issues which include Logo, GitHub repo, > > document, website and others. > > > > [1] > > > https://lists.apache.org/thread.html/rbef0779035c61d02ef9fa63e55175fd5896fc513258d1b2537b51604%40%3Cdev.dolphinscheduler.apache.org%3E > > [2] > > > https://lists.apache.org/thread.html/r79381a3fd38d112b5ccb0be67675547e187497135853b0fe999f813a%40%3Cdev.dolphinscheduler.apache.org%3E > > [3] > > > https://lists.apache.org/thread.html/raa78e55fc511b479cae1c4faefb8ae2cb31b4fb9143a1a958ac577f0%40%3Cdev.dolphinscheduler.apache.org%3E > > [4] https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-186 > > [5] > > > https://cwiki.apache.org/confluence/display/DOLPHINSCHEDULER/Podling+Maturity+Assessment+for+DolphinScheduler > > > > - > > > > Establish the Apache DolphinScheduler 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 a distributed and extensible workflow scheduler platform with > > powerful DAG visual interfaces. > > > > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee > > (PMC), to be known as the "Apache DolphinScheduler Project", be and > > hereby is established pursuant to Bylaws of the Foundation; and be it > > further > > > > RESOLVED, that the Apache DolphinScheduler Project be and hereby is > > responsible for the creation and maintenance of software related to a > > distributed and extensible workflow scheduler platform with powerful DAG > > visual interfaces.; and be it further > > > > RESOLVED, that the office of "Vice President, Apache DolphinScheduler" > > 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 > > DolphinScheduler Project, and to have primary responsibility for > > management of the projects within the scope of responsibility of the > > Apache DolphinScheduler 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 DolphinScheduler > > Project: > > > > * Furkan Kamaci > > * Gang Li > > * Guo Jiwei > > * Guo William > > * Jun Gao > > * Kevin Ratnasekera > > * Leon Bao > > * Liang Chen > > * Lidong Dai > > * Qiao Zhanwei > > * Shao Feng Shi > > * Sheng Wu > > * Wu Baoqi > > * Xiaochun Liu > > * ZijJian Gong > > > > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Lidong Dai be appointed to > > the office of Vice President, Apache DolphinScheduler, 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 DolphinScheduler Project be and hereby is > > tasked with the migration and rationalization of the Apache Incubator > > DolphinScheduler podling; and be it further > > > > RESOLVED, that all responsibilities pertaining to the Apache Incubator > > DolphinScheduler podling encumbered upon the Apache Incubator PMC are > > hereafter discharged. > > > > > > > > > > > > > Best Regards > > > > -- > > DolphinScheduler(Incubator) PPMC > > Gang Li 李岗 > > > > lgcar...@apache.org > > > > > > > -- Thanks, Ming Wen, Apache APISIX PMC Chair Twitter: _WenMing
Re: [VOTE] Release Apache Sedona 1.0.0-incubating rc1
+1 (binding) I checked: - Incubating in name - Checksums and PGP signatures are valid - DISCLAIMER-WIP exists - LICENSE and NOTICE look OK Thanks, Ming Wen, Apache APISIX PMC Chair Twitter: _WenMing Jia Yu 于2021年2月4日周四 上午11:47写道： > Dear all, > > We need to collect more votes in order to get this approved. Please take a > look at our release when you have time. > > Thank you very much! > Jia > > On Fri, Jan 29, 2021 at 1:00 PM Felix Cheung > wrote: > > > +1 (binding) > > > > Carry from dev@ > > > > > > On Thu, Jan 28, 2021 at 10:02 PM Jia Yu wrote: > > > >> Dear all, > >> > >> I would like to start a vote for the first release of Apache Sedona > >> 1.0.0-incubating rc1 > >> > >> Sedona community vote thread: > >> > >> > https://lists.apache.org/thread.html/r1c9406f0ba7b1eb942c03744ebe406344e1cc0bba8ae96430c66f63c%40%3Cdev.sedona.apache.org%3E > >> > >> Sedona community vote result thread: > >> > >> > https://lists.apache.org/thread.html/r462bd458b6542ad1bf8994e11717d8924365bfc3bb6282dc6acd5709%40%3Cdev.sedona.apache.org%3E > >> > >> Release note: > >> > >> > https://sedona.staged.apache.org/download/GeoSpark-All-Modules-Release-notes/#sedona-100 > >> > >> Build instructions: > >> https://sedona.staged.apache.org/download/compile/ > >> > >> GitHub tag: > >> > >> > https://github.com/apache/incubator-sedona/releases/tag/sedona-1.0.0-incubating-rc1 > >> > >> GPG public key to verify the Release: > >> https://dist.apache.org/repos/dist/dev/incubator/sedona/KEYS > >> > >> Source code and binaries: > >> > >> > https://dist.apache.org/repos/dist/dev/incubator/sedona/1.0.0-incubating-rc1/ > >> > >> The vote will be open for at least 72 hours. > >> > >> The vote will be open for 72 hours. > >> [ ] +1 approve > >> [ ] +0 no opinion > >> [ ] -1 do not release this package because... > >> > >> Thank you, > >> Jia Yu > >> > > >
Re: [VOTE] Graduate Apache Ratis as TLP Project
+1 binding good luck. Thanks, Ming Wen, Apache APISIX PMC Chair Twitter: _WenMing Juan Pan 于2021年2月1日周一 上午11:03写道： > Hi My +1 non-binding, good luck. > > > > > >Juan Pan (Trista) > > Senior DBA & PMC of Apache ShardingSphere > E-mail: panj...@apache.org > > > > > On 01/30/2021 04:32，Uma gangumalla wrote： > Dear Incubator Community, > > We have discussed Apache Ratis Podling graduation in the incubator general > DISCUSS thread[1] and We did not see any objections to proceed for voting. > Here is the official vote for graduating Apache Ratis project as TLP. > > Please provide your in the following options: > [ ] +1 - Recommend graduation of Apache Ratis as a TLP > [ ] 0 - I don't feel strongly about it, but don't object > [ ] -1 - Do not recommend graduation of Apache Ratis because... > > The VOTE will open for at least 72 hours. > > Just to summarize again: > Apache Ratis project is a very active project and the community has grown > well by following the Apache way in the process. It produced several > releases by having diverse people as release managers. I and the community > strongly believe that it's ready for graduation. > > The Apache Ratis project has been an Apache incubator project for nearly 3 > year. Since then the community has grown and followed Apache Way. Some > highlights include: > * 7 releases given ( including 1.0.0 and 0.0.1 alpha ) by having > different people as release managers > * 50 contributors ( from report) > * 28 committers > * More than 1161 Jiras created, 905 resolved or closed > * > 293 pull requests in github > * One of the biggest positives for this community is that most of the > members in this community have a lot of experience in other Apache projects > already. > > Some additional note about the resolution below: > The current PPMC will be transitioned to the PMC. We have invited some of > the mentors in the current PPMC who like to stay involved. > We are also adding Siddharth and Jie Wang into PMC as we believe they are > committed to the project and a good addition to PMC. > > We have already voted for Ratis TLP in the Ratis Podling community. Please > find the voting threads for reference. Ratis PPMC DISCUSS thread: [2], > Ratis PPMC Vote: [3] and Ratis Community: [4] > > To make easy for you to review, here is the *resolution text*[5] copied: > == > Establish the Apache Ratis 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 A java implementation for RAFT consensus protocol. > > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee > (PMC), to be known as the "Apache Ratis Project", be and hereby is > established pursuant to Bylaws of the Foundation; and be it further > > RESOLVED, that the Apache Ratis Project be and hereby is responsible for > the creation and maintenance of software related to A java > implementation for RAFT consensus protocol; and be it further > > RESOLVED, that the office of "Vice President, Apache Ratis" 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 Ratis > Project, and to have primary responsibility for management of the > projects within the scope of responsibility of the Apache Ratis 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 Ratis Project: > > * Anu Engineer [Hadoop, Ozone PMC, > Incubator Committer] > * Arpit Agarwal [ ASF Member, Hadoop, Ozone, > Incubator PMC] > * Enis Soztutar [ASF Member, Hadoop, HBase, > Incubator PMC and also PMC in curator, gora, phoenix] > * Hanisha Koneru[Hadoop, Ozone PMC, > Incubator Committer] > * Jie Wang [Incubator, Ozone > Committer] > * Jing Zhao [Hadoop PMC, Incubator > Committer] > * Jitendra Nath Pandey [ASF Member, Hadoop, Ozone, > Incubator PMC and also PMC in ambari, atlas, tez] > * Josh Elser [ASF Member, HBase, Incubator > PMC, and also PMC in accumulo, calcite, fluo, phoenix, rya] > * Lokesh Jain [Hadoop, Ozone PMC, Incubator > Committer] > * Marton Elek[Hadoop, Ozone PMC, Incubator > Committer] > * Mingliang Liu [Hadoop
Re: [VOTE] Heron Release 0.20.3-incubating Release Candidate 9
Hi, +1 binding I checked: - incubating in name - signatures and hashes correct - LICENSE and NOTICE good - all source files have ASF headers Thanks, Ming Wen, Apache APISIX PMC Chair Twitter: _WenMing Josh Fischer 于2021年1月14日周四 下午8:56写道： > Hi All, > > We only need 1 more binding vote to get the release out for Heron. Could > an IPMC member please vote on this? > > - Josh > > On Wed, Jan 13, 2021 at 5:48 AM Josh Fischer wrote: > > > Hi, > > > > We need one more binding vote on this RC if anyone has the time. > > > > - Josh > > > > On Mon, Jan 11, 2021 at 8:40 PM Josh Fischer > wrote: > > > >> Hi, > >> > >> We need one more binding vote on this RC if anyone has the time. > >> > >> - Josh > >> > >> On Mon, Jan 11, 2021 at 8:17 PM Josh Fischer > wrote: > >> > >>> We are in progress of building our download page. > >>> > >>> > With the full release of this version we will be putting out a > >>> download page. > >>> > >>> On Mon, Jan 11, 2021 at 8:15 PM Justin Mclean < > jus...@classsoftware.com> > >>> wrote: > >>> > >>>> Hi, > >>>> > >>>> > This isn’t a release page, only a page to select a specific version > >>>> of the > >>>> > documentation. The section that points to GitHub is only a link to > >>>> the repo. > >>>> > >>>> > >>>> Clicking on the link 0.20.2-incubating in the front pages header take > >>>> me to that page, while it not directly called a download page it > looks like > >>>> one and I can’t find another download page. Does another download page > >>>> exist? Most projects have a download page, which list versions and has > >>>> hashes and keys to refry releases. I’m fairly certain that’s a > requirement > >>>> - see [1] > >>>> > >>>> Thanks, > >>>> Justin > >>>> > >>>> 1. https://infra.apache.org/release-download-pages > >>>> - > >>>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > >>>> For additional commands, e-mail: general-h...@incubator.apache.org > >>>> > >>>> >
Re: [VOTE] Graduate Apache Gobblin (Incubating) as a TLP
+1 binding Abhishek Tiwari 于2021年1月11日 周一上午8:45写道： > Thanks Justin, I will close the vote in a few hours. > > Regards, > Abhishek > > On Sun, Jan 10, 2021 at 4:00 PM Justin Mclean > wrote: > > > Hi, > > > > Changing my vote to +1 (binding) > > > > Thanks, > > Justin > > > > - > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > > -- Thanks, Ming Wen, Apache APISIX PMC Chair Twitter: _WenMing
Re: [DISCUSS] Graduate Apache Ratis as TLP
Hi, Uma, Has Ratis completed the podling maturity assessment? which is not necessary, but is helpful for this discussion. Is the name search approved by brand vp? And I only found the vote thread[1] in your dev mailing list, but no discuss thread. Did I miss something? [1] https://lists.apache.org/thread.html/re57bc4c8e38a8e28c7b2b2f96342a93c65276fee88d8d0ef59468a54%40%3Cdev.ratis.apache.org%3E Thanks, Ming Wen, Apache APISIX PMC Chair Twitter: _WenMing Uma gangumalla 于2020年12月24日周四 上午8:43写道： > Dear All, > > The Apache Ratis podling community discussed and voted to graduate as a > TLP. > Please see the vote reference threads below: [3] [4] [5] > > Apache Ratis project is a very active project and the community has grown > well by following the Apache way in the process. It produced several > releases by having diverse people as release managers. > I and the community strongly believe that it's ready for graduation. > Please let me know if you have any feedback. > > If there are no objections, I will start the Vote thread separately. > > Here is the community voted and discussed text which includes board > resolution text: > > > > Dear Community: > > Thanks to everyone who participated in the discussion about graduation[1]. > This is a formal voting thread for Apache Ratis graduation. > > If this vote passes, the next step would be to submit the resolution below > to the Incubator PMC, Then it would vote on sending it on to the Apache > Board. > > Vote: > [ ] +1 - Recommend graduation of Apache Ratis as a TLP > [ ] 0 - I don't feel strongly about it, but don't object > [ ] -1 - Do not recommend graduation of Apache Ratis because... > > The VOTE will open for at least 72 hours. > > We already ran this vote[2] in a private list and it passed there with 14 > binding votes. Here is the opportunity for all community members to > participate in voting and provide your feedback if any. > > > - > The Apache Ratis project has been an Apache incubator project for nearly 3 > year now. Since then the community has grown and followed Apache Way. Some > highlights include: > * 7 releases given ( including 1.0.0 alpha and 0.0.1 alpha ) by having > different people as release managers > * 34 contributors ( from GitHub) > * 27 committers > * 1161 Jiras created, 905 resolved or closed > * 293 pull requests in github > * One of the biggest positives for this community is that most of the > members in this community have a lot of experience in other Apache projects > already. > > Some additional note about the resolution below: > The current PPMC will be transitioned to the PMC. We have invited some of > the mentors in the current PPMC who like to stay involved. > We are also adding Siddharth and Jie Wang into PMC as we believe they are > committed to the project and a good addition to PMC. > > Below is the text for board resolution: > = > > Establish the Apache Ratis 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 A java implementation for RAFT consensus protocol. > > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee > (PMC), to be known as the "Apache Ratis Project", be and hereby is > established pursuant to Bylaws of the Foundation; and be it further > > RESOLVED, that the Apache Ratis Project be and hereby is responsible for > the creation and maintenance of software related to A java > implementation for RAFT consensus protocol; and be it further > > RESOLVED, that the office of "Vice President, Apache Ratis" 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 Ratis > Project, and to have primary responsibility for management of the > projects within the scope of responsibility of the Apache Ratis 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 Ratis Project: > > * Anu Engineer [Hadoop, Ozone PMC, > Incubator Committer] > * Arpit Agarwal [ ASF Member, Hadoop, Ozone, > Incubator PMC] > * Enis Soztutar [ASF Member, Hadoop, HBase, > Incubator PMC and also PMC in curator, gora, phoenix] > * H
Re: [IP CLEARANCE] Apache APISIX ingress controller
With no -1 votes being cast, this IP clearance vote passes by lazy consensus. Thanks, Ming Wen, Apache APISIX PMC Chair Twitter: _WenMing Ming Wen 于2020年11月23日周一 上午11:00写道： > Apache APISIX is receiving a donation of ingress controller [1]. > > Please vote to approve this contribution. > > This is a lazy consensus majority vote, per the IP clearance process [2], > open for at least 72 hours. > > [1] > https://incubator.apache.org/ip-clearance/apisix-ingress-controller.html > [2] https://incubator.apache.org/ip-clearance/ > > Thanks, > Ming Wen, Apache APISIX PMC Chair > Twitter: _WenMing >
Re: [VOTE] Graduate Apache ECharts as TLP (round 2)
+1 non-binding Thanks, Ming Wen, Apache APISIX PMC Chair Twitter: _WenMing kezhenxu94@apache 于2020年11月23日周一 下午6:01写道： > +1 non-binding > > ECharts is one of my favorite visualization projects :) > > — > Zhenxu Ke (柯振旭) > GitHub @kezhenxu94 > > > On Nov 23, 2020, at 4:28 PM, Ovilia wrote: > > > > Hi everyone, > > > > After discussion with the community [1], and a positive vote result [2] > and > > the > > discussion under general mailing list [6], we believe > > ECharts is ready for graduation to a TLP, and we'd like to call on the > vote > > to > > graduate Apache ECharts as TPL. > > > > This is a formal voting thread about Apache ECharts's graduation, please > > Vote: > > [ ] +1 - Recommend graduation of Apache ECharts as a TLP > > [ ] 0 - I don't feel strongly about it, but don't object > > [ ] -1 - Do not recommend graduation of Apache ECharts because... > > > > The VOTE will open for at least 72 hours. > > < > https://www.timeanddate.com/countdown/vote?iso=20201126T1435=237=%5BVOTE%5D+Graduate+Apache+ECharts+as+TLP=serif=1 > > > > > https://www.timeanddate.com/countdown/vote?iso=20201126T1635=237=Graduate+Apache+ECharts+as+TLP=serif=1 > > > > - > > > > X. Establish the Apache ECharts 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 a charting and data visualization > > library written in JavaScript. > > > > NOW, THEREFORE, BE IT RESOLVED, that a Project Management > > Committee (PMC), to be known as the "Apache ECharts Project", > > be and hereby is established pursuant to Bylaws of the > > Foundation; and be it further > > > > RESOLVED, that the Apache ECharts Project be and hereby is > > responsible for the creation and maintenance of software > > related to a charting and data visualization > > library written in JavaScript; and be it further > > > > RESOLVED, that the office of "Vice President, Apache ECharts" 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 ECharts Project, and to have primary responsibility > > for management of the projects within the scope of > > responsibility of the Apache ECharts 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 ECharts Project: > > > >* Houjin Huang > >* Deqing Li > >* Dong Rui > >* Kener Linfeng > >* Kevin A. McGrail > >* Wenli Zhang > >* Shen Yi > >* Shuang Su > >* Siwen Su > >* Junting Wang > >* Zhongxiang Wang > >* Dave Fisher > >* Sheng Wu > >* Zak Wu > > > > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Wenli Zhang > > be appointed to the office of Vice President, Apache ECharts, 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 initial Apache ECharts PMC be and hereby is > > tasked with the creation of a set of bylaws intended to > > encourage open development and increased participation in the > > Apache ECharts Project; and be it further > > > > RESOLVED, that the Apache ECharts Project be and hereby > > is tasked with the migration and rationalization of the Apache > > Incubator ECharts podling; and be it further > > > > RESOLVED, that all responsibilities pertaining to the Apache > > Incubator ECharts podling encumbered upon the Apache Incubator > > Project are hereafter discharged. > > > > -- > > > > A few points to assist in the discussion: > > > > - Released 9 official Apache releases by 3 release managers [3] > > - Voted in 9 committers including 3 PPMC members > > - Achieved 43556 stars (and counting) on GitHub > > - Apache suitable name search has been approve
[IP CLEARANCE] Apache APISIX ingress controller
Apache APISIX is receiving a donation of ingress controller [1]. Please vote to approve this contribution. This is a lazy consensus majority vote, per the IP clearance process [2], open for at least 72 hours. [1] https://incubator.apache.org/ip-clearance/apisix-ingress-controller.html [2] https://incubator.apache.org/ip-clearance/ Thanks, Ming Wen, Apache APISIX PMC Chair Twitter: _WenMing
Re: Request SVN permission for ip-clearance
Hi, John, HTTPS is works. thanks for your help. Thanks, Ming Wen, Apache APISIX PMC Chair Twitter: _WenMing John D. Ament 于2020年11月22日周日 下午11:53写道： > Please make sure you are using https. HTTP is read only. Try again. > > John > > > On Sun, Nov 22, 2020 at 10:37 Ming Wen wrote: > > > hello, incubator, > > I want to submit a new ip clearance to svn[1], but I found that I did > not > > have the permission to write. > > How should I apply? thank you. > > my svn user name: wenming > > > > [1] > > > > > http://svn.apache.org/repos/asf/incubator/public/trunk/content/ip-clearance/ > > > > Thanks, > > Ming Wen, Apache APISIX PMC Chair > > Twitter: _WenMing > > >
Request SVN permission for ip-clearance
hello, incubator, I want to submit a new ip clearance to svn[1], but I found that I did not have the permission to write. How should I apply? thank you. my svn user name: wenming [1] http://svn.apache.org/repos/asf/incubator/public/trunk/content/ip-clearance/ Thanks, Ming Wen, Apache APISIX PMC Chair Twitter: _WenMing
Re: [VOTE] Graduate Apache Flagon (incubating) as a Top Level Project
Hi,Lewis Is there a discussion thread in the incubator? lewis john mcgibbney 于2020年10月8日 周四上午11:13写道： > Hi general@, > > Further to the proposed graduation resolution (https://s.apache.org/0x3wx) > this thread opens an IPMC VOTE on graduating the Apache Flagon (Incubating) > podling as a TLP. The clutch analysis for Flagon looks good with the > podling status page being updated to reflect project health. Flagon has > made several releases during its incubation period. > > Please VOTE as follows > > [ ] +1 - Graduate and establish Apache Flagon as a TLP > [ ] 0 > [ ] -1 - Do not graduate Apache Flagon because... > > This vote will open for at least 72 hours. > > P.S. here is my IPMC-binding +1 > > Thanks > lewismc > > = > > The draft resolution: > > Establish the Apache Flagon 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 thin-client behavioral logging capability >useful for business analytics, usage analytics, usability and >user testing. > >NOW, THEREFORE, BE IT RESOLVED, that a Project Management >Committee (PMC), to be known as the "Apache Flagon Project", >be and hereby is established pursuant to Bylaws of the >Foundation; and be it further > >RESOLVED, that the Apache Flagon Project be and hereby is >responsible for the creation and maintenance of software >related to thin-client behavioral logging capability >useful for business analytics, usage analytics, usability and >user testing, and be it further > >RESOLVED, that the office of "Vice President, Apache Flagon 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 Flagon Project, and to have primary responsibility >for management of the projects within the scope of >responsibility of the Apache Flagon 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 Flagon Project: > > * Joshua Poore > * Lewis John McGibbney > * Laura Mariano > * Clayton Gimenez > * Alex Ford > * Steve York > * Michelle Beard > * Robert Foley > >NOW, THEREFORE, BE IT FURTHER RESOLVED, that Joshua Poore >be appointed to the office of Vice President, Apache Flagon, 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 initial Apache Flagon PMC be and hereby is >tasked with the creation of a set of bylaws intended to >encourage open development and increased participation in the >Apache Flagon Project; and be it further > >RESOLVED, that the Apache Flagon Project be and hereby >is tasked with the migration and rationalization of the Apache >Incubator Flagon podling; and be it further > >RESOLVED, that all responsibilities pertaining to the Apache >Incubator Flagon podling encumbered upon the Apache Incubator >Project are hereafter discharged. > > -- > http://home.apache.org/~lewismc/ > http://people.apache.org/keys/committer/lewismc > -- Thanks, Ming Wen, Apache APISIX & Apache SkyWalking Twitter: _WenMing
Re: [VOTE] Hop proposal
+1 (non-binding) Thanks, Ming Wen, Apache APISIX & Apache SkyWalking Twitter: _WenMing Furkan KAMACI 于2020年9月17日周四 下午7:24写道： > Hi, > > +1 (binding)! > > Kind Regards, > Furkan KAMACI > > On Thu, Sep 17, 2020 at 1:48 PM Maximilian Michels wrote: > > > +1 (non-binding) > > > > On 17.09.20 10:21, Sheng Wu wrote: > > > +1 binding > > > > > > Good luck > > > > > > Sheng Wu 吴晟 > > > Twitter, wusheng1108 > > > > > > > > > Vinayakumar B mailto:vinayakum...@apache.org > >> > > > > > 于2020年9月17日周四 下午4:07写道： > > > > > > +1 (binding) > > > > > > -Vinay > > > > > > > > > On Thu, Sep 17, 2020 at 1:34 PM Jean-Baptiste Onofre > > > mailto:j...@nanthrax.net>> > > > wrote: > > > > > > > +1 (binding) > > > > > > > > Don’t hesitate to ping me if you need help. > > > > > > > > Regards > > > > JB > > > > > > > > > Le 16 sept. 2020 à 15:28, Matt Casters > > > > a écrit : > > > > > > > > > > Hi Apache, > > > > > > > > > > I'd like to call a vote on accepting Hop into the Apache > > Incubator. > > > > > Please see the discussion thread [1]. > > > > > > > > > > Please see the full proposal: > > > > > > > https://cwiki.apache.org/confluence/display/INCUBATOR/HopProposal > > > > > Please cast your vote > > > > > > > > > >[ ] +1 Accept Hop into the Incubator > > > > >[ ] +0 Indifferent to the acceptance of Hop > > > > >[ ] -1 Do not accept Hop because … > > > > > > > > > > The vote will be open at least for 72 hours. > > > > > > > > > > Incubator PMC member votes are binding. Everyone else is > > > welcomed to vote > > > > > too > > > > > (mark them as non-binding if you can)! > > > > > > > > > > Thanks in advance for your time. > > > > > > > > > > Regards, > > > > > Matt > > > > > > > > > > [1] > > > > > > > > > > > > > > > http://apache-incubator-general.996316.n3.nabble.com/DISCUSS-Hop-proposal-td68232.html > > > > > > > > > > > > > > - > > > > To unsubscribe, e-mail: > general-unsubscr...@incubator.apache.org > > > <mailto:general-unsubscr...@incubator.apache.org> > > > > For additional commands, e-mail: > > > general-h...@incubator.apache.org > > > <mailto:general-h...@incubator.apache.org> > > > > > > > > > > > > > > > - > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > >
Re: [VOTE] Graduate Apache IoTDB as TLP
+1 non-binding Good Luck Thanks, Ming Wen, Apache APISIX & Apache SkyWalking Twitter: _WenMing Jialin Qiao 于2020年9月10日周四 下午3:53写道： > Hi, > > +1 (non-binding) > > Thanks, > Jialin Qiao > Apache IoTDB PPMC > > > Xiangdong Huang 于2020年9月10日周四 下午3:42写道： > > > 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: > > [ ] +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.
Re: [DISCUSS] Apache IoTDB Graduation
The community is healthy and active. Congrats Thanks, Ming Wen, Apache APISIX & Apache SkyWalking Twitter: _WenMing jincheng sun 于2020年9月8日周二 上午7:42写道： > Thanks for bring up this DISCUSS Julian！ > > I believe IoTDB will have better and faster development after graduation ！ > > Best, > Jincheng > > > Sheng Wu 于2020年9月7日周一 下午10:00写道： > > > From the brief, seems the community is quite active. Congrats. > > > > Sheng Wu 吴晟 > > Twitter, wusheng1108 > > > > > > Xiangdong Huang 于2020年9月7日周一 下午7:55写道： > > > > > Hi, > > > > > > To make it easy to touch all the important information, I'd like to > > > organize the content > > > from the reference URLs, especially the whole draft of the resolution, > > to > > > this thread: > > > > > > > > > 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 > > > > > > > > > The maturity assessment is done [2], and 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 and a > > > charter [5, 6]. > > > > > > The draft of the resolution is: > > > > > > 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
Re: [DISCUSS] Apache IoTDB considers graduation
Got it, thanks for your detailed explain. Thanks, Ming Wen, Apache APISIX & Apache SkyWalking Twitter: _WenMing Xiangdong Huang 于2020年9月1日周二 下午3:41写道： > Hi Ming, > > > But I only see that iotdb has only 4 releases[1], is there something > wrong? > > Thanks for your check. :D > > Actually we had 9 releases, 0.8.0 ~ 0.8.2, 0.9.0 ~ 0.9.3, 0.10.0, and > 0.10.1. > > But several months ago Dave Fisher shepherd IoTDB and pointed out some > issues [1], > and show the link of [2]. > > Dave Fisher pointed out: > > > (1) Old releases need to be referenced at archives.apache.org and > removed > from the dist.apache.org svn repository. Kudos for already changing to use > downloads.apache.org > > And page [2] pointed out: for incubator project, only 10 files can be > leaved. > > So, we remove all outdated minor version and only leave the most latest > major versions. > > You can use [3] to get the records of all votes for releasing IoTDB. > > [1] > > https://lists.apache.org/thread.html/r9519254a5bce5975be4b9ae90fa58d91d5981b49ece3f4a60fe979e4%40%3Cdev.iotdb.apache.org%3E > > [2] https://incubator.apache.org/clutch/iotdb.html > > [3] > > https://lists.apache.org/list.html?general@incubator.apache.org:lte=24M:%5BVOTE%5D%20IoTDB%20release > > Best, > --- > Xiangdong Huang > School of Software, Tsinghua University > > 黄向东 > 清华大学 软件学院 > > > Ming Wen 于2020年9月1日周二 下午3:27写道： > > > Hi, xiangdong, > > good job for the apache iotdb community. > > But I only see that iotdb has only 4 releases[1], is there something > wrong? > > > > [1] https://dist.apache.org/repos/dist/release/incubator/iotdb/ > > > > Thanks, > > Ming Wen, Apache APISIX & Apache SkyWalking > > Twitter: _WenMing > > > > > > Xiangdong Huang 于2020年9月1日周二 下午3:19写道： > > > > > Hi, > > > > > > let me supply more info about the discussion. > > > > > > 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 > > > > > > We believe we have built a meritocratic, open collaborative process, > the > > > Apache way. :D > > > > > > And, will update the draft of the resolution after a consensus in our > > > community. > > > > > > Best, > > > --- > > > Xiangdong Huang > > > School of Software, Tsinghua University > > > > > > 黄向东 > > > 清华大学 软件学院 > > > > > > > > > Julian Feinauer 于2020年9月1日周二 下午2:51写道： > > > > > > > Hi folks, > > > > > > > > on the IoTDB mailing list we already had a discussion about our > > maturity > > > > for graduation, see [1] and recently started a vote if the community > > > wants > > > > to start the graduation process [2]. > > > > > > > > We also filled all materials necessary, see e.g. the maturity > > evaluation > > > > [3] and got positive feedback from our mentors. > > > > > > > > So I just wanted to inform this list and also start a discussion > about > > > > others thoughts about IoTDBs graduation. > > > > > > > > Best! > > > > Julian > > > > > > > > > > > > [1] > > > > > > > > > > https://lists.apache.org/thread.html/r7607cbf6ff2020dc7e7cc27eb698ce265b768ed2a63d3e353c2dc572%40%3Cdev.iotdb.apache.org%3E > > > > [2] > > > > > > > > > > https://lists.apache.org/thread.html/r5fe46923c8625601a25e51340f1df6a2b6472e52dfa2648df116f618%40%3Cdev.iotdb.apache.org%3E > > > > > > > > [3] > > > > > > > > > > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=148645763 > > > > > > > > > > > > > > > > > >
Re: [DISCUSS] Apache TVM Graduation
hello, tianqi, thanks for your detailed response. I have another question: https://tvmconf.org/ who has control of this domain name? Looks like it's controlled by https://github.com/tvmconf. Thanks, Ming Wen, Apache APISIX & Apache SkyWalking Twitter: _WenMing Tianqi Chen 于2020年8月31日周一 下午1:08写道： > Thanks Justin, Henry, Dave, Ming, Matt for helpful feedbacks. > > Personally I find the current conversation a good living example of the > Apache way for consensus building :) > Thanks to the helpful feedback we have resolved several issues. > > In order to clarify the situation, please allow me to dissect and summarize > the current situation. > There are a few categories of topics (related to the Apache way) this > thread have touched so far: > > Compliance > > Compliance is what every project is required to do. These policies are set > to protect Apache’s brand, > encourage community over code and set a common foundation for the projects. > Usually a compliance is > well documented (as per-apache way, what is not documented did not happen). > The TVM PPMC has been diligently > upholding compliances, including, but not limited to > > - T0 Project website hosted at ASF https://tvm.apache.org/. > - T1 Produce apache release, no cat-X code. > - T2 No advertising non-release items as Apache release. > - T3 Protect Apache brand, working with trademark to resolve branding > concerns. > - T4 Clearly marks third party artifacts and makes sure they comply with > trademark policies. > - T5 Open development: everyone happens (also) happens on dev@ > - T6 Consider all forms of contributions for committer nomination. > - T7 Make sure release processes are clearly documented, reproducible by > any committers. > > Customary > > There are also a few topics that touch on what many Apache(incubating) > projects do, but are not (yet) strict compliance. > The TVM PPMC could improve on. Specifically, the following item: > > - K0 Usually an incubator project produces three apache releases, with > multiple release managers. > So far TVM PPMC produced two apache releases by one manager (many PPMC > members helped on the two releases). > > Community > > Finally, the “community over code” is one of the most important factors of > the Apache way. > The TVM PPMC has been working very hard to foster a healthy, diverse and > independent community, > and will continue to do so. > > - C0: Consider all forms of contributions as merit. > - C1: Encourage community diversity by only nominating people from > different organizations. > - C2: Actively discusses, and brings in new committers from diverse > backgrounds. > The community grows healthily and is quite vibrant. > > Concerns > > - X0: Right now, Justin and Ming rightfully point out that while the TVM > community has fulfilled T7, we could improve in K0. > - X1: The subdomain name (discuss.tvm.ai) is something that we would like > to work with trademarks@ to clarify. > According to the current policy, the apache trademark cannot be used > “when the content of that domain is related > to any related software products or services”. The subdomain is not > providing any software product or deriving services > related to tvm. The TVM PPMC would be more than happy to follow > trademark’s suggestion. > > Please let me know if the summary could be improved in any way, and we > would also welcome more feedback. > > Thank you! > TQ > > On Fri, Aug 28, 2020 at 9:08 PM Tianqi Chen wrote: > > > I would like to revisit a bit about the release topic to shed light about > > the release process. > > The TVM PPMC has always been focusing on producing high quality releases. > > > > - The project has produced five major (non-apache) releases prior joining > > Apache > > - While most incubator projects start with a DISCLAIMER-WIP, the TVM > > community strives to keep the release quality high and uses the > DISCLAIMER > >in the beginning of the first release[1]. The first release contains a > > few rough edges and gets resolved very quickly thanks to the feedback > from > > Justin and other IPMC members. > >The second release is super smooth. > > - Multiple PMC members work together to generate these releases. > > > > TQ > > > > - [1] > > > https://lists.apache.org/thread.html/ad19634352f97d0a5b2bec866bcdecd556ca414cc6d4487b2282ce10%40%3Cgeneral.incubator.apache.org%3E > > > > On Fri, Aug 28, 2020 at 8:54 PM Tianqi Chen wrote: > > > >> We have also talked to Apache INFRA about the use of the > >> https://ci.tvm.ai/ due to the need of special setups in terms of GPU > &g
Re: [VOTE] Graduate Apache TVM as TLP
my -1 non-binding. see discuss thread about my concerns. Justin Mclean 于 2020年8月29日周六 上午5:59写道： > HI, > > I’m -1 (binding), please see the discussion thread for my concerns. > > Thanks, > Justin > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [DISCUSS] Apache TVM Graduation
I think only two releases and only one release manager are blocking issues. Considering that TVM merges 150 PRs a month on average, but only two releases within a year and a half, that is, users use codes that are much behind the master, which is not friendly to the community. Second, there is no conflict between high-quality releases and frequent releases. Many Apache projects have maintained frequent and high-quality releases. Third, since there is a good release document, why is there no other ppmc to serve as release manager? Tianqi Chen 于 2020年8月29日周六 上午9:51写道： > Thanks Matt! > > That was indeed the approach we used before. The main problem of this > approach is > - There could be certain upstream changes (say tensorflow get updated) that > may not retrigger the rebuild > - The CI instance itself can quickly get crowded by the historical cached > images and causes disk overflow problems. > - Overall we find it is very hard to reproduce the CI error when there is a > problem because of the potential mismatch(due to stale build) > > So the community switched to using a stable binary tag as for more stable > env without blocking the CI, while periodically updating > these images when this is a dependency change. > > TQ > > On Fri, Aug 28, 2020 at 6:47 PM Matt Sicker wrote: > > > Is there even a need to upload the Docker images for CI? Docker > recognizes > > layers by checksums, so CI build agents will cache the image layers > > regardless of whether or not you upload them to Docker Hub. Layers get > > rebuilt when the Docker file changes or you force an update. > > > > On Fri, Aug 28, 2020 at 20:12 Tianqi Chen wrote: > > > > > Thanks Justin and Henry for the discussion thread. > > > > > > > > > > > > Please allow me to dissect and summarize again some of the discussion > > > > > > points:) > > > > > > > > > > > > C0: Docker Image > > > > > > - There was a mis-understanding that the docker image like ci-gpu > > > > > > contains tvm. They do not, and instead contain an environment to > > > > > > build and run test cases. > > > > > > - The thirdparty binary cache is used to speed up the test build. > Anyone > > > > > > could build these binaries from a TVM source. > > > > > > - To avoid confusion about the branding, we have renamed the docker hub > > > > > > name to > > > > > > a different name that does not contain tvm so that it is clear as a > > > > > > thirdparty. > > > > > > > > > > > > C1: Pointing to Apache Release > > > > > > - The PPMC 100% agree that we should produce high-quality Apache > > > > > > compatible releases, and refer to them in the documents. > > > > > > - The installation documentation points to the official release > download > > > > > > page [1]. > > > > > > - There is a for developer section, which gives instructions to > > developers > > > > > > about > > > > > > how to clone the code from the git repo. > > > > > > > > > > > > C2: Number of releases > > > > > > - The PPMC wants to produce high quality releases according to feature > > > > > > plan coordinated with the community, rather than creating more > > releases. > > > > > > - The release process is well documented[2], > > > > > > - Per incubator policy[2], number of releases is not a hard bar for > > > > > > graduation. > > > > > > "Podlings do not need to actually publish a release...". Instead the > > most > > > > > > important > > > > > > thing is the demonstration of being able to cut apache release. > > > > > > - Besides the release process being well documented and there are > already > > > > > > two high-quality releases(without WIP). The PMC contains several > Apache > > > > > > members > > > > > > who have previous experiences in cutting releases in TLP projects. > > > > > > We are very confident that the PMC can continue to do so. > > > > > > > > > > > > C3: The discourse forum > > > > > > - The discourse forum, like the use of github, is mainly a way for user > > > > > > community to > > > > > > engage with the project. > > > > > > - The usage of discourse forum is voted by the community[3] > > > > > > - The community follows the public archive principle, which means > > > > > > everything is archived > > > > > > to mail-lists. Again, everything happens (also) happens on a > mail-list. > > > > > > - The discourse forum is currently maintained by a few PMC members as > > > > > > volunteers, > > > > > > as a thirdparty service to the community. > > > > > > - Again, the development happens in github, everything mirrored in dev@ > . > > > > > > The existence of the forum > > > > > > would not block the development. > > > > > > > > > > > > Finally, to summarize. I believe one of the main reasons behind these > > > > > > issues are trust rather than procedural. > > > > > > As a ASF member, I am certainly strive to make sure the related > volunteer > > > > > > maintained resources > > > > > > will continue beyond a certain individual by many ways including: > > > > > > > > > > >
Re: [DISCUSS] Apache TVM Graduation
> As per apache way, everything happens (also happens) on dev@tvm. We try to > set up the mechanism to enable maximum participation from the community, > while complying with ASF rules :) > The emails from the dev@tvm are also forwarded to the github thread. The mailing list seems to be a backup of github issues, even for something as important as announcing a new committer [1] [2]. I am not sure if this is a problem, but I have not seen such an operation in other apache projects. [1] https://lists.apache.org/thread.html/r17bdb633ec3ed1f8f80502705f9cc8cc642b189ab99cc2958847c1ac%40%3Cdev.tvm.apache.org%3E [2] https://github.com/apache/incubator-tvm/pull/4636 Thanks, Ming Wen, Apache APISIX & Apache SkyWalking Twitter: _WenMing Tianqi Chen 于2020年8月28日周五 上午1:58写道： > Thank you Dave! > > (1) They have invented a new position between Contributor and Committer > > called “Reviewer”. I’m not sure why this was done. It seems to me that > > these individuals should just become Committers. > > > > Reviewer is not an official position, but as a way for us to encourage > reviews and find potential candidates for committerships. > We use the following disclaimer which we sent during discussion a reviewer > case and not vote is carried out(to lower bar of entry) > > Background: A Reviewer is not an official role, the community use this > way to recognize potential committers early and bring them to the > project development. Given the reviewer role is not official, we will > only hold a discussion instead of a formal vote. We continue to follow > the community’s principle to only nominate someone from a different > organization. > > The recognition of (un-official) reviewer is voted by the community as part > of Apache transition plan > > https://lists.apache.org/thread.html/c34b728f01d1030146594e47e0706cd1990ed731d06e3c179b7d501a%40%3Cdev.tvm.apache.org%3E > > We strongly believe in nurturing contributions, welcome members to the > community, and help the community to grow organically under the Apache way. > The community is actively bringing in new committers, and we are doing so > at a monthly rate. > To encourage diversity and healthy growth the PPMC members strive to make a > more diverse community by only nominating people from a different > organization. > So there could be cases where a person from my own organization that I > think should be nominated as a committer, but I wait until the person get > recognized by a fellow PMC member > from another organization. This wait usually won't be too long. Even > better, the community members work together with each other, > since the most important factor is after all the community. > > (2) All discussions are threaded in GitHub and then reflected into the > > dev@tvm mailing list. I just find this strange. > > > > As per apache way, everything happens (also happens) on dev@tvm. We try to > set up the mechanism to enable maximum participation from the community, > while complying with ASF rules :) > The emails from the dev@tvm are also forwarded to the github thread. > > > > > Also, the discussion thread looks like a vote. Nothing is really > discussed > > about satisfying graduation requirements. > > > > Did TVM fill out a Maturity Model? > > > > Please see the maturity model here > > https://docs.google.com/document/d/18nyAH-fcptVezAxPQe6H3FeTKPRkujOp1tc1YRSPLok/edit?usp=sharing > The maturity model is attached as part of the community discussion as > well(inlined in the email when community model is mentioned. > > TQ > > > On Thu, Aug 27, 2020 at 10:43 AM Dave Fisher wrote: > > > > > > > > On Aug 27, 2020, at 10:27 AM, Dave Fisher wrote: > > > > > > Hi - > > > > > > I am bothered by two things that TVM does. > > > > > > (1) They have invented a new position between Contributor and Committer > > called “Reviewer”. I’m not sure why this was done. It seems to me that > > these individuals should just become Committers. > > > > Looking a little more closely it seems that Reviewers ought to be PMC > > Members. Please explain. > > > > > > > > (2) All discussions are threaded in GitHub and then reflected into the > > dev@tvm mailing list. I just find this strange. > > > > > > Also, the discussion thread looks like a vote. Nothing is really > > discussed about satisfying graduation requirements. > > > > > > Did TVM fill out a Maturity Model? > > > > I see you held that back until the VOTE thread. > > > > > > > > Regards, > > > Dave > > > > >
Re: [DISCUSS] Apache TVM Graduation
I think Apache TVM need more Apache releases and more release manager. TVM has two apache releases(12/05/2019 and 07/10/2020), and ONLY one release manager(liuyizhi) [1]. [1] https://incubator.apache.org/clutch/tvm.html Thanks, Ming Wen, Apache APISIX & Apache SkyWalking Twitter: _WenMing Henry Saputra 于2020年8月28日周五 上午4:44写道： > Yes, as Tianqi has mentioned, the PPMC members watch the commits and > development of TVM podling using Github notifications, which sent to dev@ > list. > So, they are still in the podling list. > > And of course we can always review the commits@ list via Pony mail [1] > when > needed. > > > - Henry > > [1] https://lists.apache.org/list.html?comm...@tvm.apache.org > > On Thu, Aug 27, 2020 at 12:16 PM Tianqi Chen wrote: > > > Thanks Dave! > > > > > > > With no one subscribed to commits@ how is the PPMC watching the > > codebase? > > > > > > > I believe most of us watch the codebase through github instead of the > > commits@. > > Note that the github discuss issues (VOTE, RFC, COMMUNITY) are forwarded > to > > dev@(rather than commits), so we can make sure that anyone who > > subscribed to dev@ can follow overall development, without having to be > > overwhelmed by the information in raw gituhb notifications. > > > > With only one PPMC member subscribed it would be better not to have > > > security list and instead count on securty@apache to inform > private@tvm. > > > > > > I agree that is our oversight, I created the security@mail-list, but > later > > realized that we can count on securty@apache, the current security > guide > > https://tvm.apache.org/docs/dev/security.html already points to > > security@apache > > but I forget to ask infra to remove the list > > > > To address the question about bringing in people to the committers. > > The PPMC totally agrees about bringing in new members actively to the > > community! And we are doing so in a quite steady fashion. > > > > I agree that there could be some cases where a person's proposal could be > > slightly delayed, because I try to refrain from proposing new committers > > from our own orgs. > > But overall we find that our community members interact with each > > other(outside their organizations) more often, and usually my fellow PMC > > members bring them to the commiterships in a timely manner:) > > I also think a slight lag is understandable given that most PPMC members > > are volunteers from a diverse group and operate on their part time > > capacity. > > > > Given both principles (not nominating from same org and un-official > > reviewer) are voted by the community, and we use explicit disclaimer for > > the cases, I believe it still works under the ASF framework. Just like > the > > un-official maturity model used by the incubator, which serves a goal to > > the community to grow, rather than as a gatekeeper > > > > Again, we strive to continue the effort of bringing in new members to the > > community, and nurturing community growth as we do so now. > > > > TQ > > > > > > > > > Regards, > > > Dave > > > > > > > > > > > Hope these answers help clarify your concerns and questions about the > > > > Apache TVM community. > > > > > > > > Thanks, > > > > > > > > - Henry > > > > > > > > On Thu, Aug 27, 2020 at 10:58 AM Tianqi Chen > > wrote: > > > > > > > >> Thank you Dave! > > > >> > > > >> (1) They have invented a new position between Contributor and > > Committer > > > >>> called “Reviewer”. I’m not sure why this was done. It seems to me > > that > > > >>> these individuals should just become Committers. > > > >>> > > > >> > > > >> Reviewer is not an official position, but as a way for us to > encourage > > > >> reviews and find potential candidates for committerships. > > > >> We use the following disclaimer which we sent during discussion a > > > reviewer > > > >> case and not vote is carried out(to lower bar of entry) > > > >> > > > >> Background: A Reviewer is not an official role, the community use > this > > > >> way to recognize potential committers early and bring them to the > > > >> project development. Given the reviewer role is not official, we > will > > > >> only hold a discussion instead of a fo
Re: [VOTE] Graduate Apache ECharts (incubating) as a top level project
Hi, guo jiwei, This is not the incubator vote thread. you should support them in d...@echarts.apache.org. Thanks, Ming Wen, Apache APISIX & Apache SkyWalking Twitter: _WenMing guo jiwei 于2020年8月19日周三 下午12:39写道： > +1 (non-binding) > > Regards > Jiwei Guo (Tboy) > > > On Wed, Aug 19, 2020 at 12:33 PM Ovilia wrote: > > > FYI. > > Apache ECharts (incubating) is running a community graduation vote now. > > > > Thanks > > > > *Ovilia* > > > > Forwarded Conversation > > Subject: [VOTE] Graduate Apache ECharts (incubating) as a top level > project > > > > > > From: Ovilia > > Date: Mon, Aug 17, 2020 at 11:36 AM > > To: dev > > > > > > Hi all, > > > > Hello all, > > After our discussion about readiness for graduation to TLP on the dev > > mailing list [8], I would like to call a VOTE for Apache ECharts > graduating > > as a top level project. > > > > If this vote passes, the next step would be to submit the resolution > below > > to the Incubator PMC, who would vote on sending it on to the Apache > Board. > > > > Vote: > > [ ] +1 - Recommend graduation of Apache ECharts as a TLP > > [ ] 0 - I don't feel strongly about it, but don't object > > [ ] -1 - Do not recommend graduation of Apache ECharts because... > > > > The VOTE will open for at least 72 hours. > > > > - > > > > X. Establish the Apache ECharts 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 a charting and data visualization > > library written in JavaScript. > > > > NOW, THEREFORE, BE IT RESOLVED, that a Project Management > > Committee (PMC), to be known as the "Apache ECharts Project", > > be and hereby is established pursuant to Bylaws of the > > Foundation; and be it further > > > > RESOLVED, that the Apache ECharts Project be and hereby is > > responsible for the creation and maintenance of software > > related to a charting and data visualization > > library written in JavaScript; and be it further > > > > RESOLVED, that the office of "Vice President, Apache ECharts" 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 ECharts Project, and to have primary responsibility > > for management of the projects within the scope of > > responsibility of the Apache ECharts 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 ECharts Project: > > > > * Houjin Huang > > * Deqing Li > > * Dong Rui > > * Kener Linfeng > > * Kevin A. McGrail > > * Wenli Zhang > > * Shen Yi > > * Shuang Su > > * Siwen Su > > * Junting Wang > > * Zhongxiang Wang > > * Dave Fisher > > * Sheng Wu > > * Zak Wu > > > > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Wenli Zhang > > be appointed to the office of Vice President, Apache ECharts, 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 initial Apache ECharts PMC be and hereby is > > tasked with the creation of a set of bylaws intended to > > encourage open development and increased participation in the > > Apache ECharts Project; and be it further > > > > RESOLVED, that the Apache ECharts Project be and hereby > > is tasked with the migration and rationalization of the Apache > > Incubator ECharts podling; and be it further > > > > RESOLVED, that all responsibilities pertaining to the Apache > > Incubator ECharts podling encumbered upon the Apache Incubator > > Project are hereafter discharged. > > > > > > - > > > > More information: > > > > - Asse
Re: [VOTE] Accept EventMesh into Apache Incubator
-1 non-binding. As mentioned in the discussion thread, the proposal should reflect the real situation of the project, and the contributors of the project should make active efforts to develop the community on public channels, such as github. Sheng Wu 于 2020年8月15日周六 上午11:49写道： > -1 binding > > My concerns are clear in the discussion thread. > The community is not caring for the community/user feedback from what I > have seen, such as GitHub issue discussions. > ASF and ASF incubator should never a pre-condition of the OSS community is > active or not. > > Sheng Wu 吴晟 > Twitter, wusheng1108 > > > Eason Chen 于2020年8月14日周五 下午7:57写道： > > > Hi, > > > > > > After the discussion of EventMesh proposal (discussion thread is > here[1]), > > I would like to call a VOTE to accept it into the Apache Incubator. > > > > > > Please cast your vote: > > > > > > [ ] +1, bring EventMesh into Incubator > > [ ] +0, I don't care either way > > [ ] -1, do not bring EventMesh into Incubator, because... > > > > > > The vote will open at least for 72 hours and only votes from the > Incubator > > PMC are binding. > > > > > > > > The project's proposal is available at [2]. > > > > > > [1] > > > https://lists.apache.org/thread.html/r12b7357f2a9458e6d6719558f36c0bbf7f786771d1f727848d5170b4%40%3Cgeneral.incubator.apache.org%3E > > [2] > https://cwiki.apache.org/confluence/display/INCUBATOR/EventMeshProposal >
Re: [DISCUSS] EventMesh Proposal
> Thanks for the honesty, I prefer you should adjust the proposal to match > the reality. Such as > 1. Just open-sourced > 2. Have a risk of being an orphaned project > 3. Community development would be a challenge As mentioned in wusheng’s previous email, the challenge should be stated in the proposal. Thanks, Ming Wen, Apache APISIX & Apache SkyWalking Twitter: _WenMing Eason Chen 于2020年8月14日周五 上午10:52写道： > Thanks for your help and answers @Duane, i will initiate the voting > processs later if you have no other questions. > > > > > --原始邮件-- > 发件人: > "general" > < > duane.pa...@gmail.com; > 发送时间:2020年8月11日(星期二) 凌晨0:16 > 收件人:"legal-discuss" 抄送:"general" 主题:Re: [DISCUSS] EventMesh Proposal > > > > I work for Solace and have consulted internally to confirm that we do not > have any copyright or trademark on the term “Event Mesh”. It’s true it is > something our products are closely aligned with, but it is an industry term > that has been adopted by Gartner and is gaining traction in the industry. > Solace does not oppose the term being used in other applicable products or > projects. > > +1 (non-binding) on the idea. > > Cheers, > Duane > > On Thu, Aug 6, 2020 at 11:51 AM heng du wrote: > > Hi @Michael > > Thanks for your advice. As far as I know, Solace doesn't have a > product > called Eventmesh, They're just using that name to promote their PubSub > platform. > > But in order not to cause trouble in the future, I also ask guys of > Apache > Brand to help check whether this name is appropriate. For us, we've > been > using the name EventMesh for a long time, and we want to keep it so > that > users can get better product positioning from the name. > > And base on this document[1], we searched in the U.S. Patent > Office[2] and > found nothing inappropriate. > > [1] https://incubator.apache.org/guides/names.html > [2] https://www.uspto.gov/trademark > > Thanks > Henry > > Michael André Pearce 于2020年8月6日周四 > 下午3:33写道： > > Hi > > Im PMC member from ActiveMQ project. > I like the idea, nice. +1 on it as a project idea. > > I am though a little -1 on the name of the project, I would > recommend > that an alternative name for the project is found as there maybe > a conflict > in rights ability to copyright and trademark to it. > > I’m aware there is a commercial vendor messaging company called > Solace, > where they use and market their product with heavy use of the > name Event > Mesh, you can see this just googling event mesh, brings back many > hits to > their products, marketing material and other records, so they may > hold a > heavy claim to this name. > > Best > Michael > > On 4 Aug 2020, at 18:33, Kevin Ratnasekera < > djkevincr1...@gmail.com > wrote: > > Hi Easen, > > +1, Having worked in a similar domain so far, I have to say > this is an > interesting project. If you are seeking new mentors, please > consider > adding > me as a mentor to the project. > > Regards > Kevin > > On Tue, Aug 4, 2020 at 3:34 PM Eason Chen < > daerduoc...@qq.com wrote: > > Good time of the time to all! > > > I'd like to bring this new interesting project for the > discussion, > comments and feedback with the aim of starting a formal > [VOTE] of its > acceptance into Incubator. > > > People behind this project aren't new to Apache: some of > them were > behind > the Apache RocketMQ, which I consider a huge > success(especially in > China)as > the community is literally thriving almost 3 years after > the > graduation. > > > I have been involved a little bit with this project when > it just > started > in WeBank a few years ago. And I'd like to emphasize > that the community > however small it might look so far, has been aligned > with Apache ways > of > doing things. Heng Du (from RocketMQ PMC) is very > instrumental in > tirelessly helping this group to learn what it means to > be a truly open > source project. > > > The code is already under ALv2 and is publicly > available. As you will > see > it has a lot of dependency connections with the rest of > Apache > ecosystem > and IMO will fit very well here and continue to grow the > community. > > > The project's proposal is available at [1]. > > > Thank you very much for the feedback you're willing to > provide! > > > nbsp;With best regards, > > nbsp;Eason Chen > > > > [1] > > > https://cwiki.apache.org/confluence/display/INCUBATOR/EventMeshProposal > > <https://cwiki.apache.org/confluence/display/INCUBATOR/EventMeshProposal> > ; > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: > general-h...@incubator.apache.org > >
Re: [DISCUSS] EventMesh Proposal
There are now 10 contributors of this project, but seven of them started the first commit in July. That's a little strange. Thanks, Ming Wen, Apache APISIX & Apache SkyWalking Twitter: _WenMing Eason Chen 于2020年8月6日周四 下午5:44写道： > Hi, wenming > 1. I believe more people will join in the future ;) > 2. Sure > > > > > --原始邮件-- > 发件人: > "general" > < > wenm...@apache.org; > 发送时间:2020年8月6日(星期四) 下午5:23 > 收件人:"general" > 主题:Re: [DISCUSS] EventMesh Proposal > > > > Hi, Eason, > It's an interesting project. And I have a few questions and > it would be great if you could help: > 1. According to github's statistics[1], most of the code was contributed by > yourself. > So if you're on vacation, this project will not easy to move forward. > 2. An external dependency `logback` is LGPL license, which is Category X. > Can this dependency be removed? > > [1] https://github.com/WeBankFinTech/EventMesh/graphs/contributors > > Thanks, > Ming Wen, Apache APISIX Apache SkyWalking > Twitter: _WenMing > > > Eason Chen > Good time of the time to all! > > > I'd like to bring this new interesting project for the discussion, > comments and feedback with the aim of starting a formal [VOTE] of its > acceptance into Incubator. > > > People behind this project aren't new to Apache: some of them were > behind > the Apache RocketMQ, which I consider a huge success(especially in > China)as > the community is literally thriving almost 3 years after the > graduation. > > > I have been involved a little bit with this project when it just > started > in WeBank a few years ago. And I'd like to emphasize that the > community > however small it might look so far, has been aligned with Apache ways > of > doing things. Heng Du (from RocketMQ PMC) is very instrumental in > tirelessly helping this group to learn what it means to be a truly > open > source project. > > > The code is already under ALv2 and is publicly available. As you will > see > it has a lot of dependency connections with the rest of Apache > ecosystem > and IMO will fit very well here and continue to grow the community. > > > The project's proposal is available at [1]. > > > Thank you very much for the feedback you're willing to provide! > > > nbsp;With best regards, > > nbsp;Eason Chen > > > > [1] > > https://cwiki.apache.org/confluence/display/INCUBATOR/EventMeshProposal
Re: [DISCUSS] EventMesh Proposal
Hi, Eason, It's an interesting project. And I have a few questions and it would be great if you could help: 1. According to github's statistics[1], most of the code was contributed by yourself. So if you're on vacation, this project will not easy to move forward. 2. An external dependency `logback` is LGPL license, which is Category X. Can this dependency be removed? [1] https://github.com/WeBankFinTech/EventMesh/graphs/contributors Thanks, Ming Wen, Apache APISIX & Apache SkyWalking Twitter: _WenMing Eason Chen 于2020年8月4日周二 下午6:04写道： > Good time of the time to all! > > > I'd like to bring this new interesting project for the discussion, > comments and feedback with the aim of starting a formal [VOTE] of its > acceptance into Incubator. > > > People behind this project aren't new to Apache: some of them were behind > the Apache RocketMQ, which I consider a huge success(especially in China)as > the community is literally thriving almost 3 years after the graduation. > > > I have been involved a little bit with this project when it just started > in WeBank a few years ago. And I'd like to emphasize that the community > however small it might look so far, has been aligned with Apache ways of > doing things. Heng Du (from RocketMQ PMC) is very instrumental in > tirelessly helping this group to learn what it means to be a truly open > source project. > > > The code is already under ALv2 and is publicly available. As you will see > it has a lot of dependency connections with the rest of Apache ecosystem > and IMO will fit very well here and continue to grow the community. > > > The project's proposal is available at [1]. > > > Thank you very much for the feedback you're willing to provide! > > > With best regards, > > Eason Chen > > > > [1] > https://cwiki.apache.org/confluence/display/INCUBATOR/EventMeshProposal
Re: [VOTE] Release Apache TubeMQ (Incubating) 0.5.0-incubating RC0
+1 non-binding I checked: - incubating in name. - DISCLAIMER exists (WIP). - signature and hashes correct. - LICENSE is not good which contains a lot of dependencies that shouldn't be there. - All files have ASF headers, but some of files's ASF header contains html tag [1]. > - LICENSE incorrectly list dependancies rather than what is bundled in the release. agreed, you only need to add license to LICENSE if it's code bundled in the release, Instead of all dependencies. You can refer to how TLP handles that, for example sykwalking[2]. [1] https://github.com/apache/incubator-tubemq/blob/0.5.0-incubating-RC0/tubemq-server/src/main/java/org/apache/tubemq/server/Server.java#L8 [2] https://github.com/apache/skywalking/blob/master/LICENSE#L204 Thanks, Ming Wen, Apache APISIX & Apache SkyWalking Twitter: _WenMing Justin Mclean 于2020年8月2日周日 下午6:15写道： > Hi, > > +1 (binding) > > However if it wasn’t for the Incubating WIP disclaimer I would be -1. > > The LICENSE issues where brought up last time [1] It is best if some work > is done to improve each release so it better than the last. Please ask your > mentors to help with this. > > I checked: > - incubating in names. > - signature and hashes correct. > - LICENSE incorrectly list dependancies rather than what is bundled in the > release. > - LICENSE don’t list point to full license text so is unlikely yo comply > with 3rd party license terms. > - NOTICE is very likely missing information from other Apache license > NOTICE files, but with all dependancies included it’s hard to know for sure. > - All files have ASF headers > - Failed to compile from source > > I didn’t check the binary artefacts. > > It would be interesting to know where these come from [2] and how they > were licensed. > > More concerning is why teh build is failing wth this: > [ERROR] Failed to execute goal on project tubemq-all: Could not resolve > dependencies for project org.apache.tubemq:tubemq-all:pom:0.5.0-incubating: > Could not find artifact > org.apache.tubemq:tubemq-server:tar.gz:bin:0.5.0-incubating in > berkeleydb-je (https://download.dcache.org/nexus/repository/berkeleydb-je/) > -> [Help 1] > > Why does the source release depend on the binary one? > > Thanks, > Justin > > 1. > https://lists.apache.org/thread.html/r875e3e1abe41369611e7c0c6610ac29af35c552cddc3088e4df3f99c%40%3Cgeneral.incubator.apache.org%3E > 2. ./resources/assets/public/css/fonts/icon.* > > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [VOTE] Release Apache TubeMQ (Incubating) 0.5.0-incubating RC0
Hi, Goson, I think you can look for your mentors to vote. None of them have voted yet. Thanks, Ming Wen, Apache APISIX & Apache SkyWalking Twitter: _WenMing Goson zhang 于2020年8月1日周六 下午10:55写道： > Can you review and vote for the release 0.5.0-incubating-RC0? > > I have sent the voting email for the release 0.5.0-incubating-RC0 five days > ago, but no one has voted yet. With the help of 101+ external contributors, > TubeMQ-0.5.0-incubating-RC0 has been greatly improved in terms of usability > and Improvement; at the same time, it is the first release of the TubeMQ > project with external contributions, and the second release of the project > built according to the Apache rules. > > And, I am very confused about this status, if you can provide some > suggestions for improvement I would be very grateful! > > Looking forward to your help, thanks !! > > Goson zhang 于2020年7月27日周一 上午11:17写道： > > > Hello Incubator Community, > > > > This is a call for a vote to release Apache TubeMQ (Incubating) > version > > 0.5.0-incubating RC0 > > > > The Apache TubeMQ community has voted on and approved a proposal to > > release > > Apache TubeMQ (Incubating) version 0.5.0-incubating RC0 > > > > We now kindly request the Incubator PMC members review and vote on > > this > > incubator release. > > > > TubeMQ community vote thread: > > • > > > https://lists.apache.org/thread.html/rbc5807429f0614e9130fc98dffb84521270b43e995d7f623ff9d31df%40%3Cdev.tubemq.apache.org%3E > > > > Vote result thread: > > • > > > https://lists.apache.org/thread.html/rc6ec5b024bd15fbe766c610121fcc0c0b2ce139e2dd1cbf7c76e3eea%40%3Cdev.tubemq.apache.org%3E > > > > The release candidate: > > • > > > https://dist.apache.org/repos/dist/dev/incubator/tubemq/0.5.0-incubating-RC0/ > > > > Git tag for the release: > > • > https://github.com/apache/incubator-tubemq/tree/0.5.0-incubating-RC0 > > > > Release notes: > > • > > > https://github.com/apache/incubator-tubemq/releases/tag/0.5.0-incubating-RC0 > > > > The artifacts signed with PGP key 6011859AEFC308DD, corresponding to > > gosonzh...@apache.org, that can be found in keys file: > > • https://dist.apache.org/repos/dist/dev/incubator/tubemq/KEYS > > > > The vote will be open for at least 72 hours or until a necessary > > number of votes are reached. > > > > Please vote accordingly: > > > > [ ] +1 approve > > [ ] +0 no opinion > > [ ] -1 disapprove with the reason > > > > Thanks, > > On behalf of Apache TubeMQ (Incubating) community > > >
Re: [DISCUSS] project proposal - Apache Sedona
Thanks for your explanation. Thanks, Ming Wen, Apache APISIX(incubating) & Apache SkyWalking Twitter: _WenMing Jia Yu 于2020年7月14日周二 上午11:01写道： > Hello Ming Wen, > > Thanks for the question! > > Harry Zhu is the contributor of Sedona R binding. His code is a submodule > of the main repo > https://github.com/DataSystemsLab/GeoSpark/tree/master/contrib, and thus > was not counted towards the main statistics. The main repo of GeoSpark R is > here https://github.com/harryprince/geospark > > We will soon merge his code into the main repo. This way, his contribution > will be shown in the main statistics. > > I hope this answers your question! :) > > Jia > > > > Jia Yu > > Ph.D. in Computer Science > > Arizona State University <http://www.asu.edu/> > > Reach me via: Homepage <http://jiayuasu.github.io/> | GitHub > <https://github.com/jiayuasu> > > > On Mon, Jul 13, 2020 at 7:26 PM Ming Wen wrote: > > > > The initial committers are contributors who made significant > > contributions to Apache Sedona based on the GitHub statistics: > > https://github.com/DataSystemsLab/GeoSpark/graphs/contributors > > > > hello, Jia Yu, > > I have a question. I saw that in the initial commiiters, Harry Zhu > > (7harryprince AT gmail.com) was ranked 26th in github statistics. > > Does he have some non-code contributions? > > > > Thanks, > > Ming Wen, Apache APISIX(incubating) & Apache SkyWalking > > Twitter: _WenMing > > > > > > Jia Yu 于2020年7月13日周一 下午4:29写道： > > > > > Hello Dave, > > > > > > Thank you for the great question! > > > > > > We actually have tried our best to reach out to the existing code > > > contributors to ask for their support. To be specific, we did the > > following > > > two things: > > > > > > 1. We created a GitHub issue on GeoSpark repo to explain this donation > in > > > October 2019. > > > > > > Please find the issue here: > > > https://github.com/DataSystemsLab/GeoSpark/issues/391 > > > > > > We just posted the latest update of this proposal and added that if > > anyone > > > found that we forgot them, we are more than happy to add them. > > > > > > 2. We have contacted all code contributors individually through emails > > and > > > personal contacts. They all support this donation. The initial > committers > > > are contributors who made significant contributions to Apache Sedona > > based > > > on the GitHub statistics: > > > https://github.com/DataSystemsLab/GeoSpark/graphs/contributors They > are > > > willing to continuously support this project. > > > > > > We believe that we have got strong support from the community. Hope > this > > > can answer your question! > > > > > > Regards, > > > Jia > > > > > > > > > > > > Jia Yu > > > > > > Ph.D. in Computer Science > > > > > > Arizona State University <http://www.asu.edu/> > > > > > > Reach me via: Homepage <http://jiayuasu.github.io/> | GitHub > > > <https://github.com/jiayuasu> > > > > > > On Sun, Jul 12, 2020 at 12:46 PM Dave Fisher > > > wrote: > > > > > > > >> Hi - > > > >> > > > >> You note over 30 contributors to GeoSpark, but there are only 8 > > initial > > > >> committers. Has the move to the Apache Incubator been thoroughly > > > discussed > > > >> in the existing community? Is anyone being excluded? > > > >> > > > >> Best Regards, > > > >> Dave > > > >> > > > >> Sent from my iPhone > > > >> > > > >> > On Jul 12, 2020, at 12:36 PM, Felix Cheung < > felixche...@apache.org> > > > >> wrote: > > > >> > > > > >> > Any questions or concerns? If not, I can kick off the VOTE thread > > > >> shortly. > > > >> > > > > >> > > > > >> > > > > >> >> On Thu, Jul 9, 2020 at 6:12 AM Felix Cheung < > > felixche...@apache.org> > > > >> wrote: > > > >> >> > > > >> >> Hi, > > > >> >> > > > >> >> We would like to propose Apache Sedona, currently known in its > > > >> community > > > >> >> as GeoSpark, as a new project under the Apache Incubator. > > > >> >> > > > >> >> Sedona is a big geospatial data processing engine. The system > > > provides > > > >> an > > > >> >> easy to use Scala, SQL, and Python APIs for spatial data > scientists > > > to > > > >> >> manage, wrangle, and process geospatial data. The system extends > > and > > > >> builds > > > >> >> upon a popular cluster computing framework (Apache Spark) to > > provide > > > >> >> scalability. > > > >> >> > > > >> >> > > > >> >> The proposal can be found at > > > >> >> > > > https://cwiki.apache.org/confluence/display/INCUBATOR/Sedona+Proposal > > > >> >> > > > >> >> The project can benefit from and is seeking more experienced > > mentor. > > > >> >> > > > >> >> Any thought or feedback is appreciated! > > > >> >> Regards > > > >> >> Felix > > > >> >> > > > >> >> > > > >> > > > >> > > > >> > - > > > >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > > >> For additional commands, e-mail: general-h...@incubator.apache.org > > > >> > > > >> > > > > > >
Re: [DISCUSS] project proposal - Apache Sedona
> The initial committers are contributors who made significant contributions to Apache Sedona based on the GitHub statistics: https://github.com/DataSystemsLab/GeoSpark/graphs/contributors hello, Jia Yu, I have a question. I saw that in the initial commiiters, Harry Zhu (7harryprince AT gmail.com) was ranked 26th in github statistics. Does he have some non-code contributions? Thanks, Ming Wen, Apache APISIX(incubating) & Apache SkyWalking Twitter: _WenMing Jia Yu 于2020年7月13日周一 下午4:29写道： > Hello Dave, > > Thank you for the great question! > > We actually have tried our best to reach out to the existing code > contributors to ask for their support. To be specific, we did the following > two things: > > 1. We created a GitHub issue on GeoSpark repo to explain this donation in > October 2019. > > Please find the issue here: > https://github.com/DataSystemsLab/GeoSpark/issues/391 > > We just posted the latest update of this proposal and added that if anyone > found that we forgot them, we are more than happy to add them. > > 2. We have contacted all code contributors individually through emails and > personal contacts. They all support this donation. The initial committers > are contributors who made significant contributions to Apache Sedona based > on the GitHub statistics: > https://github.com/DataSystemsLab/GeoSpark/graphs/contributors They are > willing to continuously support this project. > > We believe that we have got strong support from the community. Hope this > can answer your question! > > Regards, > Jia > > > > Jia Yu > > Ph.D. in Computer Science > > Arizona State University <http://www.asu.edu/> > > Reach me via: Homepage <http://jiayuasu.github.io/> | GitHub > <https://github.com/jiayuasu> > > On Sun, Jul 12, 2020 at 12:46 PM Dave Fisher > wrote: > > > >> Hi - > >> > >> You note over 30 contributors to GeoSpark, but there are only 8 initial > >> committers. Has the move to the Apache Incubator been thoroughly > discussed > >> in the existing community? Is anyone being excluded? > >> > >> Best Regards, > >> Dave > >> > >> Sent from my iPhone > >> > >> > On Jul 12, 2020, at 12:36 PM, Felix Cheung > >> wrote: > >> > > >> > Any questions or concerns? If not, I can kick off the VOTE thread > >> shortly. > >> > > >> > > >> > > >> >> On Thu, Jul 9, 2020 at 6:12 AM Felix Cheung > >> wrote: > >> >> > >> >> Hi, > >> >> > >> >> We would like to propose Apache Sedona, currently known in its > >> community > >> >> as GeoSpark, as a new project under the Apache Incubator. > >> >> > >> >> Sedona is a big geospatial data processing engine. The system > provides > >> an > >> >> easy to use Scala, SQL, and Python APIs for spatial data scientists > to > >> >> manage, wrangle, and process geospatial data. The system extends and > >> builds > >> >> upon a popular cluster computing framework (Apache Spark) to provide > >> >> scalability. > >> >> > >> >> > >> >> The proposal can be found at > >> >> > https://cwiki.apache.org/confluence/display/INCUBATOR/Sedona+Proposal > >> >> > >> >> The project can benefit from and is seeking more experienced mentor. > >> >> > >> >> Any thought or feedback is appreciated! > >> >> Regards > >> >> Felix > >> >> > >> >> > >> > >> > >> - > >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > >> For additional commands, e-mail: general-h...@incubator.apache.org > >> > >> >
Re: [VOTE] Release Apache APISIX (Incubating) 1.4-RC1
> "This project is dual licensed under the Apache 2.0 and AGPL licenses： > 1. If used with Apache APISIX, the license is Apache License 2.0; > 2. otherwise the license is AGPL.” > How did this come about? I hav a possible concern about this but not sure if it’s an issue or not. These two dependencies are designed and implemented specifically for Apache APISIX, and will always keep the Apache 2.0 license for Apache APISIX. At the same time, we don't want just use these two dependencies instead of Apache APISIX as a whole, so we've set up a dual licenses. For Apache APISIX, I don't think there is a license issue because both are the Apache 2.0 license. If I'm wrong, please correct me and we can fix it. Thanks, Ming Wen, Apache APISIX & Apache SkyWalking Twitter: _WenMing Justin Mclean 于2020年6月25日周四 下午2:51写道： > HI, > > +1 (binding) > > I checked: > - incubating in name > - signature and hash is fine > - DISCLAIMER exists > - NOTICE and LICENSE are all good > - No unextedtcd binary files > - All ASF file have correct headers > - Can compile > > > I did notice one odd thing I’ve not noticed before. In [1][2] > > "This project is dual licensed under the Apache 2.0 and AGPL licenses： > 1. If used with Apache APISIX, the license is Apache License 2.0; > 2. otherwise the license is AGPL.” > > How did this come about? I hav a possible concern about this but not sure > if it’s an issue or not. > > Thanks, > Justin > > 1. ./deps/lib/luarocks/rocks-5.1/jsonschema/0.8-0/doc/LICENSE > 2. ./deps/lib/luarocks/rocks-5.1/lua-resty-radixtree/1.9-0/doc/LICENSE > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [VOTE] Release Apache APISIX (Incubating) 1.4-RC1
Welocme IPMC to vote, we got 0 +1 binding vote now. Thanks, Ming Wen, Apache APISIX & Apache SkyWalking Twitter: _WenMing YuanSheng Wang 于2020年6月24日周三 上午9:50写道： > Carry my +1 non-binding from dev. > > I checked all those steps and run the Apache APISIX successfully at my > local machine(fedora 31). > > And it shows the correct version `1.4`. > > [x] Download links are valid. > [x] Checksums and PGP signatures are valid. > [x] DISCLAIMER is included. > [x] LICENSE and NOTICE files are good. > [x] No binary file. > [x] All files have license headers if necessary. > > > On Tue, Jun 23, 2020 at 6:23 PM Nirojan Selvanathan > wrote: > > > Hello everyone, > > > > This is a call for the vote to release Apache APISIX (Incubating) version > > 1.4-RC1. > > > > The Apache APISIX community has voted on and approved a proposal to > > release Apache APISIX (Incubating) version 1.4-RC1. > > We now kindly request the Incubator IPMC members review and vote on > > this incubator release. > > > > Apache APISIX is a cloud-native microservices API gateway, delivering the > > ultimate performance, security, open-source and scalable platform for all > > your APIs and microservices. > > Apache APISIX is based on Nginx and etcd, it has dynamic routing and > > plug-in hot loading, which is especially suitable for API management > under > > the micro-service system. > > > > Apache APISIX community vote and result threads: > > > > > https://lists.apache.org/thread.html/r3304413b3d69f8d388c9f42714616776d6148f7eb674794861edc790%40%3Cdev.apisix.apache.org%3E > > > > Release notes: > > https://github.com/apache/incubator-apisix/blob/v1.4/CHANGELOG.md#140 > > > > The release candidates: > > https://dist.apache.org/repos/dist/dev/incubator/apisix/1.4-rc1/ > > > > Git tag for the release: > > https://github.com/apache/incubator-apisix/tree/v1.4 > > > > Release Commit ID: > > > > > https://github.com/apache/incubator-apisix/commit/f7584f680697179f5af44dbff5e26ad25cb860e8 > > > > Keys to verify the Release Candidate: > > https://dist.apache.org/repos/dist/dev/incubator/apisix/KEYS > > > > Steps to validating the release: > > > > 1. Download the release > > ``` > > wget > > > > > https://dist.apache.org/repos/dist/dev/incubator/apisix/1.4-rc1/apache-apisix-1.4-rc1-incubating-src.tar.gz > > ``` > > > > > > 2. Checksums and signatures > > ``` > > wget https://dist.apache.org/repos/dist/dev/incubator/apisix/KEYS > > wget > > > > > https://dist.apache.org/repos/dist/dev/incubator/apisix/1.4-rc1/apache-apisix-1.4-rc1-incubating-src.tar.gz.asc > > wget > > > > > https://dist.apache.org/repos/dist/dev/incubator/apisix/1.4-rc1/apache-apisix-1.4-rc1-incubating-src.tar.gz.sha512 > > > > shasum -c apache-apisix-1.4-rc1-incubating-src.tar.gz.sha512 > > gpg --import KEYS > > > > # input `trust`, `5`, then `save` > > > > gpg --edit-key "Nirojan Selvanathan" > > gpg --verify apache-apisix-1.4-rc1-incubating-src.tar.gz.asc > > apache-apisix-1.4-rc1-incubating-src.tar.gz > > ``` > > > > 3. Unzip and Check files > > ``` > > tar zxvf apache-apisix-1.4-rc1-incubating-src.tar.gz > > ``` > > > > 4. This release contains the dashboard code for APISIX > > > > > https://github.com/apache/incubator-apisix-dashboard/tree/329b092dcaa7a505dcdec86c667b6803f5863d94 > > > > > > 5. Build Apache APISIX: > > https://github.com/apache/incubator-apisix/blob/v1.4/doc/how-to-build.md > > > > The vote will be open for at least 72 hours or until the necessary number > > of votes is reached. > > > > Please vote accordingly: > > [ ] +1 approve > > [ ] +0 no opinion > > [ ] -1 disapprove with the reason > > > > Checklist for reference: > > [ ] Download links are valid. > > [ ] Checksums and PGP signatures are valid. > > [ ] DISCLAIMER is included. > > [ ] LICENSE and NOTICE files are good. > > [ ] No binary file. > > [ ] All files have license headers if necessary. > > > > And below is a more detailed checklist: > > > > > https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist > > > > -- > > Best Regards, > > S.Nirojan > > Linked-in <https://www.linkedin.com/in/niroselva/> > > > > > -- > > *MembPhis* > My GitHub: https://github.com/membphis > Apache APISIX: https://github.com/apache/incubator-apisix >
[RESULT][VOTE] Graduate Apache APISIX (incubating) as a TLP
Hello, all, VOTE for Graduate Apache APISIX (incubating) as a TLP [1] has passed with - 10 Binding +1 votes - 15 Non-binding +1 votes - No 0 or -1 votes The following are the results of the vote： Binding +1: - Sheng Wu - Kevin Ratnasekera - Willem Jiang - Justin Mclean - Gosling Von - Furkan KAMACI - Ted Liu - dujunping - Han Luke - Liang Chen Non-binding +1: - Yuansheng Wang - Zhiyuan Ju - agile6v - Lang Wang - hui li - Guanxu Cheng - junxu chen - 7sunmiao - Linsir Wu - Juan Pan - guo jiwei - lgcareer2019 - tison - Goson zhang - coolsoul Thank you all for your votes. [1] https://lists.apache.org/thread.html/r139bc0df07ab9df0ad6b53a8a649aed1d4e49804d09dba17bf763ee8%40%3Cgeneral.incubator.apache.org%3E Thanks, Ming Wen, Apache APISIX & Apache SkyWalking Twitter: _WenMing
Re: [VOTE] Accept Pegasus into the Apache incubation
+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 > > > > > > > > > > > > > > > > > > > > >
[VOTE] Graduate Apache APISIX (incubating) as a TLP
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
[DISCUSS] Graduate Apache APISIX (incubating) as a TLP
Hello, After discussion with the community[1], finally positive vote result[2]. We'd like to bring this to a discussing at the IPMC. Please see the proposed resolution below and let us know what do you think. A few status to help with the discussion: - Released 6 Apache releases, through 6 different release managers - Invited 9 new committers (all accepted) - Invited 5 new PPMC members (all accepted) - Apache APISIX name search has been approved [3] - finished the Podling Maturity Assessment for APISIX, all items are passed[4] - Our PPMC is diverse and consists of members from 10+ organizations - 1156 emails sent by 81 people in dev mailing-list excepted GitBox forwarded - There are 82 contributors for now - Resolved 360+ issues and 820+ pull requestsduring ASF incubating We've resolved all branding issues which include Logo, GitHub repo, document, website, luarocks and DockerHub. [1] https://lists.apache.org/thread.html/r3cd791660b7a8aeb06a116a3802c8e154cde392dc90797d66a9267e9%40%3Cdev.apisix.apache.org%3E [2] https://lists.apache.org/thread.html/ree04577ad2ebb2959f401b0848400f3b2876457f510f375797b6fbf8%40%3Cdev.apisix.apache.org%3E [3] https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-180 [4] https://cwiki.apache.org/confluence/display/APISIX/Podling+Maturity+Assessment+for+APISIX --- 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 Apache APISIX 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 Incubator APISIX podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator APISIX podling encumbered upon the Apache Incubator PMC are hereafter discharged. ------- Thanks, Ming Wen, Apache APISIX & Apache SkyWalking Twitter: _WenMing
Re: [ANNOUNCE] Apache APISIX (incubating) 1.3 released
good job! This is Apache APISIX's sixth Apache Release since entering the Apache Incubator last October. Thanks, Ming Wen, Apache APISIX & Apache SkyWalking Twitter: _WenMing Lang Wang 于2020年5月24日周日 下午11:10写道： > Hi all, > > The Apache APISIX (incubating) community is glad to announce that Apache > APISIX(incubating) 1.3 has been released! > > Apache APISIX is a cloud-native microservices API gateway, > delivering the ultimate performance, security, open source and scalable > platform for all your APIs and microservices. > > Apache APISIX is based on Nginx and etcd, it has dynamic routing and > plug-in hot loading, > which is especially suitable for API management under the micro-service > system. > > Download Link: http://www.apache.org/dist/incubator/apisix/ > > Release Note: > https://github.com/apache/incubator-apisix/blob/v1.3/CHANGELOG.md > > Website: http://apisix.apache.org/ > > APISIX Resources: > - issues: https://github.com/apache/incubator-apisix/issues > - Mailing list: d...@apisix.apache.org > > = > *Disclaimer* > > Apache APISIX (incubating) is an effort undergoing incubation at The Apache > Software Foundation (ASF), sponsored by the Apache Incubator PMC. > Incubation is required of all newly accepted projects until a further > review indicates that the infrastructure, > communications, and decision making process have stabilized in a manner > consistent with other successful ASF projects. > While incubation status is not necessarily a reflection of the completeness > or stability of the code, > it does indicate that the project has yet to be fully endorsed by the ASF. > > Thanks. > totemofwolf >
Re: [VOTE] Accept Rainbow into Apache Incubator
Hi, Aviem, I did a quick in trademarkia[1], and found a lot of trademarks about `rainbow`. [1] https://www.trademarkia.com/trademarks-search.aspx?tn=rainbow Thanks, Ming Wen, Apache APISIX & Apache SkyWalking Twitter: _WenMing Aviem Zur 于2020年5月4日周一 下午1:41写道： > Not sure what legally needs to be checked, but a quick search on uspto.gov > did not return any result of the single word 'rainbow': > > > http://tmsearch.uspto.gov/bin/showfield?f=toc=4805%3A82m03t.1.1_search=searchss_L=50=_plural=yes_s_PARA1=_tagrepl%7E%3A=PARA1%24LD=PARA1+AND+PARA2_s_PARA2=rainbow_tagrepl%7E%3A=PARA2%24COMB_op_ALL=AND_default=search_search=Submit+Query_search=Submit+Query > > On Sun, May 3, 2020 at 2:00 PM Justin Mclean > wrote: > > > Hi, > > > > > We have conducted a name search for 'Rainbow'. We feel that although > > there > > > are few existing open source projects with this name, they are in a > > > different space, hence not necessarily restrict us from using it. > > > > Did you look at existing trademarks? > > > > Thanks, > > Justin > > > > - > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > >
Re: [VOTE] Graduate Apache ShardingSphere (incubating)
+1 (non-binding) Thanks, Ming Wen, Apache APISIX & Apache SkyWalking Twitter: _WenMing lidong dai 于2020年3月14日周六 上午9:11写道： > +1 (not binding) > > > Best Regards > --- > DolphinScheduler(Incubator) PPMC > Lidong Dai > dailidon...@gmail.com > --- > > > Sheng Wu 于2020年3月14日周六 上午9:04写道： > > > +1 binding. > > > > Good luck ShardingSphere > > > > Sheng Wu 吴晟 > > Twitter, wusheng1108 > > > > > > zhangli...@apache.org 于2020年3月14日周六 上午1:30写道： > > > > > Hi! > > > > > > 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 > > > ShardingSphere from the incubator to the Top Level Project. > > > > > > [ ] +1 Graduate Apache ShardingSphere from the Incubator. > > > [ ] +0 Don't care. > > > [ ] -1 Don't graduate Apache ShardingSphere from the Incubator because > > ... > > > > > > This vote will open for at least 72 hours. > > > > > > Many thanks to our mentors and everyone else for their support. > > > > > > --- > > > > > > Establish the Apache ShardingSphere 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 ShardingSphere is an ecosystem consisted of a set of > > > distributed database middleware solutions, including 2 independent > > > products, Sharding-JDBC, Sharding-Proxy. They all provide functions of > > > data sharding, distributed transaction, database and data governance, > > > applicable in a variety of situations such as Java isomorphism and > > > heterogeneous language.. > > > > > > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee > > > (PMC), to be known as the "Apache ShardingSphere Project", be and > hereby > > > is established pursuant to Bylaws of the Foundation; and be it further > > > > > > RESOLVED, that the Apache ShardingSphere Project be and hereby is > > > responsible for the creation and maintenance of software related to > > > Apache ShardingSphere is an ecosystem consisted of a set of distributed > > > database middleware solutions, including 2 independent products, > > > Sharding-JDBC, Sharding-Proxy. They all provide functions of data > > > sharding, distributed transaction, database and data governance, > > > applicable in a variety of situations such as Java isomorphism and > > > heterogeneous language.; and be it further > > > > > > RESOLVED, that the office of "Vice President, Apache ShardingSphere" 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 > > > ShardingSphere Project, and to have primary responsibility for > > > management of the projects within the scope of responsibility of the > > > Apache ShardingSphere 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 ShardingSphere > > > Project: > > > > > > * Craig L Russell > > > * Hao Cao > > > * Hongjun Du > > > * Hongtao Gao > > > * Juan Pan > > > * Jun Zhao > > > * Liang Zhang > > > * QingYang Chen > > > * Sheng Wu > > > * Von Gosling > > > * Willem Ning Jiang > > > * Xiaoguang Ma > > > * Yang Yi > > > * Yonglun Zhang > > > > > > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Liang Zhang be appointed > to > > > the office of Vice President, Apache ShardingSphere, 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 ShardingSphere Project be and hereby is > tasked > > > with the migration and rationalization of the Apache Incubator > > > ShardingSphere podling; and be it further > > > > > > RESOLVED, that all responsibilities pertaining to the Apache Incubator > > > ShardingSphere podling encumbered upon the Apache Incubator PMC are > > > hereafter discharged. > > > > > > -- > > > > > > Liang Zhang (John) > > > Apache ShardingSphere & Dubbo > > > > > >
Re: [DISCUSS] Graduate Apache ShardingSphere (incubating) as a TLP
Hi, ShardingSphere community, really great job in the incubator journey, the community grown fast. +1 (non-binding) and good luck. Thanks, Ming Wen, Apache APISIX Twitter: _WenMing zhangli...@apache.org 于2020年3月9日周一 下午10:14写道： > Hi! > > After an enthusiastic discussion with the community[1], finally positive > vote result[2]. > > We'd like to bring this to a discussing at the IPMC. > > Please see the proposed resolution below and let us know what do you think. > > A few status to help with the discussion: > > - There are 1301 emails sent by 159 people in dev mailing-list excepted > GitBox forwarded; > - 2539 Issues created during ASF incubating, 2468 Issues resolved during > ASF incubating; > - 1073 PRs created during ASF incubating, 918 PRs merged during ASF > incubating; > - There are 89 contributors for now; > - There are 4 versions released successfully conformant to Apache release > policy by 3 release managers; > - There are 2 new PPMCs and 8 new committers were invited to join the > community. > > We had already finished the Podling Maturity Assessment for > ShardingSphere[3], the 34 items are all passed. > > We had resolved all branding issues which include Logo, GitHub repo, > document, website and DockerHub image. > > [1] > > https://lists.apache.org/thread.html/rf6a2cec7143395ac0126dcb13f331fbc87b680eaca015d50d7793172%40%3Cdev.shardingsphere.apache.org%3E > [2] > > https://lists.apache.org/thread.html/rc46c2869cd87f4d92c1322f0e008fc294980e1470443265d98529e66%40%3Cdev.shardingsphere.apache.org%3E > [3] > https://github.com/apache/incubator-shardingsphere/blob/dev/MATURITY.md > > > > > Establish the Apache ShardingSphere 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 ShardingSphere is an ecosystem consisted of a set of > distributed database middleware solutions, including 2 independent > products, Sharding-JDBC, Sharding-Proxy. They all provide functions of > data sharding, distributed transaction, database and data governance, > applicable in a variety of situations such as Java isomorphism and > heterogeneous language.. > > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee > (PMC), to be known as the "Apache ShardingSphere Project", be and hereby > is established pursuant to Bylaws of the Foundation; and be it further > > RESOLVED, that the Apache ShardingSphere Project be and hereby is > responsible for the creation and maintenance of software related to > Apache ShardingSphere is an ecosystem consisted of a set of distributed > database middleware solutions, including 2 independent products, > Sharding-JDBC, Sharding-Proxy. They all provide functions of data > sharding, distributed transaction, database and data governance, > applicable in a variety of situations such as Java isomorphism and > heterogeneous language.; and be it further > > RESOLVED, that the office of "Vice President, Apache ShardingSphere" 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 > ShardingSphere Project, and to have primary responsibility for > management of the projects within the scope of responsibility of the > Apache ShardingSphere 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 ShardingSphere > Project: > > * Craig L Russell > * Hao Cao > * Hongjun Du > * Hongtao Gao > * Juan Pan > * Jun Zhao > * Liang Zhang > * QingYang Chen > * Sheng Wu > * Von Gosling > * Willem Ning Jiang > * Xiaoguang Ma > * Yang Yi > * Yonglun Zhang > > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Liang Zhang be appointed to > the office of Vice President, Apache ShardingSphere, 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 ShardingSphere Project be and hereby is tasked > with the migration and rationalization of the Apache Incubator > ShardingSphere podling; and be it further > > RESOLVED, that all responsibilities pertaining to the Apache Incubator > ShardingSphere podling encumbered upon the Apache Incubator PMC are > hereafter discharged. > > -- > > Liang Zhang (John) > Apache ShardingSphere & Dubbo >
Re: [VOTE] Release Apache APISIX (Incubating) 1.1-RC1
Welcome more IPMCs to vote, thx Thanks, Ming Wen, Apache APISIX Twitter: _WenMing Willem Jiang 于2020年2月22日周六 下午8:56写道： > +1 (binding) > I checked > - Download links are valid. > - Checksums and PGP signature are valid. > - DISCLAIMER file is included. > - Both LICENSE and NOTICE files are good. > - No binary file. > > > Willem Jiang > > Twitter: willemjiang > Weibo: 姜宁willem > > > On Fri, Feb 21, 2020 at 11:15 AM junxu chen wrote: > > > > Hello, Community, > > > > This is a call for the vote to release Apache APISIX (Incubating) version > > 1.1-RC1. > > > > The Apache APISIX community has voted on and approved a proposal to > release > > Apache APISIX (Incubating) based on 1.1-RC1. > > > > Here is the Apache APISIX community vote result: > > > > > > 6 PPMC +1 votes: > > - Yuansheng Wang > > - agile6v > > - Ming Wen > > - Lang Wang > > - Linsir Wu > > - Li Ling > > > > > > 1 mentor +1 vote: > > - Justin Mclean > > > > > > 1 community +1 vote: > > - doggieと杨 > > > > > > We now kindly request the other Incubator IPMC members to review and vote > > for this incubator release. > > > > > > Apache APISIX community vote and result threads: > > > > > https://lists.apache.org/thread.html/r97d9450c5ec695bb292d1d8119d639494d24ed57c93b63ca6a1b5d24%40%3Cdev.apisix.apache.org%3E > > > > > > > > Release notes: > > > > https://github.com/apache/incubator-apisix/blob/v1.1/CHANGELOG.md#110 > > > > > > The release candidates: > > > > https://dist.apache.org/repos/dist/dev/incubator/apisix/1.1-rc1/ > > > > > > Git tag for the release: > > > > https://github.com/apache/incubator-apisix/tree/v1.1 > > > > > > Release Commit ID: > > > > > https://github.com/apache/incubator-apisix/commit/3c57401d76ee32bc84c1ceb568e6c7ae1cef41a0 > > > > > > Keys to verify the Release Candidate: > > > > https://dist.apache.org/repos/dist/dev/incubator/apisix/KEYS > > > > > > Steps to validating the release: > > > > 1. Download the release > > > > ``` > > > > wget > > > https://dist.apache.org/repos/dist/dev/incubator/apisix/1.1-rc1/apache-apisix-1.1-rc1-incubating-src.tar.gz > > > > ``` > > > > > > 2. Checksums and signatures > > > > ``` > > > > wget https://dist.apache.org/repos/dist/dev/incubator/apisix/KEYS > > > > wget > > > https://dist.apache.org/repos/dist/dev/incubator/apisix/1.1-rc1/apache-apisix-1.1-rc1-incubating-src.tar.gz.asc > > > > wget > > > https://dist.apache.org/repos/dist/dev/incubator/apisix/1.1-rc1/apache-apisix-1.1-rc1-incubating-src.tar.gz.sha512 > > > > > > shasum -c apache-apisix-1.1-rc1-incubating-src.tar.gz.sha512 > > > > > > gpg --import KEYS > > > > # input `trust`, `5`, then `save` > > > > gpg --edit-key "Junxu Chen" > > > > gpg --verify apache-apisix-1.1-rc1-incubating-src.tar.gz.asc > > apache-apisix-1.1-rc1-incubating-src.tar.gz > > > > ``` > > > > > > 3. Unzip and Check files > > > > ``` > > > > tar zxvf apache-apisix-1.1-rc1-incubating-src.tar.gz > > > > ``` > > > > > > 4. Build Apache APISIX: > > > > https://github.com/apache/incubator-apisix/blob/v1.1/doc/how-to-build.md > > > > > > The vote will be open for at least 72 hours or until necessary number of > > votes are reached. > > > > > > Please vote accordingly: > > > > > > [ ] +1 approve > > > > [ ] +0 no opinion > > > > [ ] -1 disapprove with the reason > > > > > > Checklist for reference: > > > > > > [ ] Download links are valid. > > > > [ ] Checksums and PGP signatures are valid. > > > > [ ] DISCLAIMER is included. > > > > [ ] LICENSE and NOTICE files are good. > > > > [ ] No binary file. > > > > [ ] All files have license headers if necessary. > > > > > > > > And below is a more detailed checklist: > > > > > https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist > > > > > > > > Thanks! > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [VOTE] Release Apache APISIX Dashboard (Incubating) 1.0-RC2
Welcome more IPMCs to vote, thx Thanks, Ming Wen, Apache APISIX Twitter: _WenMing Zhiyuan Ju 于2020年2月23日周日 下午8:22写道： > Thanks for Justin and Willem Jiang's vote! > > Best Regards! > @ Zhiyuan Ju <https://www.shaoyaoju.org/> > > > Willem Jiang 于2020年2月22日周六 下午8:46写道： > > > Carry my +1 from dev@apisix here. > > > > Willem Jiang > > > > Twitter: willemjiang > > Weibo: 姜宁willem > > > > On Thu, Feb 20, 2020 at 11:35 PM Zhiyuan Ju > wrote: > > > > > > Hi everyone, > > > > > > This is a call for the vote to release Apache APISIX Dashboard > > (Incubating) > > > based on 1.0-RC2. > > > > > > The Apache APISIX community has voted on and approved a proposal to > > release > > > Apache APISIX Dashboard (Incubating) based on 1.0-RC2, 6 votes from > PPMC, > > > and 2 votes from IPMC already. > > > > > > PPMC: > > > - Ming Wen > > > - Li Ling > > > - Yuansheng Wang > > > - agile6v > > > - Lang Wang > > > - Linsir Wu > > > > > > IPMC: > > > - Justin > > > - Willem Jiang > > > > > > We now kindly request the other Incubator IPMC members to review and > vote > > > for this incubator release. > > > > > > Apache APISIX community vote and result threads: > > > > > > > > > https://lists.apache.org/thread.html/r8c37b3a99bc3819c92b838ca90a4cd3b0b4ce1c87feaf91aa1c1e751%40%3Cdev.apisix.apache.org%3E > > > > > > Release notes: > > > > > > https://github.com/apache/incubator-apisix-dashboard > > > /blob/v1.0/CHANGELOG.md#100 > > > > > > Release candidates: > > > > > > > > > https://dist.apache.org/repos/dist/dev/incubator/apisix/dashboard-1.0-rc2/ > > > > > > Git tree for the release: > > > > > > https://github.com/apache/incubator-apisix-dashboard/tree/v1.0 > > > > > > Release commit id: > > > > > > https://github.com/apache/incubator-apisix-dashboard > > > /commit/813142e202d5f90135c9aa16b7fa60be83e8d5e6 > > > > > > Keys to verify the release candidate: > > > > > > https://dist.apache.org/repos/dist/dev/incubator/apisix/KEYS > > > > > > Steps to validate the release: > > > > > > 1. Download the release: > > > > > > $ wget > https://dist.apache.org/repos/dist/dev/incubator/apisix/dashboard > > > -1.0-rc2/apache-apisix-dashboard-1.0-rc2-incubating-src.tar.gz > > > > > > 2. Checksum and verify signature: > > > > > > $ wget https://dist.apache.org/repos/dist/dev/incubator/apisix/KEYS > > > > > > $ wget > https://dist.apache.org/repos/dist/dev/incubator/apisix/dashboard > > > -1.0-rc2/apache-apisix-dashboard-1.0-rc2-incubating-src.tar.gz.asc > > > > > > $ wget > https://dist.apache.org/repos/dist/dev/incubator/apisix/dashboard > > > -1.0-rc2/apache-apisix-dashboard-1.0-rc2-incubating-src.tar.gz.sha512 > > > > > > $ shasum -c > apache-apisix-dashboard-1.0-rc2-incubating-src.tar.gz.sha512 > > > > > > $ gpg --import KEYS > > > > > > $ gpg --edit-key juzhiyuan > > > > > > $ Input *trust* and press return button > > > > > > $ Input *5* and press return button > > > > > > $ Input *y* and press return button > > > > > > $ gpg --verify > apache-apisix-dashboard-1.0-rc2-incubating-src.tar.gz.asc > > > apache-apisix-dashboard-1.0-rc2-incubating-src.tar.gz > > > > > > 3. Unzip and check files > > > > > > $ tar zxvf apache-apisix-dashboard-1.0-rc2-incubating-src.tar.gz > > > > > > $ cd apache-apisix-dashboard-1.0-incubating > > > > > > 4. Build the Apache APISIX Dashboard > > > 4.1 Make sure both Node.js 8.12.0+ and yarn are installed on your > > machine. > > > 4.2 $ yarn > > > 4.3 $ yarn build:prod > > > 4.4 copy all files under /dist directory to your APISIX's /dashboard > > > directory. > > > 4.5 Open browser and visit http://127.0.0.1:9080/apisix/dashboard/ > > > 4.6 More detailed documentation: > > https://github.com/apache/incubator-apisix# > > > dashboard > > > > > > This vote will last for at least 72 hours or necessary number of votes > > are > > > reached. > > > > > > Please vote accordingly: > > > > > > [ ] +1 approve > > > [ ] +0 no opinion > > > [ ] -1 disapprove with your reason > > > > > > Checklist for reference: > > > > > > [ ] Download links are valid. > > > [ ] Checksums and PGP signature are valid. > > > [ ] DISCLAIMER file is included. > > > [ ] Both LICENSE and NOTICE files are good. > > > [ ] No binary file. > > > [ ] All files have valid License header if necessary. > > > > > > The following link is a more detailed checklist for reference: > > > > > > > > > https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist > > > > > > Best Regards! > > > @ Zhiyuan Ju <https://www.shaoyaoju.org/> > > > > - > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > >
[jira] [Created] (INCUBATOR-249) create cwiki home space for Apache APISIX
Ming Wen created INCUBATOR-249: -- Summary: 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 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
Re: [VOTE] Accept YuniKorn into Apache Incubator
+1 (non-binding) Good luck. Thanks, Ming Wen, Apache APISIX Twitter: _WenMing Vinod Kumar Vavilapalli 于2020年1月11日周六 上午1:47写道： > Hi, > > I'd like to call a vote on accepting YuniKorn into the Apache Incubator. > > Please see the discussion thread [1]. > > Please see the full proposal: > https://cwiki.apache.org/confluence/display/INCUBATOR/YuniKornProposal > > Please cast your vote > > [ ] +1 Accept YuniKorn into the Incubator > [ ] +0 Indifferent to the acceptance of YuniKorn > [ ] -1 Do not accept YuniKorn because … > > The vote will be open at least for 72 hours. > > Incubator PMC member votes are binding. Everyone else is welcomed to vote > too (mark them as non-binding if you can)! > > Thanks > +Vinod > > [1] [DISCUSS] YuniKorn Proposal > https://lists.apache.org/thread.html/59a3fc019119352f06e75a2bae5c25cd1b652282d7a59b85ed2188cf%40%3Cgeneral.incubator.apache.org%3E > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [ANNOUNCE] Release Apache DolphinScheduler (Incubating) 1.2.0
Congratulations Thanks, Ming Wen, Apache APISIX Twitter: _WenMing 李 岗 于2020年1月2日周四 下午7:34写道： > Hi all, > > We are glad to announce the release of Apache DolphinScheduler(incubating) > 1.2.0. Once again I would like to express my thanks to your help. > > Dolphin Scheduler is a distributed and easy-to-expand visual DAG workflow > scheduling system, > dedicated to solving the complex dependencies in data processing, making > the scheduling system out of the box for data processing. > > > Download Links: > http://dolphinscheduler.apache.org/en-us/docs/user_doc/download.html > > Release Notes: > https://github.com/apache/incubator-dolphinscheduler/blob/1.2.0/ReleaseNotes.md > > Website: https://dolphinscheduler.apache.org/ > > DolphinScheduler Resources: > - Issue: https://github.com/apache/incubator-dolphinscheduler/issues/ > - Mailing list: d...@dolphinscheduler.apache.org > - Documents: > https://github.com/apache/incubator-dolphinscheduler/blob/1.2.0/README.md > > > DolphinScheduler(Incubator) PPMC > Gang Li 李岗 > > lgcareer2...@outlook.com<mailto:lgcareer2...@outlook.com> >
Re: [VOTE] Apache BatchEE leaving the incubator
+1 (non-binding) to join Apache Geronimo
Thanks,
Ming Wen, Apache APISIX
Twitter: _WenMing
Jean-Baptiste Onofré 于2019年12月7日周六 下午12:38写道：
> +1 to join Geronimo
>
> Regards
> JB
>
> On 06/12/2019 10:50, Romain Manni-Bucau wrote:
> > Hi everyone,
> >
> > BatchEE community voted to leave the incubator to join Apache Geronimo
> as a
> > subproject.
> >
> > Here is the vote thread:
> > http://mail-archives.apache.org/mod_mbox/batchee-dev/201912.mbox/browser
> >
> > Please vote:
> >
> > [ ] +1 to retire Sirona
> > [ ] -1 to retire Sirona ${cause}
> >
> > Vote will be opened for 3 days or until 3 +1 bindings are reached as
> usual
> >
> > Here is my +1
> >
> > Romain Manni-Bucau
> > @rmannibucau <https://twitter.com/rmannibucau> | Blog
> > <https://rmannibucau.metawerx.net/> | Old Blog
> > <http://rmannibucau.wordpress.com> | Github <
> https://github.com/rmannibucau> |
> > LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book
> > <
> https://www.packtpub.com/application-development/java-ee-8-high-performance
> >
> >
>
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>
Re: [VOTE] Accept NuttX into the Apache Incubator
+1 (non-binding) Thanks, Ming Wen, Apache APISIX Twitter: _WenMing Sheng Wu 于2019年12月4日周三 下午2:04写道： > +1 binding > Sheng Wu 吴晟 > Twitter, wusheng1108 > > > Dave Fisher 于2019年12月4日周三 下午2:03写道： > > > +1 (binding) > > > > Regards, > > Dave > > > > Sent from my iPhone > > > > > On Dec 3, 2019, at 9:30 PM, 俊平堵 wrote: > > > > > > Hi folks, > > > > > > > > > The [DISCUSS] thread on NuttX has died down. > > > > > > > > > Accordingly, I would like to call a VOTE to accept NuttX into the > > > > > > Apache Incubator. > > > > > > > > > Please cast your vote: > > > > > > > > > [ ] +1, bring NuttX into the Incubator > > > > > > [ ] +0, I don't care either way > > > > > > [ ] -1, do not bring NuttX into the Incubator, because... > > > > > > > > > The vote will open at least for 72 hours and only votes from the > > > > > > Incubator PMC are binding, but votes from everyone are welcome. > > > > > > > > > =Abstract= > > > > > > NuttX is a mature, real-time embedded operating system (RTOS). It has > > wide > > > usage in IoT projects, control systems, robotics, drones, and many > other > > > systems. Unique properties of NuttX are its strict adherence to > > standards > > > and its scalability. NuttX follows the Unix standards as defined > > > by OpenGroup.org (POSIX, ANSI, and others). This allows for a high > > degree > > > of portability. Scalability is supported through a configuration system > > > that allows NuttX to run on the smallest embedded platforms and through > > > high end single board computers. > > > > > > > > > =Proposal= > > > > > > NuttX was released under a BSD 3-Clause license on February 17, 2007. > > From > > > that time until now it has been managed by a single person, Gregory > Nutt. > > > The user base of NuttX has grown to probably thousands of projects and > > > perhaps a hundred active developments at any time. The code base has > > grown > > > to around 1.5 million lines of code (according to OpenHub.com). > > > > > > NuttX has benefited from this single person management because this has > > > resulted in a consistent architecture and controlled growth. But now > it > > is > > > time to open this project to the participation of others because this > > > consistent architecture assures solid future growth, and because the > > > magnitude of effort required to support the RTOS exceeds the capability > > of > > > a single person, but also because users of NuttX require a stable road > > map > > > going forward that does not depend on a single person. > > > > > > For these reasons, I propose that NuttX enter the Apache Incubator as a > > > first step in opening the project to wider participation. > > > > > > > > > =Initial Goals= > > > > > > The initial goal will be to move the existing BSD code base to Apache > and > > > integrate with the Apache development process and infrastructure. A > > primary > > > goal of incubation will be to grow and diversify the NuttX community. > We > > > will convert that code base to the Apache license during incubation. > > > > > > > > > =Current Status= > > > > > > As previously mentioned, NuttX is a mature, stable product in wide use > in > > > embedded products. > > > > > > > > > ==Meritocracy== > > > > > > We value meritocracy and we understand that it is the basis for an open > > > community that encourages multiple companies and individuals to > > contribute > > > and be invested in the project’s future. We will encourage and monitor > > > participation and make sure to extend privileges and responsibilities > to > > > all contributors. > > > > > > Being a mature project, NuttX already has an extensive user base with > > many > > > people who understand the software, who have committed hundreds of > > changes, > > > and are happy to participate in the project. I believe that with a > > little > > > guidance and formalization, a PMC and a large group of experienced > > > committers can quickly be established. > > > > > > > > > ==Community== > > > > > >
[ANNOUNCE] Apache APISIX (incubating) 0.9 released
Hi all, The Apache APISIX (incubating) community is glad to announce that Apache APISIX(incubating) 0.9 has been released! This is our first Apache release. Apache APISIX is a cloud-native microservices API gateway, delivering the ultimate performance, security, open source and scalable platform for all your APIs and microservices. Apache APISIX is based on Nginx and etcd, it has dynamic routing and plug-in hot loading, which is especially suitable for API management under the micro-service system. Download Link: http://www.apache.org/dist/incubator/apisix/ Release Note: https://github.com/apache/incubator-apisix/blob/master/CHANGELOG.md Website: http://apisix.apache.org/ APISIX Resources: - issues: https://github.com/apache/incubator-apisix/issues - Mailing list: d...@apisix.apache.org = *Disclaimer* Apache APISIX (incubating) is an effort undergoing incubation at The Apache Software Foundation (ASF), sponsored by the Apache Incubator PMC. Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and decision making process have stabilized in a manner consistent with other successful ASF projects. While incubation status is not necessarily a reflection of the completeness or stability of the code, it does indicate that the project has yet to be fully endorsed by the ASF. Thanks, Ming Wen, Apache APISIX Twitter: _WenMing
[RESULT] [VOTE] Release Apache APISIX (incubating) 0.9
Hi, all, Release vote for Release Apache APISIX (Incubating) 0.9 has PASSED and closed now. The results are as follows: 3 IPMC +1 votes: - Justin Mclean - Willem Jiang - Kevin Ratnasekera 1 non-binding +1 vote: - Yuansheng Wang Vote thread: https://lists.apache.org/thread.html/1ac4ef82541eab58de4d5202bed4fba53ecab6fc1c9ca26ca83fc66e@%3Cgeneral.incubator.apache.org%3E I'm going to publish the source release of Apache APISIX (incubating) 0.9 and send ANNOUNCE later. Thank you all for making this happen! Thanks, Ming Wen, Apache APISIX Twitter: _WenMing
Re: [VOTE] Release Apache ShardingSphere (Incubating) 4.0.0-RC3
> A link of the ASF code of conduct has been added to our code of conduct page [2]. However, i also want to plead you to confirm whether this link[3] is what you mentioned. I think you'd better also add the link of ASF code of conduct in Github: https://github.com/apache/incubator-shardingsphere/blob/4.0.0-RC3/CODE_OF_CONDUCT.md Thanks, Ming Wen, Apache APISIX Twitter: _WenMing Juan Pan 于2019年11月21日周四 下午1:06写道： > Hi Justin, > > > Very appreciated your detailed checking. > > > An issue[1] based on your suggestions was created and would be done before > next release. > > > > You might want to add a link the ASF code of conduct in your code of > conduct. > A link of the ASF code of conduct has been added to our code of conduct > page [2]. However, i also want to plead you to confirm whether this link[3] > is what you mentioned. > > > Thanks. > > > [1] https://github.com/apache/incubator-shardingsphere/issues/3566 > [2] https://shardingsphere.apache.org/community/en/contribute/code-conduct > [3] https://www.apache.org/foundation/policies/conduct.html > > > Juan Pan > > > panj...@apache.org > Juan Pan(Trista), Apache ShardingSphere > > > On 11/21/2019 08:48，Justin Mclean wrote： > Hi, > > +1 (binding) > > In the source release I checked: > - incubating in name > - signatures and hashes fine > - DISCLAIMER exists > - LICENSE and NOTICE fine > - all files have ASF headers > - no unexpected binary files > - can compile from source > > A couple of suggestions: > - You might want to add a link the ASF code of conduct in your code of > conduct. > - You might want to update your version of the Mavin wrapper to be the > latest. > - Something been to have gone wrong with the footer in [1] where is says > "Copyright © The Apache Software Foundation, Licensed under the Apache > License, Version 4.0.0-RC3”. Do you mean Apache License version 2? > > Thanks, > Justin > > 1. ./sharding-ui/sharding-ui-frontend/src/components/Footer/index.vue > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org >
[VOTE] Release Apache APISIX (Incubating) 0.9-RC1
Hello everyone, This is a call for the vote to release Apache APISIX (Incubating) version 0.9-RC1. The Apache APISIX community has voted on and approved a proposal to release Apache APISIX (Incubating) version 0.9-RC1. We now kindly request the Incubator IPMC members review and vote on this incubator release. Apache APISIX is a cloud-native microservices API gateway, delivering the ultimate performance, security, open source and scalable platform for all your APIs and microservices. Apache APISIX is based on Nginx and etcd, it has dynamic routing and plug-in hot loading, which is especially suitable for API management under the micro-service system. Apache APISIX community vote and result threads: https://lists.apache.org/thread.html/321e7e4972c836e7d31a7885f37b92919c9730cc2a4f8de82075fd3a@%3Cdev.apisix.apache.org%3E https://lists.apache.org/thread.html/703f48c69e2ac1b7f4b8ec3182782e0fa6107793f8a6f17ae3826d23@%3Cdev.apisix.apache.org%3E Release notes: https://github.com/apache/incubator-apisix/blob/v0.9/CHANGELOG.md#090-rc1 The release candidates: https://dist.apache.org/repos/dist/dev/incubator/apisix/0.9-RC1/ Git tag for the release: https://github.com/apache/incubator-apisix/tree/v0.9 Release Commit ID: https://github.com/apache/incubator-apisix/commit/31a545a72589f618db17bca794d4885914600361 Keys to verify the Release Candidate: https://dist.apache.org/repos/dist/dev/incubator/apisix/KEYS Steps to validating the release: 1. Download the release ``` wget https://dist.apache.org/repos/dist/dev/incubator/apisix/0.9-RC1/apache-apisix-0.9-rc1-incubating-src.tar.gz ``` 2. Checksums and signatures ``` wget https://dist.apache.org/repos/dist/dev/incubator/apisix/KEYS wget https://dist.apache.org/repos/dist/dev/incubator/apisix/0.9-RC1/apache-apisix-0.9-rc1-incubating-src.tar.gz.asc wget https://dist.apache.org/repos/dist/dev/incubator/apisix/0.9-RC1/apache-apisix-0.9-rc1-incubating-src.tar.gz.sha512 shasum -c apache-apisix-0.9-rc1-incubating-src.tar.gz.sha512 gpg --import KEYS # input `trust`, `5`, then `save` gpg --edit-key "wenming" gpg --verify apache-apisix-0.9-rc1-incubating-src.tar.gz.asc apache-apisix-0.9-rc1-incubating-src.tar.gz ``` 3. Unzip and Check files ``` tar zxvf apache-apisix-0.9-rc1-incubating-src.tar.gz ``` 4. Build Apache APISIX: The runtime environment for Apache APISIX requires OpenResty and etcd, So please install dependencies first: https://github.com/apache/incubator-apisix/blob/v0.9/doc/install-dependencies.md Then you can build from source release candidate: https://github.com/apache/incubator-apisix/blob/v0.9/doc/how-to-build.md#installation-via-source-release-candidate The vote will be open for at least 72 hours or until necessary number of votes are reached. Please vote accordingly: [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove with the reason Checklist for reference: [ ] Download links are valid. [ ] Checksums and PGP signatures are valid. [ ] DISCLAIMER is included. [ ] LICENSE and NOTICE files are good. [ ] No binary file. [ ] All files have license headers if necessary. Thanks, Ming Wen, Apache APISIX Twitter: _WenMing
Re: [VOTE] Accept StreamPipes into the Apache Incubator
+1 (non-binding) Thanks, Ming Wen, Apache APISIX Twitter: _WenMing Dominik Riemer 于2019年11月8日周五 上午3:00写道： > Hi all, > > following up the [DISCUSS] thread on StreamPipes ( > https://lists.apache.org/thread.html/1cf79ef65888f695b4b925fd67ef8a2b845f6b0931c251a0ff1115e1@%3Cgeneral.incubator.apache.org%3E), > I would like to call a VOTE to accept StreamPipes into the Apache Incubator. > > Please cast your vote: > > [ ] +1, bring StreamPipes into the Incubator > [ ] +0, I don't care either way > [ ] -1, do not bring StreamPipes into the Incubator, because... > > The vote will open at least for 72 hours and only votes from the Incubator > PMC are binding, but votes from everyone are welcome. > > Dominik > > > StreamPipes Proposal ( > https://cwiki.apache.org/confluence/display/INCUBATOR/StreamPipesProposal) > > == Abstract == > StreamPipes is a self-service (Industrial) IoT toolbox to enable > non-technical users to connect, analyze and explore (Industrial) IoT data > streams. > > = Proposal = > > The goal of StreamPipes (www.streampipes.org) is to provide an > easy-to-use toolbox for non-technical users, e.g., domain experts, to > exploit data streams coming from (Industrial) IoT devices. Such users are > provided with an intuitive graphical user interface with the Pipeline > Editor at its core. Users are able to graphically model processing > pipelines based on data sources (streams), data processors and data sinks. > Data processors and sinks are self-contained microservices, which implement > either stateful or stateless processing logic (e.g., a trend detection or > image classifier). Their processing logic is implemented using one of > several provided wrappers (we currently have wrappers for > standalone/Edge-based processing, Apache Flink, Siddhi and working wrapper > prototypes for Apache Kafka Streams and Spark, in the future we also plan > to integrate with Apache Beam). An SDK allows to easily create new pipeline > elements. Pipeline elements can be installed at runtime. To support users > in creating pipelines, an underlying semantics-based data model enables > pipeline elements to express requirements on incoming data streams that > need to be fulfilled, thus reducing modeling errors. > Data streams are integrated by using StreamPipes Connect, which allows to > connect data sources (based on standard protocols, such as MQTT, Kafka, > Pulsar, OPC-UA and further PLC4X-supported protocols) without further > programming using a graphical wizard. Additional user-faced modules of > StreamPipes are a Live dashboard to quickly explore IoT data streams and a > wizard that generates code templates for new pipeline elements, a Pipeline > Element Installer used to extend the algorithm feature set at runtime. > > === Background === > StreamPipes was started in 2014 by researchers from FZI Research Center > for Information Technology in Karlsruhe, Germany. The original prototype > was funded by an EU project centered around predictive analytics for the > manufacturing domain. Since then, StreamPipes was constantly improved and > extended by public funding mainly from federal German ministries. In early > 2018, the source code was officially released under the Apache License 2.0. > At the same time, while we focused on bringing the research prototype to a > production-grade tool, the first companies started to use StreamPipes. > Currently, the primary goal is to widen the user and developer base. At > ApacheCon NA 2019, after having talked to many people from the Apache > Community, we finally decided that we would like to bring StreamPipes to > the Apache Incubator. > > === Rationale === > The (Industrial) IoT domain is a highly relevant and emerging sector. > Currently, IoT platforms are offered by many vendors ranging from SMEs up > to large enterprises. We believe that open source alternatives are an > important cornerstone for manufacturing companies to easily adopt > data-driven decision making. From our point of view, StreamPipes fits very > well into the existing (I)IoT ecosystem within the ASF, with projects such > as Apache PLC4X focusing on connecting machine data from PLCs, or other > tools we are also using either in the core of StreamPipes or with > integrations (Apache Kafka, Apache IoTDB, Apache Pulsar). StreamPipes > itself focuses on enabling self-service IoT data analytics for > non-technical users. > The whole StreamPipes code is currently on Github. To get a rough estimate > of the project size: > * streampipes: Backend and core modules, ~3300 commits > * streampipes-ui: User Interface, ~1300 commits > * streampipes-pipeline-elements: ~100 Pipeline Elements (data > processors/algorithms and sinks), ~500 Commits > * stre
Re: [DISCUSS] TubeMQ Proposal
yes, agreed, good luck for your incubating journey, and I hope TubeMQ can grow up to a diversity community. Thanks, Ming Wen Twitter: _WenMing 俊平堵 于2019年10月23日周三 上午9:52写道： > As others’ reply, the challenge of building a diversity community do exists > and we should sort it out during incubation process but no need to special > concern before the incubation (thanks for reminding though). > About maintaining version, from my experience, it is simple to keep only > one version here just like TubeMQ now when it is possible. However, I also > see many other Apache projects that some companies maintain an internal > version that take/contribute PR from/to open source version as upstream > which also works well. In my understanding, It is just a version management > choice - I didn’t see how challenges it will bring during the incubation > stage. Please correct me if I am wrong here. > > Thanks, > > Junping > > Ming Wen 于2019年10月22日 周二上午11:29写道： > > > Hi, this is an interesting proposal. > > > > I think the competition among different MQ is not an issue for incubator > > stage. Users and developers will have their own choices. > > > > I guess that your challenges during the incubation: > > expanding diversity (now committers come from one company), > > and dealing with the relationship between the tencent internal version > and > > the open source version (I guess the two are not consistent, if I am > wrong, > > please correct me) . > > > > Thanks, > > Ming Wen > > Twitter: _WenMing > > > > > > Dave Fisher 于2019年10月22日周二 上午10:38写道： > > > > > Hi - > > > > > > > On Oct 21, 2019, at 7:26 PM, 俊平堵 wrote: > > > > > > > > bq. You might be right about that the project currently I believe > > there's > > > > only one mentor with recent mentoring experience, and while all > > proposed > > > are > > > > ASF members, not all of them are active on the IPMC general list. It > > > might > > > > be better for the project to have at least one other mentor with > > > executive > > > > and is more active in the IPMC. What do others think? > > > > +1. Justin, do you have candidate to join the mentor team here? > > > > > > I’m on the Pulsar PMC with Sijie and know that he was also involved > with > > > DistributedLog which graduated into Bookkeeper. He will certainly be > good > > > help as a mentor. > > > > > > If Justin is good with this initial mix. I’m fine. If not then JBO has > > > offered. > > > > > > Best wishes. > > > > > > Regards, > > > Dave > > > > > > > > > > > Thanks, > > > > > > > > Junping > > > > > > > > Justin Mclean 于2019年10月21日周一 下午10:31写道： > > > > > > > >> Hi, > > > >> > > > >>> The first one is if we are able to mentor the project well enough > > (old > > > >> discussion). > > > >> > > > >> You might be right about that the project currently I believe > there's > > > only > > > >> one mentor with recent mentoring experience, and while all proposed > > are > > > ASF > > > >> members, not all of them are active on the IPMC general list. It > might > > > be > > > >> better for the project to have at least one other mentor with > > executive > > > and > > > >> is more active in the IPMC. What do others think? > > > >> > > > >>> As the project comes from Tencent I assume that the community is > > mostly > > > >> Chinese and due to the language barrier (and probably a different > > > culture) > > > >> we have seen that these projects tend to be "more challenging" (this > > > does > > > >> not describe it accurate enough but I hope that readers understand > > what > > > I > > > >> mean). > > > >> > > > >> While projects in this group do have some challenges, I don’t > believe > > > it’s > > > >> anymore than other projects from different background. In some ways > > the > > > ASF > > > >> model is a good cultural fit - see Sharan’s thesis on that. > > > >> > > > >> Thanks, > > > >> Justin > > > >> > > > >> > > > >> > - > > > >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > > >> For additional commands, e-mail: general-h...@incubator.apache.org > > > >> > > > >> > > > > > > > > > - > > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > > > > > >
Re: [DISCUSS] TubeMQ Proposal
Hi, this is an interesting proposal. I think the competition among different MQ is not an issue for incubator stage. Users and developers will have their own choices. I guess that your challenges during the incubation: expanding diversity (now committers come from one company), and dealing with the relationship between the tencent internal version and the open source version (I guess the two are not consistent, if I am wrong, please correct me) . Thanks, Ming Wen Twitter: _WenMing Dave Fisher 于2019年10月22日周二 上午10:38写道： > Hi - > > > On Oct 21, 2019, at 7:26 PM, 俊平堵 wrote: > > > > bq. You might be right about that the project currently I believe there's > > only one mentor with recent mentoring experience, and while all proposed > are > > ASF members, not all of them are active on the IPMC general list. It > might > > be better for the project to have at least one other mentor with > executive > > and is more active in the IPMC. What do others think? > > +1. Justin, do you have candidate to join the mentor team here? > > I’m on the Pulsar PMC with Sijie and know that he was also involved with > DistributedLog which graduated into Bookkeeper. He will certainly be good > help as a mentor. > > If Justin is good with this initial mix. I’m fine. If not then JBO has > offered. > > Best wishes. > > Regards, > Dave > > > > > Thanks, > > > > Junping > > > > Justin Mclean 于2019年10月21日周一 下午10:31写道： > > > >> Hi, > >> > >>> The first one is if we are able to mentor the project well enough (old > >> discussion). > >> > >> You might be right about that the project currently I believe there's > only > >> one mentor with recent mentoring experience, and while all proposed are > ASF > >> members, not all of them are active on the IPMC general list. It might > be > >> better for the project to have at least one other mentor with executive > and > >> is more active in the IPMC. What do others think? > >> > >>> As the project comes from Tencent I assume that the community is mostly > >> Chinese and due to the language barrier (and probably a different > culture) > >> we have seen that these projects tend to be "more challenging" (this > does > >> not describe it accurate enough but I hope that readers understand what > I > >> mean). > >> > >> While projects in this group do have some challenges, I don’t believe > it’s > >> anymore than other projects from different background. In some ways the > ASF > >> model is a good cultural fit - see Sharan’s thesis on that. > >> > >> Thanks, > >> Justin > >> > >> > >> - > >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > >> For additional commands, e-mail: general-h...@incubator.apache.org > >> > >> > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: Remove PMC incubator page
+1 Good for me. Sheng Wu 于2019年10月18日周五 下午7:26写道： > Good for me. > > Sheng Wu 吴晟 > > Apache SkyWalking > Apache Incubator > Apache ShardingSphere, ECharts, DolphinScheduler podlings > Zipkin > Twitter, wusheng1108 > > > Justin Mclean 于2019年10月18日周五 上午11:59写道： > > > Hi, > > > > The page here [1] doesn’t really add anything that is not written out > > elsewhere and seems redundant. If no-one objects I’ll remove it. > > > > Thanks, > > Justin > > > > > > 1. https://incubator.apache.org/guides/pmc.html > > - > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > > -- Best regards, Ming Wen 温铭 Twitter: _WenMing
