mirror of
https://github.com/vacp2p/linea-besu.git
synced 2026-01-08 20:47:59 -05:00
111a31a039
I propose adding Edward Mack from Chainsafe Systems as a maintainer for Besu. Edward has been instrumental to adding the support for Ethereum Classic and their two testnets Kotti and Mordor. Since Classic support is not strategic to ConsenSys or Web3Labs it is safe to say that without his contribution and continued involvement Ethereum Classic support would not have happened. Because Ethereum Classic has some ambitious changes slated for the next year promoting Edward to Maintainer will further secure future support for it in Hyperledger Besu. Voting ends two weeks from today, 2am UTC on 2019-12-10 https://www.timeanddate.com/countdown/to?iso=20191210T02&p0=1440 For more information on this process see the Becoming a Maintainer section in the MAINTAINERS.md file. Signed-off-by: Danno Ferrin <danno.ferrin@gmail.com> Signed-off-by: Edward Evans <edjojob@gmail.com>
4.2 KiB
4.2 KiB
Maintainers
Active Maintainers
| Name | Github | LFID |
|---|---|---|
| Abdel Bakhta | abdelhamidbakhta | abdelhamidbakhta |
| Adrian Sutton | ajsutton | ajsutton |
| Byron Gravenorst | bgravenorst | bgravenorst |
| Chris Hare | CjHare | cjhare |
| Edward Evans | EdJoJob | EdJoJob |
| Edward Mack | edwardmack | mackcom |
| Ivaylo Kirilov | iikirilov | iikirilov |
| Jason Frame | jframe | jframe |
| Joshua Fernandes | joshuafernandes | joshuafernandes |
| Lucas Saldanha | lucassaldanha | lucassaldanha |
| Sally MacFarlane | macfarla | macfarla |
| Madeline Murray | MadelineMurray | madelinemurray |
| Mark Terry | mark-terry | m.terry |
| Meredith Baxter | mbaxter | mbaxter |
| Nicolas Massart | NicolasMassart | NicolasMassart |
| Trent Mohay | rain-on | trent.mohay |
| Rai Sur | RatanRSur | ratanraisur |
| Rob Dawson | rojotek | RobDawson |
| Danno Ferrin | shemnon | shemnon |
| Tim Beiko | timbeiko | timbeiko |
| Usman Saleem | usmansaleem | usmansaleem |
Emeritus Maintainers
None.
Becoming a Maintainer
Besu welcomes community contribution. Community members may progress to become a maintainer. To become a maintainer the following steps occur, roughly in order.
- 5 significant changes have been authored by the proposed maintainer and accepted.
- The proposed maintainer has the sponsorship of at least one other maintainer.
- This sponsoring maintainer will create a PR modifying the list of maintainers.
- The proposed maintainer accepts the nomination and expresses a willingness to be a long-term (more than 6 month) committer.
- This would be a comment in the above PR.
- This PR will be communicated in all appropriate communication channels. It should be mentioned in any maintainer/community call. It should also be posted to the appropriate mailing list or chat channels if they exist.
- Approval by at least 3 current maintainers within two weeks of the proposal or
an absolute majority of current maintainers.
- These votes will be recorded in the PR modifying the list of maintainers.
- No veto by another maintainer within two weeks of proposal are recorded.
- All vetoes must be accompanied by a public explanation as a comment in the PR for adding this maintainer
- The explanation of the veto must be reasonable.
- A veto can be retracted, in that case the approval/veto timeframe is reset.
- It is bad form to veto, retract, and veto again.
- The proposed maintainer becomes a maintainer
- Either two weeks have passed since the third approval,
- Or an absolute majority of maintainers approve.
- In either case, no maintainer presents a veto.
Removing Maintainers
Being a maintainer is not a status symbol or a title to be maintained indefinitely. It will occasionally be necessary and appropriate to move a maintainer to emeritus status. This can occur in the following situations:
- Resignation of a maintainer.
- Violation of the Code of Conduct warranting removal.
- Inactivity.
- A general measure of inactivity will be no commits or code review comments for one reporting quarter, although this will not be strictly enforced if the maintainer expresses a reasonable intent to continue contributing.
- Reasonable exceptions to inactivity will be granted for known long term leave such as parental leave and medical leave.
- Other unspecified circumstances.
Like adding a maintainer the record and governance process for moving a maintainer to emeritus status is recorded in the github PR making that change.
Returning to active status from emeritus status uses the same steps as adding a new maintainer. Note that the emeritus maintainer already has the 5 required significant changes as there is no contribution time horizon for those.