+1. I am supporting EventMesh for graduation.

Alex Luo <[email protected]> 于2023年2月6日周一 10:28写道:

> +1. I am supporting EventMesh for graduation.
>
> Alex Luo
>
> On 2023/02/06 02:24:55 ShanPeng Qing wrote:
> >
> >
> >
> > With my +1, It's a happy journey, good luck to EventMesh
> >
> > At 2023-02-06 10:14:07, "Eason Chen" <[email protected]> wrote:
> > >With my +1(binding), It's a happy journey, good luck to EventMesh.
> > >
> > >On Sat, Feb 4, 2023 at 8:59 AM heng du <[email protected]>
> wrote:
> > >>
> > >> +1
> > >>
> > >> Huimin Li <[email protected]> 于2023年2月3日周五 14:37写道:
> > >>
> > >> > +1 I cannot agree more! Highly recommend eventmesh for graduation
> from
> > >> > Apache incubator!
> > >> >
> > >> > On 2023/02/02 02:42:34 Eason Chen wrote:
> > >> > > Dear all,
> > >> > >
> > >> > > After a community discussion [1], we received a lot of positive
> > >> > > feedback that the community supports EventMesh to graduate from
> the
> > >> > > Apache incubator as a top-level Apache project.
> > >> > > 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. We believe the EventMesh
> > >> > > project has met the conditions for graduation. The project
> maturity
> > >> > > model is detailed in [2] and the summary of the state of the
> community
> > >> > > is listed 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.
> > >> > > ● 20 Bi-weekly online meetings were held among the committers,
> > >> > > contributors, and users. The meeting minutes are recorded on the
> > >> > > mailing list[3] and wiki [4].
> > >> > > ● The dev@eventmesh mailing list currently has 105 subscribers.
> > >> > > ● We think it's a diverse and Influential community now. We've
> > >> > > confirmed the VP, PMC, and Committers in the preparation
> discussion
> > >> > > [5].
> > >> > >
> > >> > > *Project*
> > >> > >
> > >> > > ● 1300+ issues created, and 1100+ issues closed [6].
> > >> > > ● 1600+ pull requests created, and 1600+ pull requests closed [7],
> > >> > > 2500+ commits added.
> > >> > > ● EventMesh official website [8] complies with Apache Foundation
> > >> > > requirements [9].
> > >> > > ● Project maturity model is detailed in [10].
> > >> > > ● See EventMesh Project Incubation Status [11] for more info.
> > >> > > ● All code patches need to pass workflow pipelines first which
> cover
> > >> > > compiling, unit test, integration test, license check, etc.
> > >> > >
> > >> > > *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.
> > >> > >
> > >> > > For these reasons, we initiate this vote on whether to graduate
> > >> > > EventMesh from Apache Incubator, everyone from the EventMesh
> community
> > >> > > has the right to vote, please vote on graduating EventMesh from
> Apache
> > >> > > Incubator:
> > >> > >
> > >> > > [ ] +1 yes, I support EventMesh to graduate from the Apache
> incubator
> > >> > > and become a top-level Apache project.
> > >> > > [ ] +0 no opinion
> > >> > > [ ] -1 no, the EventMesh project is not ready to graduate,
> because ...
> > >> > >
> > >> > > This vote will be open for at least 72 hours.
> > >> > >
> > >> > > [1]
> https://lists.apache.org/thread/k1rx0hs106jh0926wfhvjj11xtzok6t6
> > >> > > [2]
> https://github.com/apache/incubator-eventmesh/blob/master/maturity.md
> > >> > > [3]https://lists.apache.org/[email protected]
> > >> > > [4]https://cwiki.apache.org/confluence/display/EVENTMESH/Meetings
> > >> > > [5]
> https://lists.apache.org/thread/0vvsynyk6vy0vl5nhgrfj60y60ozyx5n
> > >> > > [6]https://github.com/apache/incubator-eventmesh/issues
> > >> > > [7]https://github.com/apache/incubator-eventmesh/pulls, and
> > >> > > https://github.com/apache/incubator-eventmesh-site/pulls
> > >> > > [8]https://eventmesh.apache.org/
> > >> > > [9]https://whimsy.apache.org/pods/project/eventmesh
> > >> > > [10]
> > >> >
> https://github.com/apache/incubator-eventmesh/blob/master/maturity.md
> > >> > > [11]https://incubator.apache.org/projects/eventmesh.html
> > >> > > [12]https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-189
> > >> > > [13]
> https://github.com/apache/incubator-eventmesh/blob/master/LICENSE
> > >> > > [14]https://eventmesh.apache.org/
> > >> > >
> > >> > >
> > >> > > Best Regards,
> > >> > > Eason Chen
> > >> > >
> > >> > >
> ---------------------------------------------------------------------
> > >> > > To unsubscribe, e-mail: [email protected]
> > >> > > For additional commands, e-mail: [email protected]
> > >> > >
> > >> > >
> > >> >
> > >> >
> ---------------------------------------------------------------------
> > >> > To unsubscribe, e-mail: [email protected]
> > >> > For additional commands, e-mail: [email protected]
> > >> >
> > >> >
> > >
> > >---------------------------------------------------------------------
> > >To unsubscribe, e-mail: [email protected]
> > >For additional commands, e-mail: [email protected]
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>

Reply via email to