You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

(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 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 non-code contributor

  • 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 reputation of the nominating maintainer and confirming non-code contributor combined is sufficient "social proof" for membership.

Removing access

A maintainer communicates that the non-code contributor is no longer in the role needing access.

  • post a message to the besu-contributors Discord channel

Access is removed after confirming (or after reasonable effort to do so) with the non-code contributor 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 maintainers. No other record is kept.

  • No labels