Since I joined the InLong project, the community has grown and matured significantly.
Inlong, in the beginning, was called TubeMQ which is only a message queue, and now, the community expand it to one-stop data integration framework with the whole capability of data ingestion, message queue(data cache), and ETL. Glad to see InLong is ready to graduate as a TLP. Thanks, Aloys Heal Chow <[email protected]> 于2022年5月6日周五 19:04写道： > It's great to see the discussion of graduation. Thank you, Charles Zhang. > > We achieved so many milestones in the past 2.5 years, which come from the > contributions of the whole community. > > A little question, do we plan to release the 1.2.0 before graduating from > Apache Incubator? > > Best regards, > Heal Chow > > On 2022/05/06 10:51:33 Goson zhang wrote: > > +1 for the graduation. > > > > Goson zhang <[email protected]> 于2022年5月6日周五 17:52写道： > > > > > Great to see this happen, good luck! > > > > > > Charles Zhang <[email protected]> 于2022年5月6日周五 17:19写道： > > > > > >> Hi, InLong community > > >> > > >> > > >> InLong has been incubating since 2019-11-03. In the past two and a > half > > >> years, the project has been renamed from TubeMQ to InLong, and > expanded > > >> its > > >> scope from a message queue service to a one-stop integration > framework for > > >> massive data. > > >> > > >> > > >> With 11 versions released [1], the project itself has become more > mature > > >> and stable. Since incubating in ASF, the project has: > > >> > > >> - > > >> > > >> Added 10 Committers, 3 PPMCs, all PPMCs and Committers spread > across 8 > > >> different organizations [2]. > > >> - > > >> > > >> A total of 11 versions were released 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 [1]. > > >> - > > >> > > >> Closed more than 2100 issues, with an average of 200 issues per > version > > >> [3]. > > >> - > > >> > > >> Reviewed all the dependencies and ensured no license issues. > > >> - > > >> > > >> Created channels like Email, Slack, Twitter, WeChat, and GitHub > > >> Discussions to communicate, with more than 650 subscribers. > > >> - > > >> > > >> Actively participated in or held more than 15 online or offline > meetups > > >> to increase community influence. > > >> > > >> > > >> During the incubation, the InLong project developed stably and > > >> continuously > > >> with the Apache Way. By sorting out and self-checking the InLong > maturity > > >> model [4], we believe that the InLong project has already met the > > >> conditions of graduation. Therefore, we would like to collect feedback > > >> from > > >> everyone through the discussion. > > >> > > >> > > >> Thanks to all the InLong's mentors, PPMC, Committers, and > Contributors, > > >> looking forward to your feedback. > > >> > > >> > > >> [1] https://incubator.apache.org/projects/inlong.html > > >> > > >> [2] https://whimsy.apache.org/roster/ppmc/inlong > > >> > > >> [3] https://github.com/apache/incubator-inlong/issues > > >> > > >> [4] > > >> > > >> > https://cwiki.apache.org/confluence/pages/viewpage.action?spaceKey=INLONG&title=Maturity+Assessment+for+InLong > > >> > > >> > > >> > > >> -- > > >> Best wishes, > > >> Charles Zhang > > >> > > > > > >
