update

aws/proposals/github-concerns/README.md

@@ -117,14 +117,17 @@ The backup process will be implemented using the following approach:
 As part of our resilience strategy, we need to validate GitLab as a potential temporary alternative during GitHub outages. The following items require setup and validation:
 
 1. General
-   1. Term changes
-   1. What migrates, what does not
+   1. Terminology changes from GitHub to GitLab
+   1. What features and capabilities migrate and which do not
 
 1. Infrastructure Configuration:
    1. Mirror the GitHub naming convention (replacing "github" with "gitlab" in URLs)
-   1. Deploy across the same locations (internal, t26, dmz)
-   1. Configure on F5 similar to GitHub Enterprise (even as a single instance)
-   1. Validate network access from internal networks, cloud, lab, and mobile devices
+   1. Deploy across the same locations (internal, t26, dmz) **DONE**
+      * github.it -> gitlab.it
+      * github.e.it -> gitlab.e.it
+      * github.t26.it -> gitlab.s.it
+   1. Configure on F5 similar to GitHub Enterprise (even as a single instance) **DONE**
+   1. Validate network access from internal networks, cloud, lab, and mobile devices **DONE**
 
 1. Authentication & Access:
    1. LDAP integration:
@@ -140,6 +143,7 @@ As part of our resilience strategy, we need to validate GitLab as a potential te
       1. Critical for our AWS account baseline management (~300 AWS account repos)
    1. Verification that CODEOWNERS files work as expected
    1. Markdown rendering compatibility check (important for our extensive documentation)
+   1. Organization level configuration
 
 1. Developer Workflow:
    1. CLI tools for repository operations