[Geoserver-devel] GeoServer PSC meeting, Nov 14th 2017

GeoServer GeoServer Developer
,
1

GeoTools / GeoWebcache / GeoServer Meeting 2017-11-14

Attending

Jody Garnett

Andrea Aime

Jukka Rahkonen

Ian Turton

Torben Barsballe
Actions from Last Meeting

   -

   Jody/Torben: (done) Schedule CITE debugging session
   -

   Jody: (done) Remind GeoTools PMC to vote on Java 9 Proposal
   -

   Jody: (missed) Forward OSGeo CITE Application email and determine how
   much time is left for this renewal application. Probably not much because
   automatic mail from OGC says “are due to be renewed by *October 31st, 2017*.
   -

   Jody: Need a spreadsheet comparing sprint location costs to justify
   budget request (short list from email discussion, compare flights and
   accommodation for January/February?)
   -

      No spreadsheet yet
      -

      James Hughes expressed interest in CCRi hosting/attending
      -

   Kevin: (done) Bounce GWC planning of gwc email list for discussion review
   -

   Jody: Revise http://osgeo.getinteractive.nl/projects/geotools/ with
   features list from OSGeo-Live

Agenda

   -

   Isolated workspace mail by Nuno
   -

   Java 9 compatibility follow up (sprint)
   -

   Budget (GeoServer and GeoTools) and CITE tests
   -

   Shutting down Ares
   -

   Chit/Chat

Isolated workspace mail by Nuno

Multitenancy for complex features, see “Isolated Workspaces” mail.

“The main (root) use case for this is to allow the publishing of the same
complex feature type in GeoServer multiple times in different workspaces”

   -

   Proposal or bug? Both…
   -

   Workspaces that are not listed globally
   -

   How does this differ from turning off global?
   -

      Should understand why turning off global does not meeting Nuno’s
      requirements? Appears to be due to them having common namespace
      (application schema requirement - example INSPIRE).

This is a request to read email and follow up with discussion.

Q: Should we remove JDBCConfig? (nobody answering mails or reviewing pull
requests regarding it)

   -

   Ask Boundless for next meeting

Or ask the interested party if they want to upgrade from making pull
request to becoming maintainers.
Java 9 compatibility follow up (and sprint?)

PR was merged, with a bit trouble, and master now has a distinct
FactoryRegistry separate from imageio.

Making a list of tasks here:

   -

   https://github.com/geotools/geotools/wiki/Java-9-Compatibility
   -

   Idea is to test and set up jobs with Java 9 for current release cycle

Java 8 EOL Oct 2018, so we have a bit of time left for GeoServer crowd
(conservative server side deployments). GeoTools does have early adopters.

Ideally test early and then plan, would like to avoid having a emergency
sprint in January close to release.

Q: Can we build with Java 9 on Travis?

Q: Is it worth making a milestone release?

   -

   It would answer “does it build” question
   -

   Would need some buy-in from user list to justify effort

Budget (GeoServer and GeoTools)

GeoTools Budget:
https://github.com/geotools/geotools/wiki/GeoTools-Budget-Request-2018

   -

   Budget request is for $5500 in total (the code sprint thing is a
   separate request)
   -

      4000 sprint request; this is pending us doing fund raising
      -

      1500 travel assistance
      -

   Topics considered for sprint:
   -

      Java 9 compatibility if needed
      -

      Java 8 Stream update for DataStore (see discussion in 2016)
      -

      Kick off Raster Process Engine project at OSGeo code sprint in Bonn
      -

         Design sprint, w/ architecture spike (geotools wrapper approach)?
         -

         Would need to confirm resourcing for this to work
         -

      Kick out EMF/XSD
      -

         Ian/Andrea have some frustrations .. how about ideas?
         -

         Upgraded for WMTS work, or replace with JAXB?
         -

         It is horribly opaque, can docs help? Not really it is complex.
         -

            Different modules been generated with different versions, have
            to grab that copy of eclipse that would work for each module
            -

         Massive overhead anytime we need a change
         -

         Action: Ian take discussion/research to email list

GeoServer:

   -

   Similar budget request from last year; around $3000 for sprint
   -

   Q: depending on topic we may get more people/interest? A: Then we would
   ask for more money, this is only a budget
   -

   Topics considered
   -

      GWC improvements: Kevin has been organized pushing this
      -

         If this is confirmed we can make OSGeo budget request and start
         setting up sprint planning
         -

         check with kevin if this is already in progress
         -

      REST bindings for WFS 3.0
      <https://github.com/opengeospatial/WFS_FES/blob/master/core/standard/clause_7_core.adoc&gt;?
      Swagger definition being done by OGC
      -

         Would this finish in 2018, and thus be good for a sprint?
         -

      CITE
      -

         Implement plan discussed previously, doing as a background
         activity has not been successful yet.

Action:

   -

   Jody: coordinate with GeoServer / GeoTools lists, concern about being
   able to take so much time for this activity, expect we will need to choose
   one

Shutting down Ares

CITE tests work on Build besides WFS 1.1, hangs indefinitely.

WFS 1.1 test has a problem, reported to CITE team:

   -

   https://github.com/opengeospatial/ets-wfs11/issues/77
   -

   Note we are reporting against an old release so expect no fix
   -

   https://github.com/geoserver/teamengine/tree/e4dda71c90ba601d39847d19969b4d617f90bb70
   -

   On ares this jobs also hangs, but is killed. We could reproduce this on
   build.geoserver.org with an external hack.

Action: Shut down ares, migrate build notifications.

Chit Chat

GeoTools report - anything to add:
https://github.com/geotools/geotools/wiki/GeoTools-Annual-Report-2017

Who is releasing this week? Maybe Torben:

https://github.com/geoserver/geoserver/wiki/Release-Schedule

Ari Jolma is trying to write a WCS 2.0 driver for GDAL, see
https://trac.osgeo.org/gdal/wiki/WCS%2Binteroperability

2

The OGC renewal deadline has moved to end of this month, since we are waiting a bug fix in the CITE testing application for GDAL.

Cheers,
Angelos

On 11/14/2017 07:56 PM, Andrea Aime wrote:

GeoTools / GeoWebcache / GeoServer Meeting 2017-11-14

Attending

Jody Garnett

Andrea Aime

Jukka Rahkonen

Ian Turton

Torben Barsballe
Actions from Last Meeting

    -

    Jody/Torben: (done) Schedule CITE debugging session
    -

    Jody: (done) Remind GeoTools PMC to vote on Java 9 Proposal
    -

    Jody: (missed) Forward OSGeo CITE Application email and determine how
    much time is left for this renewal application. Probably not much because
    automatic mail from OGC says “are due to be renewed by *October 31st, 2017*.
    -

    Jody: Need a spreadsheet comparing sprint location costs to justify
    budget request (short list from email discussion, compare flights and
    accommodation for January/February?)
    -

       No spreadsheet yet
       -

       James Hughes expressed interest in CCRi hosting/attending
       -

    Kevin: (done) Bounce GWC planning of gwc email list for discussion review
    -

    Jody: Revise http://osgeo.getinteractive.nl/projects/geotools/ with
    features list from OSGeo-Live

Agenda

    -

    Isolated workspace mail by Nuno
    -

    Java 9 compatibility follow up (sprint)
    -

    Budget (GeoServer and GeoTools) and CITE tests
    -

    Shutting down Ares
    -

    Chit/Chat

Isolated workspace mail by Nuno

Multitenancy for complex features, see “Isolated Workspaces” mail.

“The main (root) use case for this is to allow the publishing of the same
complex feature type in GeoServer multiple times in different workspaces”

    -

    Proposal or bug? Both…
    -

    Workspaces that are not listed globally
    -

    How does this differ from turning off global?
    -

       Should understand why turning off global does not meeting Nuno’s
       requirements? Appears to be due to them having common namespace
       (application schema requirement - example INSPIRE).

This is a request to read email and follow up with discussion.

Q: Should we remove JDBCConfig? (nobody answering mails or reviewing pull
requests regarding it)

    -

    Ask Boundless for next meeting

Or ask the interested party if they want to upgrade from making pull
request to becoming maintainers.
Java 9 compatibility follow up (and sprint?)

PR was merged, with a bit trouble, and master now has a distinct
FactoryRegistry separate from imageio.

Making a list of tasks here:

    -

    https://github.com/geotools/geotools/wiki/Java-9-Compatibility
    -

    Idea is to test and set up jobs with Java 9 for current release cycle

Java 8 EOL Oct 2018, so we have a bit of time left for GeoServer crowd
(conservative server side deployments). GeoTools does have early adopters.

Ideally test early and then plan, would like to avoid having a emergency
sprint in January close to release.

Q: Can we build with Java 9 on Travis?

Q: Is it worth making a milestone release?

    -

    It would answer “does it build” question
    -

    Would need some buy-in from user list to justify effort

Budget (GeoServer and GeoTools)

GeoTools Budget:
https://github.com/geotools/geotools/wiki/GeoTools-Budget-Request-2018

    -

    Budget request is for $5500 in total (the code sprint thing is a
    separate request)
    -

       4000 sprint request; this is pending us doing fund raising
       -

       1500 travel assistance
       -

    Topics considered for sprint:
    -

       Java 9 compatibility if needed
       -

       Java 8 Stream update for DataStore (see discussion in 2016)
       -

       Kick off Raster Process Engine project at OSGeo code sprint in Bonn
       -

          Design sprint, w/ architecture spike (geotools wrapper approach)?
          -

          Would need to confirm resourcing for this to work
          -

       Kick out EMF/XSD
       -

          Ian/Andrea have some frustrations .. how about ideas?
          -

          Upgraded for WMTS work, or replace with JAXB?
          -

          It is horribly opaque, can docs help? Not really it is complex.
          -

             Different modules been generated with different versions, have
             to grab that copy of eclipse that would work for each module
             -

          Massive overhead anytime we need a change
          -

          Action: Ian take discussion/research to email list

GeoServer:

    -

    Similar budget request from last year; around $3000 for sprint
    -

    Q: depending on topic we may get more people/interest? A: Then we would
    ask for more money, this is only a budget
    -

    Topics considered
    -

       GWC improvements: Kevin has been organized pushing this
       -

          If this is confirmed we can make OSGeo budget request and start
          setting up sprint planning
          -

          check with kevin if this is already in progress
          -

       REST bindings for WFS 3.0
       <https://github.com/opengeospatial/WFS_FES/blob/master/core/standard/clause_7_core.adoc&gt;?
       Swagger definition being done by OGC
       -

          Would this finish in 2018, and thus be good for a sprint?
          -

       CITE
       -

          Implement plan discussed previously, doing as a background
          activity has not been successful yet.

Action:

    -

    Jody: coordinate with GeoServer / GeoTools lists, concern about being
    able to take so much time for this activity, expect we will need to choose
    one

Shutting down Ares

CITE tests work on Build besides WFS 1.1, hangs indefinitely.

WFS 1.1 test has a problem, reported to CITE team:

    -

    https://github.com/opengeospatial/ets-wfs11/issues/77
    -

    Note we are reporting against an old release so expect no fix
    -

    https://github.com/geoserver/teamengine/tree/e4dda71c90ba601d39847d19969b4d617f90bb70
    -

    On ares this jobs also hangs, but is killed. We could reproduce this on
    build.geoserver.org with an external hack.

Action: Shut down ares, migrate build notifications.

Chit Chat

GeoTools report - anything to add:
https://github.com/geotools/geotools/wiki/GeoTools-Annual-Report-2017

Who is releasing this week? Maybe Torben:

https://github.com/geoserver/geoserver/wiki/Release-Schedule

Ari Jolma is trying to write a WCS 2.0 driver for GDAL, see
https://trac.osgeo.org/gdal/wiki/WCS%2Binteroperability

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot

_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

--
Angelos Tzotsos, PhD
Charter Member
Open Source Geospatial Foundation
http://users.ntua.gr/tzotsos

3

Hey,
just sharing another possibility for a code sprint that involves all projects, GeoTools, GeoServer, GWC:

  • Mass reformat all code in all active branches
  • Pick a static analysis tool and fix any issue found
  • Integrate said tool in the build (as its own goal) or as a github pull request plugin + nightly build
    Rationale: personally I’m getting kind of tired of people making pull request and then making excuses against existing (10 y old?) code practice for not formatting, leaving system outs, eating exceptions and what not…

Before you say so, yes, I’m well aware that it will be more likely that we introduce more bugs than those getting actually fixed, but it should make it easier to handle pull requests at least :-p

Cheers
Andrea

···

On Tue, Nov 14, 2017 at 6:56 PM, Andrea Aime <andrea.aime@anonymised.com> wrote:

GeoTools / GeoWebcache / GeoServer Meeting 2017-11-14

Attending

Jody Garnett

Andrea Aime

Jukka Rahkonen

Ian Turton

Torben Barsballe

Actions from Last Meeting- Jody/Torben: (done) Schedule CITE debugging session

  • Jody: (done) Remind GeoTools PMC to vote on Java 9 Proposal

  • Jody: (missed) Forward OSGeo CITE Application email and determine how much time is left for this renewal application. Probably not much because automatic mail from OGC says “are due to be renewed by October 31st, 2017.

  • Jody: Need a spreadsheet comparing sprint location costs to justify budget request (short list from email discussion, compare flights and accommodation for January/February?)

  • No spreadsheet yet

  • James Hughes expressed interest in CCRi hosting/attending

  • Kevin: (done) Bounce GWC planning of gwc email list for discussion review

  • Jody: Revise http://osgeo.getinteractive.nl/projects/geotools/ with features list from OSGeo-Live

Agenda- Isolated workspace mail by Nuno

  • Java 9 compatibility follow up (sprint)

  • Budget (GeoServer and GeoTools) and CITE tests

  • Shutting down Ares

  • Chit/Chat

Isolated workspace mail by Nuno

Multitenancy for complex features, see “Isolated Workspaces” mail.

“The main (root) use case for this is to allow the publishing of the same complex feature type in GeoServer multiple times in different workspaces”

  • Proposal or bug? Both…

  • Workspaces that are not listed globally

  • How does this differ from turning off global?

  • Should understand why turning off global does not meeting Nuno’s requirements? Appears to be due to them having common namespace (application schema requirement - example INSPIRE).

This is a request to read email and follow up with discussion.

Q: Should we remove JDBCConfig? (nobody answering mails or reviewing pull requests regarding it)

  • Ask Boundless for next meeting

Or ask the interested party if they want to upgrade from making pull request to becoming maintainers.

Java 9 compatibility follow up (and sprint?)

PR was merged, with a bit trouble, and master now has a distinct FactoryRegistry separate from imageio.

Making a list of tasks here:

Java 8 EOL Oct 2018, so we have a bit of time left for GeoServer crowd (conservative server side deployments). GeoTools does have early adopters.

Ideally test early and then plan, would like to avoid having a emergency sprint in January close to release.

Q: Can we build with Java 9 on Travis?

Q: Is it worth making a milestone release?

  • It would answer “does it build” question

  • Would need some buy-in from user list to justify effort

Budget (GeoServer and GeoTools)

GeoTools Budget: https://github.com/geotools/geotools/wiki/GeoTools-Budget-Request-2018

  • Budget request is for $5500 in total (the code sprint thing is a separate request)

  • 4000 sprint request; this is pending us doing fund raising

  • 1500 travel assistance

  • Topics considered for sprint:

  • Java 9 compatibility if needed

  • Java 8 Stream update for DataStore (see discussion in 2016)

  • Kick off Raster Process Engine project at OSGeo code sprint in Bonn

  • Design sprint, w/ architecture spike (geotools wrapper approach)?

  • Would need to confirm resourcing for this to work

  • Kick out EMF/XSD

  • Ian/Andrea have some frustrations … how about ideas?

  • Upgraded for WMTS work, or replace with JAXB?

  • It is horribly opaque, can docs help? Not really it is complex.

  • Different modules been generated with different versions, have to grab that copy of eclipse that would work for each module

  • Massive overhead anytime we need a change

  • Action: Ian take discussion/research to email list

GeoServer:

  • Similar budget request from last year; around $3000 for sprint

  • Q: depending on topic we may get more people/interest? A: Then we would ask for more money, this is only a budget

  • Topics considered

  • GWC improvements: Kevin has been organized pushing this

  • If this is confirmed we can make OSGeo budget request and start setting up sprint planning

  • check with kevin if this is already in progress

  • REST bindings for WFS 3.0? Swagger definition being done by OGC

  • Would this finish in 2018, and thus be good for a sprint?

  • CITE

  • Implement plan discussed previously, doing as a background activity has not been successful yet.

Action:

  • Jody: coordinate with GeoServer / GeoTools lists, concern about being able to take so much time for this activity, expect we will need to choose one

Shutting down Ares

CITE tests work on Build besides WFS 1.1, hangs indefinitely.

WFS 1.1 test has a problem, reported to CITE team:

Action: Shut down ares, migrate build notifications.

Chit Chat

GeoTools report - anything to add: https://github.com/geotools/geotools/wiki/GeoTools-Annual-Report-2017

Who is releasing this week? Maybe Torben:

https://github.com/geoserver/geoserver/wiki/Release-Schedule

Ari Jolma is trying to write a WCS 2.0 driver for GDAL, see https://trac.osgeo.org/gdal/wiki/WCS%2Binteroperability

–

Regards,

Andrea Aime

==
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

AVVERTENZE AI SENSI DEL D.Lgs. 196/2003

Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003.

The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy’s New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and delete the information in this message that has been received in error. The sender does not give any warranty or accept liability as the content, accuracy or completeness of sent messages and accepts no responsibility for changes made after they were sent or for other risks which arise as a result of e-mail transmission, viruses, etc.

4

That would be good for me too.

Ian

···

On 19 Nov 2017 13:59, “Andrea Aime” <andrea.aime@anonymised.com> wrote:

Hey,
just sharing another possibility for a code sprint that involves all projects, GeoTools, GeoServer, GWC:

  • Mass reformat all code in all active branches
  • Pick a static analysis tool and fix any issue found
  • Integrate said tool in the build (as its own goal) or as a github pull request plugin + nightly build
    Rationale: personally I’m getting kind of tired of people making pull request and then making excuses against existing (10 y old?) code practice for not formatting, leaving system outs, eating exceptions and what not…

Before you say so, yes, I’m well aware that it will be more likely that we introduce more bugs than those getting actually fixed, but it should make it easier to handle pull requests at least :-p

Cheers
Andrea

Check out the vibrant tech community on one of the world’s most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot

Geoserver-devel mailing list
Geoserver-devel@anonymised.com.366…sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

On Tue, Nov 14, 2017 at 6:56 PM, Andrea Aime <andrea.aime@anonymised.com> wrote:

GeoTools / GeoWebcache / GeoServer Meeting 2017-11-14

Attending

Jody Garnett

Andrea Aime

Jukka Rahkonen

Ian Turton

Torben Barsballe

Actions from Last Meeting- Jody/Torben: (done) Schedule CITE debugging session

  • Jody: (done) Remind GeoTools PMC to vote on Java 9 Proposal

  • Jody: (missed) Forward OSGeo CITE Application email and determine how much time is left for this renewal application. Probably not much because automatic mail from OGC says “are due to be renewed by October 31st, 2017.

  • Jody: Need a spreadsheet comparing sprint location costs to justify budget request (short list from email discussion, compare flights and accommodation for January/February?)

  • No spreadsheet yet

  • James Hughes expressed interest in CCRi hosting/attending

  • Kevin: (done) Bounce GWC planning of gwc email list for discussion review

  • Jody: Revise http://osgeo.getinteractive.nl/projects/geotools/ with features list from OSGeo-Live

Agenda- Isolated workspace mail by Nuno

  • Java 9 compatibility follow up (sprint)

  • Budget (GeoServer and GeoTools) and CITE tests

  • Shutting down Ares

  • Chit/Chat

Isolated workspace mail by Nuno

Multitenancy for complex features, see “Isolated Workspaces” mail.

“The main (root) use case for this is to allow the publishing of the same complex feature type in GeoServer multiple times in different workspaces”

  • Proposal or bug? Both…

  • Workspaces that are not listed globally

  • How does this differ from turning off global?

  • Should understand why turning off global does not meeting Nuno’s requirements? Appears to be due to them having common namespace (application schema requirement - example INSPIRE).

This is a request to read email and follow up with discussion.

Q: Should we remove JDBCConfig? (nobody answering mails or reviewing pull requests regarding it)

  • Ask Boundless for next meeting

Or ask the interested party if they want to upgrade from making pull request to becoming maintainers.

Java 9 compatibility follow up (and sprint?)

PR was merged, with a bit trouble, and master now has a distinct FactoryRegistry separate from imageio.

Making a list of tasks here:

Java 8 EOL Oct 2018, so we have a bit of time left for GeoServer crowd (conservative server side deployments). GeoTools does have early adopters.

Ideally test early and then plan, would like to avoid having a emergency sprint in January close to release.

Q: Can we build with Java 9 on Travis?

Q: Is it worth making a milestone release?

  • It would answer “does it build” question

  • Would need some buy-in from user list to justify effort

Budget (GeoServer and GeoTools)

GeoTools Budget: https://github.com/geotools/geotools/wiki/GeoTools-Budget-Request-2018

  • Budget request is for $5500 in total (the code sprint thing is a separate request)

  • 4000 sprint request; this is pending us doing fund raising

  • 1500 travel assistance

  • Topics considered for sprint:

  • Java 9 compatibility if needed

  • Java 8 Stream update for DataStore (see discussion in 2016)

  • Kick off Raster Process Engine project at OSGeo code sprint in Bonn

  • Design sprint, w/ architecture spike (geotools wrapper approach)?

  • Would need to confirm resourcing for this to work

  • Kick out EMF/XSD

  • Ian/Andrea have some frustrations … how about ideas?

  • Upgraded for WMTS work, or replace with JAXB?

  • It is horribly opaque, can docs help? Not really it is complex.

  • Different modules been generated with different versions, have to grab that copy of eclipse that would work for each module

  • Massive overhead anytime we need a change

  • Action: Ian take discussion/research to email list

GeoServer:

  • Similar budget request from last year; around $3000 for sprint

  • Q: depending on topic we may get more people/interest? A: Then we would ask for more money, this is only a budget

  • Topics considered

  • GWC improvements: Kevin has been organized pushing this

  • If this is confirmed we can make OSGeo budget request and start setting up sprint planning

  • check with kevin if this is already in progress

  • REST bindings for WFS 3.0? Swagger definition being done by OGC

  • Would this finish in 2018, and thus be good for a sprint?

  • CITE

  • Implement plan discussed previously, doing as a background activity has not been successful yet.

Action:

  • Jody: coordinate with GeoServer / GeoTools lists, concern about being able to take so much time for this activity, expect we will need to choose one

Shutting down Ares

CITE tests work on Build besides WFS 1.1, hangs indefinitely.

WFS 1.1 test has a problem, reported to CITE team:

Action: Shut down ares, migrate build notifications.

Chit Chat

GeoTools report - anything to add: https://github.com/geotools/geotools/wiki/GeoTools-Annual-Report-2017

Who is releasing this week? Maybe Torben:

https://github.com/geoserver/geoserver/wiki/Release-Schedule

Ari Jolma is trying to write a WCS 2.0 driver for GDAL, see https://trac.osgeo.org/gdal/wiki/WCS%2Binteroperability

–

Regards,

Andrea Aime

==
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

AVVERTENZE AI SENSI DEL D.Lgs. 196/2003

Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003.

The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy’s New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and delete the information in this message that has been received in error. The sender does not give any warranty or accept liability as the content, accuracy or completeness of sent messages and accepts no responsibility for changes made after they were sent or for other risks which arise as a result of e-mail transmission, viruses, etc.

5

Yes this does sound like a very "code sprint" kind of thing. Quite a
bit of work for something that will help maintenance in the long run and
decidedly "boring" so there's little likelihood that it would get funded
otherwise.

On 2017-11-19 12:45 PM, Ian Turton wrote:

That would be good for me too.

Ian

On 19 Nov 2017 13:59, "Andrea Aime" <andrea.aime@anonymised.com
<mailto:andrea.aime@anonymised.com>> wrote:

    Hey,
    just sharing another possibility for a code sprint that involves
    all projects, GeoTools, GeoServer, GWC:

      * Mass reformat all code in all active branches
      * Pick a static analysis tool and fix any issue found
      * Integrate said tool in the build (as its own goal) or as a
        github pull request plugin + nightly build

    Rationale: personally I'm getting kind of tired of people making
    pull request and then making excuses against existing (10 y old?)
    code practice for not formatting, leaving system outs, eating
    exceptions and what not....
    Before you say so, yes, I'm well aware that it will be more likely
    that we introduce more bugs than those getting actually fixed, but
    it should make it easier to handle pull requests at least :-p

    Cheers
    Andrea

    On Tue, Nov 14, 2017 at 6:56 PM, Andrea Aime
    <andrea.aime@anonymised.com
    <mailto:andrea.aime@anonymised.com>> wrote:

        GeoTools / GeoWebcache / GeoServer Meeting 2017-11-14

            Attending

        Jody Garnett

        Andrea Aime

        Jukka Rahkonen

        Ian Turton

        Torben Barsballe

            Actions from Last Meeting

         *

            Jody/Torben: (done) Schedule CITE debugging session

         *

            Jody: (done) Remind GeoTools PMC to vote on Java 9 Proposal

         *

            Jody: (missed) Forward OSGeo CITE Application email and
            determine how much time is left for this renewal
            application. Probably not much because automatic mail from
            OGC says “are due to be renewed by *October 31st, 2017*.

         *

            Jody: Need a spreadsheet comparing sprint location costs
            to justify budget request (short list from email
            discussion, compare flights and accommodation for
            January/February?)

             o

                No spreadsheet yet

             o

                James Hughes expressed interest in CCRi hosting/attending

         *

            Kevin: (done) Bounce GWC planning of gwc email list for
            discussion review

         *

            Jody: Revise
            http://osgeo.getinteractive.nl/projects/geotools/
            <http://osgeo.getinteractive.nl/projects/geotools/&gt;with
            features list from OSGeo-Live

            Agenda

         *

            Isolated workspace mail by Nuno

         *

            Java 9 compatibility follow up (sprint)

         *

            Budget (GeoServer and GeoTools) and CITE tests

         *

            Shutting down Ares

         *

            Chit/Chat

            Isolated workspace mail by Nuno

        Multitenancy for complex features, see “Isolated Workspaces” mail.

        “The main (root) use case for this is to allow the publishing
        of the same complex feature type in GeoServer multiple times
        in different workspaces”

         *

            Proposal or bug? Both…

         *

            Workspaces that are not listed globally

         *

            How does this differ from turning off global?

             o

                Should understand why turning off global does not
                meeting Nuno’s requirements? Appears to be due to them
                having common namespace (application schema
                requirement - example INSPIRE).

        This is a request to read email and follow up with discussion.

        Q: Should we remove JDBCConfig? (nobody answering mails or
        reviewing pull requests regarding it)

         *

            Ask Boundless for next meeting

        Or ask the interested party if they want to upgrade from
        making pull request to becoming maintainers.

            Java 9 compatibility follow up (and sprint?)

        PR was merged, with a bit trouble, and master now has a
        distinct FactoryRegistry separate from imageio.

        Making a list of tasks here:

         *

            https://github.com/geotools/geotools/wiki/Java-9-Compatibility
            <https://github.com/geotools/geotools/wiki/Java-9-Compatibility&gt;

         *

            Idea is to test and set up jobs with Java 9 for current
            release cycle

        Java 8 EOL Oct 2018, so we have a bit of time left for
        GeoServer crowd (conservative server side deployments).
        GeoTools does have early adopters.

        Ideally test early and then plan, would like to avoid having a
        emergency sprint in January close to release.

        Q: Can we build with Java 9 on Travis?

        Q: Is it worth making a milestone release?

         *

            It would answer “does it build” question

         *

            Would need some buy-in from user list to justify effort

            Budget (GeoServer and GeoTools)

        GeoTools Budget:
        https://github.com/geotools/geotools/wiki/GeoTools-Budget-Request-2018
        <https://github.com/geotools/geotools/wiki/GeoTools-Budget-Request-2018&gt;

         *

            Budget request is for $5500 in total (the code sprint
            thing is a separate request)

             o

                4000 sprint request; this is pending us doing fund raising

             o

                1500 travel assistance

         *

            Topics considered for sprint:

             o

                Java 9 compatibility if needed

             o

                Java 8 Stream update for DataStore (see discussion in
                2016)

             o

                Kick off Raster Process Engine project at OSGeo code
                sprint in Bonn

                 +

                    Design sprint, w/ architecture spike (geotools
                    wrapper approach)?

                 +

                    Would need to confirm resourcing for this to work

             o

                Kick out EMF/XSD

                 +

                    Ian/Andrea have some frustrations .. how about ideas?

                 +

                    Upgraded for WMTS work, or replace with JAXB?

                 +

                    It is horribly opaque, can docs help? Not really
                    it is complex.

                     #

                        Different modules been generated with
                        different versions, have to grab that copy of
                        eclipse that would work for each module

                 +

                    Massive overhead anytime we need a change

                 +

                    Action: Ian take discussion/research to email list

        GeoServer:

         *

            Similar budget request from last year; around$3000for sprint

         *

            Q: depending on topic we may get more people/interest? A:
            Then we would ask for more money, this is only a budget

         *

            Topics considered

             o

                GWC improvements: Kevin has been organized pushing this

                 +

                    If this is confirmed we can make OSGeo budget
                    request and start setting up sprint planning

                 +

                    check with kevin if this is already in progress

             o

                REST bindings for WFS 3.0
                <https://github.com/opengeospatial/WFS_FES/blob/master/core/standard/clause_7_core.adoc&gt;?
                Swagger definition being done by OGC

                 +

                    Would this finish in 2018, and thus be good for a
                    sprint?

             o

                CITE

                 +

                    Implement plan discussed previously, doing as a
                    background activity has not been successful yet.

        Action:

         *

            Jody: coordinate with GeoServer / GeoTools lists, concern
            about being able to take so much time for this activity,
            expect we will need to choose one

            Shutting down Ares

        CITE tests work on Build besides WFS 1.1, hangs indefinitely.

        WFS 1.1 test has a problem, reported to CITE team:

         *

            https://github.com/opengeospatial/ets-wfs11/issues/77
            <https://github.com/opengeospatial/ets-wfs11/issues/77&gt;

         *

            Note we are reporting against an old release so expect no fix

         *

            https://github.com/geoserver/teamengine/tree/e4dda71c90ba601d39847d19969b4d617f90bb70
            <https://github.com/geoserver/teamengine/tree/e4dda71c90ba601d39847d19969b4d617f90bb70&gt;

         *

            On ares this jobs also hangs, but is killed. We could
            reproduce this on build.geoserver.org
            <http://build.geoserver.org> with an external hack.

        Action:Shut down ares, migrate build notifications.

            Chit Chat

        GeoTools report - anything to add:
        https://github.com/geotools/geotools/wiki/GeoTools-Annual-Report-2017
        <https://github.com/geotools/geotools/wiki/GeoTools-Annual-Report-2017&gt;

        Who is releasing this week? Maybe Torben:

        https://github.com/geoserver/geoserver/wiki/Release-Schedule
        <https://github.com/geoserver/geoserver/wiki/Release-Schedule&gt;

        Ari Jolma is trying to write a WCS 2.0 driver for GDAL, see
        https://trac.osgeo.org/gdal/wiki/WCS%2Binteroperability
        <https://trac.osgeo.org/gdal/wiki/WCS%2Binteroperability&gt;

    --

    Regards,

    Andrea Aime

    ==GeoServer Professional Services from the experts! Visit
    http://goo.gl/it488V for more information.==Ing. Andrea Aime
    @geowolfTechnical LeadGeoSolutions S.A.S.Via di Montramito
    3/A55054 Massarosa (LU)phone: +39 0584 962313
    <tel:+39%200584%20962313>fax: +39 0584 1660272
    <tel:+39%200584%20166%200272>mob: +39 339 8844549
    <tel:+39%20339%20884%204549>http://www.geo-solutions.ithttp://twitter.com/geosolutions_it
    <http://twitter.com/geosolutions_it&gt;

    AVVERTENZE AI SENSI DEL D.Lgs. 196/2003

    Le informazioni contenute in questo messaggio di posta elettronica
    e/o nel/i file/s allegato/i sono da considerarsi strettamente
    riservate. Il loro utilizzo è consentito esclusivamente al
    destinatario del messaggio, per le finalità indicate nel messaggio
    stesso. Qualora riceviate questo messaggio senza esserne il
    destinatario, Vi preghiamo cortesemente di darcene notizia via
    e-mail e di procedere alla distruzione del messaggio stesso,
    cancellandolo dal Vostro sistema. Conservare il messaggio stesso,
    divulgarlo anche in parte, distribuirlo ad altri soggetti,
    copiarlo, od utilizzarlo per finalità diverse, costituisce
    comportamento contrario ai principi dettati dal D.Lgs. 196/2003.

    The information in this message and/or attachments, is intended
    solely for the attention and use of the named addressee(s) and may
    be confidential or proprietary in nature or covered by the
    provisions of privacy act (Legislative Decree June, 30 2003,
    no.196 - Italy's New Data Protection Code).Any use not in accord
    with its purpose, any disclosure, reproduction, copying,
    distribution, or either dissemination, either whole or partial, is
    strictly forbidden except previous formal approval of the named
    addressee(s). If you are not the intended recipient, please
    contact immediately the sender by telephone, fax or e-mail and
    delete the information in this message that has been received in
    error. The sender does not give any warranty or accept liability
    as the content, accuracy or completeness of sent messages and
    accepts no responsibility for changes made after they were sent
    or for other risks which arise as a result of e-mail transmission,
    viruses, etc.

    ------------------------------------------------------------------------------
    Check out the vibrant tech community on one of the world's most
    engaging tech sites, Slashdot.org! http://sdm.link/slashdot
    _______________________________________________
    Geoserver-devel mailing list
    Geoserver-devel@lists.sourceforge.net
    <mailto:Geoserver-devel@lists.sourceforge.net>
    https://lists.sourceforge.net/lists/listinfo/geoserver-devel
    <https://lists.sourceforge.net/lists/listinfo/geoserver-devel&gt;

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot

_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

--
Kevin Michael Smith
<smithkm@anonymised.com>

6

Of course there is nothing wrong with an exciting sprint either - indeed easier to attract sponsorship and contributors.

If I can remind everyone to check availability for next year, would like to confirm expectations so we can provide a budget request to OSGeo.

···

On 19 Nov 2017 13:59, “Andrea Aime” <andrea.aime@anonymised.com> wrote:

Hey,
just sharing another possibility for a code sprint that involves all projects, GeoTools, GeoServer, GWC:

  • Mass reformat all code in all active branches
  • Pick a static analysis tool and fix any issue found
  • Integrate said tool in the build (as its own goal) or as a github pull request plugin + nightly build
    Rationale: personally I’m getting kind of tired of people making pull request and then making excuses against existing (10 y old?) code practice for not formatting, leaving system outs, eating exceptions and what not…

Before you say so, yes, I’m well aware that it will be more likely that we introduce more bugs than those getting actually fixed, but it should make it easier to handle pull requests at least :-p

Cheers
Andrea

Check out the vibrant tech community on one of the world’s most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot

Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

On Tue, Nov 14, 2017 at 6:56 PM, Andrea Aime <andrea.aime@anonymised.com> wrote:

GeoTools / GeoWebcache / GeoServer Meeting 2017-11-14

Attending

Jody Garnett

Andrea Aime

Jukka Rahkonen

Ian Turton

Torben Barsballe

Actions from Last Meeting- Jody/Torben: (done) Schedule CITE debugging session

  • Jody: (done) Remind GeoTools PMC to vote on Java 9 Proposal

  • Jody: (missed) Forward OSGeo CITE Application email and determine how much time is left for this renewal application. Probably not much because automatic mail from OGC says “are due to be renewed by October 31st, 2017.

  • Jody: Need a spreadsheet comparing sprint location costs to justify budget request (short list from email discussion, compare flights and accommodation for January/February?)

  • No spreadsheet yet

  • James Hughes expressed interest in CCRi hosting/attending

  • Kevin: (done) Bounce GWC planning of gwc email list for discussion review

  • Jody: Revise http://osgeo.getinteractive.nl/projects/geotools/ with features list from OSGeo-Live

Agenda- Isolated workspace mail by Nuno

  • Java 9 compatibility follow up (sprint)

  • Budget (GeoServer and GeoTools) and CITE tests

  • Shutting down Ares

  • Chit/Chat

Isolated workspace mail by Nuno

Multitenancy for complex features, see “Isolated Workspaces” mail.

“The main (root) use case for this is to allow the publishing of the same complex feature type in GeoServer multiple times in different workspaces”

  • Proposal or bug? Both…

  • Workspaces that are not listed globally

  • How does this differ from turning off global?

  • Should understand why turning off global does not meeting Nuno’s requirements? Appears to be due to them having common namespace (application schema requirement - example INSPIRE).

This is a request to read email and follow up with discussion.

Q: Should we remove JDBCConfig? (nobody answering mails or reviewing pull requests regarding it)

  • Ask Boundless for next meeting

Or ask the interested party if they want to upgrade from making pull request to becoming maintainers.

Java 9 compatibility follow up (and sprint?)

PR was merged, with a bit trouble, and master now has a distinct FactoryRegistry separate from imageio.

Making a list of tasks here:

Java 8 EOL Oct 2018, so we have a bit of time left for GeoServer crowd (conservative server side deployments). GeoTools does have early adopters.

Ideally test early and then plan, would like to avoid having a emergency sprint in January close to release.

Q: Can we build with Java 9 on Travis?

Q: Is it worth making a milestone release?

  • It would answer “does it build” question

  • Would need some buy-in from user list to justify effort

Budget (GeoServer and GeoTools)

GeoTools Budget: https://github.com/geotools/geotools/wiki/GeoTools-Budget-Request-2018

  • Budget request is for $5500 in total (the code sprint thing is a separate request)

  • 4000 sprint request; this is pending us doing fund raising

  • 1500 travel assistance

  • Topics considered for sprint:

  • Java 9 compatibility if needed

  • Java 8 Stream update for DataStore (see discussion in 2016)

  • Kick off Raster Process Engine project at OSGeo code sprint in Bonn

  • Design sprint, w/ architecture spike (geotools wrapper approach)?

  • Would need to confirm resourcing for this to work

  • Kick out EMF/XSD

  • Ian/Andrea have some frustrations … how about ideas?

  • Upgraded for WMTS work, or replace with JAXB?

  • It is horribly opaque, can docs help? Not really it is complex.

  • Different modules been generated with different versions, have to grab that copy of eclipse that would work for each module

  • Massive overhead anytime we need a change

  • Action: Ian take discussion/research to email list

GeoServer:

  • Similar budget request from last year; around $3000 for sprint

  • Q: depending on topic we may get more people/interest? A: Then we would ask for more money, this is only a budget

  • Topics considered

  • GWC improvements: Kevin has been organized pushing this

  • If this is confirmed we can make OSGeo budget request and start setting up sprint planning

  • check with kevin if this is already in progress

  • REST bindings for WFS 3.0? Swagger definition being done by OGC

  • Would this finish in 2018, and thus be good for a sprint?

  • CITE

  • Implement plan discussed previously, doing as a background activity has not been successful yet.

Action:

  • Jody: coordinate with GeoServer / GeoTools lists, concern about being able to take so much time for this activity, expect we will need to choose one

Shutting down Ares

CITE tests work on Build besides WFS 1.1, hangs indefinitely.

WFS 1.1 test has a problem, reported to CITE team:

Action: Shut down ares, migrate build notifications.

Chit Chat

GeoTools report - anything to add: https://github.com/geotools/geotools/wiki/GeoTools-Annual-Report-2017

Who is releasing this week? Maybe Torben:

https://github.com/geoserver/geoserver/wiki/Release-Schedule

Ari Jolma is trying to write a WCS 2.0 driver for GDAL, see https://trac.osgeo.org/gdal/wiki/WCS%2Binteroperability

–

Regards,

Andrea Aime

== 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

AVVERTENZE AI SENSI DEL D.Lgs. 196/2003

Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003.

The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy’s New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and delete the information in this message that has been received in error. The sender does not give any warranty or accept liability as the content, accuracy or completeness of sent messages and accepts no responsibility for changes made after they were sent or for other risks which arise as a result of e-mail transmission, viruses, etc.

–
Jody Garnett