Skip to content

[Governance] Clarify response times for inactive core members #2501

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

Open
wants to merge 12 commits into
base: main
Choose a base branch
from
25 changes: 17 additions & 8 deletions community/governance.md.tmpl
Original file line number Diff line number Diff line change
Expand Up @@ -37,14 +37,20 @@ Here are defined the primary teams participating in conda-forge activities.
core, part of staged-recipes, or maintainers. This includes first-time
contributors, collaborators, and funders. They have no special rights within
the conda-forge organization itself.
* **emeritus-core:** Core members that are inactive (commits, GitHub comments/issues/reviews,
dev meetings and voting on polls) in the past six months will be asked if they want to become emeritus-core
developers. Any core member can also request to become emeritus if they wish to do so
(e.g. taking a sabbatical or long vacation).
Emeritus core members can still vote and move back to active core anytime. Emeritus
votes are used to count towards quorum but the quorum size is computed from the size of
the active core group. The `core.csv` list should be updated when a change in the status
of a member occurs.
* **emeritus-core:** Core members that are inactive (commits, GitHub
comments/issues/reviews, chat platforms, dev meetings, and voting on polls) in the
past six months will be asked if they want to become emeritus-core developers. One
week after asking, if the inactive core member has not responded, they will be
automatically moved to emeritus-core. Any core member can also request to become
emeritus if they wish to do so (e.g. taking a sabbatical or long vacation).
Every 12 months or more, one core member should ask the rest of the team to
report their activity status. The question must only include two answers:
active or inactive. Core members must have at least a week to reply. Members that reply
"inactive" or do not reply within the established period will be moved to emeritus-core.
Emeritus core members can still vote and move back to active core anytime.
Emeritus votes are used to count towards quorum but the quorum size is computed
from the size of the active core group. The `core.csv` list should be updated when
a change in the status of a member occurs.

## Sub-Teams

Expand Down Expand Up @@ -350,4 +356,7 @@ In alphabetical order,

This document was written by Anthony Scopatz.

In Apr 2025, two new clauses were added regarding core and core-emeritus
membership.

This document is released under the CC-BY 4.0 license.
Loading