Re: [Geoserver-devel] geoserver-user discourse updates

Sign in is required, adding to a special group is no longer required. - - Jody Garnett On Fri, Aug 23, 2024 at 1:48 AM Andrea Aime < andrea.a...@geosolutionsgroup.com> wrote: > Hi Jody, > some hiccups when trying out something new are part of the game. > It seems that problems are being dealt w

Re: [Geoserver-devel] -EXT-Re: How to handle "external" community modules

Hi guys, I agree a link would be best. The compatibility matrix sounds like a great idea, but for GeoMesa at least, would be largely empty - our releases aren't synced up with GeoServer, and we don't have the bandwidth to test every version for compatibility. We've had regressions in the past f

Re: [Geoserver-devel] About cloud native geoserver and security integrations

Hi Jody, For the most part, it uses GeoServer security as-is. But it's true the GeoServer OAuth2 plugins haven't been integrated, and I didn't want to, since Spring/Boot provide out of the box OAuth2/OIDC support. For that reason, and in order to avoid duplication and keep the gscloud gateway as

Re: [Geoserver-devel] How to handle "external" community modules

I vote for the least maintenance effort: a simple link. And maybe add to the RC release procedure, a step to check if the links are still valid (a once every every six months task) Regards, Andrea Aime == GeoServer Professional Services from the experts! Visit http://bit.ly/gs-services-us for

Re: [Geoserver-devel] geoserver-devel discourse or google discussions?

Hi Jody, please let's not start mixing approaches... we can have everything in discourse, or everything in google discussions, or everything in the github "discussions"... as long as we stick with one. Using different solutions for the same problem (threaded and asynch communication) is confusing.

Re: [Geoserver-devel] geoserver-user discourse updates

Hi Jody, some hiccups when trying out something new are part of the game. It seems that problems are being dealt with right? If there is no blocker, let's move on. If anything, one observation... the geoserver user support page goes to great lengths to provide all the

[Geoserver-devel] backport bot failing with "Bad Credentials"

I suppose the secret/token (GH_TOKEN_BOT) that the workflow uses has expired. see eg. https://github.com/geoserver/geoserver/actions/runs/10522214414/job/29154401033 ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lis