I’m part of the GeoCat team (back again ), which, as you may know, is one of the major contributors to this project. I’ve worked on GeoNetwork in the past and am happy to be returning more regularly.
One of my current responsibilities is to help plan our company’s contributions to GeoNetwork 5. Of course, I believe this can’t be done effectively without engaging with the community. Which is why I’m reaching out here.
I’ve been following the ongoing efforts to migrate GeoNetwork to a new stack using Spring Boot: a big and complex task, but it’s in capable hands.
I understand that there have already been meetings, code sprints, and early discussions about the future direction of GN5. While I may not have much to add at this point I would like to propose reviving some community “rituals”. In particular, regular meetings that could help us coordinate our efforts more effectively.
Would that be something the community finds useful?
17 CET seems like a good time for everyone and biweekly seems like a good idea, if we feel like we need more, we can increase. Let’s decide on the day of the week, I propose a survey. I don’t include Tuesday because at that time in Geocat we always have an internal meeting.
I’ll leave the pool open for a few more days in case there are others interested. But I’d say, for now, we have unanimity on Wednesday at 17 CET. So I’d say start setting the first appointment for next Wednesday (April 16). Please mark your calendars!
About how to organize the meetings, I really like how pygeoapi meetings are structured. I find their approach clear and efficient, so I would suggest following the same:
The meeting page is updated with attendees, notes and actions discussed during the meeting.
At the end of each meeting, the date of the next meeting and the next topics to discuss are suggested, and the wiki page for the next meeting is drafted.
Anyone is free to append new topics to the agenda up until the date of the meeting with their name.
The person proposing the agenda item has a time slot to ask about/discuss/demo/etc. the topic.
Do you think it could work also for GeoNetwork 5? Another thing I really like about these meetings is that there is always an agenda item dedicated to going through open issues and pull requests to try to address the necessary actions. It helps to keep the work moving forward constantly.
Can we use a google doc for shared agenda and meeting notes, and then copy the markdown to the forum (or wiki) after for the record. It is so helpful to have more than one person editing during a meeting - and google docs recently added markdown support which is a great fit for developers.
), which, as you may know, is one of the major contributors to this project. I’ve worked on GeoNetwork in the past and am happy to be returning more regularly.
