Hi all, I’d like to open a discussion regarding the repositories related to our backup tooling.
## Background We have been cherry-picking commits from Greenplum’s archived gpbackup into our current repository `apache/cloudberry-gpbackup`. The work has been carried out in the branch `sync-with-upstream` and is mostly complete. For details, please see: https://github.com/apache/cloudberry-gpbackup/issues/46 ## Topics for discussion 1. Repository renaming The current repository name is `apache/cloudberry-gpbackup`. Since the prefix `gp` may imply a dependency on Greenplum rather than Cloudberry itself, I propose renaming it to `apache/cloudberry-backup`, which would better reflect the independence of our project. 2. Repository consolidation There is also a small repository `apache/cloudberry-gpbackup-s3-plugin`. This repo has seen very few changes, and its core consists of fewer than 10 files. To reduce our maintenance and governance overhead, I propose merging it into the existing `apache/cloudberry-backup/plugins/` directory. * This would simplify our repo structure, improve maintainability, and make it easier to build an integrated backup ecosystem. * Some code adjustments may be needed to align the plugin more closely with the main backup tool. * Since the original `apache/gpbackup-s3-plugin` repo has no important Cloudberry-specific changes, we can also request the ASF Infra team to directly remove it after the consolidation. ## Next steps Before moving forward, I’d like to hear your thoughts and feedback regarding: * The proposed renaming of `apache/cloudberry-gpbackup` ~> `apache/cloudberry-backup` * The consolidation of `apache/cloudberry-gpbackup-s3-plugin` into the main backup repo, and deletion of the original `apache/gpbackup-s3-plugin` Looking forward to your input. Best, Dianjin Wang --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@cloudberry.apache.org For additional commands, e-mail: dev-h...@cloudberry.apache.org
