Skip to content

Commit ad2fdfb

Browse files
actions-useractions-user
committed
Sync working groups
1 parent 82c637d commit ad2fdfb

File tree

1 file changed

+50
-50
lines changed

1 file changed

+50
-50
lines changed

‎_data/wg.yaml‎

Lines changed: 50 additions & 50 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,55 @@
11
---
22
working-groups:
3+
- title: "Offering Metadata and Tooling Integration"
4+
board-url: "https://github.com/orgs/quarkusio/projects/52"
5+
short-description: |
6+
Track and coordinate the introduction of offering-level support metadata in Quarkus platform descriptors and its integration into developer tools (e.g., code.quarkus.io, CLI).
7+
readme: |
8+
<h2>Motivation:</h2>
9+
<p>Quarkus is now part of multiple product offerings (e.g., Red Hat Build of Quarkus, Camel integrations, ...). To enable tooling and automation to reflect product-specific support levels, we need to:</p>
10+
<ul>
11+
<li>Extend the platform metadata with structured offering-level support indicators.</li>
12+
<li>Adapt code.quarkus.io and code.quarkus.redhat.com to display and filter based on offering.</li>
13+
<li>Plan for downstream use by the CLI, build tooling, and possibly SKU-based features.</li>
14+
</ul>
15+
<p>This working group ensures a coordinated effort across platform, metadata, and UI/UX teams to avoid fragmentation and deliver a coherent user experience.</p>
16+
<h2>Goals:</h2>
17+
<ul>
18+
<li>Define and adopt a standard metadata format for offering-level support annotations.</li>
19+
<li>Apply metadata consistently across all productized platform descriptors.</li>
20+
<li>Integrate offering awareness into code.quarkus.redhat.com:</li>
21+
<li>Display per-offering support levels.</li>
22+
<li>Allow filtering and navigation based on offering.</li>
23+
<li>Ensure the upstream site (code.quarkus.io) remains offering-agnostic.</li>
24+
<li>Evaluate CLI support for offering information</li>
25+
</ul>
26+
<h2>Scope:</h2>
27+
<p>In scope:</p>
28+
<ul>
29+
<li>JSON platform descriptor enhancements</li>
30+
<li>Tooling (code.quarkus.io/redhat.com) UI/UX changes</li>
31+
<li>CLI enhancements (optional, pending feasibility)</li>
32+
</ul>
33+
<p>Out of scope:</p>
34+
<ul>
35+
<li>
36+
<p>Modifying Quarkus runtime behavior based on offering</p>
37+
</li>
38+
<li>
39+
<p>License/SKU enforcement mechanisms</p>
40+
</li>
41+
<li>
42+
<p>Point of contact: @ia3andy (@<strong>Andy Damevin</strong> on Zulip) and @aloubyansky (@<strong>Alexey Loubyansky</strong> on Zulip)</p>
43+
</li>
44+
</ul>
45+
status: on track
46+
lts: false
47+
completed: false
48+
last-activity: 2025-11-03
49+
last-update-date: 2025-10-27
50+
last-update: |
51+
The working group is almost complete. The main remaining task is about extending the Quarkus CLI to handle offerings.
52+
point-of-contact: "@ia3andy (@<strong>Andy Damevin</strong> on Zulip) and @aloubyansky (@<strong>Alexey Loubyansky</strong> on Zulip)"
353
- title: "Java 25 support"
454
board-url: "https://github.com/orgs/quarkusio/projects/59"
555
short-description: |
@@ -256,56 +306,6 @@ working-groups:
256306
last-update: |
257307
DNS names have now been migrated to CommonHaus.
258308
There are still many tasks to finalize the move, but we are going there smoothly.
259-
- title: "Offering Metadata and Tooling Integration"
260-
board-url: "https://github.com/orgs/quarkusio/projects/52"
261-
short-description: |
262-
Track and coordinate the introduction of offering-level support metadata in Quarkus platform descriptors and its integration into developer tools (e.g., code.quarkus.io, CLI).
263-
readme: |
264-
<h2>Motivation:</h2>
265-
<p>Quarkus is now part of multiple product offerings (e.g., Red Hat Build of Quarkus, Camel integrations, ...). To enable tooling and automation to reflect product-specific support levels, we need to:</p>
266-
<ul>
267-
<li>Extend the platform metadata with structured offering-level support indicators.</li>
268-
<li>Adapt code.quarkus.io and code.quarkus.redhat.com to display and filter based on offering.</li>
269-
<li>Plan for downstream use by the CLI, build tooling, and possibly SKU-based features.</li>
270-
</ul>
271-
<p>This working group ensures a coordinated effort across platform, metadata, and UI/UX teams to avoid fragmentation and deliver a coherent user experience.</p>
272-
<h2>Goals:</h2>
273-
<ul>
274-
<li>Define and adopt a standard metadata format for offering-level support annotations.</li>
275-
<li>Apply metadata consistently across all productized platform descriptors.</li>
276-
<li>Integrate offering awareness into code.quarkus.redhat.com:</li>
277-
<li>Display per-offering support levels.</li>
278-
<li>Allow filtering and navigation based on offering.</li>
279-
<li>Ensure the upstream site (code.quarkus.io) remains offering-agnostic.</li>
280-
<li>Evaluate CLI support for offering information</li>
281-
</ul>
282-
<h2>Scope:</h2>
283-
<p>In scope:</p>
284-
<ul>
285-
<li>JSON platform descriptor enhancements</li>
286-
<li>Tooling (code.quarkus.io/redhat.com) UI/UX changes</li>
287-
<li>CLI enhancements (optional, pending feasibility)</li>
288-
</ul>
289-
<p>Out of scope:</p>
290-
<ul>
291-
<li>
292-
<p>Modifying Quarkus runtime behavior based on offering</p>
293-
</li>
294-
<li>
295-
<p>License/SKU enforcement mechanisms</p>
296-
</li>
297-
<li>
298-
<p>Point of contact: @ia3andy (@<strong>Andy Damevin</strong> on Zulip) and @aloubyansky (@<strong>Alexey Loubyansky</strong> on Zulip)</p>
299-
</li>
300-
</ul>
301-
status: on track
302-
lts: false
303-
completed: false
304-
last-activity: 2025-10-27
305-
last-update-date: 2025-10-27
306-
last-update: |
307-
The working group is almost complete. The main remaining task is about extending the Quarkus CLI to handle offerings.
308-
point-of-contact: "@ia3andy (@<strong>Andy Damevin</strong> on Zulip) and @aloubyansky (@<strong>Alexey Loubyansky</strong> on Zulip)"
309309
- title: "Observability.Next"
310310
board-url: "https://github.com/orgs/quarkusio/projects/42"
311311
short-description: |

0 commit comments

Comments
 (0)