Proposal: GSIP 233 - Community Publish Profile

GeoServer GeoServer Developer
1

The following proposal has now been revised and is ready for voting:

The motion is held open for 2 weeks until August 9, 2025:

  • Alessio Fabiani +1
  • Andrea Aime +1
  • Ian Turton
  • Jody Garnett +1 initial motion
  • Jukka Rahkonen
  • Kevin Smith
  • Nuno Oliveira
  • Peter Smythe +1
  • Simone Giannecchini +0
  • Torben Barsballe +1

Community support:

  • TBD

Thanks everyone.

2

LGTM, +1

Cheers
Andrea

3

+0

4

+1

5

+1

6

+1

Cheers,
Torben

On Sat, Jul 26, 2025 at 2:42 AM Jody Garnett via OSGeo Discourse <noreply@discourse.osgeo.org> wrote:

jive Leader
July 26

The following proposal has now been revised and is ready for voting:

The motion is held open for 2 weeks until August 9, 2025:

  • Alessio Fabiani
  • Andrea Aime
  • Ian Turton
  • Jody Garnett +1 initial motion
  • Jukka Rahkonen
  • Kevin Smith
  • Nuno Oliveira
  • Peter Smythe
  • Simone Giannecchini
  • Torben Barsballe

Community support:

  • TBD

Thanks everyone.

Visit Topic or reply to this email to respond.

You are receiving this because you enabled mailing list mode.

To unsubscribe from these emails, click here.

1 Like
7

Thanks, this proposal has been accepted.

8

Starting to implement this as part of the GeoServer 3 code sprint (where we have a few modules passing QA and we would like to use communityPublish profile as a way to first nominate, and then include these modules in the build with QA testing.

Now that we are implementing I would like to note a few “improvements” for feedback:

  • The difference between communityRelease and communityPublish is hard to communicate.
    I like the idea of giving each category its own word: extension, community, pending
  • We would like to include QA as a target, presently on formatting is required
  • We will use the first couple of emails as examples for the developer guide :slight_smile:

Thanks!

9

Pending works for me

Yep, during the GS3 sprint we have made several community modules pass QA as well, so it’s a good time to lock these modules down with both tests and QA enabled

Cheers

Andrea

10

Hi,

this is a great initiative.

I’d like to propose the geoparquet community module for the communityPublish profile, since after the sprint we’ll be working on getting it production ready.

Cheers,

Gabe

1 Like
11

Hi.

Since during GS3 we have improved QA on several modules, I would also like to start working on moving the wps-download-netcdf to the pending status / communityPublish (having QA passing and a codecoverage over 60%).

Daniele

1 Like
12

Similarly, I would like to include the OpenSeach for EO and STAC modules (the lot of modules under community/oseo)
in the pending profile.

The modules have documentation, a few installations, they have good test coverage, pass QA.
I’m just not asking them to be included in the release profile as the storage backend in now PostgreSQL + feature templates to build the complex JSON in output,
but a new implementation based on ElasticSearch could pop un in the future, which may rock the boat (so not confident on the “stable” bit required for extension).

13

Thanks Andrea, +1 for trying out “pending” profile with Open Search for EO and STACK modules.

Consider listing the design question (PostgreSQL or Elasticsearch) as the feedback needed for the module to graduate?