Dear GeoServer PSC,
Following guidance from Andrea and Jody, we would like to formally request that Camptocamp be recognized as a Core Contributor on the GeoServer project. We believe our team meets all three core contributor responsibilities (core, committer, and support) as outlined in the GeoServer service provider checklist[1][2]. Below we summarize our contributions in each area with supporting details:
Core (ongoing responsibility):
-
Security & Releases: Our team actively participates in GeoServer’s security process and release management. For example, Cécile Vuilleumier has been volunteering with the GeoServer security group[3], regularly attending security meetings. We also assist with GeoServer releases – Gabriel Roldán has served as a release manager in the past (co-authoring the GeoServer 2.17.5 release)[4] and continues to help with recent releases. He provided feedback and testing for the 2.28.0 milestone[5] and has been in charge of the GeoServer 2.27.0 release.
-
Supported Extensions: Camptocamp takes responsibility for maintaining and enhancing GeoServer extensions. Notably, our team leads development of GeoServer Cloud (the “Cloud Native GeoServer” microservices architecture)[7] and ensures its alignment with GeoServer core. We have contributed improvements from GeoServer Cloud back to the community – for instance, Gabriel Roldán folded the new DataDir catalog loader performance enhancement into a GeoServer community module for general use[8]. We also spearheaded the GeoServer ACL (Access Control List) plugin project to extend GeoServer’s security capabilities (Gabriel is the contact point for this effort)[9]. These activities demonstrate ongoing stewardship of key GeoServer subsystems and extensions.
Committer (active development):
-
Code Contributions: Camptocamp developers are very active on GeoServer’s codebase. We contribute new features, bug fixes, and improvements across GeoServer and its extensions via GitHub. Some examples: our team members have implemented features like a Google Cloud Storage backend for GeoWebCache and a PMTiles datastore. Gabriel Roldan has driven the GeoTools “Bill of Materials” dependency management update in preparation for the GeoServer’s build migration to Java 17. José Macchi contributed Helm deployment examples to the GeoServer Cloud documentation[10], and Cécile Vuilleumier is working on migrating geotools to Apache HttpComponents 5 Httpclient 5 migration by vuilleumierc · Pull Request #5392 · geotools/geotools · GitHub.
-
Reviews, Bug Fixes & Sprints: As committers, we regularly review pull requests on the geoserver-devel list and in GitHub, providing feedback and ensuring quality. Our team fixes assigned JIRA issues and participates in community bug-fix efforts (e.g. bug stomp days). We also engage in GeoServer development sprints. In fact, Camptocamp developers Cécile Vuilleumier and Gabriel Roldán attended the October 2025 GeoServer 3 migration sprint[13], where we helped refactor and upgrade the GeoServer codebase to Java 17/Spring 6. This continued involvement in sprints and issue resolution underlines our sustained active development role.
Support (sustained community support):
-
User Support: Our team, particularly Alexandre Gacon, dedicates time to assist GeoServer users in the community. We actively answer questions and share expertise on the GeoServer users mailing list and forums. For example, Cécile Vuilleumier has participated in user discussions (see her GeoServer-users mailing list post about managing feature types via REST[14][15]), and Gabriel Roldán likewise engages in user threads to advise on best practices (for instance, weighing in on safe handling of REST API operations)[16][14]. Through these interactions, we help troubleshoot issues and guide users, demonstrating long-term commitment to the GeoServer user community. We also keep an eye on the issue tracker (JIRA), commenting on and triaging issues where we can contribute.
-
Outreach & Project Sustainability: Camptocamp has been a vocal advocate and supporter of GeoServer in the wider geospatial community. We give talks (e.g. FOSS4G presentations on GeoServer Cloud) and publish blog posts to promote GeoServer. Importantly, we helped initiate and lead the GeoServer 3 crowdfunding campaign to ensure the project’s future. Camptocamp was one of the three organizations spearheading GeoServer 3.0 development[17], contributing a significant financial donation and dedicated developer effort to that campaign. This consortium leadership is noted by the GeoServer project (“the GeoServer 3 major upgrade, led by Camptocamp, GeoSolutions, and GeoCat”[17]), and reflects our long-standing investment in GeoServer’s sustainability and growth. We were thrilled to see the GeoServer 3 funding goal surpassed with our support[18][19], and we continue to prioritize GeoServer’s success through both technical contributions and community sponsorship.
In summary, our team’s contributions cover all aspects of a core contributor’s responsibility – we help maintain core project health (security, releases, extensions), actively develop and review code, and support the user community and broader project sustainability. We have demonstrated a sustained commitment to GeoServer’s development and outreach. We respectfully ask the PSC to list Camptocamp as a Core Contributor service provider on the GeoServer website, in recognition of these efforts[1][2].
Thank you very much for your consideration. We remain at the PSC’s disposal for any questions or further information needed.
Sincerely,
The Camptocamp GeoServer Team (Gabriel Roldán, Cécile Vuilleumier, Pierre Mauduit, José Macchi, Andrea Borghi, Alexandre Gacon, Emmanuel Belo and more…)
[1] [2] Service Providers — GeoServer 3.0 Developer Manual
https://docs.geoserver.org/latest/en/developer/policies/service_providers.html
[3] [11] [12] GS3 Milestone 1 Updates - GeoServer Developer - OSGeo Discourse
https://discourse.osgeo.org/t/gs3-milestone-1-updates/147158
[4] GeoServer 2.17.5 Released
https://geoserver.org/announcements/2021/02/22/geoserver-2-17-5-released.html
[5] GeoServer 2.28.0 Release
https://geoserver.org/announcements/vulnerability/2025/10/14/geoserver-2-28-0-released.html
[6] GeoServer PSC meeting notes, March 25th 2025 - GeoServer Developer - OSGeo Discourse
https://discourse.osgeo.org/t/geoserver-psc-meeting-notes-march-25th-2025/146138
[7] geOcom 2022 GeoServer_Cloud
https://www.georchestra.org/public/geocom2022/presentation/05-CampToCamp-GeoServer_Cloud.pdf
[8] [9] GeoServer 2.24.0 Release
https://geoserver.org/announcements/vulnerability/2023/10/15/geoserver-2-24-0-released.html
[10] GeoServer PR - GitHub
https://github.com/geoserver/geoserver/pulls?q=is%3Apr+author%3Agroldan+is%3Aclosed
https://github.com/geoserver/geoserver/pulls?q=is%3Apr+is%3Aclosed+author%3Ajemacchi
https://github.com/geotools/geotools/pulls?q=is%3Apr+is%3Aclosed+author%3Avuilleumierc
https://github.com/geotools/geotools/pulls?q=is%3Apr+is%3Aclosed+author%3Ajemacchi
[13] GeoServer 3 Sprint · geoserver/geoserver Wiki · GitHub
https://github.com/geoserver/geoserver/wiki/GeoServer-3-Sprint
[14] [15] [16] [Geoserver-users] Deleting database table through REST API - GeoServer User - OSGeo Discourse
https://discourse.osgeo.org/t/geoserver-users-deleting-database-table-through-rest-api/49450
[17] GeoServer 3 Crowdfunding
https://geoserver.org/sponsor/gs3-crowdfunding
[18] [19] GeoServer 3 Crowdfunding Goal Surpassed!
https://geoserver.org/behind%20the%20scenes/2025/05/13/gs3-crowdfunding-surpassed.html
