Skip to content

Update Product Development flow to mention Legal Compliance consideration

Sarah McCreesh requested to merge smccreesh-master-patch-52240 into master

Why is this change being made?

Closes https://gitlab.com/gitlab-com/www-gitlab-com/-/issues/13573

This MR is being created to introduce a reference to the new **legal risk checklist **process, which is being added to the product development flow, in order to aid PMs with identifying legal risks that can arise during the development process.

Whilst the legal risk checklist will live in the internal handbook, as its publication within the public-facing handbook could prejudice GitLab in future/related legal proceedings, this MR will provide a helpful link to the relevant internal handbook content, in order to promote greater accessibility for team members involved in identifying risk.

Note that at the time of MR submission, the internal handbook content for the legal risk checklist is not yet live, so the link included will not resolve yet. It is intended that this will be updated before the submission of this MR for approval, following feedback from Product and Product Ops team members.

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.
  • 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
  • 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 Farnoosh Seifoddini

Merge request reports