Trainee Maintainer (CI/CD Templates) - Lucas Charles

Basic setup

  1. Read the code review page in the handbook and the code review guidelines.
  2. Understand how to become a maintainer
  3. Read over our Development Guide for GitLab CI/CD Templates
  4. Create a merge request updating your team member entry adding yourself as a trainee maintainer.

Working towards becoming a maintainer

There is no checklist here, only guidelines. Remember that there is no specific timeline on this.

Your reviews should aim to cover maintainer responsibilities as well as reviewer responsibilities. Your approval means you think it is ready to merge.

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")

(Maintainer who reviewed this merge request) Please add feedback, and compare
this review to the average maintainer review.

Tip: There are tools available to assist with this task.

When you're ready to make it official

When reviews have accumulated, and recent reviews consistently fulfill maintainer responsibilities, any maintainer can take the next step. The trainee should also feel free to discuss their progress with their manager or any maintainer at any time.

  1. Create a merge request updating your team member entry proposing yourself as a maintainer.
  2. Create a merge request for CODEOWNERS, adding yourself accordingly, and ask a maintainer to review it.
  3. Keep reviewing, start merging 🤘
  4. Keep reviewing, and helping with merge requests! 🎉
  5. Important Read: If you are not currently a backend or frontend maintainer, please assign the merge requests to a maintainer who can merge on your behalf, specifying that it has already been approved by a CI/CD templates maintainer.
Edited by Lucas Charles