Onboard more team members
I am listed as the only codeowner currently. We should onboard more team members:
Use teams rather than individuals as owners, to make it self updating over time and resilient to people taking time off
Broken out of gitlab#355433 (closed)
We can follow this guideline: https://about.gitlab.com/handbook/engineering/workflow/code-review/#maintainership-process-for-smaller-projects
Projects may adopt these guidelines for maintainership to help grow maintainers in projects where there are not enough maintainers.
-
All team members should consult the engineering development roles and become a reviewer or maintainer. -
@alipniagov
-
@rzwambag
-
@nmilojevic1
-
-
Enable Danger Review using simple_roulette within the project to identify MR reviewers. -
Create an issue template for maintainer trainees. A lightweight template is provided. -
Reduce the number of Merge Request reviews required to be considered a maintainer. - I think this is something we can compromise on easily, so checking this as done.
-
Count work on the project itself as progress for maintainership. -
Require a maintainer mentor to help speed up the process. -
@mkaeppler
can be the DRI for this.
-
-
Add instructions on how to become a project maintainer to the project README. -
Curate some practice MRs based on past reviews. Create copies of the MRs in a closed state and provide the links in the project maintainership process. -
Consider creating project-specific development guidelines if they don't already exist for the project.
Edited by Matthias Käppler