[image]All: Vote on open proposals if you haven’t already
[image]Peter: Cite test proposal - Coordinate payment, add blog post, update site
[image]Jody: make a blog post covering FOSS4G workshops and presentations (see below)
Agenda
CITE tests, OGC API Tiles and certification
GeoServer 3 progress
Two weeks to FOSS4G EU
Java 17 incoming
OAuth2 PR merged
Actions
[image]Check on the “GSIP 233 - community release” proposal and see if passed.
jody: Take an action to reword “commuityRelease” as a new option, rather than a reduction of the modules qualifying for nightly build.
[image]Torben: Download NGINX access logs, provide to Peter to extract community module stats
CITE tests, OGC API Tiles and certification
Peter has heard back from OSGeo, we are waiting on OGC process:
Won’t work on production version of engine, but this is fixed on the beta
Community module, so not in position to certify for real yet?
We can still submit , with disclaimer about beta used for testing
OGCAPI Process - going to be a while
two reference implementations are the same one working around bugs
echo process used for certification
GSIP 233 - community release
No voting since this proposal was revised for feedback - Jody will make a new thread
Move list of candidates to appendix at the end, so that casual readers won’t take this as a firm commitment.
Further discussion on what merits a community release - proposal includes a higher threshold of requirements for publishing as part of the communityRelease build
Raises the barrier to entry for publishing WIP modules too high
However, we also have modules that have been sitting in communityRelease state for years with no active development (but often still a small number of users)
There’s also a persistent issue of (potential) users complaining about the inaccessibility of these modules and wasting community members time
Q: Do we have download stats for community modules?