Hi all, Thank you for the votes and discussion. I’m closing this vote now. I’ll post the result in a separate thread.
-- Anton сб, 9 мая 2026 г. в 04:15, Yang Wang <[email protected]>: > > +1(no-binding) > > Best regards, > Yang > > Anton Borisov <[email protected]> 于2026年5月6日周三 17:57写道： > > > Hi all, > > > > I would like to start a vote on FIP-40: Merge apache/fluss-rust into > > apache/fluss. > > > > Discussion thread: > > https://lists.apache.org/thread/wz6ghy28kgww3pvgs7s1hfz2y2bn9vvr > > > > Proposal: > > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=421957144 > > > > The proposal is to consolidate the current apache/fluss-rust > > repository into apache/fluss under a new fluss-rust/ directory. > > > > At a high level, this includes: > > > > - migrating the current apache/fluss-rust tree into > > apache/fluss/fluss-rust/ > > - preserving git history > > - unifying CI under apache/fluss with path filters for Java, Rust, > > bindings, and docs > > - consolidating client documentation under fluss.apache.org/docs/clients/ > > - retiring clients.fluss.apache.org with redirects > > - making fluss-rpc/src/main/proto/FlussApi.proto the single source of > > truth for Rust-generated protocol types > > - archiving apache/fluss-rust as read-only after migration > > - keeping published artifacts unchanged: Maven, crates.io, PyPI, and > > source/build-from-source targets > > > > The motivation is to reduce duplicated infrastructure, duplicated > > protobuf definitions, split documentation, manual server-version > > pinning, and cross-repository coordination overhead before Fluss > > reaches 1.0 GA. > > > > Please vote: > > > > [ ] +1 Approve the proposal > > [ ] 0 No opinion > > [ ] -1 Do not approve, because... > > > > The vote will remain open for at least 72 hours. > > > > -- Anton > >
