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

* Clarify response times for inactive core members

* add option to survey activity on the whole team once a year

* fix history

* Apply suggestions from code review

* Update community/governance.md.tmpl

Co-authored-by: Matthew R. Becker <[email protected]>

* pre-commit

* clarify contacting rules

* Update community/governance.md.tmpl

* clarify public question

---------

Co-authored-by: Matthew R. Becker <[email protected]>

Author: jaimergp

community/governance.md.tmpl

@@ -37,14 +37,25 @@ 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 do not show any activity in their core
+  responsibilities (including organization maintenance in the form of commits,
+  GitHub comments, issues, or reviews; participation in chat platforms and
+  community meetings; voting on polls) in the past six months will be asked if
+  they want to become emeritus-core developers. Four weeks after asking, if the
+  inactive core member has not responded, they will be automatically moved to
+  emeritus-core. Every 12 months, 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 reply within four weeks.
+  The question should be asked in a public space (e.g. a Github issue/PR).
+  Members that reply "inactive" or do not reply within the established period
+  will be moved to emeritus-core. Individual and group activity inquiries must
+  at least follow the same contacting methods stated for Time-out Quorum Rules.
+  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` and `emeritus.csv` lists must be updated when
+  a change in the status of a member occurs.
 
 ## Sub-Teams
 
@@ -350,4 +361,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.