Bolsena 2023

Agenda for the Bolsena Code Sprint 2023

Link to the event: Bolsena_Code_Sprint_2023

Presentations & discussions

• Week 1
  • Monday: Group meeting
  • Tuesday:
  • Wednesday:
  • Thursday:
  • Friday: Group presentations
• Week 2
  • Monday:
  • Tuesday:
  • Wednesday:
  • Thursday:
  • Friday:

Agenda

Topics to talk about/things to do

• Week 1
  • Documentation: Gather sphinx-docs material for conversion
• Week 2
  • Documentation: MkDocs Documentation
  • GeoTools 30-M0 upgrade test

Community

Project features

Project updates

Releases & documentation

Work items

geonetwork-ui

• Write documentation
• Handle GN4 backend version & compatibility
• Pivot format as internal model
• Decide on a communication channel (discord/gitter/slack/IRC?) see https://github.com/geonetwork/geonetwork-ui/discussions/509
• Publish geonetwork-ui libs as npm package
• Bundle geonetwork-ui apps in the geonetwork WAR (e.g. datahub, editor)

OGC API Records

• facet proposal

GeoTools 30-M0 upgrade/test

• Part of OpenGIS Harmonization activity GeoTools 30-M0 milestone release being created with incompatible changes
• Coordinate update / test of GeoTools 30-M0 milestone with co-sprinting activity on second week of sprint
• Expect a script to run (changing package imports) and confirm project compiles and functions
• OSGeo budget available to support affected projects if this can be of assistance

MkDocs Documentation

documentation content (first week - volunteer needed)

• Fold in documentation repository to core-geonetwork to version alongside codebase
• Rescue missing pages from 2.10 documentation
• Gather existing translations into RST form

transition to mkdocs (second week - jody garnett, and friends?)

• Example: sphinx transition to MkDocs
• Document Conversion: Change from Rich-Structured-Text to Material for MkDocs (regex, pandoc, regex, and manual review)
• Documentation translation
  • Use of document translator like deepl, or continue with POT files and osgeo weblate or transifex
• Writing guide
  • Consisting "tone/professionalism"
  • Address consistent Markdown use (Bold for user interface elements, italic for captions, etc...)
• Configuration of Material Theme for GeoNetwork Branding