From 111b7f1e7b61943fcf39b2c10530ab83e5af4ef1 Mon Sep 17 00:00:00 2001 From: Sebastian Beltran Date: Wed, 14 May 2025 22:10:10 -0500 Subject: [PATCH 1/3] feat(docs): add inactivity policy for any roles Signed-off-by: Sebastian Beltran --- docs/GOVERNANCE.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/docs/GOVERNANCE.md b/docs/GOVERNANCE.md index 5dd4be7..b1c58bc 100644 --- a/docs/GOVERNANCE.md +++ b/docs/GOVERNANCE.md @@ -155,6 +155,18 @@ The list can be found at [https://github.com/expressjs/discussions/blob/HEAD/doc The list can be found at [https://github.com/expressjs/discussions/blob/HEAD/docs/contributing/captains_and_committers.md#current-initiative-captains](https://github.com/expressjs/discussions/blob/HEAD/docs/contributing/captains_and_committers.md#current-initiative-captains) +## Inactivity Policy for Any Role + +To ensure the *health* and *continuity* of the project, anyone holding a *role* within the community (*Triager, Committer, Project Captain,* or *TC member*) must maintain *active participation*. + +**Definition of *inactivity*:** Not having *activity* in the project (such as *contributions, reviews, triage, attending meetings, participating in discussions,* etc.) for a *consecutive period of 6 months*. + +**Process upon detecting *inactivity*:** + +- The person will be *notified* about their *inactive status* and *invited* to *resume participation* within a *reasonable timeframe*. +- If *participation* is *not resumed* after that period, the person may be *removed* or *moved to an inactive status* corresponding to their *role*. +- In case of *disagreement*, the situation may be *discussed* and *resolved by consensus* within the *TC* or the respective *team*. + ## Developer's Certificate of Origin 1.1 ```text From f26ab6052475210315766f85ff75af77bd6d3e86 Mon Sep 17 00:00:00 2001 From: Sebastian Beltran Date: Thu, 15 May 2025 08:13:39 -0500 Subject: [PATCH 2/3] Update docs/GOVERNANCE.md MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Ulises Gascón --- docs/GOVERNANCE.md | 20 +++++++++++++------- 1 file changed, 13 insertions(+), 7 deletions(-) diff --git a/docs/GOVERNANCE.md b/docs/GOVERNANCE.md index b1c58bc..be87b0d 100644 --- a/docs/GOVERNANCE.md +++ b/docs/GOVERNANCE.md @@ -155,17 +155,23 @@ The list can be found at [https://github.com/expressjs/discussions/blob/HEAD/doc The list can be found at [https://github.com/expressjs/discussions/blob/HEAD/docs/contributing/captains_and_committers.md#current-initiative-captains](https://github.com/expressjs/discussions/blob/HEAD/docs/contributing/captains_and_committers.md#current-initiative-captains) -## Inactivity Policy for Any Role +## Inactivity and Emeritus Policy for Any Role -To ensure the *health* and *continuity* of the project, anyone holding a *role* within the community (*Triager, Committer, Project Captain,* or *TC member*) must maintain *active participation*. +To support the health and continuity of the project, all individuals holding a role within the community (Triager, Committer, Project Captain, or TC member) are expected to maintain active participation. -**Definition of *inactivity*:** Not having *activity* in the project (such as *contributions, reviews, triage, attending meetings, participating in discussions,* etc.) for a *consecutive period of 6 months*. +Inactivity is defined as the absence of meaningful involvement in the project—such as contributions, code reviews, triage, meeting attendance, or discussion participation—for a continuous period of 6 months. -**Process upon detecting *inactivity*:** +### Exceptions +Anyone may request a temporary leave from active participation due to personal or professional reasons. In such cases, the individual should inform the relevant team or the Technical Committee (TC). During this time, the inactivity policy is paused, and the individual will not be flagged as inactive. -- The person will be *notified* about their *inactive status* and *invited* to *resume participation* within a *reasonable timeframe*. -- If *participation* is *not resumed* after that period, the person may be *removed* or *moved to an inactive status* corresponding to their *role*. -- In case of *disagreement*, the situation may be *discussed* and *resolved by consensus* within the *TC* or the respective *team*. +### Inactivity Process +- If no exception is communicated and inactivity is detected, the individual will be notified and invited to resume participation within a reasonable timeframe. +- If participation is not resumed, the individual may be transitioned to an emeritus role that reflects their past contributions. +- The emeritus status helps preserve a clear record of contributors who have meaningfully shaped the project over time. + +### Accountability +- The Technical Committee (TC) is responsible for monitoring activity levels and applying this policy fairly and transparently, in coordination with other relevant teams. +- In case of disagreement, the situation can be discussed and resolved by consensus within the TC or appropriate team. ## Developer's Certificate of Origin 1.1 From cda4da8d6ac2ac37a615514d42f2acfa4bed7576 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ulises=20Gasc=C3=B3n?= Date: Thu, 15 May 2025 15:42:06 +0200 Subject: [PATCH 3/3] Update docs/GOVERNANCE.md Co-authored-by: Sebastian Beltran --- docs/GOVERNANCE.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/GOVERNANCE.md b/docs/GOVERNANCE.md index be87b0d..44abbde 100644 --- a/docs/GOVERNANCE.md +++ b/docs/GOVERNANCE.md @@ -170,7 +170,7 @@ Anyone may request a temporary leave from active participation due to personal o - The emeritus status helps preserve a clear record of contributors who have meaningfully shaped the project over time. ### Accountability -- The Technical Committee (TC) is responsible for monitoring activity levels and applying this policy fairly and transparently, in coordination with other relevant teams. +- The Technical Committee (TC) and the respective captains of each package/team are responsible for monitoring activity levels and enforcing this policy fairly and transparently, in coordination with other relevant teams. - In case of disagreement, the situation can be discussed and resolved by consensus within the TC or appropriate team. ## Developer's Certificate of Origin 1.1