Update foundations standup to deduplicate status updates

Why is this change being made?

Context

We have several places we look at priorities and status updates:

• Weekly geekbot standup in #g_infra_foundations_social asking for weekly priorities, what was accomplished, and if there are any blockers
• Weekly geekbot standup in #g_infra_foundations_social to note weekly wins and a general "how did the week go".
• Daily geekbot standup #sre_standups to note what work is in progress, what was completed, and if there are any blockers/help needed.
• Weekly sync status updates noting "ongoing work"
• 1:1 structure noting weekly priorities

Weekly priorities are duplicated in a few different places so it makes sense to consolidate. Also, geekbot participation is not consistent throughout the team, so it is not very useful.

Overview

After discussions with the team about deduplicating the posting of weekly priorities, I came to the following takeaways:

• It’s helpful to track wins and possibly priorities in 1:1 docs for performance review/self evals.
• No one seems to have a strong attachment to the weekly standups that we run. (I see this reflected in that participation is not consistent and can often be low).

What I need:

• A place to see what everyone’s priorities are. (After reflecting on this in our discussions in this MR I realize I don't need this as I trust what you are spending your time on and can always ask if I need clarity.) This makes sense to keep in the team sync. Each team member can decide if they would like to keep this also in their 1:1s for career development reference.

What I believe is helpful for the team:

• A place to have insight on what everyone is working on day to day. This provides openings for discussion, help, and visibility around interrupt work. The #sre_standup channel fulfills this need.

Proposal

This MR proposes using the #sre_standup channel moving forward and removing the weekly standups from the #g_infra_foundations_social channel to achieve the notes above.

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
  • 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
    • For high-priority company-wide announcements work with the internal communications team to post the update in #company-fyi and align on a plan to circulate in additional channels like the "While You Were Iterating" Newsletter

---