From e6db2e6782dec57accad4581a479f17ba2e10c73 Mon Sep 17 00:00:00 2001
From: Isaac Milarsky <imilarsky@gmail.com>
Date: Tue, 11 Feb 2025 11:40:44 -0600
Subject: [PATCH] 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 f54cde1..f3c99ff 100644
--- a/CODEOWNERS.md
+++ b/CODEOWNERS.md
@@ -30,3 +30,18 @@ To set up GitHub teams:
 
 /css, /js [@natalialuzuriaga](https://github.com/natalialuzuriaga)
 /schemas [@natalialuzuriaga](https://github.com/natalialuzuriaga) [@decause-gov](https://github.com/decause-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 1c53d19..f180dd9 100644
--- a/MAINTAINERS.md
+++ b/MAINTAINERS.md
@@ -290,3 +290,7 @@ In rare cases, a hotfix for a prior release may be required out-of-phase with th
    ```
 
 [proj-releases-new]: https://github.com/DSACMS/codejson-generator/releases/new
+ 
+ ## 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. -->
+ -