Skip to content

Draft: Add DEI section to strategy

Daniel Murphy requested to merge add-dei-growth-strategy into master

Why is this change being made?

This MR adds the new Diversity, Equity and Inclusion (DEI) strategies for Developer Relations into the Open Source Growth Strategy.

This adds a 5th key area in support of the dual-flywheel strategy. The new area, Foster Diversity, Equity and Inclusion, would branch off of Scale the Community and sit alongside Improve Contribution Velocity and Increase Contribution Value. The new area, Foster Diversity, Equity and Inclusion would lead to Contributor & Contribution Increase.

An updated mermaid diagram is needed to reflect this change.

Additionally, a new contributorgrowth label is needed for marking issues relevant to this value: i.e. contributorgrowth::DEI

Related issue: gitlab-org/developer-relations/contributor-success/team-task#286

💡 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.

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
Edited by Daniel Murphy

Merge request reports