From 4a06d925b5dff94f655f8053ef03ef103802a42e Mon Sep 17 00:00:00 2001
From: Isaac Milarsky <imilarsky@gmail.com>
Date: Fri, 24 Jan 2025 12:42:53 -0600
Subject: [PATCH 1/3] changes based on repolinter output

---
 CODEOWNERS.md  | 15 +++++++++++++++
 MAINTAINERS.md |  4 ++++
 2 files changed, 19 insertions(+)

diff --git a/CODEOWNERS.md b/CODEOWNERS.md
index 04f0761..f8c759b 100644
--- a/CODEOWNERS.md
+++ b/CODEOWNERS.md
@@ -31,3 +31,18 @@ Thank you [US Digital Response](https://www.usdigitalresponse.org/) Team for you
 # Questions?
 
 Email opensource@cms.hhs.gov
+ 
+ ## Repository Domains
+ <!--
+The Repo Domains section of your CODEOWNERS.md file helps manage code review responsibilities efficiently. Each domain represents a different aspect of the repository, such as documentation, frontend, backend, DevOps, testing, etc. In this section, list each domain and assign the appropriate GitHub usernames or teams responsible for that domain. This ensures that pull requests (PRs) are reviewed by the right experts, maintaining high code quality and relevance.
+For example:
+/docs/ @doc-team @johnsmith @janedoe
+/frontend/ @frontend-team @alice @bob
+/backend/ @backend-team @charlie @dana
+Furthermore, GitHub teams are a good feature for managing groups of contributors who need to be notified about specific domains within a repository. By creating and using GitHub teams, you can allow contributors to ping multiple relevant experts simultaneously.
+To set up GitHub teams:
+- Navigate to your organization's settings and select 'Teams'.
+- Create a new team for each domain, such as @frontend-team, @backend-team, or @doc-team.
+- Add the relevant members to each team. Ensure that the team includes all the individuals who should be notified about PRs in their domain.
+- When filling out the Repo Domains section in your CODEOWNERS.md file, use the team handles instead of or alongside individual usernames. This way, when a contributor opens a PR affecting a specific domain, they can simply tag the team, and every member of that team will be notified.
+--> 
diff --git a/MAINTAINERS.md b/MAINTAINERS.md
index 3744b42..044ce17 100644
--- a/MAINTAINERS.md
+++ b/MAINTAINERS.md
@@ -36,3 +36,7 @@ Total number of contributors: <!--CONTRIBUTOR COUNT START--> <!--CONTRIBUTOR COU
 
 <!-- readme: contributors -start -->
 <!-- readme: contributors -end -->
+ 
+ ## Maintainers List: 
+<!-- TODO: What groups/domains are maintainers a part of? Does your project have domains/areas that are maintained by specific people? List @USERNAMES directly, or any @ALIASES for groups/teams. -->
+ - 

From f0081abae6e157fc10c14dc159f0d506137fdb44 Mon Sep 17 00:00:00 2001
From: Natalia Luzuriaga <natalia.luzuriaga@cms.hhs.gov>
Date: Thu, 30 Jan 2025 08:12:40 -0800
Subject: [PATCH 2/3] Update MAINTAINERS.md

---
 MAINTAINERS.md | 19 +++++++++++++++----
 1 file changed, 15 insertions(+), 4 deletions(-)

diff --git a/MAINTAINERS.md b/MAINTAINERS.md
index 044ce17..7fb0e3b 100644
--- a/MAINTAINERS.md
+++ b/MAINTAINERS.md
@@ -10,6 +10,21 @@ This is a list of maintainers for this project. See [CODEOWNERS.md](./CODEOWNERS
 - [@sachin-panayil](https://github.com/sachin-panayil)
 - [@DinneK](https://github.com/DinneK)
 
+ ## Maintainers List: 
+<!-- TODO: What groups/domains are maintainers a part of? Does your project have domains/areas that are maintained by specific people? List @USERNAMES directly, or any @ALIASES for groups/teams. -->
+Repository Templates
+- [@natalialuzuriaga](https://github.com/natalialuzuriaga)
+- [@sachin-panayil](https://github.com/sachin-panayil)
+- [@IsaacMilarky](https://github.com/IsaacMilarky)
+
+Outbound Checklists
+- [@natalialuzuriaga](https://github.com/natalialuzuriaga)
+
+GitHub Actions
+- [@sachin-panayil](https://github.com/sachin-panayil)
+- [@IsaacMilarky](https://github.com/IsaacMilarky)
+- [@natalialuzuriaga](https://github.com/natalialuzuriaga)
+
 ## Approvers:
 
 - [@decause-gov](https://github.com/decause-gov)
@@ -36,7 +51,3 @@ Total number of contributors: <!--CONTRIBUTOR COUNT START--> <!--CONTRIBUTOR COU
 
 <!-- readme: contributors -start -->
 <!-- readme: contributors -end -->
- 
- ## Maintainers List: 
-<!-- TODO: What groups/domains are maintainers a part of? Does your project have domains/areas that are maintained by specific people? List @USERNAMES directly, or any @ALIASES for groups/teams. -->
- - 

From 6ef3afb4ea2c91c5d99a2f3c7a7cd89e1a97e2e6 Mon Sep 17 00:00:00 2001
From: Natalia Luzuriaga <natalia.luzuriaga@cms.hhs.gov>
Date: Thu, 30 Jan 2025 08:13:20 -0800
Subject: [PATCH 3/3] Update CODEOWNERS.md

---
 CODEOWNERS.md | 15 ---------------
 1 file changed, 15 deletions(-)

diff --git a/CODEOWNERS.md b/CODEOWNERS.md
index f8c759b..04f0761 100644
--- a/CODEOWNERS.md
+++ b/CODEOWNERS.md
@@ -31,18 +31,3 @@ Thank you [US Digital Response](https://www.usdigitalresponse.org/) Team for you
 # Questions?
 
 Email opensource@cms.hhs.gov
- 
- ## Repository Domains
- <!--
-The Repo Domains section of your CODEOWNERS.md file helps manage code review responsibilities efficiently. Each domain represents a different aspect of the repository, such as documentation, frontend, backend, DevOps, testing, etc. In this section, list each domain and assign the appropriate GitHub usernames or teams responsible for that domain. This ensures that pull requests (PRs) are reviewed by the right experts, maintaining high code quality and relevance.
-For example:
-/docs/ @doc-team @johnsmith @janedoe
-/frontend/ @frontend-team @alice @bob
-/backend/ @backend-team @charlie @dana
-Furthermore, GitHub teams are a good feature for managing groups of contributors who need to be notified about specific domains within a repository. By creating and using GitHub teams, you can allow contributors to ping multiple relevant experts simultaneously.
-To set up GitHub teams:
-- Navigate to your organization's settings and select 'Teams'.
-- Create a new team for each domain, such as @frontend-team, @backend-team, or @doc-team.
-- Add the relevant members to each team. Ensure that the team includes all the individuals who should be notified about PRs in their domain.
-- When filling out the Repo Domains section in your CODEOWNERS.md file, use the team handles instead of or alongside individual usernames. This way, when a contributor opens a PR affecting a specific domain, they can simply tag the team, and every member of that team will be notified.
--->