Update existing systems through renaming Community Relations to Developer Relations
# Tech Stack - Update Existing System
## Business/Technical System Owner or Delegate to CompletePlease do not merge before the Business Systems Analysts have reviewed and approved.
-
Rename this MR's title to [System Name] - Tech Stack - Update Existing System
-
Update data field(s) for the existing system within the 'Changes' tab of this MR. Commit update when ready. More instructions are here.
Are you changing the existing system's provisioner(s)?
-
Yes. Create an Issue to add the new provisioner(s) of the system to the appropriate Google/Slack/GitLab groups: - [Issue link]
-
No
Are you removing an existing system from the Tech Stack?
-
Yes. Be sure to complete a Tech Stack Offboarding Issue as well. -
No
Security Risk to Complete
Not required prior to merging
-
Create Existing System - TS Update Tracking Issue in StORM board: - [Tracking Issue link]
-
Once updates are finalized, sync changes with the ZenGRC System Object
/cc @gitlab-com/gl-security/security-assurance/security-risk-team
Why is this change being made?
Based on a recent decision of renaming the Community Relations to Developer Relations department, I'm creating the first draft of the MR that changes this in the handbook. See also gitlab-com/marketing&3867
What was not updated:
- Roles in job families (different process, so better not to get into a delay or conflict there yet)
- Slack channels (different MRs & issue: https://gitlab.com/gitlab-com/marketing/community-relations/team-administration/-/issues/37#note_1379603610)
- Project handles (
@gitlab-com/marketing/community-relations
)
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 Nick Veenhof