List completed working groups in the working group page

Extend working group metadata to detect completed working groups.
Do not display completed working groups as cards.
Add a simple list at the bottom of the page.

Author: cescoffier

_data/wg.yaml

@@ -1,5 +1,32 @@
 ---
 working-groups:
+    - 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)
+      readme: |
+        <p>This working group uses a different board:</p>
+        <ul>
+        <li>The <code>under discussion</code> column contains the issues we would like to have in the next LTS but are still under consideration.</li>
+        <li>The <code>out of scope</code> column contains the issues under discussion' that won't be included. The reason can be time or technical...</li>
+        <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: on track
+      completed: false
+      last-activity: 2024-10-01
+      last-update: |
+        3.15 has been cut. 
+        The 3.15.x is the new LTS, starting with 3.15.1
+    - title: "Quarkus Config and IDEs"
+      board-url: "https://github.com/orgs/quarkusio/projects/32"
+      short-description: Let's define a format for the files containing the config model we will include in the jars for IDE consumption.
+      readme: |
+        <p>Let's define a format for the files containing the config model we will include in the jars for IDE consumption.</p>
+        <p>See https://github.com/quarkusio/quarkus/discussions/42671 for more details.</p>
+        <p><em>Point of contact</em>: @gsmet (Zulip: @_<strong>Guillaume Smet</strong> )</p>
+      status: on track
+      completed: false
+      last-activity: 2024-09-30
     - 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...)
@@ -9,6 +36,7 @@ working-groups:
         <p>The goal of this focus group is to continue integrating the TLS registry and improve Quarkus integration with certificate providers (Let's Encrypt, Cert-Manager). In addition, we would like to provide a frictionless local experience around TLS (i.e., without the infamous untrusted certificate screen).</p>
         <p><em>Point of contact:</em> @cescoffier (@<strong>Clement Escoffier</strong> on Zulip)</p>
       status: complete
+      completed: true
       last-activity: 2024-09-29
       last-update: |
         This working group is complete! 
@@ -43,25 +71,10 @@ working-groups:
         <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
+      completed: false
       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)
-      readme: |
-        <p>This working group uses a different board:</p>
-        <ul>
-        <li>The <code>under discussion</code> column contains the issues we would like to have in the next LTS but are still under consideration.</li>
-        <li>The <code>out of scope</code> column contains the issues under discussion' that won't be included. The reason can be time or technical...</li>
-        <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: on track
-      last-activity: 2024-09-29
-      last-update: |
-        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.
@@ -74,20 +87,12 @@ working-groups:
         <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>
       status: on track
+      completed: false
       last-activity: 2024-09-24
       last-update: |
         Since we don't have a target date, and progress is being made, I can declare this on track, with only a slightly murky conscience. 
         
         This is a big change, and one which doesn't lend itself well to dividing into smaller chunks. I'm keeping a spreadsheet of build results. In the CI runs, the number of failing jobs was 31 at the last update, and it is now 25. A number of suites, such as `integration-tests/devtools` were failing, and are now passing.
-    - title: "Quarkus Config and IDEs"
-      board-url: "https://github.com/orgs/quarkusio/projects/32"
-      short-description: Let's define a format for the files containing the config model we will include in the jars for IDE consumption.
-      readme: |
-        <p>Let's define a format for the files containing the config model we will include in the jars for IDE consumption.</p>
-        <p>See https://github.com/quarkusio/quarkus/discussions/42671 for more details.</p>
-        <p><em>Point of contact</em>: @gsmet (Zulip: @_<strong>Guillaume Smet</strong> )</p>
-      status: on track
-      last-activity: 2024-09-24
     - title: "Roq :: Quarkus SSG"
       board-url: "https://github.com/orgs/quarkiverse/projects/6"
       short-description: Allow Static Site Generation with Quarkus.
@@ -108,6 +113,7 @@ working-groups:
         <p>This effort is now tracked using a &quot;Working Group&quot; project: https://github.com/orgs/quarkiverse/projects/6</p>
         <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>
       status: on track
+      completed: false
       last-activity: 2024-09-23
       last-update: |
         0.0.3 has been released, it is the MVP version and allowed to publish the Roq blog: https://quarkiverse.io/quarkus-roq/posts/2024-08-29-welcome-to-roq/
@@ -133,6 +139,7 @@ working-groups:
         Once completed, this working group will be followed by other initiatives focusing on generating the Github Action and Tekton pipelines.</p>
         <p><em>Point of contact</em>: @iocanel (<code>Ioannis Canellos</code>on Zulip)</p>
       status: on track
+      completed: false
       last-activity: 2024-09-10
       last-update: |
         There is a first draft https://github.com/quarkusio/quarkus/pull/42316
@@ -151,6 +158,7 @@ working-groups:
         <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>
         <p>Point of contact: @mkouba (@<strong>Martin Kouba</strong>  on Zulip)</p>
       status: on track
+      completed: false
       last-activity: 2024-09-05
       last-update: |
         The last outstanding issue is OTel integration. @michalvavrik is working on a [pull request](https://github.com/quarkusio/quarkus/pull/41956). I will meet with Michal and Bruno in the coming weeks. The PR is quite massive and we need to review it carefully.

_includes/working-group-band.html

@@ -9,6 +9,7 @@
 
 
     {% for item in site.data.wg.working-groups %}
+    {% unless item.completed %}
     <div class="card">
       <div class="card-header">
         <p class="card-title">{{ item.title }}</p>
@@ -22,6 +23,24 @@
         <a href="{{ item.board-url }}" class="float-end"> View the {{ item.title }} Board <i class="fa-solid fa-chevron-right"></i></a>
       </div>
     </div>
+    {% endunless %}
     {% endfor %}      
   </div>
-</div>
+
+  <h2>Completed working groups</h2>
+  <p class="mt-0">
+    These working groups have completed their work and are no longer active:
+  </p>
+  <ul>
+    {% for item in site.data.wg.working-groups %}
+    {% if item.completed %}
+    <li>
+      <a href="{{ item.board-url }}">{{ item.title }} ({{ item.last-activity | date: '%B %d, %Y' }})</a>
+    </li>
+    {% endif %}
+    {% endfor %}
+  </ul>
+
+
+</div>
+

working-groups/main.java

@@ -208,6 +208,11 @@ public String getIndentedLastUpdate() {
             return lastUpdateBody.replaceAll("\n", "\n        ").trim();
         }
 
+        public boolean isCompleted() {
+            var last = getLastUpdate();
+            return last != null && last.status().equals("COMPLETE");
+        }
+
         public Status getStatus() {
             if (statusUpdates.isEmpty()) {
                 return Status.INACTIVE;

working-groups/templates/wg.yaml.template

@@ -7,6 +7,7 @@ working-groups:
       readme: |
         {board.getIndentedReadme().raw}
       status: {board.getBadgeText()}
+      completed: {board.isCompleted()}
       last-activity: {board.getLastActivityDate()}
       {#if board.getLastUpdate()  && board.getLastUpdate().body.trim()}
       last-update: |