Skip to content

Remove /direction/maturity

Javier Garcia requested to merge jgarc-master-patch-3a51 into master

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.

Production Review app
https://about.gitlab.com/direction/maturity/ This page will get deleted, redirected to /direction/

https://gitlab.slack.com/archives/C03EHG8DP3N/p1713976903849749

Changes to YAML and discrepancies here lead to issues with Sales.

Change requested towards moving this page to an internal handbook page. A stopgap solution is to remove the chart for now and introduce this as an internal handbook link at a later date.

Rationale

  1. Deleted the entire page, At first, we found that the build process breaks... this made me consider just removing the chart. If we don't want to redirect to a new page, we should remove the legend/chart for now. Currently, this MR is deleting the entire page
  2. This page is linked across www and the handbook, meaning we would also need to set up a redirect for this. If we leave the page intact and remove the chart/legend, we wouldn't need to do this.

NOTE: I anticipate this change to be contested. This seems like something that I can see sparking conversation in issues and on Slack. We should prepare some communication about that when those conversations come up.

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

Closes: gitlab-com/marketing/digital-experience/buyer-experience#3674 (closed)

Edited by Javier Garcia

Merge request reports