Skip to content

Updates the Frontend Observability working group

Sam Beckham requested to merge getting-the-band-back-together into master

Why is this change being made?

To kick-start the Frontend Observability Working Group back into action!

There's been a lot of movement on the sentry front lately so now is a good time to start this working group back up. This MR updates the member list, but since it's been so long, I'd like to ask y'all to take a look and let me know if you still want to be a part of this group, and if I have all your details correct.

Once we've got the band back together we can look at the rest of this page and the associated epic (gitlab-org&6584 (closed)) to make sure everything is up to date. Then we can get the meetings scheduled and get to the fun part of this effort!

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.

Merge request reports