+1 (binding)

Best,
Giannis

On Thu, 13 Aug 2026 at 12:50 PM, Yang Wang <[email protected]>
wrote:

> Hi everyone,
>
> A quick process correction: I omitted [email protected] from the
> recipient list of the original vote email. I have now added it to this
> thread for PMC notification and record.
>
> The proposal and voting options remain unchanged. To ensure that all PMC
> members have sufficient time to participate, the vote will remain open for
> at least 72 hours from this email.
>
> Sorry for the oversight.
>
> Thanks,
> Yang
>
>
> Junbo Wang <[email protected]> 于2026年8月13日周四 16:20写道:
>
> > Hi Yang,
> >
> > +1 (non-binding)
> >
> > The scope, governance boundaries, and disclaimers look clear to me.
> > Thanks for driving this.
> >
> > Best regards,
> > Junbo Wang
> >
> > > On 13 Aug 2026, at 15:58, Yang Wang <[email protected]> wrote:
> > >
> > > Hi everyone,
> > >
> > > Following the discussion at:
> > >
> > > https://lists.apache.org/thread/dq04hq5gsnjnsm2mcmr6spsbyoyl4bb0
> > >
> > > I would like to call a vote to authorize the use of the "Fluss" name
> > > for a third-party GitHub organization named "fluss-extensions":
> > >
> > > https://github.com/fluss-extensions
> > >
> > > Purpose
> > > =======
> > >
> > > The organization will provide a neutral home for independently
> > > maintained ecosystem projects related to Apache Fluss, including:
> > >
> > > - Native components that follow release cycles different from Apache
> > Fluss,
> > >  such as a dedicated RocksDB JNI distribution;
> > > - Non-JVM integrations, such as a DuckDB extension for Fluss;
> > > - Connectors, CDC bridges, benchmark suites, and language bindings;
> > > - Other Fluss-related projects that are not ready or suitable for
> > donation
> > >  to the ASF.
> > >
> > > Status and relationship with Apache Fluss
> > > =========================================
> > >
> > > The following boundaries will apply:
> > >
> > > - fluss-extensions is an independently operated, third-party GitHub
> > >  organization.
> > > - It is not owned, operated, or governed by the Apache Software
> > Foundation
> > >  or the Apache Fluss PMC.
> > > - Repositories hosted there are not official Apache Fluss repositories.
> > > - Code and artifacts published there are not Apache Software Foundation
> > >  releases.
> > > - Hosting a repository does not constitute endorsement by the ASF or
> the
> > >  Apache Fluss PMC.
> > > - Each repository owner is responsible for the project's development,
> > >  releases, licensing, security, and maintenance.
> > > - The official Apache Fluss project remains hosted at:
> > >
> > >  https://fluss.apache.org/
> > >  https://github.com/apache/fluss
> > >
> > > Governance
> > > ==========
> > >
> > > The organization will follow the governance model described in the
> > > discussion thread, inspired by the flink-extended organization:
> > >
> > > - A small group of individual volunteers will administer the
> > organization.
> > > - Although some volunteers may also be Apache Fluss committers or PMC
> > >  members, they will operate the organization in their individual
> > capacity,
> > >  not on behalf of the ASF or the Fluss PMC.
> > > - When a project is accepted, its owner will receive the necessary
> > >  permissions and remain responsible for its day-to-day operation.
> > > - Every hosted repository must display a prominent disclaimer
> describing
> > >  its independent, third-party status.
> > > - Hosted projects will be strongly encouraged to use the Apache License
> > 2.0.
> > > - The organization administrators will maintain public governance and
> > >  repository admission and removal policies.
> > > - If the organization no longer follows these conditions, the Apache
> > Fluss
> > >  PMC may withdraw its permission to use the Fluss name.
> > >
> > > Branding
> > > ========
> > >
> > > ASF Brand Management has confirmed that the proposed organization name
> > > and trademark usage are acceptable.
> > >
> > > This vote authorizes the use of the "Fluss" name subject to the scope,
> > > governance, and disclaimers described above. It does not approve or
> > > endorse any individual repository, artifact, release, product, or
> service
> > > hosted by the organization.
> > >
> > > Please vote:
> > >
> > > [ ] +1 Approve the use of the Fluss name for the fluss-extensions
> > >        GitHub organization under the conditions above
> > > [ ]  0 No opinion
> > > [ ] -1 Do not approve (please explain)
> > >
> > > Only votes from Apache Fluss PMC members are binding, but all community
> > > members are welcome to vote.
> > >
> > > This vote will remain open for at least 72 hours.
> > >
> > > Thanks,
> > > Yang
> >
> >
>

Reply via email to