Update governance model around changes in maintainership (#29292)
* Update governance model around changes in maintainership Signed-off-by: stianst <stianst@gmail.com> * Update GOVERNANCE.md * Update GOVERNANCE.md Co-authored-by: Stan Silvert <ssilvert@redhat.com> --------- Signed-off-by: stianst <stianst@gmail.com> Co-authored-by: Stan Silvert <ssilvert@redhat.com>
This commit is contained in:
parent
b019cf6129
commit
ceb70778e4
1 changed files with 8 additions and 1 deletions
|
@ -72,7 +72,14 @@ For the nominee to be accepted as a maintainer at least 2/3 of existing maintain
|
|||
|
||||
### Changes in Maintainership
|
||||
|
||||
Maintainers can be removed if at least 2/3 of existing maintainers agree.
|
||||
Every 6 months (March and September) active maintainers fill in a survey covering what they have been doing as a maintainer
|
||||
for the last period, and what they are planning on focusing on in the next period. The survey is not made publicly
|
||||
available, but is shared with existing maintainers. This serves two purposes; firstly for the maintainers group to better
|
||||
understand what each maintainer is focusing on, and secondly to identify maintainers that are no longer active.
|
||||
|
||||
In the majority of cases a maintainer is removed by the maintainer stepping down themselves (by sending an email to
|
||||
keycloak-maintainers(at)googlegroups.com). However, in exceptional circumstances a maintainer can also be removed with
|
||||
2/3 of votes from existing maintainers.
|
||||
|
||||
|
||||
## Contributing Changes
|
||||
|
|
Loading…
Reference in a new issue