## Overview Approximately 12 months ago, 3 of the 5 [gitlab-shell maintainers](https://gitlab.com/groups/gitlab-org/maintainers/gitlab-shell/-/group_members?with_inherited_permissions=exclude) worked in the team responsible for the project (Source Code BE) with 3 maintainers now being reduced to 1 maintainer. ## Proposal I believe it's critical for gitlab-shell to have maintainers who actively work in and responsible for the project and so I'm proposing we add at minimum 1 and ideally 2 additional gitlab-shell maintainers from the Source Code BE team. To achieve the goal to become a Gitlab Shell Maintainer here are the steps to follow. * [ ] Open an child item under this issue to apply for Maintainer status. [Example](https://gitlab.com/gitlab-org/gitlab-shell/-/issues/768) * [ ] Begin reviewing [Open MR's](https://gitlab.com/gitlab-org/gitlab-shell/-/merge_requests/?label_name%5B%5D=automation%3Abot-authored) and provide updates in the Maintainer issue. * [ ] Gather feedback on the issue from an existing GitLab Shell Maintainer on the review checkpoints. * [ ] Start contributing to Gitlab Shell project. There are no strict requirements to become a maintainer for GitLab-Shell. Based on the process followed previously, to become a maintainer, we can ensure to: * Contribute at least 3 merge requests * Review at least 3 merge requests * Review the codebase to be familiar with it