Background
Currently the process for becoming a besu-docs maintainer mirrors the process for becoming a besu maintainer, but based on besu-docs contributions rather than besu code contributions.
However this prevents besu maintainers from directly contributing to the besu-docs repository.
The besu-docs repo has CI steps to check formatting, grammar, validity of internal and external HTTP links.
All changes also require separate approval.
Proposal
Since we trust besu maintainers to make changes to the code, this proposal is to also trust those individuals to make changes to the related docs.
Proposal:
- have all current besu maintainers become besu-docs maintainers
- existing besu-docs maintainers remain besu-docs maintainers
- when someone becomes a besu maintainer, they also become a besu-docs maintainer
- still keep the separate process for someone to become a besu-docs maintainer without first becoming a besu maintainer.