Skip to content

Trainee Backend Maintainer (GitLab) - [Emma Park]

Basic setup

  1. Decide which project you would like to become a maintainer of: GitLab
  2. Read the code review guidelines.
  3. Understand how to become a maintainer.
  4. Add yourself as a trainee maintainer in the team database.
  5. Mention your manager in this issue for awareness.

Working towards becoming a maintainer

This is not a checklist, but guidelines that will help you become a maintainer. Remember that there is no specific timeline on this, and that you should work together with your manager and current maintainers.

It is up to you to ensure that you are getting enough MRs to review. If you are not receiving enough MRs to advance in your training, be proactive and seek out opportunities for review. Maintainers are available to help guide you.

After each MR is merged or closed, add a discussion to this issue using this template:

### (Merge request title): (Merge request URL)

During review:
- (List anything of note, or a quick summary. "I suggested/identified/noted...")

Post-review:
- (List anything of note, or a quick summary. "I missed..." or "Merged as-is")

(@support-maintainer-username) please add feedback, and compare this review to
the average maintainer review.

Warning: For security MRs, no discussion should take place in the issue (even if using an internal note), as this might reveal security issue details. Instead, if you want to discuss the MR, you may create a discussion in the original MR, and link to it from a discussion in the trainee maintainer issue.

When you're ready to make it official

When reviews have accumulated, and recent reviews consistently fulfill maintainer responsibilities:

  1. Create a merge request updating your team member entry using one of available merge request templates proposing yourself as a maintainer for the relevant application.
  2. Follow the instructions in the merge request template
Edited by Emma Park