Sync working groups

Author: actions-user

_data/wg.yaml

@@ -1,5 +1,52 @@
 ---
 working-groups:
+    - title: "Unified Saga implementation"
+      board-url: "https://github.com/orgs/quarkusio/projects/48"
+      short-description: |
+        The main objective of this working group is to unify Quarkus's story about Saga-based transactions.
+      readme: |
+        <h3>Objective:</h3>
+        <p>The main objective of this working group is to unify Quarkus's story about Saga-based transactions.</p>
+        <h3>The Problem</h3>
+        <p>The primary saga solution for distributed transactions is <a href="https://github.com/quarkusio/quarkus/tree/main/extensions/narayana-lra">narayana-lra</a> extension. However, it wasn't maintained and marketed as the number one solution for distributed sagas. So we either need to update LRA to make a unified solution for Quarkus or pick a different solution that was introduced in the meantime. This WG will unify Quarkus's story in a distributed transaction solution.</p>
+        <h3>The proposed Solution</h3>
+        <p>We will investigate and compare available solutions for the saga-based implementation of the distributed tx processing. This will be documented, and the choice should be proven to be able to drive development and innovation in this area. We will ensure the solution meets the Quarkus standards (build/runtime split, dev service, dev ui).</p>
+        <h3>Definition of Done</h3>
+        <ul>
+        <li>A new guide for the distributed tx (or the chosen solution if there is only one)</li>
+        <li>Blog post comparing available solutions or just marketing the chosen solution</li>
+        <li>Quarkus insights about this topic</li>
+        </ul>
+        <h3>Scope of Work</h3>
+        <p>The scope of this WG is to pick a chosen saga-based implementation and make it Quarkus native (dev mode, any possible enhancements). We will choose implementation with an already available Quarkus integration. Research of new saga-based alternatives is out of scope.</p>
+        <h3>Organizing the Work</h3>
+        <p>Communication and Transparency:</p>
+        <p>Coordination will be done in this GitHub discussion and the individual GitHub issues. GitHub issues can be closed if the saga-solution is not to be updated anymore. The decision of the chosen solution will be stated also as the resolution of https://github.com/quarkusio/quarkus/issues/34181.</p>
+        <p>This work can take place in either Quarkus core (narayana-lra) or some new extension that will be provided in Quarkiverse.</p>
+        <h3>Expected Timeline:</h3>
+        <p>Milestone 1 - Document in this discussion saga-based implementations alternatives
+        Milestone 2 - Pick one solution that will be Quarkus Saga solution
+        Milestone 3 - Update the chosen alternative for Quarkus standards (simplification of use, dev * features)
+        Milestone 4 - Create a guide to document it
+        Milestone 5 - Blog + Quarkus insights</p>
+        <hr />
+        <ul>
+        <li>Point of contact: @xstefank (@<strong>Martin Stefanko|448453</strong>  on Zulip)</li>
+        <li>Proposal: https://github.com/quarkusio/quarkus/discussions/46672</li>
+        <li>Deliverable: TBD</li>
+        </ul>
+      status: on track
+      lts: false
+      completed: false
+      last-activity: 2026-05-01
+      last-update-date: 2026-03-30
+      last-update: |
+        We've enabled the Narayana JTA Recovery service by default. For Quarkus 3.27, the flaky LRA TCK tests were addressed, but they're still under active investigation.
+        
+        (This status update was automatically generated using AI.)
+      deliverable: TBD
+      point-of-contact: "@xstefank (@<strong>Martin Stefanko|448453</strong>  on Zulip)"
+      proposal: https://github.com/quarkusio/quarkus/discussions/46672
     - title: "Java 25 support"
       board-url: "https://github.com/orgs/quarkusio/projects/59"
       short-description: |
@@ -360,53 +407,6 @@ working-groups:
       point-of-contact: "@holly-cummins and @ia3andy"
       proposal: https://github.com/quarkusio/quarkus/discussions/53541
       discussion: https://quarkusio.zulipchat.com/#narrow/channel/187038-dev
-    - title: "Unified Saga implementation"
-      board-url: "https://github.com/orgs/quarkusio/projects/48"
-      short-description: |
-        The main objective of this working group is to unify Quarkus's story about Saga-based transactions.
-      readme: |
-        <h3>Objective:</h3>
-        <p>The main objective of this working group is to unify Quarkus's story about Saga-based transactions.</p>
-        <h3>The Problem</h3>
-        <p>The primary saga solution for distributed transactions is <a href="https://github.com/quarkusio/quarkus/tree/main/extensions/narayana-lra">narayana-lra</a> extension. However, it wasn't maintained and marketed as the number one solution for distributed sagas. So we either need to update LRA to make a unified solution for Quarkus or pick a different solution that was introduced in the meantime. This WG will unify Quarkus's story in a distributed transaction solution.</p>
-        <h3>The proposed Solution</h3>
-        <p>We will investigate and compare available solutions for the saga-based implementation of the distributed tx processing. This will be documented, and the choice should be proven to be able to drive development and innovation in this area. We will ensure the solution meets the Quarkus standards (build/runtime split, dev service, dev ui).</p>
-        <h3>Definition of Done</h3>
-        <ul>
-        <li>A new guide for the distributed tx (or the chosen solution if there is only one)</li>
-        <li>Blog post comparing available solutions or just marketing the chosen solution</li>
-        <li>Quarkus insights about this topic</li>
-        </ul>
-        <h3>Scope of Work</h3>
-        <p>The scope of this WG is to pick a chosen saga-based implementation and make it Quarkus native (dev mode, any possible enhancements). We will choose implementation with an already available Quarkus integration. Research of new saga-based alternatives is out of scope.</p>
-        <h3>Organizing the Work</h3>
-        <p>Communication and Transparency:</p>
-        <p>Coordination will be done in this GitHub discussion and the individual GitHub issues. GitHub issues can be closed if the saga-solution is not to be updated anymore. The decision of the chosen solution will be stated also as the resolution of https://github.com/quarkusio/quarkus/issues/34181.</p>
-        <p>This work can take place in either Quarkus core (narayana-lra) or some new extension that will be provided in Quarkiverse.</p>
-        <h3>Expected Timeline:</h3>
-        <p>Milestone 1 - Document in this discussion saga-based implementations alternatives
-        Milestone 2 - Pick one solution that will be Quarkus Saga solution
-        Milestone 3 - Update the chosen alternative for Quarkus standards (simplification of use, dev * features)
-        Milestone 4 - Create a guide to document it
-        Milestone 5 - Blog + Quarkus insights</p>
-        <hr />
-        <ul>
-        <li>Point of contact: @xstefank (@<strong>Martin Stefanko|448453</strong>  on Zulip)</li>
-        <li>Proposal: https://github.com/quarkusio/quarkus/discussions/46672</li>
-        <li>Deliverable: TBD</li>
-        </ul>
-      status: on track
-      lts: false
-      completed: false
-      last-activity: 2026-04-27
-      last-update-date: 2026-03-30
-      last-update: |
-        We've enabled the Narayana JTA Recovery service by default. For Quarkus 3.27, the flaky LRA TCK tests were addressed, but they're still under active investigation.
-        
-        (This status update was automatically generated using AI.)
-      deliverable: TBD
-      point-of-contact: "@xstefank (@<strong>Martin Stefanko|448453</strong>  on Zulip)"
-      proposal: https://github.com/quarkusio/quarkus/discussions/46672
     - title: "Dev Star"
       board-url: "https://github.com/orgs/quarkusio/projects/75"
       short-description: |