I totally agree. It would be great to have a single library where all of our assets are stored.
But until we start large-scale reconstruction work, I would like to ask a slightly off-topic question: Why do we even need a cloudberry-release-devops? Why can't all our scripts be stored in the main repository? It happens to be rather tedious to use two repos, especially when changing something big. Such as adding PAX support. For such a big change you need to commit something breaking the building to the main repo. And at that point, your tests will fail. Then you have to fix the cloudberry-release-devops (add additional packages), but the tests may still fail. And now you could fix the tests and make a final commit. And only now can one check if everything is OK. We could store all our scripts together with the code. Best regards, Leonid On Mon, Jun 9, 2025 at 9:05 AM Dianjin Wang <wangdian...@gmail.com> wrote: > Hi all, > > Over the past two years, the bootcamp repo has grown to include > various types of content, such as sandbox Dockerfiles, tutorials, and > learning materials. I’d like to start a discussion around reorganizing > the `apache/cloudberry-bootcamp` repo to improve clarity and > maintainability across our community resources. > > The primary motivation is to consolidate content by type and reduce > redundancy, which would: > * Make it easier for contributors to find and update documentation > * Reduce ongoing maintenance overhead > > ## Proposal (for discussion) > > I propose reorganizing this bootcamp repo as follows: > > * Move sandbox-related files to `apache/cloudberry-devops-release`, > where we maintain tools related to deployment and release automation > -- a new dir called `sandbox` will be created to store them. > * For the benchmark test files -- a new directory called `benchmark` > will be created under `apache/cloudberry-devops-release`, but we can > do this until these files are ready. > * Migrate tutorials, crash courses, and learning content to the > `apache/cloudberry-site` repo, which now serves as the single source > for end-user documentation. All of these materials have been copied to > our website repo [1]. > > Once the content has been fully migrated and verified, plan to: > > * Archive the cloudberry-bootcamp repository, with a notice in the > README indicating that it is no longer actively maintained and that > the relevant content has been moved. > > ## Request for Feedback > > This is just a proposal at this stage. I’d love to hear your thoughts > and suggestions. If most of the members agree, I would like to help > take action on this plan. > > Thanks, and looking forward to your feedback! > > [1] https://cloudberry.apache.org/bootcamp#cloudberry-sandbox > > Best, > Dianjin Wang > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@cloudberry.apache.org > For additional commands, e-mail: dev-h...@cloudberry.apache.org > >
