Remove last activity and improve dates in the working group page

Author: cescoffier

_data/wg.yaml

@@ -12,7 +12,7 @@ working-groups:
         <li>The <code>done</code> column means that the issues have been completed</li>
         </ul>
       status: at risk
-      last-activity: 19/08/2024
+      last-activity: 2024-08-19
     - 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...)
@@ -22,7 +22,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: on track
-      last-activity: 19/08/2024
+      last-activity: 2024-08-19
       last-update: We just got an end-to-end let's encrypt demo working!
     - title: "Test classloading"
       board-url: "https://github.com/orgs/quarkusio/projects/30"
@@ -36,7 +36,7 @@ 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
-      last-activity: 18/08/2024
+      last-activity: 2024-08-18
     - title: "Roq :: Quarkus SSG"
       board-url: "https://github.com/orgs/quarkiverse/projects/6"
       short-description: Allow Static Site Generation with Quarkus.
@@ -57,7 +57,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
-      last-activity: 16/08/2024
+      last-activity: 2024-08-16
       last-update: Good progress so far.
     - title: "Docker file generation"
       board-url: "https://github.com/orgs/quarkusio/projects/27"
@@ -75,7 +75,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
-      last-activity: 05/08/2024
+      last-activity: 2024-08-05
     - title: "WebSocket Next"
       board-url: "https://github.com/orgs/quarkusio/projects/26"
       short-description: WebSocket-Next related tasks
@@ -84,4 +84,4 @@ 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: staled
-      last-activity: 24/07/2024
+      last-activity: 2024-07-24

_includes/working-group-band.html

@@ -16,8 +16,7 @@
       <div class="card-body">
         <p class="card-text"><span class="key">Status:</span>&nbsp;<span class="status {{ item.status | | replace: ' ', '-'}}">{{ item.status }}</span></p>
         <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">Last Activity:</span>&nbsp;<span class="last-activity">{{ item.last-activity }}</span></p>
-        {% if item.last-update %}<p class="card-text"><span class="key">Last status update:</span>&nbsp;<span class="last-update">{{ item.last-update }}</span></p>{% endif %}      
+        <p class="card-text"><span class="key">Last Activity:</span>&nbsp;<span class="last-activity">{{ item.last-activity | date: '%B %d, %Y' }} </span></p>        
       </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>

working-groups/main.java

@@ -176,7 +176,7 @@ public String getLastActivityDate() {
             LocalDateTime dateTime = LocalDateTime.ofInstant(updateDate, ZoneId.of("UTC"));
 
             // Define the formatter
-            DateTimeFormatter formatter = DateTimeFormatter.ofPattern("dd/MM/yyyy");
+            DateTimeFormatter formatter = DateTimeFormatter.ofPattern("yyyy-MM-dd");
 
             // Format the LocalDateTime
             return dateTime.format(formatter);