Add a note regarding groups with multiple owners to namesquatting workflow
Why is this change being made?
For situation where there are several owners to a group, we need to contact each owners individually. See slack thread :
Ségolène Delaby Bouly: [Name squatting question] For group with several owners, should we contact all of them in one ticket or only one owner or multiple tickets?
Ségolène Delaby Bouly: I am going for multiple tickets so I not share emails addresses
Cynthia 'Arty' Ng: you know, I think we used to have 1 ticket for multiple owners, but that's a good point. Could you update the handbook? Feel free to set me as reviewer.
Also, I usually limit it to the earliest 3-5 owners because some groups had a lot.
Author Checklist
-
Provided a concise title for this Merge Request (MR) -
Added a description to this MR explaining the reasons for the proposed change, per say why, not just what - Copy/paste the Slack conversation to document it for later, or upload screenshots. Verify that no confidential data is added, and the content is SAFE
-
Assign reviewers for this MR to the correct Directly Responsible Individual/s (DRI) - If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the
Maintained by
section on the page being edited - If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in #mr-buddies
- The when to get approval handbook section explains the workflow in more detail
- If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the
-
If the changes affect team members, or warrant an announcement in another way, please consider posting an update in #whats-happening-at-gitlab linking to this MR - If this is a change that directly impacts the majority of global team members, it should be a candidate for #company-fyi. Please work with internal communications and check the handbook for examples.
Edited by Segolene Bouly