Skip to content

Add Scalability project structure

Sean McGivern requested to merge scalability-project-structure into master

Why is this change being made?

I wanted to add a 'template' of sorts for Scalability project epics. I went with the word 'structure' instead as some items (like start and due dates) are not part of the epic description, but other attributes on the epic.

I was talking with @jacobvosmaer-gitlab about our current projects in a call (brief notes in https://docs.google.com/document/d/1VSHkLzm0fn3y6Iux4xoJZQIogH6JapoxoDOYx3_2sE0/edit#), and we were talking about how valuable the exit criteria issues have been:

  1. For the Sidekiq epic, @oswaldo created them.
  2. For the Redis observability and monitoring epic, @rnienaber created them.

In both cases they were created fairly late on. Instead, we're suggesting creating them first, almost as a form of test-driven project management. This should help keep us focused on the goal, rather than on the specifics of building a particular cool thing, and it should also make the project clearer to people not intimately involved with it.

cc @gitlab-org/scalability

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 your manager.
    • 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.

For help with failing pipelines reach out in #mr-buddies in Slack

Merge request reports