Skip to content

Dev Advocacy job family update: URLs and name changes, part 2

Michael Friedrich requested to merge dev-advocacy-renames-part-2 into main

Why is this change being made?

💡 Provide a detailed answer to the question on why this change is being proposed, in accordance with our value of Transparency.

CHANGEME - add the details saying why, not just what.

The Developer Advocacy job family required more fixes in the handbook, avoiding redirects, wrong terms and broken URLs.

  • More Evangelism term renaming, URL fixes
  • s,/handbook/marketing/developer-relations/developer-evangelism/,/handbook/marketing/developer-relations/developer-advocacy/,g
  • s,gitlab.com/gitlab-com/marketing/community-relations/dev-evangelism,gitlab.com/gitlab-com/marketing/developer-relations/developer-advocacy,g
  • s,gitlab-com/marketing/community-relations/dev-evangelism/meta,gitlab-com/marketing/developer-relations/developer-advocacy/developer-advocacy-meta,g
  • s,gitlab-com/marketing/developer-relations/dev-evangelism/,gitlab-com/marketing/developer-relations/developer-advocacy/,g
  • s,gitlab-com/marketing/developer-relations/dev-evangelism/de-tmm-meta,gitlab-com/marketing/developer-relations/developer-advocacy/developer-advocacy-meta,g

Relates to https://gitlab.com/gitlab-com/marketing/developer-relations/developer-advocacy/developer-advocacy-meta/-/issues/389

Author and Reviewer Checklist

Please verify the check list and ensure to tick them off before the MR is merged.

  • 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
  • For transparency, share this MR with the audience that will be impacted.
    • Team: For changes that affect your direct team, share in your group Slack channel
    • Department: If the update affects your department, share the MR in your department Slack channel
    • Company: If the update affects all (or the majority of) GitLab team members, post an update in #whats-happening-at-gitlab linking to this MR

Merge request reports