Repolinter Results

COMMUNITY.md

@@ -0,0 +1,77 @@
+## 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 --> 
+
+repo-scaffolder 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                                    |
+| :---------------- | :---------------- | :--------------------------------------------- |
+| Open Source Lead  | Remy DeCausemaker | OSPO, Digital Service at CMS                   |
+| Software Engineer | Natalia Luzuriaga | OSPO, Digital Service at CMS, US Digital Corps |
+| Software Engineer | Isaac Milarsky    | OSPO, Digital Service at CMS, US Digital Corps |
+| Software Engineer | Dinne Kopelevich  | OSPO, Digital Service at CMS, US Digital Corps |
+| Software Engineer | Sachin Panayil    | OSPO, Digital Service at CMS, US Digital Corps |
+
+## Roles & Responsibilities
+
+The members of the repo-scaffolder community are responsible for guiding its development, ensuring quality standards, and fostering a collaborative environment. They play a vital role in making decisions about code contributions, handling releases, and ensuring the project meets its goals and objectives. Below is a list of the key members and their specific roles and responsibilities.
+
+### Maintainers:
+
+- @natalialuzuriaga
+- @decause-gov
+
+### Approvers:
+
+- @natalialuzuriaga
+- @decause-gov
+
+### Reviewers:
+
+- @IsaacMilarky
+- @DinneK
+- @sachin-panayil
+
+| Roles      | Responsibilities                               | Requirements                                                                      | Defined by                                                |
+| ---------- | :--------------------------------------------- | :-------------------------------------------------------------------------------- | :-------------------------------------------------------- |
+| member     | active contributor in the community            | multiple contributions to the project.                                            | PROJECT GitHub org Committer Team                         |
+| reviewer   | review contributions from other members        | history of review and authorship in a sub-project                                 | COMMUNITY file reviewer entry, and GitHub Org Triage Team |
+| approver   | approve accepting contributions                | highly experienced and active reviewer + contributor to a sub-project             | COMMUNITY file approver entry and GitHub Triage Team      |
+| maintainer | set direction and priorities for a sub-project | demonstrated responsibility and excellent technical judgement for the sub-project | COMMUNITY file owner entry and GitHub Org Admin Team      |
+
+ ## 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
+
+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
+
+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 ospo-guide 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)
+- 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
+
+The Community Guidelines sections were 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.