Vue 3 Working Group Disbanding

Why is this change being made?

The Vue 3 working group is not meeting its purpose for several reasons:

1. The scope of the working group is too large
2. The members list does not reflect who's actually working on this migration
3. We're getting too bogged down in the actual migrations instead of solving the hard problems and pulling in support from the wider org.

Because of this, the plan is to disband the working group and split the important tasks into smaller, more focused, task groups. This way we can get the right people on the right problems at the right time and can work in parallel where it makes sense.

Note: For the current ask of migrating all the tests, our plan is to tighten the rules on the failing jobs and leave the migrations to GitLab engineers. I'll add this to the handbook seperately.

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

---