Last week was super productive, with many important conversations and decisions happening in person.
This thread is an opportunity to share what was accomplished, so we can keep communication going with those who could not attend.
I had a productive / busy time - with many of my sprint activities only coming together on the Friday after everyone else had stopped.
Discourse
Last week really marked the change over to discourse, working with @cvvergara from the system admin committee to setup categories and transfer the contents of each mailing list.
Now that instructions are translated to Spanish and French I will be turning off the source forge mailing lists.
Roadmap project board
We agreed to use the GitHub project board for the project-steering-committee proposal process; but found that it was also being used to plan upcoming releases. The resulting muddle became hard to follow!
The roadmap project board is now strictly about proposals, with clear columns matching the project-steering-committee voting process. Thanks to @ticheler for working with me on this.
The project-steering-committee details process was updated to change from mailing list to github voting.
Release project board
This release process now has its own project board. Shown below you can see the activities that are currently under test ahead of the 4.4.6 release cycle.
GeoNetwork 5 proposal and project board
A probably most important thing (for which I claim no credit) is proposing GeoNetwork 5 as a bold response to the roadmap challenges (shared earlier this year as sponsorship opportunities).
The general idea is to start a new GeoNetwork 5 codebase using spring-boot and the latest Java technologies. Taking the opportunity to use SaxxonHE and other supported technologies for a fresh start.
During the period of transition GeoNetwork 5 will delegate to a complete GeoNetwork 4 instance. This provides a ready-to-use system at each stage as components are migrated from GeoNetwork 5 to GeoNetwork 4.
This matter has some urgency now as spring-framework 5.3 reached end-of-life in August 2024.
This proposal is presently up for voting by the PSC.
There is also a GeoNetwork 5 project board which we will use to coordinate architecture decisions and migrate components from GeoNetwork 4 to GeoNetwork 5.
1 Like
Hi, Jody,
For the sprint, I was working on the OGCAPI-Records (located in the geonetwork-microservices project.
I created a PR which improves some of the JSON output. Also, see the documentation included in the PR.
There’s a short overview video here -
This also demos the very simple Angular app that uses the GN OGCAPI-Records JSON (with the extended catalog.yaml information).
I’ve moved on to the Search/Queryables/Sorting infrastructure - and making good progress this week. I’ve started a PR for people interested.
Thanks,
Dave
2 Likes
Welcome to discourse David, and thanks so much for the video.