Skip to content

Add section to Fulfillment Guide about storage enforcement notifications

Alex Martin requested to merge alex_martin-master-patch-74789 into master

Objective: document all the notifications we have going to customers about namespace / project enforcement

Asks:

  • Please review changes and verify for accuracy especially where I have (needs to be verified)
  • I am going to add in some example images in a future MR. I have most of them but still lacking what CLI notifications might look like for group namespace storage enforcement, so if you have a link for me that would be great.

PS you might be wondering why I am documenting this here. I discussed with Omar and he recommended preferred documented order:

  • docs.gitlab.com - transparent to the customer, easily searchable, very official.
  • fulfillment guide - public, anyone can find it including Google, kinda official, but messy
  • internal handbook - if it really can’t be public
  • an issue

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.

Edited by Alex Martin

Merge request reports

Loading