CipherLabs
/
besu
mirror of https://github.com/hyperledger/besu
2
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Maintainers: Remove Curators list and move current Curators to emeritus (#3885)

Browse Source 
* remove non-code maintainers section

Signed-off-by: Sally MacFarlane <sally.macfarlane@consensys.net>
pull/3930/head
Sally MacFarlane 3 years ago committed by GitHub
parent 6f85e1f83b
commit 03ee5f7e6b
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 7 additions and 31 deletions
Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL
Show Stats Download Patch File Download Diff File
  1. 38
      MAINTAINERS.md

38
MAINTAINERS.md
Unescape View File

@ -2,7 +2,7 @@
<!-- Please keep all lists sorted alphabetically by github --> <!-- Please keep all lists sorted alphabetically by github -->
## Active Code Maintainers ## Active Maintainers
<!-- besu-maintainers group has maintainer access to besu repo --> <!-- besu-maintainers group has maintainer access to besu repo -->
@ -34,15 +34,6 @@
| Usman Saleem | usmansaleem | usmansaleem | | Usman Saleem | usmansaleem | usmansaleem |
## Active Non-code Maintainers
<!-- besu-triage group has Write access to besu repo -->
| Name | Github | LFID |
| ---------------- | ---------------- | ---------------- |
| Madeline Murray | MadelineMurray | madelinemurray |
| Sajida Zouarhi | sajz | SajidaZ |
## Emeritus Maintainers ## Emeritus Maintainers
| Name | Github | LFID | | Name | Github | LFID |
@ -53,9 +44,11 @@
| Edward Evans | EdJoJob | EdJoJob | | Edward Evans | EdJoJob | EdJoJob |
| Edward Mack | edwardmack | mackcom | | Edward Mack | edwardmack | mackcom |
| Ivaylo Kirilov | iikirilov | iikirilov | | Ivaylo Kirilov | iikirilov | iikirilov |
| Madeline Murray | MadelineMurray | madelinemurray |
| Trent Mohay | rain-on | trent.mohay | | Trent Mohay | rain-on | trent.mohay |
| Rai Sur | RatanRSur | ratanraisur | | Rai Sur | RatanRSur | ratanraisur |
| Rob Dawson | rojotek | RobDawson | | Rob Dawson | rojotek | RobDawson |
| Sajida Zouarhi | sajz | SajidaZ |
| Tim Beiko | timbeiko | timbeiko | | Tim Beiko | timbeiko | timbeiko |
| Vijay Michalik | vmichalik | VijayMichalik | | Vijay Michalik | vmichalik | VijayMichalik |
@ -64,31 +57,20 @@
Besu welcomes community contribution. Besu welcomes community contribution.
Each community member may progress to become a maintainer. 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 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). - 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 ### 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. - The proposed maintainer has the sponsorship of at least one other maintainer.
- This sponsoring maintainer will create a proposal PR modifying the list of - This sponsoring maintainer will create a proposal PR modifying the list of
maintainers. (see [proposal PR template](#proposal-pr-template).) maintainers. (see [proposal PR template](#proposal-pr-template).)
@ -147,18 +129,12 @@ There is no contribution prescription delay.
```markdown ```markdown
I propose to add [maintainer github handle] as a Besu project maintainer. I propose to add [maintainer github handle] as a Besu project maintainer.
<!-- for code contributors -->
[maintainer github handle] contributed with many high quality commits: [maintainer github handle] contributed with many high quality commits:
- [list significant achievements] - [list significant achievements]
Here are [their past contributions on Besu project](https://github.com/hyperledger/besu/commits?author=[user github handle]). Here are [their past contributions on Besu project](https://github.com/hyperledger/besu/commits?author=[user github handle]).
<!-- for non-code contributors -->
[maintainer github handle] contributed with many high quality actions:
- [list significant actions]
Voting ends two weeks from today. Voting ends two weeks from today.
For more information on this process see the Becoming a Maintainer section in the MAINTAINERS.md file. For more information on this process see the Becoming a Maintainer section in the MAINTAINERS.md file.

Write Preview
Loading…
Cancel
Save