Hi Yu Li, and thanks for driving this. I fully relate to what Nicholas mentioned. Fluss has grown a lot over the graduation period, and it has attracted lots of people who have engaged with the community. I'm only excited to witness how much the project has evolved, all the work we have achieved during the incubation, and the excitement we keep on getting from people being involved. Overall, I can say with confidence that Fluss is a mature project, with a vibrant community and lots of promise.
+1 for me. Looking forward to the graduation of Apache Fluss (Incubating) and to the road ahead. Best, Giannis On Mon, May 25, 2026 at 10:32 AM Nicholas Jiang <[email protected]> wrote: > Hi Yu Li, > > Thanks for driving the discussion of graduation of Apache Fluss > (Incubating). Based on past observations, the Fluss community demonstrates > a remarkably high level of activity and robust health. It comprises > numerous contributors and corporate users from around the world who are > continuously driving its iteration. Currently, the Fluss community is > experiencing excellent growth and development. > > +1 for me. Looking forward to the graduation of Apache Fluss (Incubating). > > Regards, > Nicholas Jiang > > On 2026/05/25 06:50:58 Yu Li wrote: > > Hi All, > > > > About one year ago, we started the discussion to donate Fluss into the > > incubator as Apache Fluss, with the goal of building a more vibrant and > > vendor-neutral community [1] [2]. Since then, with the guidance of the > > Incubator, we have made significant progress - exceeding our own > > expectations - and have become a truly diverse community. > > > > Recently, after thorough discussions [3] [4], the community has voted [5] > > to proceed with graduation [6]. We would like to invite the Incubator PMC > > to review our progress and welcome any feedback regarding our readiness > to > > graduate. > > > > Below are key facts and project highlights from the incubation period, > > along with the draft resolution: > > > > - Currently, our community consists of 20 committers (including mentors) > > from more than 8 different companies, with 14 serving as PPMC members[7]. > > > > - At present, we boast 121 contributors. > > > > - Throughout the incubation period, we've made 5 releases [8] [9] [10] in > > 11 months, at a stable pace. > > > > - We've had 4 different release managers to date. > > > > - Our software is used in production by 10+ well known entities. > > > > - As yet, we have opened 1,533 issues with 1,041 successfully resolved > [11]. > > > > - We have submitted a total of 1,796 PRs, out of which 1,551 have been > > merged or closed [12]. > > > > - Through self-assessment [13], we have met all maturity criteria as > > outlined in [14]. > > > > We've resolved all branding issues which include Logo, GitHub repo, > > document, website, and others [15] [16]. > > > > We'd also like to take this opportunity to extend a sincere thank you to > > our mentors, for their invaluable insight and assistance with getting us > to > > this point. > > > > Thanks a lot, Becket Qin, Jean-Baptiste Onofré, Jingsong Lee, Yu Li and > > Zili Chen! > > > > ------------------- > > > > 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 (on behalf of the Apache Fluss PPMC) > > > > [1] https://lists.apache.org/thread/osg23opm9x95xm318160808r984k0wk9 > > [2] https://incubator.apache.org/projects/fluss.html > > [3] https://lists.apache.org/thread/42w3l2j4575yk4yds4v6m9g9xv0nm48g > > [4] https://lists.apache.org/thread/9z36p0fg5vv7hh4dcr5yqc5f6krjry3x > > [5] https://lists.apache.org/thread/pf606zthz0xztl8cjzow50dx77c0217f > > [6] https://lists.apache.org/thread/4z2qlm3h8bvj268ob8h7gmw47jrslx1c > > > > [7] https://whimsy.apache.org/roster/ppmc/fluss > > > > [8] https://github.com/apache/fluss/releases > > > > [9] https://github.com/apache/fluss-rust/releases > > > > [10] https://github.com/apache/fluss-shaded/releases > > > > [11] https://github.com/apache/fluss/issues > > > > [12] https://github.com/apache/fluss/pulls > > > > [13] > > > https://cwiki.apache.org/confluence/display/FLUSS/Maturity+Assessment+for+Apache+Fluss > > > > [14] https://opendal.apache.org/community/maturity > > [15] https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-239 > > [16] https://whimsy.apache.org/pods/project/fluss > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
