ワーキング・グループ
Driving the future of Quarkus.
A working group is a small team of contributors collaborating on a specific topic or initiative within the Quarkus ecosystem. Each group drives progress in a focused area, such as new features, tools, or long-term improvements.
Joining a working group is a great way to get involved and help shape the future of Quarkus. If you're interested in participating, check the group's board or contact its point of contact.
You can also propose a new working group by opening a design discussion using the working group proposal template.
Active working groups
Staled or at risk working groups
These working groups either lack recent activity (i.e., have gone stale), are approaching a time-sensitive deadline, or are facing a technical blocker.
LTS versions
Quarkus LTS versions are managed as long-running working group to track releases and issues selection.
Completed working groups
These working groups have completed their work and are no longer active:
Gizmo 2
Description: Gizmo 2 related tasks
Completed on: March 13, 2025
Deliverable: TBD
Quarkus 3.15 LTS
Description: This WG focuses on defining the issues we would like to have in the next-to-be LTS (Quarkus 3.14/3.15)
Completed on: April 01, 2025
OIDC improvements
Description: 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
Completed on: March 28, 2025
Deliverable: TBD
Test classloading
Description: The goal of this working group is to rewrite Quarkus's test classloading, so that tests are run in the same classloader as the application under tests, and Quarkus extensions can do "Quarkus-y" manipulations of test classes.
Completed on: March 25, 2025
Quarkus 3.20 LTS
Description: This working group aims to track the effort around the Quarkus 3.20 LTS version.
Completed on: April 01, 2025
Unified Saga implementation
Description: The main objective of this working group is to unify Quarkus's story about Saga-based transactions.
Completed on: March 31, 2025
Deliverable: TBD
Roq :: Quarkus SSG
Description: Allow Static Site Generation with Quarkus.
Completed on: November 18, 2024
Deliverable: Quarkus Insight
Chappie
Description: The main objective of this working group is to allow AI features in Quarkus Dev Mode (Dev UI and CLI)
Completed on: March 27, 2025
Observability.Next
Description: Observability.Next is a strategic initiative to modernize the observability stack within the Quarkus framework, aiming to streamline and enhance its ability to monitor and manage distributed systems.
Completed on: March 31, 2025
WebSocket Next
Description: WebSocket-Next related tasks
Completed on: December 16, 2024
Deliverable: Quarkus Insight
Quarkus Config and IDEs
Description: Let's define a format for the files containing the config model we will include in the jars for IDE consumption.
Completed on: November 29, 2024
Enhanced TLS support
Description: Track the progress around the new TLS configuration centralization and new features (like Let's Encrypt, Cert-Manager, and local experience...)
Completed on: September 29, 2024
Deliverable: Quarkus Insight
Docker file generation
Description: A working group focusing on the generation of Dockerfile / ContainerFile
Completed on: March 13, 2025
Quarkus to the CommonHaus Foundation
Description: Work needed around moving Quarkus to foundation and streamline open governance.
Completed on: February 25, 2025
