+1 yes, I support ShenYu to graduate from the Apache incubator and
become a top-level Apache project.

ChenBin <s...@apache.org> 于2022年6月12日周日 22:32写道:

> +1 Hope the community gets better and better
>
> > 2022年6月12日 22:25,XiaoYu <xia...@apache.org> 写道:
> >
> > + 1  for me
> >
> > 张铎(Duo Zhang) <palomino...@gmail.com> 于2022年6月12日周日 21:28写道:
> >>
> >> +1, glad to see that we are finally ready to graduate.
> >>
> >> jincheng sun <sunjincheng...@gmail.com> 于2022年6月12日周日 11:21写道:
> >>
> >>> +1,Would be great to see  ShenYu graduating from the incubator. I
> believe
> >>> the ShenYu community will continues to make progress according to the
> >>> Apache way.
> >>>
> >>> Best,
> >>> Jincheng Sun
> >>>
> >>> Liang Liu <midnight2...@apache.org> 于2022年6月11日周六 18:38写道:
> >>>
> >>>> +1, congratulations, I hope it gets better and better.
> >>>>
> >>>> On 2022/06/10 05:01:46 XiaoYu wrote:
> >>>>> Hi ShenYu community,
> >>>>>
> >>>>> After a community discussion [1], we gathered a lot of feedback that
> >>>>> the community supported ShenYu to graduate from the Apache incubator
> >>>>> as a top-level Apache project.
> >>>>>
> >>>>> ShenYu has been incubating since 2021-05-03. For over a year, the
> >>>>> ShenYu community has made great progress and grown rapidly under the
> >>>>> guidance of our mentors. We believe the ShenYu project has met the
> >>>>> conditions for graduation. Project maturity model is detailed in [2],
> >>>>> and the summary on the state of the community are listed below.
> >>>>>
> >>>>> *Code, License, and Copyright*
> >>>>>
> >>>>> ShenYu 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 [3].
> All
> >>>>> the status files, license headers, and copyright are up to date.
> >>>>>
> >>>>> *Release*
> >>>>>
> >>>>> ShenYu community released a total of 4 versions by 4 different
> release
> >>>>> managers. The release cadence is about 3 months. All versions closed
> >>>>> more than 700 issues, with an average of 175 issues per version [4].
> >>>>>
> >>>>> *Quality*
> >>>>>
> >>>>> ShenYu community created more than 8 GitHub Workflows, which cover
> >>>>> compilation, unit testing, integration testing, license checking,
> >>>>> Docker image creation, etc. All code patches need to pass these
> >>>>> pipelines first. In addition, ShenYu has a matching Pull Request
> >>>>> template and commit requirements to ensure that all commits have
> >>>>> corresponding classification and traceability.
> >>>>>
> >>>>> *Community*
> >>>>>
> >>>>> ShenYu community has 6 Mentors, 30 PPMCs, 37 Committers, and more
> than
> >>>>> 270 unique Contributors [5].
> >>>>> The dev@shenyu.a.o mailing list currently has 355 subscribers, and
> all
> >>>>> major project discussions are happening in the dev@shenyu.a.o.
> >>>>> 26 Bi-weekly online meetings were held between committers,
> >>>>> contributors and users.
> >>>>>
> >>>>> *Independence*
> >>>>>
> >>>>> All of the 30 PPMC members are spread across more than 15 different
> >>>>> organizations.
> >>>>>
> >>>>> For these reasons, we initiate this vote on whether to graduate
> ShenYu
> >>>>> from Apache Incubator, everyone from the ShenYu community has the
> >>>>> right to vote, please vote on graduating ShenYu from Apache
> Incubator:
> >>>>>
> >>>>> [ ] +1 yes, I support ShenYu to graduate from the Apache incubator
> and
> >>>>> become a top-level Apache project.
> >>>>>
> >>>>> [ ] +0 no opinion
> >>>>>
> >>>>> [ ] -1 no, the ShenYu project is not ready to graduate, because ...
> >>>>>
> >>>>> This vote will be open for at least 72 hours.
> >>>>>
> >>>>> [1] https://lists.apache.org/thread/lc1xr9gjf1t2lbk8070thf1bgt3sq1v3
> >>>>> [2]
> https://github.com/apache/incubator-shenyu/blob/master/MATURITY.md
> >>>>> [3] https://github.com/apache/incubator-shenyu/tree/master/LICENSE
> >>>>> [4]
> >>>>
> >>>
> https://github.com/apache/incubator-shenyu/issues?q=is%3Aissue+is%3Aclosed+closed%3A%3E2021-05-03
> >>>>> [5] https://shenyu.apache.org/community/team
> >>>>>
> >>>>
> >>>
>
>

Reply via email to