Skip to content

Commit 309fd95

Browse files
committed
Sync working groups
1 parent 3569b44 commit 309fd95

File tree

1 file changed

+25
-25
lines changed

1 file changed

+25
-25
lines changed

_data/wg.yaml

Lines changed: 25 additions & 25 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,30 @@
11
---
22
working-groups:
3+
- title: "WebSocket Next"
4+
board-url: "https://github.com/orgs/quarkusio/projects/26"
5+
short-description: WebSocket-Next related tasks
6+
readme: |
7+
<p>The WebSocket Next <em>focus group</em> aims to improve our WebSocket experience.</p>
8+
<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>
9+
<ul>
10+
<li>Point of contact: @mkouba (@<strong>Martin Kouba</strong> on Zulip)</li>
11+
<li>Proposal: https://github.com/quarkusio/quarkus/discussions/38473</li>
12+
</ul>
13+
status: on track
14+
completed: false
15+
last-activity: 2024-11-20
16+
last-update-date: 2024-11-05
17+
last-update: |
18+
### Telemetry
19+
https://github.com/quarkusio/quarkus/pull/41956 was merged last week. @michalvavrik is going to send a pull request with Micrometer support this week.
20+
21+
### Performance
22+
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.
23+
The CDI request context is only activated if needed: https://github.com/quarkusio/quarkus/pull/43915.
24+
25+
I hope that WS Next will be feature-complete at the time of 3.17 release.
26+
point-of-contact: "@mkouba (@<strong>Martin Kouba</strong> on Zulip)"
27+
proposal: https://github.com/quarkusio/quarkus/discussions/38473
328
- title: "Roq :: Quarkus SSG"
429
board-url: "https://github.com/orgs/quarkiverse/projects/6"
530
short-description: Allow Static Site Generation with Quarkus.
@@ -56,31 +81,6 @@ working-groups:
5681
deliverable: <a rel="nofollow" href="https://www.youtube.com/watch?v=VP7c9ftFwrQ">Quarkus Insight</a>
5782
point-of-contact: "@cescoffier (@<strong>Clement Escoffier</strong> on Zulip)"
5883
proposal: https://github.com/quarkusio/quarkus/discussions/41024
59-
- title: "WebSocket Next"
60-
board-url: "https://github.com/orgs/quarkusio/projects/26"
61-
short-description: WebSocket-Next related tasks
62-
readme: |
63-
<p>The WebSocket Next <em>focus group</em> aims to improve our WebSocket experience.</p>
64-
<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>
65-
<ul>
66-
<li>Point of contact: @mkouba (@<strong>Martin Kouba</strong> on Zulip)</li>
67-
<li>Proposal: https://github.com/quarkusio/quarkus/discussions/38473</li>
68-
</ul>
69-
status: on track
70-
completed: false
71-
last-activity: 2024-11-19
72-
last-update-date: 2024-11-05
73-
last-update: |
74-
### Telemetry
75-
https://github.com/quarkusio/quarkus/pull/41956 was merged last week. @michalvavrik is going to send a pull request with Micrometer support this week.
76-
77-
### Performance
78-
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.
79-
The CDI request context is only activated if needed: https://github.com/quarkusio/quarkus/pull/43915.
80-
81-
I hope that WS Next will be feature-complete at the time of 3.17 release.
82-
point-of-contact: "@mkouba (@<strong>Martin Kouba</strong> on Zulip)"
83-
proposal: https://github.com/quarkusio/quarkus/discussions/38473
8484
- title: "Test classloading"
8585
board-url: "https://github.com/orgs/quarkusio/projects/30"
8686
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.

0 commit comments

Comments
 (0)