|
1 | 1 | --- |
2 | 2 | working-groups: |
| 3 | + - title: "OIDC improvements" |
| 4 | + board-url: "https://github.com/orgs/quarkusio/projects/46" |
| 5 | + short-description: | |
| 6 | + The goal of this working group is to improve quarkus-oidc by: implementing crucial new security features, continuing with improving the way OIDC requests can be intercepted, prioritizing some other open issues, such as using JWT bearer client authentication to complete the authorization code flow |
| 7 | + readme: | |
| 8 | + <p>The goal of this working group is to improve quarkus-oidc by: implementing crucial new security features, continuing with improving the way OIDC requests can be intercepted, prioritizing some other open issues, such as using JWT bearer client authentication to complete the authorization code flow</p> |
| 9 | + <ul> |
| 10 | + <li>Point of contact: @sberyozkin (@_<strong>Sergey Beryozkin</strong> on Zulip)</li> |
| 11 | + <li>Proposal: https://github.com/quarkusio/quarkus/discussions/42116</li> |
| 12 | + <li>Deliverable: TBD</li> |
| 13 | + </ul> |
| 14 | + status: on track |
| 15 | + lts: false |
| 16 | + completed: false |
| 17 | + last-activity: 2025-07-22 |
| 18 | + last-update-date: 2025-06-24 |
| 19 | + last-update: | |
| 20 | + In the past month, the WG - OIDC improvements has successfully closed an issue focused on providing migration guides for transitioning from Vert.x OIDC to Quarkus OIDC, enhancing the usability of the framework. No new issues were opened during this period, indicating a focus on completing existing tasks and improving the overall OIDC experience. |
| 21 | + |
| 22 | + (This status update was automatically generated using AI.) |
| 23 | + deliverable: TBD |
| 24 | + point-of-contact: "@sberyozkin (@_<strong>Sergey Beryozkin</strong> on Zulip)" |
| 25 | + proposal: https://github.com/quarkusio/quarkus/discussions/42116 |
| 26 | + - title: "Quarkus 4" |
| 27 | + board-url: "https://github.com/orgs/quarkusio/projects/51" |
| 28 | + short-description: | |
| 29 | + The Quarkus 4 working group aims to coordinate and track all Quarkus 4-related development in a long-running effort. |
| 30 | + readme: | |
| 31 | + <h2>Objective</h2> |
| 32 | + <p>This long‑running working group is dedicated to tracking development and ensuring a smooth rollout for Quarkus 4. It will serve as the central coordination point for feature tracking, release hygiene, migration guidance, and community alignment related to Quarkus 4.</p> |
| 33 | + <h2>The Problem</h2> |
| 34 | + <p>Quarkus 4 introduces significant shifts, including new Java 25 flags, architectural refinements, deprecations, and ecosystem changes. Without a focused group, efforts become fragmented, and downstream consumers (extensions, integrations, platform partners) may struggle to stay aligned.</p> |
| 35 | + <h2>Proposed Solution</h2> |
| 36 | + <p>Establish a designated WG to:</p> |
| 37 | + <ul> |
| 38 | + <li>Track all Quarkus 4‑related issues and PRs (using label triage/quarkus-4)</li> |
| 39 | + <li>Maintain a GitHub project board for feature status, blockers, and timelines</li> |
| 40 | + <li>Coordinate across teams (core, extensions, platform, tooling)</li> |
| 41 | + <li>Surface migration considerations and flag impacts (e.g. new --add-opens needs, optimized defaults) - useful to create the migration guide and rules</li> |
| 42 | + <li>Publish ADRs, migration guides, and summary docs</li> |
| 43 | + </ul> |
| 44 | + <h2>Definition of Done</h2> |
| 45 | + <p>This WG will be considered complete when:</p> |
| 46 | + <ul> |
| 47 | + <li>Quarkus 4 GA is released (including the platform)</li> |
| 48 | + <li>All major features are merged and tested</li> |
| 49 | + <li>Migration documentation is publicly available</li> |
| 50 | + </ul> |
| 51 | + <h2>Organizing the Work</h2> |
| 52 | + <p>Coordination via:</p> |
| 53 | + <ul> |
| 54 | + <li>GitHub Discussions: use design‑discussions category</li> |
| 55 | + <li>Issues/PRs: label with <code>triage/quarkus-4</code></li> |
| 56 | + <li>Project board to track status</li> |
| 57 | + </ul> |
| 58 | + <h2>Expected Timeline:</h2> |
| 59 | + <p>This is a long-running WG, starting now and wrapping up post‑GA (~late Q2 2026). We’ll mark it as “done” upon the public release of Quarkus 4 GA.</p> |
| 60 | + status: on track |
| 61 | + lts: false |
| 62 | + completed: false |
| 63 | + last-activity: 2025-07-22 |
| 64 | + last-update-date: 2025-07-22 |
| 65 | + last-update: | |
| 66 | + Working group started. |
3 | 67 | - title: "Quarkus to the CommonHaus Foundation" |
4 | 68 | board-url: "https://github.com/orgs/quarkusio/projects/38" |
5 | 69 | short-description: | |
@@ -38,29 +102,6 @@ working-groups: |
38 | 102 | In the last month, the WG - Quarkus to the CommonHaus Foundation successfully closed an issue related to setting up the recommended files necessary for the transition to the foundation. Additionally, a new issue was opened to enable a Sponsor button in the Quarkiverse, indicating ongoing efforts to enhance community engagement and streamline governance as Quarkus moves to CommonHaus Foundation. |
39 | 103 | |
40 | 104 | (This status update was automatically generated using AI.) |
41 | | - - title: "OIDC improvements" |
42 | | - board-url: "https://github.com/orgs/quarkusio/projects/46" |
43 | | - short-description: | |
44 | | - The goal of this working group is to improve quarkus-oidc by: implementing crucial new security features, continuing with improving the way OIDC requests can be intercepted, prioritizing some other open issues, such as using JWT bearer client authentication to complete the authorization code flow |
45 | | - readme: | |
46 | | - <p>The goal of this working group is to improve quarkus-oidc by: implementing crucial new security features, continuing with improving the way OIDC requests can be intercepted, prioritizing some other open issues, such as using JWT bearer client authentication to complete the authorization code flow</p> |
47 | | - <ul> |
48 | | - <li>Point of contact: @sberyozkin (@_<strong>Sergey Beryozkin</strong> on Zulip)</li> |
49 | | - <li>Proposal: https://github.com/quarkusio/quarkus/discussions/42116</li> |
50 | | - <li>Deliverable: TBD</li> |
51 | | - </ul> |
52 | | - status: on track |
53 | | - lts: false |
54 | | - completed: false |
55 | | - last-activity: 2025-07-21 |
56 | | - last-update-date: 2025-06-24 |
57 | | - last-update: | |
58 | | - In the past month, the WG - OIDC improvements has successfully closed an issue focused on providing migration guides for transitioning from Vert.x OIDC to Quarkus OIDC, enhancing the usability of the framework. No new issues were opened during this period, indicating a focus on completing existing tasks and improving the overall OIDC experience. |
59 | | - |
60 | | - (This status update was automatically generated using AI.) |
61 | | - deliverable: TBD |
62 | | - point-of-contact: "@sberyozkin (@_<strong>Sergey Beryozkin</strong> on Zulip)" |
63 | | - proposal: https://github.com/quarkusio/quarkus/discussions/42116 |
64 | 105 | - title: "Dev Services Lifecycle" |
65 | 106 | board-url: "https://github.com/orgs/quarkusio/projects/49" |
66 | 107 | short-description: | |
|
0 commit comments