diff --git a/MAINTAINERS.md b/MAINTAINERS.md index f4605d55d6..5603cfa8e1 100644 --- a/MAINTAINERS.md +++ b/MAINTAINERS.md @@ -2,7 +2,7 @@ -## Active Code Maintainers +## Active Maintainers @@ -34,15 +34,6 @@ | Usman Saleem | usmansaleem | usmansaleem | -## Active Non-code Maintainers - - - -| Name | Github | LFID | -| ---------------- | ---------------- | ---------------- | -| Madeline Murray | MadelineMurray | madelinemurray | -| Sajida Zouarhi | sajz | SajidaZ | - ## Emeritus Maintainers | Name | Github | LFID | @@ -53,9 +44,11 @@ | Edward Evans | EdJoJob | EdJoJob | | Edward Mack | edwardmack | mackcom | | Ivaylo Kirilov | iikirilov | iikirilov | +| Madeline Murray | MadelineMurray | madelinemurray | | Trent Mohay | rain-on | trent.mohay | | Rai Sur | RatanRSur | ratanraisur | | Rob Dawson | rojotek | RobDawson | +| Sajida Zouarhi | sajz | SajidaZ | | Tim Beiko | timbeiko | timbeiko | | Vijay Michalik | vmichalik | VijayMichalik | @@ -64,31 +57,20 @@ Besu welcomes community contribution. Each community member may progress to become a maintainer. -There are two ways to become a maintainer: +How to become a maintainer: - Contribute significantly to the code in this repository. -- Contribute significantly to the doc or being recognized as great help by other contributors. -### Code maintainers contribution requirement +### Maintainers contribution requirement -The requirement to be able to be proposed as a code maintainer is: +The requirement to be able to be proposed as a maintainer is: - 5 significant changes on code have been authored in this repos by the proposed maintainer and accepted (merged PRs). -### Other maintainers contribution requirement - -The requirements to be able to be proposed as a non-code maintainer are: - -- 5 significant changes on documentation have been authored in this repos by the proposed maintainer and accepted (merged pull-requests (PR), excluding hyperledger/besu-doc repos contribution). -- or 5 significant support answers on official public channels that solved the user issue. -- or being recognised as a fully involved and significant help for issue triage and assignment or roadmap planning effort and code review by other maintainers. - There is no number defined for these criteria as the vote will decide if the criteria are valid. - ### Maintainers approval process -For both types of maintainers, the following steps must occur for a contributor to be "upgraded" as a maintainer: +The following steps must occur for a contributor to be "upgraded" as a maintainer: -- The proposed maintainer meets the expectations for the targeted maintainership type (see [code](#code-maintainers-contribution-requirement) and [non code](#other-maintainers-contribution-requirement) types.) - The proposed maintainer has the sponsorship of at least one other maintainer. - This sponsoring maintainer will create a proposal PR modifying the list of maintainers. (see [proposal PR template](#proposal-pr-template).) @@ -147,18 +129,12 @@ There is no contribution prescription delay. ```markdown I propose to add [maintainer github handle] as a Besu project maintainer. - [maintainer github handle] contributed with many high quality commits: - [list significant achievements] Here are [their past contributions on Besu project](https://github.com/hyperledger/besu/commits?author=[user github handle]). - -[maintainer github handle] contributed with many high quality actions: - -- [list significant actions] - Voting ends two weeks from today. For more information on this process see the Becoming a Maintainer section in the MAINTAINERS.md file.