Repolinter Results

COMMUNITY.md

@@ -0,0 +1,36 @@
+## Project Members 
+<!-- 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. 
+ Roles to include, but not limited to: Project Owner, Technical Lead, Developers/Contributors, Community Manager, Security Team, Policy Advisor, Contracting Officer's Representative, Compliance Officer, Procurement Officer --> 
+
+{{ cookiecutter.project_repo_name }} is supported by a dedicated team of individuals fulfilling various roles to ensure its success, security, and alignment with government standards and agency goals.
+
+| Role | Name | Affiliation |
+| :----- | :------ | :------------- |
+| {role} | {names} | {affiliations} |
+
+ ## Roles & Responsibilities 
+<!-- Who are the project maintainers? List out @USERNAMES where possible so they can be tagged in issues/PRs directly. -->
+
+ ## Maintainers List 
+<!-- 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. -->
+
+ ## Approvers List 
+<!-- Who are the project approvers? List out @USERNAMES where possible so they can be tagged in issues/PRs directly. -->
+
+ ## Reviewers List 
+<!-- Who are the project reviewers? List out @USERNAMES where possible so they can be tagged in issues/PRs directly. -->
+
+ ## Contributors 
+<!-- Who has contributed to the project? Highlight and credit the users who have contributed to the repository. -->
+
+ ## Alumni 
+<!-- Who are the past maintainers or contributors who previously played significant roles in this project who are no longer actively involved? Consider including their roles and dates for context. -->
+
+ ## Principles 
+<!-- This section communicates to prospective contributors and users what the values of your community are. -->
+
+ ## Community Guidelines 
+<!-- This section communicates specific norms and guidelines for how to participate and contribute positively to your community. The more explicit you can be about behaviors you'd like to encourage or discourage, the less friction new contributors will experience in onboarding and operating within your project. -->
+
+ ## Acknowledgements 
+<!-- This section recognizes previous work and best practices established by the other members of the federal open source community such as USDS, GSA, 18F, and the Justice40 Project. -->

GOVERNANCE.md

@@ -0,0 +1,3 @@
+# Governance 
+<!-- TODO: Starting at Tier 3 GOVERNANCE.md has basic language about early community governance, how the project make decisions, and how contributors are elevated through the leadership process if any (e.g. joining teams, getting maintainer status, etc...)--> 
+ This project is governed by our [Community Guidelines](COMMUNITY.md) and [Code of Conduct](CODE_OF_CONDUCT.md). 

README.md

@@ -155,3 +155,12 @@ For more information and resources about SBOMs, visit: https://www.cisa.gov/sbom
 This project is in the public domain within the United States, and copyright and related rights in the work worldwide are waived through the [CC0 1.0 Universal public domain dedication](https://creativecommons.org/publicdomain/zero/1.0/) as indicated in [LICENSE](LICENSE).
 
 All contributions to this project will be released under the CC0 dedication. By submitting a pull request or issue, you are agreeing to comply with this waiver of copyright interest.
+
+ ## Project Mission 
+<!-- Provide the core mission and objectives driving this project. --> 
+
+ ## Agency Mission 
+<!-- Provide the mission of the agency and how this project aligns. --> 
+
+ ## Team Mission 
+<!-- Provide the team's mission and how they work together. -->