Skip to content

Adds the index page for technical blueprint

Ashwin Bilgirequested to merge
abilgi/adds_technical_blueprint into main

Why is this change being made?

💡 Provide a detailed answer to the question on why this change is being proposed, in accordance with our value of Transparency.

Please add the details saying why, not just what in this section. Example: We have discussed the topic in Slack - (copy of Slack conversation). The current process is not efficient, this MR makes the description of X more clear, and helps move Y forward.

As a part of the efforts tracked in this epic:

Create the technical blueprint/north star visio... (gitlab-org/analytics-section/analytics-instrumentation&10) • Ashwin Bilgi

we as a team agreed to create a technical blueprint for the team. The technical blueprint serves as a living document that describes

  • where we are today
  • What do our systems look like today
  • what are our current gaps, challenges, opportunities
  • where do we want to be, knowing what we know today
  • a rough plan on how to get there.

This MR adds the index page for the technical blueprint. This contains the context and motivation for the analytics instrumentation team.

Related issue: https://gitlab.com/gitlab-org/analytics-section/analytics-instrumentation/proposals/-/issues/2+s

Note: The page contains a link to a handbook page that will go live once https://gitlab.com/gitlab-com/content-sites/internal-handbook/-/merge_requests/7507+s is merged

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
    • The when to get approval handbook section explains when DRI approval is required
    • The who can approve handbook section explains how to identify the DRI
    • If the MR does not require DRI approval, consider asking someone on your team, such as your manager.
    • The approver may merge the MR. If they approve but don't merge, you can merge.
  • 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 the index page for technical blueprint.
  • Adds home page for technical blueprint.
Edited by Ashwin Bilgi

Merge request reports