governance.md: add inactivity policy for any roles #378
Conversation
Signed-off-by: Sebastian Beltran <[email protected]>
Co-authored-by: Ulises Gascón <[email protected]>
bjohansebas
added
top priority
Co-authored-by: Sebastian Beltran <[email protected]>
|
|
||
| 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. |
There was a problem hiding this comment.
Did we intentionally shorten this compared to what is in the Contributing guide?
To remain "active" a TC member should have participation within the last 12 months and miss no more than six consecutive TC meetings. Our goal is to increase participation, not punish people for any lack of participation, this guideline should be only be used as such (replace an inactive member with a new active one, for example). Members who do not meet this are expected to step down. If A TC member does not step down, an issue can be opened in the discussions repo to move them to inactive status. TC members who step down or are removed due to inactivity will be moved into inactive status.
There was a problem hiding this comment.
We discussed on the working session today that we are good with this change as long as we also apply it to the TC wording there. We just want to keep it simple and have one policy. The easiest way seems to be to make this also 12 months, but I don't think anyone had a major concern about changing that to 6 months either.
There was a problem hiding this comment.
Discussed on TC call today and we are good to go forward with this. We will update the other contributing guide to align on 6 months going forward.
| @@ -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. | |||
There was a problem hiding this comment.
| 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. | |
| 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 expected to maintain active participation. |
There was a problem hiding this comment.
| 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. | |
| 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 encouraged to maintain active participation. |
| - 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. |
There was a problem hiding this comment.
I would much prefer that we just notify them and transition them. Adding an additional waiting period is just another thing to track. It's also ambiguous what a "reasonable timeframe is", and that can get muddy trying to decide what a specific time period would be. And none of that is worth it because in nearly all cases, people who have stopped participating are not suddenly going to spring into action again just because we have notified them they have been inactive.
There was a problem hiding this comment.
I agree, It is really easy to just re-add folks.
| @@ -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. | |||
There was a problem hiding this comment.
| 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. | |
| 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 encouraged to 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. | ||
|
|
||
| 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. |
There was a problem hiding this comment.
We discussed on the working session today that we are good with this change as long as we also apply it to the TC wording there. We just want to keep it simple and have one policy. The easiest way seems to be to make this also 12 months, but I don't think anyone had a major concern about changing that to 6 months either.
The goal of this is to have something written for when a member is considered inactive and to establish a certain process. Any suggestions on the wording are welcome.
This is important because of roles like captains who have access to package publishing—having someone with access who is no longer active in the project can be risky, so only active people should have access