update addressed issues

Author: joshgav

projects/k8gb/governance-review/2026-01-21.md

@@ -21,9 +21,8 @@ This review is based on the template at
 **The following issues have been identified that need to be resolved before
 [project milestone or other requirement]:**
 
-- The process for choosing the project lead should be described.
-- Who the project lead is should be indicated somewhere.
-- In the future, a GitHub issue should be created for election of each new maintainer.
+- The project must rename the API group for its CRDs from `k8gb.absa.oss`. This
+  work is tracked in <https://github.com/k8gb-io/k8gb/issues/2180>.
 
 ### Points of Excellence
 
@@ -39,6 +38,7 @@ examples for other projects to copy:**
 **Over the next year, the project should work on the following issues to improve
 its governance, these are considered non-blocking:**
 
+- In the future, a GitHub issue should be created for election of each new maintainer.
 - If there are people who make significant code contributions but not at the
   level of maintainers, consider an official "Contributor" role and listing to
   recognize and reward their contribution.
@@ -131,8 +131,8 @@ offboarding, and emeritus status).**
 **Incubating:** Suggested | **Graduated:** Required
 
 Maintainers are added to CODEOWNERS following a period of contributions to the
-project. They are removed voluntarily or per a supermajority vote of
-maintainers.
+project, nomination and election in a GitHub issue. They are removed voluntarily
+or per a supermajority vote of maintainers.
 
 **Demonstrate usage of the maintainer lifecycle with outcomes, either through
 the addition or replacement of maintainers as project events have required.**