misc: add project governance etc

CODE_OF_CONDUCT.md

@@ -0,0 +1,90 @@
+# Contributor Covenant 3.0 Code of Conduct
+
+## Our Pledge
+
+We pledge to make our community welcoming, safe, and equitable for all.
+
+We are committed to fostering an environment that respects and promotes the dignity, rights, and contributions of all individuals, regardless of characteristics including race, ethnicity, caste, color, age, physical characteristics, neurodiversity, disability, sex or gender, gender identity or expression, sexual orientation, language, philosophy or religion, national or social origin, socio-economic position, level of education, or other status. The same privileges of participation are extended to everyone who participates in good faith and in accordance with this Covenant.
+
+
+## Encouraged Behaviors
+
+While acknowledging differences in social norms, we all strive to meet our community's expectations for positive behavior. We also understand that our words and actions may be interpreted differently than we intend based on culture, background, or native language.
+
+With these considerations in mind, we agree to behave mindfully toward each other and act in ways that center our shared values, including:
+
+1. Respecting the **purpose of our community**, our activities, and our ways of gathering.
+2. Engaging **kindly and honestly** with others.
+3. Respecting **different viewpoints** and experiences.
+4. **Taking responsibility** for our actions and contributions.
+5. Gracefully giving and accepting **constructive feedback**.
+6. Committing to **repairing harm** when it occurs.
+7. Behaving in other ways that promote and sustain the **well-being of our community**.
+
+
+## Restricted Behaviors
+
+We agree to restrict the following behaviors in our community. Instances, threats, and promotion of these behaviors are violations of this Code of Conduct.
+
+1. **Harassment.** Violating explicitly expressed boundaries or engaging in unnecessary personal attention after any clear request to stop.
+2. **Character attacks.** Making insulting, demeaning, or pejorative comments directed at a community member or group of people.
+3. **Stereotyping or discrimination.** Characterizing anyone’s personality or behavior on the basis of immutable identities or traits.
+4. **Sexualization.** Behaving in a way that would generally be considered inappropriately intimate in the context or purpose of the community.
+5. **Violating confidentiality**. Sharing or acting on someone's personal or private information without their permission.
+6. **Endangerment.** Causing, encouraging, or threatening violence or other harm toward any person or group.
+7. Behaving in other ways that **threaten the well-being** of our community.
+
+### Other Restrictions
+
+1. **Misleading identity.** Impersonating someone else for any reason, or pretending to be someone else to evade enforcement actions.
+2. **Failing to credit sources.** Not properly crediting the sources of content you contribute.
+3. **Promotional materials**. Sharing marketing or other commercial content in a way that is outside the norms of the community.
+4. **Irresponsible communication.** Failing to responsibly present content which includes, links or describes any other restricted behaviors.
+
+
+## Reporting an Issue
+
+Tensions can occur between community members even when they are trying their best to collaborate. Not every conflict represents a code of conduct violation, and this Code of Conduct reinforces encouraged behaviors and norms that can help avoid conflicts and minimize harm.
+
+When an incident does occur, it is important to report it promptly. Report a possible violation to MPICH Technical Steering Committee via tsc@lists.mpich.org (see GOVERNANCE). Members from the Technical Steering Committee will act as Community Moderators and address violation reports.
+
+Community Moderators take reports of violations seriously and will make every effort to respond in a timely manner. They will investigate all reports of code of conduct violations, reviewing messages, logs, and recordings, or interviewing witnesses and other participants. Community Moderators will keep investigation and enforcement actions as transparent as possible while prioritizing safety and confidentiality. In order to honor these values, enforcement actions are carried out in private with the involved parties, but communicating to the whole community may be part of a mutually agreed upon resolution.
+
+
+## Addressing and Repairing Harm
+
+If an investigation by the Community Moderators finds that this Code of Conduct has been violated, the following enforcement ladder may be used to determine how best to repair harm, based on the incident's impact on the individuals involved and the community as a whole. Depending on the severity of a violation, lower rungs on the ladder may be skipped.
+
+1) Warning
+   1) Event: A violation involving a single incident or series of incidents.
+   2) Consequence: A private, written warning from the Community Moderators.
+   3) Repair: Examples of repair include a private written apology, acknowledgement of responsibility, and seeking clarification on expectations.
+2) Temporarily Limited Activities
+   1) Event: A repeated incidence of a violation that previously resulted in a warning, or the first incidence of a more serious violation.
+   2) Consequence: A private, written warning with a time-limited cooldown period designed to underscore the seriousness of the situation and give the community members involved time to process the incident. The cooldown period may be limited to particular communication channels or interactions with particular community members.
+   3) Repair: Examples of repair may include making an apology, using the cooldown period to reflect on actions and impact, and being thoughtful about re-entering community spaces after the period is over.
+3) Temporary Suspension
+   1) Event: A pattern of repeated violation which the Community Moderators have tried to address with warnings, or a single serious violation.
+   2) Consequence: A private written warning with conditions for return from suspension. In general, temporary suspensions give the person being suspended time to reflect upon their behavior and possible corrective actions.
+   3) Repair: Examples of repair include respecting the spirit of the suspension, meeting the specified conditions for return, and being thoughtful about how to reintegrate with the community when the suspension is lifted.
+4) Permanent Ban
+   1) Event: A pattern of repeated code of conduct violations that other steps on the ladder have failed to resolve, or a violation so serious that the Community Moderators determine there is no way to keep the community safe with this person as a member.
+   2) Consequence: Access to all community spaces, tools, and communication channels is removed. In general, permanent bans should be rarely used, should have strong reasoning behind them, and should only be resorted to if working through other remedies has failed to change the behavior.
+   3) Repair: There is no possible repair in cases of this severity.
+
+This enforcement ladder is intended as a guideline. It does not limit the ability of Community Managers to use their discretion and judgment, in keeping with the best interests of our community.
+
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public or other spaces. Examples of representing our community include using an official email address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
+
+
+## Attribution
+
+This Code of Conduct is adapted from the Contributor Covenant, version 3.0, permanently available at [https://www.contributor-covenant.org/version/3/0/](https://www.contributor-covenant.org/version/3/0/).
+
+Contributor Covenant is stewarded by the Organization for Ethical Source and licensed under CC BY-SA 4.0. To view a copy of this license, visit [https://creativecommons.org/licenses/by-sa/4.0/](https://creativecommons.org/licenses/by-sa/4.0/)
+
+For answers to common questions about Contributor Covenant, see the FAQ at [https://www.contributor-covenant.org/faq](https://www.contributor-covenant.org/faq). Translations are provided at [https://www.contributor-covenant.org/translations](https://www.contributor-covenant.org/translations). Additional enforcement and community guideline resources can be found at [https://www.contributor-covenant.org/resources](https://www.contributor-covenant.org/resources). The enforcement ladder was inspired by the work of [Mozilla’s code of conduct team](https://github.com/mozilla/inclusion).
+

GOVERNANCE.md

@@ -0,0 +1,84 @@
+# Governance of the MPICH project
+
+## Governance Model
+
+The MPICH Project adopts a flexible hybrid governance model consisting of a
+Technical Core Team and a Steering Committee.
+
+The Technical Core Team is responsible for the day-to-day technical development
+and maintenance of MPICH. Core Team members are generally those granted write
+access to the MPICH GitHub repository. Core Team members may make routine
+technical decisions within their areas of responsibility. While review and
+discussion are strongly encouraged, the level of process required may vary
+depending on the scope, urgency, and impact of a change.
+
+The Steering Committee provides strategic guidance and community oversight. The
+committee may be convened to discuss significant technical, organizational, or
+policy matters affecting the project. Through the voting process defined below,
+the committee may affirm, modify, or overturn decisions made by the Technical
+Core Team.
+
+The governance model is intentionally lightweight and is designed to balance
+efficient project development with broad community participation.
+
+## Technical Core Team
+
+The Technical Core Team consists of members who have at least _Maintain_ permission on the MPICH GitHub project.
+The current members of the Technical Core Team are:
+
+- Hui Zhou, @hzhou, Argonne National Laboratory
+- Rajeev Thakur, @rsth, Argonne National Laboratory
+- Kenneth Raffenetti, @raffenet, Cornelis Networks
+- Robert Latham, @roblatham00, Argonne National Laboratory
+- Sonja Happ, @sonjahapp, ParTec AG
+
+The composition of the Technical Core Team may evolve over time as determined by
+the existing Core Team.
+
+## Technical Steering Committee
+### Role
+The role of the Technical Steering Committee (TSC) is to provide technical direction to the project. The TSC will vote on any matters deferred by the Technical Core Team or issues raised by the community.
+
+### Membership
+Members can be added to the TSC by a majority vote of the TSC. Members may be removed from the TSC by a 2/3 vote of the TSC. If a TSC member has been inactive for over 6 months, the TSC must hold a vote on whether to remove that member from the TSC.
+
+Current Membership:
+
+1. Hui Zhou (Argonne National Laboratory)
+2. Rajeev Thakur (Argonne National Laboratory)
+3. Kenneth Raffenetti (Cornelis Networks)
+4. William Gropp (University of Illinois Urbana-Champaign)
+5. Steve Oyanagi (Hewlett Packard Enterprise)
+6. Nathaniel Shineman (The Ohio State University)
+7. Simon Pickartz (ParTec AG)
+
+### TSC Chair
+The TSC will elect a chair annually. The TSC chair runs TSC meetings and may make interim decisions on urgent matters on behalf of the TSC, which may be reviewed by the TSC at its next meeting.
+
+Current chair:
+
+  * Rajeev Thakur (Argonne National Laboratory)
+
+### Meetings and Notes
+The TSC meets regularly twice every year (time TBD). The meeting agenda will be announced at least two weeks ahead of the meeting. Additional meetings and issues can be raised by TSC members and organised by the TSC chair.
+The meetings are open to the public, and are held virtually. Meeting notes will be published in the MPICH Github wiki.
+
+## Other Public MPICH fora
+
+### Weekly MPICH development meetings
+Public MPICH development meetings are held every Thursday at 9am Central Time. These meetings are held virtually. Meeting agenda and meeting links are announced at least one day ahead via devel@lists.mpich.org.
+
+### MPICH website
+[mpich.org](https://mpich.org)
+
+### MPICH mailing lists
+* annouce@lists.mpich.org - MPICH announcement mailing list
+* devel@lists.mpich.org - MPICH developer mailing list
+* discuss@lists.mpich.org - MPICH general discussion mailing list
+
+### MPICH Slack
+The MPICH project uses #mpich-dev Slack channel for online discussions between MPICH developers. Access to the Slack channel can be requested via devel@lists.mpich.org.
+
+### MPICH Github
+MPICH issues, pull requests, and long term discussions are tracked on the MPICH GitHub page.
+