Skip to content

Commit

Permalink
Sync working groups
Browse files Browse the repository at this point in the history
  • Loading branch information
@actions-user
actions-user committed Sep 29, 2024
1 parent 2f294c9 commit 3b7a07e
Showing 1 changed file with 36 additions and 35 deletions.
71 changes: 36 additions & 35 deletions _data/wg.yaml
View file
Original file line number Diff line number Diff line change
@@ -1,5 +1,37 @@
---
working-groups:
- title: "Quarkus to the CommonHaus Foundation"
board-url: "https://github.com/orgs/quarkusio/projects/38"
short-description: Work needed around moving Quarkus to foundation and streamline open governance.
readme: |
<p>from Discussion at https://github.com/quarkusio/quarkus/discussions/43013</p>
<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>
<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>
<h1>Goal</h1>
<p>Two parts</p>
<ul>
<li>setup Quarkus to have transparent and open governance</li>
<li>Go through the few but important requirements for a CommonHaus project.</li>
</ul>
<h1>Initial work items/questions:</h1>
<p>Current known list, but not limited to:</p>
<ul>
<li>identify design communication channels (i.e. #41973)</li>
<li>which repositories / code will move</li>
<li>impact (if any) on quarkiverse projects</li>
<li>how will trademarks work/change</li>
<li>identify running services and setup/maintain them (registry.quarkus.io, code.quarkus.io etc.)</li>
<li>add required metadata/files to the various repositories</li>
</ul>
<h1>Tracking</h1>
<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>
<h1>When will this working group be done?</h1>
<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>
<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>
status: on track
last-activity: 2024-09-29
last-update: |
Just got started.
- 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 @@ -11,10 +43,11 @@ working-groups:
<li>The <code>in progress</code> means that the work has started and should be completed before the TLS cut date</li>
<li>The <code>done</code> column means that the issues have been completed</li>
</ul>
status: at risk
last-activity: 2024-09-27
status: on track
last-activity: 2024-09-29
last-update: |
Work is progressing. Still items that will need to be cleaned. Thus still at risk but managable.
3.15 has been cut.
The 3.15.x is the new LTS, starting with 3.15.1
- 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.
Expand Down Expand Up @@ -70,38 +103,6 @@ working-groups:
The target is to have 1.0.0 the 1 October 2024.
For 1.0 we need pagination, tags and SEO.
- title: "Moving Quarkus to the CommonHaus Foundation"
board-url: "https://github.com/orgs/quarkusio/projects/38"
short-description: Work needed around moving Quarkus to foundation and streamline open governance.
readme: |
<p>from Discussion at https://github.com/quarkusio/quarkus/discussions/43013</p>
<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>
<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>
<h1>Goal</h1>
<p>Two parts</p>
<ul>
<li>setup Quarkus to have transparent and open governance</li>
<li>Go through the few but important requirements for a CommonHaus project.</li>
</ul>
<h1>Initial work items/questions:</h1>
<p>Current known list, but not limited to:</p>
<ul>
<li>identify design communication channels (i.e. #41973)</li>
<li>which repositories / code will move</li>
<li>impact (if any) on quarkiverse projects</li>
<li>how will trademarks work/change</li>
<li>identify running services and setup/maintain them (registry.quarkus.io, code.quarkus.io etc.)</li>
<li>add required metadata/files to the various repositories</li>
</ul>
<h1>Tracking</h1>
<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>
<h1>When will this working group be done?</h1>
<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>
<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>
status: on track
last-activity: 2024-09-20
last-update: |
Just got started.
- 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 Down

0 comments on commit 3b7a07e

Please sign in to comment.