Move CH WG to past working groups.

Why is this change being made?

We’ll be winding down the ClickHouse Working Group, with the last WG meeting scheduled for this Thursday. In the last year we’ve made major progress introducing ClickHouse to GitLab’s architecture to support GitLab’s analytics and monitoring features. We have:

• Enabled usage of ClickHouse Cloud with GitLab, including security and legal approval for storing customer RED data and production readiness reviews.
• Consolidated our multiple ClickHouse hosting setups into ClickHouse Cloud, reducing operational load for our teams and improving reliability. Released multiple features that would not have been possible without ClickHouse’s capabilities.
• Fixed features such as Contributor Analytics which were no longer performant on GitLab.com.
• Developed documentation and tooling for using ClickHouse in GitLab’s development process.

We’ve decided that because of the overlap with the recently created Product Usage Data Architecture Working Group, it makes sense to wind down the ClickHouse group, and roll those concerns into that group’s work defining the architecture for analytical features. I’ll continue working with folks to complete our open work items such as improving backup retention, completing GA production readiness review, and completing the migration to us-east1. I want to thank everyone for the work they’ve put into the ClickHouse WG and the progress we’ve made as a group. I’d also encourage you all to check out the work being done in Product Usage Data Architecture Working Group and consider how you can contribute there.

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
    • 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

Commits

• Move CH WG to Paast working groups.

---