Sync working groups

Author: actions-user

_data/wg.yaml

@@ -12,7 +12,18 @@ working-groups:
         <li>The <code>done</code> column means that the issues have been completed</li>
         </ul>
       status: at risk
-      last-activity: 2024-08-29
+      last-activity: 2024-08-30
+    - 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-08-30
+      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: "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.
@@ -66,17 +77,6 @@ working-groups:
         <p><em>Point of contact</em>: @gsmet (Zulip: @_<strong>Guillaume Smet</strong> )</p>
       status: on track
       last-activity: 2024-08-23
-    - 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-08-19
-      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