|
1 | 1 | --- |
2 | 2 | working-groups: |
| 3 | + - title: "Quarkus to the CommonHaus Foundation" |
| 4 | + board-url: "https://github.com/orgs/quarkusio/projects/38" |
| 5 | + short-description: | |
| 6 | + Work needed around moving Quarkus to foundation and streamline open governance. |
| 7 | + readme: | |
| 8 | + <p>from Discussion at https://github.com/quarkusio/quarkus/discussions/43013</p> |
| 9 | + <p>We started the move of Quarkus to a foundation <a href="https://quarkus.io/blog/quarkus-in-a-foundation/">earlier this year</a> and recently <a href="https://quarkus.io/blog/quarkus-moving-to-commonhaus/">set the direction</a> towards <a href="https://www.commonhaus.org/">CommonHaus</a> and during the summer break the CommonHaus council <a href="https://github.com/commonhaus/foundation/pull/183">approved our request</a> to join.</p> |
| 10 | + <p>Thus, now the real work starts, and it's just fitting we set up a working group for the effort getting Quarkus to CommonHaus foundation.</p> |
| 11 | + <h1>Goal</h1> |
| 12 | + <p>Two parts</p> |
| 13 | + <ul> |
| 14 | + <li>setup Quarkus to have transparent and open governance</li> |
| 15 | + <li>Go through the few but important requirements for a CommonHaus project.</li> |
| 16 | + </ul> |
| 17 | + <h1>Initial work items/questions:</h1> |
| 18 | + <p>Current known list, but not limited to:</p> |
| 19 | + <ul> |
| 20 | + <li>identify design communication channels (i.e. #41973)</li> |
| 21 | + <li>which repositories / code will move</li> |
| 22 | + <li>impact (if any) on quarkiverse projects</li> |
| 23 | + <li>how will trademarks work/change</li> |
| 24 | + <li>identify running services and setup/maintain them (registry.quarkus.io, code.quarkus.io etc.)</li> |
| 25 | + <li>add required metadata/files to the various repositories</li> |
| 26 | + </ul> |
| 27 | + <h1>Tracking</h1> |
| 28 | + <p>We will use the working group board to track publicly all the known relevant work and questions.For the few exception cases where, for legal or personal constraints, the work must happen in private, we will post the outcome and results in public places (like a GitHub discussion of a GitHub issue tracked on the working group board).</p> |
| 29 | + <h1>When will this working group be done?</h1> |
| 30 | + <p>When Quarkus has an active working governance model in place and all major work items around setting up Quarkus at CommonHaus are completed - after that, its expected things will just be iteratively improved, and the dedicated working group will not be needed (others might start to continue more specific efforts).</p> |
| 31 | + <p>The majority of the work must be done before the end of December 2024. The latest deadline for CommonHaus is April 2025, when the bootstrap period of CommonHaus ends.</p> |
| 32 | + status: at risk |
| 33 | + lts: false |
| 34 | + completed: false |
| 35 | + last-activity: 2025-07-22 |
| 36 | + last-update-date: 2025-06-24 |
| 37 | + last-update: | |
| 38 | + 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 | + |
| 40 | + (This status update was automatically generated using AI.) |
3 | 41 | - title: "OIDC improvements" |
4 | 42 | board-url: "https://github.com/orgs/quarkusio/projects/46" |
5 | 43 | short-description: | |
@@ -322,44 +360,6 @@ working-groups: |
322 | 360 | last-update-date: 2025-04-01 |
323 | 361 | last-update: | |
324 | 362 | In the last month, the WG - Quarkus 3.15 LTS closed two issues: one regarding the assignment of random ports in the configuration and another updating the Kafka client version to 3.7.2 to address CVE-2024-56128. No new issues were opened, reflecting a commitment to resolving important topics for the upcoming LTS release. |
325 | | - - title: "Quarkus to the CommonHaus Foundation" |
326 | | - board-url: "https://github.com/orgs/quarkusio/projects/38" |
327 | | - short-description: | |
328 | | - Work needed around moving Quarkus to foundation and streamline open governance. |
329 | | - readme: | |
330 | | - <p>from Discussion at https://github.com/quarkusio/quarkus/discussions/43013</p> |
331 | | - <p>We started the move of Quarkus to a foundation <a href="https://quarkus.io/blog/quarkus-in-a-foundation/">earlier this year</a> and recently <a href="https://quarkus.io/blog/quarkus-moving-to-commonhaus/">set the direction</a> towards <a href="https://www.commonhaus.org/">CommonHaus</a> and during the summer break the CommonHaus council <a href="https://github.com/commonhaus/foundation/pull/183">approved our request</a> to join.</p> |
332 | | - <p>Thus, now the real work starts, and it's just fitting we set up a working group for the effort getting Quarkus to CommonHaus foundation.</p> |
333 | | - <h1>Goal</h1> |
334 | | - <p>Two parts</p> |
335 | | - <ul> |
336 | | - <li>setup Quarkus to have transparent and open governance</li> |
337 | | - <li>Go through the few but important requirements for a CommonHaus project.</li> |
338 | | - </ul> |
339 | | - <h1>Initial work items/questions:</h1> |
340 | | - <p>Current known list, but not limited to:</p> |
341 | | - <ul> |
342 | | - <li>identify design communication channels (i.e. #41973)</li> |
343 | | - <li>which repositories / code will move</li> |
344 | | - <li>impact (if any) on quarkiverse projects</li> |
345 | | - <li>how will trademarks work/change</li> |
346 | | - <li>identify running services and setup/maintain them (registry.quarkus.io, code.quarkus.io etc.)</li> |
347 | | - <li>add required metadata/files to the various repositories</li> |
348 | | - </ul> |
349 | | - <h1>Tracking</h1> |
350 | | - <p>We will use the working group board to track publicly all the known relevant work and questions.For the few exception cases where, for legal or personal constraints, the work must happen in private, we will post the outcome and results in public places (like a GitHub discussion of a GitHub issue tracked on the working group board).</p> |
351 | | - <h1>When will this working group be done?</h1> |
352 | | - <p>When Quarkus has an active working governance model in place and all major work items around setting up Quarkus at CommonHaus are completed - after that, its expected things will just be iteratively improved, and the dedicated working group will not be needed (others might start to continue more specific efforts).</p> |
353 | | - <p>The majority of the work must be done before the end of December 2024. The latest deadline for CommonHaus is April 2025, when the bootstrap period of CommonHaus ends.</p> |
354 | | - status: at risk |
355 | | - lts: false |
356 | | - completed: false |
357 | | - last-activity: 2025-06-24 |
358 | | - last-update-date: 2025-06-24 |
359 | | - last-update: | |
360 | | - 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. |
361 | | - |
362 | | - (This status update was automatically generated using AI.) |
363 | 363 | - title: "Unified Saga implementation" |
364 | 364 | board-url: "https://github.com/orgs/quarkusio/projects/48" |
365 | 365 | short-description: | |
@@ -471,13 +471,13 @@ working-groups: |
471 | 471 | <p>Let's define a format for the files containing the config model we will include in the jars for IDE consumption.</p> |
472 | 472 | <p>See https://github.com/quarkusio/quarkus/discussions/42671 for more details.</p> |
473 | 473 | <p><em>Point of contact</em>: @gsmet (Zulip: @_<strong>Guillaume Smet</strong> )</p> |
474 | | - status: staled |
| 474 | + status: paused |
475 | 475 | lts: false |
476 | 476 | completed: false |
477 | 477 | last-activity: 2024-11-29 |
478 | | - last-update-date: 2024-11-29 |
| 478 | + last-update-date: 2025-07-22 |
479 | 479 | last-update: | |
480 | | - I fixed a few issues in the doc generation but wasn't able to make much progress for this round. |
| 480 | + The working group has been paused due to a lack of progress for some time now. Let's revisit it in a few months. |
481 | 481 | - title: "Enhanced TLS support" |
482 | 482 | board-url: "https://github.com/orgs/quarkusio/projects/24" |
483 | 483 | short-description: | |
|
0 commit comments