diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 4f1bde1f4..141d8d168 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -166,10 +166,8 @@ behavior, do your best to explain to the user why this is the case.
 - If it seems to be a genuine bug, you can /triage accept the issue. In addition, investigate if there are workarounds or
 alternative solutions for the user that they can try until the issue gets resolved.
 
-Administrative notes:
-
-- The [OWNERS file spec] is a useful resources in making changes.
-- Maintainers and admins must be added to the appropriate lists in both [Kustomize OWNERS_ALIASES] and [SIG-CLI Teams]. If this isn't done, the individual in question will lack either PR approval rights (Kustomize list) or the appropriate Github repository permissions (community list).
+The triage party for kustomize is here https://cli.triage.k8s.io/s/kustomize and can be a easy way to
+find issues that have not been triaged yet.
 
 ## Project/Product Managers
 
@@ -194,6 +192,11 @@ You will also be asked to help with roadmap planning, deprecation communication,
 and doing research on kustomize usage when appropriate, though these responsibilities will occur less
 frequently.
 
+## Administrative notes:
+
+- The [OWNERS file spec] is a useful resources in making changes.
+- Maintainers and admins must be added to the appropriate lists in both [Kustomize OWNERS_ALIASES] and [SIG-CLI Teams]. If this isn't done, the individual in question will lack either PR approval rights (Kustomize list) or the appropriate Github repository permissions (community list).
+
 ## Contact Information
 
 - [Slack channel]
diff --git a/ROADMAP.md b/ROADMAP.md
index 461019633..ba6f872e5 100644
--- a/ROADMAP.md
+++ b/ROADMAP.md
@@ -11,6 +11,13 @@ the project board for that area and assign yourself to one of the issues. It is
 recommended to start with smaller issues to ramp up on the project before starting
 to tackle larger issues.
 
+Project boards:
+https://github.com/orgs/kubernetes-sigs/projects/50
+https://github.com/orgs/kubernetes-sigs/projects/51
+https://github.com/orgs/kubernetes-sigs/projects/52
+https://github.com/orgs/kubernetes-sigs/projects/53
+https://github.com/orgs/kubernetes-sigs/projects/54
+
 ## Kustomize contributors (at time of writing):
 
 kustomize owner: @natasha41575
@@ -30,11 +37,11 @@ Priority: High
 
 Effort: Medium
 
-In the past, when the leads have left in various kubernetes projects, it
-left a wide hole that few could easily fill, leaving the remaining leads in a
-bad position and the project understaffed. We should assume that we will need
-to onboard new maintainers in the future, and should have playbooks for doing so.
-As we grow the contributor base in kustomize, we will build these playbooks for
+In the past, when the leads stopped contributing (for various reasons, not covered here)
+in various kubernetes projects, it left a wide hole that few could easily fill,
+leaving the remaining leads in a bad position and the project understaffed. We should assume
+that we will need to onboard new maintainers in the future, and should have playbooks
+for doing so. As we grow the contributor base in kustomize, we will build these playbooks for
 those who are contributing and those who are looking to grow into kustomize leaders.
 To ensure the long term health and stability of the project, we should have:
 
@@ -58,7 +65,12 @@ healthy and making progress.
 The primary means in which we will try to find new kustomize contributors is through the new kustomize
 maintainer training cohort. We will lead a group of ~20 kubernetes community members through a 3-6 month
 training program, involving talk sessions, bug scrubs, issue triage, PR reviews, and coding projects for
-each member. The effort from existing kustomize maintainers here will be to:
+each member.
+
+See [our call for help](https://groups.google.com/a/kubernetes.io/g/dev/c/M5OphEVsv5o/m/zc6G4H15AAAJ) for more
+specific details about the program.
+
+The effort from existing kustomize maintainers here will be to:
 - Organize the cohort, so that each cohort member feels productive and understands what they should work on
 - Align motivation of the cohort members with the work that we assign to them.
 - Review PRs from cohort members in a timely manner.