Difference between revisions of "Category:Maintainer"
Jump to navigation
Jump to search
(Created page with "See http://docs.bisq.network/roles.html#maintainer Category:Roles") |
HunterNyan (talk | contribs) (Describe "Maintainer" Role Types) |
||
Line 1: | Line 1: | ||
− | + | =Maintainer= | |
+ | A Maintainer is a contributor responsible for enforcing process in a given GitHub repository. | ||
+ | |||
+ | Examples: [[Proposals Maintainer]], [[Compensation maintainer]]. | ||
+ | |||
+ | ==Maintainer Duties== | ||
+ | * Merging or closing pull requests after sufficient review. | ||
+ | * Tagging releases. | ||
+ | * Triaging incoming issues and keeping them organized over time. | ||
+ | ** A Maintainer is not a Developer or a Reviewer | ||
+ | ** Submitting and reviewing pull requests is something any contributor can do; neither are maintainer duties per se. | ||
+ | ** This is particularly important from a [[Compensation]] perspective. If you are a maintainer, do NOT group your development and review activities together with your maintainer role in your compensation requests. Rather, account for them separately like any other contributor would. | ||
+ | ** The goal is to have as many competent contributors developing and reviewing as possible, not to load everything on the maintainer. [https://rfc.unprotocols.org/spec:1/C4/#21-preliminaries C4] is the inspiration here, it’s worth (re-)reading. | ||
+ | |||
+ | ==Maintainer Rights== | ||
+ | * Write access to the repository they are responsible for. | ||
[[Category:Roles]] | [[Category:Roles]] |
Latest revision as of 18:33, 27 April 2020
Maintainer
A Maintainer is a contributor responsible for enforcing process in a given GitHub repository.
Examples: Proposals Maintainer, Compensation maintainer.
Maintainer Duties
- Merging or closing pull requests after sufficient review.
- Tagging releases.
- Triaging incoming issues and keeping them organized over time.
- A Maintainer is not a Developer or a Reviewer
- Submitting and reviewing pull requests is something any contributor can do; neither are maintainer duties per se.
- This is particularly important from a Compensation perspective. If you are a maintainer, do NOT group your development and review activities together with your maintainer role in your compensation requests. Rather, account for them separately like any other contributor would.
- The goal is to have as many competent contributors developing and reviewing as possible, not to load everything on the maintainer. C4 is the inspiration here, it’s worth (re-)reading.
Maintainer Rights
- Write access to the repository they are responsible for.
Pages in category "Maintainer"
The following 5 pages are in this category, out of 5 total.