Merge "Define clear criteria for maintainer election"
This commit is contained in:
@@ -209,10 +209,20 @@ In addition, maintainers from Google can:
|
|||||||
link:dev-processes.html#upgrading-libraries[Upgrading Libraries]
|
link:dev-processes.html#upgrading-libraries[Upgrading Libraries]
|
||||||
* edit permissions on the Gerrit core projects
|
* edit permissions on the Gerrit core projects
|
||||||
|
|
||||||
|
[[maintainer-election]]
|
||||||
Maintainers can nominate new maintainers by posting a nomination on the
|
Maintainers can nominate new maintainers by posting a nomination on the
|
||||||
non-public maintainers mailing list. Nominations are approved by
|
non-public maintainers mailing list. Nominations should stay open for
|
||||||
consensus among the maintainers. This means maintainers can veto a
|
at least 14 calendar days so that all maintainers have a chance to
|
||||||
nomination.
|
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
|
To become a maintainer, a link:#contributor[contributor] should have a
|
||||||
history of deep technical contributions across different parts of the
|
history of deep technical contributions across different parts of the
|
||||||
|
Reference in New Issue
Block a user