GeoTools / GeoServer PMC meeting - 2021-02-16Attending

*Kevin SmithTorben BarsballeJody GarnettAndrea AImeGabriel RoldanJukka
Rahkonnen*Actions from last meeting:


* - [DONE] Gabe/Jody to have a relaxed release of 2.17.5 (over the
weekend?)- [DONE] Kevin: Review GWC Gridset x2 pull request
<https://github.com/GeoWebCache/geowebcache/pull/924/files>- [In Progress]
Jody/Gabriel: Write up GSIP for GeoServer-Cloud project- [In Progress]
Torben: Try zhCN translation to see if it is published*Agenda


* 1. Release updates2. Windows installer update3. Cloud Native GeoServer
project donation4. Pom file formatting and xml file formatting5.
Documentation Translation6. More QA rules incoming*Actions



* - *Release updates









*JTS upgrade made it in (thanks James)Release is underway: - Done: Disabled
jobs - Done: GeoTools- “Done”: GeoWebCache, sent issue to developer list-
osgeo ldap went down making this step delayed- GeoServer is next- Start
setting up the jobs againHelp needed / interesting activities: - Blog post
has a lot to write up!  Andrea to help on blog post ← that will be great! -
A new template will be needed due to all the new modules graduating-
Action: start a branch / pr to work on thisRename master to main? - This is
only proposed for GeoServer, and approved a while back?- This is probably a
good idea for GeoTools, GeoWebCache - Send email to GeoTools and
GeoWebCache about this...- GitHub re-targets existing open PRs to “main”
automatically*Windows installer update




* - Waiting on above release - Sander will need access to Jenkins, will
email PSC for this.- Goal is to have this for 2.19.0 (if we can)*Cloud
Native GeoServer project donation







*See https://github.com/geoserver/geoserver/wiki/GSIP-201
<https://github.com/geoserver/geoserver/wiki/GSIP-201>  - Any quick
feedback?Q: In camptocamp already has a CLA, do they need to fill in this
form again?A: Yes, please fill in section B listing “cloud native
geoserver” as a donated thingQ: what is next?A: Email geoserver-devel with
GSIP-201 for votes, there is a ten day window for feedbackQ: Github
documentation site?There is one already on
https://camptocamp.github.io/geoserver-cloud/
<https://camptocamp.github.io/geoserver-cloud/> does this get moved to
https://geoserver.github.io/geoserver-cloud/
<https://geoserver.github.io/geoserver-cloud/> (yes because it is a a docs
folder on the master branch).Discussion: - master → main branch - Name:
“Cloud Native GeoServer” vs “GeoServer MicroServices”?- Discussion of
“production” instance cited in PR, emphasis on high-availabilityFuture
plans and experiments: - Trying out shared data directory, not the
“stateless” goal but may be fun- Can consider a redis approach similar to
stratus. Has a Redis Catalog Facade, with some deep performance
enhancements to prefetch and cut down number of queries (per request
caching facade)- Experimenting with moving event handling to the catalog,
to make catalog more self contained and cut down on cross catalog
concerns.- Also trying out catalog/config modifications based on “patches”
rather than whole-object modifications*Pom file formatting and xml file
formatting





*Attempts: - https://github.com/geoserver/geoserver/pull/4663
<https://github.com/geoserver/geoserver/pull/4663> (Acegi formatter)- This
removed all our logical blocks and comments-
https://github.com/geoserver/geoserver/pull/4800
<https://github.com/geoserver/geoserver/pull/4800> (Eclipse formatter)-
Good for application-context files- Messes up the pom.xml files- Issue:
https://github.com/revelc/formatter-maven-plugin/issues/433
<https://github.com/revelc/formatter-maven-plugin/issues/433> - Next:
https://github.com/Ekryd/sortpom <https://github.com/Ekryd/sortpom> - Only
one way to produce valid pom.xml, very specific order, etc…- Q: Does it
preserve comments? Yes- A bit annoying to have three formatters (google
java, eclipse xml, sort pom)...- The last version that supports Java 8 has
a fix we are interested in- Longer term this will be Java 11 only
(sad)Discussion: - JG: Was sad this did not make it in before RC.- AA:
never mind, there is always a next release :-DQ: This should be applied
across branches right?A: Yes this is the way*Documentation Translation





*Torben: - Looking at chinese translation that was merged- Some build
changes (pom.xml and build deploy) need to be added- PR coming soon
(maybe)- Build server will also need updating to trigger the new
buildsJody: - Sphinx translation of docs are thing, and would let docs be
translated from transifex- Would take 1/2 day to set this up, if there is
anyone interested in doing
translationhttps://www.transifex.com/GeoServer/geoserver/dashboard/
<https://www.transifex.com/GeoServer/geoserver/dashboard/> *More QA rules
incoming

   -

   PrintStackTrace (finally!)
   -

   Constant array creation
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Reply via email to