From 359513e9ae7d39b07f407a9e785eb4ae59db6dbb Mon Sep 17 00:00:00 2001
From: GitHub Action <action@github.com>
Date: Mon, 28 Oct 2024 10:02:17 +0000
Subject: [PATCH] Sync working groups

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

diff --git a/_data/wg.yaml b/_data/wg.yaml
index 6b694d1c20..e5dd1ba7c6 100644
--- a/_data/wg.yaml
+++ b/_data/wg.yaml
@@ -1,5 +1,38 @@
 ---
 working-groups:
+    - 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.
+      readme: |
+        <p>from Discussion at https://github.com/quarkusio/quarkus/discussions/43013</p>
+        <p>We started the move of Quarkus to a foundation <a href="https://quarkus.io/blog/quarkus-in-a-foundation/">earlier this year</a> and recently <a href="https://quarkus.io/blog/quarkus-moving-to-commonhaus/">set the direction</a> towards <a href="https://www.commonhaus.org/">CommonHaus</a> and during the summer break the CommonHaus council <a href="https://github.com/commonhaus/foundation/pull/183">approved our request</a> to join.</p>
+        <p>Thus, now the real work starts, and it's just fitting we set up a working group for the effort getting Quarkus to CommonHaus foundation.</p>
+        <h1>Goal</h1>
+        <p>Two parts</p>
+        <ul>
+        <li>setup Quarkus to have transparent and open governance</li>
+        <li>Go through the few but important requirements for a CommonHaus project.</li>
+        </ul>
+        <h1>Initial work items/questions:</h1>
+        <p>Current known list, but not limited to:</p>
+        <ul>
+        <li>identify design communication channels (i.e. #41973)</li>
+        <li>which repositories / code will move</li>
+        <li>impact (if any) on quarkiverse projects</li>
+        <li>how will trademarks work/change</li>
+        <li>identify running services and setup/maintain them (registry.quarkus.io, code.quarkus.io etc.)</li>
+        <li>add required metadata/files to the various repositories</li>
+        </ul>
+        <h1>Tracking</h1>
+        <p>We will use the working group board to track publicly all the known relevant work and questions.For the few exception cases where, for legal or personal constraints, the work must happen in private, we will post the outcome and results in public places (like a GitHub discussion of a GitHub issue tracked on the working group board).</p>
+        <h1>When will this working group be done?</h1>
+        <p>When Quarkus has an active working governance model in place and all major work items around setting up Quarkus at CommonHaus are completed - after that, its expected things will just be iteratively improved, and the dedicated working group will not be needed (others might start to continue more specific efforts).</p>
+        <p>The majority of the work must be done before the end of December 2024. The latest deadline for CommonHaus is April 2025, when the bootstrap period of CommonHaus ends.</p>
+      status: on track
+      completed: false
+      last-activity: 2024-10-28
+      last-update: |
+        Just got started.
     - 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.
@@ -127,36 +160,3 @@ working-groups:
         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.
-      readme: |
-        <p>from Discussion at https://github.com/quarkusio/quarkus/discussions/43013</p>
-        <p>We started the move of Quarkus to a foundation <a href="https://quarkus.io/blog/quarkus-in-a-foundation/">earlier this year</a> and recently <a href="https://quarkus.io/blog/quarkus-moving-to-commonhaus/">set the direction</a> towards <a href="https://www.commonhaus.org/">CommonHaus</a> and during the summer break the CommonHaus council <a href="https://github.com/commonhaus/foundation/pull/183">approved our request</a> to join.</p>
-        <p>Thus, now the real work starts, and it's just fitting we set up a working group for the effort getting Quarkus to CommonHaus foundation.</p>
-        <h1>Goal</h1>
-        <p>Two parts</p>
-        <ul>
-        <li>setup Quarkus to have transparent and open governance</li>
-        <li>Go through the few but important requirements for a CommonHaus project.</li>
-        </ul>
-        <h1>Initial work items/questions:</h1>
-        <p>Current known list, but not limited to:</p>
-        <ul>
-        <li>identify design communication channels (i.e. #41973)</li>
-        <li>which repositories / code will move</li>
-        <li>impact (if any) on quarkiverse projects</li>
-        <li>how will trademarks work/change</li>
-        <li>identify running services and setup/maintain them (registry.quarkus.io, code.quarkus.io etc.)</li>
-        <li>add required metadata/files to the various repositories</li>
-        </ul>
-        <h1>Tracking</h1>
-        <p>We will use the working group board to track publicly all the known relevant work and questions.For the few exception cases where, for legal or personal constraints, the work must happen in private, we will post the outcome and results in public places (like a GitHub discussion of a GitHub issue tracked on the working group board).</p>
-        <h1>When will this working group be done?</h1>
-        <p>When Quarkus has an active working governance model in place and all major work items around setting up Quarkus at CommonHaus are completed - after that, its expected things will just be iteratively improved, and the dedicated working group will not be needed (others might start to continue more specific efforts).</p>
-        <p>The majority of the work must be done before the end of December 2024. The latest deadline for CommonHaus is April 2025, when the bootstrap period of CommonHaus ends.</p>
-      status: on track
-      completed: false
-      last-activity: 2024-09-29
-      last-update: |
-        Just got started.