Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Outline process for maintainer promotion #52

Closed
lukehinds opened this issue Feb 2, 2022 · 1 comment · Fixed by #412
Closed

Outline process for maintainer promotion #52

lukehinds opened this issue Feb 2, 2022 · 1 comment · Fixed by #412
Labels
enhancement New feature or request

Comments

@lukehinds
Copy link
Member

lukehinds commented Feb 2, 2022 •
edited

Document what is the expected duties of a maintainer and how a maintainer is nominated and on boarded (and off boarded). Some considerations:

  • Can someone self nominate, or should an existing maintainer nominate the individual
  • Should there be an outline of what makes a good maintainer (contributions (perhaps a key feature), thoughtful reviews etc). I don't think we can set a criteria and enforce it, but we can at least give contributors some insight into some level of expectation we have.
  • Should there be some expectations of what a maintainer should do (chop the wood / carry water , so triage issues / house keep the project).
@lukehinds lukehinds added bug Something isn't working enhancement New feature or request and removed bug Something isn't working labels Feb 2, 2022
@lukehinds lukehinds changed the title Outline process for maintainer proposals Outline process for maintainer promotion Feb 2, 2022
@dlorenc
Copy link
Member

dlorenc commented Feb 2, 2022

IMO:

  • Can someone self nominate, or should an existing maintainer nominate the individual

I think anyone should be able to do the nomination, either a maintainer or the person.

  • Should there be an outline of what makes a good maintainer (contributions (perhaps a key feature), thoughtful reviews etc). I don't think we can set a criteria and enforce it, but we can at least give contributors some insight into some level of expectation we have.

Yeah, we can give some examples. It could be lots of core feature work, or just lots of reviews/maintenance, or something in between.

  • Should there be some expectations of what a maintainer should do (chop the wood / carry water , so triage issues / house keep the project).

I think there should be a basic handbook. It should include stuff like always acting in the best interest of the project, what to do in case of a conflict between maintainers, etc.

@haydentherapper haydentherapper mentioned this issue Mar 12, 2024
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Update community membership guidelines haydentherapper/community
2 participants
@dlorenc @lukehinds