(DRAFT process)

Non-code Curating contributors AKA Curators have "triage" access 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 nominated by a maintainer they work with

...

And nomination confirmed by an existing non-code contributorCurator

• 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 non-code contributor combined Curator is sufficient "social proof" for membership.

Removing access

A maintainer communicates that the non-code contributor is Curator 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 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.