+1
I support the proposal to create apache/tsfile-extras and to accept the existing DuckDB extension as its initial codebase, subject to completion of the ASF IP Clearance process. I believe a shared extras repository provides a practical home for integrations that target projects do not yet accept or require to be maintained externally, while still allowing us to follow the upstream-first principle whenever possible. I am willing to help freeze the exact revision of the DuckDB extension, review its provenance and licenses, and complete the donation and import work. Best regards, Colin Lee At 2026-08-17 10:43:00, "Yuan Tian" <[email protected]> wrote: >Hi all, > >Following the discussion in the “[DISCUSS] Integrate Apache TsFile with >DuckDB” thread, I would like to start a vote on the following proposal. > > 1. > > Create a new blank public repository named tsfile-extras for the Apache > TsFile project through ASF SelfServe: > > https://github.com/apache/tsfile-extras > > The repository will be under the responsibility of the Apache TsFile PMC. > 2. > > Position tsfile-extras as a companion repository to the main Apache > TsFile repository. It may contain integrations, extensions, examples, and > supporting tools that do not belong in the core TsFile repository. > > This follows a model similar to: > - > > https://github.com/apache/iotdb-extras > - > > https://github.com/apache/plc4x-extras > 3. > > Follow an upstream-first principle for integrations: > - > > When the target project is willing to accept and maintain an > integration, we should contribute it to that project whenever possible. > - > > When the target project does not yet accept the integration, or > requires its source code to be maintained externally, the Apache TsFile > community may maintain it in tsfile-extras. > - > > A shared repository will avoid creating and releasing a separate > Apache repository for every integration. > 4. > > Accept the existing DuckDB extension as the initial codebase of > tsfile-extras, subject to successful completion of the ASF IP Clearance > process: > > https://github.com/ColinLeeo/tsfile-duckdb > > The extension has already been accepted into DuckDB Community Extensions: > > https://github.com/duckdb/community-extensions/pull/2435 > > DuckDB Community Extensions currently requires the extension source to > be buildable from the repository root and cannot reference a subdirectory. > The initial repository layout should therefore preserve root-level > compatibility with the DuckDB Extension Template. The organization of > future components can be discussed separately as they are added. > 5. > > Before importing the existing code, we will: > - > > identify and freeze the exact revision to be donated; > - > > complete any required ICLA, Software Grant, and ASF IP Clearance > procedures; > - > > verify the provenance and license compatibility of the source code > and third-party dependencies; > - > > ensure that the LICENSE, NOTICE, and source headers comply with ASF > requirements; and > - > > configure .asf.yaml and repository notifications consistently with > the existing Apache TsFile repositories. > 6. > > After the import is complete, we will update the DuckDB Community > Extensions descriptor to reference the Apache-owned repository. > >The proposed repository name follows the ASF Infra convention of >$project-$reponame. > >Please vote: > >[ ] +1: Approve the proposal >[ ] 0: No opinion >[ ] -1: Do not approve (please provide the reason) > >This vote will remain open for at least 72 hours. At least three binding +1 >votes and no binding vetoes are required. Votes from Apache TsFile PMC >members are binding, while votes from all community members are welcome. > >Best regards, > >Yuan Tian
