From bc0a55da58ff6ee94d66d70892de2b7215f285b3 Mon Sep 17 00:00:00 2001
From: GitHub Action <action@github.com>
Date: Tue, 10 Sep 2024 22:05:33 +0000
Subject: [PATCH] Sync working groups

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

diff --git a/_data/wg.yaml b/_data/wg.yaml
index 3841dec8cb..229caf2c23 100644
--- a/_data/wg.yaml
+++ b/_data/wg.yaml
@@ -1,5 +1,22 @@
 ---
 working-groups:
+    - 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
+      readme: |
+        <p>At the moment, when you create a Quarkus project (from code.quarkus.io or the CLI), a set of <code>Dockerfiles</code> is generated. However,</p>
+        <ol>
+        <li>Not all these files are used by the user</li>
+        <li>These files are very quickly outdated</li>
+        <li>It does not allow <em>extensions</em> to customize the content</li>
+        </ol>
+        <p>This working group aims to replace these `Dockerfiles' with a CLI command that generates an up-to-date Dockerfile and includes extension customization.</p>
+        <p>The goal is not to allow updating these files once generated but to provide a one-off generation that the user can consult and use. It will use the recommended and up-to-date <code>FROM</code> image to improve security and, depending on the generated <em>variant</em> (JVM, native, native-micro...), follow good practices (such as using <code>run-java</code> for the JVM one).</p>
+        <p>You can find more details about this working group on <a href="https://github.com/quarkusio/quarkus/discussions/41352">this discussion</a>.
+        Once completed, this working group will be followed by other initiatives focusing on generating the Github Action and Tekton pipelines.</p>
+        <p><em>Point of contact</em>: @iocanel (<code>Ioannis Canellos</code>on Zulip)</p>
+      status: staled
+      last-activity: 2024-09-10
     - 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)
@@ -125,20 +142,3 @@ working-groups:
         The target is to have 1.0.0 the 1 October 2024.
         
         For 1.0 we need pagination, tags and SEO.
-    - 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
-      readme: |
-        <p>At the moment, when you create a Quarkus project (from code.quarkus.io or the CLI), a set of <code>Dockerfiles</code> is generated. However,</p>
-        <ol>
-        <li>Not all these files are used by the user</li>
-        <li>These files are very quickly outdated</li>
-        <li>It does not allow <em>extensions</em> to customize the content</li>
-        </ol>
-        <p>This working group aims to replace these `Dockerfiles' with a CLI command that generates an up-to-date Dockerfile and includes extension customization.</p>
-        <p>The goal is not to allow updating these files once generated but to provide a one-off generation that the user can consult and use. It will use the recommended and up-to-date <code>FROM</code> image to improve security and, depending on the generated <em>variant</em> (JVM, native, native-micro...), follow good practices (such as using <code>run-java</code> for the JVM one).</p>
-        <p>You can find more details about this working group on <a href="https://github.com/quarkusio/quarkus/discussions/41352">this discussion</a>.
-        Once completed, this working group will be followed by other initiatives focusing on generating the Github Action and Tekton pipelines.</p>
-        <p><em>Point of contact</em>: @iocanel (<code>Ioannis Canellos</code>on Zulip)</p>
-      status: staled
-      last-activity: 2024-08-05