New trainee maintainers for gitlab-shell
Much like this equivalent issue in gitlab-workhorse: gitlab-workhorse#209 (closed)
Currently, the list of gitlab-shell maintainers is:
So at first glance, it's much healthier than gitlab-workhorse.
However.
We're currently in the middle of an effort to completely rewrite gitlab-shell in Go: &706 (closed) . Of the maintainers above, only @ashmckenzie and I have significant Go expertise.
So, we need to think about what maintainership will look like once that's done, and make sure we aren't accidentally creating a small bus factor.
The way we're conducting the rewrite - gradually, over many releases - naturally means that a number of different people are involved in it already. I honestly think we can just follow @smcgivern's traintainer process with people who are working on gitlab-shell, and get them to review each other's reimplementations of the existing functionality. I know @reprazent and @igor.drozdov already did this for one issue, for instance.
Perhaps by reviewing the new go code, some of the existing maintainers will feel comfortable remaining maintainers once it's done, or perhaps it will be reduced to myself + 2-3 others. I'm happy with either outcome. I wouldn't be happy with gitlab-shell maintainership ending up as being just me and @ashmckenzie !
People involved with the rewrite so far:
- @patrickbajao (already volunteered for gitlab-workhorse!)
- @jacobvosmaer-gitlab (already quite busy! Peripheral involvement by moving the hooks to gitaly)
- @reprazent
- @igor.drozdov
- @ashmckenzie (already a maintainer)
As in the workhorse issue, I'd suggest anyone interested in finishing up a gitlab-shell maintainer should chat about it in their regular EM 1:1, then create an issue with this template. We can continue from there.
Now to create a similar issue in gitlab-pages ;)