Skip to content

Fix stripe broken link in the Values handbook page

Why is this change being made?

This MR fixes a broken link pointing to quick guide to Stripe's culture in the Gitlab's Values page

According to Internet archive wayback machine, starting from 2020, this link has redirected the traffic to https://stripe.com/jobs/culture which lists the Stripe's operating principles.

Right now, the link just returns an HTTP 404 Not found error.

One way to solve this would have been to change the target link. However, there are two issues with that:

  1. The new page is titled "Operating principles" and not the old "Quick guide to Stripe's culture".
  2. Among the principles, there is no longer "Global optimization", which is what this link was for, to mention where it came from.

Proposal

As the link is broken, and the actual equivalent target page doesn't mention the "Global Optimization" value. I see these options:

  • A. Remove the link and the mention of that "quick guide to Stripe's culture" as well.
  • B. Remove the link and mention that in the past, Stripe's culture had this value documented.
  • C. Change the link to the most recent archive.org version, which shows the expected information.

In this MR, I suggest option A, since IMHO, it would cause more confusion to follow archived pages or try to understand why this value is not mentioned anymore.

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

Merge request reports