Skip to content

Updating product principles with new examples

Veethika Mishra requested to merge v_mishra-master-patch-92432 into master

Why is this change being made?

What does this MR do?

As stated in our product principles, at GitLab we put developer first and avoid instance level features so that maximum number of our users could use it.

Recently in ~"group::continuous integration" we ran into an issue where enabling a feature on the project level first to(taking a developer first approach) backfired as it resulted in extreme infrastructural load for our on-prem users and the lack of disk space eventually stalled the application performance as a whole.

To avoid such situations in future, this MR adds an exception case example to the section Avoid instance-wide features and elaborates on the sensible default terminology.

Author Checklist

  • Provided a concise title for the MR
  • Added a description to this MR explaining the reasons for the proposed change, per say-why-not-just-what
  • Assign this change to the correct 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 in 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 relate to any part of the project other than updates to content and/or data files please make sure to ping @gl-static-site-editor in a comment for a review and merge. For example changes to .gitlab-ci.yml, JavaScript/CSS/Ruby code or the layout files. (this requirement has been removed pending identification of a new DRI for the handbook)

Merge request reports