Sync working groups

_data/wg.yaml

@@ -1,5 +1,19 @@
 ---
 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>
+        <p><em>Point of contact:</em> @cescoffier (@<strong>Clement Escoffier</strong> on Zulip)</p>
+      status: complete
+      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.
     - title: "Quarkus to the CommonHaus Foundation"
       board-url: "https://github.com/orgs/quarkusio/projects/38"
       short-description: Work needed around moving Quarkus to foundation and streamline open governance.
@@ -103,18 +117,6 @@ working-groups:
         The target is to have 1.0.0 the 1 October 2024.
         
         For 1.0 we need pagination, tags and SEO.
-    - 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: on track
-      last-activity: 2024-09-13
-      last-update: |
-        Approaching completion. Watch [Quarkus Insight #177](https://www.youtube.com/watch?v=VP7c9ftFwrQ&list=PLsM3ZE5tGAVatO65JIxgskQh-OKoqM4F2&index=1) to see various demo going from configuration, local TLS, certificate reloading and ACME integration.
     - title: "Docker file generation"
       board-url: "https://github.com/orgs/quarkusio/projects/27"
       short-description: A working group focusing on the generation of Dockerfile / ContainerFile