Sync working groups

Author: actions-user

_data/wg.yaml

@@ -1,24 +1,5 @@
 ---
 working-groups:
-    - title: "OIDC improvements"
-      board-url: "https://github.com/orgs/quarkusio/projects/46"
-      short-description: The goal of this working group is to improve quarkus-oidc by: implementing crucial new security features, continuing with improving the way OIDC requests can be intercepted, prioritizing some other open issues, such as using JWT bearer client authentication to complete the authorization code flow
-      readme: |
-        <p>The goal of this working group is to improve quarkus-oidc by: implementing crucial new security features, continuing with improving the way OIDC requests can be intercepted, prioritizing some other open issues, such as using JWT bearer client authentication to complete the authorization code flow</p>
-        <ul>
-        <li>Point of contact: @sberyozkin (@_<strong>Sergey Beryozkin</strong>  on Zulip)</li>
-        <li>Proposal: https://github.com/quarkusio/quarkus/discussions/42116</li>
-        <li>Deliverable: TBD</li>
-        </ul>
-      status: on track
-      completed: false
-      last-activity: 2025-03-28
-      last-update-date: 2025-03-28
-      last-update: |
-        The working group has now officially started. As the work began before the kick-off, a few items are already in the "completed" state.
-      deliverable: TBD
-      point-of-contact: "@sberyozkin (@_<strong>Sergey Beryozkin</strong>  on Zulip)"
-      proposal: https://github.com/quarkusio/quarkus/discussions/42116
     - title: "Gizmo 2"
       board-url: "https://github.com/orgs/quarkusio/projects/43"
       short-description: Gizmo 2 related tasks
@@ -38,6 +19,25 @@ working-groups:
       deliverable: TBD
       point-of-contact: "@mkouba (@<strong>Martin Kouba</strong>  on Zulip)"
       proposal: https://github.com/quarkusio/quarkus/discussions/46627
+    - title: "OIDC improvements"
+      board-url: "https://github.com/orgs/quarkusio/projects/46"
+      short-description: The goal of this working group is to improve quarkus-oidc by: implementing crucial new security features, continuing with improving the way OIDC requests can be intercepted, prioritizing some other open issues, such as using JWT bearer client authentication to complete the authorization code flow
+      readme: |
+        <p>The goal of this working group is to improve quarkus-oidc by: implementing crucial new security features, continuing with improving the way OIDC requests can be intercepted, prioritizing some other open issues, such as using JWT bearer client authentication to complete the authorization code flow</p>
+        <ul>
+        <li>Point of contact: @sberyozkin (@_<strong>Sergey Beryozkin</strong>  on Zulip)</li>
+        <li>Proposal: https://github.com/quarkusio/quarkus/discussions/42116</li>
+        <li>Deliverable: TBD</li>
+        </ul>
+      status: on track
+      completed: false
+      last-activity: 2025-03-28
+      last-update-date: 2025-03-28
+      last-update: |
+        The working group has now officially started. As the work began before the kick-off, a few items are already in the "completed" state.
+      deliverable: TBD
+      point-of-contact: "@sberyozkin (@_<strong>Sergey Beryozkin</strong>  on Zulip)"
+      proposal: https://github.com/quarkusio/quarkus/discussions/42116
     - title: "Test classloading"
       board-url: "https://github.com/orgs/quarkusio/projects/30"
       short-description: The goal of this working group is to rewrite Quarkus's test classloading, so that tests are run in the same classloader as the application under tests, and Quarkus extensions can do "Quarkus-y" manipulations of test classes.