Sub-epic to P1BIGROCKS-2753 To improve the user experience, we should segregate Value Stream tools, Product tools & packages, and automation for the environment at the first level BB group. - Infrastructure: IaC templates for various K8S distros / Cloud providers. (e.g. Openshift, EKS, Konvoy, RKE2 on AWS (split from customer template), Air Gap (Zarf config), Quickstart/dev). No actual configuration here, just templates/code. - Pipelines: Anything related to CICD. (e.g. gluon, pipeline templates) - Team: Items used internal by the value stream. (e.g. charter, epics scoring, repo master template, dogfood configuration, staging/production configuration) - Tools: Internal value stream tools. (e.g. renovate-runner, gitlab-triage, bb-bot, docs compiler, r2d2) - Product: Public facing Big Bang consumables. (e.g. bigbang, bbctl, customer template (w/o infrastructure), wrapper, landscape) - Training: special courses (e.g. istio labs, workshop, engineering cohort). Should repo1.dso.mil/platform-one/onboarding/Big-Bang be moved here? - Packages: flat repo of all core/addons/community/third-party. Badges will be used to identify maturity, support group, etc. Repos should only be created here if they are planned for a TOC maturity discussion. - Plugins: homegrown plugins (e.g. keycloak, kustomize-helmgenerator) > Packages are applications that have been (or plan to be) integrated with Big Bang, are deployable, and provide a service after running. Plugins are optional, tightly-coupled modules that extend package capabilities. They are dependent on the deployment of a package to work properly. > Short-lived or experimental projects needed for development will only be available in personal areas (e.g. https://repo1.dso.mil/myusername/). We wish to encourage proof-of-concept and momentum before formally create a repo under Big Bang. For CI security, we should consider how CI env variables will be consumed and ensure the repo structure is optimized to support. This depends our design of how CI secrets will be passed in.