Re: [VOTE] Graduate Apache EventMesh(incubating) as an Apache Top Level Project
+1 On 2023/02/10 02:31:56 Eason Chen wrote: > Dear Apache Incubator Community and IPMC members, > > After having the graduation discussion in the EventMesh community [1], > we passed the vote within the EventMesh community [2] and the vote > result was published[3]. > We then discussed the graduation for EventMesh in the Apache Incubator > Community [4], where no issues were raised and positive replies were > received. > > I would like to start this voting thread to request graduating Apache > EventMesh(incubating) from Apache Incubator as a Top Level Project. > > Please provide your vote accordingly: > [ ] +1 Yes, I support the EventMesh project to graduate from the > Apache Incubator. > [ ] +0 No opinion. > [ ] -1 No, the EventMesh project is not ready to graduate, because... > > Thank you for participating in the vote. This vote will stay open for > at least 72 hours. > > Here is an overview of the Apache EventMesh(incubating) to help with the vote. > > *Community* > > ● 5 new PPMC members were added, bringing the total number of PPMC > members to 14 from at least 9 different organizations. > ● 20 new Committers were added, bringing the total number of > committers to 42 from at least 30 different organizations. > ● 220+ new contributors participate in the community. The number of > contributors is now 250+ and growing. > ● 20 Bi-weekly online meetings were held among the committers, > contributors, and users. The meeting minutes are recorded on the > mailing list[5] and cwiki [6]. > ● The dev@eventmesh mailing list currently has 117 subscribers. > ● We've confirmed the VP, PMC, and Committers in the preparation > discussion at private@eventmesh [7]. Eason > Chen(chenguangsh...@apache.org) was recommended as Vice President. > > *Project* > > ● Apache EventMesh(incubating) builds a fully serverless platform for > distributed event-driven applications. > ● Project maturity model is detailed in [8]. > ● EventMesh has been incubating [9] since 2021-02-18 for over 23 months. > ● EventMesh community released a total of 7 Apache releases [10] by 6 > different release managers from 5 different organizations. > ● 1300+ issues created, and 1100+ issues closed [11]. > ● 1600+ pull requests created, and 1600+ pull requests closed [12], > 2500+ commits added. > ● The release cadence is about 3 months, with an average of 180+ > issues and 230+ pull requests per release. > ● Please refer to the EventMesh project incubation status [13][14] for > more information. > > *Brands, License, and Copyright* > > ● We applied the brand [15], which has been reviewed and approved. > ● EventMesh community maintains project code on GitHub and all modules > code is under Apache 2.0 license. We have reviewed all the > dependencies and ensured they do not bring any license issues [16]. > All the status files, license headers, and copyright are up to date. > ● EventMesh official website [17] is compliant with Apache Foundation > requirements[18]. > > - > BEGINNING OF DRAFT RESOLUTION > - > > Establish the Apache EventMesh 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 fully serverless platform used to build distributed > event-driven applications. > > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee > (PMC), to be known as the "Apache EventMesh Project", be and hereby is > established pursuant to Bylaws of the Foundation; and be it further > > RESOLVED, that the Apache EventMesh Project be and hereby is responsible > for the creation and maintenance of software related to a fully > serverless platform used to build distributed event-driven applications; > and be it further > > RESOLVED, that the office of "Vice President, Apache EventMesh" 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 EventMesh > Project, and to have primary responsibility for management of the > projects within the scope of responsibility of the Apache EventMesh > 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 EventMesh > Project: > > * Alex Luo > * Du Heng > * Eason Chen > * Francois Papon > * Jean-Baptiste Onofré > * Junping Du > * Justin Mclean > * ShannonDing > * Von Gosling > * Weiqiang Liang > * Wenjun Ruan > * XiaoShuang Li > * Xue Weiming > * Yuwei Zhu > > NOW, THEREFORE, BE IT FURTHER RESOLVED, that
Re: [VOTE] Graduate Apache EventMesh(incubating) as an Apache Top Level Project
+1 I can’t agree more! On 2023/02/09 12:19:14 Eason Chen wrote: > Dear Apache Incubator Community and IPMC members, > > After having the graduation discussion in the EventMesh community [1], > we passed the vote within the EventMesh community [2] and the vote > result was published[3]. > We then discussed the graduation for EventMesh in the Apache Incubator > Community [4], where no issues were raised and positive replies were > received. > > I would like to start this voting thread to request graduating Apache > EventMesh(incubating) from Apache Incubator as a Top Level Project. > > Please provide your vote accordingly: > [ ] +1 Yes, I support the EventMesh project to graduate from the > Apache Incubator. > [ ] +0 No opinion. > [ ] -1 No, the EventMesh project is not ready to graduate, because... > > Thank you for participating in the vote. This vote will stay open for > at least 72 hours. > > Here is an overview of the Apache EventMesh(incubating) to help with the vote. > > *Community* > > ● 5 new PPMC members were added, bringing the total number of PPMC > members to 14 from at least 9 different organizations. > ● 20 new Committers were added, bringing the total number of > committers to 42 from at least 30 different organizations. > ● 220+ new contributors participate in the community. The number of > contributors is now 250+ and growing. > ● 20 Bi-weekly online meetings were held among the committers, > contributors, and users. The meeting minutes are recorded on the > mailing list[5] and cwiki [6]. > ● The dev@eventmesh mailing list currently has 117 subscribers. > ● We've confirmed the VP, PMC, and Committers in the preparation > discussion at private@eventmesh [7]. Eason > Chen(chenguangsh...@apache.org) was recommended as Vice President. > > *Project* > > ● Apache EventMesh(incubating) is a fully serverless platform used to > build distributed event-driven applications. > ● Project maturity model is detailed in [8]. > ● EventMesh has been incubating [9] since 2021-02-18 for over 23 months. > ● EventMesh community released a total of 7 Apache releases [10] by 6 > different release managers from 5 different organizations. > ● 1300+ issues created, and 1100+ issues closed [11]. > ● 1600+ pull requests created, and 1600+ pull requests closed [12], > 2500+ commits added. > ● The release cadence is about 3 months, with an average of 180+ > issues and 230+ pull requests per release. > ● Please refer to the EventMesh project incubation status [13][14] for > more information. > > *Brands, License, and Copyright* > > ● We applied the brand [15], which has been reviewed and approved. > ● EventMesh community maintains project code on GitHub and all modules > code is under Apache 2.0 license. We have reviewed all the > dependencies and ensured they do not bring any license issues [16]. > All the status files, license headers, and copyright are up to date. > ● EventMesh official website [17] is compliant with Apache Foundation > requirements[18]. > > - > BEGINNING OF DRAFT RESOLUTION > - > > Establish the Apache EventMesh 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 fully serverless platform used to build distributed > event-driven applications. > > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee > (PMC), to be known as the "Apache EventMesh Project", be and hereby is > established pursuant to Bylaws of the Foundation; and be it further > > RESOLVED, that the Apache EventMesh Project be and hereby is responsible > for the creation and maintenance of software related to EventMesh is a > fully serverless platform used to build distributed event-driven > applications; and be it further > > RESOLVED, that the office of "Vice President, Apache EventMesh" 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 EventMesh > Project, and to have primary responsibility for management of the > projects within the scope of responsibility of the Apache EventMesh > 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 EventMesh > Project: > > * Alex Luo > * Du Heng > * Eason Chen > * Francois Papon > * Jean-Baptiste Onofré > * Junping Du > * Justin Mclean > * ShannonDing > * Von Gosling > * Weiqiang Liang > * Wenjun Ruan > * XiaoShuang Li > * Xue Weiming > * Yuwei Zhu > > NOW,
Re: [DISCUSS] Graduate Apache EventMesh(incubating) as an Apache Top Level Project
+1 congratulations! I can’t wait to hear the news. On 2023/02/06 09:27:26 Eason Chen wrote: > Dear Apache Incubator Community, > > Apache EventMesh has been incubating [1] since 2021-02-18 for over 23 > months. The EventMesh community has grown rapidly under the guidance > of mentors and the Apache Way. After self-checking the EventMesh maturity > model [2] and having a discussion [3], we started a vote [4] for > graduation within the EventMesh community and got unanimous positive > feedback [5]. We believe Apache EventMesh (Incubating) is now ready to > graduate to be a Top Level Project. We'd like to have a discussion > with the incubator community and get more feedback. > > Here is an overview of the Apache EventMesh(incubating) to help with > the discussion. > > *Community* > > ● 5 new PPMC members were added, bringing the total number of PPMC > members to 14 from at least 9 different organizations. > ● 20 new Committers were added, bringing the total number of > committers to 42 from at least 23 different organizations. > ● 210+ new contributors participate in the community. The number of > contributors is now 240+ and growing. > ● 20 Bi-weekly online meetings were held among the committers, > contributors, and users. The meeting minutes are recorded on the > mailing list[6] and wiki [7]. > ● The dev@eventmesh mailing list currently has 117 subscribers. > ● We've confirmed the VP, PMC, and Committers in the preparation > discussion at private@eventmesh [8]. Eason > Chen(chenguangsh...@apache.org) was recommended as Vice President. > > *Project* > > ● Apache EventMesh(incubating) builds a fully serverless platform used > to build distributed event-driven applications. > ● EventMesh community released a total of 7 Apache releases [9] by 6 > different release managers from 5 different organizations. > ● 1300+ issues created, and 1100+ issues closed [10]. > ● 1600+ pull requests created, and 1600+ pull requests closed [11], > 2500+ commits added. > ● The release cadence is about 3 months, with an average of 180+ > issues and 230+ pull requests per release. > > *Brands, License, and Copyright* > > ● We submitted an application for the brand [12], which has been > reviewed and approved. > ● EventMesh community maintains project code on GitHub and all modules > code is under Apache 2.0 license. We have reviewed all the > dependencies and ensured they do not bring any license issues [13]. > All the status files, license headers, and copyright are up to date. > ● EventMesh official website [14] is compliant with Apache Foundation > requirements. > > - > BEGINNING OF DRAFT RESOLUTION > - > > Establish the Apache EventMesh 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 EventMesh is a fully serverless platform used to build > distributed event-driven applications. > > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee > (PMC), to be known as the "Apache EventMesh Project", be and hereby is > established pursuant to Bylaws of the Foundation; and be it further > > RESOLVED, that the Apache EventMesh Project be and hereby is responsible > for the creation and maintenance of software related to EventMesh is a > fully serverless platform used to build distributed event-driven > applications; and be it further > > RESOLVED, that the office of "Vice President, Apache EventMesh" 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 EventMesh > Project, and to have primary responsibility for management of the > projects within the scope of responsibility of the Apache EventMesh > 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 EventMesh > Project: > > * Alex Luo > * Du Heng > * Eason Chen > * Francois Papon > * Jean-Baptiste Onofré > * Junping Du > * Justin Mclean > * ShannonDing > * Von Gosling > * Weiqiang Liang > * Wenjun Ruan > * XiaoShuang Li > * Xue Weiming > * Yuwei Zhu > > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Eason Chen be appointed > to the office of Vice President, Apache EventMesh, 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 EventMesh
