Project ownership: ~team::Scalability ?
This is something of a shower thought. Workhorse is nominally owned by devopscreate , and by implication, groupsource code: https://about.gitlab.com/handbook/product/categories/#other-functionality-in-create-stage - but unlike gitlab-shell, it's not a natural fit as a lot of what workhorse does is actually owned by other groups. It has to sit somewhere, though.
However, there is one unifying characteristic for everything workhorse does, summarized as:
Handles slow HTTP requests for GitLab
Since we now have ~"team::Scalability", it makes me wonder if this is a more natural fit for an owner of this project. I don't envision changing maintainers or anything - it's more about ensuring that there's a good DRI for things that affect workhorse as a whole, so prioritisation works smoothly.
When we're asking "should this slow operation be moved from gitlab
/ implemented in workhorse
", it feels-like ~"team::Scalability" is a natural fit to answer. When someone is making a case for an architectural change to workhorse, or to change fundamentals of its operation, it also seems like a reasonable fit.
Do you have any thoughts @jacobvosmaer-gitlab @nolith @ashmckenzie @steveazz @patrickbajao (workhorse (train|main)tainers)? @danielgruesso (product)? @m_gill @rnienaber (EMs)?