Add an issue template for maintainer onboarding #1924
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
svrnm
requested review from
alolita,
austinlparker,
danielgblanco,
dyladan,
jpkrohling,
mtwo,
tedsuo and
trask
as code owners
| type: checkboxes | ||
| attributes: | ||
| label: Maintainer Onboarding Tasks | ||
| description: | |
There was a problem hiding this comment.
Should this mention that these are to be done by a current maintainer?
There was a problem hiding this comment.
Yeah, this needs to be clearer
| type: checkboxes | ||
| attributes: | ||
| label: Maintainer Election | ||
| description: | |
There was a problem hiding this comment.
Should this point back to the Becoming a Maintainer part of the docs rather than repeating the election process?
There was a problem hiding this comment.
good point! Let me fix that.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR introduces a dedicated issue template to elect and onboard a new maintainer.
Preview: https://github.com/svrnm/community/issues/new?assignees=&labels=area%2Fgithub-membership&projects=&template=maintainer-onboarding.yml&title=Onboard+%3CGitHub+handle%3E+as+%3CSIG%2FWG+FOO%3E+maintainer
Problem
the current process to elect maintainers has never(?) been applied, and since the list of maintainers & approvers lives mainly in the SIG repos now ("The list of active members (both "approvers" and "maintainers") for the can be found in the README file") it also does not match the requirements anymore.
Unfortunately, by only updating those files in the repo (or updating the github teams) the community does not hear about new maintainers stepping up. This makes it hard for cross-functional SIGS (Comms, EUWG, security, demo) to know who the maintainers are and also the TC&GC has no full visiblity into that, making it hard to judge from the outside if a SIG has a healthy set of maintainers. Finally, we (the OpenTelemetry community) should treat an individual stepping up as a maintainer as a highlight, that should be visible and recognized.
Solution
By introducing an onboarding issue for maintainers we can address all those needs, and at the same time also accomplish a few additional things, like having checklists for existing maintainers and new maintainers, or being able to introduce same additional rituals (e.g. introducing an informal chat between a new maintainer and a GC member to welcome them)
Please, take a look at this PR. I added a lot of additional features, that may not be wanted, so I expect this file to shrink, and there may be things I missed, so it might grow.
Other details