Create members groups reflecting gitlab organizational groups to facilitate communication
Problem
In GitLab day-to-day working we frequently need to communicate with other groups/people we don't know. This is might be a challenge when you don't previously know some one in the group you need to communicate with. It's usual to open the handbook to see who's in the group you need to mention, get a name/handler to then mention (@handler
) in an issues/merge requests/epics/etc.
On the same topic, currently it's hard to associate Gitlab Groups (groups os people/teams) as CODEOWNERS, as we don't have a standard way to create these groups.
Some groups simplified that by manually creating GitLab groups with their members to centralize the mention to the group in a single handler, like @gitlab-org/manage/import/backend
or @gitlab-org/manage/engineering-managers
, but this is not standardized.
Proposed solution
Would be nice if we had a normalized group structure reflecting GitLab organizational groups. This way, for instance, if someone need to ping a security counter part on the access team we could intuitively use something like: @gitlab-org/manage/access/security
, which is following the format: @gitlab/stage/group/subgroup
.
I imagine we could use some automation to create these groups from the team.yml
So I envision something like:
-
@gitlab-org/manage/import/backend
-> backend engineers ofmanage/import
group -
@gitlab-org/manage/import/frontend
-> frontend engineers ofmanage/import
group -
@gitlab-org/manage/import/security
-> security counter part ofmanage/import
group -
@gitlab-org/manage/import/ux
-> ux counter part ofmanage/import
group -
@gitlab-org/manage/import/set
-> software engineer in test ofmanage/import
group -
@gitlab-org/manage/import/em
-> engineer manager ofmanage/import
group -
@gitlab-org/manage/import/pm
-> product manager ofmanage/import
group
Maybe we could even create handlers to a more broad set of people from the same stage: (follow-up?)
-
@gitlab-org/manage/em
-> all engineer managers ofmanage
stage -
@gitlab-org/manage/pm
-> all product managers ofmanage
stage
SPIKE
A discussion about how to implement the solution can be found in the SPIKE: gitlab-org/quality/triage-ops!2212 (comment 1387806603)