ci: add workflow to move inactive approvers/maintainers to emeritus #5898
+245
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Which problem is this PR solving?
This PR introduces partial automation for a task that is necessary but often emotionally taxing: maintaining accurate membership in the @open-telemetry/javascript-approvers and @open-telemetry/javascript-maintainers groups.
While the process of removing inactive members is not personal, it can feel personal. That emotional overhead tends to make this task harder than it should be, and often consumes more mental energy than the actual work involved. Automating parts of it helps reduce that burden and allows us to focus on finding new members to fill that role, rather than stressing over the removal part.
This initial automation focuses on Maintainers and Approvers as we:
The script uses very long threshold: 4 months of no review activity triggers a PR to propose moving a member to emeritus status. This PR still has to be manually approved by the remaining maintainers, and after the PR is merged, the group itself has to be manually updated. A single review within that period - regardless of whether it’s on their own PR or someone else's - prevents being auto-moved to emeritus. I chose this time frame to accommodate very-long vacations and other planned absences. For longer periods of inactivity, contributors are encouraged to reach out to the Maintainers.
I plan to further tweak the script in the coming months, including other members like Triagers and Component Owners as well.