misc: add project governance etc by hzhou · Pull Request #7841 · pmodels/mpich

hzhou · 2026-06-14T21:37:43Z

Pull Request Description

In preparing for joining HPSF - hpsfoundation/tac#91

Adopt Apache 2 license
Add CODE_OF_CONDUCT
Add GOVERNANCE.md

[skip spell]
[skip whitespace]
[skip warnings]

Author Checklist

Provide Description
Particularly focus on why, not what. Reference background, issues, test failures, xfail entries, etc.
Commits Follow Good Practice
Commits are self-contained and do not do two things at once.
Commit message is of the form: module: short description
Commit message explains what's in the commit.
Passes All Tests
Whitespace checker. Warnings test. Additional tests via comments.
Contribution Agreement
For non-Argonne authors, check contribution agreement.
If necessary, request an explicit comment from your companies PR approval manager.

raffenet · 2026-07-15T17:26:39Z

+### Weekly MPICH development meetings
+Public MPICH development meetings are held every Thursday at 9am Central Time. These meetings are held virtually. Meeting agenda and meetinglinks are announced at least one day ahead via devel@lists.mpich.org.
+
+### MPICH mailing lists


do you also want to list announce@lists.mpich.org? related Q: do we know if a web interface for mailing lists will be available again?

Yes. Thanks for reminding me.

The archives are available, for example: https://mailman.cels.anl.gov/archives/list/discuss@lists.mpich.org/. It appears to me it is a public accessible link. But let me know if you have access issue. We probably should post the archive links on the website (my TODO this afternoon).

Unfortunately the old archives are not available at the moment. I need work with the IT to see if we can get that up as well.

Ah. I guess I was expecting a redirect for https://lists.mpich.org/ to go to the new web interface. I can just go to the CELS page myself from now on.

sonjahapp

Some editorial comments - mainly about unifying the terminology.

sonjahapp · 2026-07-16T14:18:41Z

+## Governance Model
+
+The MPICH Project adopts a flexible hybrid governance model consisting of a
+Technical Core Team and a Steering Committee.


Suggested change

Technical Core Team and a Steering Committee.

Technical Core Team and a Technical Steering Committee.

We should probably introduce the two acronyms TCT and TSC already here.

sonjahapp · 2026-07-16T14:19:06Z

+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


Suggested change

and maintenance of MPICH. Core Team members are generally those granted write

and maintenance of MPICH. Technical Core Team members are generally those granted write

sonjahapp · 2026-07-16T14:19:25Z

+
+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


Suggested change

access to the MPICH GitHub repository. Core Team members may make routine

access to the MPICH GitHub repository. Technical Core Team members may make routine

sonjahapp · 2026-07-16T14:20:17Z

+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


Suggested change

The Steering Committee provides strategic guidance and community oversight. The

The Technical Steering Committee provides strategic guidance and community oversight. The

sonjahapp · 2026-07-16T14:20:50Z

+- Sonja Happ, @sonjahapp, ParTec AG
+
+The composition of the Technical Core Team may evolve over time as determined by
+the existing Core Team.


Suggested change

the existing Core Team.

the existing Technical Core Team.

sonjahapp · 2026-07-16T14:23:25Z

+
+## 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.


Suggested change

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.

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.

Each member of the TSC has one vote.

Clarify that voting is one vote per member of TSC.

Do we want (need?) to specify the required majority to take a decision? For the membership votings this is more clearly specified.

sonjahapp · 2026-07-16T14:24:53Z

+[mpich.org](https://mpich.org)
+
+### MPICH mailing lists
+* annouce@lists.mpich.org - MPICH announcement mailing list


Suggested change

* annouce@lists.mpich.org - MPICH announcement mailing list

* announce@lists.mpich.org - MPICH announcement mailing list

spickartz

Added some minor questions/corrections.

spickartz · 2026-07-16T16:25:22Z

+## Governance Model
+
+The MPICH Project adopts a flexible hybrid governance model consisting of a
+Technical Core Team and a Steering Committee.


We should probably introduce the two acronyms TCT and TSC already here.

spickartz · 2026-07-16T16:28:48Z

+  * 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.


Suggested change

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 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 organized by the TSC chair.

spickartz · 2026-07-16T16:31:44Z

+
+## 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.


Do we want (need?) to specify the required majority to take a decision? For the membership votings this is more clearly specified.

spickartz · 2026-07-16T16:33:15Z

+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.


What means "active"? If the TSC only meets twice a year, does this mean the member has to attend each meeting to be counted as active?

LICENSE is a copy of the Apache v2.0 license text. NOTICE adopts Apache recommendation and lists major contributors.

This is an exact copy from https://www.contributor-covenant.org. It will serve as a starting base. MPICH's adaptation will show as spearate individual commits.

A simplified version following the example of the spack project.

hzhou changed the title ~~2606 governance~~ misc: add project governance etc Jun 16, 2026

hzhou force-pushed the 2606_governance branch 2 times, most recently from df3916b to 238f248 Compare July 14, 2026 16:29

hzhou requested review from raffenet, rsth, spickartz and wgropp July 14, 2026 16:57

raffenet reviewed Jul 15, 2026

View reviewed changes

hzhou force-pushed the 2606_governance branch 2 times, most recently from f634bf8 to 14f5673 Compare July 15, 2026 17:43

raffenet approved these changes Jul 15, 2026

View reviewed changes

hzhou force-pushed the 2606_governance branch 5 times, most recently from 06c85ae to a313661 Compare July 15, 2026 19:45

sonjahapp reviewed Jul 16, 2026

View reviewed changes

spickartz reviewed Jul 16, 2026

View reviewed changes

hzhou added 4 commits August 12, 2026 12:27

misc: add Apache v2.0 license files

7403091

LICENSE is a copy of the Apache v2.0 license text. NOTICE adopts Apache recommendation and lists major contributors.

misc: add base copy of CODE_OF_CONDUCT

7cda2c0

This is an exact copy from https://www.contributor-covenant.org. It will serve as a starting base. MPICH's adaptation will show as spearate individual commits.

misc: adapt the NOTES in CODE_OF_CONDUCT

94b376c

misc: add GOVERNANCE.md

cee7394

A simplified version following the example of the spack project.

hzhou force-pushed the 2606_governance branch from a313661 to cee7394 Compare August 12, 2026 17:28

	Technical Core Team and a Steering Committee.
	Technical Core Team and a Technical Steering Committee.

	and maintenance of MPICH. Core Team members are generally those granted write
	and maintenance of MPICH. Technical Core Team members are generally those granted write

	access to the MPICH GitHub repository. Core Team members may make routine
	access to the MPICH GitHub repository. Technical Core Team members may make routine

	The Steering Committee provides strategic guidance and community oversight. The
	The Technical Steering Committee provides strategic guidance and community oversight. The

	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.
	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.
	Each member of the TSC has one vote.

	* annouce@lists.mpich.org - MPICH announcement mailing list
	* announce@lists.mpich.org - MPICH announcement mailing list

	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 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 organized by the TSC chair.

Uh oh!

Conversation

hzhou commented Jun 14, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Pull Request Description

Author Checklist

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

sonjahapp left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

spickartz left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

hzhou commented Jun 14, 2026 •

edited

Loading