changes based on repolinter output

CODEOWNERS.md

@@ -1,33 +1,17 @@
-# Code Owners
-
-[@decause-gov](https://github.com/decause-gov)
-[@natalialuzuriaga](https://github.com/natalialuzuriaga)
-[@IsaacMilarky](https://github.com/IsaacMilarky)
-[@sachin-panayil](https://github.com/sachin-panayil)
-[@DinneK](https://github.com/DinneK)
-
-## Repository Domains
-
-- Repository Templates in `/tier*/` [@natalialuzuriaga](https://github.com/natalialuzuriaga) [@sachin-panayil](https://github.com/sachin-panayil) [@IsaacMilarky](https://github.com/IsaacMilarky)
-- Outbound Checklists in `/tier*/checklist.md` [@natalialuzuriaga](https://github.com/natalialuzuriaga)
-- GitHub Actions in `/.github` [@sachin-panayil](https://github.com/sachin-panayil) [@IsaacMilarky](https://github.com/IsaacMilarky) [@natalialuzuriaga](https://github.com/natalialuzuriaga)
-
-## Shoutouts
-
-[@usdigitalresponse](https://github.com/usdigitalresponse)
-
-- [@aprilselby88](https://github.com/aprilselby88)
-- [@vantuyls](https://github.com/vantuyls)
-- [@sgarciahelguera](https://github.com/sgarciahelguera)
-
-Thank you [US Digital Response](https://www.usdigitalresponse.org/) Team for your support creating this repository!
-
-[Coding It Forward Fellows](https://codingitforward.com/fellowship)
-
-- [@Firebird1029](https://github.com/Firebird1029)
-- [@CreativeNick](https://github.com/CreativeNick)
-- [@RicardoZamora01](https://github.com/RicardoZamora01)
-
-# Questions?
-
-Email [email protected]
+#Code Owners 
+<!-- TODO: Who are the points of contact in your project who are responsible/accountable for the project? This can often be an engineering or design manager or leader, who may or may not be the primary maintainers of the project. List them by GitHub Username--> 
+
+ ## 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.
+--> 

CODE_OF_CONDUCT.md

@@ -1,17 +1,10 @@
-## Contributor Code of Conduct
-
-As contributors and maintainers of this project, we pledge to respect all people who contribute through reporting issues, posting feature requests, updating documentation, submitting pull requests or patches, and other activities.
-
-We are committed to making participation in this project a harassment-free experience for everyone, regardless of the level of experience, gender, gender identity, expression, sexual orientation, disability, personal appearance, body size, race, ethnicity, age, or religion.
-
-Examples of unacceptable behavior by participants include the use of sexual language or imagery, derogatory comments or personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct.
-
-Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned with this Code of Conduct.
-
-Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by opening an issue or contacting one or more of the project maintainers at [email protected].
-
-This Code of Conduct is adapted from the [Contributor Covenant](http://contributor-covenant.org), version 1.0.0, available at [http://contributor-covenant.org/version/1/0/0/](http://contributor-covenant.org/version/1/0/0/)
-
-## Acknowledgements
-
-This CODE_OF_CONDUCT.md was originally forked from the [United States Digital Service](https://usds.gov) [Justice40](https://thejustice40.com) open source [repository](https://github.com/usds/justice40-tool), and we would like to acknowledge and thank the community for their contributions.
+## Contributor Code of Conduct 
+As contributors and maintainers of this project, we pledge to respect all people who contribute through reporting issues, posting feature requests, updating documentation, submitting pull requests or patches, and other activities. 
+ We are committed to making participation in this project a harassment-free experience for everyone, regardless of the level of experience, gender, gender identity, expression, sexual orientation, disability, personal appearance, body size, race, ethnicity, age, or religion. 
+ Examples of unacceptable behavior by participants include the use of sexual language or imagery, derogatory comments or personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. 
+ Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned with this Code of Conduct. 
+ Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by opening an issue or contacting one or more of the project maintainers at [email protected]. 
+ This Code of Conduct is adapted from the [Contributor Covenant](http://contributor-covenant.org), version 1.0.0, available at [http://contributor-covenant.org/version/1/0/0/](http://contributor-covenant.org/version/1/0/0/) 
+
+ ## Acknowledgements 
+This CODE_OF_CONDUCT.md was originally forked from the [United States Digital Service](https://usds.gov) [Justice40](https://thejustice40.com) open source [repository](https://github.com/usds/justice40-tool), and we would like to acknowledge and thank the community for their contributions. 

COMMUNITY_GUIDELINES.md

@@ -1,37 +1,29 @@
-# repo-scaffolder Open Source Community Guidelines
-
-This document contains principles and guidelines for participating in the repo-scaffolder open source community.
-
-## Principles
-
+# {name_of_project_here} Open Source Community Guidelines 
+This document contains principles and guidelines for participating in the {name_of_project_here} open source community. 
+
+ ## Principles 
 These principles guide our data, product, and process decisions, architecture, and approach.
-
 - Open means transparent and participatory.
 - We take a modular and modern approach to software development.
 - We build open-source software and open-source process.
 - We value ease of implementation.
 - Fostering community includes building capacity and making our software and processes accessible to participants with diverse backgrounds and skillsets.
 - Data (and data science) is as important as software and process. We build open data sets where possible.
-- We strive for transparency for algorithms and places we might be introducing bias.
-
-## Community Guidelines
-
+- We strive for transparency for algorithms and places we might be introducing bias. 
+
+ ## Community Guidelines 
 All community members are expected to adhere to our [Code of Conduct](CODE_OF_CONDUCT.md).
-
 Information on contributing to this repository is available in our [Contributing file](CONTRIBUTING.md).
-
-When participating in the repo-scaffolder open source community conversations and spaces, we ask individuals to follow the following guidelines:
-
+When participating in {{ cookiecutter.project_name }} open source community conversations and spaces, we ask individuals to follow the following guidelines:
 - When joining a conversation for the first time, please introduce yourself by providing a brief intro that includes:
-  - your related organization (if applicable)
-  - your pronouns
-  - your superpower, and how you hope to use it for {{ cookiecutter.project_name }}
+ - your related organization (if applicable)
+ - your pronouns
+ - your superpower, and how you hope to use it for {{ cookiecutter.project_name }}
 - Embrace a culture of learning, and educate each other. We are all entering this conversation from different starting points and with different backgrounds. There are no dumb questions.
 - Take space and give space. We strive to create an equitable environment in which all are welcome and able to participate. We hope individuals feel comfortable voicing their opinions and providing contributions and will do our best to recognize and make space for individuals who may be struggling to find space here. Likewise, we expect individuals to recognize when they are taking up significant space and take a step back to allow room for others.
 <!-- TODO: Add if your repo has a community chat - Be present when joining synchronous conversations such as our community chat. Why be here if you're not going to *be here*? -->
 - Be respectful.
 - Default to positive. Assume others' contributions are legitimate and valuable and that they are made with good intention.
-
-## Acknowledgements
-
+
+ ## Acknowledgements 
 This COMMUNITY_GUIDELINES.md was originally forked from the [United States Digital Service](https://usds.gov) [Justice40](https://thejustice40.com) open source [repository](https://github.com/usds/justice40-tool), and we would like to acknowledge and thank the community for their contributions.