From 0eb78c9232f7050cc35c5445a81bdbe7aa4cd649 Mon Sep 17 00:00:00 2001
From: GitHub Action <action@github.com>
Date: Mon, 18 Nov 2024 11:03:43 +0000
Subject: [PATCH] Sync working groups

---
 _data/wg.yaml | 34 +++++++++++++++++++---------------
 1 file changed, 19 insertions(+), 15 deletions(-)

diff --git a/_data/wg.yaml b/_data/wg.yaml
index 783eea21ef8..7b14910e4ae 100644
--- a/_data/wg.yaml
+++ b/_data/wg.yaml
@@ -1,5 +1,24 @@
 ---
 working-groups:
+    - 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...)
+      readme: |
+        <p>TLS is becoming increasingly common and recommended. However, for years, each Quarkus extension has been doing its own TLS configuration and management. As a result, the configuration looks different everywhere, and many extensions have incomplete configurations.</p>
+        <p>Based on the newly integrated TLS registry, we now have a single place to configure TLS. At runtime, it provides methods to configure Vert.x and &quot;pure&quot; Java clients (using an <code>SSLContext</code>).</p>
+        <p>The goal of this focus group is to continue integrating the TLS registry and improve Quarkus integration with certificate providers (Let's Encrypt, Cert-Manager). In addition, we would like to provide a frictionless local experience around TLS (i.e., without the infamous untrusted certificate screen).</p>
+        <ul>
+        <li>Point of contact:  @cescoffier (@<strong>Clement Escoffier</strong> on Zulip)</li>
+        <li>Deliverable: <a href="https://www.youtube.com/watch?v=VP7c9ftFwrQ">Quarkus Insight</a></li>
+        <li>Discussion: https://github.com/quarkusio/quarkus/discussions/41024</li>
+        </ul>
+      status: complete
+      completed: true
+      last-activity: 2024-11-18
+      last-update: |
+        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
@@ -164,18 +183,3 @@ working-groups:
         References:
         https://github.com/fluorumlabs/asciidocj
         https://github.com/vsch/flexmark-java
-    - 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...)
-      readme: |
-        <p>TLS is becoming increasingly common and recommended. However, for years, each Quarkus extension has been doing its own TLS configuration and management. As a result, the configuration looks different everywhere, and many extensions have incomplete configurations.</p>
-        <p>Based on the newly integrated TLS registry, we now have a single place to configure TLS. At runtime, it provides methods to configure Vert.x and &quot;pure&quot; Java clients (using an <code>SSLContext</code>).</p>
-        <p>The goal of this focus group is to continue integrating the TLS registry and improve Quarkus integration with certificate providers (Let's Encrypt, Cert-Manager). In addition, we would like to provide a frictionless local experience around TLS (i.e., without the infamous untrusted certificate screen).</p>
-        <p><em>Point of contact:</em> @cescoffier (@<strong>Clement Escoffier</strong> on Zulip)</p>
-      status: complete
-      completed: true
-      last-activity: 2024-09-29
-      last-update: |
-        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.