[Geoserver-devel] GeoTools / GeoServer PMC meeting - 2018-11-13

GeoServer GeoServer Developer
, ,
1

Attending

Torben Barsballe

Jody Garnett

Jukka Rahkonen

Kevin Smith

Agenda- Do we want to change the time of the 19:30 UTC meeting now that Ben has stepped down?

  • OSGeo unspent budget

  • QGIS Export of raster symbolizer

  • JDK 11 Sprint follow-up

  • JDK 11 Blog post

  • 2.14.1 release scheduled for this week - call for volunteers

  • GeoServer + GeoWebCache Doc migration

Actions from Last meeting- Discuss topics on email

Actions- Jody: Take meeting time proposal to mailing list [DONE]

  • Jody: Update QGIS raster export proposal - +$1.5k to budget and call for vote [DONE]

  • All: Vote on QGIS raster export proposal

  • All: Anyone have time to fix the outstanding JDK 11 issues?

  • Jody: send “release train” email for friday (since this falls on the weekend) [DONE]

Meeting time- Change to earlier time-slot for this meeting?

  • consider dropping down to half an hour

  • Motion: Change to 16:00 UTC for half an hour on jitsi

  • action: Jody taking proposal to email list.

OSGeo Unspent Budget

2018 Budget review:

  • GeoTools: $1.5k - attend bonn code sprint to support JAI replacement, attend AGM

  • 1.5k added by OSGeo:UK for QGIS / GeoTools interoperability

  • GeoServer: $1k - general project expenses

  • GeoWebCache: via incubation committee

Ideas for remained of 2018:

  • “code-sprint” t-shirts

  • Kevin: Maybe logos of participating projects on jigsaw puzzle pieces?

  • “project specific shirts” to send out to contributors

  • single color shirt two-color logo

  • “I am a GeoServer Contributor” on the front

  • OSGeo Project log on the back (very small)

  • Jody proposes picking up $1k and taking to marketing committee for the above

  • contribute to the QGIS raster symbolizer export

  • “add a tutorial to the geoserver manual” ← adds value to above

  • “add mapping between QGIS functions and GeoTools functions”? ← probably too much work

  • proposal: Add $1500 from geoserver budget to this proposal with an additional deliverable of a tutorial for the GeoServer manual.

  • action: take to existing email discussion for vote.

Start thinking about 2019 budget, need to make the request in December :slight_smile:

  • JAI if it happens in 2019 it will be a large activity

  • java roadmap will be an ongoing cost

  • Do we want to focus on the LTS? probably

  • Running on last LTS and current “master” would be least risk

  • Send officers to AGM?

  • OSGeo code sprint participation?

QGIS Export of raster symbolizer

See budget discussion above, and update to proposal on Mailing list.

JDK 11 Sprint Follow-up- Jody provided an update to the board with respect to sponsorship, budget and osgeo hosting the event and what it means to the projects.

  • Aside: reporting back positive feedback from customers (impressed this was done at all, and that it was “done” so quickly)

  • Finish up sprint split-package goal and unfreezing master [DONE]

  • https://github.com/geotools/geotools/pull/2154, https://github.com/geoserver/geoserver/pull/3217

  • What else is left - see https://docs.google.com/spreadsheets/d/1oE6mU4jp-ZL5PebgXf-fuhtf7MY5dzSwPqpMtrzdZ94/edit#gid=2055024842&range=A513

  • App-schema split packages

  • ArcSDE internal split package

  • sqlite/spatialite split package

  • JAIExt scale split package

  • anything else

  • jody has a split of gt-metadata into gt-metadata and gt-util

  • Running up t-shirts for sprint participants

  • jody has taken an action to ask marketing committee for design and quote

  • Documentation

  • We need migration instructions for GeoTools

  • Turn the spreadsheet into sed script?

  • For GeoServer we to update the Production Considerations section for Java 11

  • https://docs.geoserver.org/latest/en/user/production/java.html

  • Blog post:

  • Publish once upgrade and production consideration docs are ready to link to

  • We have a responsibility to thank sponsors in the blog post, and release announcements.

  • Schedule a milestone “release” based on our results for sometime in November?

  • We probably want to be able to release a jar bundle compiled on Java 11 (for both GeoTools, GeoWebCache, and GeoServer) alongside the regular release.

  • alternative: consider releasing early? RC end of december, release in January?

  • This is subject to the split-package work being completed

  • Writing migration documentation, and blog posts

  • See “actions” below, will propose if successful by the 30th

Actions:

  • Anyone have time?
    (May need to address via Nov 30th bug stomp - sigh)

2.14.1 GeoServer Release - Call for volunteers- Jody has volunteered

  • Torben as backup / GWC

Action:

  • sent “release train” email for friday (since this falls on the weekend)

GeoServer / GeoWebCache doc migration

Doc migration started during code sprint.

GS Doc builds fixed last week.

Swagger docs are currently broken. Planning on investigating if the swagger docs can be hosted statically.

For GeoWebCache - geowebcache.org/docs doesn’t work, www.geowebcache.org/docs/current/index.html does (you need the index.html as part of the URL).

2

Ideas for remained of 2018:

  • “code-sprint” t-shirts

  • Kevin: Maybe logos of participating projects on jigsaw puzzle pieces?

  • “project specific shirts” to send out to contributors

  • single color shirt two-color logo

  • “I am a GeoServer Contributor” on the front

  • OSGeo Project log on the back (very small)

  • Jody proposes picking up $1k and taking to marketing committee for the above

The idea seems cool, but at the same time, I’m wondering if we should be investing the money in the project instead, there
are a variety of things that could be done, e.g. start pushing more aggressively towards code quality (PMD, findbugs and the like in the builds),
refreshing CITE tests, or even getting more people to help on the user list somehow.
I get t-shirts help morale and pride, but will this turn into more participation? Cause that’s what we actually need :slight_smile:

Start thinking about 2019 budget, need to make the request in December :slight_smile:

  • JAI if it happens in 2019 it will be a large activity

  • java roadmap will be an ongoing cost

  • Do we want to focus on the LTS? probably

Check out the AWS OpenJDK long term support move… it’s on Java 8:
https://aws.amazon.com/it/corretto/

So be mindful of that, Java on AWS seems like it will mean Java 8 for quite some time.
(at least, they are not mentioning a java 11 version of it)

  • Running on last LTS and current “master” would be least risk

  • Send officers to AGM?

  • OSGeo code sprint participation?

This would work, if we can find a topic that drives people there (something actionable with immediate benefit)

JDK 11 Sprint Follow-up- Jody provided an update to the board with respect to sponsorship, budget and osgeo hosting the event and what it means to the projects.

Can you ping me before publishing it, I’d like to help, there is a lot of work that did not make into twitter and mails,
mostly because the european team passed the current status in an oral way as opposed to mails.

2.14.1 GeoServer Release - Call for volunteers- Jody has volunteered

  • Torben as backup / GWC

Thank you!

Action:

  • sent “release train” email for friday (since this falls on the weekend)

GeoServer / GeoWebCache doc migration

Doc migration started during code sprint.

GS Doc builds fixed last week.

Swagger docs are currently broken. Planning on investigating if the swagger docs can be hosted statically.

I keep on not understanding this “statically” bit. The swagger UI javascript/html combo just needs a URL to the YAML that
defines the API and does everything else on its own, the current issue afaik is just that the link it’s getting is the wrong one

Cheers
Andrea

···

GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. == Ing. Andrea Aime @geowolf Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa (LU) phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 339 8844549 http://www.geo-solutions.it 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.

3

On Wed, Nov 14, 2018 at 10:19 AM Andrea Aime <andrea.aime@anonymised.com> wrote:

On Tue, Nov 13, 2018 at 9:52 PM Torben Barsballe <tbarsballe@anonymised.com> wrote:

GeoServer / GeoWebCache doc migration

Doc migration started during code sprint.

GS Doc builds fixed last week.

Swagger docs are currently broken. Planning on investigating if the swagger docs can be hosted statically.

I keep on not understanding this “statically” bit. The swagger UI javascript/html combo just needs a URL to the YAML that
defines the API and does everything else on its own, the current issue afaik is just that the link it’s getting is the wrong one

I think there might be a little more JS magic in there somewhere, given the swagger path uses # - I have not had a chance to look into the exact issue yet.
But yes, it is something that should work fine statically (i.e. from the filesystem or from the current S3 doc hosting solution); the issue is it doesn’t right now. It’s entirely possible it is as simple as an incorrect path.

Cheers,

Torben