Skip to content

Adds design documents from first half of 2023

Why is this change being made?

Move Architecture Blueprints to Public Handbook (#279 - closed)

This MR adds design documents from the first half of 2023 from the gitlab project to the handbook project with proper metadata (leaves out one document that has open MRs. See table on the migration issue). See this section of the migration issue for info on how the migration was done.

Excerpt from design docs table. These documents are in this MR.

Design document folder Creation Date Migrated? Redirect?
clickhouse_ingestion_pipeline 2023-01-10 🚧
ci_builds_runner_fleet_metrics 2023-01-25 🚧
gitaly_plugins 2023-02-01 🚧
clickhouse_usage 2023-02-02 🚧
clickhouse_read_abstraction_layer 2023-02-23 🚧
model_experiments_and_registry 2023-03-04 🚧
gitlab_events_platform 2023-03-06 🚧
runner_admission_controller 2023-03-07 🚧
permissions 2023-03-10 🚧
gitlab_ci_events 2023-03-15 🚧
object_pools 2023-03-30 🚧
organization 2023-04-05 🚧
gitlab_ml_experiments 2023-04-13 🚧
repository_backups 2023-04-26 🚧
ci_pipeline_processing 2023-05-15 🚧
git_data_offloading 2023-05-19 🚧
gitaly_adaptive_concurrency_limit 2023-05-30 🚧
gitaly_transaction_management 2023-05-30 🚧 Migration MR until here

Author and Reviewer Checklist

Please verify the check list and ensure to tick them off before the MR is merged.

  • 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
  • For transparency, share this MR with the audience that will be impacted.
    • Team: For changes that affect your direct team, share in your group Slack channel
    • Department: If the update affects your department, share the MR in your department Slack channel
    • Division: If the update affects your division, share the MR in your division Slack channel
    • Company: If the update affects all (or the majority of) GitLab team members, post an update in #whats-happening-at-gitlab linking to this MR

Commits

  • Adds design documents from first half of 2023

Edited by Marc Saleiko

Merge request reports

Loading