+1

nicolchen <[email protected]> 于2023年1月30日周一 17:13写道:

> +1
> Congratulations! So glad to hear about this great news
>
> horoc <[email protected]> 于2023年1月30日周一 16:36写道:
>
> > +1
> >
> > *Congratulations for the EventMesh graduation.  I am very glad to be a
> > committer and will continue to contribute to this project. *
> >
> >
> > Eason Chen <[email protected]> 于2023年1月30日周一 10:07写道:
> >
> > > Dear all,
> > >
> > > EventMesh has been incubating in the Apache incubator since 2021-02-18
> > > for over 22 months, the community has developed rapidly under the
> > > guidance of mentors and the Apache Way. I'm glad to start a discussion
> > > about graduation as TLP for Apache EventMesh(Incubating).
> > >
> > > I've summarized some of the data below:
> > >
> > > *Community*
> > >
> > > ● 7 releases by 6 release managers from 5 different organizations.
> > > ● 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 38 from at least 23 different organizations.
> > > ● 210+ new contributors participate in the community. The number of
> > > contributors is now 240+ and growing.
> > > ● 19 Bi-weekly online meetings were held among the committers,
> > > contributors, and users. The meeting minutes are recorded on the
> > > mailing list[1] and wiki [2].
> > >
> > > *Project*
> > >
> > > ● 1300+ issues created, and 1100+ issues closed [3].
> > > ● 1600+ pull requests created, and 1600+ pull requests closed [4],
> > > 2500+ commits added.
> > > ● EventMesh official website [5] complies with Apache Foundation
> > > requirements [6].
> > > ● Project maturity model is detailed in [7].
> > > ● See EventMesh Project Incubation Status [8] for more info.
> > >
> > > *Brands, License, and Copyright*
> > >
> > > ● We submitted an application for the brand [9] and it 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 [10].
> > > All the status files, license headers, and copyright are up to date.
> > > ● EventMesh official website [11] is compliant with Apache Foundation
> > > requirements.
> > >
> > > Based on previous discussion resolutions from the private list [12],
> > > with Eason Chen as VP of Apache EventMesh, the PMC list is as follows:
> > > ● [email protected]
> > > ● [email protected]
> > > ● [email protected]
> > > ● [email protected]
> > > ● [email protected]
> > > ● [email protected]
> > > ● [email protected]
> > > ● [email protected]
> > > ● [email protected]
> > > ● [email protected]
> > > ● [email protected]
> > > ● [email protected]
> > > ● [email protected]
> > > ● [email protected]
> > >
> > > Thanks to all the EventMesh Mentors, PPMC, Committers, and
> > > Contributors, looking forward to your feedback. This discussion will
> > > be open for at least 72 hours.
> > >
> > > [1]https://lists.apache.org/[email protected]
> > > [2]https://cwiki.apache.org/confluence/display/EVENTMESH/Meetings
> > > [3]https://github.com/apache/incubator-eventmesh/issues
> > > [4]https://github.com/apache/incubator-eventmesh/pulls, and
> > > https://github.com/apache/incubator-eventmesh-site/pulls
> > > [5]https://eventmesh.apache.org/
> > > [6]https://whimsy.apache.org/pods/project/eventmesh
> > > [7]
> https://github.com/apache/incubator-eventmesh/blob/master/maturity.md
> > > [8]https://incubator.apache.org/projects/eventmesh.html
> > > [9]https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-189
> > > [10]https://github.com/apache/incubator-eventmesh/blob/master/LICENSE
> > > [11]https://eventmesh.apache.org/
> > > [12]https://lists.apache.org/thread/0vvsynyk6vy0vl5nhgrfj60y60ozyx5n
> > >
> > > Best Regards,
> > > Eason Chen
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: [email protected]
> > > For additional commands, e-mail: [email protected]
> > >
> > >
> >
>

Reply via email to