Hi Yu, Justin, all, I would like to provide an update on the follow-up actions we took based on the feedback in this thread.
First of all, thank you again for the careful and constructive feedback on the proposed PMC roster. The Fluss PPMC took this feedback seriously and restarted a fresh discussion [1] on the private mailing list to review the proposed PMC roster more deliberately. In this new discussion, we aligned around the Apache Incubator guidance [2] for selecting the initial PMC at graduation, reviewed candidates against governance and contribution criteria, considered active committers who have demonstrated readiness for PMC responsibility. We also prepared a summary [3] of each proposed member’s contributions from the discussion thread, including their contributions, willingness, and forward-looking responsibilities. After the discussion and a formal PPMC vote [4][5], the Fluss PPMC has approved the following updated proposed PMC roster for graduation: ============ The proposed PMC consists of 16 members: >From existing PPMC members (9): 1. Jark Wu (Alibaba Cloud) - PMC Chair 2. Nicholas Jiang (Ant Group) 3. Mehul Batra (DigitalOcean) 4. Yunhong Zheng (Alibaba Cloud) 5. Yuxia Luo (Alibaba Cloud) 6. Giannis Polyzos (Ververica) 7. Michael Koepf (Dynatrace) 8. Feng Wang (Alibaba Cloud) 9. Benchao Li (ByteDance) >From existing committers (2): 10. Anton Borisov (Fresha) 11. Keith Lee (Confluent) >From mentors, who will continue on the PMC after graduation (5): 12. Yu Li (Alibaba Cloud) 13. Becket Qin (LinkedIn) 14. Jean-Baptiste Onofré (Dremio) 15. Jingsong Lee (Alibaba Cloud) 16. Zili Chen (ScopeDB) ============ All members in the proposed roster have confirmed their willingness to take on active governance responsibilities after graduation. We have also informed the dev mailing list of the updated roster for transparency [6]. Regarding the other issues raised earlier in this thread, the Fluss community has addressed them as well: - The download page has been updated to use ASF mirror links via closer.lua, include a KEYS link, checksum/signature links, and visible verification instructions [7]. - GitHub release notes and release artifacts have been reviewed and updated with the required incubating disclaimer where applicable [8]. - Docker Hub descriptions have been updated, including the deprecated pre-Apache fluss/fluss repository and the official apache/fluss repository [9][10]. - Maven POM descriptions have been updated to include the incubation disclaimer [11]. - Branding issues in documentation, blogs, and related external pages have been reviewed and corrected, including the previously mentioned Ververica documentation page (removed), Alibaba Cloud blog content, and product page related Apache Fluss branding [12]~[19]. - We will continue monitoring third-party references and correcting branding issues when we find them. With these updates, we believe the proposed PMC roster better reflects the current stewardship, governance readiness, vendor diversity, and forward-looking commitment of the Fluss community, while also addressing the compliance and branding concerns raised during the discussion. We would sincerely appreciate further feedback from the IPMC on the updated roster and the current graduation readiness of Apache Fluss. Best regards, Jark Wu (on behalf of the Apache Fluss PPMC) [1] https://lists.apache.org/thread/gkh1to6ftcf6ptgq94m1v6f58htr76mz [2] https://cwiki.apache.org/confluence/display/INCUBATOR/Selecting+the+Initial+PMC+at+Graduation [3] https://lists.apache.org/thread/bf1c30xxhw1t7db4x00ww2ltdb6lgqlh [4] https://lists.apache.org/thread/nzd17ffjdbof4n5q913dyv8r7lr3od7x [5] https://lists.apache.org/thread/9089hm0k15rv3gkklmkxyrc8680w3z92 [6] https://lists.apache.org/thread/656x5bqync05l3o7rsjj58fd84l7smj4 [7] https://fluss.apache.org/downloads/#verifying-downloads [8] https://github.com/apache/fluss/releases [9] https://hub.docker.com/r/fluss/fluss [10] https://hub.docker.com/r/apache/fluss [11] https://github.com/apache/fluss/blob/e176dbb69f1094ad97c18ee2c2574c454c4686a2/pom.xml#L40-L47 [12] https://docs.ververica.com/introduction/about-ecosystem/fluss/ [13] https://www.alibabacloud.com/blog/602412 [14] https://www.alibabacloud.com/blog/apache-fluss-vs--apache-paimon-two-engines-for-the-real-time-lakehouse_602687 [15] https://www.alibabacloud.com/blog/why-fluss-top-4-challenges-of-using-kafka-for-real-time-analytics_601879 [16] https://www.alibabacloud.com/blog/understanding-fluss-partial-update_602282 [17] https://www.alibabacloud.com/blog/introducing-fluss-streaming-storage-for-real-time-analytics_601921 [18] https://www.alibabacloud.com/blog/apache-flussincubating-vs--apache-paimon-two-engines-for-the-real-time-lakehouse_602687 [19] https://www.alibabacloud.com/blog/fluss-redefining-streaming-storage-for-real-time-data-analytics-and-ai_602412 On Mon, 1 Jun 2026 at 13:11, Jark Wu <[email protected]> wrote: > > Hi Yu, Justin, and all, > > Thank you both for the careful and constructive feedback, and to Yu > for laying out a clear path forward. > > As a PPMC member, I fully agree with the recommendation and we accept > the action items. I will start a fresh discussion on the private list > to determine an updated PMC roster. Through the new discussion, > > (1) we will consider adding new active committers to the PMC who has > earned PMC membership through their work during this period. > > (2) we will review each proposed PMC member's contributions during > incubation to ensure the roster reflects current stewardship and > forward-looking commitment. > > Once we finalize the updated roster, we will report the revised > resolution back to this thread and also notify the dev list for > transparency. > > Best, > Jark Wu > > On Mon, 1 Jun 2026 at 09:00, Justin Mclean <[email protected]> wrote: > > > > HI, > > > > I’ve put together a guide that may help: > > https://cwiki.apache.org/confluence/display/INCUBATOR/Selecting+the+Initial+PMC+at+Graduation > > > > Kind Regards, > > Justin --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
