Working Groups

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

Test classloading

Status: on track

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.

Last Activity: August 04, 2025

Point of Contact: @holly-cummins (@Holly Cummins on Zulip)

Gizmo 2

Status: on track

Description: Gizmo 2 related tasks

Last Activity: July 25, 2025

Point of Contact: @mkouba (@Martin Kouba on Zulip)

Offering Metadata and Tooling Integration

Status: on track

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).

Last Activity: July 24, 2025

Point of Contact: @ia3andy (@Andy Damevin on Zulip) and @aloubyansky (@Alexey Loubyansky on Zulip)

OIDC improvements

Status: on track

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

Last Activity: July 24, 2025

Point of Contact: @sberyozkin (@_Sergey Beryozkin on Zulip)

Unified Saga implementation

Status: on track

Description: The main objective of this working group is to unify Quarkus's story about Saga-based transactions.

Last Activity: July 24, 2025

Point of Contact: @xstefank (@Martin Stefanko|448453 on Zulip)

Quarkus 4

Status: on track

Description: The Quarkus 4 working group aims to coordinate and track all Quarkus 4-related development in a long-running effort.

Last Activity: July 24, 2025

Dev Services Lifecycle

Status: on track

Description: This working group will define and implement a consistent and configurable lifecycle model for Dev Services. It will shift the startup to the correct phase, enable optional reuse across dev and test modes, and clarify teardown and sharing behavior. The goal is to improve the developer experience.

Last Activity: July 18, 2025

Point of Contact: @holly-cummins (@Holly Cummins on Zulip), @ozangunalp (@Ozan Günalp on Zulip )

Panache.Next

Status: on track

Description: The primary objective of this working group is to develop the next version of Panache.

Last Activity: July 17, 2025

Point of Contact: @FroMage (@Stephane Epardaud on Zulip)

Observability.Next

Status: on track

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.

Last Activity: July 02, 2025

Point of Contact: @brunobat

Chappie

Status: on track

Description: The main objective of this working group is to allow AI features in Quarkus Dev Mode (Dev UI and CLI)

Last Activity: June 27, 2025

Point of Contact: @phillip-kruger (@Phillip Krüger on Zulip)

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.

Quarkus to the CommonHaus Foundation

Status: at risk

Description: Work needed around moving Quarkus to foundation and streamline open governance.

Last Activity: July 22, 2025

Docker file generation

Status: staled

Description: A working group focusing on the generation of Dockerfile / ContainerFile

Last Activity: October 31, 2024

LTS versions

Quarkus LTS versions are managed as long-running working group to track releases and issues selection.

Quarkus 3.20 LTS

Status: on track

Description: This working group aims to track the effort around the Quarkus 3.20 LTS version.

Last Activity: June 25, 2025

Quarkus 3.15 LTS

Status: on track

Description: This WG focuses on defining the issues we would like to have in the next-to-be LTS (Quarkus 3.14/3.15)

Last Activity: June 25, 2025

Paused working groups

These working groups have been paused (lack of bandwidth). If you are interested, feel free to reach out!

Quarkus Config and IDEs

Status: paused

Description: Let's define a format for the files containing the config model we will include in the jars for IDE consumption.

Last Activity: November 29, 2024

Completed working groups

These working groups have completed their work and are no longer active:

Roq :: Quarkus SSG

Description: Allow Static Site Generation with Quarkus.

Completed on: November 18, 2024

Deliverable: Quarkus Insight

WebSocket Next

Description: WebSocket-Next related tasks

Completed on: December 16, 2024

Deliverable: Quarkus Insight

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