opendev/gerrit
Code Issues Proposed changes

Merge "Define clear criteria for maintainer election"

Browse Source
This commit is contained in:
David Pursehouse
2019-07-24 10:42:25 +00:00
committed by Gerrit Code Review
parent 2aee58d0ce de2c7e10c7
commit e139996123
1 changed files with 13 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

16
Documentation/dev-roles.txt
View File

@@ -209,10 +209,20 @@ In addition, maintainers from Google can:
link:dev-processes.html#upgrading-libraries[Upgrading Libraries]
* edit permissions on the Gerrit core projects
[[maintainer-election]]
Maintainers can nominate new maintainers by posting a nomination on the
non-public maintainers mailing list. Nominations are approved by
consensus among the maintainers. This means maintainers can veto a
nomination.
non-public maintainers mailing list. Nominations should stay open for
at least 14 calendar days so that all maintainers have a chance to
vote. To be approved as maintainer a minimum of 5 positive votes and no
negative votes is required. This means if 5 positive votes without
negative votes have been reached and 14 calendar days have passed, any
maintainer can close the vote and welcome the new maintainer. Extending
the voting period during holiday season or if there are not enough
votes is possible, but the voting period should not exceed 1 month. If
there are negative votes that are considered unjustified, the
link:dev-processes.html#steering-committee[engineering steering
committee] may get involved to decide whether the new maintainer can be
accepted anyway.
To become a maintainer, a link:#contributor[contributor] should have a
history of deep technical contributions across different parts of the