-
-
Notifications
You must be signed in to change notification settings - Fork 489
GeoNetwork 2025 Sponsorship Opportunities
The GeoNetwork project recognizes the importance of a sustainable financial story to support the efforts of our developers, project-steering-committee, and meet the operational costs associated with running a successful open source project.
Occasionally a much larger sponsorship callout will be made when the team is faced with significant roadmap challenges that are beyond the reach of a single developer or organization.
The team has identified the following goals for 2025 roadmap planning.
The Geonetwork 5 project is a bold response to some of the update challenges involved in migrating to spring-framework-6 which requires a new operational environment to be successful.
The proposal covers setting up a new codebase with Java 21/JakartaEE/SpringBoot for GeoNetwork 5. This contains a gateway which delegates to Java 11/Jakarata/Tomcat environment running GeoNetwork 4 during the development cycle.
This allows the system as whole to function as modules are ported from GeoNetwork 4 to GeoNetwork 5.
- Ideally a minimal GeoNetwork 5 app can be available for publishing providing a reduced security target for public facing service.
- The more fully featured GeoNetwork 5 / GeoNetwork 4 environment can be maintained during the transition for internal use.
- When the modules are all transferred the GeoNetwork 4 environment will no longer be required.
This activity is now quite urgent and has the highest priority.
Spring Framework Spring Framework 6
Migration from sping-framework 5.3 to spring-framework 6 is required to ensure we are on a supported platform and have access to the latest security fixes. This issue was not addressed in 2024 and is now urgent.
Why this is important: The spring-framework is the glue which holds the GeoNetwork application together and provides a lot of the security integrations we use with other systems. It is important to remain on a supported version of the spring-framework so we can maintain compatibility with newer versions of Java and Tomcat, and have access to fixes for security vulnerabilities.
Their are already mounting security vulnerabilities reported against this spring-framework that require this update to take place for resolution:
- CVE-2016-1000027 Unsafe deserialization in Spring RemoteInvocationSerializingExporter could lead to remote code execution.
- CVE-2024-38816 Path traversal vulnerability in functional web frameworks
Saxon → Saxon HE
GeoNetwork has continued to use an old version of Saxon XSLT with custom patches for newer Java. This activity is to use Saxon HE which is required for Java 17 compatibility required for spring-framework-6 above.
This is a longstanding technical debt item, which now must be addressed for the roadmap spring-framework-6 item.
Why this is important: The Saxon XSLT engine is used for almost everything GeoNetwork does, from processing records into different output formats, staging information for display by the user interface, or expanding records into all the information required to run the record editor. Updating this important component must be done with care and will require funding, developers and testing to be successful.
sponsors: no present sponsors
in-kind: no in-kind participants
-
GeoCat has committed to GeoNetwork 5 response outlined below
The user-interface framework used by GeoNetwork has reached end-of-life in 2021.
This is a technical debt item.
Why this is important: This is an important activity our geonetwork community is presently running on an unsupported user interface framework and we cannot ensure that compatibility and security issues are resolved at all, let alone in a timely fashion.
sponsors: no present sponsors
in-kind:
-
No in-kind activities at present time
-
Camptocamp has been working working on geonetwork-ui providing a set of components that can be used for this activity.
sponsors: no present sponsors
in-kind: no in-kind participants
-
GeoCat has attended ogcapi-records sprint on this topic
Support for DCAT was identified in 2023 user meeting as a roadmap priority for the project.
This is a roadmap planning item.
Why this is important: There is considerable interest an opportunity in the DCAT format which open ups future opportunities for the project and our user community.
sponsors: no present sponsors
in-kind: no in-kind participants
-
GeoCat has attended ogcapi-records sprint on this topic
The transition to OGCAPI Services is presently underway, with the OGCAPI Records standard taking shape gradually as it works through the standardization process.
This is a roadmap planning item.
Why this is important: There is considerable interest in moving on from XML based standards and adopting modern OpenAPI and JSON standards.
Open Source Geospatial Foundation manages financial contributions to the GeoNetwork project:
-
Direct OSGeo Sponsorship - email [email protected] to request an invoice and be recognized on the OSGeo sponsors page.
Subject: GeoNetwork sponsorship
Treasurer:
We recognize the value in supporting free software, and have set aside operational budget for a Silver sponsorship.
Please send us an invoice for $3000 USD. We have attached a logo for the sponsorship page.
attachement: organisation_logo.svg
-
Donate via PayPal - easy for one time donations, but does use a small overhead charge. The link directly donates to the GeoNetwork project.
-
Donate via GitHub Sponsors - great for ongoing donations, provides some some sponsorship matching, a github sticker, and avoids PayPal overhead. Email [email protected] making a note of your donation so that it may be directed to the GeoNetwork project.
Subject: Sponsorship for GeoNetwork
Treasurer:
I have used GitHub Sponsors page to setup a monthly donation of $50 to the GeoNework project. Please observe the attached logo for OSGeo Bronze sponsorship.
attachement: company_logo.svg
For details see how to become a sponsor which includes example emails.
We appreciate all levels of support, the following recommend donation levels provide the team an opportunity to acknowledge your support:
Please note that sponsorship at these levels helps the project steering committee support developers in small ways. Examples include covering travel expenses and code-sprint attendance.
- $5/monthly Enthusiast: Recommended for fans of OSGeo, badge your repository as supporting OSGeo with a small donation.
- $10/monthly Supporter: Recommended for GIS Professionals, Name listed as 2024 Donations on GeoNetwork website.
- $50/monthly Supporter: Recommended for Consultants, Logo listed as 2024 Donations on GeoNetwork website, cross-listed to OSGeo website as a bronze sponsors, bronze sponsor logo, be sure to setup your service provider page.
Amount | GeoNetwork | OSGeo |
---|---|---|
$5/monthly Enthusiast |
Name listed 2025 Donations | GitHub supporter badge |
$10/monthly Supporter |
Name listed 2025 Donations | GitHub supporter badge |
$50/month Bronze Sponsor |
Logo listed 2025 sponsors | Logo listed on sponsors page Use of Bronze logo |
For more information on OSGeo perks described above see How to become a sponsor.
Please note that sponsorship contributes to the operational expenses, allowing the project steering committee to address care-and-feeding activities.
- $500/annually OSGeo Bronze Sponsorship: Recommended for individual consultants
- $3000/annually OSGeo Silver Sponsorship: Recommended support level for Small Organizations using GeoNetwork internally to support their employees.
- $10,00/annually OSGeo Gold Sponsorship: Recommended support level for Small Organizations using GeoNetwork to meet communication needs with the public or meet regulatory requirements.
- $20,00/annually OSGeo Platinum Sponsorship: Recommended support level for Large Organizations using GeoNetwork internally to support their employees
- $30,00/annually OSGeo Diamond Sponsorship: Recommended support level for Large Organizations using GeoNetwork to meet communication needs with the public or meet regulatory requirements.
Organizations should sponsorship GeoNetwork because they appreciate or depend on its availability, sponsorship is not a replacement for commercial support!
Amount | GeoNetwork. | OSGeo |
---|---|---|
$500/annually Bronze Sponsor |
Logo listed 2025 sponsors | Logo listed on sponsors page Use of OSGeo Bronze logo |
$3000/annually Silver Sponsor |
Logo listed 2025 sponsors GeoNetwork blog post |
Logo listed on sponsors page Logo displayed in page footer Sponsorship blog post Networking event Use of OSGeo Silver logo |
$10,000/annually Gold Sponsor |
Logo listed 2025 sponsors GeoNetwork blog post |
Logo listed on sponsors page Logo displayed in page footer Sponsorship blog post Networking event Use of OSGeo Gold logo |
$20,000/annually Platinum Sponsor |
Logo listed 2025 sponsors GeoNetwork blog post |
Logo listed on sponsors page Logo displayed in page footer Logo added to OSGeo booth Logo added to OSGeo marketing collateral Logo added to About OSGeo in all press releases Sponsorship blog post Networking event Use of Platinum logo |
$30,000/annually Diamond Sponsor |
Logo listed 2025 sponsors GeoNetwork blog post |
Logo listed on sponsors page Logo displayed in page footer Logo added to OSGeo booth Logo added to OSGeo marketing collateral Logo added to About OSGeo in all press releases Sponsorship blog post Networking event Use of Diamond logo |
For more information on OSGeo perks described above see How to become a sponsor.
As a member of the Open Source Geospatial Foundation the project team receives some financial assistance. The following is the GeoNetwork budget request, usually devoted to operational or planning costs. This guidance is provided to the OSGeo Board for budget planning.
Guidance for OSGeo Budget 2024 planning:
request | activity |
---|---|
$1000 | Process and procedure update to improve PSC transparency |
$1000 | Security procedure review and support |
The above request is made in support of the project goals for 2025. Each of these tasks requires upfront planning before a coordinated response and budget can be established.
We also wish to maintain some capacity to respond to security issues as they are reported and work on improving our process over the course of 2025.
The following code-sprints are of interest to our community:
- Bolsena Code Sprint
- OGC Code Sprints on standards development
- OSGeo Code sprint
We do forsee the need for assistance to attend the 2025 AGM.
If you have some comments, start a discussion, raise an issue or use one of our other communication channels to talk to us.