+1(non-binding) Thanks for driving this discussion of graduation. Excited to see Fluss graduate.
Best regards, Junbo Wang > 2026年5月15日 15:52，Anton Borisov <[email protected]> 写道： > > Hi all, > > +1 (non-binding) for graduating Fluss as a TLP. > > Thanks Yu for driving this discussion and for the comprehensive > summary. It is exciting to see Fluss reach this point in its > incubation journey. > > As someone who joined the project during this period, I have really > appreciated the openness of the community: active reviews, thoughtful > design discussions, regular releases, and a clear willingness to help > new contributors get involved. Combined with the growing production > adoption and ecosystem interest, I think Fluss is well positioned for > graduation. > > Looking forward to seeing Fluss become a TLP, and to continuing to > help the project grow. > > -- Anton > > пт, 15 мая 2026 г. в 08:10, Mehul Batra <[email protected]>: >> >> Hi all, >> >> +1 (binding) for graduating Fluss as a TLP. >> >> Thanks Yu for driving this discussion and for the detailed summary. It's a >> moment worth reflecting on. When I look at what this community has >> accomplished 5 compliant releases, 120 contributors from 8+ organizations, >> consistent and open governance I see a project that has genuinely earned >> graduation. >> >> What I'm most proud of is how we've approached community building. Openness >> for us isn't just a license or a codebase it's transparent governance, >> mentorship for new contributors, and creating space for people to grow >> alongside the project. I say this personally: I am myself a product of that >> mentorship culture, having been guided by existing members going back to >> the initial days, I couldn't be less grateful to Apache community and Fluss >> members. That kind of investment in people is what makes a community last, >> and I'm glad to see it carried forward in Fluss. >> >> We've had the privilege of representing Apache Fluss at talks and events, >> sharing our vision for streaming storage as the real-time data layer in >> AI-native Lakehouse architectures. The conversations have been energizing, >> and there's clear momentum in the ecosystem. Graduation is the right next >> step not just a milestone, but a launchpad for broader adoption, deeper >> integrations, and a community that continues to grow and pay it forward. >> >> Looking forward to what comes next! >> >> Best regards, >> Mehul Batra >> >> On Fri, May 15, 2026 at 11:56 AM Prajwal Banakar <[email protected]> >> wrote: >> >>> Hi Yu and everyone, >>> >>> +1 (non-binding). >>> >>> It is incredibly exciting to see this graduation discussion. As a student >>> contributor, witnessing the community’s evolution has been an invaluable >>> learning experience. >>> >>> I am grateful for the opportunity to work alongside such talented >>> developers and look forward to seeing Fluss thrive as a TLP! >>> >>> Best regards, >>> Prajwal Banakar >>> >>> >>> On Fri, 15 May, 2026, 11:52 am Yang Wang, <[email protected]> >>> wrote: >>> >>>> Thanks, Yu, for driving this initiative and summarizing the progress. I >>>> fully support the graduation of Apache Fluss. >>>> >>>> +1 (non-binding) >>>> >>>> Best regards, >>>> Yang >>>> >>>> Yu Li <[email protected]> 于2026年5月13日周三 19:50写道： >>>> >>>>> Dear Fluss Devs, >>>>> >>>>> We, the Fluss community, began our incubation journey on June 4th, >>> 2025. >>>>> Since then, through the continuous efforts of all contributors, our >>>>> community has developed steadily and matured significantly, now >>>> approaching >>>>> the graduation criteria [1]. I would therefore like to initiate a >>>>> discussion on graduating Fluss as a TLP. Below are some statistics I >>> have >>>>> collected, please review them and let me know your thoughts. >>>>> >>>>> - Currently, our community comprises 20 committers (including mentors) >>>> from >>>>> more than 8 different companies, with 14 serving as PPMC members [2]. >>>>> - At present, we have 120 contributors. >>>>> - Throughout the incubation period, we have made 5 releases [3] [4] [5] >>>>> over 11 months, maintaining a stable cadence. >>>>> - We have had 4 different release managers to date. >>>>> - Our software is used in production by 10+ well-known entities. >>>>> - To date, we have opened 1,510 issues, of which 1,034 have been >>>>> successfully resolved [6]. >>>>> - We have submitted a total of 1,759 PRs, of which 1,532 have been >>> merged >>>>> or closed [7]. >>>>> - Through self-assessment [8], we have met all maturity criteria as >>>>> outlined in [9]. >>>>> >>>>> And below is the drafted graduation resolution, JFYI: >>>>> ------------------- >>>>> Establish the Apache Fluss Project >>>>> >>>>> WHEREAS, the Board of Directors deems it to be in the best interests of >>>>> the Foundation and consistent with the Foundation's purpose to >>> establish >>>>> a Project Management Committee charged with the creation and >>> maintenance >>>>> of open-source software, for distribution at no charge to the public, >>>>> related to a streaming storage built for real-time analytics which can >>>>> serve as the real-time data layer for Lakehouse architectures. >>>>> >>>>> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee >>>>> (PMC), to be known as the "Apache Fluss Project", be and hereby is >>>>> established pursuant to Bylaws of the Foundation; and be it further >>>>> >>>>> RESOLVED, that the Apache Fluss Project be and hereby is responsible >>> for >>>>> the creation and maintenance of software related to a streaming storage >>>>> built for real-time analytics which can serve as the real-time data >>>>> layer for Lakehouse architectures; and be it further >>>>> >>>>> RESOLVED, that the office of "Vice President, Apache Fluss" be and >>>>> hereby is created, the person holding such office to serve at the >>>>> direction of the Board of Directors as the chair of the Apache Fluss >>>>> Project, and to have primary responsibility for management of the >>>>> projects within the scope of responsibility of the Apache Fluss >>> Project; >>>>> and be it further >>>>> >>>>> RESOLVED, that the persons listed immediately below be and hereby are >>>>> appointed to serve as the initial members of the Apache Fluss Project: >>>>> >>>>> * Becket Qin <[email protected]> >>>>> * Benchao Li <[email protected]> >>>>> * Feng Wang <[email protected]> >>>>> * Giannis Polyzos <[email protected]> >>>>> * Jark Wu <[email protected]> >>>>> * Jean-Baptiste Onofré <[email protected]> >>>>> * Jingsong Lee <[email protected]> >>>>> * Mehul Batra <[email protected]> >>>>> * Michael Koepf <[email protected]> >>>>> * Nicholas Jiang <[email protected]> >>>>> * Yu Li <[email protected]> >>>>> * Yunhong Zheng <[email protected]> >>>>> * Yuxia Luo <[email protected]> >>>>> * Zili Chen <[email protected]> >>>>> >>>>> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Jark Wu be appointed to >>> the >>>>> office of Vice President, Apache Fluss, to serve in accordance with and >>>>> subject to the direction of the Board of Directors and the Bylaws of >>> the >>>>> Foundation until death, resignation, retirement, removal or >>>>> disqualification, or until a successor is appointed; and be it further >>>>> >>>>> RESOLVED, that the Apache Fluss Project be and hereby is tasked with >>> the >>>>> migration and rationalization of the Apache Incubator Fluss podling; >>> and >>>>> be it further >>>>> >>>>> RESOLVED, that all responsibilities pertaining to the Apache Incubator >>>>> Fluss podling encumbered upon the Apache Incubator PMC are hereafter >>>>> discharged. >>>>> ------------------- >>>>> >>>>> Best Regards, >>>>> Yu >>>>> >>>>> [1] https://incubator.apache.org/guides/graduation.html >>>>> >>>>> [2] https://whimsy.apache.org/roster/ppmc/fluss >>>>> >>>>> [3] https://github.com/apache/fluss/releases >>>>> >>>>> [4] https://github.com/apache/fluss-rust/releases >>>>> >>>>> [5] https://github.com/apache/fluss-shaded/releases >>>>> >>>>> [6] https://github.com/apache/fluss/issues >>>>> >>>>> [7] https://github.com/apache/fluss/pulls >>>>> >>>>> [8] >>>>> >>>>> >>>> >>> https://cwiki.apache.org/confluence/display/FLUSS/Maturity+Assessment+for+Apache+Fluss >>>>> >>>>> [9] https://opendal.apache.org/community/maturity >>>>> >>>> >>>
