Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rework the working group page #2169

Merged
merged 1 commit into from
Nov 19, 2024
Merged

Rework the working group page #2169

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
119 changes: 64 additions & 55 deletions _data/wg.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,54 +1,5 @@
---
working-groups:
- title: "WebSocket Next"
board-url: "https://github.com/orgs/quarkusio/projects/26"
short-description: WebSocket-Next related tasks
readme: |
<p>The WebSocket Next <em>focus group</em> aims to improve our WebSocket experience.</p>
<p>Recently, we delivered a new approach to dealing with WebSocket (both for the server and client). This was the first step. There are still a few areas to improve, such as documentation, security, observability, and testability. The goal of this focus group is to track these efforts.</p>
<ul>
<li>Point of contact: @mkouba (@<strong>Martin Kouba</strong> on Zulip)</li>
<li>Discussion: https://github.com/quarkusio/quarkus/discussions/38473</li>
</ul>
status: on track
completed: false
last-activity: 2024-11-19
last-update: |
### Telemetry
https://github.com/quarkusio/quarkus/pull/41956 was merged last week. @michalvavrik is going to send a pull request with Micrometer support this week.

### Performance
Two problems were addressed in Vert.x: https://github.com/eclipse-vertx/vert.x/pull/5358 and https://github.com/eclipse-vertx/vert.x/pull/5348.
The CDI request context is only activated if needed: https://github.com/quarkusio/quarkus/pull/43915.

I hope that WS Next will be feature-complete at the time of 3.17 release.
point-of-contact: "@mkouba (@<strong>Martin Kouba</strong> on Zulip)"
discussion: https://github.com/quarkusio/quarkus/discussions/38473
- title: "Test classloading"
board-url: "https://github.com/orgs/quarkusio/projects/30"
short-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.
readme: |
<p>At the moment, Quarkus tests are invoked using one classloader, and then executed in a different classloader. This mostly works well, but means some use cases don't work: extensions cannot manipulate test classes in the same way that they do normal application classes. For example, anything run via a JUnit @TestTemplate test case will see the un-transformed class.</p>
<p>It also means we have extra user-facing complexity, such as the QuarkusTest*Callbacks](https://quarkus.io/guides/getting-started-testing#enrichment-via-quarkustestcallback):</p>
<blockquote>
<p>While it is possible to use JUnit Jupiter callback interfaces like BeforeEachCallback, you might run into classloading issues because Quarkus has to run tests in a custom classloader which JUnit is not aware of.</p>
</blockquote>
<p>A final benefit is a reduction in the internal complexity of our code. Hopping between classloaders during test execution takes a lot of work, and adds a lot of code! It also is brittle in places. For example, because the hop between classloaders relies on serialization in some cases, it's becoming harder to do as the JVM tightens up security restrictions. We used to rely on xstream, but that stopped working in Java 17. In https://github.com/quarkusio/quarkus/pull/40601, @dmlloyd moved us to use the JBoss Serializer, which works better, but might still be affected by future restrictions on class access.</p>
<p>The goal of this working group is to allow test classes to fully participate in the 'quarkification' of classes. The mechanism for this is probably just to load the test classes with the classloader we intend to run them with, so that JUnit sees the 'correct' version of the class.</p>
<ul>
<li>Point of contact: @holly-cummins (@<strong>Holly Cummins</strong> on Zulip)</li>
<li>Discussion: https://github.com/quarkusio/quarkus/discussions/41867</li>
<li>Chat: <a href="https://quarkusio.zulipchat.com/#narrow/channel/187038-dev/topic/WG.20.2330.20Test.20Classloading.20chatter/">Zulip topic</a></li>
</ul>
status: on track
completed: false
last-activity: 2024-11-19
last-update: |
A few pre-existing issues have been added to this project, since we're pretty confident the rewrite will either fix them, or unlock the next step for the fix.

Progress on the main work item has been delayed by conferences!
point-of-contact: "@holly-cummins (@<strong>Holly Cummins</strong> on Zulip)"
discussion: https://github.com/quarkusio/quarkus/discussions/41867
- title: "Roq :: Quarkus SSG"
board-url: "https://github.com/orgs/quarkiverse/projects/6"
short-description: Allow Static Site Generation with Quarkus.
Expand All @@ -70,17 +21,18 @@ working-groups:
<p>This is a great opportunity to participate in fun effort and be involved with the Quarkus community, if anyone is interested in being a part of this, please reach out to me 🚀</p>
<ul>
<li>Point of contact: @ia3andy</li>
<li>Discussion: https://github.com/quarkusio/quarkus/discussions/41309</li>
<li>Proposal: https://github.com/quarkusio/quarkus/discussions/41309</li>
<li>Deliverable: <a href="https://www.youtube.com/live/hrF1a5sKqBI">Quarkus Insight</a></li>
</ul>
status: complete
completed: true
last-activity: 2024-11-18
last-activity: 2024-11-19
last-update-date: 2024-11-18
last-update: |
ROQ has been released! See https://www.youtube.com/live/hrF1a5sKqBI to see ROQ in action.
deliverable: <a rel="nofollow" href="https://www.youtube.com/live/hrF1a5sKqBI">Quarkus Insight</a>
point-of-contact: "@ia3andy"
discussion: https://github.com/quarkusio/quarkus/discussions/41309
proposal: https://github.com/quarkusio/quarkus/discussions/41309
- title: "Enhanced TLS support"
board-url: "https://github.com/orgs/quarkusio/projects/24"
short-description: Track the progress around the new TLS configuration centralization and new features (like Let's Encrypt, Cert-Manager, and local experience...)
Expand All @@ -91,18 +43,71 @@ working-groups:
<ul>
<li>Point of contact: @cescoffier (@<strong>Clement Escoffier</strong> on Zulip)</li>
<li>Deliverable: <a href="https://www.youtube.com/watch?v=VP7c9ftFwrQ">Quarkus Insight</a></li>
<li>Discussion: https://github.com/quarkusio/quarkus/discussions/41024</li>
<li>Proposal: https://github.com/quarkusio/quarkus/discussions/41024</li>
</ul>
status: complete
completed: true
last-activity: 2024-11-18
last-activity: 2024-11-19
last-update-date: 2024-09-29
last-update: |
This working group is complete!
That does not mean that no work will be done around TLS, but what was defined in the initial scope of the working group has been completed.
Enhancements and bug fixes will follow.
deliverable: <a rel="nofollow" href="https://www.youtube.com/watch?v=VP7c9ftFwrQ">Quarkus Insight</a>
point-of-contact: "@cescoffier (@<strong>Clement Escoffier</strong> on Zulip)"
discussion: https://github.com/quarkusio/quarkus/discussions/41024
proposal: https://github.com/quarkusio/quarkus/discussions/41024
- title: "WebSocket Next"
board-url: "https://github.com/orgs/quarkusio/projects/26"
short-description: WebSocket-Next related tasks
readme: |
<p>The WebSocket Next <em>focus group</em> aims to improve our WebSocket experience.</p>
<p>Recently, we delivered a new approach to dealing with WebSocket (both for the server and client). This was the first step. There are still a few areas to improve, such as documentation, security, observability, and testability. The goal of this focus group is to track these efforts.</p>
<ul>
<li>Point of contact: @mkouba (@<strong>Martin Kouba</strong> on Zulip)</li>
<li>Proposal: https://github.com/quarkusio/quarkus/discussions/38473</li>
</ul>
status: on track
completed: false
last-activity: 2024-11-19
last-update-date: 2024-11-05
last-update: |
### Telemetry
https://github.com/quarkusio/quarkus/pull/41956 was merged last week. @michalvavrik is going to send a pull request with Micrometer support this week.

### Performance
Two problems were addressed in Vert.x: https://github.com/eclipse-vertx/vert.x/pull/5358 and https://github.com/eclipse-vertx/vert.x/pull/5348.
The CDI request context is only activated if needed: https://github.com/quarkusio/quarkus/pull/43915.

I hope that WS Next will be feature-complete at the time of 3.17 release.
point-of-contact: "@mkouba (@<strong>Martin Kouba</strong> on Zulip)"
proposal: https://github.com/quarkusio/quarkus/discussions/38473
- title: "Test classloading"
board-url: "https://github.com/orgs/quarkusio/projects/30"
short-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.
readme: |
<p>At the moment, Quarkus tests are invoked using one classloader, and then executed in a different classloader. This mostly works well, but means some use cases don't work: extensions cannot manipulate test classes in the same way that they do normal application classes. For example, anything run via a JUnit @TestTemplate test case will see the un-transformed class.</p>
<p>It also means we have extra user-facing complexity, such as the QuarkusTest*Callbacks](https://quarkus.io/guides/getting-started-testing#enrichment-via-quarkustestcallback):</p>
<blockquote>
<p>While it is possible to use JUnit Jupiter callback interfaces like BeforeEachCallback, you might run into classloading issues because Quarkus has to run tests in a custom classloader which JUnit is not aware of.</p>
</blockquote>
<p>A final benefit is a reduction in the internal complexity of our code. Hopping between classloaders during test execution takes a lot of work, and adds a lot of code! It also is brittle in places. For example, because the hop between classloaders relies on serialization in some cases, it's becoming harder to do as the JVM tightens up security restrictions. We used to rely on xstream, but that stopped working in Java 17. In https://github.com/quarkusio/quarkus/pull/40601, @dmlloyd moved us to use the JBoss Serializer, which works better, but might still be affected by future restrictions on class access.</p>
<p>The goal of this working group is to allow test classes to fully participate in the 'quarkification' of classes. The mechanism for this is probably just to load the test classes with the classloader we intend to run them with, so that JUnit sees the 'correct' version of the class.</p>
<ul>
<li>Point of contact: @holly-cummins (@<strong>Holly Cummins</strong> on Zulip)</li>
<li>Proposal: https://github.com/quarkusio/quarkus/discussions/41867</li>
<li>Discussion: <a href="https://quarkusio.zulipchat.com/#narrow/channel/187038-dev/topic/WG.20.2330.20Test.20Classloading.20chatter/">Zulip topic</a></li>
</ul>
status: on track
completed: false
last-activity: 2024-11-19
last-update-date: 2024-10-29
last-update: |
A few pre-existing issues have been added to this project, since we're pretty confident the rewrite will either fix them, or unlock the next step for the fix.

Progress on the main work item has been delayed by conferences!
point-of-contact: "@holly-cummins (@<strong>Holly Cummins</strong> on Zulip)"
proposal: https://github.com/quarkusio/quarkus/discussions/41867
discussion: https://quarkusio.zulipchat.com/#narrow/channel/187038-dev/topic/WG.20.2330.20Test.20Classloading.20chatter/
- title: "Quarkus 3.15 LTS"
board-url: "https://github.com/orgs/quarkusio/projects/28"
short-description: This WG focuses on defining the issues we would like to have in the next-to-be LTS (Quarkus 3.14/3.15)
Expand All @@ -117,6 +122,7 @@ working-groups:
status: on track
completed: false
last-activity: 2024-11-13
last-update-date: 2024-10-28
last-update: |
Everything is fine for now.

Expand All @@ -139,6 +145,7 @@ working-groups:
status: on track
completed: false
last-activity: 2024-10-31
last-update-date: 2024-09-27
last-update: |
There is a first draft https://github.com/quarkusio/quarkus/pull/42316
The PR introduces a CLI plugin that generates a Dockerfile.
Expand Down Expand Up @@ -179,6 +186,7 @@ working-groups:
status: on track
completed: false
last-activity: 2024-10-28
last-update-date: 2024-10-28
last-update: |
Still on track.
In the last period, we organized an international manhunt to find the owner of the quarkus.dev DNS name :-) We were able to identify the owner, and everything is fine. `quarkus.io` and `quarkus.dev` should be transferred to the foundation at some point.
Expand All @@ -194,6 +202,7 @@ working-groups:
status: on track
completed: false
last-activity: 2024-10-03
last-update-date: 2024-10-29
last-update: |
The main missing piece for now is the Asciidoctor -> Markdown transformer. I did a first try with some regexp-based parser but it was too limited for some of the content we have (mostly complex tables). I have another lead as someone actually wrote a Java Asciidoctor parser. The only problem is that the HTML transformation is intertwined with the parser. I need to split them and then create a Markdown document from there. Making slow progress as time permits.

Expand Down
17 changes: 12 additions & 5 deletions _includes/working-group-band.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -21,12 +21,19 @@
{% if item.point-of-contact %}
<p class="card-text"><span class="key">Point of Contact:</span>&nbsp;<span class="point-of-contact">{{ item.point-of-contact }}</span></p>
{% endif %}
</div>
<div class="card-footer">
<div class="icons">
{% if item.proposal %}
<a href="{{ item.proposal }}" title="See the working group proposal"><i class="icon fa-regular fa-file-lines"></i></i></a>&nbsp;
{% endif %}
<a href="{{ item.board-url }}" title="View the working group board"><i class="icon fa-brands fa-square-github"></i></a>&nbsp;
{% if item.discussion %}
<p class="card-text"><span class="key">Discussion:</span>&nbsp;<a class="discussion" href="{{ item.discussion }}">Link</a></p>
<a href="{{ item.discussion }}" title="Discuss about the working group"><i class="icon fa-solid fa-comments"></i></i></a>&nbsp;
{% else %}
<a href="https://quarkusio.zulipchat.com/#narrow/stream/187038-dev" title="Discuss about the working group"><i class="icon fa-solid fa-comments"></i></a>
{% endif %}
</div>
<div class="card-footer">
<a href="{{ item.board-url }}" class="float-end"> View the {{ item.title }} Board <i class="fa-solid fa-chevron-right"></i></a>
</div>
</div>
</div>
{% endunless %}
Expand All @@ -46,7 +53,7 @@ <h2>Completed working groups</h2>
</div>
<div class="card-body">
<p class="card-text"><span class="key">Description:</span>&nbsp;<span class="short-description">{{ item.short-description }}</span></p>
<p class="card-text"><span class="key">Completed on:</span>&nbsp;<span class="last-activity">{{ item.last-activity | date: '%B %d, %Y' }} </span></p>
<p class="card-text"><span class="key">Completed on:</span>&nbsp;<span class="last-activity">{{ item.last-update-date | date: '%B %d, %Y' }} </span></p>
{% if item.deliverable %}
<p class="card-text"><span class="key">Deliverable:</span>&nbsp;<span class="deliverable">{{ item.deliverable }}</span></p>
{% endif %}
Expand Down
28 changes: 24 additions & 4 deletions _sass/layouts/working-groups.scss
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -25,14 +25,12 @@
}

.card-header {
padding-bottom: 5px;
border-bottom: 1px solid var(--card-outline);
height: 2rem
height: fit-content
}

.card-body {
padding: 1rem 0rem;
height: 15rem;
padding: 1rem 0rem;
}

.card-completed {
Expand All @@ -42,11 +40,28 @@
.card-footer {
padding-top: 10px;
border-top: 1px solid var(--card-outline);

.icons {
display: flex;
height: 10vh;
align-items: center;
align-content: flex-start;
font-size: xx-large;
text-align: center;
vertical-align: bottom;
color: var(--card-outline);
justify-content: center;
flex-wrap: nowrap;
flex-direction: row;
}
}



.card-title {
font-size: 1.25rem;
font-weight: 400;
margin-bottom: 0.5rem;
}

.card-text {
Expand All @@ -62,10 +77,15 @@
position: relative;
word-wrap: break-word;
background-clip: border-box;
align-items: start;
padding: 1rem;
border-radius: 10px;
border: 1px solid var(--card-outline);
width: calc(100% - 2rem);
grid-column: span 4;
justify-content: center;
justify-items: stretch;
align-content: space-between;

grid-column: span 4;

Expand Down
Loading