Re: [Geoserver-devel] GeoServer 2.25.1 release train
Fixed, docker for 2.25.1 should now be available. -- Jody Garnett On May 23, 2024 at 9:34:45 AM, Jody Garnett wrote: > Thanks Johannes, I think I can grant the gsbuilder account docker > permission (that way the build server will just have one set of credentials > for repo.osgeo.org). > > I have tested the downloads, and the release announcement has now been > reviewed (thanks Peter and Andrea). > > I will have a go at fixing docker and then release either way. > -- > Jody Garnett > > > On May 22, 2024 at 11:26:38 PM, Johannes Weskamm > wrote: > >> Hi, >> >> As i do not have access to the build infrastructure, someone else will >> have to fix the credentials, either by contacting me to get the password or >> by creating a new password / another account for the build. >> >> The account i have was originally intended for deploys from github action >> pipelines into the osgeo repo, but things turned out different. >> >> So if you need any input from my side just let me know. >> >> >> Greetings, >> >> Johannes >> >> >> Am 23.05.24 um 06:01 schrieb Jody Garnett: >> >> Blog post ready for review: >> https://github.com/geoserver/geoserver.github.io/pull/196 >> >> Please check it over and we can announce tomorrow. >> >> Please note that the docker build is down due to credential change at >> repo.osgeo.org - Johannes Weskamm has the credentials that were used. >> Let me know if you can fix it; or if I should generate something else >> tomorrow? >> >> The job to re-run is >> https://build.geoserver.org/view/release/job/geoserver-release-docker/1021/ >> (parameters >> version 2.25.1 build 82) >> -- >> Jody Garnett >> >> >> On May 22, 2024 at 6:09:46 PM, Jody Garnett >> wrote: >> >>> Preflight artifacts available for testing >>> https://build.geoserver.org/view/release/job/geoserver-release/141/artifact/distribution/2.25.1 >>> -- >>> Jody Garnett >>> >>> >>> On May 13, 2024 at 11:07:01 PM, Jody Garnett >>> wrote: >>> >>>> I notice that both Ian and myself have signed up for the release this >>>> month :) >>>> >>>> It was my intension to do the stable releases when I have an >>>> opportunity to do so - by collaboration is good :) >>>> >>>> Are there any pull requests in need of review ahead of release? I see >>>> that the 18th falls on a Saturday so I am likely to set the release on >>>> Monday 20 May, and announce the following day (if everything goes well). >>>> >>>> >>>> >>>> >>>> >>>> -- >>>> Jody Garnett >>>> >>> -- >> Dipl.-Geogr. Johannes Weskamm >> — Anwendungsentwickler — >> >> terrestris GmbH & Co. KG >> Kölnstraße 99 >> 53111 Bonn >> >> Tel: +49 (0)228 / 96 28 99 -51 >> Fax: +49 (0)228 / 96 28 99 -57 >> >> Email: wesk...@terrestris.de >> Web: https://www.terrestris.de >> >> Amtsgericht Bonn, HRA 6835 >> Komplementärin: terrestris Verwaltungsgesellschaft mbH >> vertreten durch: Torsten Brassat, Marc Jansen >> >> Informationen über Ihre gespeicherten Daten finden Sie auf >> unserer Homepage unter folgendem Link: >> https://www.terrestris.de/datenschutzerklaerung/ >> >> ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Re: [Geoserver-devel] GeoServer 2.25.1 release train
Thanks Johannes, I think I can grant the gsbuilder account docker permission (that way the build server will just have one set of credentials for repo.osgeo.org). I have tested the downloads, and the release announcement has now been reviewed (thanks Peter and Andrea). I will have a go at fixing docker and then release either way. -- Jody Garnett On May 22, 2024 at 11:26:38 PM, Johannes Weskamm wrote: > Hi, > > As i do not have access to the build infrastructure, someone else will > have to fix the credentials, either by contacting me to get the password or > by creating a new password / another account for the build. > > The account i have was originally intended for deploys from github action > pipelines into the osgeo repo, but things turned out different. > > So if you need any input from my side just let me know. > > > Greetings, > > Johannes > > > Am 23.05.24 um 06:01 schrieb Jody Garnett: > > Blog post ready for review: > https://github.com/geoserver/geoserver.github.io/pull/196 > > Please check it over and we can announce tomorrow. > > Please note that the docker build is down due to credential change at > repo.osgeo.org - Johannes Weskamm has the credentials that were used. > Let me know if you can fix it; or if I should generate something else > tomorrow? > > The job to re-run is > https://build.geoserver.org/view/release/job/geoserver-release-docker/1021/ > (parameters > version 2.25.1 build 82) > -- > Jody Garnett > > > On May 22, 2024 at 6:09:46 PM, Jody Garnett > wrote: > >> Preflight artifacts available for testing >> https://build.geoserver.org/view/release/job/geoserver-release/141/artifact/distribution/2.25.1 >> -- >> Jody Garnett >> >> >> On May 13, 2024 at 11:07:01 PM, Jody Garnett >> wrote: >> >>> I notice that both Ian and myself have signed up for the release this >>> month :) >>> >>> It was my intension to do the stable releases when I have an opportunity >>> to do so - by collaboration is good :) >>> >>> Are there any pull requests in need of review ahead of release? I see >>> that the 18th falls on a Saturday so I am likely to set the release on >>> Monday 20 May, and announce the following day (if everything goes well). >>> >>> >>> >>> >>> >>> -- >>> Jody Garnett >>> >> -- > Dipl.-Geogr. Johannes Weskamm > — Anwendungsentwickler — > > terrestris GmbH & Co. KG > Kölnstraße 99 > 53111 Bonn > > Tel: +49 (0)228 / 96 28 99 -51 > Fax: +49 (0)228 / 96 28 99 -57 > > Email: wesk...@terrestris.de > Web: https://www.terrestris.de > > Amtsgericht Bonn, HRA 6835 > Komplementärin: terrestris Verwaltungsgesellschaft mbH > vertreten durch: Torsten Brassat, Marc Jansen > > Informationen über Ihre gespeicherten Daten finden Sie auf > unserer Homepage unter folgendem Link: > https://www.terrestris.de/datenschutzerklaerung/ > > ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Re: [Geoserver-devel] GeoServer 2.25.1 release train
Blog post ready for review: https://github.com/geoserver/geoserver.github.io/pull/196 Please check it over and we can announce tomorrow. Please note that the docker build is down due to credential change at repo.osgeo.org - Johannes Weskamm has the credentials that were used. Let me know if you can fix it; or if I should generate something else tomorrow? The job to re-run is https://build.geoserver.org/view/release/job/geoserver-release-docker/1021/ (parameters version 2.25.1 build 82) -- Jody Garnett On May 22, 2024 at 6:09:46 PM, Jody Garnett wrote: > Preflight artifacts available for testing > https://build.geoserver.org/view/release/job/geoserver-release/141/artifact/distribution/2.25.1 > -- > Jody Garnett > > > On May 13, 2024 at 11:07:01 PM, Jody Garnett > wrote: > >> I notice that both Ian and myself have signed up for the release this >> month :) >> >> It was my intension to do the stable releases when I have an opportunity >> to do so - by collaboration is good :) >> >> Are there any pull requests in need of review ahead of release? I see >> that the 18th falls on a Saturday so I am likely to set the release on >> Monday 20 May, and announce the following day (if everything goes well). >> >> >> >> >> >> -- >> Jody Garnett >> > ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Re: [Geoserver-devel] GeoServer 2.25.1 release train
Preflight artifacts available for testing https://build.geoserver.org/view/release/job/geoserver-release/141/artifact/distribution/2.25.1 -- Jody Garnett On May 13, 2024 at 11:07:01 PM, Jody Garnett wrote: > I notice that both Ian and myself have signed up for the release this > month :) > > It was my intension to do the stable releases when I have an opportunity > to do so - by collaboration is good :) > > Are there any pull requests in need of review ahead of release? I see that > the 18th falls on a Saturday so I am likely to set the release on Monday 20 > May, and announce the following day (if everything goes well). > > > > > > -- > Jody Garnett > ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
[Geoserver-devel] GeoServer PSC Meeting notes, May 21 2024
GeoTools / GeoServer PMC meeting - 2024-05-21Attending - David Blasby - Peter Smythe - Jody Garnett - Jukka Rahkonen Actions from prior meeting: - [DONE] Jody: Make a ticket about GROUP_ADMIN not having permission to create a new user (GEOS-10938 <https://osgeo-org.atlassian.net/browse/GEOS-10938>) - [DONE] Jody: Make a ticket on clean up of admin roles and constants ( GEOS-11389 <https://osgeo-org.atlassian.net/browse/GEOS-11389>) - [DONE] Jody: Open a ticket to refine Demo Page Javascript rewrite ( GEOS-11390 <https://osgeo-org.atlassian.net/browse/GEOS-11390>) Agenda: - repo.osgeo.org maintenance - build status - Why do checks fail, what is the process to handle failures? - Dependabot https://github.com/geoserver/geoserver/pull/7637 process? - release status - discourse migration - Clean up old branches, keeping 2.2.x, ones with open PRs? - TestWFSPost servlet removal (replace w/ 100% JS). Demo Request, WCS Request, WPS Request - mkdocs repo.osgeo.org maintenance Upgrade Nexus to v3.68.1 for CVE-2024-4956: - Asked to reset gsbuild user (done) - contacted torben, updated build.geoserver.org settings.xml - Asked to reset gsdocker user - contacted wesk...@terrestris.de ? - See: https://trac.osgeo.org/osgeo/ticket/3189 build status Q: Why do checks fail, what is the process to handle failures? - Jody broke last week (did not run -DQA checks when backporting using cherry-pick) - Had to close and open backports to “rebase” effectively - Checks that are needed across projects (geotools api change; that needed a geoserver - For intermittent failures - Quick: rerun failed test … - Why: Each example needs investigation - windows locked file is a common failure with older file system? - Perhaps some state changed (environmental variable) that affects another test… - Perhaps opening a port → randomise the port used (minimise error) Thanks Andrea for fixing build (twice) recently. About backports: - Yes - if we can (example dependabot) - New functionality? - https://docs.geoserver.org/latest/en/developer/policies/pull_request.html If the new feature is suitable for backport, you may ask on the developer list after a 1 month. - Q: Add this to CONTRIBUTING.md also? Dependabot https://github.com/geoserver/geoserver/pull/7637 process? release status Delayed: Waiting on PR reviews and build stability PRs: - https://github.com/geotools/geotools/pull/4773 Geometry type mismatch in WFS 1.1.0 - version updates of stuff? Some from GeoTools… discourse migration This is ready to move - Marketing committee made the change, can see their instructions - We need similar instructions in our docs, and then inform the user-list Clean up old branches, keeping 2.y.x, ones with open PRs? In general we keep in case people need an emergency patch - We can see examples where release are made for archived releases Stale PRs get removed, with the idea that the branch is there if anyone wishes to recover the work. So deleting the branch may not be kind? Stale working branches? - Developers should remove when activity is complete - It would be nice to clean these up, I do not know of anything automatic - Ones with “stale” PRs may be worth keeping? - Some from big refactors are useful to keep (example refactor code sprint) Perhaps these could be placed in to a folder? TestWFSPost servlet removal (replace w/ 100% JS). Demo Request, WCS Request, WPS Request Positive response, nice work David. Peter had feedback on workflow and button order consistency between Demo Request page, WPS Builder, WCS Builder. - https://github.com/geoserver/geoserver/pull/7672 ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Re: [Geoserver-devel] GeoServer 2.25.1 release train
I would like to do the release today, there was some build instability last week (thanks for fixing Andrea and Peter). I have one PR to check (hopefully it has been reviewed) before release. -- Jody Garnett On Wed, May 15, 2024 at 9:57 AM Jody Garnett wrote: > Checking in ahead of release, > > I am ware of https://github.com/geoserver/geoserver/pull/7580 needing > review. > > Are their any other pull requests in need of review and backport ahead of > 2.25.1 release? > -- > Jody Garnett > > > On May 13, 2024 at 11:07:01 PM, Jody Garnett > wrote: > >> I notice that both Ian and myself have signed up for the release this >> month :) >> >> It was my intension to do the stable releases when I have an opportunity >> to do so - by collaboration is good :) >> >> Are there any pull requests in need of review ahead of release? I see >> that the 18th falls on a Saturday so I am likely to set the release on >> Monday 20 May, and announce the following day (if everything goes well). >> >> >> >> >> >> -- >> Jody Garnett >> > ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Re: [Geoserver-devel] is CatalogListener.reloaded() dead code?
What does happen on catalogue reload? can we restore the event? -- Jody Garnett On Sun, May 19, 2024 at 5:27 PM Gabriel Roldan < gabriel.rol...@camptocamp.com> wrote: > Hey all, > > tried to live-test a CatalogListener.reloaded() implementation, turns out > I can't find any caller in the codebase: > > grep "\.reloaded()" -R --include=*.java > wms/src/test/java/org/geoserver/wms/capabilities/GetCapabilitiesLegendURLTest.java: >((LegendSampleImpl) > GeoServerExtensions.bean(LegendSample.class)).reloaded(); > > Is it supposed to be replaced by GeoServerLifecycleHandler.onReload(), or > at some point we stopped calling it? > There seems to be a couple implementations out there with non-empty bodies: > - LayerGroupContainmentCache$CatalogChangeListener > - LegendSampleImpl > - MimeTypeCacheClearingListener > - WFSConfiguration'\s anonymous inner class > > > TIA, > gabe > *camptocamp* > INNOVATIVE SOLUTIONS > BY OPEN SOURCE EXPERTS > > *Gabriel Roldán* > Geospatial Developer > > ___ > Geoserver-devel mailing list > Geoserver-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/geoserver-devel > ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Re: [Geoserver-devel] GeoServer 2.25.1 release train
Checking in ahead of release, I am ware of https://github.com/geoserver/geoserver/pull/7580 needing review. Are their any other pull requests in need of review and backport ahead of 2.25.1 release? -- Jody Garnett On May 13, 2024 at 11:07:01 PM, Jody Garnett wrote: > I notice that both Ian and myself have signed up for the release this > month :) > > It was my intension to do the stable releases when I have an opportunity > to do so - by collaboration is good :) > > Are there any pull requests in need of review ahead of release? I see that > the 18th falls on a Saturday so I am likely to set the release on Monday 20 > May, and announce the following day (if everything goes well). > > > > > > -- > Jody Garnett > ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Re: [Geoserver-devel] -EXT-Re: Jakarta EE upgrade support
Sounds good, I am in the same boat - waiting for funding or other parties before being in position to commit. -- Jody Garnett On May 14, 2024 at 5:46:03 AM, "Lahr-Vivaz, Emilio" < emilio.lahr-vi...@ga-ccri.com> wrote: > Hi Jody! > > I'm still trying to work through approval for us to do the work, so we > can't firmly commit to anything quite yet. But with that understanding, if > our participation helps attract others, then that would be great! We'll > probably be able to commit (or not) to something in June. At any rate, it > looks like there is definitely work we could do, so that should help with > getting approval. I'll stay in touch over the next few weeks until we can > firm up a plan. > > Thanks, > > *Emilio Lahr-Vivaz* > General Atomics, CCRi > -- > *From:* Jody Garnett > *Sent:* Monday, May 13, 2024 12:17 PM > *To:* Lahr-Vivaz, Emilio > *Cc:* geoserver-devel@lists.sourceforge.net < > geoserver-devel@lists.sourceforge.net> > *Subject:* -EXT-Re: [Geoserver-devel] Jakarta EE upgrade support > > > WARNING: This message is from an external source. Evaluate the message > carefully BEFORE clicking on links or opening attachments. > Hello Emilio! > > It is really nice to hear from CCRi thank you for contacting us. It would > be *very* helpful, while a fair amount of work is outlined (planning ahead) > only a few activities are moving. > > It is always a risk sharing roadmap information for an open source project > from a funding perspective. > > I am going to write an update Q2 roadmap blog post focusing just on: > >- Goals that are in progress now - Wicket Update >- Goals that are actionable now - Spring-security update/rewrite for >OAuth2 client / ImageN >- Upcoming activities that have attracted in-kind or financial support > > > Thus far we have not gotten sufficient financial / inkind response > response to do planning, but at least folks are talking :) > > If it is okay with you I will list CCRi as committed for spring-framework > update 'in-kind" activity in the hopes of attracting greater participation: > >- My understanding is if we add some Java startup parameters to "open >javax" this activity could be worked ahead of ImageN availability. >- Even if spring-framework upgrade cannot be worked on directly in >July - some of the actives will be available and unblocked >- If I know CCRi is available I can work with my employer GeoCat to be >available in July-September timeframe > > > > Thanks > -- > Jody Garnett > > > On Mon, May 13, 2024 at 7:07 AM Lahr-Vivaz, Emilio < > emilio.lahr-vi...@ga-ccri.com> wrote: > > Hello, > > My company is interested in running GeoServer with Spring 6, and > considering if we can provide development support to help with that > upgrade. I see from the roadmap > <https://github.com/geoserver/geoserver/wiki/Jakarta-EE> that there is a > fair amount of work in progress, and a lot left to do. Would development > work in the July-September time frame be helpful, and if so are there any > particular tasks we could sign up for? > > Thanks, > > Emilio > > *Emilio Lahr-Vivaz* > General Atomics, CCRi > ___ > Geoserver-devel mailing list > Geoserver-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/geoserver-devel > > ___ > Geoserver-devel mailing list > Geoserver-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/geoserver-devel > ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
[Geoserver-devel] GeoServer 2.25.1 release train
I notice that both Ian and myself have signed up for the release this month :) It was my intension to do the stable releases when I have an opportunity to do so - by collaboration is good :) Are there any pull requests in need of review ahead of release? I see that the 18th falls on a Saturday so I am likely to set the release on Monday 20 May, and announce the following day (if everything goes well). -- Jody Garnett ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Re: [Geoserver-devel] Backporting filter parameter fixes for file blobstore
+1 Q: Is this fix intended for the 2.25.1 release next week? :) -- Jody Garnett On Fri, May 10, 2024 at 8:14 AM Andrea Aime < andrea.a...@geosolutionsgroup.com> wrote: > Hi all, > a month ago this PR that fixes an issue with filter parameters handling in > GWC file blob storage: > https://github.com/GeoWebCache/geowebcache/pull/1230 > > Some context: > >- Filter parameters in GWC allow the creation of parallel caches for >different parameter values (e.g., time, elevation, viewparam, env, anything >hanging an effect on the tile contents) >- Given the parameter contents might be long, complex, and not file >system friendly, all blob storages turn them into a summary string, a SHA1, >that identifies them (not entirely collision free, but the chance is really >low) >- The mapping between the sha1 and the actual set of parameter values >is stored too. And here is where the difference is, the cloud storages >store it in the same "folder" where the tiles are put, the file system in a >single, centralized property file for the layer > > The latter is handy, but at the same time, it creates a point of > contention among many threads/processes, and the file can grow very large > (think of long time series), exacerbating the problem to the point that > even just adding a new entry is slow. Add to that a NFS mount, and you have > all the elements for a horror movie. > > The PR simply aligns the file system blobstore practice with the cloud > storage case, where the file has only one entry, is immutable past > creation, and if two processes manage to step on each other toas, they > would still produce the same file content. > > And oh, the code is setup so that there is transparent migration of the > entries from the old to the new storage, so nothing is lost. > > Soo... objections to backport to stable/maintenance? > > Regards, > > Andrea Aime > > > == > GeoServer Professional Services from the experts! > > Visit http://bit.ly/gs-services-us for more information. > == > > Ing. Andrea Aime > @geowolf > Technical Lead > > GeoSolutions Group > phone: +39 0584 962313 > > fax: +39 0584 1660272 > > mob: +39 339 8844549 > > https://www.geosolutionsgroup.com/ > > http://twitter.com/geosolutions_it > > --- > > Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE > 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si > precisa che ogni circostanza inerente alla presente email (il suo > contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è > riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il > messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra > operazione è illecita. Le sarei comunque grato se potesse darmene notizia. > > This email is intended only for the person or entity to which it is > addressed and may contain information that is privileged, confidential or > otherwise protected from disclosure. We remind that - as provided by > European Regulation 2016/679 “GDPR” - copying, dissemination or use of this > e-mail or the information herein by anyone other than the intended > recipient is prohibited. If you have received this email by mistake, please > notify us immediately by telephone or e-mail > ___ > Geoserver-devel mailing list > Geoserver-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/geoserver-devel > ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Re: [Geoserver-devel] Jakarta EE upgrade support
Hello Emilio! It is really nice to hear from CCRi thank you for contacting us. It would be *very* helpful, while a fair amount of work is outlined (planning ahead) only a few activities are moving. It is always a risk sharing roadmap information for an open source project from a funding perspective. I am going to write an update Q2 roadmap blog post focusing just on: - Goals that are in progress now - Wicket Update - Goals that are actionable now - Spring-security update/rewrite for OAuth2 client / ImageN - Upcoming activities that have attracted in-kind or financial support Thus far we have not gotten sufficient financial / inkind response response to do planning, but at least folks are talking :) If it is okay with you I will list CCRi as committed for spring-framework update 'in-kind" activity in the hopes of attracting greater participation: - My understanding is if we add some Java startup parameters to "open javax" this activity could be worked ahead of ImageN availability. - Even if spring-framework upgrade cannot be worked on directly in July - some of the actives will be available and unblocked - If I know CCRi is available I can work with my employer GeoCat to be available in July-September timeframe Thanks -- Jody Garnett On Mon, May 13, 2024 at 7:07 AM Lahr-Vivaz, Emilio < emilio.lahr-vi...@ga-ccri.com> wrote: > Hello, > > My company is interested in running GeoServer with Spring 6, and > considering if we can provide development support to help with that > upgrade. I see from the roadmap > <https://github.com/geoserver/geoserver/wiki/Jakarta-EE> that there is a > fair amount of work in progress, and a lot left to do. Would development > work in the July-September time frame be helpful, and if so are there any > particular tasks we could sign up for? > > Thanks, > > Emilio > > *Emilio Lahr-Vivaz* > General Atomics, CCRi > ___ > Geoserver-devel mailing list > Geoserver-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/geoserver-devel > ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Re: [Geoserver-devel] Proposal for adding exact term search to search text-boxes
I was just checking in, I am sure it would be fine as an improvement in the bug tracker. I had considered avoiding double quotes, and just using white space separators (with the idea that would be easier for users to discover as it would occur naturally while typing). 'foo' --> foo 'foo ' --> (\s|^)foo(\s|$) 'foo bar' --> (\s|^)(foo|bar)+(\s|$) -- Jody Garnett On Fri, May 10, 2024 at 7:23 AM Andrea Aime < andrea.a...@geosolutionsgroup.com> wrote: > I think Alessandro used "propose" in loose terms, without necessarily > meaning GSIP. > Do you believe it's a GSIP worthy change? It seems mostly transparent to > the current usage. > > Regards, > > Andrea Aime > > > == > GeoServer Professional Services from the experts! > > Visit http://bit.ly/gs-services-us for more information. > == > > Ing. Andrea Aime > @geowolf > Technical Lead > > GeoSolutions Group > phone: +39 0584 962313 > > fax: +39 0584 1660272 > > mob: +39 339 8844549 > > https://www.geosolutionsgroup.com/ > > http://twitter.com/geosolutions_it > > --- > > Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE > 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si > precisa che ogni circostanza inerente alla presente email (il suo > contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è > riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il > messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra > operazione è illecita. Le sarei comunque grato se potesse darmene notizia. > > > This email is intended only for the person or entity to which it is > addressed and may contain information that is privileged, confidential or > otherwise protected from disclosure. We remind that - as provided by > European Regulation 2016/679 “GDPR” - copying, dissemination or use of this > e-mail or the information herein by anyone other than the intended > recipient is prohibited. If you have received this email by mistake, please > notify us immediately by telephone or e-mail > > > On Fri, May 10, 2024 at 7:22 AM Jody Garnett > wrote: > >> Alessandro, >> >> If you are happy with your proposal (it seems clear) could you admit is >> as a page to the wiki: >> https://github.com/geoserver/geoserver/wiki/Proposals >> >> There is a template >> <https://github.com/geoserver/geoserver/blob/main/doc/en/developer/source/policies/gsip_template.txt> >> to cut and paste (see developer guide >> <https://docs.geoserver.org/latest/en/developer/policies/gsip.html> for >> details). >> -- >> Jody Garnett >> >> >> On Apr 26, 2024 at 8:25:23 AM, Alessandro Ricchiuti < >> alessandro.ricchi...@geosolutionsgroup.com> wrote: >> >>> Hello, GeoServer Community. >>> >>> I am writing to propose a modification to the GeoServer web interface >>> that I believe would enhance the user experience and improve usability. >>> >>> The goal is to extend the search functionality within GeoServer pages by >>> introducing a specific feature that could help to better search for >>> elements with the textual search box. >>> >>> Background: >>> >>> Currently, the search functionality lacks the capability to find >>> specific words. Its full-text fashion simply returns any word that contains >>> the search term. For example, if a user searches for layers named "gis", he >>> may get results like gis_store and registered because the search term >>> appears within both words. >>> >>> >>> Proposal Overview: >>> >>> My proposal consists in expanding the syntax that the search box >>> recognizes, adding the possibility to have an exact term search just >>> quoting the word. >>> >>> >>> Follows a visual example in the screenshots below. >>> >>> >>> The full-text search has returned two layers as the results of the query >>> arch. >>> >>> As you can see, in the returned layers not only the actual arch layer >>> is present, but also the archive one, since the latter contains the >>> searched word in its name. >>> >>> >>> Here is an example showing the new functionality, where the search has >>> been made for an exact term, quoting the word: "arch". >>> >>> As a result, only the arch layer is displayed. >>> >>> >>> Impact and Benefits: >>> >>> Th
Re: [Geoserver-devel] Proposal for adding exact term search to search text-boxes
Alessandro, If you are happy with your proposal (it seems clear) could you admit is as a page to the wiki: https://github.com/geoserver/geoserver/wiki/Proposals There is a template <https://github.com/geoserver/geoserver/blob/main/doc/en/developer/source/policies/gsip_template.txt> to cut and paste (see developer guide <https://docs.geoserver.org/latest/en/developer/policies/gsip.html> for details). -- Jody Garnett On Apr 26, 2024 at 8:25:23 AM, Alessandro Ricchiuti < alessandro.ricchi...@geosolutionsgroup.com> wrote: > Hello, GeoServer Community. > > I am writing to propose a modification to the GeoServer web interface that > I believe would enhance the user experience and improve usability. > > The goal is to extend the search functionality within GeoServer pages by > introducing a specific feature that could help to better search for > elements with the textual search box. > > Background: > > Currently, the search functionality lacks the capability to find specific > words. Its full-text fashion simply returns any word that contains the > search term. For example, if a user searches for layers named "gis", he may > get results like gis_store and registered because the search term appears > within both words. > > > Proposal Overview: > > My proposal consists in expanding the syntax that the search box > recognizes, adding the possibility to have an exact term search just > quoting the word. > > > Follows a visual example in the screenshots below. > > > The full-text search has returned two layers as the results of the query > arch. > > As you can see, in the returned layers not only the actual arch layer is > present, but also the archive one, since the latter contains the searched > word in its name. > > > Here is an example showing the new functionality, where the search has > been made for an exact term, quoting the word: "arch". > > As a result, only the arch layer is displayed. > > > Impact and Benefits: > > These changes would not affect the default search functionality, that > would be still made on all the text attributes of the searched element > (layer, workspace, style, etc.). > > Additionally, users can combine full-text search with exact term search to > create more complex queries, such as: “history” “gis” arch (all elements > containing in their text fields the word history or all elements > containing in their text fields the word gis or all elements containing > in their text fields a word that contains arch). > > > Implementation Plan: > > The changes needed to implement this functionality should be limited to > the `GeoServerDataProvider` classes. Additionally, a tooltip explaining the > new syntax next to the search box would be beneficial for users. > > > I am eager to hear your thoughts and feedback on this proposal. > > Please feel free to share any concerns, suggestions, or alternative > approaches that you believe should be considered. > > > Best regards, > Alessandro Ricchiuti > == > Professional Support for GeoNode, GeoServer and MapStore from the experts! > Visit http://bit.ly/gs-services for more information. > == > > Alessandro Ricchiuti > Software Engineer > > GeoSolutions Group > phone: +39 0584 962313 > fax: +39 0584 1660272 > > https://www.geosolutionsgroup.com > https://twitter.com/geosolutions_it > > --- > This email is intended only for the person or entity to which it is > addressed and may contain information that is privileged, confidential or > otherwise protected from disclosure. We remind that - as provided by > European Regulation 2016/679 “GDPR” - copying, dissemination or use of this > e-mail or the information herein by anyone other than the intended > recipient is prohibited. If you have received this email by mistake, please > notify us immediately by telephone or e-mail. > ___ > Geoserver-devel mailing list > Geoserver-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/geoserver-devel > ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Re: [Geoserver-devel] "ADMIN" vs "ROLE_ADMINISTRATOR"
Hi David,
I created a ticket GEOS-11389
<https://osgeo-org.atlassian.net/browse/GEOS-11389> to continue the
discussion, but perhaps this should go on the "technical debt" wiki page.
It is surprisingly complicated.
--
Jody Garnett
On May 7, 2024 at 11:11:56 AM, David Blasby via Geoserver-devel <
geoserver-devel@lists.sourceforge.net> wrote:
> Hi,
>
> Here are my notes after the PMC meeting.
>
>
> After talking in the PMC meeting, a full-admin should have two roles;
> * ROLE_ADMINISTRATOR
> * ADMIN
>
> This is how the standard geoserver "admin" user is configured ("release"
> data dir).
>
> See the PMC meeting notes as well. No action for a while because this is
> "opening a can of worms."
>
> I will put a PR for the jwt-headers so it handles these multiple-roles
> better.
>
> CF:
>
> https://github.com/geoserver/geoserver/blob/main/data/release/security/rest.properties
>
>
>
> https://github.com/geoserver/geoserver/blob/a634daa9f243c818e1e7ae8ea3504f803676aa19/src/main/src/main/java/org/geoserver/security/impl/GeoServerRole.java#L21
>
>
>
> https://github.com/geoserver/geoserver/blob/6e9e25c0c7cdda9ada9f33f8255130d3afc76801/src/main/src/main/java/org/geoserver/security/impl/AbstractGeoServerSecurityService.java#L25
>
>
> https://github.com/geoserver/geoserver/blob/fb441eefa631a2f66b31b62c6811e44517493b2c/src/main/src/main/java/org/geoserver/security/GeoServerSecurityManager.java#L2047
>
> Thanks,
> Dave
>
> On Mon, May 6, 2024 at 5:23 PM David Blasby
> wrote:
>
>> Hi,
>>
>> I was doing some testing for the JWT Headers SSO module, and noticed a
>> problem when accessing the REST API.
>>
>> I've tracked this down to the roles "ADMIN" vs role "ROLE_ADMINISTRATOR".
>>
>> I believe (could be wrong) that the WEB uses the role
>> "ROLE_ADMINISTRATOR", but the REST API uses the role "ADMIN".
>>
>> This seems to be setup in -
>> https://github.com/geoserver/geoserver/blob/main/data/release/security/rest.properties
>>
>>
>> When I add "ADMIN" to my roles, the REST API allows me access.
>>
>> I am a bit confused on this - what is the difference between these roles
>> and should admin users have both these roles ("ADMIN" and
>> "ROLE_ADMINISTRATOR")?
>>
>> Thanks,
>> Dave
>>
> ___
> Geoserver-devel mailing list
> Geoserver-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>
___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
[Geoserver-devel] GeoServer PSC 2024-05-07
GeoTools / GeoServer PMC meeting - 2024-05-07Attending
-
David Blasby
-
Peter Smythe
-
Jody Garnett
-
Andrea Aime
Actions from prior meeting:
-
[DONE] Jody: Make a PR for GSIP 224
<https://github.com/geoserver/geoserver/wiki/GSIP-224>
-
[DONE] Peter: Make a similar proposal for GeoTools
-
[DONE] Jody: Make a Proposal for geoserver-users transition to discourse
Agenda:
-
GSIP-224 - Individual contributor clarification
<https://github.com/geoserver/geoserver/wiki/GSIP-224>
-
GSIP-223 - Community module graduation, amending generality rule
<https://github.com/geoserver/geoserver/wiki/GSIP-223>
-
GSIP-222 - Promote Raster Attribute Table module to extension
<https://github.com/geoserver/geoserver/wiki/GSIP-222>
-
GSIP-225 - Migrate geoserver-users from SourceForge to discourse
<https://github.com/geoserver/geoserver/wiki/GSIP-225>
-
https://github.com/geotools/geotools/wiki/Individual-contributor-clarification
-
Security roles internals
-
Record of meeting minutes
Actions:
-
Jody: Make a ticket about GROUP_ADMIN not having permission to create a
new user (GEOS-10938 <https://osgeo-org.atlassian.net/browse/GEOS-10938>)
-
Jody: Make a ticket on clean up of admin roles and constants (GEOS-11389
<https://osgeo-org.atlassian.net/browse/GEOS-11389>)
-
Jody: Open a ticket to refine Demo Page Javascript rewrite (GEOS-11390
<https://osgeo-org.atlassian.net/browse/GEOS-11390>)
GSIP-224 - Individual contributor clarification
https://github.com/geoserver/geoserver/wiki/GSIP-224
-
Is this done? yes
GSIP-223 - Community module graduation, amending generality rule
https://github.com/geoserver/geoserver/wiki/GSIP-223
No PR, Jody made a PR? Can we merge …
-
https://github.com/geoserver/geoserver/pull/7603 done
-
Does this need backport? Probably not since we only publish from main …
GSIP-222 - Promote Raster Attribute Table module to extension
https://github.com/geoserver/geoserver/wiki/GSIP-222
What is the status?
-
Proposal was not completed by the time the release window…
-
Not sure if this is merged can we check? Yes …
-
2.25 and main!
-
Updated Proposals <https://github.com/geoserver/geoserver/wiki/Proposals>
page to indicate this is complete
GSIP-225 - Migrate geoserver-users from SourceForge to discourse
https://github.com/geoserver/geoserver/wiki/GSIP-225
-
Proposal was made, and approved
What happens next:
-
user list to discourse is a go, we will wait on SAC for the change
-
Expected some kind of PR for the website to provide instructions
-
Then notify users of the change
-
Proposal has shutting down the SF list after 1 month, and migrate any
additional messages over
See proposal for details …
Encouragement from mastodon:
https://fosstodon.org/@geoserver/112367510772585467
GeoTools proposal for individual contributors
https://github.com/geotools/geotools/wiki/Individual-contributor-clarification
50% response rate …
-
Torben is away so assume +0
-
No objections
-
Likely to pass on May 9th :D
Could probably safely start the PR
Security roles internals
Email questions
-
Hard to talk about due to naming “role_admin” “admin”
“role_administrator”
-
Sometimes objects, sometimes strings
ROLE_ADMINISTRATOR
-
This is for the user interface, it unlocks the data admin console screens
ADMINISTRATOR
-
This is the “root” kind of access, often used for the REST API
-
Unlocks all the admin console for all the screens
GROUP_ADMIN
-
Unlocks the security admin console screens
The rest.properties is parsed:
-
The constants from GeoServerRole.java
<https://github.com/geoserver/geoserver/blob/main/src/main/src/main/java/org/geoserver/security/impl/GeoServerRole.java>
define the role objects
GeoServerRole ADMIN_ROLE = new GeoServerRole("ROLE_ADMINISTRATOR");
GeoServerRole GROUP_ADMIN_ROLE = new GeoServerRole("ROLE_GROUP_ADMIN");
GeoServerRole AUTHENTICATED_ROLE = new GeoServerRole("ROLE_AUTHENTICATED");
GeoServerRole ANY_ROLE = new GeoServerRole("*");
GeoServerRole ANONYMOUS_ROLE = new GeoServerRole("ROLE_ANONYMOUS");
The
https://github.com/geoserver/geoserver/blob/main/data/release/security/rest.properties
file is parsed:
/**;GET=ADMIN
/**;POST,DELETE,PUT=ADMIN
Parsed by AbstractGeoServerSecurityService.java
<https://github.com/geoserver/geoserver/blob/main/src/main/src/main/java/org/geoserver/security/impl/AbstractGeoServerSecurityService.java>
:
-
Has its own contents …
String DEFAULT_NAME = "default";
String DEFAULT_LOCAL_ADMIN_ROLE = "ADMIN";
String DEFAULT_LOCAL_GROUP_ADMIN_ROLE = "GROUP_ADMIN"
Re: [Geoserver-devel] "ADMIN" vs "ROLE_ADMINISTRATOR"
Thinking that this may be by design?
Admin gets full access, … including by default the rest api.
Role Admin is used to unlock some of the data admin screens in the user
interface ( and can be set on a workspace or layer level. )
Admin is required for the more advanced user interface screens like global
settings.
It may be that some of the REST API endpoints could be configured allow
Role Admin access?
--
Jody Garnett
On Mon, May 6, 2024 at 5:49 PM David Blasby via Geoserver-devel <
geoserver-devel@lists.sourceforge.net> wrote:
> Hi,
>
> I was doing some testing for the JWT Headers SSO module, and noticed a
> problem when accessing the REST API.
>
> I've tracked this down to the roles "ADMIN" vs role "ROLE_ADMINISTRATOR".
>
> I believe (could be wrong) that the WEB uses the role
> "ROLE_ADMINISTRATOR", but the REST API uses the role "ADMIN".
>
> This seems to be setup in -
> https://github.com/geoserver/geoserver/blob/main/data/release/security/rest.properties
>
>
> When I add "ADMIN" to my roles, the REST API allows me access.
>
> I am a bit confused on this - what is the difference between these roles
> and should admin users have both these roles ("ADMIN" and
> "ROLE_ADMINISTRATOR")?
>
> Thanks,
> Dave
> ___
> Geoserver-devel mailing list
> Geoserver-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>
___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Re: [Geoserver-devel] GSIP-225 - Migrate geoserver-users from SourceForge to discourse
Well this motion has passed, obtaining be bare minimum to do so. I did ask online for project's experience and encouragement on the change and got some useful responses <https://fosstodon.org/@geoserver/112367510772585467> from mastadon. I also had a go at configuring the staging environment <https://discourse.staging.osgeo.org/c/geoserver-users/12> with our branding (success) and background color (not really). -- Jody Garnett On Apr 25, 2024 at 8:23:37 AM, Jody Garnett wrote: > I have collected notes from yesterday's meeting into a proposal. > > GSIP-225 - Migrate geoserver-users from SourceForge to discourse > <https://github.com/geoserver/geoserver/wiki/GSIP-225> > > The proposal is held open for 10 days until Monday May 6th. > > >- Alessio Fabiani >- Andrea Aime >- Ian Turton >- Jody Garnett +1 >- Jukka Rahkonen >- Kevin Smith >- Nuno Oliveira >- Peter Smythe >- Simone Giannecchini >- Torben Barsballe > > > -- > Jody Garnett > ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Re: [Geoserver-devel] GSIP-225 - Migrate geoserver-users from SourceForge to discourse
Hey folks, this proposal is open for a few more days. Reviewing our earlier communication in January there was I believe a willingness to try discourse out. As I learn more about discourse I am more positive about the change. I was surprised that stack exchange has gotten a similar number of geoserver questions as our geoserver-users email list has received messages. The email workflow remains supported by this proposal; so your personal workflow can be maintained. -- Jody Garnett On Apr 25, 2024 at 8:23:37 AM, Jody Garnett wrote: > I have collected notes from yesterday's meeting into a proposal. > > GSIP-225 - Migrate geoserver-users from SourceForge to discourse > <https://github.com/geoserver/geoserver/wiki/GSIP-225> > > The proposal is held open for 10 days until Monday May 6th. > > >- Alessio Fabiani >- Andrea Aime >- Ian Turton >- Jody Garnett +1 >- Jukka Rahkonen >- Kevin Smith >- Nuno Oliveira >- Peter Smythe >- Simone Giannecchini >- Torben Barsballe > > > -- > Jody Garnett > ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Re: [Geoserver-devel] Proposal for adding exact term search to search text-boxes
That looks fun, +1 I considered if it could be more easily discoverable if a space separator was used; but the result was less clear. -- Jody Garnett On Fri, Apr 26, 2024 at 8:26 AM Alessandro Ricchiuti < alessandro.ricchi...@geosolutionsgroup.com> wrote: > Hello, GeoServer Community. > > I am writing to propose a modification to the GeoServer web interface that > I believe would enhance the user experience and improve usability. > > The goal is to extend the search functionality within GeoServer pages by > introducing a specific feature that could help to better search for > elements with the textual search box. > > Background: > > Currently, the search functionality lacks the capability to find specific > words. Its full-text fashion simply returns any word that contains the > search term. For example, if a user searches for layers named "gis", he may > get results like gis_store and registered because the search term appears > within both words. > > > Proposal Overview: > > My proposal consists in expanding the syntax that the search box > recognizes, adding the possibility to have an exact term search just > quoting the word. > > > Follows a visual example in the screenshots below. > > > The full-text search has returned two layers as the results of the query > arch. > > As you can see, in the returned layers not only the actual arch layer is > present, but also the archive one, since the latter contains the searched > word in its name. > > > Here is an example showing the new functionality, where the search has > been made for an exact term, quoting the word: "arch". > > As a result, only the arch layer is displayed. > > > Impact and Benefits: > > These changes would not affect the default search functionality, that > would be still made on all the text attributes of the searched element > (layer, workspace, style, etc.). > > Additionally, users can combine full-text search with exact term search to > create more complex queries, such as: “history” “gis” arch (all elements > containing in their text fields the word history or all elements > containing in their text fields the word gis or all elements containing > in their text fields a word that contains arch). > > > Implementation Plan: > > The changes needed to implement this functionality should be limited to > the `GeoServerDataProvider` classes. Additionally, a tooltip explaining the > new syntax next to the search box would be beneficial for users. > > > I am eager to hear your thoughts and feedback on this proposal. > > Please feel free to share any concerns, suggestions, or alternative > approaches that you believe should be considered. > > > Best regards, > Alessandro Ricchiuti > == > Professional Support for GeoNode, GeoServer and MapStore from the experts! > Visit http://bit.ly/gs-services for more information. > == > > Alessandro Ricchiuti > Software Engineer > > GeoSolutions Group > phone: +39 0584 962313 > fax: +39 0584 1660272 > > https://www.geosolutionsgroup.com > https://twitter.com/geosolutions_it > > --- > This email is intended only for the person or entity to which it is > addressed and may contain information that is privileged, confidential or > otherwise protected from disclosure. We remind that - as provided by > European Regulation 2016/679 “GDPR” - copying, dissemination or use of this > e-mail or the information herein by anyone other than the intended > recipient is prohibited. If you have received this email by mistake, please > notify us immediately by telephone or e-mail. > ___ > Geoserver-devel mailing list > Geoserver-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/geoserver-devel > ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Re: [Geoserver-devel] GSIP-225 - Migrate geoserver-users from SourceForge to discourse
Sorry I meant discourse - the proposal is correct It is the service being offered by OSGeo so worth a shot, I find it interesting that the same developer did both stackexchange and then discourse as improvement for small communities. -- Jody Garnett On Apr 25, 2024 at 9:01:59 AM, Ian Turton wrote: > +0 > > I can see moving to a new service but I'm not sure if discord is an > improvement > > Ian > > On Thu, 25 Apr 2024 at 16:24, Jody Garnett wrote: > >> I have collected notes from yesterday's meeting into a proposal. >> >> GSIP-225 - Migrate geoserver-users from SourceForge to discourse >> <https://github.com/geoserver/geoserver/wiki/GSIP-225> >> >> The proposal is held open for 10 days until Monday May 6th. >> >> >>- Alessio Fabiani >>- Andrea Aime >>- Ian Turton >>- Jody Garnett +1 >>- Jukka Rahkonen >>- Kevin Smith >>- Nuno Oliveira >>- Peter Smythe >>- Simone Giannecchini >>- Torben Barsballe >> >> >> -- >> Jody Garnett >> ___ >> Geoserver-devel mailing list >> Geoserver-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/geoserver-devel >> > > > -- > Ian Turton > ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
[Geoserver-devel] GSIP-225 - Migrate geoserver-users from SourceForge to discourse
I have collected notes from yesterday's meeting into a proposal. GSIP-225 - Migrate geoserver-users from SourceForge to discourse <https://github.com/geoserver/geoserver/wiki/GSIP-225> The proposal is held open for 10 days until Monday May 6th. - Alessio Fabiani - Andrea Aime - Ian Turton - Jody Garnett +1 - Jukka Rahkonen - Kevin Smith - Nuno Oliveira - Peter Smythe - Simone Giannecchini - Torben Barsballe -- Jody Garnett ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Re: [Geoserver-devel] GSIP 223, Community module graduation, amending generality rule
This was marked as passed in the PSC meeting March 26, changing it to an active proposal. -- Jody Garnett On Mar 26, 2024 at 10:32:45 AM, Peter Smythe wrote: > +1 > > Peter > > GeoServer PSC > AWS Solutions Architect > https://github.com/petersmythe > <https://fdfdfha.r.af.d.sendibt2.com/tr/cl/KiUJnvoWcw1hi1Az4Cnko8zw9P_Gf5QBAJadFSNm_MGk6JtQjnEYaP3z20JgajolZkqfhjJ_CqhYrTCnsgdCJczpsUFB6JiU89RqSkXe9FCCnt2WYaCE5_1E3IhuTVwhSxO5XyZ77B95f72dUaBhQSm_n03pu5ISy4_rWDQzKeHfh-kdJz9sIRZqxq9Tekt8mmA1_sLt6WGnIT5avtXrcvET_QhSYifN6_uXBvyugF4gMD1TThL8QgZkGwSeJ6CIgrgzC0y8WrlJ8rw-5y1s9p1s8lDfdkdAMoPaMj8> > > > On Fri, 15 Mar 2024 at 00:00, Andrea Aime < > andrea.a...@geosolutionsgroup.com> wrote: > >> Hi all, >> based on the conversations on list and during the PSC meeting, here is >> GSIP-223, to amend the community module graduation generality rule: >> >> https://github.com/geoserver/geoserver/wiki/GSIP-223 >> <https://fdfdfha.r.af.d.sendibt2.com/tr/cl/gKMO4TM-LcfbUtEPIzp2gPul2OKDLZPvL0sDnLnoEPzmhI7uKfIg5QQUuZrP8rIyyCIpSVP5Syr7OksKcHm8iciNFXSx0EUBUI41frQ9eY3BDmD6xLoahKYEwHBpGZV_6KGDzY4RLlCHR5yz3nflTtaC_cqRQODC7nIUZpdYL-R4DteMG-hc1_SlgTUSuc4njU439yJmjlnPD9kVIv5lMXoe-x-QZzJrhL2cRvJQ-8lm5edsuSB4N6O3UqusBHNyX1rg7tYQIrHHa6Sj8MfiRKHHDlF91cmvU8fp4kJL-MKuT-0Ze-IfSvEaYQF3NEz8Eljg_c7kevP9> >> >> Further feedback and votes welcomed. As indicated before, please stay on >> topic (rule 1 of the module graduation rules), collateral discussion is >> welcomed in its own separate thread. >> >> Regards, >> >> Andrea Aime >> >> >> == >> GeoServer Professional Services from the experts! >> >> Visit http://bit.ly/gs-services-us >> <https://fdfdfha.r.af.d.sendibt2.com/tr/cl/_3RUWoCkhPqVzwFTsrzoT-Zf_n_LsaMow6Se_tv3EVGroO2lR4yTp2tAgg386DP5iXt-YrAoQJhSKOkWNbSLcimatwMBA_h6Yg43CCHC0-PqrtZ9R5DD1Q7xKvyaheWrersrIhYQscieKo8KYnUtW3y6jNSi4kZkZDoUV309wImqPOB4CVZtB0XrM-r_iMArSqMtT3hiBWDab2L7la2bXayrEyRy0sXqxw5RMjsqXM8KHFLJjSL0p5kLwhRv6QN6gTWhFzIAMqaYnplvsjWanrIQrh4uVq19Zz6l> >> for more information. >> == >> >> Ing. Andrea Aime >> @geowolf >> Technical Lead >> >> GeoSolutions Group >> phone: +39 0584 962313 >> >> fax: +39 0584 1660272 >> >> mob: +39 339 8844549 >> >> https://www.geosolutionsgroup.com/ >> <https://fdfdfha.r.af.d.sendibt2.com/tr/cl/tw-Q8Gi-6ZIwNlR-BPX3Z0Q8q53hobjWI6fccjkeBFDwpcynBHENHpW4gaFkbYwk3qh0ys8wrVXwRrkg9Xuqmwpqr0HsBWmwuxIo020eTwZ6GZ5WQawDtXTYuXx6-eIw3eDpyju9OEcdu0-1elbFrd8INhr4mHNKW3gFb3QQG6qpk7ms9aXy9f0IXcY1_s_ufp6dFLTz8wVcqBl1QuRYZmN3HGPSMaWPaWX4Zd8m_z4Tcdw-wkl3HnbJbs0NZzZzCX6G56bkNeuQIY9ddDfHp2YuXXXYmVzv2bkpiPKZBNiJ> >> >> http://twitter.com/geosolutions_it >> <https://fdfdfha.r.af.d.sendibt2.com/tr/cl/NiVtOubkrMHR1GRpopQGoh6i8NA3gYjjCLeC7KPLrsQEFZodMLAe4jaMD2W482CYh1zB41eE2rQn22v-n2PzqmMPs_Cd0XC5m1MWa89Zt0kxhXtmfq8s4aXSYRWehZdnsTbM45JMRtAADsEhymyszALyuCT9GnEvszPV3RtW3_ZFLUwLy2dmDWWDGT3wlRhc0-s9enqfaD9MI0Yjch7jEtZNUvoIzwkbblH07TJgjtwX3rjarPlA3b6gMQ2-6bfodbX9BXLyemG0TN_VrP3JzsodgKmky-spS2FGn3BWfEDq> >> >> --- >> >> Con riferimento alla normativa sul trattamento dei dati personali (Reg. >> UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si >> precisa che ogni circostanza inerente alla presente email (il suo >> contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è >> riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il >> messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra >> operazione è illecita. Le sarei comunque grato se potesse darmene notizia. >> >> This email is intended only for the person or entity to which it is >> addressed and may contain information that is privileged, confidential or >> otherwise protected from disclosure. We remind that - as provided by >> European Regulation 2016/679 “GDPR” - copying, dissemination or use of this >> e-mail or the information herein by anyone other than the intended >> recipient is prohibited. If you have received this email by mistake, please >> notify us immediately by telephone or e-mail >> ___ >> Geoserver-devel mailing list >> Geoserver-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/geoserver-devel >> <https://fdfdfha.r.af.d.sendibt2.com/tr/cl/V-2BnbK-XNDEvKAYJiCfNOPbYwMbbi5N9KmFJ5BNF-iubLLQm3iZahocJYKM2vMzvWnfl53dxL3sr81r6B1FbXGHbS20xC51eFFhMPXsxwm2skn3h4DOwBkVa91Dr7S-j8ApuM7_fxqmTTv26SrcX5NiBuBCxyK3KW7VnNdnMb20b9Qqb7OxuW7uyEmpGuJKwOLBeEZui5rAmuqdKeDFEKfvBhcXC7QQyufgGNFGXnPhfUFZGXXzCOM4CbUKWKKdRdzlpUS2cwmd4wpsKt7pd_9_d0ODin3duKLtE8jIvIyZ7neb5FFWqKhHoZE5Ta4G1VJZlyIswE56f0qifplp> >> > ___ > Geoserver-devel mailing list > Geoserver-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/geoserver-devel > ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Re: [Geoserver-devel] GSIP 222: Graduating the Raster Attribute Table community module
Following up on GSIP-222: GSIP-222 - Promote Raster Attribute Table module to extension <https://github.com/geoserver/geoserver/wiki/GSIP-222> Can I mark this as addressed for GeoServer 2.25 on the proposal page <https://github.com/geoserver/geoserver/wiki/Proposals>? I could not find the associated jira ticket ... -- Jody Garnett On Mar 25, 2024 at 2:17:09 AM, Andrea Aime < andrea.a...@geosolutionsgroup.com> wrote: > Thank you all for voting, the proposal reached the 10 days and passed > with +1s and +0s. > I'll make the PR to graduate the module. > > Regards, > > Andrea Aime > > > == > GeoServer Professional Services from the experts! > > Visit http://bit.ly/gs-services-us for more information. > == > > Ing. Andrea Aime > @geowolf > Technical Lead > > GeoSolutions Group > phone: +39 0584 962313 > > fax: +39 0584 1660272 > > mob: +39 339 8844549 > > https://www.geosolutionsgroup.com/ > > http://twitter.com/geosolutions_it > > --- > > Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE > 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si > precisa che ogni circostanza inerente alla presente email (il suo > contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è > riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il > messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra > operazione è illecita. Le sarei comunque grato se potesse darmene notizia. > > This email is intended only for the person or entity to which it is > addressed and may contain information that is privileged, confidential or > otherwise protected from disclosure. We remind that - as provided by > European Regulation 2016/679 “GDPR” - copying, dissemination or use of this > e-mail or the information herein by anyone other than the intended > recipient is prohibited. If you have received this email by mistake, please > notify us immediately by telephone or e-mail > > > On Tue, Mar 12, 2024 at 12:23 PM Andrea Aime < > andrea.a...@geosolutionsgroup.com> wrote: > >> Hi all, >> (hello PSC members!), I'd like to start a discussion about graduating the >> Raster Attribute Table community module, proposal with details here: >> >> https://github.com/geoserver/geoserver/wiki/GSIP-222 >> >> Regards, >> >> Andrea Aime >> >> >> == >> GeoServer Professional Services from the experts! >> >> Visit http://bit.ly/gs-services-us for more information. >> == >> >> Ing. Andrea Aime >> @geowolf >> Technical Lead >> >> GeoSolutions Group >> phone: +39 0584 962313 >> >> fax: +39 0584 1660272 >> >> mob: +39 339 8844549 >> >> https://www.geosolutionsgroup.com/ >> >> http://twitter.com/geosolutions_it >> >> --- >> >> Con riferimento alla normativa sul trattamento dei dati personali (Reg. >> UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si >> precisa che ogni circostanza inerente alla presente email (il suo >> contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è >> riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il >> messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra >> operazione è illecita. Le sarei comunque grato se potesse darmene notizia. >> >> This email is intended only for the person or entity to which it is >> addressed and may contain information that is privileged, confidential or >> otherwise protected from disclosure. We remind that - as provided by >> European Regulation 2016/679 “GDPR” - copying, dissemination or use of this >> e-mail or the information herein by anyone other than the intended >> recipient is prohibited. If you have received this email by mistake, please >> notify us immediately by telephone or e-mail >> > ___ > Geoserver-devel mailing list > Geoserver-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/geoserver-devel > ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
[Geoserver-devel] GeoServer PSC Meeting notes April 23 2024
GeoTools / GeoServer PMC meeting - 2024-04-23Attending - Torben Barsballe - Andrea Aime - Jody Garnett - Jukka Rahkonnen - Peter Smythe Actions from prior meetings: - [DONE] Andrea: send an email for the release manager - [DONE] (no response yet) Jody: Reach out to Jo Cook (Astun) regarding core contributor status - [DONE] Jody: Propose adjustments to contributor policy requiring interaction on an individual (not organization) level Agenda - Crazy issue with Azure blobstore, and how to prevent it - GRIB backwards compatibility broken (with silver lining) - Mkdocs conversion getting it moving again - GSIP 224 discussion - Roadmap communication and chit-chat Actions - Jody: Make a PR for GSIP 224 <https://github.com/geoserver/geoserver/wiki/GSIP-224> - Peter: Make a similar proposal for GeoTools - Jody: Make a PR for geoserver-users transition to discourse Crazy issue with Azure blobstore, and how to prevent it GWC Report makes a massive amount of requests <https://github.com/GeoWebCache/geowebcache/issues/1149> to Azure blob store: - Deleting a layer / gridset resulted in an infinite loop due to a … jackson upgrade resulting in a regression - API uses JSON, we use jackson to parse the JSON including the token to page through results … and token was null when reaching the end - Jackson upgrade changed null to empty string, so infinite loop Can we run tests? - There is a cost (paid account), but for an infinite loop this would be expensive … - emulator + client library are a matched set - so we need to migrate to newer client library to make use of the API - Azure / S3 / etc… all have this lack of infrastructure to test against problem There is a public ticket here, but has not attracted interest / fix… - 33000 requests per min is expensive! - Fix was to check for empty string This is a good example of where the PSC can ask for funding? - Would have to set a hard limit of build server use (for each day a specific number of calls etc…) - This is also an example of shared risk, someone found the 33000 requests per min and reported it (so it was available for others to see and work on). - So we could estimate the cost to setup a “cloud infrastructure” testing … GRIB backwards compatibility broken (with silver lining) - Follow on to this from a few meetings ago … - Manual upgrade process documented <https://docs.geoserver.org/latest/en/user/installation/upgrade.html#grib-layers-geoserver-2-26-and-newer> (also for GeoTools <https://docs.geotools.org/latest/userguide/welcome/upgrade.html>)… - Can kind of guess and rewrite the variable names - But the time format changes so still some risk.. - We do expect time format to change once again (hopefully before September release cycle) - With all this … success we are now on a supported version netCDF library - Quite a bit faster (example 20x), especially on a network … mkdocs conversion getting it moving again - Jody is back from travel and available to work on this again - available on pypi: https://pypi.org/project/mkdocs-translate/0.4.0/ - tested by Andrea, can make it run, however breaking on pandoc - jody is using pandoc 3.1.7 (installed via homebrew) - latest is 2 weeks ago: pandoc 3.1.13 (pip only has up to 2.3, Mint up to 2.9) - GeoCat will provide a tester to help with the remaining A/B testing Examples of the kind of RST fixes to expect: - closed: https://github.com/geoserver/geoserver/pull/7429 applied fixes (yet to be backported) - open: https://github.com/geoserver/geoserver/pull/7462 pending rst fixes GSIP 224 discussion GSIP 224 clarification about be grateful to companies (while explaining that commit access is extended to individuals): GeoServer is grateful that organizations of all shapes and sizes support our project with in-kind participation of their employees. Extending commit access is made to individuals directly based on their expertise demonstrated over time. Proposal is approved - Jody will take an action to make a PR for GSIP224 - Peter to make a similar proposal for GeoTools Roadmap communication and chit-chat 2024 Q1: https://geoserver.org/behind%20the%20scenes/2024/01/03/roadmap.html https://github.com/geoserver/geoserver/wiki/Maintenance-%26-Roadmap 2024 Q2: jody is considering making another news announcement. - goal would be to emphasis the in-kind contributions / commitment - any progress… - fundraising progress … not very much sadly Q: What roadmap items can be worked on now? - As spring-framework upgrade is “stuck” pending fun
Re: [Geoserver-devel] GSIP-224 Individual Contributor clarification
This proposal is now approved, the text was slightly modified to indicate "grateful": GeoServer is *grateful* that organizations of all shapes and sizes support > our project with in-kind participation of their employees. Extending commit > access is made to individuals directly based on their expertise > demonstrated over time. > I will make a PR for this change. -- Jody Garnett On Apr 22, 2024 at 5:30:27 PM, Torben Barsballe wrote: > +1 > > Cheers, > Torben > > On Fri, Apr 19, 2024 at 1:23 PM Jody Garnett > wrote: > >> The proposal has the followin: >> >> GeoServer recognizes that organizations of all shapes and sizes support >> our project with in-kind participation of their employees. Extending commit >> access is made to individuals directly based on their expertise >> demonstrated over time. >> >> They s that sufficient? It was my intention to also recognize companies >> in the text. >> -- >> Jody Garnett >> >> >> On Fri, Apr 19, 2024 at 7:19 AM Andrea Aime < >> andrea.a...@geosolutionsgroup.com> wrote: >> >>> Hi Jody, >>> sounds good. At the same time, I would also made explicit that we are >>> thankful to companies, just in a different way. >>> Something like "companies contributing to GeoServer are recognized and >>> thanked for the time poured in individual contributors in the release >>> notes, and routinely, in conference presentations". >>> Does not have to be that exact wording mind, I just would like to also >>> point out the existing practice of being grateful to companies for >>> financial and in-kind contributions. >>> My worry is that the message could otherwise read "we care about the >>> individual, the company be damned", which is definitely not the case. >>> >>> Regards, >>> >>> Andrea Aime >>> >>> >>> == >>> GeoServer Professional Services from the experts! >>> >>> Visit http://bit.ly/gs-services-us for more information. >>> == >>> >>> Ing. Andrea Aime >>> @geowolf >>> Technical Lead >>> >>> GeoSolutions Group >>> phone: +39 0584 962313 >>> >>> fax: +39 0584 1660272 >>> >>> mob: +39 339 8844549 >>> >>> https://www.geosolutionsgroup.com/ >>> >>> http://twitter.com/geosolutions_it >>> >>> --- >>> >>> Con riferimento alla normativa sul trattamento dei dati personali (Reg. >>> UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si >>> precisa che ogni circostanza inerente alla presente email (il suo >>> contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è >>> riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il >>> messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra >>> operazione è illecita. Le sarei comunque grato se potesse darmene notizia. >>> >>> This email is intended only for the person or entity to which it is >>> addressed and may contain information that is privileged, confidential or >>> otherwise protected from disclosure. We remind that - as provided by >>> European Regulation 2016/679 “GDPR” - copying, dissemination or use of this >>> e-mail or the information herein by anyone other than the intended >>> recipient is prohibited. If you have received this email by mistake, please >>> notify us immediately by telephone or e-mail >>> >>> >>> On Tue, Apr 9, 2024 at 7:57 PM Jody Garnett >>> wrote: >>> >>>> Proposal for discussion >>>> https://github.com/geoserver/geoserver/wiki/GSIP-224 >>>> >>>> New text proposed for >>>> https://docs.geoserver.org/latest/en/developer/policies/committing.html >>>> page: >>>> >>>> All contributors are asked to provide an assignment agreement for >>>> working on the project: >>>> >>>> >>>>- individual_contributor >>>> <https://www.osgeo.org/resources/individual-contributor-license/> >>>> - Individual contributor agreement. >>>> >>>> >>>> >>>>- corporate_contributor >>>> <https://www.osgeo.org/resources/individual-contributor-license/> >>>> - Corporate contributor agreement to authorize employees to work >>>> on
Re: [Geoserver-devel] GeoServer 2.24.3 artifacts available for testing
Thanks for making the release Andrea, I see the release announcement is up also. -- Jody Garnett On Apr 19, 2024 at 7:31:25 AM, Andrea Aime < andrea.a...@geosolutionsgroup.com> wrote: > Hi all, > the 2.24.3 pre-release artifacts are available for testing here: > > https://build.geoserver.org/view/release/job/geoserver-release/140/artifact/distribution/2.24.3/ > > Regards, > > Andrea Aime > > > == > GeoServer Professional Services from the experts! > > Visit http://bit.ly/gs-services-us for more information. > == > > Ing. Andrea Aime > @geowolf > Technical Lead > > GeoSolutions Group > phone: +39 0584 962313 > > fax: +39 0584 1660272 > > mob: +39 339 8844549 > > https://www.geosolutionsgroup.com/ > > http://twitter.com/geosolutions_it > > --- > > Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE > 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si > precisa che ogni circostanza inerente alla presente email (il suo > contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è > riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il > messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra > operazione è illecita. Le sarei comunque grato se potesse darmene notizia. > > This email is intended only for the person or entity to which it is > addressed and may contain information that is privileged, confidential or > otherwise protected from disclosure. We remind that - as provided by > European Regulation 2016/679 “GDPR” - copying, dissemination or use of this > e-mail or the information herein by anyone other than the intended > recipient is prohibited. If you have received this email by mistake, please > notify us immediately by telephone or e-mail > ___ > Geoserver-devel mailing list > Geoserver-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/geoserver-devel > ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Re: [Geoserver-devel] GSIP-224 Individual Contributor clarification
The proposal has the followin: GeoServer recognizes that organizations of all shapes and sizes support our project with in-kind participation of their employees. Extending commit access is made to individuals directly based on their expertise demonstrated over time. They s that sufficient? It was my intention to also recognize companies in the text. -- Jody Garnett On Fri, Apr 19, 2024 at 7:19 AM Andrea Aime < andrea.a...@geosolutionsgroup.com> wrote: > Hi Jody, > sounds good. At the same time, I would also made explicit that we are > thankful to companies, just in a different way. > Something like "companies contributing to GeoServer are recognized and > thanked for the time poured in individual contributors in the release > notes, and routinely, in conference presentations". > Does not have to be that exact wording mind, I just would like to also > point out the existing practice of being grateful to companies for > financial and in-kind contributions. > My worry is that the message could otherwise read "we care about the > individual, the company be damned", which is definitely not the case. > > Regards, > > Andrea Aime > > > == > GeoServer Professional Services from the experts! > > Visit http://bit.ly/gs-services-us for more information. > == > > Ing. Andrea Aime > @geowolf > Technical Lead > > GeoSolutions Group > phone: +39 0584 962313 > > fax: +39 0584 1660272 > > mob: +39 339 8844549 > > https://www.geosolutionsgroup.com/ > > http://twitter.com/geosolutions_it > > --- > > Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE > 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si > precisa che ogni circostanza inerente alla presente email (il suo > contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è > riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il > messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra > operazione è illecita. Le sarei comunque grato se potesse darmene notizia. > > This email is intended only for the person or entity to which it is > addressed and may contain information that is privileged, confidential or > otherwise protected from disclosure. We remind that - as provided by > European Regulation 2016/679 “GDPR” - copying, dissemination or use of this > e-mail or the information herein by anyone other than the intended > recipient is prohibited. If you have received this email by mistake, please > notify us immediately by telephone or e-mail > > > On Tue, Apr 9, 2024 at 7:57 PM Jody Garnett > wrote: > >> Proposal for discussion >> https://github.com/geoserver/geoserver/wiki/GSIP-224 >> >> New text proposed for >> https://docs.geoserver.org/latest/en/developer/policies/committing.html >> page: >> >> All contributors are asked to provide an assignment agreement for working >> on the project: >> >> >>- individual_contributor >> <https://www.osgeo.org/resources/individual-contributor-license/> >> - Individual contributor agreement. >> >> >> >>- corporate_contributor >> <https://www.osgeo.org/resources/individual-contributor-license/> >> - Corporate contributor agreement to authorize employees to work >> on project. May also be used as a software grant to donate software to >> the >> project. >> >> >> GeoServer recognizes that organizations of all shapes and sizes support >> our project with in-kind participation of their employees. Extending commit >> access is made to individuals directly based on their expertise >> demonstrated over time. >> >> >> Thanks! >> -- >> Jody Garnett >> > ___ >> Geoserver-devel mailing list >> Geoserver-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/geoserver-devel >> > ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Re: [Geoserver-devel] GSIP-224 Individual Contributor clarification
So far there has been no discussion, so I am going to proceed with motion: A quick proposal to update the language to reflect GeoServer commit access > is granted to individuals (not a group). > Motion held open for 10 days until April 29th: - Alessio Fabiani - Andrea Aime - Ian Turton - Jody Garnett +1 initial motion - Jukka Rahkonen - Kevin Smith - Nuno Oliveira - Peter Smythe - Simone Giannecchini - Torben Barsballe Thanks -- Jody Garnett On Apr 9, 2024 at 7:56:45 PM, Jody Garnett wrote: > Proposal for discussion > https://github.com/geoserver/geoserver/wiki/GSIP-224 > > New text proposed for > https://docs.geoserver.org/latest/en/developer/policies/committing.html > page: > > All contributors are asked to provide an assignment agreement for working > on the project: > > >- individual_contributor > <https://www.osgeo.org/resources/individual-contributor-license/> > - Individual contributor agreement. > > > >- corporate_contributor > <https://www.osgeo.org/resources/individual-contributor-license/> > - Corporate contributor agreement to authorize employees to work on > project. May also be used as a software grant to donate software to the > project. > > > GeoServer recognizes that organizations of all shapes and sizes support > our project with in-kind participation of their employees. Extending commit > access is made to individuals directly based on their expertise > demonstrated over time. > > > Thanks! > -- > Jody Garnett > ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
[Geoserver-devel] GSIP-224 Individual Contributor clarification
Proposal for discussion https://github.com/geoserver/geoserver/wiki/GSIP-224 New text proposed for https://docs.geoserver.org/latest/en/developer/policies/committing.html page: All contributors are asked to provide an assignment agreement for working on the project: - individual_contributor <https://www.osgeo.org/resources/individual-contributor-license/> - Individual contributor agreement. - corporate_contributor <https://www.osgeo.org/resources/individual-contributor-license/> - Corporate contributor agreement to authorize employees to work on project. May also be used as a software grant to donate software to the project. GeoServer recognizes that organizations of all shapes and sizes support our project with in-kind participation of their employees. Extending commit access is made to individuals directly based on their expertise demonstrated over time. Thanks! -- Jody Garnett ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Re: [Geoserver-devel] Introducing WFS HTML outputformat Community Module
+1 that sounds like a good community module -- Jody Garnett On Thu, Mar 28, 2024 at 11:54 AM Alessio Fabiani < alessio.fabi...@geosolutionsgroup.com> wrote: > Dear Devs, > I would like to introduce a very small but useful community module, WFS > Freemarker Template. > > This one is a super-light module which basically allows to expose the HTML > output, the same used by the WMS module to render the GetFetureInfo one, > for the WFS too. > > The extension is optional, of course, and therefore the now output format > will be enabled only when installing the module. > > The WFS FreeMarker plugin enables the application of a FreeMarker template > to a WFS GetFeature response, allowing for the generation of HTML output, > akin to the functionality already present for WMS GetFeatureInfo requests. > > It leverages the same logic and machinery utilized in templating WMS > responses, utilizing the org.geoserver.wms.featureinfo.HTMLTemplateManager > mechanism. > > This feature is also accessible on the Layer Preview page in GeoServer, > where a new HTML output format is provided for the WFS preview. > > *NOTE*: This module requires a minor refactoring of the WMS > GetFeatureInfo classes in order to expose the HTMLFreemarkerTemplate > private class as a public one. > > -- > > Regards, > > Alessio Fabiani > > == > GeoServer Professional Services from the experts! > > Visit http://bit.ly/gs-services-us for more information. > == > > Ing. Alessio Fabiani > > @alfa7691 > Founder/Technical Lead > > > GeoSolutions Group > phone: +39 0584 962313 > > fax: +39 0584 1660272 > > mob: +39 331 6233686 > > https://www.geosolutionsgroup.com/ > > http://twitter.com/geosolutions_it > > --- > > Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE > 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si > precisa che ogni circostanza inerente alla presente email (il suo > contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è > riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il > messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra > operazione è illecita. Le sarei comunque grato se potesse darmene notizia. > > This email is intended only for the person or entity to which it is > addressed and may contain information that is privileged, confidential or > otherwise protected from disclosure. We remind that - as provided by > European Regulation 2016/679 “GDPR” - copying, dissemination or use of this > e-mail or the information herein by anyone other than the intended > recipient is prohibited. If you have received this email by mistake, please > notify us immediately by telephone or e-mail. > ___ > Geoserver-devel mailing list > Geoserver-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/geoserver-devel > ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Re: [Geoserver-devel] [Geotools-devel] GeoServer/GeoTools PMC Meeting at 18:30 CET / 10:30 PDT tomorrow
I am at OGC meeting today but will attend for a bit if available. Thanks to the team making the release and CVE processing. -- Jody Garnett On Tue, Mar 26, 2024 at 6:11 AM Torben Barsballe wrote: > Reminder that the next PMC meeting is scheduled for tomorrow, March 26, at > 18:30 > <https://www.timeanddate.com/worldclock/fixedtime.html?year=2024=3=26=18=30=0=GeoTools%20/%20GeoServer%20Meeting=1=1=215> > CET. > > We're still out of sync with Daylight Savings, so this will once again be > at *10:30am* instead of 9:30am PDT for the North American folks. > > You can join the meeting by following this link: > https://meet.osgeo.org/GeoServerMeeting > > Also, I'm not going to be able to make the meeting this week. > > Cheers, > Torben > ___ > GeoTools-Devel mailing list > geotools-de...@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/geotools-devel > ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Re: [Geoserver-devel] GSIP 223, Community module graduation, amending generality rule
Thanks Andrea, we will try and stay on topic I have updated the page with votes thus far. -- Jody Garnett On Mar 14, 2024 at 11:19:42 AM, Andrea Aime < andrea.a...@geosolutionsgroup.com> wrote: > Hi all, > based on the conversations on list and during the PSC meeting, here is > GSIP-223, to amend the community module graduation generality rule: > > https://github.com/geoserver/geoserver/wiki/GSIP-223 > > Further feedback and votes welcomed. As indicated before, please stay on > topic (rule 1 of the module graduation rules), collateral discussion is > welcomed in its own separate thread. > > Regards, > > Andrea Aime > > > == > GeoServer Professional Services from the experts! > > Visit http://bit.ly/gs-services-us for more information. > == > > Ing. Andrea Aime > @geowolf > Technical Lead > > GeoSolutions Group > phone: +39 0584 962313 > > fax: +39 0584 1660272 > > mob: +39 339 8844549 > > https://www.geosolutionsgroup.com/ > > http://twitter.com/geosolutions_it > > --- > > Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE > 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si > precisa che ogni circostanza inerente alla presente email (il suo > contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è > riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il > messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra > operazione è illecita. Le sarei comunque grato se potesse darmene notizia. > > This email is intended only for the person or entity to which it is > addressed and may contain information that is privileged, confidential or > otherwise protected from disclosure. We remind that - as provided by > European Regulation 2016/679 “GDPR” - copying, dissemination or use of this > e-mail or the information herein by anyone other than the intended > recipient is prohibited. If you have received this email by mistake, please > notify us immediately by telephone or e-mail > ___ > Geoserver-devel mailing list > Geoserver-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/geoserver-devel > ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Re: [Geoserver-devel] New Community Plugin: Features Autopopulate
+1 on the community module, it is an interesting addition. Kind of like a
minimal ELT stage.
--
Jody Garnett
On Mar 14, 2024 at 7:46:58 AM, Alessio Fabiani <
alessio.fabi...@geosolutionsgroup.com> wrote:
> Dear devs,
> presenting here a new community plugin. PR available here:
> https://github.com/geoserver/geoserver/pull/7474
>
> The Features Autopopulate plug-in listens to transactions (so far only
> issued by WFS), and autopopulates the feature type attributes according to
> the values retrieved from the properties file.
>
> The plugin uses a custom TransactionCallback that alters the insert/update
> WFS-T operations, forcing in specific values into them, based on
> configuration files.
>
> To support configuration for multiple layers, the easiest thing is to
> place a configuration, file in the directories of the layers themselves,
> pretty much like the featureinfo templates.
>
> A "transactionCustomizer.properties" file that contains a set of names and
> CQL expressions
> e.g.:
>
> ```
> UTENTE=env('GSUSER') # this will be replaced with the current user see
> @EnviromentInjectionCallback
> AGGIORNAMENTO=now() # this will be replaced with the current date
> ```
>
> To keep things simple, the expressions will just use environment
> variables, but not see the other values provided in the update/insert, and
> will not be differentiated by insert/update cases
>
> --
>
> Regards,
>
> Alessio Fabiani
>
> ==
> GeoServer Professional Services from the experts!
>
> Visit http://bit.ly/gs-services-us for more information.
> ==
>
> Ing. Alessio Fabiani
>
> @alfa7691
> Founder/Technical Lead
>
>
> GeoSolutions Group
> phone: +39 0584 962313
>
> fax: +39 0584 1660272
>
> mob: +39 331 6233686
>
> https://www.geosolutionsgroup.com/
>
> http://twitter.com/geosolutions_it
>
> ---
>
> Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE
> 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si
> precisa che ogni circostanza inerente alla presente email (il suo
> contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è
> riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il
> messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra
> operazione è illecita. Le sarei comunque grato se potesse darmene notizia.
>
> This email is intended only for the person or entity to which it is
> addressed and may contain information that is privileged, confidential or
> otherwise protected from disclosure. We remind that - as provided by
> European Regulation 2016/679 “GDPR” - copying, dissemination or use of this
> e-mail or the information herein by anyone other than the intended
> recipient is prohibited. If you have received this email by mistake, please
> notify us immediately by telephone or e-mail.
> ___
> Geoserver-devel mailing list
> Geoserver-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>
___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Re: [Geoserver-devel] Pre-proposal discussion, amending community module graduation rules
Andrea: I am in favour of being less *specific* in these kind of requirements in preference to stating the goal and providing an example. "The module is not site specific and can be configured for use by the general GeoServer community. A community module that already has 3 users would meet this goal; while a community module that has hard coded a domain name would not." (And I will stay on topic) -- Jody Garnett On Mar 12, 2024 at 4:19:42 AM, Andrea Aime < andrea.a...@geosolutionsgroup.com> wrote: > Hi all, > I'm starting this conversation to see if/how we can amend the procedures > for graduating a community module a bit. > > For reference, the current procedure is here: > > https://docs.geoserver.org/latest/en/developer/policies/community-modules.html#id2 > > In particular, I'm thinking about requirement "1", the module has at least > 3 users. > The reason for the check is a good one, we don't want to clutter the main > code base with modules that are specific to one single user site. At the > same time, this creates a "chicken and egg" problem, because many sites > won't consider using a module until it's supported. > > So, I'd like to keep the intent of requirement 1, but propose a change in > its implementation. 3 usage sites can be one of the options, but can we > also consider a PSC opinion on the matter as a valid alternative? And a PSC > member can provide feedback on the module generality while the graduation > is being voted. > > I know that Jody wants to also talk about point 3 (module being stable, as > a prerequisite, the standards that the module is based on being stable > too), but can we please have a separate thread for that? > > Best regards > Andrea > > == > GeoServer Professional Services from the experts! > > Visit http://bit.ly/gs-services-us for more information. > == > > Ing. Andrea Aime > @geowolf > Technical Lead > > GeoSolutions Group > phone: +39 0584 962313 > > fax: +39 0584 1660272 > > mob: +39 339 8844549 > > https://www.geosolutionsgroup.com/ > > http://twitter.com/geosolutions_it > > --- > > Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE > 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si > precisa che ogni circostanza inerente alla presente email (il suo > contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è > riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il > messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra > operazione è illecita. Le sarei comunque grato se potesse darmene notizia. > > This email is intended only for the person or entity to which it is > addressed and may contain information that is privileged, confidential or > otherwise protected from disclosure. We remind that - as provided by > European Regulation 2016/679 “GDPR” - copying, dissemination or use of this > e-mail or the information herein by anyone other than the intended > recipient is prohibited. If you have received this email by mistake, please > notify us immediately by telephone or e-mail > ___ > Geoserver-devel mailing list > Geoserver-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/geoserver-devel > ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Re: [Geoserver-devel] GSIP 222: Graduating the Raster Attribute Table community module
+1 Did you want to include this in the 2.25.0 release also? -- Jody Garnett On Mar 12, 2024 at 4:23:15 AM, Andrea Aime < andrea.a...@geosolutionsgroup.com> wrote: > Hi all, > (hello PSC members!), I'd like to start a discussion about graduating the > Raster Attribute Table community module, proposal with details here: > > https://github.com/geoserver/geoserver/wiki/GSIP-222 > > Regards, > > Andrea Aime > > > == > GeoServer Professional Services from the experts! > > Visit http://bit.ly/gs-services-us for more information. > == > > Ing. Andrea Aime > @geowolf > Technical Lead > > GeoSolutions Group > phone: +39 0584 962313 > > fax: +39 0584 1660272 > > mob: +39 339 8844549 > > https://www.geosolutionsgroup.com/ > > http://twitter.com/geosolutions_it > > --- > > Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE > 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si > precisa che ogni circostanza inerente alla presente email (il suo > contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è > riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il > messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra > operazione è illecita. Le sarei comunque grato se potesse darmene notizia. > > This email is intended only for the person or entity to which it is > addressed and may contain information that is privileged, confidential or > otherwise protected from disclosure. We remind that - as provided by > European Regulation 2016/679 “GDPR” - copying, dissemination or use of this > e-mail or the information herein by anyone other than the intended > recipient is prohibited. If you have received this email by mistake, please > notify us immediately by telephone or e-mail > ___ > Geoserver-devel mailing list > Geoserver-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/geoserver-devel > ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
[Geoserver-devel] mkdocs migration Monday
Hello geoserver-devel, It is my goal to address reported issues on Monday and start the mkdocs conversion. Thanks to testers who have now tested 40% of the content. With respect to the content I am on will leave the existing sphinx rst files in place for one release cycle so we can re-convert individual pages if their is a problem found after the documentation is public. I would appreciate any additional volunteers testing, please ask for edit access to mkdocs review <https://docs.google.com/spreadsheets/d/1HMqUpTirEwwSQfeNYikPjU0aFMl0-W4Xj44cg8V_VJA/edit?usp=sharing> spreadsheet. -- Jody Garnett On Feb 27, 2024 at 11:21:41 PM, Jody Garnett wrote: > Good evening GeoServer community, > > To start out with I would like to thank everyone who has signed up and > tested a few pages: > >- Alexandre Gacon >- Peter Smythe >- Andrea Aime >- GeoSpatial Techno >- Marcus Lingenfelder > > > With their help we about 1/4 of the way through reviewing the pages: > >- We identified a consistent problem with complicated tabes not >rendering (tables with. Nested notes and figures), these are now processed >into definition lists. > > > https://jodygarnett.github.io/geoserver/data/raster/imagemosaic/configuration/#primary-configuration-file >- Definition lists are styled to look like tables (see what I did >there!) which works out great for documenting step by step instructions >where field entry is needed. >https://jodygarnett.github.io/geoserver/ >- Examples that change based on version and release are correct (big >improvement, you can now cut and paste command line examples): >https://jodygarnett.github.io/geoserver/installation/docker/ >- The download, download extension and download community modules >external links look good (we can give it the nice appearance like the >docker page later): > >https://jodygarnett.github.io/geoserver/extensions/geopkg-output/install/ > > > While I think we are through the big problems I still need to ask for your > help: > > >1. I would like to ask 10 volunteers >2. If everyone can review 30 pages each we will be done >3. Lots of pages can be reviewed in under 1-2 mins: >- locate a row that "needs review" >- click on the "origional" link and open in an other tab >- click on the "migrated" link and open in an other tab >4. Swap between the pages to check >5. If they are the same (no content is lost), update the review column >to be done >6. If they are different change "needs review" to describing what is >different: >- many pages will have "block quotes" when none were intended (this is >something we need to fix by hand before conversion) > > > *Popular request BEFORE / AFTER * > > Reviewers asked to "see the markdown" that was generated. > >- Each page has a view source button at the top showing the generated >markdown >- Links to both the original rst and generated md are now available in >the review spreadsheet > > > *Sign up sheet* > > I am going to be focused on the 2.25-RC release candidate this week; but I > would like to check back next week with a list of things to fix. > > The sign up spreadsheet is here: mkdocs review > <https://docs.google.com/spreadsheets/d/1HMqUpTirEwwSQfeNYikPjU0aFMl0-W4Xj44cg8V_VJA/edit?usp=sharing> > (open > spreadsheet and ask for edit access). > > Please reply if you have any questions - I appreciate your help. > > Thanks to my employer, and GeoCat Live product, for the opportunity to > work on this activity. > -- > Jody Garnett > ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
[Geoserver-devel] GeoServer 2.25-RC release candidate
The GeoServer team is pleased to is share GeoServer 2.25-RC <https://geoserver.org/release/2.25-RC/>. Check out the release announcement <https://geoserver.org/announcements/2024/03/04/geoserver-2-25-RC-released.html> for what is new: - A number of configuration changes when updating - Experimental Java 21 support - JTS fast polygon intersection enabled by default - A lot of MapML improvements There has been a lot of research and development with new community modules: - Raster attribute Table community module - Graticules for WMS maps - GeoServer monitor Kafka storage - JWT Headers security extension Please try out this release candidate and let us know how it works for you! -- Jody Garnett ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Re: [Geoserver-devel] Starting the release train 2.25.x
The blog post has gotten a lot of feedback (thanks Andrea) and I have rewritten a couple sections. While I wait for confirmation testing the 2.25.x docker image shows that this file: - https://github.com/geoserver/docker/blob/master/build/release.sh Needed an updated to indicate MAIN=2.26.x (so that community modules are installed correctly). I am going to try and run the docker deploy step again. -- Jody Garnett On Mar 3, 2024 at 7:18:58 AM, Jody Garnett wrote: > Blog post is up, https://github.com/geoserver/geoserver.github.io/pull/187 > > Scheduled for Monday. > -- > Jody Garnett > > > On Mar 2, 2024 at 9:18:08 AM, Jody Garnett wrote: > >> Artifacts available for preflight testing: >> https://build.geoserver.org/view/geoserver/job/geoserver-release/lastSuccessfulBuild/artifact/distribution/2.25-RC/ >> >> Thanks! >> -- >> Jody Garnett >> >> >> On Mar 2, 2024 at 12:29:12 AM, Jody Garnett >> wrote: >> >>> The new branches are created, I will check in the morning if they build. >>> >>> The release process has a lot of manually editing of documentation >>> conf.py files I expect some troubleshooting before build is stable. >>> -- >>> Jody Garnett >>> >>> >>> On Mar 1, 2024 at 11:24:04 PM, Jody Garnett >>> wrote: >>> >>>> The GeoTools and GeoWebCache are built, in the middle of making the >>>> 2.25.x branch and jobs now. >>>> -- >>>> Jody Garnett >>>> >>> ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Re: [Geoserver-devel] Starting the release train 2.25.x
Blog post is up, https://github.com/geoserver/geoserver.github.io/pull/187 Scheduled for Monday. -- Jody Garnett On Mar 2, 2024 at 9:18:08 AM, Jody Garnett wrote: > Artifacts available for preflight testing: > https://build.geoserver.org/view/geoserver/job/geoserver-release/lastSuccessfulBuild/artifact/distribution/2.25-RC/ > > Thanks! > -- > Jody Garnett > > > On Mar 2, 2024 at 12:29:12 AM, Jody Garnett > wrote: > >> The new branches are created, I will check in the morning if they build. >> >> The release process has a lot of manually editing of documentation >> conf.py files I expect some troubleshooting before build is stable. >> -- >> Jody Garnett >> >> >> On Mar 1, 2024 at 11:24:04 PM, Jody Garnett >> wrote: >> >>> The GeoTools and GeoWebCache are built, in the middle of making the >>> 2.25.x branch and jobs now. >>> -- >>> Jody Garnett >>> >> ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Re: [Geoserver-devel] Starting the release train 2.25.x
Artifacts available for preflight testing: https://build.geoserver.org/view/geoserver/job/geoserver-release/lastSuccessfulBuild/artifact/distribution/2.25-RC/ Thanks! -- Jody Garnett On Mar 2, 2024 at 12:29:12 AM, Jody Garnett wrote: > The new branches are created, I will check in the morning if they build. > > The release process has a lot of manually editing of documentation conf.py > files I expect some troubleshooting before build is stable. > -- > Jody Garnett > > > On Mar 1, 2024 at 11:24:04 PM, Jody Garnett > wrote: > >> The GeoTools and GeoWebCache are built, in the middle of making the >> 2.25.x branch and jobs now. >> -- >> Jody Garnett >> > ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Re: [Geoserver-devel] Starting the release train 2.25.x
The new branches are created, I will check in the morning if they build. The release process has a lot of manually editing of documentation conf.py files I expect some troubleshooting before build is stable. -- Jody Garnett On Mar 1, 2024 at 11:24:04 PM, Jody Garnett wrote: > The GeoTools and GeoWebCache are built, in the middle of making the 2.25.x > branch and jobs now. > -- > Jody Garnett > ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
[Geoserver-devel] Starting the release train 2.25.x
The GeoTools and GeoWebCache are built, in the middle of making the 2.25.x branch and jobs now. -- Jody Garnett ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Re: [Geoserver-devel] mkdocs updates and before/after
Thanks for asking, I would like to ask people to check new pages so I can have a lot of content to work on and detect the same kind of problems occurring multiple times. If there was a page previously reported with errors I will mark it fixed when I have addressed the problem. If I marked a page you reviewed a fixed, you are welcome to go back and see how it turned out of course. As time goes on checking each page will be faster and faster, as I learn how to automate more fixes. -- Jody Garnett On Feb 28, 2024 at 9:56:24 PM, Alexandre Gacon wrote: > Hello Jody, > > Do you want reviewers to check again pages with errors after some changes > of your own or should we focus on reviewing more pages? > > Regards > Alexandre > > Le mer. 28 févr. 2024 à 08:22, Jody Garnett a > écrit : > >> Good evening GeoServer community, >> >> To start out with I would like to thank everyone who has signed up and >> tested a few pages: >> >>- Alexandre Gacon >>- Peter Smythe >>- Andrea Aime >>- GeoSpatial Techno >>- Marcus Lingenfelder >> >> >> With their help we about 1/4 of the way through reviewing the pages: >> >>- We identified a consistent problem with complicated tabes not >>rendering (tables with. Nested notes and figures), these are now processed >>into definition lists. >> >> >> https://jodygarnett.github.io/geoserver/data/raster/imagemosaic/configuration/#primary-configuration-file >>- Definition lists are styled to look like tables (see what I did >>there!) which works out great for documenting step by step instructions >>where field entry is needed. >>https://jodygarnett.github.io/geoserver/ >>- Examples that change based on version and release are correct (big >>improvement, you can now cut and paste command line examples): >>https://jodygarnett.github.io/geoserver/installation/docker/ >>- The download, download extension and download community modules >>external links look good (we can give it the nice appearance like the >>docker page later): >> >>https://jodygarnett.github.io/geoserver/extensions/geopkg-output/install/ >> >> >> While I think we are through the big problems I still need to ask for >> your help: >> >> >>1. I would like to ask 10 volunteers >>2. If everyone can review 30 pages each we will be done >>3. Lots of pages can be reviewed in under 1-2 mins: >>- locate a row that "needs review" >>- click on the "origional" link and open in an other tab >>- click on the "migrated" link and open in an other tab >>4. Swap between the pages to check >>5. If they are the same (no content is lost), update the review >>column to be done >>6. If they are different change "needs review" to describing what is >>different: >>- many pages will have "block quotes" when none were intended (this >>is something we need to fix by hand before conversion) >> >> >> *Popular request BEFORE / AFTER * >> >> Reviewers asked to "see the markdown" that was generated. >> >>- Each page has a view source button at the top showing the generated >>markdown >>- Links to both the original rst and generated md are now available >>in the review spreadsheet >> >> >> *Sign up sheet* >> >> I am going to be focused on the 2.25-RC release candidate this week; but >> I would like to check back next week with a list of things to fix. >> >> The sign up spreadsheet is here: mkdocs review >> <https://docs.google.com/spreadsheets/d/1HMqUpTirEwwSQfeNYikPjU0aFMl0-W4Xj44cg8V_VJA/edit?usp=sharing> >> (open >> spreadsheet and ask for edit access). >> >> Please reply if you have any questions - I appreciate your help. >> >> Thanks to my employer, and GeoCat Live product, for the opportunity to >> work on this activity. >> -- >> Jody Garnett >> ___ >> Geoserver-devel mailing list >> Geoserver-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/geoserver-devel >> > > > -- > Alexandre Gacon > ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Re: [Geoserver-devel] GeoServer 2.25-RC0 PR roundup
I will be merging the RST changes on the PR ahead of the 2.25-RC this week: - 7429 [GEOS-11221] mkdocs preflight rst fixes <https://github.com/geoserver/geoserver/pull/7429> These changes are all formatting to make content migration easier. In some cases they are fixing broken links (to OGC standards that have changed or dead Wikipedia pages). Can I ask for a review please. -- Jody Garnett On Feb 27, 2024 at 3:26:12 PM, Jody Garnett wrote: > I have a small PR for this weeks release-candidate: > > >- https://github.com/geoserver/geoserver/pull/7444 >- https://osgeo-org.atlassian.net/browse/GEOS-10438 > > > This changes the default behaviour entity resolution allow list, something > I have been intended to do for several release cycles now. > -- > Jody Garnett > ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
[Geoserver-devel] mkdocs updates and before/after
Good evening GeoServer community, To start out with I would like to thank everyone who has signed up and tested a few pages: - Alexandre Gacon - Peter Smythe - Andrea Aime - GeoSpatial Techno - Marcus Lingenfelder With their help we about 1/4 of the way through reviewing the pages: - We identified a consistent problem with complicated tabes not rendering (tables with. Nested notes and figures), these are now processed into definition lists. https://jodygarnett.github.io/geoserver/data/raster/imagemosaic/configuration/#primary-configuration-file - Definition lists are styled to look like tables (see what I did there!) which works out great for documenting step by step instructions where field entry is needed. https://jodygarnett.github.io/geoserver/ - Examples that change based on version and release are correct (big improvement, you can now cut and paste command line examples): https://jodygarnett.github.io/geoserver/installation/docker/ - The download, download extension and download community modules external links look good (we can give it the nice appearance like the docker page later): https://jodygarnett.github.io/geoserver/extensions/geopkg-output/install/ While I think we are through the big problems I still need to ask for your help: 1. I would like to ask 10 volunteers 2. If everyone can review 30 pages each we will be done 3. Lots of pages can be reviewed in under 1-2 mins: - locate a row that "needs review" - click on the "origional" link and open in an other tab - click on the "migrated" link and open in an other tab 4. Swap between the pages to check 5. If they are the same (no content is lost), update the review column to be done 6. If they are different change "needs review" to describing what is different: - many pages will have "block quotes" when none were intended (this is something we need to fix by hand before conversion) *Popular request BEFORE / AFTER * Reviewers asked to "see the markdown" that was generated. - Each page has a view source button at the top showing the generated markdown - Links to both the original rst and generated md are now available in the review spreadsheet *Sign up sheet* I am going to be focused on the 2.25-RC release candidate this week; but I would like to check back next week with a list of things to fix. The sign up spreadsheet is here: mkdocs review <https://docs.google.com/spreadsheets/d/1HMqUpTirEwwSQfeNYikPjU0aFMl0-W4Xj44cg8V_VJA/edit?usp=sharing> (open spreadsheet and ask for edit access). Please reply if you have any questions - I appreciate your help. Thanks to my employer, and GeoCat Live product, for the opportunity to work on this activity. -- Jody Garnett ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
[Geoserver-devel] GeoServer 2.25-RC0 PR roundup
I have a small PR for this weeks release-candidate: - https://github.com/geoserver/geoserver/pull/7444 - https://osgeo-org.atlassian.net/browse/GEOS-10438 This changes the default behaviour entity resolution allow list, something I have been intended to do for several release cycles now. -- Jody Garnett ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Re: [Geoserver-devel] New Community Module - JWT Headers (security)
+1 although I am your co-worker, others may have questions I know you are aware the transition to spring-framework 6 is planned; so the community module will need to be rewritten before becoming an extension; or did you just stick to spring-security core? I would like to get your PR in promptly so the docs are picked up in mkdocs migration. -- Jody Garnett On Feb 22, 2024 at 11:54:28 AM, David Blasby wrote: > Hi, > > This is a request to create a new community module. > > This is a fairly simple security module for header-based OAUTH2/OIDC type > authentication - for example Apache mod_auth_openid and robot-base-access > with JWT Access Tokens. > > New functionality: > > 1. Extract user name from a JSON header (including json path) > 2. Extract user name from an attached JWT token > 3. Extract Roles from JSON Header (including json path) > 4. Extract Roles from JWT Header (including json path) > 5. Role Translation from the external (IDP) names to internal GeoServer > role names > 6. Access Token Validation; > + signature validation > + expiry validation > + IDP external endpoint validation (including subject validation) > + audience validation > > Test coverage is about 90%. > > I will create a PR when approved. > > Code - > https://github.com/davidblasby/geoserver/tree/_jwtheaders/src/community/jwt-headers > > Doc - > https://github.com/davidblasby/geoserver/tree/_jwtheaders/doc/en/user/source/community/jwt-headers > > NOTE: I just put together the docs today - will be making them a bit > "nicer" next week. > > Some of the functionality is available in the very simple Headers security > extension and the oauth2-* community modules. This module is much simpler, > much more complete, and MUCH easier to maintain/test/configure. > > In fact, if you want to use OIDC and are willing to put your geoserver > behind apache (with mod_auth_openid), this module makes it MUCH MUCH easier > to setup and maintain wrt the oauth2-* community modules. If you want to > have GeoServer communicate DIRECTLY with your OIDC IDP, continue using the > oauth2-* community modules. > > NOTE: I am planning to add similar functionality to GeoNetwork. > > Thanks, > Dave > ___ > Geoserver-devel mailing list > Geoserver-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/geoserver-devel > ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Re: [Geoserver-devel] mkdocs preflight rst fixes, call out for any pending rst documentation changes
Here is a google spreadsheet which people can contribute to (just ask for access to edit). That way we can avoid multiple people checking the same page (and we can also know when we are done). https://docs.google.com/spreadsheets/d/1HMqUpTirEwwSQfeNYikPjU0aFMl0-W4Xj44cg8V_VJA/edit?usp=sharing -- Jody Garnett On Feb 22, 2024 at 5:14:34 AM, Andrea Aime < andrea.a...@geosolutionsgroup.com> wrote: > Hi Jody, > I believe some way to assign section to a volunteer is needed, or you'll > get some sections checked twice and others never > > Cheers > Andrea > > On Thu, Feb 22, 2024 at 10:48 AM Jody Garnett > wrote: > >> Okay docs are updated: https://jodygarnett.github.io/geoserver/ >> >> Taking the RST changes PR out of draft: >> https://github.com/geoserver/geoserver/pull/7429 >> >> The above PR is just the changes to RST files (and should be suitable for >> backport). >> -- >> Jody Garnett >> >> >> On Feb 21, 2024 at 8:29:08 AM, Jody Garnett >> wrote: >> >>> Thanks, I took some time out to document the translate script and teach >>> it to generate the nav tree from `toctree` directives: >>> https://jodygarnett.github.io/translate/ >>> >>> I would double check the translation is smooth, and take this out of >>> draft. >>> -- >>> Jody Garnett >>> >>> >>> On Wed, Feb 21, 2024 at 1:30 AM Andrea Aime < >>> andrea.a...@geosolutionsgroup.com> wrote: >>> >>>> Hi Jody, >>>> I had a quick look, but the PR is still marked as Draft. Will you let >>>> us know when it's "ready for review"? >>>> >>>> [image: image.png] >>>> >>>> Cheers >>>> Andrea >>>> >>>> >>>> >>>> On Sat, Feb 17, 2024 at 11:04 PM Jody Garnett >>>> wrote: >>>> >>>>> I have assembled a PR here of preflight changes to rst content: >>>>> https://github.com/geoserver/geoserver/pull/7429 >>>>> (Just hunting down some broken relative links and PR is ready to >>>>> review). >>>>> >>>>> I would live to convert next Wednesday 21 February, after (after the >>>>> stable release has gone out). >>>>> >>>>> Thanks >>>>> -- >>>>> Jody Garnett >>>>> >>>> ___ >>>>> Geoserver-devel mailing list >>>>> Geoserver-devel@lists.sourceforge.net >>>>> https://lists.sourceforge.net/lists/listinfo/geoserver-devel >>>>> >>>> >>>> >>>> -- >>>> >>>> Regards, >>>> >>>> Andrea Aime >>>> >>>> == >>>> GeoServer Professional Services from the experts! >>>> >>>> Visit http://bit.ly/gs-services-us for more information. >>>> == >>>> >>>> Ing. Andrea Aime >>>> @geowolf >>>> Technical Lead >>>> >>>> GeoSolutions Group >>>> phone: +39 0584 962313 >>>> >>>> fax: +39 0584 1660272 >>>> >>>> mob: +39 339 8844549 >>>> >>>> https://www.geosolutionsgroup.com/ >>>> >>>> http://twitter.com/geosolutions_it >>>> >>>> --- >>>> >>>> Con riferimento alla normativa sul trattamento dei dati personali (Reg. >>>> UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si >>>> precisa che ogni circostanza inerente alla presente email (il suo >>>> contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è >>>> riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il >>>> messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra >>>> operazione è illecita. Le sarei comunque grato se potesse darmene notizia. >>>> >>>> This email is intended only for the person or entity to which it is >>>> addressed and may contain information that is privileged, confidential or >>>> otherwise protected from disclosure. We remind that - as provided by >>>> European Regulation 2016/679 “GDPR” - copying, dissemination or use of this >>>> e-mail or the information herein by anyone other than the intended >>>> recipient is prohibited. If you have received this email by mistake, please &g
Re: [Geoserver-devel] 2024 roadmap - wiki pages
Thanks Peter for getting organized (my brain is fuzzy from doing regular expressions for several weeks). Here is a google spreadsheet which people can contribute to (just ask for access to edit). That way we can avoid multiple people checking the same page (and we can also know when we are done). https://docs.google.com/spreadsheets/d/1HMqUpTirEwwSQfeNYikPjU0aFMl0-W4Xj44cg8V_VJA/edit?usp=sharing There are instructions on that spreadsheet for how to sign up (first tab), and how to record problems (second tab), and provide feedback (third tab). Have a look, and request edit access to volunteer. -- Jody Garnett On Thu, Feb 22, 2024 at 7:56 AM Peter Smythe wrote: > Good day GeoServer users > > Here's a quick update to the effort coordination for the 2024 roadmap. > Thank you to the few individuals who have responded with offers of > assistance. > > The 9 tasks have been broken up into individual wiki pages, all linked > from > https://github.com/geoserver/geoserver/wiki/Maintenance-%26-Roadmap#2024-roadmap > <https://fdfdfha.r.af.d.sendibt2.com/tr/cl/DA0nss6mSuDpzEtvtmsVZVycSFpm7wBG33M4rgxwv2cXqFT-YsX_ShGe3SBwUADQlkJ5SBbyzJMnugE4BzQMpeJW-KgW_Qtq_lGCXQFrRMbAix4WEvKdTh3DepPmOTzm9BnJ_6sjX6jgitlV1tkFKrz695GeYYVE36LS_uqE8XysZhyucKPvRbL9PdFI518Ooe-oCjDC7NWYxaD7loMK8PcTzzRu1XGWNTC5TkSJxXZTeyiSr4MByH8f82h4RU-A9POKrnwDqEKA_DECelXTtRvg-ef4W6lqtsak7RuP1UPc23s2xAzhx-CwrWDpbIuIbO_S9PKgWsWZlHdKyGlTEjYkyJDgQoSdimNRq0hPS8_RuCawVTYGqDg>. > Please take a look at them, see which ones interest you and your company > the most, and put your name down to assist** > > One current task that I would like to highlight is the effort by Jody > (GeoCat) to migrate all the brilliant GeoServer documentation (that you > reference every week!) from sphinx to mkdocs: > https://github.com/geoserver/geoserver/wiki/Migrate-documentation-to-mkdocs > <https://fdfdfha.r.af.d.sendibt2.com/tr/cl/KeVXCoXbthFos6tQkETXV2N1IkqKVf0WATjJvjxrkchqtF2VvlslTXk5P2OTAsBwkNdI13eci9QtBnIb74vcvxx0aXyfv8yyo1cPEbknaj_iD_QD2bFfL9NJ-LTfG1pkFLmYnWVshKY_7Y0CEKqUkzEldE3zbOD4UOthippOUAQ-XjVmEGFZfXQr-1PNeEE28jcyTrSJxO6dII5UD8i-1a-MDn52cDSzAsbILe6SjvwoCmZ-uMpzFEk_8PAf4BeVT6_z_o_3TjfzPv3QTOmRJm_NaKAY2cchHki7rHXtCxpWuXANodupxGZqaEqqGRxkq5H7mZtFNIV2ZPKCaNJx1712uPpBqg75fUKGC1BZqvw> > > He has now asked for users to compare the old documentation to the new > documentation (preview found here: > https://jodygarnett.github.io/geoserver/ > <https://fdfdfha.r.af.d.sendibt2.com/tr/cl/XYdWuKQlyvyrMT3NCaiZG4674xdV9R4kBay_LvL3CtvO9XiQh6crkoYQuA979myCYi3sz7UzUyb1aSdk3F3a567DsQ67abmhkMDcfhfDg_p9r1QIzkElknDZsALZtiYR4JITtdI1h0A_hxwdKcA-LuSnavuqTkIiIK-T0sdslX1fwhHzWdMyUP11rrIQebJ0TPChFFJ-2iXG353l-tJvZMnL_bVOm1GVpMmci7wI8rC92spFguhGSP4ii_JHtpqamYT3RAB1c3cNUmAbawYpUMahfS3yRDeuV7WhWJAXDmwIfPA9-uPkEMU>) > and to let us know if there are any glaring issues, like broken links or > elements that are not properly rendered. He has done a fantastic job so > far of automating the migration, but *we need your eyes on the new > documentation*, please, for the final acceptance. > > *This is something that you can all get involved in!* > > ** How to make a wiki edit > Hmm, we're working on that. For now, please just reply by email with your > offer to help. > > ** How to report an issue with mkdocs > If you have a GitHub account, make a detailed comment in the pull request: > https://github.com/geoserver/geoserver/pull/7429 > <https://fdfdfha.r.af.d.sendibt2.com/tr/cl/o-ynFSXIWJCR3WrIzKb2V-EQEvyuwqnT64GRWXWyf8rSq4hGaOZooKlLgf4lPt3dq1rzIIrbu4rbwVuiQycNEJQ-5StUGuXDE0vVJTtT9itqBx9NtbP0BkUwL1-XZgzS2YuwpUldUqD1zeegO1QSu1NnCOXO0RrC_0-YwYP2xy3rdu1Fw7GA4cNZH4XjBxFrPc-hchuvqeo5UgBJfgsaWscemLpL9kP3YtE23uISEhP_fUE0WYrrywqXyoeRe-PvTcTY1eCqcew78YtDvtOWIQ65e-mp2dVFPR7QZo-it5ruYSiSmEBk0WEtp3JIiMzBP1_w8aM> > If you don't have a GitHub account, we would love you to make one, so that > you can contribute more easily: https://github.com/signup > <https://fdfdfha.r.af.d.sendibt2.com/tr/cl/ksm6Oy_m28OtV001HXPtroEGp0youJQgXvWl3JYDb-McLt3EDmmjMUBOTBfs53SI0x2N4E1kXTxcCu3RJRR8tdT_x6oVGscf55uBp3tQhXG63yDVp1Cu2KfgbRscvdao4huF8p6TJovK0biRZ5igd5ffhM1DQUexWDC94ska9p024tygE47md1NVbu2yXIPG-tnGm-zGGFI0swfuPMBHAF6zEl_T5jJKK7lLu82Qd1m2_4n_2ROHlPpl-EZHtVsdCe4wqKviqW9xiWeFPvLtEX1D_fP5GnpX> > (3 minutes, plus it is visually fun!) > If you really don't want to sign up, you can reply publically (preferably > not privately) and I will capture your feedback in the pull request for you. > > Thanks for your time! > > Peter > > GeoServer PSC > AWS Solutions Architect > https://github.com/petersmythe > <https://fdfdfha.r.af.d.sendibt2.com/tr/cl/obLyozLaHCg5OG-c0svUR1LD7kYzEd3ohJk0Fr68Mws_NiP53v2VhrDpVJbvBXvohPCJXkveh9eLlDEprQtNZtvpBRseEpunbRKcUGc0lEGbDZZs6ZWJ9MbRpjOAmgi7bcZ2fzbT_w_KWyNbuFPgqLgiPrkkKcSAkXXA6M-vdZsEBDAVLIAEdB2vcxvZI-0QJ8MY5DQDE65wI8bApLKY
Re: [Geoserver-devel] mkdocs preflight rst fixes, call out for any pending rst documentation changes
Maybe we can set up a spreadsheet? -- Jody Garnett On Thu, Feb 22, 2024 at 5:14 AM Andrea Aime < andrea.a...@geosolutionsgroup.com> wrote: > Hi Jody, > I believe some way to assign section to a volunteer is needed, or you'll > get some sections checked twice and others never > > Cheers > Andrea > > On Thu, Feb 22, 2024 at 10:48 AM Jody Garnett > wrote: > >> Okay docs are updated: https://jodygarnett.github.io/geoserver/ >> >> Taking the RST changes PR out of draft: >> https://github.com/geoserver/geoserver/pull/7429 >> >> The above PR is just the changes to RST files (and should be suitable for >> backport). >> -- >> Jody Garnett >> >> >> On Feb 21, 2024 at 8:29:08 AM, Jody Garnett >> wrote: >> >>> Thanks, I took some time out to document the translate script and teach >>> it to generate the nav tree from `toctree` directives: >>> https://jodygarnett.github.io/translate/ >>> >>> I would double check the translation is smooth, and take this out of >>> draft. >>> -- >>> Jody Garnett >>> >>> >>> On Wed, Feb 21, 2024 at 1:30 AM Andrea Aime < >>> andrea.a...@geosolutionsgroup.com> wrote: >>> >>>> Hi Jody, >>>> I had a quick look, but the PR is still marked as Draft. Will you let >>>> us know when it's "ready for review"? >>>> >>>> [image: image.png] >>>> >>>> Cheers >>>> Andrea >>>> >>>> >>>> >>>> On Sat, Feb 17, 2024 at 11:04 PM Jody Garnett >>>> wrote: >>>> >>>>> I have assembled a PR here of preflight changes to rst content: >>>>> https://github.com/geoserver/geoserver/pull/7429 >>>>> (Just hunting down some broken relative links and PR is ready to >>>>> review). >>>>> >>>>> I would live to convert next Wednesday 21 February, after (after the >>>>> stable release has gone out). >>>>> >>>>> Thanks >>>>> -- >>>>> Jody Garnett >>>>> >>>> ___ >>>>> Geoserver-devel mailing list >>>>> Geoserver-devel@lists.sourceforge.net >>>>> https://lists.sourceforge.net/lists/listinfo/geoserver-devel >>>>> >>>> >>>> >>>> -- >>>> >>>> Regards, >>>> >>>> Andrea Aime >>>> >>>> == >>>> GeoServer Professional Services from the experts! >>>> >>>> Visit http://bit.ly/gs-services-us for more information. >>>> == >>>> >>>> Ing. Andrea Aime >>>> @geowolf >>>> Technical Lead >>>> >>>> GeoSolutions Group >>>> phone: +39 0584 962313 >>>> >>>> fax: +39 0584 1660272 >>>> >>>> mob: +39 339 8844549 >>>> >>>> https://www.geosolutionsgroup.com/ >>>> >>>> http://twitter.com/geosolutions_it >>>> >>>> --- >>>> >>>> Con riferimento alla normativa sul trattamento dei dati personali (Reg. >>>> UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si >>>> precisa che ogni circostanza inerente alla presente email (il suo >>>> contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è >>>> riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il >>>> messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra >>>> operazione è illecita. Le sarei comunque grato se potesse darmene notizia. >>>> >>>> This email is intended only for the person or entity to which it is >>>> addressed and may contain information that is privileged, confidential or >>>> otherwise protected from disclosure. We remind that - as provided by >>>> European Regulation 2016/679 “GDPR” - copying, dissemination or use of this >>>> e-mail or the information herein by anyone other than the intended >>>> recipient is prohibited. If you have received this email by mistake, please >>>> notify us immediately by telephone or e-mail >>>> >>> > > -- > > Regards, > > Andrea Aime > > == > GeoServer Professional Services from the experts! > > Visit http://bit.ly/gs-services-us for mo
[Geoserver-devel] manual review of mkdocs migration
Hello GeoServer Team, Now that I have something ready to share I can *finally* as for some help - please review https://jodygarnett.github.io/geoserver/ page by page. - please added review comments somewhere I can find them (reply to this email (or on the https://github.com/geoserver/geoserver/pull/7429 PR). - As an example https://jodygarnett.github.io/geoserver/datadirectory/ is showing some broken links. - Note: We are just transferring documentation at this time, no content changes please. I will check back in tomorrow to see what has been found! -- Jody Garnett ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Re: [Geoserver-devel] mkdocs preflight rst fixes, call out for any pending rst documentation changes
Okay docs are updated: https://jodygarnett.github.io/geoserver/ Taking the RST changes PR out of draft: https://github.com/geoserver/geoserver/pull/7429 The above PR is just the changes to RST files (and should be suitable for backport). -- Jody Garnett On Feb 21, 2024 at 8:29:08 AM, Jody Garnett wrote: > Thanks, I took some time out to document the translate script and teach it > to generate the nav tree from `toctree` directives: > https://jodygarnett.github.io/translate/ > > I would double check the translation is smooth, and take this out of draft. > -- > Jody Garnett > > > On Wed, Feb 21, 2024 at 1:30 AM Andrea Aime < > andrea.a...@geosolutionsgroup.com> wrote: > >> Hi Jody, >> I had a quick look, but the PR is still marked as Draft. Will you let us >> know when it's "ready for review"? >> >> [image: image.png] >> >> Cheers >> Andrea >> >> >> >> On Sat, Feb 17, 2024 at 11:04 PM Jody Garnett >> wrote: >> >>> I have assembled a PR here of preflight changes to rst content: >>> https://github.com/geoserver/geoserver/pull/7429 >>> (Just hunting down some broken relative links and PR is ready to review). >>> >>> I would live to convert next Wednesday 21 February, after (after the >>> stable release has gone out). >>> >>> Thanks >>> -- >>> Jody Garnett >>> >> ___ >>> Geoserver-devel mailing list >>> Geoserver-devel@lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/geoserver-devel >>> >> >> >> -- >> >> Regards, >> >> Andrea Aime >> >> == >> GeoServer Professional Services from the experts! >> >> Visit http://bit.ly/gs-services-us for more information. >> == >> >> Ing. Andrea Aime >> @geowolf >> Technical Lead >> >> GeoSolutions Group >> phone: +39 0584 962313 >> >> fax: +39 0584 1660272 >> >> mob: +39 339 8844549 >> >> https://www.geosolutionsgroup.com/ >> >> http://twitter.com/geosolutions_it >> >> --- >> >> Con riferimento alla normativa sul trattamento dei dati personali (Reg. >> UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si >> precisa che ogni circostanza inerente alla presente email (il suo >> contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è >> riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il >> messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra >> operazione è illecita. Le sarei comunque grato se potesse darmene notizia. >> >> This email is intended only for the person or entity to which it is >> addressed and may contain information that is privileged, confidential or >> otherwise protected from disclosure. We remind that - as provided by >> European Regulation 2016/679 “GDPR” - copying, dissemination or use of this >> e-mail or the information herein by anyone other than the intended >> recipient is prohibited. If you have received this email by mistake, please >> notify us immediately by telephone or e-mail >> > ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Re: [Geoserver-devel] mkdocs preflight rst fixes, call out for any pending rst documentation changes
Thanks, I took some time out to document the translate script and teach it to generate the nav tree from `toctree` directives: https://jodygarnett.github.io/translate/ I would double check the translation is smooth, and take this out of draft. -- Jody Garnett On Wed, Feb 21, 2024 at 1:30 AM Andrea Aime < andrea.a...@geosolutionsgroup.com> wrote: > Hi Jody, > I had a quick look, but the PR is still marked as Draft. Will you let us > know when it's "ready for review"? > > [image: image.png] > > Cheers > Andrea > > > > On Sat, Feb 17, 2024 at 11:04 PM Jody Garnett > wrote: > >> I have assembled a PR here of preflight changes to rst content: >> https://github.com/geoserver/geoserver/pull/7429 >> (Just hunting down some broken relative links and PR is ready to review). >> >> I would live to convert next Wednesday 21 February, after (after the >> stable release has gone out). >> >> Thanks >> -- >> Jody Garnett >> > ___ >> Geoserver-devel mailing list >> Geoserver-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/geoserver-devel >> > > > -- > > Regards, > > Andrea Aime > > == > GeoServer Professional Services from the experts! > > Visit http://bit.ly/gs-services-us for more information. > == > > Ing. Andrea Aime > @geowolf > Technical Lead > > GeoSolutions Group > phone: +39 0584 962313 > > fax: +39 0584 1660272 > > mob: +39 339 8844549 > > https://www.geosolutionsgroup.com/ > > http://twitter.com/geosolutions_it > > --- > > Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE > 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si > precisa che ogni circostanza inerente alla presente email (il suo > contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è > riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il > messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra > operazione è illecita. Le sarei comunque grato se potesse darmene notizia. > > This email is intended only for the person or entity to which it is > addressed and may contain information that is privileged, confidential or > otherwise protected from disclosure. We remind that - as provided by > European Regulation 2016/679 “GDPR” - copying, dissemination or use of this > e-mail or the information herein by anyone other than the intended > recipient is prohibited. If you have received this email by mistake, please > notify us immediately by telephone or e-mail > ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Re: [Geoserver-devel] Hibernate version
Is there a problem updating content from one version of hibernate to the next? I have not heard of any plans to update, but I do not know a reason to stay on hibernate 3.6.9 either. -- Jody Garnett On Feb 19, 2024 at 6:22:54 AM, Niels Charlier via Geoserver-devel < geoserver-devel@lists.sourceforge.net> wrote: > Hello, > > Currently, the managed version of Hibernate is 3.6.9. This version is > rather ancient, from 2011. It is used by one extension: > geofence-server; and one community module: monitor-hibernate. > > Taskmanager, a community module that I maintain, uses a more recent > version of hibernate: 5.3.20. This does not pose any issues in building > and deploying as long as you do not combine it with either one of the > two other modules. However, the plugin ZIP file is broken and this > cannot be fixed because the 'release' module must choose one version for > everything. (This was reported by a user on jira: > https://osgeo-org.atlassian.net/browse/GEOS-10690) > > Are there any plans to upgrade the hibernate version of the other > modules? I don't think it even involves even any considerable coding > work, although it may generate a lot of 'deprecated' warnings. > > I noticed there has been talk about removing 'monitor-hibernate' > altogether. Since the community dir has its own release module, I > suppose it would be technically possible to change the version only > there, but perhaps rather confusing. > > Kind Regards > > Nuiels > > ___ > Geoserver-devel mailing list > Geoserver-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/geoserver-devel > ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Re: [Geoserver-devel] GeoServer PSC Meeting 2024-02-13
Understood, I can respect that. -- Jody Garnett On Feb 19, 2024 at 1:20:39 AM, Andrea Aime < andrea.a...@geosolutionsgroup.com> wrote: > On Fri, Feb 16, 2024 at 8:47 PM Jody Garnett > wrote: > >> Opinion: Andrea it is not the best use of resources to devote your time >> to making releases, as you are more effective reviewing PRs (and >> troubleshooting / RnD). >> In a year when we have some technical challenges mapped out we may be >> able to make a more effective arrangements. >> > > Best or not, we don't have enough people participating and we need to all > work on it, spreading out the load, > so that nobody burns out. > I can flip your reasoning, and note that having a single > developer performing most reviews is less than ideal. > > Cheers > Andrea > > == > > GeoServer Professional Services from the experts! > > Visit http://bit.ly/gs-services-us for more information. > == > > Ing. Andrea Aime > @geowolf > Technical Lead > > GeoSolutions Group > phone: +39 0584 962313 > > fax: +39 0584 1660272 > > mob: +39 339 8844549 > > https://www.geosolutionsgroup.com/ > > http://twitter.com/geosolutions_it > > --- > > Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE > 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si > precisa che ogni circostanza inerente alla presente email (il suo > contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è > riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il > messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra > operazione è illecita. Le sarei comunque grato se potesse darmene notizia. > > This email is intended only for the person or entity to which it is > addressed and may contain information that is privileged, confidential or > otherwise protected from disclosure. We remind that - as provided by > European Regulation 2016/679 “GDPR” - copying, dissemination or use of this > e-mail or the information herein by anyone other than the intended > recipient is prohibited. If you have received this email by mistake, please > notify us immediately by telephone or e-mail > ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
[Geoserver-devel] mkdocs preflight rst fixes, call out for any pending rst documentation changes
I have assembled a PR here of preflight changes to rst content: https://github.com/geoserver/geoserver/pull/7429 (Just hunting down some broken relative links and PR is ready to review). I would live to convert next Wednesday 21 February, after (after the stable release has gone out). Thanks -- Jody Garnett ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Re: [Geoserver-devel] Upcoming 2.25-RC Release candidate planning
One more to add to the list, as it has a big impact on PostGIS performance is may be worth a backport to the maintenance branch also: - [GEOS-11306] Java 21 and Java 17 check to allow GetFeature lazy JDBC count(*) optimization <https://github.com/geoserver/geoserver/pull/7428> -- Jody Garnett On Feb 15, 2024 at 11:59:25 PM, Jody Garnett wrote: > We are a couple weeks a way from the 2.25-RC and I am aware of a number of > outstanding pull-requests that are wishing review. > > >- [GEOS-11284] Promote community module "datadir catalog loader" to >core <https://github.com/geoserver/geoserver/pull/7421> >- Andrea is presently reviewing >- [GEOS-11050] Refactor Resources and Paths API to support alternative ><https://github.com/geoserver/geoserver/pull/7156> >- Jody (and possibly Gabe) to review >- If there is anything else please speak up! > > > NOTICE: As per last meeting I volunteered to do this release, checking my > work calendar I may be doing this a few days early (Feb 28-29). > -- > Jody Garnett > ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Re: [Geoserver-devel] GSIP 221 mkdocs progress and end-game
When I last checked in you were working on traversing rst table of contents directives to generate nav tree? Is it okay if I take on that part, and you can look at re-using it in generation of mkdocs.yml (for use converting other projects). Thanks for helping move this activity along and encouraging me with python stuff. -- Jody Garnett On Feb 15, 2024 at 11:52:47 PM, Jody Garnett wrote: > All documentation pages are now converted: > https://jodygarnett.github.io/geoserver/ > > Todo: > >- I have around 20 broken relative links to check >- The navigation to complete. >- (You can use search if you wish to review any pages not presently in >the nav). > > > Whew > > Andrea with respect to who can help, I am comfortable sharing this with > the user list and casting a wider net for review assistance. > -- > Jody Garnett > > > On Feb 15, 2024 at 8:09:14 AM, Jody Garnett > wrote: > >> I thanks for the thought, I think I am okay. >> >> I asked for some help when we go live to troubleshoot deploy as that is >> not something we can test ahead of time. >> >> I was stuck on downloads for a while (this is also not an urgent activity >> for me). >> >> Now that I am unstuck it is manual work doing a section creating the page >> navigation tree, repeat. I should have probably made a script for the nav >> tree creation. >> >> I am being pragmatic in fixing broken relative links and so on in the RST >> docs (rather than try and make the script robust). >> -- >> Jody Garnett >> >> >> On Thu, Feb 15, 2024 at 1:04 AM Andrea Aime < >> andrea.a...@geosolutionsgroup.com> wrote: >> >>> Hi Jody, >>> the plan looks good to me, what I'm missing right now is how you get >>> there. >>> During the meeting it was said you're working one section at a time, at >>> a superficial level >>> it seems half of them are still to be covered: >>> https://jodygarnett.github.io/geoserver/ >>> >>> Each section might hold surprises. So wondering if you need help and >>> who's up to do so >>> (calling myself out here, using the little I have to get the wicket >>> upgrade to completion... >>> besides I can do python only when chatgpt writes it for me 藍). >>> >>> Cheers >>> Andrea >>> >>> On Thu, Feb 15, 2024 at 8:35 AM Jody Garnett >>> wrote: >>> >>>> I have made considerable progress on the GSIP-221 >>>> <https://github.com/geoserver/geoserver/wiki/GSIP-221> script, you can >>>> see a preview here: https://jodygarnett.github.io/geoserver/styling/ >>>> >>>>- Downloads are now handled >>>>- Nested admonition directives are now handled >>>> >>>> >>>> Script is not as forgiving as sphinx-build so I will have some small >>>> pull-requests to clean up the rst docs before conversion. >>>> >>>> My plan is to: >>>> >>>> >>>>1. Give warning, and call for a documentation code freeze (this is >>>>disruptive as most PRs update the docs also). >>>>2. Run the script on all three active branches, producing three >>>>pull-requests >>>>3. Merge each branch in turn, ensuring docs are published to >>>>https://docs.geoserver.org as expected >>>> >>>> >>>> Is there anything I am missing? >>>> -- >>>> Jody Garnett >>>> >>> ___ >>>> Geoserver-devel mailing list >>>> Geoserver-devel@lists.sourceforge.net >>>> https://lists.sourceforge.net/lists/listinfo/geoserver-devel >>>> >>> >>> >>> -- >>> >>> Regards, >>> >>> Andrea Aime >>> >>> == >>> GeoServer Professional Services from the experts! >>> >>> Visit http://bit.ly/gs-services-us for more information. >>> == >>> >>> Ing. Andrea Aime >>> @geowolf >>> Technical Lead >>> >>> GeoSolutions Group >>> phone: +39 0584 962313 >>> >>> fax: +39 0584 1660272 >>> >>> mob: +39 339 8844549 >>> >>> https://www.geosolutionsgroup.com/ >>> >>> http://twitter.com/geosolutions_it >>> >>> --- >>> >>> Con riferimento alla normativa sul trattamento dei dati personali
Re: [Geoserver-devel] Upcoming 2.25-RC Release candidate planning
Thanks Gabe for being clear - we are operating with reduced resources these days and I need to ask for help where it can be effective. Niels I have set aside time next week to fix the bug getting in your way (for sure); and go over the javadocs API changes to see if we can work out a compromise. -- Jody Garnett On Feb 16, 2024 at 6:49:35 AM, Niels Charlier via Geoserver-devel < geoserver-devel@lists.sourceforge.net> wrote: > Hello Gabe, > > Okay, I will do that. > > I wish I had done it earlier actually, because it would have helped me > remember the details which are already fading :) > > Regards > > Niels > On 16/02/2024 15:36, Gabriel Roldan wrote: > > Hi, > > I do want to get involved in the ResourceStore API discussion. > > Unfortunately, I'll be on vacation next week, so if you don't mind I > propose we leave it off from this release. > > Meanwhile, I'd like to ask Niels to update the PR description with a > (rather succinct) description of the issue and breakdown of the approach. > That helps a lot in reviewing, and going through the very long discussion > on the email list is draining. > > TIA, > Gabe > *camptocamp* > INNOVATIVE SOLUTIONS > BY OPEN SOURCE EXPERTS > > *Gabriel Roldán* > Geospatial Developer > > > > On Fri, Feb 16, 2024 at 4:59 AM Jody Garnett > wrote: > >> We are a couple weeks a way from the 2.25-RC and I am aware of a number >> of outstanding pull-requests that are wishing review. >> >> >>- [GEOS-11284] Promote community module "datadir catalog loader" to >>core >> >> <https://dficcfc.r.af.d.sendibt2.com/tr/cl/uy2GjYiTnyfYzry_ryOcCtUfK1cFmz7nQcOz5pB4znyVuRZ8gKnn6WAccArwEtvngkFKPhDWQd9igi0SIm3Jo3_haZoSTyJHPrUUePjeAQIrHKF7F74Ghj63wnkddVLgvsXVS2uJKDfJgrNKPcje3HtClqHEuqR7vLIYEt28MF1r1NQPXn-YmBcKIY5CcOu9hB6n3zI_BaVcx3slejOQNhwypnOj5UmbLNFc2JaDR0yJiFvMbNTl7gnn1Vo_WU3993Q3G-Tjk8HP6G5ePQ76OI6kzJU_j9wqAtZ_yVwriyDMVj4gr_RYLHw6_xCTkQVmuDosYEY> >>- Andrea is presently reviewing >>- [GEOS-11050] Refactor Resources and Paths API to support alternative >> >> <https://dficcfc.r.af.d.sendibt2.com/tr/cl/li4NVJ7rI9pcvsHNOrTXSL4ky3IZENeOhT2vNHM8QeuzVPgGHzRCiudEL4DZyHs1Pn_9uk1D8RwumUGFgPaBufAnTkOEoHl9RQoQm-k1Uh4FgV9-llvZXa0KPVF3PH4MP7JuXUKfSvSlMZt0CsIAVKEaz74GXQo3bzdlHVOwb7tnaAhRstmYlEkay-tU-qjRx2W_-8M6rTYZh85EPiRdvZLASpXNmw6FKC6KeB8P4Zlo9n7-bwpE2Bk7M7SA8hcny5sTe7eZnwJIJsM70pcU3VY0C8FdOT3rwRxFC6kEXN7BsN6Bw5438jw_DOorn7Ol_lKdG9Y> >>- Jody (and possibly Gabe) to review >>- If there is anything else please speak up! >> >> >> NOTICE: As per last meeting I volunteered to do this release, checking my >> work calendar I may be doing this a few days early (Feb 28-29). >> -- >> Jody Garnett >> ___ >> Geoserver-devel mailing list >> Geoserver-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/geoserver-devel >> <https://dficcfc.r.af.d.sendibt2.com/tr/cl/Y3hsSy8dtF3lAfrWSugfxLJbDXBnsF6Yf9Ew4sELQE-FP48LbBnKG8-SzdabX0NjOpXMp091HGOhCU8qJqRt01aD-RTpYah61lIZhG0IW9oQLTjgXZsXIiJJjkbI-gR_RjmPNzzRdP9yzyhrDYRlnKK0mhUZy8dn8hmxTOeIR2jyEyWrhIEdkS6mgFJR8K7S37L2Dvv3p--GvwN-uTH2AP0XejYn0Oal6PhmkuEE4L_DCHuy-aKaGajmBq3kQnWhDO0Jq05MlucwuQ-5kt7IUxufmNqNslVi5UrDNJYCR_k8UP6_OjnV28sMvR2lIC9JW4_wBqVNKUsGlHfkNSA-> >> > > > ___ > Geoserver-devel mailing > listGeoserver-devel@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/geoserver-devel > > <https://dficcfc.r.af.d.sendibt2.com/tr/cl/czqWXBciB6xo0XlbfDhxi1PMFnLWPAe92KpwUkyEP56spLHVqWzbkI2hFT92ma_Dli9XPDGlke2SKa0XYz3DNurJZtjWxJlYGRjwDCeLZ-NfM-hQ3__C1gWvAAL0hh6vjxGJr3ibV0QH9kD80HFqM7F574nFfdAx8zZ9sNouG6nXhc7iflPSyLkGJTU2Vlfw7veKP_eZbAJkyS_MnHC4wTQhjUnSadlr971PjU6ZkPIJY_dop0ZwTPc49S1Pk55olzCfB395wPzBrWa11IEjX0Iij66ESISSet-CgrOF8cNQTsqsxfyZ7vd4fa9bsL3J62FlVAqkWPza3DzNBz7c> > > ___ > Geoserver-devel mailing list > Geoserver-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/geoserver-devel > ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Re: [Geoserver-devel] GeoServer PSC Meeting 2024-02-13
I am generally content to make the stable releases (in support of my GeoCat customers). Thanks for taking the 2.26-RC (I find making the release-candidate and all the jobs to be a bother with all the job creation and management.) Aside: It should be possible to change to a Jenkinsfile (so one job would be responsible for all branches) which is what we use at GeoCat. Opinion: Andrea it is not the best use of resources to devote your time to making releases, as you are more effective reviewing PRs (and troubleshooting / RnD). In a year when we have some technical challenges mapped out we may be able to make a more effective arrangements. -- Jody Garnett On Feb 16, 2024 at 6:31:33 AM, Andrea Aime < andrea.a...@geosolutionsgroup.com> wrote: > On Thu, Feb 15, 2024 at 8:40 AM Jody Garnett > wrote: > >> Release schedule >> >> GeoTools 29.5 / GeoServer 2.23.5 this month >> >> Need a volunteer - Andrea will ask around GeoSolutions but no promises. >> Fallback: Peter >> > > So, I will run the release on Monday. > > The company also asked if I can have a longer term plan of when we manage > releases, making time > available for 4 releases per year. > To set up for that, I've extended the release schedule until December > 2024, can anyone double check it? > https://github.com/geoserver/geoserver/wiki/Release-Schedule > > If it is correct, I'd book for the following releases (in addition to > Monday's one), making sure to include a RC in the mix: > >- 2024-05-18, 2.25.1 train >- 2024-09-02, 2.26-RC train >- 2024-12-18, 2.25.4 train > > Opinions? > > Cheers > Andrea > > == > > GeoServer Professional Services from the experts! > > Visit http://bit.ly/gs-services-us for more information. > == > > Ing. Andrea Aime > @geowolf > Technical Lead > > GeoSolutions Group > phone: +39 0584 962313 > > fax: +39 0584 1660272 > > mob: +39 339 8844549 > > https://www.geosolutionsgroup.com/ > > http://twitter.com/geosolutions_it > > --- > > Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE > 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si > precisa che ogni circostanza inerente alla presente email (il suo > contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è > riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il > messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra > operazione è illecita. Le sarei comunque grato se potesse darmene notizia. > > This email is intended only for the person or entity to which it is > addressed and may contain information that is privileged, confidential or > otherwise protected from disclosure. We remind that - as provided by > European Regulation 2016/679 “GDPR” - copying, dissemination or use of this > e-mail or the information herein by anyone other than the intended > recipient is prohibited. If you have received this email by mistake, please > notify us immediately by telephone or e-mail > ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
[Geoserver-devel] Upcoming 2.25-RC Release candidate planning
We are a couple weeks a way from the 2.25-RC and I am aware of a number of outstanding pull-requests that are wishing review. - [GEOS-11284] Promote community module "datadir catalog loader" to core <https://github.com/geoserver/geoserver/pull/7421> - Andrea is presently reviewing - [GEOS-11050] Refactor Resources and Paths API to support alternative <https://github.com/geoserver/geoserver/pull/7156> - Jody (and possibly Gabe) to review - If there is anything else please speak up! NOTICE: As per last meeting I volunteered to do this release, checking my work calendar I may be doing this a few days early (Feb 28-29). -- Jody Garnett ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Re: [Geoserver-devel] GSIP 221 mkdocs progress and end-game
All documentation pages are now converted: https://jodygarnett.github.io/geoserver/ Todo: - I have around 20 broken relative links to check - The navigation to complete. - (You can use search if you wish to review any pages not presently in the nav). Whew Andrea with respect to who can help, I am comfortable sharing this with the user list and casting a wider net for review assistance. -- Jody Garnett On Feb 15, 2024 at 8:09:14 AM, Jody Garnett wrote: > I thanks for the thought, I think I am okay. > > I asked for some help when we go live to troubleshoot deploy as that is > not something we can test ahead of time. > > I was stuck on downloads for a while (this is also not an urgent activity > for me). > > Now that I am unstuck it is manual work doing a section creating the page > navigation tree, repeat. I should have probably made a script for the nav > tree creation. > > I am being pragmatic in fixing broken relative links and so on in the RST > docs (rather than try and make the script robust). > -- > Jody Garnett > > > On Thu, Feb 15, 2024 at 1:04 AM Andrea Aime < > andrea.a...@geosolutionsgroup.com> wrote: > >> Hi Jody, >> the plan looks good to me, what I'm missing right now is how you get >> there. >> During the meeting it was said you're working one section at a time, at a >> superficial level >> it seems half of them are still to be covered: >> https://jodygarnett.github.io/geoserver/ >> >> Each section might hold surprises. So wondering if you need help and >> who's up to do so >> (calling myself out here, using the little I have to get the wicket >> upgrade to completion... >> besides I can do python only when chatgpt writes it for me 藍). >> >> Cheers >> Andrea >> >> On Thu, Feb 15, 2024 at 8:35 AM Jody Garnett >> wrote: >> >>> I have made considerable progress on the GSIP-221 >>> <https://github.com/geoserver/geoserver/wiki/GSIP-221> script, you can >>> see a preview here: https://jodygarnett.github.io/geoserver/styling/ >>> >>>- Downloads are now handled >>>- Nested admonition directives are now handled >>> >>> >>> Script is not as forgiving as sphinx-build so I will have some small >>> pull-requests to clean up the rst docs before conversion. >>> >>> My plan is to: >>> >>> >>>1. Give warning, and call for a documentation code freeze (this is >>>disruptive as most PRs update the docs also). >>>2. Run the script on all three active branches, producing three >>>pull-requests >>>3. Merge each branch in turn, ensuring docs are published to >>>https://docs.geoserver.org as expected >>> >>> >>> Is there anything I am missing? >>> -- >>> Jody Garnett >>> >> ___ >>> Geoserver-devel mailing list >>> Geoserver-devel@lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/geoserver-devel >>> >> >> >> -- >> >> Regards, >> >> Andrea Aime >> >> == >> GeoServer Professional Services from the experts! >> >> Visit http://bit.ly/gs-services-us for more information. >> == >> >> Ing. Andrea Aime >> @geowolf >> Technical Lead >> >> GeoSolutions Group >> phone: +39 0584 962313 >> >> fax: +39 0584 1660272 >> >> mob: +39 339 8844549 >> >> https://www.geosolutionsgroup.com/ >> >> http://twitter.com/geosolutions_it >> >> --- >> >> Con riferimento alla normativa sul trattamento dei dati personali (Reg. >> UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si >> precisa che ogni circostanza inerente alla presente email (il suo >> contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è >> riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il >> messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra >> operazione è illecita. Le sarei comunque grato se potesse darmene notizia. >> >> This email is intended only for the person or entity to which it is >> addressed and may contain information that is privileged, confidential or >> otherwise protected from disclosure. We remind that - as provided by >> European Regulation 2016/679 “GDPR” - copying, dissemination or use of this >> e-mail or the information herein by anyone other than the intended >> recipient is prohibited. If you have received this email by mistake, please >> notify us immediately by telephone or e-mail >> > ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Re: [Geoserver-devel] GSIP 221 mkdocs progress and end-game
I thanks for the thought, I think I am okay. I asked for some help when we go live to troubleshoot deploy as that is not something we can test ahead of time. I was stuck on downloads for a while (this is also not an urgent activity for me). Now that I am unstuck it is manual work doing a section creating the page navigation tree, repeat. I should have probably made a script for the nav tree creation. I am being pragmatic in fixing broken relative links and so on in the RST docs (rather than try and make the script robust). -- Jody Garnett On Thu, Feb 15, 2024 at 1:04 AM Andrea Aime < andrea.a...@geosolutionsgroup.com> wrote: > Hi Jody, > the plan looks good to me, what I'm missing right now is how you get there. > During the meeting it was said you're working one section at a time, at a > superficial level > it seems half of them are still to be covered: > https://jodygarnett.github.io/geoserver/ > > Each section might hold surprises. So wondering if you need help and who's > up to do so > (calling myself out here, using the little I have to get the wicket > upgrade to completion... > besides I can do python only when chatgpt writes it for me 藍). > > Cheers > Andrea > > On Thu, Feb 15, 2024 at 8:35 AM Jody Garnett > wrote: > >> I have made considerable progress on the GSIP-221 >> <https://github.com/geoserver/geoserver/wiki/GSIP-221> script, you can >> see a preview here: https://jodygarnett.github.io/geoserver/styling/ >> >>- Downloads are now handled >>- Nested admonition directives are now handled >> >> >> Script is not as forgiving as sphinx-build so I will have some small >> pull-requests to clean up the rst docs before conversion. >> >> My plan is to: >> >> >>1. Give warning, and call for a documentation code freeze (this is >>disruptive as most PRs update the docs also). >>2. Run the script on all three active branches, producing three >> pull-requests >>3. Merge each branch in turn, ensuring docs are published to >>https://docs.geoserver.org as expected >> >> >> Is there anything I am missing? >> -- >> Jody Garnett >> > ___ >> Geoserver-devel mailing list >> Geoserver-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/geoserver-devel >> > > > -- > > Regards, > > Andrea Aime > > == > GeoServer Professional Services from the experts! > > Visit http://bit.ly/gs-services-us for more information. > == > > Ing. Andrea Aime > @geowolf > Technical Lead > > GeoSolutions Group > phone: +39 0584 962313 > > fax: +39 0584 1660272 > > mob: +39 339 8844549 > > https://www.geosolutionsgroup.com/ > > http://twitter.com/geosolutions_it > > --- > > Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE > 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si > precisa che ogni circostanza inerente alla presente email (il suo > contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è > riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il > messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra > operazione è illecita. Le sarei comunque grato se potesse darmene notizia. > > This email is intended only for the person or entity to which it is > addressed and may contain information that is privileged, confidential or > otherwise protected from disclosure. We remind that - as provided by > European Regulation 2016/679 “GDPR” - copying, dissemination or use of this > e-mail or the information herein by anyone other than the intended > recipient is prohibited. If you have received this email by mistake, please > notify us immediately by telephone or e-mail > ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
[Geoserver-devel] GeoServer PSC Meeting 2024-02-13
GeoTools / GeoServer PMC meeting - 2024-02-13Attending
-
Peter Smythe
-
Gabriel Roldan
-
Jody Garnett
-
Torben Barsballe
-
Andrea Aime
-
Jukka Rahkonen
-
Kevin Smith
Actions from prior meetings:
-
[DONE] Peter: Make a PR to update the PSC list (in the developers guide)
gabe: Please help with review of #7156
-
[DONE] Peter: Check-in with Brad to see how we can help/plan
-
Peter: Share new wiki pages with the community
-
[WIP] gabe: Will make a PR for parallel loader
-
andrea: add peter to the security vulnerabilities issues
Agenda
-
Release schedule
-
mkdocs update
-
Discourse update
-
github security advisory graph question
-
Worldwide installations of GeoServers
-
Firefox redirection
-
GEOS-11284 Promote community module "datadir catalog loader" to core
-
GEOT-7411 App-schema performance improvement in setting attribute values
-
SLD Arrow Regression
-
JNDI documentation critical fix
-
“www” no longer serving JS apps
Actions
-
Peter: create a sed script to fix email addresses in sourceforge lists
export
-
Jody: setup a github workflow to use dependency submission API
<https://docs.github.com/en/code-security/supply-chain-security/understanding-your-software-supply-chain/using-the-dependency-submission-api>
-
Release schedule
GeoTools 29.5 / GeoServer 2.23.5 this month
Need a volunteer - Andrea will ask around GeoSolutions but no promises.
Fallback: Peter
Next RC cycle (2.25) is also approaching.
Adjusting release schedule to avoid extra 2.24 stable release…
https://github.com/geoserver/geoserver/wiki/Release-Schedule
Several potentially large changes outstanding:
-
Wicket 9 <https://github.com/geoserver/geoserver/pull/7154> (postpone to
2.26)
-
Resources and Paths API
<https://github.com/geoserver/geoserver/pull/7156>
-
one legit bug on windows
-
Firefox redirectionand stuck on difference of opinion on API meaning
(need to clarify javadoc)
-
action: gabe: volunteer to check in on this later in the month
(breakout meeting)
-
startup enhancements (should be good)
-
mkdocs (branch <https://github.com/geoserver/geoserver/tree/mkdocs>)
(timing would be good)
sidebar: Handling of WPS results with respect of ResourceStore and multiple
containers
-
there is some other way to handle that, can check system property
-
ideally a blob storage would be good for shared WPS output
-
Configure in WPS administration panel, where to share output
mkdocs update
Download directives now work:
https://jodygarnett.github.io/geoserver/introduction/license/
-
docs/introduciton/download/download.txt - lists “external” files
-
docs/introduction/download/.gitignore - to avoid storing duplicate files
-
mkdocs.yml has a hook to code to read download.txt above
Example of using {{ version }} and {{ release }}:
-
https://jodygarnett.github.io/geoserver/installation/docker/
-
Short term {{ release }}
-
Jody would like to grab these from pom.xml (this would be a change to
release procedure)
-
Or can we determine from git history
-
I cannot determine with git because our tags are not on our branch, ours
are not :)
Can we convert the chinese docs:
-
yes we could, there is a language chooser
-
can convert chinese docs later, run the script, need a native speaker to
review
-
jody has a script to convert language, but need a native speaker to
review results
Discourse update
https://trac.osgeo.org/osgeo/ticket/3104#comment:7
Migration broken by SF anonymization…
Action: Peter to create a sed script to fix email addresses
github security advisory graph question
A change to a published vulnerability came in from Mark:
-
https://github.com/github/advisory-database/pull/3483
-
Q: why is this not being made to our geoserver one?
Fundamental questions:
-
For a vulnerability in gs-web-core …
-
Do we also record gs-web-app? For the war overlay use?
-
Do we also record against the war for download use
-
Do we also record against the windows installer …
-
Would this change for wps extension?
Jody’s expectation is to write down the most specific thing … and trust the
tools
The answer provided by dependabot is a github action, that would run for
each tag, that would publish the “graph” based on the pom.xml file
relationships.
-
https://github.com/dependabot/dependabot-core/issues/2640
-
No it does not handle maven pom.xml directly, there is an action that
processes the dependency:tree into the “graph” used by the tools
-
would it be smart enough for profiles?
action: setup a github workflow to use dependency submission AP
[Geoserver-devel] GSIP 221 mkdocs progress and end-game
I have made considerable progress on the GSIP-221 <https://github.com/geoserver/geoserver/wiki/GSIP-221> script, you can see a preview here: https://jodygarnett.github.io/geoserver/styling/ - Downloads are now handled - Nested admonition directives are now handled Script is not as forgiving as sphinx-build so I will have some small pull-requests to clean up the rst docs before conversion. My plan is to: 1. Give warning, and call for a documentation code freeze (this is disruptive as most PRs update the docs also). 2. Run the script on all three active branches, producing three pull-requests 3. Merge each branch in turn, ensuring docs are published to https://docs.geoserver.org as expected Is there anything I am missing? -- Jody Garnett ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Re: [Geoserver-devel] Eclipse Setup
Everyone does what they like - we have build tools to keep formatting consistent (which makes life easier for everyone). Personally I use both IntelliJ and maven+text editor as the situation warrants. I use eclipse for large refactoring - although we did the last refactoring using scripts so it was crazy. I believe you can get Eclipse to work if that is your preferred choice. I would focus on maven integration and ignore the rest. Note: in IntelliJ I have to turn off a lot of the spring framework and JavaEE helpers because geoserver is split across so many modules the IDE produces warnings and confusion. -- Jody Garnett On Sat, Feb 3, 2024 at 8:54 AM Watermeyer, Andreas < andreas.waterme...@its-digital.de> wrote: > Hi Jody, > > thanks for your explanations, that helps me. > > Regarding the IDE: > Has the project agreed on the use of a different IDE or does everyone > follow their personal preference? What do you think is used by the > majority? > > -- > Andreas Watermeyer > > > >ITS Digital Solutions GmbH >Dillenburger Str. 77 | 51105 Köln > <https://www.google.com/maps/search/Dillenburger+Str.+77+%7C+51105+K%C3%B6ln?entry=gmail=g> >+49 231 222 49 370 >andreas.waterme...@its-digital.de >www.its-digital.de > > > > Sitz der Gesellschaft: Dortmund, Amtsgericht Dortmund, HRB 28563 > Geschäftsführer: Ludger Schulte, Gunnar Haack, Ralf Petersilka, Raimund > Schipp, Heinrich Toben > > Von: Jody Garnett > Gesendet: Samstag, 3. Februar 2024 05:52 > An: Watermeyer, Andreas > Cc: geoserver-devel@lists.sourceforge.net > Betreff: Re: [Geoserver-devel] Eclipse Setup > > [Externe E-Mail] Vorsicht beim Öffnen von Links und Anhängen. / Be careful > when opening links and attachments. > It has been a couple years since I used Eclipse IDE personally. I found > it was important to do one run on the command line to make the generated > code directories so the IDE could see them. > > For community modules we try and respect that they are experiments and > ensure they compile (so take part in any refactoring) - but we do not offer > them CPU cycles for testing on our build server (they are not stable enough > to always pass tests). > > We know for the work ahead that OAuth community plugins need to be > rewritten; if possible I would like to have one release cycle where new > community module for OIDC is made alongside the older one to allow folks to > migrate. But really for such an important component it difficult to > understand why they have not attracted funding to be stable. > > So goal is: > 1. include community module in refactor with the goal of compiling > 2. Include community module in dependency upgrade with goal of compiling > 3. When dependency upgrade cannot even compile (sigh) spend a few minuets > to determine why, comment the plugin of the “release” profile, and notify > the developer > > 1. How do you handle the extensions and the community modules > > Yes it does, I think this is why I stopped using Eclipse. > > 2. What do you do in case your changes on for example GS platform breaks > community code or community tests. > > The priority is the code: do whatever you can to make it compile. > If you really cannot get it to compile (say due to a dependency change) > drop it from the build. > The tests are not a priority at all, they are not included in the build. > > Your time as a volunteer is to be respected. > > 3. What is the expectation for the Jakarta EE migration regarding > extensions and community code? > > Extensions are part of the GeoServer application and will be migrated. > They are only optional to download, not optional to the GeoServer story. > The module maintainer put enough enough tests to help us as maintainers > just for situations like this. > (We experienced this first hand with the big bad geotools refactor last > year, the test coverage for GeoServer is really good and it makes the code > much more maintainable). > > Community modules are experiments, and to be treated as such. There tests > do not need to pass, or even be run. > > We have to respect our time as volunteers. > > 4. I wonder if you experience some specific problems, too and how you > handle them > > a) In geofence: "The package javax.xml.namespace is accessible from more > than one module: , java.xml". This causes a chain of compiler > errors for me in Eclipse. Similar in other projects. > > During the api change last year we had to make a branch on the geofence > project and work in parallel. > The same for geowebcache, and mapfish-print-v2. > > b) Eclipse has trouble with "GeoServerTestSupport" because it is > referenced tests of dependent projects, but i
Re: [Geoserver-devel] Eclipse Setup
It has been a couple years since I used Eclipse IDE personally. I found it was important to do one run on the command line to make the generated code directories so the IDE could see them. For community modules we try and respect that they are experiments and ensure they compile (so take part in any refactoring) - but we do not offer them CPU cycles for testing on our build server (they are not stable enough to always pass tests). We know for the work ahead that OAuth community plugins need to be rewritten; if possible I would like to have one release cycle where new community module for OIDC is made alongside the older one to allow folks to migrate. But really for such an important component it difficult to understand why they have not attracted funding to be stable. So goal is: 1. include community module in refactor with the goal of compiling 2. Include community module in dependency upgrade with goal of compiling 3. When dependency upgrade cannot even compile (sigh) spend a few minuets to determine why, comment the plugin of the “release” profile, and notify the developer *1. How do you handle the extensions and the community modules* Yes it does, I think this is why I stopped using Eclipse. *2. What do you do in case your changes on for example GS platform breaks community code or community tests.* The priority is the code: do whatever you can to make it compile. If you really cannot get it to compile (say due to a dependency change) drop it from the build. The tests are not a priority at all, they are not included in the build. Your time as a volunteer is to be respected. *3. What is the expectation for the Jakarta EE migration regarding extensions and community code?* Extensions are part of the GeoServer application and will be migrated. They are only optional to download, not optional to the GeoServer story. The module maintainer put enough enough tests to help us as maintainers just for situations like this. (We experienced this first hand with the big bad geotools refactor last year, the test coverage for GeoServer is really good and it makes the code much more maintainable). Community modules are experiments, and to be treated as such. There tests do not need to pass, or even be run. We have to respect our time as volunteers. *4. I wonder if you experience some specific problems, too and how you handle them* *a) In geofence: "The package javax.xml.namespace is accessible from more than one module: , java.xml". This causes a chain of compiler errors for me in Eclipse. Similar in other projects.* During the api change last year we had to make a branch on the geofence project and work in parallel. The same for geowebcache, and mapfish-print-v2. *b) Eclipse has trouble with "GeoServerTestSupport" because it is referenced tests of dependent projects, but it resides in gs-main/src/test/java, where it is not avaible for reuse. Normally it would expect that GeoServerTestSupport is in src/main/java of a test project or gs-main is an additional "test-jar" dependency. How do you handle that?* I remember being able to add a test dependency or something in eclipse. It is unusual but maven supports doing so. *c) Eclipse: Cannot nest "gs-rest-openapi-generated-feign-client/target/generated-sources/openapi/src/main/java" inside "gs-rest[...]".* I would talk to Gabe about that - it looks very cool. I assume it is an integration test. A generated maven project that eclipse has picked up? I do not think you edit that code directly, somehow ignore it from Eclipse and trust the command line to run that integration test. Have a good weekend yourself. -- Jody Garnett On Fri, Feb 2, 2024 at 10:23 AM Watermeyer, Andreas < andreas.waterme...@its-digital.de> wrote: > Hi community, > > I am trying to setup Eclipse 2023-12 with JDK 11 for the GeoServer project > to support in the Jakarta EE migration. I use the main branch and I pretty > much followed the developer guide. I have a couple of questions though: > > 1. How do you handle the extensions and the community modules: The > workspace gets pretty big having all those projects open and Eclipse is > quite slow especially on pom updates. Do you close the community module you > are not responsible for? > > 2. What do you do in case your changes on for example GS platform breaks > community code or community tests. Do you fix them? Or is the maintainer > expected to jump in? > > 3. What is the expectation for the Jakarta EE migration regarding > extensions and community code? > > 4. I wonder if you experience some specific problems, too and how you > handle them. For example: > > a) In geofence: "The package javax.xml.namespace is accessible from more > than one module: , java.xml". This causes a chain of compiler > errors for me in Eclipse. Similar in other projects. > > b) Eclipse has trouble with &
[Geoserver-devel] GeoServer PSC Meeting Notes 2024-01-30
GeoTools / GeoServer PMC meeting - 2024-01-30Attending - Torben Barsballe - Peter Smythe - Kevin Smith - Gabriel Roldan - Andrea Aime - Amir Nikfal - Jody Garnett Actions from prior meetings: - [DONE] action: Reopen ContentDataStore API ticket GEOT-7509 <https://osgeo-org.atlassian.net/browse/GEOT-7509> to update affected docs - Action: Wait for Carsten to read the above SQL Function discussion, and we can discuss further in email - action: Make a https://trac.osgeo.org/ right away to ask osgeo to purchase domain name (https://trac.osgeo.org/osgeo/ticket/3121#ticket) - [DONE] Action: Peter: create roadmap placeholder pages so we can list in-kind interested parties and sponsors - [DONE] action: Andrea creating a ticket <https://sourceforge.net/p/forge/site-support/25396/> for SF mailman download - [DONE] action: Jody to reply to email topic on getfeature freemarker encoding Agenda - [GEOT-7411] App-schema performance improvement in setting attribute values <https://github.com/geotools/geotools/pull/4410>ready to merge, no bandwidth to fix failing integration tests? - Welcome to Peter in the PSC - Extending Query to support sorting on expression - Security vulnerability update/review ahead of 2.25.0 release cycle - Release/Roadmap planning Actions - peter: Make a PR to update the PSC list (in the developers guide) gabe: Please help with review of #7156 - [done] peter: Check-in with Brad to see how we can help/plan - Peter: Share new wiki pages with the community - gabe: Will make a PR for parallel loader - andrea: add peter to the security vulnerabilities issues [GEOT-7411] App-schema performance improvement in setting attribute values ready to merge, no bandwidth to fix failing integration tests? PR has been re-aligned. Issue, there are failing tests in the postgis online app-schema tests: [ERROR] FeatureChainingWfsTest.testEncodeFeatureMember:1868->AbstractAppSchemaTestSupport.assertXpathCount:340 expected:<1> but was:<0> [ERROR] PagingTest.testGetFeatureWithCSVFormat:900 expected: but was: [ERROR] SRSWfsTest.testGetFeatureContent:148->AbstractAppSchemaTestSupport.assertXpathEvaluatesTo:329 expected:<[-1.2 52.5 -1.2 52.6 -1.1 52.6 -1.1 52.5 -1.2 52.5]> but was:<[52.5 -1.2 52.6 -1.2 52.6 -1.1 52.5 -1.1 52.5 -1.2]> [ERROR] SRSWfsTest.testReproject:378->AbstractAppSchemaTestSupport.assertXpathEvaluatesTo:329 expected:<[-1.2 52.5 -1.2 52.6 -1.1 52.6 -1.1 52.5 -1.2 52.5]> but was:<[52.5004 -1.2 52.6004 -1.2 52.6004 -1.1 52.5004 -1.1 5 Welcome to Peter in the PSC We appreciate all the help Peter has been giving to the project as of late! Welcome Peter to the PSC. action: - peter: Make a PR to update the PSC list <https://github.com/geoserver/geoserver/blob/main/doc/en/developer/source/policies/psc.rst> (in the developers guide) Extending Query to support sorting on expression Query SortBy allows sort on propertyName - We should be able to sort by an expression - Yes we should … make a GeoTools more general - May be a challenge for some DataStores? - Yeah but ContentDataStore handles this in memory or disk if your store cannot do the thing … - JDBCDataStore can learn how to do this, maybe Dialect? - PropertyName getPropertyName() // deprecated Expression getPropertyName() - Go through normal API change cycle, deprecate and remove - Make a proposal so we get all the tasks (example updating parsers) Great idea! Release/Roadmap planning We identified a bunch work: - Peter made wiki pages for helpers, in-kind assistance - https://github.com/geoserver/geoserver/wiki/Maintenance-%26-Roadmap Can we do anything for the 2.25 release cycle? - roadmap: If the wicket 9 upgrade is ready it can be included? Not sure … - volunteers are asking how to help (for manual testing)… - but we first need developers to finish - roadmap: nothing else is close to being ready - Niels resource store api PR <https://github.com/geoserver/geoserver/pull/7156> still needs jody to review (sigh) - https://github.com/geoserver/geoserver/pull/7156 - there is a solid test failure to fix here - Jody requests help as we seem to be at an impasse (Niels is correct in identifying the problem; just do not have a clear solution I am happy with) - Jody wants the paths to be consistent clear javadocs - roadmap: can we include the parallel loader please? - Gabe is using it as the default loader in geoserver-cloud. It has a bunch of production testing now (3-4 instances for some time now) -
Re: [Geoserver-devel] Geoserver 2.24.2 artifacts available for preflight testing
Thanks for feedback and testing, proceeding with release step. Peter we can have a moment to test Docker before announcing. -- Jody Garnett On Jan 24, 2024 at 7:30:15 AM, Jody Garnett wrote: > Hi Peter, > > You should be able to test against docker yes. > I am testing the maven artifacts today also. > -- > Jody Garnett > > > On Wed, Jan 24, 2024 at 3:23 AM Peter Smythe wrote: > >> Hi Jody >> >> Thanks for the release artefacts. I was able to use winsetup to install >> to Windows, manually downloading and adding the extensions that I use. >> GeoServer 2.24.2 ran with our most complex configurations, however, I was >> not able to fully test as I have not yet set up JNDI on this Windows >> laptop. I will still try to do that some time. >> >> However, as mentioned before, it might be far more useful to test against >> a *docker* pre-flight image, if that is available. >> >> I was able to determine from >> https://github.com/geoserver/geoserver/tree/2.24.x >> <https://fdfdfha.r.af.d.sendibt2.com/tr/cl/sA6p_kv-Z8UmS0cWVqzB53I1U54gFubHhtDqq__2tIeYgqxbtjefT3FxeisV24jYUGhF3min0sBNAJUawwULpX5XW7WjUug0_sDjlr52WDI8J5xFAEsWytAJT69oxW1v8v5YWHCzVAUq0MqYx7ACYZb3-a39Mj37Vpj8CySEXRk8iDGPybIXdsjfLS3_SRTy1TBygXx_nSty9SC3cDccOci1wrUZnRKai83ajJutq_gd1-gJt_VnBLA2BD5QwOhFggv17sKTiZvTowAVvNpwxYXlmLIEyH6kCauMdrCuuxjusLur7s6hGw> >> and >> https://github.com/geotools/geotools/tree/30.x >> <https://fdfdfha.r.af.d.sendibt2.com/tr/cl/CpgTegtIBAEWRY9NsdROXBKzMfef_BiYgvWcoLGjK-M3XhwoENrUSRYlpphuHcvJAUIf02ASYgUGyML3lIvV0YPbeTXfmNy8LQNyaHT3gQgC-tL4Gd5Xz_AFiq-ly34EyQUxHaJOlA8vXVSHBpxgyvu8uEpqH2vsICuwv2AzsTRIJYohIyhQPNgT-gwpISN3YRUOeUZqJub1wL9S__e5iF3gezfgna7mWT-s5OWPoFsXDHOe9R4ubDAlPC7VqXtmPhLWyXj90WVuyRNFcNtmXR4vxmwTjz1nYtZnbJwx9BoK8zqn> >> >> (but ignoring the recent >> https://github.com/GeoWebCache/geowebcache/tree/1.24.x >> <https://fdfdfha.r.af.d.sendibt2.com/tr/cl/NH8wGPkQE4ZAztgI-0UtK_V8hPBdWzwqNwh8xWGVObD50JUYba8YvtPowPU-BbPGxW5rDvqm6GXyFkLpwsmv_W7liUIxlu0KK40ZI3isVJmqGLDU8QHOFk3mb-CUi1hHXk6YkX5GR-2M722NDHgrqRQpd1-fGBXuldXx3lAqJUFGD-oM33-Anwf9v2nL1YPPm8OlY_LnpuFOAKbYOxiId5EGZ2gYuvpMU7ymcvCqKDD5jcsNuzsUe9vohSAYjsdU7jt2KP7jMXwRToATM9LHrSnWfKXvb6IpuwD5OgJVObmURvmdTzOzE12Y6po> >> commits) >> that there were no commits in the last 24 hours, so the most recent >> https://build.geoserver.org/view/geoserver/job/geoserver-2.24.x-nightly/ >> <https://fdfdfha.r.af.d.sendibt2.com/tr/cl/vAeko_gKWI7mRUW8PZTK38A2i25jPzkonqIDcoVP7ZPoH-GSb901jC04dTvYlMuIMQ4dL87JQQodfke37Crc89bdnwBzg9Nky5Z3ZkMSRFWX0zGrsFxYAvK2BYvYWdth4bdBEi16CjfPldk0Im5nR2OcmZNfXG0JppStAS1B5tR4fmOBFOs5cVVVqNvkHA3YxHmoDCBpC8cS1IlSKMfSBajG3A-t876iE5R-uMFWtgZZrHMwWAypx-2e3q3H40eZNbI8MB1u5xPvEqWWQu-u-BFbVClrlzp0dUKH7TyarmIMprsDZ0ywmn8JsEjq5WjDMSel5e8Ix7JYaiL3ncD4_w> >> should have produced a 2.24.x docker image at >> https://docker.osgeo.org/#browse/browse:docker:v2/geoserver/tags/2.24.x >> <https://fdfdfha.r.af.d.sendibt2.com/tr/cl/UO5n5ufSCbiRNO2Pi6qeenbyN-IL_BTngq7re3CL0vrl8TPJoiZu5erodrqivgJUadGo3NRiI-Bx3FMqFiK4ZPCdV-xqqq9C14dQHvIFgEJlNd8zKqgVtsfAwP-YyckLhIosvr0DcBwLf2alCI4XtJQ4Rc9-i2xky8tLsf0ufKp2Z0pE0_wbubeS-JiRtvvDe13BBt4aKNZ4m_tHhSk0vgdKzbJ5okDK2RTSnxSse_F5xh6U_G3NCm2wuPPHV8-qK51tyo43X6uSbGqC9VFUk4zyHJXV0z6QlGczGFl2o-rVDCUWMenqbyw_6fDxhaGrNif9-jT6jlJq4AiBzhLmw3oP-ouV> >> that approximates these pre-flight artefacts. (Actually, I see this docker >> image was produced 10 hours ago, when you built the release. Did you kick >> off another job, or is that now part of the automated release process?) >> >> Should we add to the "artefacts available" email a link/reference to the >> docker image for more developers to test against? >> >> Anyway, testing against this 2.24.x docker image was successful, >> including JNDI and all the extensions that we make use of. LGTM. >> >> Peter >> >> On Wed, 24 Jan 2024 at 04:04, Jody Garnett >> wrote: >> >>> Artifacts are available for pre-flight testing here: >>> >>>- >>> >>> https://build.geoserver.org/view/geoserver/job/geoserver-release/lastSuccessfulBuild/artifact/distribution/2.24.2/ >>> >>> <https://fdfdfha.r.af.d.sendibt2.com/tr/cl/ZhTxFyeeGp5kVUWy4duvVY9WZfg8SYJN1g33K5sgjSVd4YvGezV0XbE0roEuw8OHpFVlw8wmTAtoV3T0d4vGmzyXgmZrWrBzpJxf_8yBpEkbl-o4l6xGOr2GpS8rh0qJc1cSWxh13bocmIDOX7D-4VfP6Hjiz6DTffVc73sLQLWouuRBsDvqo1pWQrfnWyPDnY-dSG-o0ky70MsRNzPldiwtUvcDirB6Tj4bxjYv0KE5dsGH3Bx48QchczFpWXIDHXhvvXToQtViTKhEtzNBcOp9BQDt3fBMJ1il4cFFW9B3qystXaJz9LmexQr4wGv_qXN7OEP1vhKBorf1SHAL3SpBpYDttP18LwlzKy94CA2uFEEqK9tmOLgIJJ_d09OhDJhTI0x7abwlr6KETrH1IAsH> >>>- By the time you r
Re: [Geoserver-devel] GeoServer spring-security upgrade
Wow thanks, even just creating the tickets helps at this point in the game! Thoughts: - Yes you can very much start - Is it clear what needs to be done? Classic shoot first aim second ... - I am not sure if you want a wiki page for communication (or just use the tickets) -- Jody Garnett On Wed, Jan 24, 2024 at 7:42 AM Watermeyer, Andreas < andreas.waterme...@its-digital.de> wrote: > Hello community, > > as discussed with Jody and Andrea I can offer to work on the GeoServer > spring-security 5.8 upgrade. > > I have created corresponding issues: > * GEOS-11271: Upgrade spring-security to 5.8 [1] > * GEOS-11272: spring-security-oauth replacement, with spring-security 5.8 > [2] > > It would be nice if someone from the core team could confirm that I can > start to ensure that no other people step in and to avoid misunderstandings. > > [1] https://osgeo-org.atlassian.net/browse/GEOS-11271 > [2] https://osgeo-org.atlassian.net/browse/GEOS-11272 > > > Best regards, > Andreas > > >ITS Digital Solutions GmbH >Dillenburger Str. 77 | 51105 Köln >+49 231 222 49 370 >andreas.waterme...@its-digital.de >www.its-digital.de > > > > Sitz der Gesellschaft: Dortmund, Amtsgericht Dortmund, HRB 28563 > Geschäftsführer: Ludger Schulte, Gunnar Haack, Ralf Petersilka, Raimund > Schipp, Heinrich Toben > > > > ___ > Geoserver-devel mailing list > Geoserver-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/geoserver-devel > ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Re: [Geoserver-devel] Geoserver 2.24.2 artifacts available for preflight testing
Hi Peter, You should be able to test against docker yes. I am testing the maven artifacts today also. -- Jody Garnett On Wed, Jan 24, 2024 at 3:23 AM Peter Smythe wrote: > Hi Jody > > Thanks for the release artefacts. I was able to use winsetup to install to > Windows, manually downloading and adding the extensions that I use. > GeoServer 2.24.2 ran with our most complex configurations, however, I was > not able to fully test as I have not yet set up JNDI on this Windows > laptop. I will still try to do that some time. > > However, as mentioned before, it might be far more useful to test against > a *docker* pre-flight image, if that is available. > > I was able to determine from > https://github.com/geoserver/geoserver/tree/2.24.x > <https://fdfdfha.r.af.d.sendibt2.com/tr/cl/sA6p_kv-Z8UmS0cWVqzB53I1U54gFubHhtDqq__2tIeYgqxbtjefT3FxeisV24jYUGhF3min0sBNAJUawwULpX5XW7WjUug0_sDjlr52WDI8J5xFAEsWytAJT69oxW1v8v5YWHCzVAUq0MqYx7ACYZb3-a39Mj37Vpj8CySEXRk8iDGPybIXdsjfLS3_SRTy1TBygXx_nSty9SC3cDccOci1wrUZnRKai83ajJutq_gd1-gJt_VnBLA2BD5QwOhFggv17sKTiZvTowAVvNpwxYXlmLIEyH6kCauMdrCuuxjusLur7s6hGw> > and > https://github.com/geotools/geotools/tree/30.x > <https://fdfdfha.r.af.d.sendibt2.com/tr/cl/CpgTegtIBAEWRY9NsdROXBKzMfef_BiYgvWcoLGjK-M3XhwoENrUSRYlpphuHcvJAUIf02ASYgUGyML3lIvV0YPbeTXfmNy8LQNyaHT3gQgC-tL4Gd5Xz_AFiq-ly34EyQUxHaJOlA8vXVSHBpxgyvu8uEpqH2vsICuwv2AzsTRIJYohIyhQPNgT-gwpISN3YRUOeUZqJub1wL9S__e5iF3gezfgna7mWT-s5OWPoFsXDHOe9R4ubDAlPC7VqXtmPhLWyXj90WVuyRNFcNtmXR4vxmwTjz1nYtZnbJwx9BoK8zqn> > > (but ignoring the recent > https://github.com/GeoWebCache/geowebcache/tree/1.24.x > <https://fdfdfha.r.af.d.sendibt2.com/tr/cl/NH8wGPkQE4ZAztgI-0UtK_V8hPBdWzwqNwh8xWGVObD50JUYba8YvtPowPU-BbPGxW5rDvqm6GXyFkLpwsmv_W7liUIxlu0KK40ZI3isVJmqGLDU8QHOFk3mb-CUi1hHXk6YkX5GR-2M722NDHgrqRQpd1-fGBXuldXx3lAqJUFGD-oM33-Anwf9v2nL1YPPm8OlY_LnpuFOAKbYOxiId5EGZ2gYuvpMU7ymcvCqKDD5jcsNuzsUe9vohSAYjsdU7jt2KP7jMXwRToATM9LHrSnWfKXvb6IpuwD5OgJVObmURvmdTzOzE12Y6po> > commits) > that there were no commits in the last 24 hours, so the most recent > https://build.geoserver.org/view/geoserver/job/geoserver-2.24.x-nightly/ > <https://fdfdfha.r.af.d.sendibt2.com/tr/cl/vAeko_gKWI7mRUW8PZTK38A2i25jPzkonqIDcoVP7ZPoH-GSb901jC04dTvYlMuIMQ4dL87JQQodfke37Crc89bdnwBzg9Nky5Z3ZkMSRFWX0zGrsFxYAvK2BYvYWdth4bdBEi16CjfPldk0Im5nR2OcmZNfXG0JppStAS1B5tR4fmOBFOs5cVVVqNvkHA3YxHmoDCBpC8cS1IlSKMfSBajG3A-t876iE5R-uMFWtgZZrHMwWAypx-2e3q3H40eZNbI8MB1u5xPvEqWWQu-u-BFbVClrlzp0dUKH7TyarmIMprsDZ0ywmn8JsEjq5WjDMSel5e8Ix7JYaiL3ncD4_w> > should have produced a 2.24.x docker image at > https://docker.osgeo.org/#browse/browse:docker:v2/geoserver/tags/2.24.x > <https://fdfdfha.r.af.d.sendibt2.com/tr/cl/UO5n5ufSCbiRNO2Pi6qeenbyN-IL_BTngq7re3CL0vrl8TPJoiZu5erodrqivgJUadGo3NRiI-Bx3FMqFiK4ZPCdV-xqqq9C14dQHvIFgEJlNd8zKqgVtsfAwP-YyckLhIosvr0DcBwLf2alCI4XtJQ4Rc9-i2xky8tLsf0ufKp2Z0pE0_wbubeS-JiRtvvDe13BBt4aKNZ4m_tHhSk0vgdKzbJ5okDK2RTSnxSse_F5xh6U_G3NCm2wuPPHV8-qK51tyo43X6uSbGqC9VFUk4zyHJXV0z6QlGczGFl2o-rVDCUWMenqbyw_6fDxhaGrNif9-jT6jlJq4AiBzhLmw3oP-ouV> > that approximates these pre-flight artefacts. (Actually, I see this docker > image was produced 10 hours ago, when you built the release. Did you kick > off another job, or is that now part of the automated release process?) > > Should we add to the "artefacts available" email a link/reference to the > docker image for more developers to test against? > > Anyway, testing against this 2.24.x docker image was successful, including > JNDI and all the extensions that we make use of. LGTM. > > Peter > > On Wed, 24 Jan 2024 at 04:04, Jody Garnett wrote: > >> Artifacts are available for pre-flight testing here: >> >>- >> >> https://build.geoserver.org/view/geoserver/job/geoserver-release/lastSuccessfulBuild/artifact/distribution/2.24.2/ >> >> <https://fdfdfha.r.af.d.sendibt2.com/tr/cl/ZhTxFyeeGp5kVUWy4duvVY9WZfg8SYJN1g33K5sgjSVd4YvGezV0XbE0roEuw8OHpFVlw8wmTAtoV3T0d4vGmzyXgmZrWrBzpJxf_8yBpEkbl-o4l6xGOr2GpS8rh0qJc1cSWxh13bocmIDOX7D-4VfP6Hjiz6DTffVc73sLQLWouuRBsDvqo1pWQrfnWyPDnY-dSG-o0ky70MsRNzPldiwtUvcDirB6Tj4bxjYv0KE5dsGH3Bx48QchczFpWXIDHXhvvXToQtViTKhEtzNBcOp9BQDt3fBMJ1il4cFFW9B3qystXaJz9LmexQr4wGv_qXN7OEP1vhKBorf1SHAL3SpBpYDttP18LwlzKy94CA2uFEEqK9tmOLgIJJ_d09OhDJhTI0x7abwlr6KETrH1IAsH> >>- By the time you read this the windows installer should also be >>available for testing. >> >> >> Release notes: https://github.com/geoserver/geoserver/releases/tag/2.24.2 >> <https://fdfdfha.r.af.d.sendibt2.com/tr/cl/ZBgkuPHEABkuMp0rww9YXicz7Y7xNH4N9boCs4Yxn1M4Kx6cfvjlYFSvALI4tTAYQXJPfSPn_T5dwQyz68hxQpXoM0HvEm0xJhMLXVXeSP3055U4PiZnxeSxCxAfViHbEDjVS5FjCJ8k-ipqR_VEfNRvdA0aWXnkQ9AAvMJ3avWx2_RIy62bkL17aGs9Pkf30-qxN4QBnpu16JIogTeBBnU0Us_ChA_mcPUIDn6j9__yUaz1BINc4QzQfwXfd1z32_5S6p15vH3un1
Re: [Geoserver-devel] GeoServer PSC Meeting 2024-01-16 Notes
Great, Can you coordinate the transfer on the SAC ticket: https://trac.osgeo.org/osgeo/ticket/3104 This ticket was blocked. They offer to set it up in staging so we can evaluate. -- Jody Garnett On Wed, Jan 24, 2024 at 12:39 AM Andrea Aime < andrea.a...@geosolutionsgroup.com> wrote: > On Tue, Jan 16, 2024 at 8:26 PM Jody Garnett > wrote: > >> Probably need to make a SF ticket to request assistance. >> >> >>- >> >>action: Andrea creating a ticket >><https://sourceforge.net/p/forge/site-support/25396/> for SF mailman >>download >> >> > The mbox file is now downloadable, providing admin level credentials. I > would not do it from a browser, > it just renders directly in place, but use a command line tool instead, > for example: > > wget --user --password > https://lists.sourceforge.net/mbox/geoserver-devel > > I'm downloading a local copy just to be on the safe side, but I guess it's > best to download > directly on a server that would need it (I'd expect it to be pretty large). > > Cheers > Andrea > > == > > GeoServer Professional Services from the experts! > > Visit http://bit.ly/gs-services-us for more information. > == > > Ing. Andrea Aime > @geowolf > Technical Lead > > GeoSolutions Group > phone: +39 0584 962313 > > fax: +39 0584 1660272 > > mob: +39 339 8844549 > > https://www.geosolutionsgroup.com/ > > http://twitter.com/geosolutions_it > > --- > > Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE > 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si > precisa che ogni circostanza inerente alla presente email (il suo > contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è > riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il > messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra > operazione è illecita. Le sarei comunque grato se potesse darmene notizia. > > This email is intended only for the person or entity to which it is > addressed and may contain information that is privileged, confidential or > otherwise protected from disclosure. We remind that - as provided by > European Regulation 2016/679 “GDPR” - copying, dissemination or use of this > e-mail or the information herein by anyone other than the intended > recipient is prohibited. If you have received this email by mistake, please > notify us immediately by telephone or e-mail > ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
[Geoserver-devel] Geoserver 2.24.2 artifacts available for preflight testing
Artifacts are available for pre-flight testing here: - https://build.geoserver.org/view/geoserver/job/geoserver-release/lastSuccessfulBuild/artifact/distribution/2.24.2/ - By the time you read this the windows installer should also be available for testing. Release notes: https://github.com/geoserver/geoserver/releases/tag/2.24.2 Draft blog post is available for review: https://github.com/geoserver/geoserver.github.io/pull/180 Pending feedback I would like to release tomorrow, to avoid getting too close to the weekend. -- Jody Garnett ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
[Geoserver-devel] Recognizing Gabe for continued recurring donation to GeoServer project
I wanted to take a moment to recognize Gabe for his recurring donations to the GeoServer project, setup through GitHub osgeo sponsorship age. https://geoserver.org/sponsor/ If you like Gabe have setup a GitHub page please remember to email treasu...@osgeo.org (otherwise the GeoServer project does not directly get your donation). Thanks Gabe! -- GeoServer Project Steering Committee ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
[Geoserver-devel] New sponsor illustreets (Manuel Timita)
I wanted to thank illustreets for sponsoring GeoServer! I have updated the website, and sponsors page to thank Manuel Timita and his company illustreets for this support: https://geoserver.org/sponsor/ This financial support is recognized as an OSGeo bronze sponsorship: http://osgeo.org/sponsors/ Thanks Manuel! -- Jody Garnett ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
[Geoserver-devel] Thanks for the donation
I have updated the sponsors page to thank Marco Lucarelli for a donation to the project: - https://geoserver.org/sponsor/ Thanks Marco! -- Jody Garnett ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
[Geoserver-devel] Following up on 2024 roadmap and sponsorship stuff
Thanks to everyone who has responded with feedback, or donation, to the project: https://geoserver.org/behind%20the%20scenes/2024/01/03/roadmap.html We do indeed have a challenging year ahead. As pages are created for individual goals we will have a chance to list those offering in-kind support. I have added the sponsorship recommendations from that blog post to the wiki page on sponsorship: https://github.com/geoserver/geoserver/wiki/Sponsor Please review, and when we are comfortable with the description we can add it to the website page. The main feedback was that we should outline all of the OSGeo sponsorship levels, and be clear that sponsorship contributes towards sustainability, and is not a replacement for commercial support. -- Jody Garnett ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
[Geoserver-devel] PSC Nomination: Peter Smythe
I have been meaning to discuss this at the last several geoserver meetings - but we have had stacked agendas. I would like to nominate Peter Smythe for the GeoServer Project Steering Committee, and have checked that he is willing to be nominated (thanks Peter). My nomination is two fold: a) Peter has been a great addition to the team, and has demonstrated the community perspective expected of steering committee members: taking on maintenance / communication / community care and feeding activities. He has also done this with some joy and enthusiasm which is welcome and a good reflection on his character. b) It is good to have a balance of perspectives on the project steering committee from different organisations (something we should always try and seek out). Our procedure is here https://docs.geoserver.org/latest/en/developer/policies/psc.html#new-psc-members -- Jody Garnett ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Re: [Geoserver-devel] Using WMS Freemarker templates for GetFeature output as well?
Andrea, I think that is a good idea? Similar in use to the WMS "preview" link? I think this is "simple" enough functionality that having it is core should be fine (only take it into its own module if you wish to backport eh?). You mention the overlap with OGCAPI, but I view that document as a bit more "connected" with links to the collection page and so on. I view the free marker page as ... very simple? Would you bother with page next / prev controls or let people adjust the URL... -- Jody Garnett On Jan 11, 2024 at 10:26:57 AM, Andrea Aime < andrea.a...@geosolutionsgroup.com> wrote: > Hi all, > I'm considering extending the usage of HTML GetFeatureInfo templates for > WFS as well. > Here are some pros/cons of that approach: > > >- GetFeatureInfo is already taking N feature collections and encoding >the output towards the desired format. It's the same as what a GetFeature >does (a GetFeature can request multiple feature types, too) >- The Freemarker encoding machinery is 95% independent of WMS, there >is only one WMS setting called "GetFeatureInfo results auto-escaping". This >setting could have to be replicated for WFS as well >- There are a couple of places where adding a core HTML WFS output >format might cause friction, one is users of the XSLT extension, that could >have configured a HTML output format, and the OGC API, that has its own >native HTML output format. >- The XSLT does not seem used very much, so probably not a big deal, >while the OGC API module could recognize the WFS HTML output format and >just blacklist it from usage in OGC API Features >- As an alternative, the WFS HTML output format based on Freemarker >templates could become its own separate module, maybe a community one, >solving a couple of problems, it could depend on WMS too, releaving the >issue with the configuration, and being optional, it would not affect >existing installations. Downside, the module would be a very thin >implementation, which may make people wonder why it's even there > > Opinions? > > Cheers > Andrea > > > == > GeoServer Professional Services from the experts! > > Visit http://bit.ly/gs-services-us for more information. > == > > Ing. Andrea Aime > @geowolf > Technical Lead > > GeoSolutions Group > phone: +39 0584 962313 > > fax: +39 0584 1660272 > > mob: +39 339 8844549 > > https://www.geosolutionsgroup.com/ > > http://twitter.com/geosolutions_it > > --- > > Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE > 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si > precisa che ogni circostanza inerente alla presente email (il suo > contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è > riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il > messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra > operazione è illecita. Le sarei comunque grato se potesse darmene notizia. > > This email is intended only for the person or entity to which it is > addressed and may contain information that is privileged, confidential or > otherwise protected from disclosure. We remind that - as provided by > European Regulation 2016/679 “GDPR” - copying, dissemination or use of this > e-mail or the information herein by anyone other than the intended > recipient is prohibited. If you have received this email by mistake, please > notify us immediately by telephone or e-mail > ___ > Geoserver-devel mailing list > Geoserver-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/geoserver-devel > ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
[Geoserver-devel] GeoServer PSC Meeting 2024-01-16 Notes
GeoTools / GeoServer PMC meeting - 2024-01-16Attending - Torben Barsballe - Jody Garnett - Peter Smythe - Gabriel Roldan - Jukka Rahkonnen - Andrea Aime Actions from prior meetings: - Andrea: Look into JIRA license limit - Brad: Give the OK on the Wicket 9 Upgrade Agenda - Proposal: SQL Encoding of Vendor Provided Custom Functions - Release Planning - Roadmap coordination - Sponsorship updates - User-list / Discourse discussion - Security Vulnerabilities update/review - HTML GetFeature encoding with Freemarker templates - Jitsi Issues - geowebcache domain name was not renewed Actions - action: Reopen ContentDataStore API ticket GEOT-7509 <https://osgeo-org.atlassian.net/browse/GEOT-7509> to update affected docs - Action: Wait for Carsten to read the above SQL Function discussion, and we can discuss further in email - action: Make a https://trac.osgeo.org/ right away to ask osgeo to purchase domain name (https://trac.osgeo.org/osgeo/ticket/3121#ticket) - Action: Peter: create roadmap placeholder pages so we can list in-kind interested parties and sponsors - action: Andrea creating a ticket <https://sourceforge.net/p/forge/site-support/25396/> for SF mailman download - action: Jody to reply to email topic on getfeature freemarker encoding Proposal: SQL Encoding of Vendor Provided Custom Functions Proposal from email: https://github.com/geotools/geotools/wiki/SQL-Encoding-of-Vendor%E2%80%90Provided-Custom-Functions Q: Is this the change to the ContentDataStore canProcess(filter) kind of thing? A: No, it was only an API change to main (no need to backport) so that got merged. - Um, did this update the content datastore tutorial? Um no … - action: Reopen ContentDataStore API ticket to update affected docs please … Discussion: - Jody would like to avoid functionality that only works in PostGIS (for example?) to avoid breaking WFS. - Apparently this is already the case with some placeholder functions (KNN for example) - Why? Because then the WFS GetCapabilities advertises functionality that “does not work” (this is somewhat a limitation of the WFS standard) - Still the approach could be okay for GeoTools Java programmers, but does it really affect GeoServer? What to do? - SLD already has a mechanism for this? Providing a “fallback value” if the function is not available in that context … - We could use the marker interface to avoid listing these functions in WFS GetCapabilities Goal is to make the SQL generation / encoding extensible: - seems okay; but is “per datastore” - even that should be fine as long as their is a java fallback so it can be listed in WFS GetCapabilities - If there is no fallback java implementation? Do not list in WFS GetCapabilities, but could be used in SLD (if there is a fallback value for safety) The limitations about exact function name match? - that is not so good as different databases may have different function names, or small SQL snippets … Jody: WIth the changes above I think this could be a good addition… Action: Wait for Carsten to read the above SQL Function discussion, and we can discuss further in email Release Planning Jody volunteering to do the release this week, see https://github.com/geoserver/geoserver/wiki/Release-Schedule aside: new graphic for https://geoserver.org/roadmap/ is cute mkdocs No I do not have mkdocs ready but you can look: http://jodygarnett.github.io/geoserver/ download is a challenge: - within in a docs folder a relative link, - linking to stuff outside of docs? - We have like 400 examples of this - link to raw github on the branch or something. - Or use ant to prefetch everything into the docs folder? snippets allows an “include” folder which would be appropriate? - See https://jodygarnett.github.io/geoserver/introduction/license/ Roadmap coordination What is going on: 1. Wicket 9 upgrade if ready (2.25.x be ideal if we can coordinate it) 2. ImageN: Andrea joined email list, needs to be nominated for commit access 3. spring-framework-6: gabe started looking at it Can we coordinate with Brad to get Wicket upgrade in time for 2.25.x release cycle? - PR here: https://github.com/geoserver/geoserver/pull/7154 - Brad outlined something technical about wicket upgrade and said not to test yet? - New security feature of the browser, which disables inline styles, … - result is need to removing inline styles - What is needed: - Brad to enjoy summer vacation in Australia :) - Setup a planning document, or wiki page, to outline plan for the year - so peo
Re: [Geoserver-devel] osgeo discourse option for mailing list / forum
It maybe moot - I could not get the documented export from SF to download. Can someone else try… -- Jody Garnett On Wed, Jan 10, 2024 at 12:17 AM Andrea Aime < andrea.a...@geosolutionsgroup.com> wrote: > Open to try this out, > as others have already voiced, the user list is already getting several > unanswered posts, making it easier to post > is likely going to make that worse... unless some people that "drive by" > start answering while they browse? > My experience tells me no, I don't believe it happened with Nabble, but > who knows. > > It seems one can add some description below the title, we should place > there the usual links we have at the bottom of > mails sent to the list, along with a clear warning that the forum is > powered by volunteers and one cannot expect > to get an answer within a given deadline, or an answer at all. > > Cheers > Andrea > > > > On Mon, Jan 8, 2024 at 6:46 PM Jody Garnett > wrote: > >> I have started a ticket here https://trac.osgeo.org/osgeo/ticket/3104 to >> check if it is possible to migrate from SF mailman. >> >> The document I found here indicates some kind of export is possible >> https://sourceforge.net/p/forge/documentation/Mailing%20List%20Archives/ >> -- >> Jody Garnett >> >> >> On Jan 3, 2024 at 11:52:03 AM, Jody Garnett >> wrote: >> >>> Looks like osgeo is setting up discourse as a mailing list option when >>> migrating from mailman 2. This can take the place of nabble as a searchable >>> history (for osgeo lists), or operate as a forum - opening up for more >>> casual communication that signing to an email list. >>> >>> How do we feel about that? Do we wish to migrate from sourceforge? >>> -- >>> Jody Garnett >>> >> ___ >> Geoserver-devel mailing list >> Geoserver-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/geoserver-devel >> > > > -- > > Regards, > > Andrea Aime > > == > GeoServer Professional Services from the experts! > > Visit http://bit.ly/gs-services-us for more information. > == > > Ing. Andrea Aime > @geowolf > Technical Lead > > GeoSolutions Group > phone: +39 0584 962313 > > fax: +39 0584 1660272 > > mob: +39 339 8844549 > > https://www.geosolutionsgroup.com/ > > http://twitter.com/geosolutions_it > > --- > > Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE > 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si > precisa che ogni circostanza inerente alla presente email (il suo > contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è > riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il > messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra > operazione è illecita. Le sarei comunque grato se potesse darmene notizia. > > This email is intended only for the person or entity to which it is > addressed and may contain information that is privileged, confidential or > otherwise protected from disclosure. We remind that - as provided by > European Regulation 2016/679 “GDPR” - copying, dissemination or use of this > e-mail or the information herein by anyone other than the intended > recipient is prohibited. If you have received this email by mistake, please > notify us immediately by telephone or e-mail > ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Re: [Geoserver-devel] Missing documentation page: extension point
I may have a zip of the prior confluence wiki; but the documentation for each extension point was never clearly written. I think we learned to provide an example for people to copy (as been done for community modules). I have taken to using javadocs to communicate this Information. -- Jody Garnett On Wed, Jan 10, 2024 at 8:06 AM Peter Smythe wrote: > Hi all, especially the old-timers > > In the developer documentation > https://docs.geoserver.org/latest/en/developer/programming-guide/web-ui/overview.html > <https://fdfdfha.r.bh.d.sendibt3.com/tr/cl/d5vBd-vYw3-GsezsrRSkQmZs0EJcS2tHR_fg76DnHJDafNFc1ISnoK3rpAUIO72rBCBYmrIxhyoJFhJ2qTNybUHxPZfd0n6PHW5aZiSKHxjwBYkfWfomhiVV_fy3l9qyVH8EgzH81JHKuHBq0Vv2T5d3hZ_7RiUni41fWtDj156R4IVgOdNIiCgMZnUCbMaCrot8n9QFZ61EaPNHewSgZE1XIoAosxsBV6K9HGplxjRdDgWZjZ8gCYs29ZcXG56IbJDEJ51AzHqYEBuQLq8mS6nfRgeRvyOCZEXNTth4RaOfRPaXeXWIZYaVQyin7SBrjfRbqE95HXaZl6H5PqxGpGwHouXXtI1NYVpc50iY9sT-rz4kQC68w17QTjs19A>, > at the bottom of the page it says: > > A ComponentInfo instance contains meta information about the component >> being plugged in such as its title and description, as well as the class >> which implements the component. > > Each subclass of ComponentInfo represents a specific extension point >> <https://fdfdfha.r.bh.d.sendibt3.com/tr/cl/osqJw99fzP7KzfaAg3ld3RJNZRZp2kbzvjDLGTyCCKGFxKHDc7dF0SsWdVzu0t9aXxci5QIzBZFbLCOUI6y0KRc0KT55tbXq7BCI27xRC6ES19-Fgi_z10wqFXzHyY0qho8pyclM9M0Ii_mp29XgVC1GxqUGMDC74rUSe0Fb-ODtKMcEwtLiv_DCynR75Ih1f5_zXErA1DyHdzfU8RkI5OmyQ3oueceZB8c6mQ0-UBGiEhmGHYUg2cVGvs5xs4-JBt3zWnEPYtDl3aUjKBD1uYnMSuy-20IGYC3O2VT0guxD7FE7x0HJKnjYz8-rjcrcpLYtMJrVU5FGzAwWigsvwA-ZIxjwJSc3xYuI1Tx7OnhwlyBIJON3XCNXamdBxmzlZKPtE8B8VesN32WcAYKgjKTZQ5zjmiSc>. >> For instance the class org.geoserver.web.MenuPageInfo represents the >> extension point for “main” pages, ie pages that are linked to from the main >> menu of the application. > > > This hyperlink > https://docs.geoserver.org/latest/en/developer/programming-guide/extension-points/index.html#extension-points > <https://fdfdfha.r.bh.d.sendibt3.com/tr/cl/37Ma0S9Eeowr-IFaG8WTG8YxTnbQqw2FKKxJXdoWZWqo_U2UDGBCwaoh5VWeYYykv03Snf2dfPWBJ3-dy_sXQUpzi63XsMw1tNNYS6Mk__Ni9_qJYXZ72-pE2Tau3SGzOUTCfzcdvothHgKVRKxihDHmutIHdwjThwyPNjmKUKbaQSZnPojNpk4u-Xb68g3PtcZAiN-s50IaiTCgDK7lTmfZaUeoaE2mrlhF7i2i2gnVYI-7Y5xxzC0XuvaEhoKlQN64WuDlZOyXTv4q_z8W5xPpygvF3rNc7wJ93d7rWMeJu5cMaZqaD7e03ctAnQCJswpPd9SQLhTKPsWxaOPTvVsxMetinUqR0E5iLOAqKhG7Z5BHASnt6ahn0LaQ36bmoDqO6HGTlp9ZIttk5r8C0flN7_ZIUE5a> > is basically a blank page. > > According to > https://github.com/geoserver/geoserver/commits/main/doc/en/developer/source/programming-guide/extension-points > <https://fdfdfha.r.bh.d.sendibt3.com/tr/cl/f9lGcMUWH4Q9k5UBbrKq2oW8Dj0U9TYxGv9PLmXC6f5UEFYVjVnHZRdaNGpbv_npaYlYqGXkM7u_FRAti1H7rOHlrIpngDA4cUdiu_jYd-MgeGhC7EQ9f604l5VyvM4v1fcTu_LkSLqi7Hl0rTGf3dB6woSV3_X-CnNVQX2x7olWzOHki-6jmVmrR_n07OZel0nsq_d-HP-kt-3FSFYHCQrk_ovUm4yaZ0AJXu8D4p5eW8Wl_ymX0_B_hd-BXQWq9tkTpi5laiHmpo_dqSj8EbmLl_QTuhoCuJ6ThNdaOr4mOxGvwHRz3Wi0b0w122MOgrHydugkF06otVcuhEAGsbhE6KNh98UCkzTzACjGbiV4-fRAVu-zU_UEKei9ibDcdlJ0c5jGnQbwEm77a7qQa2REYnRfzSwMCHoM6InYEQ> > it has been like this since 2011. Is that when the code/docs were migrated > from SVN to Git? > > Did this page exist before then, does anyone have a copy of the page so > that I can import it, or can anyone provide a brief explanation of what an > extension point is? > > Thanks > > Peter > ___ > Geoserver-devel mailing list > Geoserver-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/geoserver-devel > ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
[Geoserver-devel] GeoServer 2.24.2 release volunteer
I would like to do the upcoming GeoServer 2.24.2 release scheduled for next week. If you have anything needed for the next release please speak up (ask for assistance / code reviews / encouragement) as needed! I am going to try and get mkdocs conversion done; but will not hold up the release on that account. -- Jody Garnett ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Re: [Geoserver-devel] Update to Wicket 8
Brad: I was hoping to get organized to help coordinate testing on this one Q: Is there a separate wiki page / proposal (or is it all part of the Jakarta EE planning?). Rough idea: 1. Setting up a list of components to test 2. Make a 2.25-M0 milestone release from your branch. 3. Set up a google document to coordinate feedback 4. And then make a day of it - perhaps towards the end of the month? I love the idea of getting this work in for the 2.25.x release cycle, takes the pressure off 2024 roadmap. -- Jody Garnett On Oct 5, 2023 at 3:07:55 AM, Brad Hards wrote: > As identified at > https://github.com/geoserver/geoserver/wiki/Jakarta-EE#wicket > we need to migrate to Wicket 10, ideally in small steps. > > In support of a migration from what we currently have (Wicket 7) to Wicket > 8.15.0 (or maybe later - 8.x is coming towards EOL), I have put up some > work > at https://github.com/geoserver/geoserver/pull/7154 > > I think I've done most of the boring (but easy) parts. This is enough to > get > GeoServer to the "will boot, and let you log in" stage. > > I am going to need help to fix what is left. > > In particular, I would like help to fix: > > > https://github.com/geoserver/geoserver/pull/7154/ > > files#diff-150ffebe59f506d34ef00088e4dbe5e57cb4372a806a40c249ce7f0b00c3aca1L208- > R225 > > > > https://github.com/geoserver/geoserver/pull/7154/files#diff-fe73940d7eaa413f0f13bddd992bf9d822572fee288c51c500223bd8eca01bd6R541-R630 > (which is probably the same issue affecting similar tests for > WFS,WMS,WMTS, > etc) > > > https://github.com/geoserver/geoserver/pull/7154/ > > files#diff-8ec72c8b3e191b33378849c0ac5d294c925fb2f15a0693d97c1864079599L79- > R86 > (even a hint on what the > urlFor(IFormSubmitListener.INTERFACE, new PageParameters()) > line was doing would help) > > > > and any other testing / fixes that anyone has time for. > > I'm happy for this to be on a geoserver branch if that would make it > easier. > > Any suggestions / assistance appreciated. > > Brad > > > > > ___ > Geoserver-devel mailing list > Geoserver-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/geoserver-devel > ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
[Geoserver-devel] starting mk-docs work
I will be working with this as a priority this week, ask for community review, and then cut over active branches. Torben we may need to coordinate a bit to troubleshoot publication scripts. There is a tradeoff between having a version switcher: - - https://docs.geoserver.org/user/devel - https://docs.geoserver.org/user/2.25 - https://docs.geoserver.org/user/stable - https://docs.geoserver.org/user/2.24 - https://docs.geoserver.org/user/maintain - https://docs.geoserver.org/user/2.23 - https://docs.geoserver.org/user/2.22 Or current goal of prioritizing/maintaining exiting URLs to avoid broken links: - https://docs.geoserver.org/latest/en/user/ - https://docs.geoserver.org/stable/en/user/ - https://docs.geoserver.org/maintain/en/user/ If we had access to apache redirect we could make this seamless (it is what geonetwork did). Do you know if we establish redirect rules?! -- Jody Garnett ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Re: [Geoserver-devel] GSIP-221 mkdocs proposal (closing January 3rd)
This proposal has passed with the following support: - Alessio Fabiani +1 - Andrea Aime +1 - Ian Turton +1 - Jody Garnett +1 initial motion - Jukka Rahkonen +1 - Kevin Smith - Nuno Oliveira +1 - Simone Giannecchini - Torben Barsballe +1 Community support: - Peter smythe +1 -- Jody Garnett On Dec 19, 2023 at 10:21:46 PM, Jody Garnett wrote: > I would like to make the following proposal: > > >- GSIP-222 mkdocs ><https://github.com/geoserver/geoserver/wiki/GSIP-221> > > > Thanks to Krishna Lodha (rottengrapes.tech) for woking on this proposal > with me. > > Our policy > <https://docs.geoserver.org/latest/en/developer/policies/psc.html#> is to > hold voting open for ten days (December 29 th), given that many people are > occupied with the festive season I will keep this proposal open until > January 3rd. > > >- Alessio Fabiani >- Andrea Aime >- Ian Turton >- Jody Garnett +1 initial motion >- Jukka Rahkonen >- Kevin Smith >- Nuno Oliveira >- Simone Giannecchini >- Torben Barsballe > > > Community support: > > >- Krishna Lodha > > -- > Jody Garnett > ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Re: [Geoserver-devel] osgeo discourse option for mailing list / forum
I have started a ticket here https://trac.osgeo.org/osgeo/ticket/3104 to check if it is possible to migrate from SF mailman. The document I found here indicates some kind of export is possible https://sourceforge.net/p/forge/documentation/Mailing%20List%20Archives/ -- Jody Garnett On Jan 3, 2024 at 11:52:03 AM, Jody Garnett wrote: > Looks like osgeo is setting up discourse as a mailing list option when > migrating from mailman 2. This can take the place of nabble as a searchable > history (for osgeo lists), or operate as a forum - opening up for more > casual communication that signing to an email list. > > How do we feel about that? Do we wish to migrate from sourceforge? > -- > Jody Garnett > ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Re: [Geoserver-devel] osgeo discourse option for mailing list / forum
For my own thoughts … I like the idea, and could see running it just as a discussion forum. Ideally similar stack exchange where questions can stay answered. I also like that there is a adtivepub feed for folks wishing to follow via mastodon. It will be a challenge to transfer from SF; but we can make the request to collect the mailman archive. If we cannot keep our history I am not so interested. -- Jody Garnett On Sun, Jan 7, 2024 at 3:16 PM Nuno Oliveira < nuno.olive...@geosolutionsgroup.com> wrote: > +1 > > On Sun, Jan 7, 2024 at 6:41 PM Simone Giannecchini < > simone.giannecch...@geosolutionsgroup.com> wrote: > >> +1 >> >> Regards, >> Simone Giannecchini >> == >> Online training classes for GeoNode, GeoServer and MapStore from the >> experts! >> Visit https://www.geosolutionsgroup.com/professional-training/ for more >> information. >> == >> Ing. Simone Giannecchini >> @simogeo >> Founder/Director GeoSolutions Italy >> President GeoSolutions USA >> >> phone: +39 0584 962313 >> fax: +39 0584 1660272 >> mob: +39 333 8128928 >> US: +1 (845) 547-7905 >> >> http://www.geosolutionsgroup.com >> http://twitter.com/geosolutions_it >> >> --- >> This email is intended only for the person or entity to which it is >> addressed and may contain information that is privileged, confidential or >> otherwise protected from disclosure. We remind that - as provided by >> European Regulation 2016/679 “GDPR” - copying, dissemination or use of this >> e-mail or the information herein by anyone other than the intended >> recipient is prohibited. If you have received this email by mistake, please >> notify us immediately by telephone or e-mail. >> >> >> On Wed, Jan 3, 2024 at 8:52 PM Jody Garnett >> wrote: >> >>> Looks like osgeo is setting up discourse as a mailing list option when >>> migrating from mailman 2. This can take the place of nabble as a searchable >>> history (for osgeo lists), or operate as a forum - opening up for more >>> casual communication that signing to an email list. >>> >>> How do we feel about that? Do we wish to migrate from sourceforge? >>> -- >>> Jody Garnett >>> ___ >>> Geoserver-devel mailing list >>> Geoserver-devel@lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/geoserver-devel >>> >> ___ >> Geoserver-devel mailing list >> Geoserver-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/geoserver-devel >> > > > -- > > Regards, > > Nuno Oliveira > > == > GeoServer Professional Services from the experts! > > Visit http://bit.ly/gs-services-us for more information. > == > > Nuno Miguel Carvalho Oliveira > @nmcoliveira > Technical Lead / Project Manager > > > GeoSolutions Group > phone: +39 0584 962313 > fax: +39 0584 1660272 > > https://www.geosolutionsgroup.com/ > http://twitter.com/geosolutions_it > --- > > > Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE > 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si > precisa che ogni circostanza inerente alla presente email (il suo > contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è > riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il > messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra > operazione è illecita. Le sarei comunque grato se potesse darmene notizia. > > > > This email is intended only for the person or entity to which it is > addressed and may contain information that is privileged, confidential or > otherwise protected from disclosure. We remind that - as provided by > European Regulation 2016/679 “GDPR” - copying, dissemination or use of this > e-mail or the information herein by anyone other than the intended > recipient is prohibited. If you have received this email by mistake, please > notify us immediately by telephone or e-mail. > ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Re: [Geoserver-devel] Confusion around v2.25 (due April 2024)
The change to mkdocs could be an excuse to change this from latest to main or development, and we can place a banner at the top of each page -- Jody Garnett On Fri, Jan 5, 2024 at 5:07 AM Peter Smythe wrote: > Hi all > > I am well aware that the main/development version is currently > 2.25-SNAPSHOT (for six months), but the actual release 2.25.0 is only due > in April 2024. Our latest release is currently only 2.24.1. > https://geoserver.org/roadmap/ > <https://fdfdfha.r.bh.d.sendibt3.com/tr/cl/vQvUxIRvi8q1_jKDrz2RpcyjnyaUpsEEuNxobsB_1nsxLiB56D2rEF3beI9efzAR6YOZF4O1JBWFCEYAP48qIp_4mYA5Lwl1tuLx8fmW2OVYsWwbWikwG5GtSWGVkB35KjM9QwCLx1LCTDtpv_aIE1wVmOiEslk0yc98Q_6ctwStjWqBV3BIcrbXQPMPLqe1AkXAmlQsNayosOEGNmrUfElmhDt2MMj1qapVdQH1NdYxLr3SyWEYMVAI9-ehNgPxBNiSVwUB5af4wwnazU83mljx6PEyPEV7DltoVJikmA> > > Is it not confusing to users, then, that the title of each documentation > <https://fdfdfha.r.bh.d.sendibt3.com/tr/cl/P-8YmUAK7Z83pVeXdLXH_HjxNa93wBpEmQGLV_VZV3tX6Sjt3S8uZB3IHuZJ6d6Tt3OqIrgo8EtvG-xJRudHGEDXVIIkNisrf7VDywPLdYTW5BKRcqHHHfJM8JJbsmpn7vNttBe_TX09-COZ6XntoLO5ghAYJu0QxOtzeMDGQ6beqZzeyP_MvGKIVYPz9Q_BI0ozU2NiX4WPn2w992uzPgNsOOnTs3WmD_1mI8lhxXejLZcjiiTPTFq8O_bece2s2YCxBHRcyU1Ujy1h1ZKb95LdR9j5W_3ITn3ywjtgRO-3IqJ59bQ5GpXtT9iCtU0> > page already refers to GeoServer 2.25.x User Manual, as does the > heading/breadcrumb: > > [image: image.png] > > Yes, the document changes are committed to main and immediately published > to https://docs.geoserver.org/ > <https://fdfdfha.r.bh.d.sendibt3.com/tr/cl/ciszKm4EW4s7QpMEpO2MB_hYQetjaWQdasIlEQU6w4_XGbyNjZlaw7qtJYyO9XsX4gs1tBnuh76wZef5BhnJLxm-kJtW3gp3pY-FqRT88lDlmt3c9R_F2vO89e2pD9nrs42oYLcIwZJlEL6u-NMJyBE110RGDiSWgsP2LnXoVWJUC9TSmAwTm1T1IQAU4D2M2OxoZ-trFXqFUGToi5ksv76FazyebXe50_MSjmD0Pr5bYyMWRWNI7g2T4FoTUMVnybS1-1gEBGtDRxjj6JUrmY_l8b-6atOOmfk> > *latest*/en/user/ so technically it is correct. > > I also note that while https://docs.geoserver.org/ > <https://fdfdfha.r.bh.d.sendibt3.com/tr/cl/LCflsyRjk3pF5RBnc5BgtprUV3xEiXoVD1E6BDCuDRcrvP06h9Ok6v5hmepf-DYTfBUDxlFQydARb68kvu1RJe5lKsUC1UTJSphejQ6_og3QceE-Y2lLbfebvLST9qfoJtABjs4b4DpyGvqWkx6raWUoqVOtTCyiVVpwK441VvDEv4aXsRwDkmjA_6BqCgDWQTzKKsMWyWnKNcd0soUyVOgXB0nKiVgUZEU_j4wEs73auS6pPWz1EFeMtrsOW8-nMkhXhSiS3OmtYpAUfT_rnErPe32EFoDJMHU> > *stable*/en/user/ is correctly titled 2.24.x, https://docs.geoserver.org/ > <https://fdfdfha.r.bh.d.sendibt3.com/tr/cl/w_Re8pRuIboO7CrRjZRQWv9YB7C3_79FRApkEeCCC4nMon7gzstPKc61M7QCeGCJHW5qgXpJz53CuAbSUEV0WLZ5IdztjwG1GAdeMYoUIdBBeT0_icY0q00KqIWhKPfWoj3MeawnfyGTRQ16fK2z_Bps8SXkD6IwrvZ_FOCFq-KRYadDcxjgg2K1ZBJ_yG2eLXi2Wf1-2DOnUSr4d5_3GVxEzE-3l9v7XUY1qrPgKnpaXhhzmvEFlYk-iic9p7e4v1B9qrekgaUMoabozc7DUdkljL0WrZdelHg> > *maintenance*/en/user/ is incorrectly titled 2.22-SNAPSHOT instead of > 2.23.x > > Peter > ___ > Geoserver-devel mailing list > Geoserver-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/geoserver-devel > ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
[Geoserver-devel] Thanks for donation
I have updated the sponsor page to thank Peter Rushforth for donation to the project: - https://geoserver.org/sponsor/ I confirmed that Peter is correctly listed here as supporting osgeo: - https://github.com/sponsors/OSGeo#sponsors - https://github.com/prushforth Thanks Peter :) -- Jody Garnett ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Re: [Geoserver-devel] GeoServer sponsorship
Q: When adding you to the geoserver sponsors as an individual I will just use your name; should I link to your GitHub repository or something else? -- Jody Garnett On Jan 4, 2024 at 2:31:39 PM, Peter Rushforth wrote: > Hi Jody, > > Thanks! The point of this email isn't so much to ask for a logo as to > ensure that the contribution is directed to the GeoServer project. The > process of contributing didn't make that clear to me. > > Cheers, > Peter > > On Thu, Jan 4, 2024 at 10:19 AM Jody Garnett > wrote: > >> Thanks Peter, >> >> An OSGeo logo should show up on your GitHub repo. >> I will add to the geoserver sponsor page. >> >> The OSGeo website has a Bronze level at 500 a year for organizations. >> -- >> Jody Garnett >> >> >> On Thu, Jan 4, 2024 at 6:46 AM Peter Rushforth >> wrote: >> >>> Hi, and apologies for cross-posting: >>> >>> I have used GitHub Sponsors page to setup a monthly donation of $5 to >>> the GeoServer project. >>> >>> I was intending to sponsor GeoServer project monthly. I didn't see a >>> way to actually select a project to sponsor, but I went ahead with it >>> anyway. Hopefully it gets to the right place. >>> >>> Thanks >>> Peter >>> ___ >>> Geoserver-devel mailing list >>> Geoserver-devel@lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/geoserver-devel >>> >> ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Re: [Geoserver-devel] GeoServer sponsorship
Thanks Peter, An OSGeo logo should show up on your GitHub repo. I will add to the geoserver sponsor page. The OSGeo website has a Bronze level at 500 a year for organizations. -- Jody Garnett On Thu, Jan 4, 2024 at 6:46 AM Peter Rushforth wrote: > Hi, and apologies for cross-posting: > > I have used GitHub Sponsors page to setup a monthly donation of $5 to the > GeoServer project. > > I was intending to sponsor GeoServer project monthly. I didn't see a way > to actually select a project to sponsor, but I went ahead with it anyway. > Hopefully it gets to the right place. > > Thanks > Peter > ___ > Geoserver-devel mailing list > Geoserver-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/geoserver-devel > ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Re: [Geoserver-devel] [Geotools-devel] GeoTools / GeoServer PMC meeting - 2024-01-02
Perhaps Michel who did the initial cleanup of inline styles can offer perspective? -- Jody Garnett On Wed, Jan 3, 2024 at 3:04 PM Brad Hards wrote: > On Wednesday, 3 January 2024 7:21:43 PM AEDT Andrea Aime wrote: > > If so, it's big (the style part at > > least) but not massive. Looks like a lot of small changes, which would > > fit nicely in my "around one hour a week" typical availability. > > I don't have a good feel for how complete the list is, but at least > the style fixes probably a good estimate. > > I plan to do the style fixes first, then look at inline scripts. > > I can do most of them, but would like help with the "display: none" part, > especially in the base page where there is a comment about using the > feedback > spinner as a veil (proxy?) for AJAX interactions. I have no idea how that > works, and its causing noise on every page that derives from it. > > Have dropped a comment in the PR to show the unsafe-inline setting. > > Brad > > > > > ___ > Geoserver-devel mailing list > Geoserver-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/geoserver-devel > ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
[Geoserver-devel] osgeo discourse option for mailing list / forum
Looks like osgeo is setting up discourse as a mailing list option when migrating from mailman 2. This can take the place of nabble as a searchable history (for osgeo lists), or operate as a forum - opening up for more casual communication that signing to an email list. How do we feel about that? Do we wish to migrate from sourceforge? -- Jody Garnett ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Re: [Geoserver-devel] [Geotools-devel] Time to upgrade Spotless... and maybe take advantage of the break?
I really like the more terse alternative and longer line width. Since I like two things +2 :) -- Jody Garnett On Tue, Jan 2, 2024 at 9:06 AM Andrea Aime < andrea.a...@geosolutionsgroup.com> wrote: > Hi all, > you probably know that we are formatting the source code with the Spotless > Maven plugin, > in combination with the Google Java Format library. > > Currently, we are using an older version of both, because they upgraded > time ago to require Java 11 as the minimum version, and we were still using > Java 8. But we have been on Java 11 for a while now, and we can update up > the dependencies. > > I've prepared a pure upgrade of GeoTools, as an example, here: > https://github.com/aaime/geotools/tree/spotless_upgrade > > The update touches 2k files, mostly changing the javadoc style for single > line javadocs, to use three lines instead. Lots of noise, no significant > gain in my opinion. > > One formatting library that I've been keeping an eye on for a while is > Palantir's fork of Google Java format. They made some significant changes: > >- 4 spaces indent by default (we get this by adopting the AOSP style >of Google's one) >- 120 columns rather than 100 >- Formatter optimized for streams and functional style to use less >space. > > They have some significant examples in their landing page > <https://github.com/palantir/palantir-java-format?tab=readme-ov-file#motivation--examples>. > I've tried this out with GeoTools, and linking what I've found, also with > GeoServer (both are best viewed offline, in a checkout): > >- https://github.com/aaime/geotools/tree/spotless_palantir >- https://github.com/aaime/geoserver/tree/spotless_palantir > > In this case, the GeoTools diff is significantly bigger than the pure > Spotless upgrade, touches 2k files, but in the end, manages to cut down 60k > lines of code. > > What is your opinion? Would you like to go with Palantir? > > If we went down that road, I'd recommend to: > >- Wait until the Wicket 9 upgrade is done >- Wholesale reformat all three projects (GeoTools, GeoWebCache, >GeoServer) >- Reformat all active branches for ease of backport (if this ends up >landing after the 2.25.x release, maybe also reformat the 2.23.x series as >it will likely get some extra fixes in the next few months). > > Cheers > Andrea > > == > > GeoServer Professional Services from the experts! > > Visit http://bit.ly/gs-services-us for more information. > == > > Ing. Andrea Aime > @geowolf > Technical Lead > > GeoSolutions Group > phone: +39 0584 962313 > > fax: +39 0584 1660272 > > mob: +39 339 8844549 > > https://www.geosolutionsgroup.com/ > > http://twitter.com/geosolutions_it > > --- > > Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE > 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si > precisa che ogni circostanza inerente alla presente email (il suo > contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è > riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il > messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra > operazione è illecita. Le sarei comunque grato se potesse darmene notizia. > > This email is intended only for the person or entity to which it is > addressed and may contain information that is privileged, confidential or > otherwise protected from disclosure. We remind that - as provided by > European Regulation 2016/679 “GDPR” - copying, dissemination or use of this > e-mail or the information herein by anyone other than the intended > recipient is prohibited. If you have received this email by mistake, please > notify us immediately by telephone or e-mail > ___ > GeoTools-Devel mailing list > geotools-de...@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/geotools-devel > ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Re: [Geoserver-devel] [Geotools-devel] GeoServer/GeoTools PMC Meeting at 18:30 CET / 9:30 PST tomorrow
I may be in transit and unavailable for tomorrow's meeting. Topics: - blog post is ready: https://github.com/geoserver/geoserver.github.io/pull/175 describing 2024 roadmap - GSIP is ready: https://github.com/geoserver/geoserver/wiki/GSIP-221 Community stuffs: - New osgeo board is being assembled, voting starts this week - The existing board is assembling the budget from everything provided thus far - The text of the european Cyber Resilience Act is out; and has a lot of language softening open-source exposure. There will still be work to do to support our core contributors but that is fine. -- Jody Garnett On Mon, Jan 1, 2024 at 6:32 PM Torben Barsballe wrote: > Reminder that the next PMC meeting is scheduled for tomorrow, January 2, > at 18:30 > <https://www.timeanddate.com/worldclock/fixedtime.html?year=2024=1=2=18=30=0=GeoTools%20/%20GeoServer%20Meeting=1=1=215> > CET. > > You can join the meeting by following this link: > https://meet.osgeo.org/GeoServerMeeting > > Cheers, > Torben > > ___ > GeoTools-Devel mailing list > geotools-de...@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/geotools-devel > ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Re: [Geoserver-devel] GSIP-221 mkdocs proposal (closing January 3rd)
A reminder that this is held open until next week :) Given how quiet it is we may need to hold it open until Jan 5th. If you have not done looked at the proposal recently I now have 95% of content converting okay, even the tricky ones like literalinclude and include etc... I also got some "geoserver theme" aspects to work with both light and dark mode. Some work remains, some trouble with nested directives, specifically block directives in block directives as seen here: https://jodygarnett.github.io/geoserver/installation/docker/#adding-geoserver-extensions All the best in the new year. -- Jody Garnett On Tue, Dec 19, 2023 at 10:21 PM Jody Garnett wrote: > I would like to make the following proposal: > > >- GSIP-222 mkdocs ><https://github.com/geoserver/geoserver/wiki/GSIP-221> > > > Thanks to Krishna Lodha (rottengrapes.tech) for woking on this proposal > with me. > > Our policy > <https://docs.geoserver.org/latest/en/developer/policies/psc.html#> is to > hold voting open for ten days (December 29 th), given that many people are > occupied with the festive season I will keep this proposal open until > January 3rd. > > > - Alessio Fabiani >- Andrea Aime >- Ian Turton >- Jody Garnett +1 initial motion >- Jukka Rahkonen >- Kevin Smith >- Nuno Oliveira >- Simone Giannecchini >- Torben Barsballe > > > Community support: > > >- Krishna Lodha > > -- > Jody Garnett > ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Re: [Geoserver-devel] windows build server
My employer GeoCat is hosing some azure build services (which is how we have windows build downloads presently). Can azure supplier a macOS build environment? -- Jody Garnett On Tue, Dec 26, 2023 at 1:18 PM sechelé delaruse wrote: > howdy > < (We do still lack a macOS build server.) > > i skimmed the docs but the only real mention of macos was here > https://github.com/geoserver/geoserver/blob/main/build/mac_installer.sh > > the product of mac_installer.sh is a .dmg as per > # upload dmg to final location > upload_installer $tag geoserver-$tag.dmg > > assuming > >- no signing of the distribution with an apple developer certificate >-> if signing required details are required on how this is currently >accomplished >- mac_installer.sh is the workflow entrypoint for building a macos >distribution >- no macos build server required > > > if the above assumptions are true builds can be accomplished at will in > azure devops as follows > >- ensure an organization in azure devops >- ensure a public project to host the build, ensuring open source sla >which is unlimited builds >- create a pipeline that can clone the required assets from github >- ensure a linux build agent >- add a script task to the pipeline initialized to the location >required by mac_installer.sh >- ensure pipeline auth to the upload location >- ensure pipeline artifact versioning >- ensure permissions and pipeline triggers > > > if no personpower is available to accomplish these tasks certainly i can > make those things happen > > these are some pipelines i currently operate in azure devops - the target > environment is kubernetes, the artifacts are npm and nuget packages and > python whatevers and docker images, with an expectation that the customer > may want to operate a geoserver instance in the cluster, hence my interest > >- >https://dev.azure.com/electricrucible/the%20horseless%20newspaper/_build > >- https://dev.azure.com/electricrucible/metoffice/_build > > > on the matter of task 'ownership' i would suggest that if there is a > corporate entity associated with producing geoserver builds, that entity > should own the azure devops organization to accrue the benefits of the open > source azure devops sla, and delegate permissions to whoever is going to > accomplish the above tasks > > regards > > -- > *From:* Jody Garnett > *Sent:* Sunday, December 24, 2023 2:26 AM > *To:* sechelé delaruse > *Cc:* geoserver-devel@lists.sourceforge.net < > geoserver-devel@lists.sourceforge.net> > *Subject:* Re: [Geoserver-devel] windows build server > > That is interesting; my employer GeoCat has setup Jenkins on an azure > build server. So we should update that page. > > (We do still lack a macOS build server.) > -- > Jody Garnett > > > On Dec 23, 2023 at 7:46:34 PM, sechelé delaruse > wrote: > > on the first day of christmas i noticed that this url > https://docs.geoserver.org/stable/en/developer/installer/index.html > contains the following content > > > At the time the GeoServer project does not have financial resources and > man power to stand up a Windows build server (if you can help with this, > please contact the developer list) > > > if this is no longer true please disregard > > if build server still required > >- i happen to know that as an open source project the geoserver >project can run unlimited builds in azure devops. so can anyone else who >clones the repo in a public azure devops project >- after investigating the geoserver github actions i saw nothing >incompatible with triggering builds in azure devops in collaboration with >specific github actions >- the primary showstopper risk seems to revolve around headless >installation of nsis itself and its dependencies on azure build servers as >per > - extract the .DLL files (AccessControl.dll) and copy it to the > NSIS plugins directory usually > C:\Program Files\NSIS\Plugins\x86-ansi > > > if build server still required and mitigations exist for installing nsis > and dependencies on cloud build agents, i offer to > >- evaluate the full build process for the windows geoserver >- deliver a proof of concept of a suitable pipeline that runs in azure >devops > > > please advice > ___ > Geoserver-devel mailing list > Geoserver-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/geoserver-devel > > ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Re: [Geoserver-devel] Cannot create issue
Dear Vicky, Yeah GeoServer team has some kind of access for free projects; but it has a limit for the number of users. We need to go through and clear unused accounts. I am forwarding to geoserver-devel for action. -- Jody Garnett On Tue, Dec 26, 2023 at 1:35 PM Vicky Vergara wrote: > Hi all > Got this message on info > Regards > > On Tue, Dec 26, 2023 at 4:12 AM Iñigo Alcalde > wrote: > >> Hello >> I want to create an issue in Jira so I can link it from GitHub and >> contribute with a bugfix. >> I registered with my google account but sadly, when I try to login, I get >> this message: >> >> *You don't have access to osgeo-org.atlassian.net >> <http://osgeo-org.atlassian.net>* >> >> The message continues and says that my email account *does not have >> access because osgeo-org.atlassian.net <http://osgeo-org.atlassian.net> has >> reached the license limit*. >> >> ¿Can you help me? >> > ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
