update governance #12896
Draft
update governance #12896
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
agramfort
approved these changes
Oct 13, 2024
| among SC members) | ||
| - Attendance at advisory board meetings (approx. every 1-2 years) | ||
| - Write funding proposals | ||
| - Communicate/coordinate with maintainer team |
There was a problem hiding this comment.
Suggested change
| - Communicate/coordinate with maintainer team | |
| - Communicate/coordinate with Maintainer Team |
| responsibilities of other teams | ||
| - Attendance at Steering Council meetings (approx. every 2 weeks; time to be decided | ||
| among SC members) | ||
| - Attendance at advisory board meetings (approx. every 1-2 years) |
There was a problem hiding this comment.
Suggested change
| - Attendance at advisory board meetings (approx. every 1-2 years) | |
| - Attendance at Advisory Board meetings (approx. every 1-2 years) |
|
|
||
| - Obtaining funding (either by writing grants specifically for MNE development, or | ||
| convincing others to include funds for MNE development in their research grants) | ||
| - Translating high-level roadmap guidance from the advisory board (e.g. “better support |
There was a problem hiding this comment.
Suggested change
| - Translating high-level roadmap guidance from the advisory board (e.g. “better support | |
| - Translating high-level roadmap guidance from the Advisory Board (e.g. “better support |
| Maintainer Team | ||
| --------------- | ||
|
|
||
| The maintainer team is responsible for implementing changes to the software and |
There was a problem hiding this comment.
Suggested change
| The maintainer team is responsible for implementing changes to the software and | |
| The Maintainer Team is responsible for implementing changes to the software and |
| All-hands meetings | ||
| ------------------ | ||
|
|
||
| At least once a year, all Maintainers and Steering Council members should come together |
There was a problem hiding this comment.
Suggested change
| At least once a year, all Maintainers and Steering Council members should come together | |
| At least once a year, all maintainers and Steering Council members should come together |
|
|
||
| Votes for steering council membership shall be scheduled as-needed to address steering | ||
| council workload, and advertised to eligible candidates (i.e., the maintainer team) for | ||
| a minimum of 14 days, after which a vote of current maintainers and steering council |
There was a problem hiding this comment.
Suggested change
| a minimum of 14 days, after which a vote of current maintainers and steering council | |
| a minimum of 14 days, after which a vote of current maintainers and Steering Council |
Comment on lines
+283
to
+284
| steering council shall be scheduled. The maintainer team shall set up a confidential | ||
| submission system for applications (consisting of short candidate statements), such as a |
There was a problem hiding this comment.
Suggested change
| steering council shall be scheduled. The maintainer team shall set up a confidential | |
| submission system for applications (consisting of short candidate statements), such as a | |
| Steering Council shall be scheduled. The Maintainer Team shall set up a confidential | |
| submission system for applications (consisting of short candidate statements), such as a |
| - Monitoring CI failures and addressing them | ||
| - Community maintenance: answering forum posts, holding office hours | ||
| - Community information: social media announcements (releases, new features, etc) | ||
| - Training new members of the maintainer team |
There was a problem hiding this comment.
Suggested change
| - Training new members of the maintainer team | |
| - Training new members of the Maintainer Team |
Comment on lines
+57
to
+58
| - Infrastructure/large-scale software decisions, in partnership with the steering | ||
| council |
There was a problem hiding this comment.
Suggested change
| - Infrastructure/large-scale software decisions, in partnership with the steering | |
| council | |
| - Infrastructure/large-scale software decisions, in partnership with the Steering | |
| Council |
| multiple submodules), in partnership with the maintainer team | ||
| - Infrastructure decisions (e.g., dependency version policy, release cadence, CI | ||
| management, etc), in partnership with the maintainer team | ||
| - Any other Governance task not mentioned elsewhere, and that falls outside of the |
There was a problem hiding this comment.
Suggested change
| - Any other Governance task not mentioned elsewhere, and that falls outside of the | |
| - Any other governance task not mentioned elsewhere, and that falls outside of the |
larsoner
approved these changes
Oct 15, 2024
I agree with this. However note that I have not been employed by "Max Planck Institute für Bildungsforschung" since 2024-07-14. So I guess this triggered the "1 year grace period" for them until they are moved to "former partners". Shall I create an event for this on our mne steering council calendar? EDIT: As institutional partners are typically tied to a steering council member, it would be good to put some processes in place that these steering council members keep track of adding / removing the institutional partners (and how, e.g., with calendar entries for removal). |
sappelhoff
approved these changes
Oct 16, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Update our public governance document.
TODOs:
doc/overview/people.rstdoc/overview/people.rstinstead.