FY21 Q2 OKR - Secure Frontend: One or two members in Maintainer Trainee program
Goals:
- Increase exposure to the thought process of a maintainer, therefore shifting left style guide and review principals.
- Eventually increase capacity of maintainer support within Secure FE in the future. We currently have a 1:5 ratio.
- Key Result: One or two members of Secure Frontend to be trainee maintainers in Q2.
- Key Result: Feedback on the program and expressed interest or disinterest in continuing down the path of becoming a maintainer.
- Key Result: Retrospective with the Secure Frontend team and possibly #frontend.
Actions to achieve this goal:
- Gauge interest within the team and identify 1 or 2 individuals to become trainees.
- These individuals will go through the https://about.gitlab.com/handbook/engineering/workflow/code-review/#trainee-maintainer as well as shadow current maintainers during reviews.
References:
Outcomes
2020-06-05 Update: We have one engineer in the maintainer trainee program.
2020-07-21 Update: Dave Pisek's is adding more review examples to his maintainer issue at #5754 (closed). Goal to be more definitive on desire to be a maintainer by 2020-08-22.
2020-07-30 Update: Paul Gascou-Vaillancourt has submitted his MR to become a maintainer for the GitLab UI project.
Retrospective
Feature work and outside influences (COVID, especially) deemphasized this goal within the team this quarter. Dave and I discussed this several times and agreed to push it out to August for reconsideration. There's an interesting maintainer retro issue created in the last couple days that cites other reasons similar to that Dave and I have discussed. #8504 (closed)
Paul and I have discussed his role on GitLab UI and agreed it makes sense for him to be a maintainer. He's an active developer on that project and very involved. He created his maintainer MR this week.
I want to extend this goal into the early part of Q3. It will be beneficial to get their feedback and share with the rest of the team.