Skip to content

governance.md: add inactivity policy for any roles #378

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.

Sign up for GitHub

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 3 commits into
base: master
Choose a base branch
from
Open

governance.md: add inactivity policy for any roles #378

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
111b7f1
feat(docs): add inactivity policy for any roles
bjohansebas May 15, 2025
f26ab60
Update docs/GOVERNANCE.md
bjohansebas May 15, 2025
cda4da8
Update docs/GOVERNANCE.md
UlisesGascon May 15, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 18 additions & 0 deletions docs/GOVERNANCE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -155,6 +155,24 @@ 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 and Emeritus Policy for Any Role

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.

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.

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

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

```text
Expand Down