Update sites/handbook/source/handbook/markdown-guide/index.html.md file
Self-assessment
It's hard to specify hard requirements for becoming a maintainer, which is why the documentation consists of flexible guidelines. Nevertheless, it's still important to have a more formal list to help both a candidate and their manager to assess the "readiness" of the candidate.
-
Advanced understanding of the GitLab project as per the documentation: good feel for the project codebase, expertise in one or more domains, and deep understanding of our coding standards
-
The MRs reviewed by the candidate consistently make it through maintainer review without significant additionally required changes. -
The MRs authored by the candidate consistently make it through reviewer and maintainer review without significant required changes.
Links to Non-Trival MRs I've Reviewed
Links to Non-Trivial MRs I've Written
@gitlab-org/maintainers/frontend please chime in below with your thoughts, and approve this MR if you agree.
Once This MR is Merged
-
Create an access request for maintainer access to gitlab-org
. -
Create an access request to be added to the [at]frontend-maintainers
slack group -
Let a maintainer add you to gitlab-org/maintainers/frontend
-
Announce it everywhere -
Keep reviewing, start merging 🤘 😎 🤘