Skip to content

Commit 37818da

Browse files
committed
Sync working groups
1 parent 481d68d commit 37818da

File tree

1 file changed

+28
-28
lines changed

1 file changed

+28
-28
lines changed

_data/wg.yaml

Lines changed: 28 additions & 28 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,33 @@
11
---
22
working-groups:
3+
- title: "Chappie"
4+
board-url: "https://github.com/orgs/quarkiverse/projects/8"
5+
short-description: The main objective of this working group is to allow AI features in Quarkus Dev Mode (Dev UI and CLI)
6+
readme: |
7+
<p>The main objective of this working group is to allow AI features in Quarkus Dev Mode (Dev UI and CLI)</p>
8+
<h3>The Problem</h3>
9+
<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>
10+
<h3>The proposed Solution</h3>
11+
<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>
12+
<p>Quarkus core should allow hooks (BuildItems) that extensions can use to define AI functions.</p>
13+
<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>
14+
<p>The Chappie extension will manage the backend configuration, connection (to the LLM), and the elements in the Dev UI.</p>
15+
<p>Extensions will provide relevant AI functions.</p>
16+
<p>Adding a chatbot can also be added.</p>
17+
<ul>
18+
<li>Point of contact: @phillip-kruger (@<strong>Phillip Krüger</strong> on Zulip)</li>
19+
<li>Proposal: https://github.com/quarkusio/quarkus/discussions/45377</li>
20+
<li>Discussion: <a href="https://quarkusio.zulipchat.com/#narrow/stream/187038-dev">Zulip topic</a></li>
21+
</ul>
22+
status: on track
23+
completed: false
24+
last-activity: 2025-03-17
25+
last-update-date: 2025-03-13
26+
last-update: |
27+
Work started.
28+
point-of-contact: "@phillip-kruger (@<strong>Phillip Krüger</strong> on Zulip)"
29+
proposal: https://github.com/quarkusio/quarkus/discussions/45377
30+
discussion: https://quarkusio.zulipchat.com/#narrow/stream/187038-dev
331
- title: "Gizmo 2"
432
board-url: "https://github.com/orgs/quarkusio/projects/43"
533
short-description: Gizmo 2 related tasks
@@ -44,34 +72,6 @@ working-groups:
4472
point-of-contact: "@holly-cummins (@<strong>Holly Cummins</strong> on Zulip)"
4573
proposal: https://github.com/quarkusio/quarkus/discussions/41867
4674
discussion: https://quarkusio.zulipchat.com/#narrow/channel/187038-dev/topic/WG.20.2330.20Test.20Classloading.20chatter/
47-
- title: "Chappie"
48-
board-url: "https://github.com/orgs/quarkiverse/projects/8"
49-
short-description: The main objective of this working group is to allow AI features in Quarkus Dev Mode (Dev UI and CLI)
50-
readme: |
51-
<p>The main objective of this working group is to allow AI features in Quarkus Dev Mode (Dev UI and CLI)</p>
52-
<h3>The Problem</h3>
53-
<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>
54-
<h3>The proposed Solution</h3>
55-
<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>
56-
<p>Quarkus core should allow hooks (BuildItems) that extensions can use to define AI functions.</p>
57-
<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>
58-
<p>The Chappie extension will manage the backend configuration, connection (to the LLM), and the elements in the Dev UI.</p>
59-
<p>Extensions will provide relevant AI functions.</p>
60-
<p>Adding a chatbot can also be added.</p>
61-
<ul>
62-
<li>Point of contact: @phillip-kruger (@<strong>Phillip Krüger</strong> on Zulip)</li>
63-
<li>Proposal: https://github.com/quarkusio/quarkus/discussions/45377</li>
64-
<li>Discussion: <a href="https://quarkusio.zulipchat.com/#narrow/stream/187038-dev">Zulip topic</a></li>
65-
</ul>
66-
status: on track
67-
completed: false
68-
last-activity: 2025-03-13
69-
last-update-date: 2025-03-13
70-
last-update: |
71-
Work started.
72-
point-of-contact: "@phillip-kruger (@<strong>Phillip Krüger</strong> on Zulip)"
73-
proposal: https://github.com/quarkusio/quarkus/discussions/45377
74-
discussion: https://quarkusio.zulipchat.com/#narrow/stream/187038-dev
7575
- title: "Quarkus 3.15 LTS"
7676
board-url: "https://github.com/orgs/quarkusio/projects/28"
7777
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)

0 commit comments

Comments
 (0)