Create a guide or template for projects to implement a maintainership process
Background
This issue is related to the Create an implementation plan to remedy gaps in Maintainership coverage epic which is a part of the larger Maintainership Working Group Epic.
Some projects have well-defined maintainership processes. See this guide for gitlab-rails frontend, backend, database maintainers for example. However, smaller or less active projects may not have a well-defined or documented maintainership process. While every project will have different needs, we think there is an opportunity to create a guide or template that projects can use to define and document their maintainership processes without becoming overly prescriptive or imposing a rigid standards.
Purpose
The purpose of this issue is to:
- Draft a general purpose template that can guide project owners through creating their own maintainership process. We should clarify the scope of this - are we talking about the process to become a maintainer only or are we also talking about code review?
- Consider creating a sample process that new projects can copy and adapt for their own use.
- Consider developing guidelines about when and how to evolve the process as a project matures.
Where can I find out more about the efforts of the Working Group?
To learn more about the latest topics being discussed by the Maintainership Working Group, please refer to any of the items below: