You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: _data/wg.yaml
+54-54Lines changed: 54 additions & 54 deletions
Original file line number
Diff line number
Diff line change
@@ -37,12 +37,65 @@ working-groups:
37
37
status: on track
38
38
lts: false
39
39
completed: false
40
-
last-activity: 2026-06-11
40
+
last-activity: 2026-06-12
41
41
last-update-date: 2026-05-26
42
42
last-update: |
43
43
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.
44
44
45
45
(This status update was automatically generated using AI.)
The main objective of this working group is to convert our Jekyll-based website to one built on Roq.
50
+
readme: |
51
+
<h2>Objective:</h2>
52
+
<p>The main objective of this working group is to convert our Jekyll-based website to a Roq-based one.</p>
53
+
<h2>The Problem</h2>
54
+
<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>
55
+
<ul>
56
+
<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>
57
+
<li>The site build is temperamental. Local Ruby installations can break, and even the container-based build can break.</li>
58
+
</ul>
59
+
<h2>The proposed Solution</h2>
60
+
<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>
61
+
<h2>Definition of Done</h2>
62
+
<p>This working group is complete when the live quarkus.io site is based on Roq.</p>
63
+
<h2>Scope of Work</h2>
64
+
<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>
65
+
<h2>Organizing the Work</h2>
66
+
<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>
67
+
<h2>Expected Timeline:</h2>
68
+
<p>I expect about six months to be a suitable timescale.</p>
69
+
<p>As always, we will aim for an incremental delivery, although the final switch will be a big bang.</p>
70
+
<ul>
71
+
<li>Support building Roq sites in quarkus.io preview</li>
72
+
<li>Develop conversion scripts</li>
73
+
<li>Maintain a long-running PR, with scripts</li>
74
+
<li>Fill functionality gaps in Roq</li>
75
+
<li>(possibly) Split site and and ship some sub-sections as Roq, some as Jekyll</li>
76
+
</ul>
77
+
<h2>Potential Outcomes & Deliverables</h2>
78
+
<p>The deliverables of this working group include:</p>
The main objective of this working group is to convert our Jekyll-based website to one built on Roq.
267
-
readme: |
268
-
<h2>Objective:</h2>
269
-
<p>The main objective of this working group is to convert our Jekyll-based website to a Roq-based one.</p>
270
-
<h2>The Problem</h2>
271
-
<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>
272
-
<ul>
273
-
<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>
274
-
<li>The site build is temperamental. Local Ruby installations can break, and even the container-based build can break.</li>
275
-
</ul>
276
-
<h2>The proposed Solution</h2>
277
-
<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>
278
-
<h2>Definition of Done</h2>
279
-
<p>This working group is complete when the live quarkus.io site is based on Roq.</p>
280
-
<h2>Scope of Work</h2>
281
-
<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>
282
-
<h2>Organizing the Work</h2>
283
-
<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>
284
-
<h2>Expected Timeline:</h2>
285
-
<p>I expect about six months to be a suitable timescale.</p>
286
-
<p>As always, we will aim for an incremental delivery, although the final switch will be a big bang.</p>
287
-
<ul>
288
-
<li>Support building Roq sites in quarkus.io preview</li>
289
-
<li>Develop conversion scripts</li>
290
-
<li>Maintain a long-running PR, with scripts</li>
291
-
<li>Fill functionality gaps in Roq</li>
292
-
<li>(possibly) Split site and and ship some sub-sections as Roq, some as Jekyll</li>
293
-
</ul>
294
-
<h2>Potential Outcomes & Deliverables</h2>
295
-
<p>The deliverables of this working group include:</p>
0 commit comments