Trainee BE maintainer (gitlab-pages) - Naman Gala
Basic setup
-
Read the code review page in the handbook and the code review guidelines. -
Understand how to become a maintainer -
Ask your manager to set up a check in on this issue every six weeks or so. -
Optional: Consider finding a mentor to help you become a maintainer.
Working towards becoming a maintainer
The process to become a maintainer at GitLab is defined in the handbook, and it is the baseline for this process. One thing that is expected is a high number of reviews, however; the rate of change of the GitLab Pages compared to the GitLab Rails project is too little.
To work around that problem, one must be comfortable in the following areas of the codebase:
Main areas:
-
Namespace/project resolution -
ZIP serving and the virtual file system -
Authentication
Smaller areas:
-
Redirects -
Artifacts proxying -
Handling of TLS certificates -
Rate-limiting -
Metrics and monitoring
To achieve this, you should try to make relevant contributions in all main areas and 2-3 smaller areas mentioned above so that you have a better understanding of the functionality. A relevant contribution may be a bug fix, a performance improvement, a new feature, or a significant refactoring.
When you're ready to make it official
You are probably ready to become a maintainer when these statements feel true:
-
The MRs you have reviewed consistently make it through maintainer review without significant additionally required changes
-
The MRs you have created consistently make it through reviewer and maintainer review without significant required changes
-
You feel comfortable working through operational tasks
-
open an MR promoting you to maintainer and tag the existing maintainers.