Sync working groups

Author: actions-user

_data/wg.yaml

@@ -1,5 +1,57 @@
 ---
 working-groups:
+    - title: "Offering Metadata and Tooling Integration"
+      board-url: "https://github.com/orgs/quarkusio/projects/52"
+      short-description: |
+        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).
+      readme: |
+        <h2>Motivation:</h2>
+        <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>
+        <ul>
+        <li>Extend the platform metadata with structured offering-level support indicators.</li>
+        <li>Adapt code.quarkus.io and code.quarkus.redhat.com to display and filter based on offering.</li>
+        <li>Plan for downstream use by the CLI, build tooling, and possibly SKU-based features.</li>
+        </ul>
+        <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>
+        <h2>Goals:</h2>
+        <ul>
+        <li>Define and adopt a standard metadata format for offering-level support annotations.</li>
+        <li>Apply metadata consistently across all productized platform descriptors.</li>
+        <li>Integrate offering awareness into code.quarkus.redhat.com:</li>
+        <li>Display per-offering support levels.</li>
+        <li>Allow filtering and navigation based on offering.</li>
+        <li>Ensure the upstream site (code.quarkus.io) remains offering-agnostic.</li>
+        <li>Evaluate CLI support for offering information</li>
+        </ul>
+        <h2>Scope:</h2>
+        <p>In scope:</p>
+        <ul>
+        <li>JSON platform descriptor enhancements</li>
+        <li>Tooling (code.quarkus.io/redhat.com) UI/UX changes</li>
+        <li>CLI enhancements (optional, pending feasibility)</li>
+        </ul>
+        <p>Out of scope:</p>
+        <ul>
+        <li>
+        <p>Modifying Quarkus runtime behavior based on offering</p>
+        </li>
+        <li>
+        <p>License/SKU enforcement mechanisms</p>
+        </li>
+        <li>
+        <p>Point of contact: @ia3andy (@<strong>Andy Damevin</strong>  on Zulip) and @aloubyansky (@<strong>Alexey Loubyansky</strong>  on Zulip)</p>
+        </li>
+        </ul>
+      status: on track
+      lts: false
+      completed: false
+      last-activity: 2025-09-17
+      last-update-date: 2025-09-08
+      last-update: |
+        In the past month, the WG - Offering Metadata and Tooling Integration has made significant progress by closing several important issues. Notably, the group successfully implemented offering-based filtering, enhanced the ability to add filters using OR logic, and introduced a wildcard filter to display all extensions associated with a specific tag key, such as redhat-support. No new issues were opened during this period, indicating a focus on consolidating efforts and refining existing features.
+        
+        (This status update was automatically generated using AI.)
+      point-of-contact: "@ia3andy (@<strong>Andy Damevin</strong>  on Zulip) and @aloubyansky (@<strong>Alexey Loubyansky</strong>  on Zulip)"
     - title: "Test classloading"
       board-url: "https://github.com/orgs/quarkusio/projects/30"
       short-description: |
@@ -329,58 +381,6 @@ working-groups:
       last-update-date: 2025-09-08
       last-update: |
         We identified several improvements we want to make for Quarkus 4, typically related to Vert.x 5/ Netty 4.2 (to support HTTP/3, gRPC transcoding, etc.).
-    - title: "Offering Metadata and Tooling Integration"
-      board-url: "https://github.com/orgs/quarkusio/projects/52"
-      short-description: |
-        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).
-      readme: |
-        <h2>Motivation:</h2>
-        <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>
-        <ul>
-        <li>Extend the platform metadata with structured offering-level support indicators.</li>
-        <li>Adapt code.quarkus.io and code.quarkus.redhat.com to display and filter based on offering.</li>
-        <li>Plan for downstream use by the CLI, build tooling, and possibly SKU-based features.</li>
-        </ul>
-        <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>
-        <h2>Goals:</h2>
-        <ul>
-        <li>Define and adopt a standard metadata format for offering-level support annotations.</li>
-        <li>Apply metadata consistently across all productized platform descriptors.</li>
-        <li>Integrate offering awareness into code.quarkus.redhat.com:</li>
-        <li>Display per-offering support levels.</li>
-        <li>Allow filtering and navigation based on offering.</li>
-        <li>Ensure the upstream site (code.quarkus.io) remains offering-agnostic.</li>
-        <li>Evaluate CLI support for offering information</li>
-        </ul>
-        <h2>Scope:</h2>
-        <p>In scope:</p>
-        <ul>
-        <li>JSON platform descriptor enhancements</li>
-        <li>Tooling (code.quarkus.io/redhat.com) UI/UX changes</li>
-        <li>CLI enhancements (optional, pending feasibility)</li>
-        </ul>
-        <p>Out of scope:</p>
-        <ul>
-        <li>
-        <p>Modifying Quarkus runtime behavior based on offering</p>
-        </li>
-        <li>
-        <p>License/SKU enforcement mechanisms</p>
-        </li>
-        <li>
-        <p>Point of contact: @ia3andy (@<strong>Andy Damevin</strong>  on Zulip) and @aloubyansky (@<strong>Alexey Loubyansky</strong>  on Zulip)</p>
-        </li>
-        </ul>
-      status: on track
-      lts: false
-      completed: false
-      last-activity: 2025-09-08
-      last-update-date: 2025-09-08
-      last-update: |
-        In the past month, the WG - Offering Metadata and Tooling Integration has made significant progress by closing several important issues. Notably, the group successfully implemented offering-based filtering, enhanced the ability to add filters using OR logic, and introduced a wildcard filter to display all extensions associated with a specific tag key, such as redhat-support. No new issues were opened during this period, indicating a focus on consolidating efforts and refining existing features.
-        
-        (This status update was automatically generated using AI.)
-      point-of-contact: "@ia3andy (@<strong>Andy Damevin</strong>  on Zulip) and @aloubyansky (@<strong>Alexey Loubyansky</strong>  on Zulip)"
     - title: "Quarkus to the CommonHaus Foundation"
       board-url: "https://github.com/orgs/quarkusio/projects/38"
       short-description: |