What the board has decided about this committee or office, and the reports it filed, most recent first. Generated from the published minutes.
These categorised views are best effort. They are read from the published minutes by a program, and what it can attribute to a committee depends on how each resolution happens to be worded — so a page may be incomplete, and nothing here overrides the minutes themselves. The raw minutes are the source of truth.
Please note. The board approves the minutes of a meeting at the meeting after it, and they are published then - so the most recent meeting is not usually here. ASF Members can read the draft in the board's own repository until it is.
[raw] the published minutes, which are the record. [main index]
| Date | Decision | Item | Outcome |
|---|---|---|---|
| 2026-07-15 | Established, Jark Wu as VP | special order | approved, minutes pending approval |
## Description: Apache Fluss is a streaming storage system built for real-time analytics and AI, serving as the real-time data layer for Lakehouse architectures. ## Project Status: Current project status: New, with high activity. Issues for the board: none ## Membership Data: Apache Fluss was founded 2026-07-15 (24 days ago) There are currently 22 committers and 14 PMC members in this project. The Committer-to-PMC ratio is roughly 3:2. Community changes, past quarter: - No new PMC members (project graduated recently). - Yang Wang was added as committer on 2026-08-06 ## Project Activity: The community completed and published the Apache Fluss graduation announcement, working with the ASF Marketing and Publicity team and updating the project website, blog, README, and community channels to reflect the new TLP status. Most post-graduation tasks have been completed. This work included: - Verifying the initial PMC roster, Chair setup, private mailing-list membership, and mailing-list moderation. - Removing remaining "Incubating" references and obsolete Incubator URLs from project websites, documentation, repository metadata, Maven configuration, CI, and notification settings. - Updating the Incubator status records to mark Fluss as graduated. - Creating and verifying the new `/dev/fluss/` and `/release/fluss/` distribution areas and copying the project KEYS file. - Updating release scripts, artifact naming, voting templates, release announcement templates, and the release guide for the TLP release process. The main technical focus is now Apache Fluss 1.0. The community plans to release it in August 2026 and is currently completing the remaining feature development and stabilization work. Apache Fluss also had a strong presence at Community Over Code Asia 2026. Fluss community members Yang Wang and Yuxia Luo delivered sessions about Fluss, while project contributors presented two additional Fluss-related sessions. These 4 sessions helped share the project's work with the broader Apache and open-source community. Apache Fluss 1.0 will be the project's first release as a TLP. It will follow the TLP release process without the `-incubating` suffix. The required release resources, scripts, templates, distribution locations, and release documentation have already been updated. The most recent release was Apache Fluss 0.9.1-incubating, released on 2026-05-04. ## Community Health: The Fluss community remains active and healthy. PMC members, committers, and contributors have worked collaboratively on the graduation process, post-graduation migration, community outreach, and preparation for the 1.0 release. Mailing-list activity during the past quarter was: - `dev@fluss.apache.org`: 375 emails, an 8% decrease from 406 in the previous quarter. - `issues@fluss.apache.org`: 3,259 emails, a 28% decrease from 4,476. - `user@fluss.apache.org`: 2 emails, an 89% decrease from 18. The decreases on the development and issues mailing lists do not indicate a community health concern. The reporting period overlapped with the summer vacation season, which is typically quieter because many community members take extended leave. At the same time, the community devoted substantial effort to graduation, post-graduation migration, and preparation for the 1.0 release. With most graduation-related work now complete, the community has shifted its focus back to completing the remaining features and stabilizing Apache Fluss 1.0. This renewed focus is already reflected in development activity: traffic on the dev mailing list increased from 70 emails in June to 129 in July, an increase of approximately 84%. Issue and pull-request activity is also expected to grow as the release approaches. The user mailing list has a small absolute message volume and is primarily used by community members for announcements. Most Fluss users currently ask questions and interact with the community through Slack instead of the mailing list. The project's recorded monthly community calls provide another sign of growing engagement. The latest call attracted approximately 30 participants despite the summer vacation period, and participation has increased over the past several months as more people have started engaging with the project. The Fluss LinkedIn page has also grown to approximately 2,300 followers within its first year; July 2026 marked the first anniversary of the page's creation. The addition of a new committer, the growing participation in monthly community calls, the project's expanding social-media reach, and the community's presence at Community Over Code Asia 2026 provide further signs of continued participation and growth. Overall, the PMC sees no concerns regarding community health. The observed changes in mailing-list traffic reflect the quieter summer period, a temporary shift in project focus, and the community's current communication-channel preferences rather than a reduction in project activity.
Fluss is a streaming storage built for real-time analytics which can serve as the real-time data layer for Lakehouse architectures. Fluss has been incubating since 2025-06-04. ### Three most important unfinished issues to address before graduating: 1. Complete more Apache releases: finalizing the Fluss-Rust 0.1.0 RC voting process and planning the Fluss 0.9.1 release for April. 2. Grow the community and attract more committers, contributors and users. 3. Fill out the maturity model and graduation preparations ### Are there any issues that the IPMC or ASF Board need to be aware of? There are no critical issues to report at this time. The team is currently preparing for the first release of Fluss-Rust, which includes C++ and Python bindings. We expect to initiate the IPMC voting process within the next few days. ### How has the community developed since the last report? - Add 2 new committers (Liebing Yu and Keith Lee), currently with total 19 committers. - Add 1 new PPMC member (Mehul Batra), the first invited PPMC member since incubation, currently with total 14 PPMC members (including mentors). - Held regular monthly community calls in January, February, and March. - Community presentations and outreach: * Fluss PPMC members presented at the joint "Apache Fluss × Apache Iceberg" webinar on January 20, 2026. * Giannis Polyzos spoke at QCon London on March 17, 2026. ### How has the project developed since the last report? - Released version 0.9.0 on March 2, 2026, marking the second official release under the Apache Incubator. This milestone reflects three months of collaborative development featuring over 400 commits and 12 highlighted features from the community. - Initiated the release of Fluss-Rust 0.1.0, which includes C++ and Python SDKs. This represents the first multi-language client version for Fluss, comprising over 200 commits from 27 contributors. - Active development is underway for version 1.0.0, with a target release date in June 2026. - The community discussed and finalized the [project roadmap for 2026](https://github.com/apache/fluss/discussions/2342). ### How would you assess the podling's maturity? Please feel free to add your own commentary. - [ ] Initial setup - [ ] Working towards first release - [ ] Community building - [X] Nearing graduation - [ ] Other: ### Date of last release: 2026-03-02 (v0.9.0) ### When were the last committers or PPMC members elected? 2026-03-10 ### Have your mentors been helpful and responsive? Yes. ### Is the PPMC managing the podling's brand / trademarks? Yes, everything is fine. ### Signed-off-by: - [X] (fluss) Jean-Baptiste Onofré Comments: I think Fluss is pretty close to graduation. Maybe worth to start evaluating the maturity model and other preparation steps. - [X] (fluss) Becket Qin Comments: I agree that Fluss is making steady progress and close to graduation. - [X] (fluss) Yu Li Comments: It's great to see new committers and a PMC member joining, which indicates a more diverse community. Regular sync meetings and consistent releases further reflect robust community development, and I'm confident the project is steadily progressing toward graduation. - [X] (fluss) Jingsong Lee Comments: +1 to fluss is close to graduation. I have seen a lot of participants working together to make the Fluss community better. - [ ] (fluss) Zili Chen Comments: ### IPMC/Shepherd notes:
Fluss is a streaming storage built for real-time analytics which can serve as the real-time data layer for Lakehouse architectures. Fluss has been incubating since 2025-06-04. ### Three most important unfinished issues to address before graduating: 1. The second release (v0.9.0) under the ASF incubator 2. Grow the community and attract more committers, contributors and users. 3. Fill out the maturity model ### Are there any issues that the IPMC or ASF Board need to be aware of? None at this time. ### How has the community developed since the last report? 1. Add 2 new committers, currently with total 17 committers. 2. The Fluss PPMC created a [LinkedIn page](https://s.apache.org/fluss-linkedin), which now has 1,302 followers, doubling organically over the past three months. 3. [Regular Monthly Community Call](s.apache.org/fluss-community-call) for October and November; December’s call was skipped due to the holiday season. 4. An “Apache Fluss × Apache Iceberg” joint webinar is scheduled for January 20, 2026, featuring contributors from both communities. 5. Community presentations and outreach: * Jark Wu and Giannis Polyzos presented at Flink Forward Barcelona (2025-10-15) * Leonard Xu presented Fluss at QCon Shanghai (2025-10-24) * Giannis Polyzos spoke at Big Data Europe (2025-11-19) * Jark Wu presented to the CMU Database Group (2025-12-08) ### How has the project developed since the last report? - Released v0.8.0 on 2025-11-09 which is the project’s first official release under the Apache Incubator. This milestone represents 4 months of collaborative development with 400+ commits from the community. - 8 new Fluss Improvement Proposals (FIPs) were submitted over the past quarter; several have already been approved and implemented. - Active development is underway for v0.9.0, targeted for release by end of January 2026. ### How would you assess the podling's maturity? - [ ] Initial setup - [ ] Working towards first release - [X] Community building - [ ] Nearing graduation - [ ] Other: Commentary: The project has successfully shipped its first Apache release and is actively growing its contributor and user base. Community engagement is strong, with regular calls, public talks, and cross-project collaboration. While still in its incubation, Fluss is steadily progressing toward graduation readiness. ### Date of last release: 2025-11-09 (v0.8.0) ### When were the last committers or PPMC members elected? 2025-11-28 ### Have your mentors been helpful and responsive? Yes. ### Is the PPMC managing the podling's brand / trademarks? Yes, everything is fine. ### Signed-off-by: - [X] (fluss) Jean-Baptiste Onofré Comments: The podling is operating great. The community is smoothly growing up. - [X] (fluss) Becket Qin Comments: - [X] (fluss) Yu Li Comments: Good to see new committers joining and vibrant community activities. - [X] (fluss) Jingsong Lee Comments: - [X] (fluss) Zili Chen Comments: ### IPMC/Shepherd notes:
Fluss is a streaming storage built for real-time analytics which can serve
as the real-time data layer for Lakehouse architectures.
Fluss has been incubating since 2025-06-04.
### Three most important unfinished issues to address before graduating:
1. Publish the first release under the ASF incubator
2. Grow the community and attract more committers, contributors and users.
3. Fill out the maturity model
### Are there any issues that the IPMC or ASF Board need to be aware of?
Fluss plans to release its first version (v0.8) under ASF incubator in
October and will need IPMC assistance, including validation and voting.
### How has the community developed since the last report?
- Add 2 new committers, currently with total 15 committers.
- The Fluss PPMC created a [LinkedIn page]
(https://www.linkedin.com/company/apachefluss/), which has 625
followers within ~3 months, all organic growth.
- [Regular Monthly Community Call]
(https://docs.google.com/document/d/18b7G_dvYx-1FogV7LWEFMHXze5D5T9XZ3h
9zSU75dDA/edit?tab=t.0#heading=h.9aenn0fakn4l) for July, Aug, Sept.
- Jark Wu presented Fluss at CommunityOverCode Asia 2025 on July 26th.
- Jark Wu and Giannis Polyzos are going to Flink Forward Barcelona 2025
to present Fluss on October 15th.
- Leonard Xu is going to QCon Shanghai to represent Fluss on October 24th.
- Giannis Polyzos is going to Big Data Europe to present Fluss on
November 19-21.
- Fluss participated #hacktoberfest2025
### How has the project developed since the last report?
We have completed the full migration of the website and codebase from
Alibaba to Apache.
Additionally, we’ve finalized development of Fluss v0.8 which was started
since the project entered ASF incubator.
This version introduces Streaming Lakehouse support with Apache Iceberg
and Lance. Now, all streaming events written to Fluss are automatically
converted into either Iceberg or Lance format in real-time, enabling
seamless lakehouse integration.
Besides, since introducing the Fluss Improvement Proposal (FIP) process
in July, we have already created 17 FIPs, many of which have been approved
and implemented.
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [ ] Initial setup
- [X] Working towards first release
- [ ] Community building
- [ ] Nearing graduation
- [ ] Other:
### Date of last release:
N/A
We released fluss-shaded-1.0-incubating in August, but this is not
considered an official Fluss release, as it is a shaded utility module
rather than part of the core Fluss system. The community is working on the
official release of Fluss core (v0.8).
### When were the last committers or PPMC members elected?
2025-07-29
### Have your mentors been helpful and responsive?
Yes
### Is the PPMC managing the podling's brand / trademarks?
N/A
### Signed-off-by:
- [X] (fluss) Jean-Baptiste Onofré
Comments: Good "start" for the podling, growing the community already
happens. I'm looking for the first Apache release.
- [X] (fluss) Becket Qin
Comments:
- [X] (fluss) Yu Li
Comments: Good to see new committers joining and rich community
activities. Looking forward to the first apache release.
- [ ] (fluss) Jingsong Lee
Comments:
- [X] (fluss) Zili Chen
Comments:
### IPMC/Shepherd notes:
Fluss is a streaming storage built for real-time analytics which can serve as the real-time data layer for Lakehouse architectures. Fluss has been incubating since 2025-06-04. ### Three most important unfinished issues to address before graduating: 1. Ensure website and code are full compliance with ASF policie 2. Publish the first release under the ASF incubator 3. Grow the community and fill out the maturity model ### Are there any issues that the IPMC or ASF Board need to be aware of? No. ### How has the community developed since the last report? We are still in the setup phase, but we have seen some active contributors that deserved to be committer candidates. Jark Wu is going to Flink Forward Asia 2025 (Singapore) to present Fluss on July 3rd. ### How has the project developed since the last report? The community is developing for the next release v0.8 which is expected to be released at September. The community has established the Fluss Improvement Proposal (FIP) process [1] to facilitate design discussions for major features. Currently, there are already five FIPs in progress. [1] https://cwiki.apache.org/confluence/display/FLUSS/Fluss+Improvement+Proposal s ### How would you assess the podling's maturity? Please feel free to add your own commentary. - [X] Initial setup - [ ] Working towards first release - [ ] Community building - [ ] Nearing graduation - [ ] Other: We are still in the process of initial setup. We have migrated the GitHub repository and website to the Apache organization. We will set up the CI/CD pipelines to streamline future development and deployment. ### Date of last release: N/A ### When were the last committers or PPMC members elected? N/A ### Have your mentors been helpful and responsive? Yes ### Is the PPMC managing the podling's brand / trademarks? N/A ### Signed-off-by: - [X] (fluss) Jean-Baptiste Onofré Comments: Good work on the initial setup. Congrats ! - [ ] (fluss) Becket Qin Comments: - [X] (fluss) Yu Li Comments: Initial setup is completed and look forward to the further development of the project. - [X] (fluss) Jingsong Lee Comments: - [X] (fluss) Zili Chen Comments: ### IPMC/Shepherd notes: