fix: add inactivity policy for any roles (#378)

* feat(docs): add inactivity policy for any roles

Signed-off-by: Sebastian Beltran <bjohansebas@gmail.com>

* Update docs/GOVERNANCE.md

Co-authored-by: Ulises Gascón <ulisesgascongonzalez@gmail.com>

* Update docs/GOVERNANCE.md

Co-authored-by: Sebastian Beltran <bjohansebas@gmail.com>

* Update docs/GOVERNANCE.md

Co-authored-by: Wes Todd <wes@wesleytodd.com>

* Update docs/GOVERNANCE.md

Co-authored-by: Jon Church <me@jonchurch.com>

* fix lint issues

Signed-off-by: Sebastian Beltran <bjohansebas@gmail.com>

* reference to working groups members

Signed-off-by: Sebastian Beltran <bjohansebas@gmail.com>

* Update docs/GOVERNANCE.md

Co-authored-by: Wes Todd <wes@wesleytodd.com>

---------

Signed-off-by: Sebastian Beltran <bjohansebas@gmail.com>
Co-authored-by: Ulises Gascón <ulisesgascongonzalez@gmail.com>
Co-authored-by: Jon Church <me@jonchurch.com>
Co-authored-by: Wes Todd <wes@wesleytodd.com>

Author: 4 people

docs/GOVERNANCE.md

@@ -156,6 +156,26 @@ 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 (such as Triager, Committer, WG member, Project Captain, or TC member) are encouraged 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 someone is deemed inactive, the individual may be transitioned to an emeritus role that reflects their past contributions. A best effort will be made to inform them that this has occurred. They may request to be reinstated when they are ready to be active again.
+* 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 assessing activity levels and enacting 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