Hi Yu, Yes, they will be opening discussions for each FIP on the dev mailing list. However, FIP-1 and FIP-2 were already implemented in the v0.7 release. We’ve simply moved them from Google Docs into the official FIP format to make them more visible, as they contain important designs (will update the status of FIP-1 and FIP-2).
Best, Jark On Tue, 1 Jul 2025 at 16:44, Yu Li <[email protected]> wrote: > +1. > > Minor: I could see six FIP documents on confluence while only FIP-6 is > marked as "WIP". It seems the status of the github issue of the other five > are all open, so I guess they are all still in discussion and will follow > the FIP process announced here, right? > > Best Regards, > Yu > > > On Tue, 1 Jul 2025 at 09:59, Jark Wu <[email protected]> wrote: > > > Hi all, > > > > This is the first discussion thread for Fluss on the ASF mailing list. > I’d > > like to take this opportunity to introduce and discuss the *Fluss > > Improvement Proposal (FIP)* process. > > > > The FIP process is inspired by the Apache Flink community’s FLIP process, > > and we’ve named it "FIP" to clearly distinguish it from FLIP. Most of the > > content and guidelines are aligned with FLIP. > > > > Compared to our previous approach, the key change for the Fluss community > > is that all major improvement proposals must be submitted as an FIP on > the > > Fluss wiki instead of a Google doc, followed by a DISCUSS thread on the > dev > > mailing list. > > > > Looking forward to your feedback and participation! > > > > > > Best, > > Jark > > > > > > [1] > > > > > https://cwiki.apache.org/confluence/display/FLUSS/Fluss+Improvement+Proposals > > >
