Skip to content

Commit ef44182

Browse files
actions-useractions-user
committed
Sync working groups
1 parent 5bd6f3f commit ef44182

1 file changed

Lines changed: 82 additions & 82 deletions

File tree

‎_data/wg.yaml‎

Lines changed: 82 additions & 82 deletions
Original file line numberDiff line numberDiff line change
@@ -1,58 +1,5 @@
11
---
22
working-groups:
3-
- title: "Convert quarkus.io to Roq"
4-
board-url: "https://github.com/orgs/quarkusio/projects/79"
5-
short-description: |
6-
The main objective of this working group is to convert our Jekyll-based website to one built on Roq.
7-
readme: |
8-
<h2>Objective:</h2>
9-
<p>The main objective of this working group is to convert our Jekyll-based website to a Roq-based one.</p>
10-
<h2>The Problem</h2>
11-
<p>Although Quarkus promotes a Quarkus-based static site generator, our own website uses a Ruby-based one. As well as being reputationally awkward (why aren't we eating our own dog food?), the Ruby-based generator has several practical limitations:</p>
12-
<ul>
13-
<li>It is difficult for the Java experts in the Quarkus team to make changes to the Ruby site code to add dynamic features. This means many enhancements get ruled out at the design stage.</li>
14-
<li>The site build is temperamental. Local Ruby installations can break, and even the container-based build can break.</li>
15-
</ul>
16-
<h2>The proposed Solution</h2>
17-
<p>Add support for Roq for the range of features used on quarkus.io, and add migration scripts to convert Jekyll to Quarkus. Once these are done, the quarkus.io site can be converted to Roq.</p>
18-
<h2>Definition of Done</h2>
19-
<p>This working group is complete when the live quarkus.io site is based on Roq.</p>
20-
<h2>Scope of Work</h2>
21-
<p>Visual changes to the website are outside the scope of this work. Conversion of some of the smaller satellite sites, such as https://quarkiverse.io/, could be in scope to act as prototypes. It is assumed that the quarkus.io contents that use asciidoc will continue to do so.</p>
22-
<h2>Organizing the Work</h2>
23-
<p>Issues will be split between the https://github.com/quarkusio/quarkusio.github.io and https://github.com/quarkiverse/quarkus-roq repositories. Zulip will be used for coordination.</p>
24-
<h2>Expected Timeline:</h2>
25-
<p>I expect about six months to be a suitable timescale.</p>
26-
<p>As always, we will aim for an incremental delivery, although the final switch will be a big bang.</p>
27-
<ul>
28-
<li>Support building Roq sites in quarkus.io preview</li>
29-
<li>Develop conversion scripts</li>
30-
<li>Maintain a long-running PR, with scripts</li>
31-
<li>Fill functionality gaps in Roq</li>
32-
<li>(possibly) Split site and and ship some sub-sections as Roq, some as Jekyll</li>
33-
</ul>
34-
<h2>Potential Outcomes &amp; Deliverables</h2>
35-
<p>The deliverables of this working group include:</p>
36-
<ul>
37-
<li>An easy-to-build, high-quality, dog-fooded website</li>
38-
<li>Technical improvements to Roq to support the range of features required for a site as complex as quarkus.io</li>
39-
<li>A set of documentation and scripts that will help other people do Jekyll to Roq conversions</li>
40-
</ul>
41-
<ul>
42-
<li>Point of contact: @holly-cummins and @ia3andy</li>
43-
<li>Proposal: https://github.com/quarkusio/quarkus/discussions/53541</li>
44-
<li>Discussion: <a href="https://quarkusio.zulipchat.com/#narrow/channel/187038-dev">Zulip</a>)</li>
45-
</ul>
46-
status: on track
47-
lts: false
48-
completed: false
49-
last-activity: 2026-06-16
50-
last-update-date: 2026-04-27
51-
last-update: |
52-
WG started.
53-
point-of-contact: "@holly-cummins and @ia3andy"
54-
proposal: https://github.com/quarkusio/quarkus/discussions/53541
55-
discussion: https://quarkusio.zulipchat.com/#narrow/channel/187038-dev
563
- title: "Quarkus Data"
574
board-url: "https://github.com/orgs/quarkusio/projects/50"
585
short-description: |
@@ -111,7 +58,7 @@ working-groups:
11158
status: on track
11259
lts: false
11360
completed: false
114-
last-activity: 2026-06-16
61+
last-activity: 2026-06-17
11562
last-update-date: 2026-05-26
11663
last-update: |
11764
The Quarkus Data WG completed a big renaming effort, transitioning Panache Next to Quarkus Data and its module to Quarkus Data Hibernate. We improved native compilation support, especially when Hibernate Reactive is absent. Security annotations now properly apply to repositories, and we resolved various compilation issues. Plus, we switched repository scopes from `@Dependant` to `@ApplicationScoped`.
@@ -158,12 +105,92 @@ working-groups:
158105
status: on track
159106
lts: false
160107
completed: false
161-
last-activity: 2026-06-16
108+
last-activity: 2026-06-17
162109
last-update-date: 2026-05-26
163110
last-update: |
164111
Big strides this week on the Quarkus 4 effort! We finally closed out the upgrade to Vert.x 5, including migrating the OpenTelemetry extension and several others. Also got the OpenShift, Kubernetes, and MongoDB dev services to behave and not start during augmentation.
165112
166113
(This status update was automatically generated using AI.)
114+
- title: "Dev Services Lifecycle"
115+
board-url: "https://github.com/orgs/quarkusio/projects/49"
116+
short-description: |
117+
This working group will define and implement a consistent and configurable lifecycle model for Dev Services. It will shift the startup to the correct phase, enable optional reuse across dev and test modes, and clarify teardown and sharing behavior. The goal is to improve the developer experience.
118+
readme: |
119+
<p>This working group was formed to address long-standing inconsistencies and pain points in the Dev Services lifecycle within Quarkus. Dev Services are essential for simplifying local development and testing by automatically provisioning runtime dependencies (e.g., databases, message brokers), but their current lifecycle behavior leads to confusion and inefficiencies. Most notably, they are started during the augmentation phase, which conflicts with their inherently runtime-oriented nature and causes issues with newer efforts such as the test classloading revamp.</p>
120+
<p>The primary goal of this group is to define and implement a consistent, runtime-aligned lifecycle model for Dev Services. This includes shifting their startup to a phase after augmentation but before the application begins execution, ensuring better alignment with the runtime environment. A critical focus will also be on enabling optional reuse of Dev Services across dev and test modes — including reuse between repeated test executions — to reduce startup time and improve the iterative development experience.</p>
121+
<p>The group's scope covers several strategic areas: formalizing when and how Dev Services are started, reused, or stopped; defining rules for discoverability and sharing between profiles or processes; and avoiding resource leaks or accidental retention. It explicitly excludes broader orchestration features (such as service dependency graphs) and unrelated feature enhancements.</p>
122+
<p>The working group will produce a set of deliverables to support the new model. These include one or more Architecture Decision Records (ADRs) describing the new lifecycle model, the implementation of lifecycle logic in Quarkus Core, and updates to both user-facing and contributor documentation. Additionally, enhancements to the Dev Services development model will make it easier for extension authors to adopt and follow the new lifecycle standards. A public communication effort (e.g., blog posts or demos) will also be used to showcase the improvements.</p>
123+
<p>The new API is described here: https://quarkus.io/blog/new-dev-services-api/</p>
124+
<ul>
125+
<li>Point of contact: @holly-cummins (@<strong>Holly Cummins</strong> on Zulip), @ozangunalp (@<strong>Ozan Günalp</strong> on Zulip )</li>
126+
<li>Proposal: https://github.com/quarkusio/quarkus/discussions/47683</li>
127+
<li>Discussion: <a href="https://quarkusio.zulipchat.com/#narrow/channel/187038-dev">Zulip</a>)</li>
128+
</ul>
129+
status: on track
130+
lts: false
131+
completed: false
132+
last-activity: 2026-06-17
133+
last-update-date: 2026-05-26
134+
last-update: |
135+
The Dev Services Lifecycle group made significant progress, ensuring OpenShift, Kubernetes, and MongoDB services no longer start during augmentation. We also enabled reusing dev services containers across restarts and migrated the Kubernetes Dev Service to its new architecture. We're now tracking further work around scoping Dev Services config and adding tests for the old model.
136+
137+
(This status update was automatically generated using AI.)
138+
point-of-contact: "@holly-cummins (@<strong>Holly Cummins</strong> on Zulip), @ozangunalp (@<strong>Ozan Günalp</strong> on Zulip )"
139+
proposal: https://github.com/quarkusio/quarkus/discussions/47683
140+
discussion: https://quarkusio.zulipchat.com/#narrow/channel/187038-dev
141+
- title: "Convert quarkus.io to Roq"
142+
board-url: "https://github.com/orgs/quarkusio/projects/79"
143+
short-description: |
144+
The main objective of this working group is to convert our Jekyll-based website to one built on Roq.
145+
readme: |
146+
<h2>Objective:</h2>
147+
<p>The main objective of this working group is to convert our Jekyll-based website to a Roq-based one.</p>
148+
<h2>The Problem</h2>
149+
<p>Although Quarkus promotes a Quarkus-based static site generator, our own website uses a Ruby-based one. As well as being reputationally awkward (why aren't we eating our own dog food?), the Ruby-based generator has several practical limitations:</p>
150+
<ul>
151+
<li>It is difficult for the Java experts in the Quarkus team to make changes to the Ruby site code to add dynamic features. This means many enhancements get ruled out at the design stage.</li>
152+
<li>The site build is temperamental. Local Ruby installations can break, and even the container-based build can break.</li>
153+
</ul>
154+
<h2>The proposed Solution</h2>
155+
<p>Add support for Roq for the range of features used on quarkus.io, and add migration scripts to convert Jekyll to Quarkus. Once these are done, the quarkus.io site can be converted to Roq.</p>
156+
<h2>Definition of Done</h2>
157+
<p>This working group is complete when the live quarkus.io site is based on Roq.</p>
158+
<h2>Scope of Work</h2>
159+
<p>Visual changes to the website are outside the scope of this work. Conversion of some of the smaller satellite sites, such as https://quarkiverse.io/, could be in scope to act as prototypes. It is assumed that the quarkus.io contents that use asciidoc will continue to do so.</p>
160+
<h2>Organizing the Work</h2>
161+
<p>Issues will be split between the https://github.com/quarkusio/quarkusio.github.io and https://github.com/quarkiverse/quarkus-roq repositories. Zulip will be used for coordination.</p>
162+
<h2>Expected Timeline:</h2>
163+
<p>I expect about six months to be a suitable timescale.</p>
164+
<p>As always, we will aim for an incremental delivery, although the final switch will be a big bang.</p>
165+
<ul>
166+
<li>Support building Roq sites in quarkus.io preview</li>
167+
<li>Develop conversion scripts</li>
168+
<li>Maintain a long-running PR, with scripts</li>
169+
<li>Fill functionality gaps in Roq</li>
170+
<li>(possibly) Split site and and ship some sub-sections as Roq, some as Jekyll</li>
171+
</ul>
172+
<h2>Potential Outcomes &amp; Deliverables</h2>
173+
<p>The deliverables of this working group include:</p>
174+
<ul>
175+
<li>An easy-to-build, high-quality, dog-fooded website</li>
176+
<li>Technical improvements to Roq to support the range of features required for a site as complex as quarkus.io</li>
177+
<li>A set of documentation and scripts that will help other people do Jekyll to Roq conversions</li>
178+
</ul>
179+
<ul>
180+
<li>Point of contact: @holly-cummins and @ia3andy</li>
181+
<li>Proposal: https://github.com/quarkusio/quarkus/discussions/53541</li>
182+
<li>Discussion: <a href="https://quarkusio.zulipchat.com/#narrow/channel/187038-dev">Zulip</a>)</li>
183+
</ul>
184+
status: on track
185+
lts: false
186+
completed: false
187+
last-activity: 2026-06-16
188+
last-update-date: 2026-04-27
189+
last-update: |
190+
WG started.
191+
point-of-contact: "@holly-cummins and @ia3andy"
192+
proposal: https://github.com/quarkusio/quarkus/discussions/53541
193+
discussion: https://quarkusio.zulipchat.com/#narrow/channel/187038-dev
167194
- title: "Modularity (JPMS) and JLink"
168195
board-url: "https://github.com/orgs/quarkusio/projects/76"
169196
short-description: |
@@ -524,33 +551,6 @@ working-groups:
524551
point-of-contact: "@phillip-kruger"
525552
proposal: https://github.com/quarkusio/quarkus/discussions/53093#discussioncomment-16271096
526553
discussion: https://quarkusio.zulipchat.com/#narrow/channel/187038-dev/topic/wg-dev-star/with/581636141
527-
- title: "Dev Services Lifecycle"
528-
board-url: "https://github.com/orgs/quarkusio/projects/49"
529-
short-description: |
530-
This working group will define and implement a consistent and configurable lifecycle model for Dev Services. It will shift the startup to the correct phase, enable optional reuse across dev and test modes, and clarify teardown and sharing behavior. The goal is to improve the developer experience.
531-
readme: |
532-
<p>This working group was formed to address long-standing inconsistencies and pain points in the Dev Services lifecycle within Quarkus. Dev Services are essential for simplifying local development and testing by automatically provisioning runtime dependencies (e.g., databases, message brokers), but their current lifecycle behavior leads to confusion and inefficiencies. Most notably, they are started during the augmentation phase, which conflicts with their inherently runtime-oriented nature and causes issues with newer efforts such as the test classloading revamp.</p>
533-
<p>The primary goal of this group is to define and implement a consistent, runtime-aligned lifecycle model for Dev Services. This includes shifting their startup to a phase after augmentation but before the application begins execution, ensuring better alignment with the runtime environment. A critical focus will also be on enabling optional reuse of Dev Services across dev and test modes — including reuse between repeated test executions — to reduce startup time and improve the iterative development experience.</p>
534-
<p>The group's scope covers several strategic areas: formalizing when and how Dev Services are started, reused, or stopped; defining rules for discoverability and sharing between profiles or processes; and avoiding resource leaks or accidental retention. It explicitly excludes broader orchestration features (such as service dependency graphs) and unrelated feature enhancements.</p>
535-
<p>The working group will produce a set of deliverables to support the new model. These include one or more Architecture Decision Records (ADRs) describing the new lifecycle model, the implementation of lifecycle logic in Quarkus Core, and updates to both user-facing and contributor documentation. Additionally, enhancements to the Dev Services development model will make it easier for extension authors to adopt and follow the new lifecycle standards. A public communication effort (e.g., blog posts or demos) will also be used to showcase the improvements.</p>
536-
<p>The new API is described here: https://quarkus.io/blog/new-dev-services-api/</p>
537-
<ul>
538-
<li>Point of contact: @holly-cummins (@<strong>Holly Cummins</strong> on Zulip), @ozangunalp (@<strong>Ozan Günalp</strong> on Zulip )</li>
539-
<li>Proposal: https://github.com/quarkusio/quarkus/discussions/47683</li>
540-
<li>Discussion: <a href="https://quarkusio.zulipchat.com/#narrow/channel/187038-dev">Zulip</a>)</li>
541-
</ul>
542-
status: on track
543-
lts: false
544-
completed: false
545-
last-activity: 2026-06-12
546-
last-update-date: 2026-05-26
547-
last-update: |
548-
The Dev Services Lifecycle group made significant progress, ensuring OpenShift, Kubernetes, and MongoDB services no longer start during augmentation. We also enabled reusing dev services containers across restarts and migrated the Kubernetes Dev Service to its new architecture. We're now tracking further work around scoping Dev Services config and adding tests for the old model.
549-
550-
(This status update was automatically generated using AI.)
551-
point-of-contact: "@holly-cummins (@<strong>Holly Cummins</strong> on Zulip), @ozangunalp (@<strong>Ozan Günalp</strong> on Zulip )"
552-
proposal: https://github.com/quarkusio/quarkus/discussions/47683
553-
discussion: https://quarkusio.zulipchat.com/#narrow/channel/187038-dev
554554
- title: "Observability.Next"
555555
board-url: "https://github.com/orgs/quarkusio/projects/42"
556556
short-description: |

0 commit comments

Comments
 (0)