misc: add project governance etc - #7841
Conversation
df3916b to
238f248
Compare
| ### 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 |
There was a problem hiding this comment.
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?
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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.
f634bf8 to
14f5673
Compare
06c85ae to
a313661
Compare
sonjahapp
left a comment
sonjahapp
left a comment
There was a problem hiding this comment.
Some editorial comments - mainly about unifying the terminology.
|
|
||
| ## 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. |
There was a problem hiding this comment.
| 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.
There was a problem hiding this comment.
Do we want (need?) to specify the required majority to take a decision? For the membership votings this is more clearly specified.
spickartz
left a comment
spickartz
left a comment
There was a problem hiding this comment.
Added some minor questions/corrections.
|
|
||
| ## 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. |
There was a problem hiding this comment.
Do we want (need?) to specify the required majority to take a decision? For the membership votings this is more clearly specified.
| 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. |
There was a problem hiding this comment.
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.
4 participants
Pull Request Description
In preparing for joining HPSF - hpsfoundation/tac#91
[skip spell]
[skip whitespace]
[skip warnings]
Author Checklist
Particularly focus on why, not what. Reference background, issues, test failures, xfail entries, etc.
Commits are self-contained and do not do two things at once.
Commit message is of the form:
module: short descriptionCommit message explains what's in the commit.
Whitespace checker. Warnings test. Additional tests via comments.
For non-Argonne authors, check contribution agreement.
If necessary, request an explicit comment from your companies PR approval manager.