Skip to content
Open
Changes from all commits
Commits
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
39 changes: 39 additions & 0 deletions processes/INACTIVE_MAINTAINERS.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,39 @@

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I could be really annoying and mention the unnecessary blank lines on line 1, 9, and 10. But that would be super nitpicky and annoying.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LMACTFT. Let me ask Claude to Fix That! Yeah, this is definitly not yet ready for final approval.

## Process

1. Find inactive maintainer using [metrics dashboard](https://metrics.opensearch.org/_dashboards/app/dashboards#/view/30fedc30-9ae2-11ef-a168-f19b1bbc360c)
1. Filter out archived repos
1. Open a PR using the template text below
1. Wait seven days
1. Close or merge the PR per the instructions in the template text

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

While I think its great to make any document as minimal as possible, the first time of me looking into this document left me slightly confused as I first did not realize that the above 5 lines are actually the main content of this document.

I am wondering whether it might help first to add a very short Introduction section, which specifies what process is defined here. That might be just something along

This document specifies the process for implementing the maintainer inactivity policy

Additionally, I guess a process definition needs to define who (or which roles) is/are going to execute the process and possibly as well how often this is going to happen (just roughly).



## PR Template Text

```
Hey @{GITHUB_HANDLE}, we noticed you haven't used your maintainer privileges
in this repository over the past year. Per the OpenSearch Project
[inactivity policy](https://github.com/opensearch-project/technical-steering/blob/main/policies/RESPONSIBILITIES.md#inactivity),
maintainers inactive for 12 months or more are moved to emeritus status.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is slightly incorrect, as the 12 months are not specified in the RESPONSIBILITIES.md file. It just says:

If a maintainer becomes inactive for a time (usually several months), ...

I think the RESPONSIBILITIES.md should be then also adapted to reflect this figure.


**If you plan to continue contributing as a maintainer**, please respond here
and close this PR and no further action is needed.

Otherwise, this PR will move you to the emeritus list. Emeritus status is
not permanent: you can return to active maintainer status at any time by
expressing interest to the current maintainers.

**Existing maintainers**: Please merge this PR once @{GITHUB_HANDLE} confirms
they do not plan to use their maintainer privileges, or after 7 days with no
response. If neither maintainers nor @{GITHUB_HANDLE} take any action within
7 days, a member of the [admin team](https://github.com/orgs/opensearch-project/teams/admin)
will merge it.

### Activity data

This determination is based on the
[OpenSearch Maintainer Dashboard](https://metrics.opensearch.org/_dashboards/app/dashboards#/view/30fedc30-9ae2-11ef-a168-f19b1bbc360c)
(filter by repository: `{REPO_NAME}`). If you believe the activity data is
mistaken, please say so here so we can investigate before merging.
```
Loading