+1 (non-binding) Congratulations!
Wei Liu <timcr...@apache.org> 于2023年2月6日周一 19:26写道： > +1 > > Congratulations! > > 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 <alex...@apache.org> > > * Du Heng <duhengfore...@apache.org> > > * Eason Chen <chenguangsh...@apache.org> > > * Francois Papon <fpa...@apache.org> > > * Jean-Baptiste Onofré <jbono...@apache.org> > > * Junping Du <junping...@apache.org> > > * Justin Mclean <jmcl...@apache.org> > > * ShannonDing <ding...@apache.org> > > * Von Gosling <vongosl...@apache.org> > > * Weiqiang Liang <wqli...@apache.org> > > * Wenjun Ruan <wen...@apache.org> > > * XiaoShuang Li <lixiaoshu...@apache.org> > > * Xue Weiming <mike...@apache.org> > > * Yuwei Zhu <walterzy...@apache.org> > > > > 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 Project be and hereby is tasked with > > the migration and rationalization of the Apache Incubator EventMesh > > podling; and be it further > > > > RESOLVED, that all responsibilities pertaining to the Apache Incubator > > EventMesh podling encumbered upon the Apache Incubator PMC are hereafter > > discharged. > > > > ------------------------------------------ > > END OF DRAFT RESOLUTION > > ------------------------------------------ > > > > Please refer to the EventMesh project incubation status [15][16] for > > more information. This discussion will continue for at least 72 hours, > > looking forward to your feedback. > > > > Best regards, > > Eason Chen > > > > [1] > https://cwiki.apache.org/confluence/display/INCUBATOR/EventMeshProposal > > [2] > https://github.com/apache/incubator-eventmesh/blob/master/maturity.md > > [3] https://lists.apache.org/thread/0vvsynyk6vy0vl5nhgrfj60y60ozyx5n > > [4] https://lists.apache.org/thread/c2jxkklyv2rr7tzs2jrrzwpq81mo9kzk > > [5] https://lists.apache.org/thread/dq0nx64ov1k7lbbdnml4f8dpw104p5wk > > [6] https://lists.apache.org/list.html?d...@eventmesh.apache.org > > [7] https://cwiki.apache.org/confluence/display/EVENTMESH/Meetings > > [8] https://lists.apache.org/thread/9h9dn5g8tv4hjr2rb6flptf7xcoxs691 > > [9] https://github.com/apache/incubator-eventmesh/releases > > [10] https://github.com/apache/incubator-eventmesh/issues > > [11] https://github.com/apache/incubator-eventmesh/pulls and > > https://github.com/apache/incubator-eventmesh-website/pulls > > [12] https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-189 > > [13] https://github.com/apache/incubator-eventmesh/blob/master/LICENSE > > [14] https://eventmesh.apache.org/ > > [15] https://incubator.apache.org/projects/eventmesh.html > > [16] https://incubator.apache.org/clutch/ > > > > --------------------------------------------------------------------- > > 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 > >
