Sync working groups

Author: actions-user

_data/wg.yaml

@@ -1,5 +1,26 @@
 ---
 working-groups:
+    - title: "WebSocket Next"
+      board-url: "https://github.com/orgs/quarkusio/projects/26"
+      short-description: WebSocket-Next related tasks
+      readme: |
+        <p>The WebSocket Next <em>focus group</em> aims to improve our WebSocket experience.</p>
+        <p>Recently, we delivered a new approach to dealing with WebSocket (both for the server and client). This was the first step. There are still a few areas to improve, such as documentation, security, observability, and testability. The goal of this focus group is to track these efforts.</p>
+        <ul>
+        <li>Point of contact: @mkouba (@<strong>Martin Kouba</strong>  on Zulip)</li>
+        </ul>
+      status: on track
+      completed: false
+      last-activity: 2024-11-18
+      last-update: |
+        ### Telemetry
+        https://github.com/quarkusio/quarkus/pull/41956 was merged last week. @michalvavrik is going to send a pull request with Micrometer support this week.
+        
+        ### Performance
+        Two problems were addressed in Vert.x: https://github.com/eclipse-vertx/vert.x/pull/5358 and https://github.com/eclipse-vertx/vert.x/pull/5348.
+        The CDI request context is only activated if needed: https://github.com/quarkusio/quarkus/pull/43915.
+        
+        I hope that WS Next will be feature-complete at the time of 3.17 release.
     - title: "Enhanced TLS support"
       board-url: "https://github.com/orgs/quarkusio/projects/24"
       short-description: Track the progress around the new TLS configuration centralization and new features (like Let's Encrypt, Cert-Manager, and local experience...)
@@ -19,25 +40,6 @@ working-groups:
         This working group is complete! 
         That does not mean that no work will be done around TLS, but what was defined in the initial scope of the working group has been completed. 
         Enhancements and bug fixes will follow.
-    - title: "WebSocket Next"
-      board-url: "https://github.com/orgs/quarkusio/projects/26"
-      short-description: WebSocket-Next related tasks
-      readme: |
-        <p>The WebSocket Next <em>focus group</em> aims to improve our WebSocket experience.</p>
-        <p>Recently, we delivered a new approach to dealing with WebSocket (both for the server and client). This was the first step. There are still a few areas to improve, such as documentation, security, observability, and testability. The goal of this focus group is to track these efforts.</p>
-        <p>Point of contact: @mkouba (@<strong>Martin Kouba</strong>  on Zulip)</p>
-      status: on track
-      completed: false
-      last-activity: 2024-11-13
-      last-update: |
-        ### Telemetry
-        https://github.com/quarkusio/quarkus/pull/41956 was merged last week. @michalvavrik is going to send a pull request with Micrometer support this week.
-        
-        ### Performance
-        Two problems were addressed in Vert.x: https://github.com/eclipse-vertx/vert.x/pull/5358 and https://github.com/eclipse-vertx/vert.x/pull/5348.
-        The CDI request context is only activated if needed: https://github.com/quarkusio/quarkus/pull/43915.
-        
-        I hope that WS Next will be feature-complete at the time of 3.17 release.
     - title: "Quarkus 3.15 LTS"
       board-url: "https://github.com/orgs/quarkusio/projects/28"
       short-description: This WG focuses on defining the issues we would like to have in the next-to-be LTS (Quarkus 3.14/3.15)