Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

update governance #12896

Draft
wants to merge 7 commits into
base: main
Choose a base branch
from
Draft

update governance #12896

wants to merge 7 commits into from

Conversation

drammock
Copy link
Member

@drammock drammock commented Oct 11, 2024

Update our public governance document.

TODOs:

  • now that new governance is adopted, set a deadline for current maintainer team members to volunteer for steering council. deadline is Nov 1 and was announced on Discord and maintainer email list
  • Once steering council membership finalized, update doc/overview/people.rst
  • the sections on "the project" and "institutional partners" were not included in the proposed restructuring. For now I've left them in place. If folks disagree with that course of action, I think we could summarize the "institutional partners" content at the start of the "institutional partners" list on doc/overview/people.rst instead.

Copy link
Member

@britta-wstnr britta-wstnr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM.
Unified capitalization a bit more - hope I have caught all (most) things.

among SC members)
- Attendance at advisory board meetings (approx. every 1-2 years)
- Write funding proposals
- Communicate/coordinate with maintainer team
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

@sappelhoff
Copy link
Member

sappelhoff commented Oct 16, 2024

the sections on "the project" and "institutional partners" were not included in the proposed restructuring. For now I've left them in place.

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants