[Announcement] Migration to apache/paimon-cpp

[lxy-9602]

Search before asking

• I searched in the issues and found nothing similar.

Motivation

We are excited to announce that Apache Paimon C++ is migrating to its official Apache repository:

👉 https://github.com/apache/paimon-cpp

Solution

Migration Plan

• We plan to migrate starting from the release-0.2 milestone.
• During the transition, active development continues at https://github.com/alibaba/paimon-cpp. Once release-0.2 is stable and fully migrated, subsequent PRs will be moved to apache/paimon-cpp.

Large, Independent Features (e.g., Range Index, System Table)

For contributors working on larger self-contained features, we offer two options:

1. We migrate on your behalf — We will port your PR to the new repository.
2. You migrate it yourself — You can resubmit your PR directly to apache/paimon-cpp once all prerequisite dependencies are ready.

If you prefer option 2, we will @mention you at the appropriate time to proceed with the migration.

Please let us know your preference in the comments.

What's Next

Once migration is complete, all future contributions should target https://github.com/apache/paimon-cpp.

We will keep this issue updated with progress.

---

Thank you for your continued support! We look forward to seeing you on the new repository.

Anything else?

No response

Are you willing to submit a PR?

• I'm willing to submit a PR!

[mrdrivingduck]

If you prefer option 2, we will @mention you at the appropriate time to proceed with the migration.

@lxy-9602 Why not mirror the branch directly to new repo? So that all the commit history can be kept, and no more manual work.

[lxy-9602]

@mrdrivingduck That is a very good question.

The main reason is that the Paimon community expects the migration to happen through split PRs rather than a direct branch mirror. Reviewing and merging the code in smaller pieces helps encourage more community discussion, surface potential issues earlier, and gives the project a better chance to evolve collaboratively during the migration process.

Another important consideration is contribution attribution. The contribution history in the Alibaba repository does not map cleanly to the Apache repository in terms of ownership and committer recognition. Migrating the code through separate PRs helps establish a clearer contribution under Apache.