(DRAFT process)
Non-code contributors Curators have "triage" access to the Besu GitHub repository which means they can:
- curate, manage, label and otherwise categorize bugs and other Github issues for Besu,
- collaborate with the existing maintainers to help coordinate the development and roadmap planning of Besu
...
The process for becoming a non-code contributor Curator is separate from the process for becoming a Besu maintainer.
Access is controlled by this GitHub group.
Granting access
PMs that need access are vouched for nominated by a maintainer they work with (
- post a message to the besu-contributors Discord channel introducing them
...
- and their role
And nomination confirmed by an existing Curator
- reply to the nomination/introduction post in the besu-contributors Discord channel
- tag or direct message to a maintainer of the GitHub group to add the new member, and then access is granted
. There is no voting or other approval. The The combined reputation of the nominating maintainer and confirming Curator is sufficient "social proof" for membership.
Removing access
A maintainer communicates (that the Curator is no longer in the role needing access.
- post a message to the besu-contributors Discord channel
) that the non-code contributor is no longer in the role needing access. Access is removed after confirming (or after reasonable effort to do so) with the non-code contributor being removed.Curator being removed.
- tag or direct message to a maintainer of the GitHub group, and then access is removed
Historical record
The membership of the besu-triage group is the record of current non-code maintainersCurators. No other record is kept.