Make Vladimir Shushlin a backend maintainer for gitlab rails
Manager Justification
It's hard to specify hard requirements for becoming a maintainer, which is why the documentation consists of flexible guidelines. Reviewers are encouraged to think of their eligibility for maintainership in the terms of "I could be ready at any time to be a maintainer as long as my work as an author and reviewer is consistent with other maintainers".
-
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.
@vshushlin has joined GitLab 4 years ago, so far:
- authored almost 250 MR's to the gitlab rails project
- approved 225 merged MR's in the gitlab rails projest
- Being a maintainer for GitLab Pages(230 approved MR's merged) and Release-cli
- Contributed as author and/or reviewer to other projects, including Gitaly, Charts, Omnibus, Gdk...
-
Authored 40+ and approved 16 (should actually be more
🤔 ) security MR's.
About 4 months ago I switched to an Acting EM role on the grouprelease and we felt like it was better to set aside maintainership even though @vshushlin, @nicolewilliams (manager at the time) and @smcgivern (maintainership mentor) felt like I was more than ready.
And I didn't pursue backend maintainership before that because the workload of the pages maintainer was enough.
Now on the new Re-figure
team we only have 1 BE maintainer(@shinya.maeda), and we look for more to make team more efficient. So it's probably the right time to resurrect this.
Before Merging (Manager Tasks)
-
Close any relevant trainee maintainer issues with a comment indicating that this merge request is being created, as (they are no longer required to become a maintainer). -
Mention the maintainers from the given specialty with the template below. -
Leave this merge request open for 1 week, to give the maintainers time to provide feedback. -
Ensure we have at least 2 approvals from existing maintainers.
Template call to action
SPECIALITY Maintainers, please review this proposal to make TRAINEE maintainer of PROJECT.
* If you have blocking feedback adhering [to the documentation](https://about.gitlab.com/handbook/engineering/workflow/code-review/#how-to-become-a-project-maintainer) please share it with me via Slack.
* If you are in agreement please approve or give a 👍 on the MR
After 1 week, if there is no blocking feedback and at least 2 approvals, I will merge this MR.
Once This MR is Merged
-
Join the #backend_maintainers
Slack channel -
Ask the maintainers in your group to invite you to any maintainer-specific meeting if one exists. -
Let a maintainer add you to @gitlab-org/maintainers/rails-backend
-
Announce it everywhere -
Keep reviewing, start merging 🤘 😎 🤘