Hi Yu and everyone,

+1 (binding) for graduation.

Thanks Yu for driving this initiative. I'm glad to see this discussion
happening now.

Looking at what the community has accomplished over the incubation
period — multiple compliant releases, a healthy and growing contributor
base, clean IP compliance, and well-established governance — I believe
we are well-positioned for graduation. The groundwork has been laid
thoroughly and I think this is the right time to take the next step.

From what I've observed with other recently graduated projects (e.g.,
Paimon, Answer), graduation provides a significant boost in visibility
and credibility that directly translates into broader adoption and
ecosystem partnerships. As a top-level project, it will be much easier
to promote Fluss in conferences, joint integrations, and production
use cases. I'm looking forward to contributing more on that front
post-graduation.

Best,
Leonard

> 2026 5月 15 14:04,Yang Guo <[email protected]> 写道:
> 
> +1 (non-binding)
> 
> Looking forward to seeing Fluss be an Apache TLP.
> 
> Regards,
> Yang Guo
> 
> On Fri, May 15, 2026 at 1:59 PM yuxia <[email protected]> wrote:
> 
>> Hi Yu,
>> 
>> Thanks for driving discussion of graduation.
>> 
>> +1 for graduating Fluss as a TLP.  I've witnessed the community's steady
>> growth throughout the incubation period. The statistics speak for
>> themselves — 5 releases with 4 different release managers, 120 contributors
>> from 8+ organizations. The community has clearly met the graduation
>> criteria.
>> 
>> Looking forward to seeing Fluss become a top-level project!
>> 
>> Best regards,
>> Yuxia
>> 
>> ----- 原始邮件 -----
>> 发件人: "Nicholas Jiang" <[email protected]>
>> 收件人: "dev" <[email protected]>
>> 发送时间: 星期五, 2026年 5 月 15日 下午 1:53:58
>> 主题: Re: [DISCUSS] Graduate Fluss as TLP
>> 
>> Thanks for driving discussion of graduation. It's really exciting for
>> community.
>> 
>> +1 (binding). Looking forward to see graduation of Fluss as a TLP.
>> 
>> Regards,
>> Nicholas Jiang
>> 
>> On 2026/05/13 11:49:37 Yu Li wrote:
>>> 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
>>> 
>> 

Reply via email to