Resolve "Add documentation to BB for the tracks"

docs/FAQ.md

@@ -103,3 +103,9 @@ on the [Big Bang Universe.](https://universe.bigbang.dso.mil/)
 
 It would also be useful to review
 [Understanding Big Bang.](https://docs-bigbang.dso.mil/latest/docs/understanding-bigbang/?h=understanding+bigbang%2F)
+
+## New Packages
+
+> How do I get a new package integrated into Big Bang?
+
+To integrate a new package into Big Bang, follow the steps outlined in the [package integration documents](developer/package-integration/README.md) and the [developing a package document](developer/develop-package.md).

docs/developer/develop-package.md

@@ -214,3 +214,5 @@ In some instances you may wish to manually create a private-registry secret in t
     ```shell
     -f reg-creds.yaml
     ```
+
+21. Integrate the package using the [Package Integration Documents](package-integration/README.md).

docs/developer/package-integration/README.md

@@ -2,6 +2,7 @@
 
 The following documents should be followed, in order, to fully integrate a new package into Big Bang:
 
+1. [Get BBTOC Approval](https://repo1.dso.mil/big-bang/product/bbtoc/-/blob/main/process/Package%20Maintenance%20Tracks.md): Follow the BBTOC Package Maintenance Tracks process to get approval for package integration
 1. [Upstream Helm Chart](upstream.md): Initialize package workspace using an upstream Helm chart
 1. [CICD Pipeline](pipeline.md): Establish a baseline package pipeline for testing changes
 1. [Flux Helm Chart](flux.md): Create Flux compatible GitOps Helm chart required by Big Bang
@@ -13,6 +14,7 @@ The following documents should be followed, in order, to fully integrate a new p
 1. [Additional Tests](testing.md): Add testing to validate basic functionality
 1. [Network Policies](network-policies.md): Add ingress/egress policies to restrict network traffic for security
 1. [Policy Enforcement](policy-enforcement.md): Update package to comply with default security and governance policies in Big Bang
-2. [Supported Package](supported.md): Migrate package into the Big Bang repo as a supported package
-3. [Final Documentation](documentation.md): Add additional Big Bang documentation for final release
-4. [Big Bang Merge Request](bigbang-merge-request.md): Create Big Bang Merge Request and run all packages pipeline
+1. [Istio Hardening](../IstioHardened.md): Update package to comply with Istio hardening policies in Big Bang
+1. [Supported Package](supported.md): Migrate package into the Big Bang repo as a supported package
+1. [Final Documentation](documentation.md): Add additional Big Bang documentation for final release
+1. [Big Bang Merge Request](bigbang-merge-request.md): Create Big Bang Merge Request and run all packages pipeline

docs/understanding-bigbang/package-architecture/README.md

@@ -6,7 +6,7 @@ Big Bang includes many different packages that provide services to the ecosystem
 
 ## Technical Oversight Committee (TOC)
 
-The Big Bang TOC supports users and contributors of the Big Bang ecosystem.  If you would like to add, modify, or remove packages in Big Bang, we encourage you to attend the TOC to discuss your ideas.  You can find details in [the BBTOC repository](https://repo1.dso.mil/big-bang/product/bbtoc).
+The Big Bang TOC supports users and contributors of the Big Bang ecosystem.  If you would like to add, modify, or remove packages in Big Bang, we encourage you to attend the TOC to discuss your ideas.  You can find details in [the BBTOC repository](https://repo1.dso.mil/big-bang/product/bbtoc), specifically in the [Package Maintenance Tracks](https://repo1.dso.mil/big-bang/product/bbtoc/-/blob/main/process/Package%20Maintenance%20Tracks.md) document.
 
 ## Dependency Tree