(DRAFT process)
Non-code contributors have "triage" access which means they can:
- 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
This means they have the ability to label and close GitHub issues, helping to keep the project tidy.
This role tends to be held by Product Managers (PMs). All are currently employed by ConsenSys.
The process for becoming a non-code contributor 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 by a maintainer they work with (post a message to the besu-contributors Discord channel introducing them), and then access is granted. There is no voting or other approval. The reputation of the maintainer is sufficient "social proof" for membership.
Removing access
A maintainer communicates (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.
Historical record
The membership of the besu-triage group is the record of current non-code maintainers. No other record is kept.