Sync working groups

Author: actions-user

_data/wg.yaml

@@ -1,5 +1,35 @@
 ---
 working-groups:
+    - title: "Chappie"
+      board-url: "https://github.com/orgs/quarkiverse/projects/8"
+      short-description: |
+        The main objective of this working group is to allow AI features in Quarkus Dev Mode (Dev UI and CLI)
+      readme: |
+        <p>The main objective of this working group is to allow AI features in Quarkus Dev Mode (Dev UI and CLI)</p>
+        <h3>The Problem</h3>
+        <p>The way developers write code is changing with the rise of AI tools like chatGPT, etc. Developers now ask an AI agent to help with tasks.</p>
+        <h3>The proposed Solution</h3>
+        <p>Provide a way to allow AI integration into Quarkus Dev Mode (Dev UI and CLI) . They should enable extensions to to contribute to the AI hooks.</p>
+        <p>Quarkus core should allow hooks (BuildItems) that extensions can use to define AI functions.</p>
+        <p>The chappie extensions will use this and set it up in Dev UI. The Chappie extension will also be responsible for an indexed vector DB that contains the Quarkus documentation. Extensions should be able to use this with groupId and artifactId.</p>
+        <p>The Chappie extension will manage the backend configuration, connection (to the LLM), and the elements in the Dev UI.</p>
+        <p>Extensions will provide relevant AI functions.</p>
+        <p>Adding a chatbot can also be added.</p>
+        <ul>
+        <li>Point of contact: @phillip-kruger (@<strong>Phillip Krüger</strong>  on Zulip)</li>
+        <li>Proposal: https://github.com/quarkusio/quarkus/discussions/45377</li>
+        <li>Discussion: <a href="https://quarkusio.zulipchat.com/#narrow/stream/187038-dev">Zulip topic</a></li>
+        </ul>
+      status: on track
+      completed: false
+      last-activity: 2025-04-02
+      last-update-date: 2025-03-27
+      last-update: |
+        We had several discussions to find the proper architecture/modularization. It will likely require conditional dependencies to avoid pulling AI-related "code" into the regular extension. 
+        Thus, priorities shifted slightly to focus on "general" action in a first step.
+      point-of-contact: "@phillip-kruger (@<strong>Phillip Krüger</strong>  on Zulip)"
+      proposal: https://github.com/quarkusio/quarkus/discussions/45377
+      discussion: https://quarkusio.zulipchat.com/#narrow/stream/187038-dev
     - title: "Test classloading"
       board-url: "https://github.com/orgs/quarkusio/projects/30"
       short-description: |
@@ -140,36 +170,6 @@ working-groups:
       last-update-date: 2025-04-01
       last-update: |
         In the last month, the WG - Quarkus 3.15 LTS closed two issues: one regarding the assignment of random ports in the configuration and another updating the Kafka client version to 3.7.2 to address CVE-2024-56128. No new issues were opened, reflecting a commitment to resolving important topics for the upcoming LTS release.
-    - title: "Chappie"
-      board-url: "https://github.com/orgs/quarkiverse/projects/8"
-      short-description: |
-        The main objective of this working group is to allow AI features in Quarkus Dev Mode (Dev UI and CLI)
-      readme: |
-        <p>The main objective of this working group is to allow AI features in Quarkus Dev Mode (Dev UI and CLI)</p>
-        <h3>The Problem</h3>
-        <p>The way developers write code is changing with the rise of AI tools like chatGPT, etc. Developers now ask an AI agent to help with tasks.</p>
-        <h3>The proposed Solution</h3>
-        <p>Provide a way to allow AI integration into Quarkus Dev Mode (Dev UI and CLI) . They should enable extensions to to contribute to the AI hooks.</p>
-        <p>Quarkus core should allow hooks (BuildItems) that extensions can use to define AI functions.</p>
-        <p>The chappie extensions will use this and set it up in Dev UI. The Chappie extension will also be responsible for an indexed vector DB that contains the Quarkus documentation. Extensions should be able to use this with groupId and artifactId.</p>
-        <p>The Chappie extension will manage the backend configuration, connection (to the LLM), and the elements in the Dev UI.</p>
-        <p>Extensions will provide relevant AI functions.</p>
-        <p>Adding a chatbot can also be added.</p>
-        <ul>
-        <li>Point of contact: @phillip-kruger (@<strong>Phillip Krüger</strong>  on Zulip)</li>
-        <li>Proposal: https://github.com/quarkusio/quarkus/discussions/45377</li>
-        <li>Discussion: <a href="https://quarkusio.zulipchat.com/#narrow/stream/187038-dev">Zulip topic</a></li>
-        </ul>
-      status: on track
-      completed: false
-      last-activity: 2025-03-20
-      last-update-date: 2025-03-27
-      last-update: |
-        We had several discussions to find the proper architecture/modularization. It will likely require conditional dependencies to avoid pulling AI-related "code" into the regular extension. 
-        Thus, priorities shifted slightly to focus on "general" action in a first step.
-      point-of-contact: "@phillip-kruger (@<strong>Phillip Krüger</strong>  on Zulip)"
-      proposal: https://github.com/quarkusio/quarkus/discussions/45377
-      discussion: https://quarkusio.zulipchat.com/#narrow/stream/187038-dev
     - title: "Observability.Next"
       board-url: "https://github.com/orgs/quarkusio/projects/42"
       short-description: |