+1, I support InLong to graduate from the Apache incubator and become a top-level Apache project
At 2022-05-11 11:47:33, "Forward Xu" <[email protected]> wrote: >+1 > >best >forwardxu > >On 2022/05/11 03:21:11 Zijie Lu wrote: >> +1 I support InLong to graduate from the Apache incubator and >> become a top-level Apache project. >> >> On 2022/05/11 03:06:38 Daniel Li wrote: >> > +1, I support InLong to graduate from the Apache incubator and >> > become a top-level Apache project. >> > >> > On 2022/05/11 03:04:09 blue wang wrote: >> > > +1, I support InLong to graduate from the Apache incubator and >> > > become a top-level Apache project. >> > > >> > > 廖锐 <[email protected]> 于2022年5月11日周三 11:03写道： >> > > >> > > > +1, I support InLong to graduate from the Apache incubator and >> > > > become a top-level Apache project. >> > > > >> > > > Charles Zhang <[email protected]> 于2022年5月11日周三 10:51写道： >> > > > >> > > > > Hi, InLong community >> > > > > >> > > > > After community discussions [1], we got enough feedback that >> > > > > community >> > > > > support InLong to graduate from the Apache incubator and become a >> > > > top-level >> > > > > Apache project. >> > > > > >> > > > > >> > > > > InLong has been incubating since 2019-11-03. In the past two and a >> > > > > half >> > > > > years, the InLong project developed stably and sustainably with the >> > > > Apache >> > > > > Way. We used the ASF project maturity model to evaluate the InLong >> > > > project, >> > > > > by self-checking the InLong maturity model [2] and the pre-graduation >> > > > Check >> > > > > List [3], we believe that the InLong project is ready to graduate >> > > > > from >> > > > > Apache Incubator. We make a brief summary of several aspects to show >> > > > > the >> > > > > status of InLong: >> > > > > >> > > > > >> > > > > *Code, License, and Copyright* >> > > > > >> > > > > InLong 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 [4]. All the status files, >> > > > > license >> > > > > headers, and copyright are up to date. >> > > > > >> > > > > >> > > > > *Release* >> > > > > >> > > > > InLong community released a total of 11 versions by 6 different >> > > > > release >> > > > > managers, of which 5 versions are the original TubeMQ, and 6 >> > > > > versions are >> > > > > after the name was changed to InLong. The release cadence is about 2 >> > > > > months. All versions closed more than 2100 issues, with an average >> > > > > of 200 >> > > > > issues per version [5]. >> > > > > >> > > > > >> > > > > *Quality* >> > > > > >> > > > > InLong community created more than 7 GitHub Workflows, which cover >> > > > > compilation, unit testing, integration testing, license checking, >> > > > > Docker >> > > > > image creation, Helm Charts testing, etc. All code patches need to >> > > > > pass >> > > > > these pipelines first. In addition, InLong has a matching Pull >> > > > > Request >> > > > > template and commit requirements to ensure that all commits have >> > > > > corresponding classification and traceability. >> > > > > >> > > > > >> > > > > *Community* >> > > > > >> > > > > InLong community 5 Mentors, 18 PPMCs, 8 Committers, and more than 99 >> > > > unique >> > > > > Contributors [6]. All PPMCs and Committers are spread across more >> > > > > than 8 >> > > > > different organizations, and some of them focus on document >> > > > > management, >> > > > > tools building, and official website support. The community also has >> > > > > created channels like Email, Slack, Twitter, WeChat, and GitHub >> > > > Discussions >> > > > > to communicate, with more than 650 subscribers, and actively >> > > > > participated >> > > > > in or held more than 15 online or offline meetups to increase >> > > > > community >> > > > > influence. we think it's a diverse and Influential community now. >> > > > > >> > > > > >> > > > > *Independence* >> > > > > >> > > > > InLong community added 10 Committers, 3 PPMCs started from >> > > > > incubating, >> > > > they >> > > > > are from 4 different organizations, and all PPMCs and Committers are >> > > > spread >> > > > > across 8 different organizations. >> > > > > >> > > > > >> > > > > For these reasons, we initiate this vote on whether to graduate >> > > > > InLong >> > > > from >> > > > > Apache Incubator, everyone from the InLong community has the right to >> > > > vote, >> > > > > please vote on graduating InLong from Apache Incubator: >> > > > > >> > > > > [ ] +1 yes, I support InLong to graduate from the Apache incubator >> > > > > and >> > > > > become a top-level Apache project. >> > > > > >> > > > > [ ] +0 no opinion >> > > > > >> > > > > [ ] -1 no, the InLong project is not ready to graduate, because ... >> > > > > >> > > > > >> > > > > [1] https://lists.apache.org/thread/pzqk3z4pbbh3qx0cl1hmpzo1305p2lro >> > > > > >> > > > > [2] >> > > > > >> > > > > >> > > > https://cwiki.apache.org/confluence/pages/viewpage.action?spaceKey=INLONG&title=Maturity+Assessment+for+InLong >> > > > > >> > > > > [3] >> > > > > https://cwiki.apache.org/confluence/display/INLONG/Graduation+Check+List >> > > > > >> > > > > [4] https://github.com/apache/incubator-inlong/tree/master/licenses >> > > > > >> > > > > [5] https://github.com/apache/incubator-inlong/issues >> > > > > >> > > > > [6] https://whimsy.apache.org/roster/ppmc/inlong >> > > > > >> > > > > -- >> > > > > Best wishes, >> > > > > Charles Zhang >> > > > > >> > > > >> > > >> > >>
