[Geoserver-devel] GeoTools / GeoServer Meeting 2017-11-28

GeoServer GeoServer Developer
1

Attending

Ben Caradoc-Davies

Torben Barsballe

Jody Garnett

Kevin Smith

Jukka Rahkonen

Apologies# Agenda- Ares Migration

  • GWC Configuration Rewrite

  • Budget Requests

  • Development Discussion

Actions- Kevin to prepare GWC configuration change proposal

  • Ben/Simone to email board with GeoServer budget request

  • Jody to email the board with GeoTools budget request

  • Kevin to email incubation list with GWC budget request

  • Jody to reply to devel list about eclipse compiler protections

  • Nick/Torben - Install Java 9, add non-scheduled job. Make sure it doesn’t publish artifacts

Previous meeting actions- (done) Ask about JDBCConfig support

  • Ian take EMF/XSD discussion/research to email list

  • (done) Jody: coordinate budget with GeoServer / GeoTools lists

  • Jody: sprint planning topics

  • Jody: Sprint planning spreadsheet

  • Shut down ares, migrate build notifications.

Action discussion:

  • JDBCConfig: community module shared to facilitate collaboration, not in position to support user list.

  • Budget requests - will make during today’s meeting

  • Sprint planning topics:

  • JAI-EXT operation performance performance parity with JAI

  • GWC feature parity, precondition code cleanup

  • Sprint planning:

  • Jan 13 $2000, Jan 20 $1000, Jan 21 $1000

Ares Migration

  • Ares shutdown? All jobs/notifications migrated

  • Jobs on ares disabled and not running

  • Exceptions GeoFence and GeoScript

  • Should be fixed in week or so

  • Ares still around but deprecated

  • See mailing list

GWC Configuration Rewrite- Boundless want to rework GWC configuration

  • API breaking change

  • Action: Kevin to prepare GWC configuration change proposal

  • Needed for clustering

  • Jody: 2.0?

  • Kevin: no changes on disk, add support for not in-memory, preserve compatibility.

Budget requests

Board needs to pull together a draft budget before Dec 7th meeting, call has gone out to project officers for any budget requests.

GeoServer

  • Last year: asked for $2000, spend $3000

  • This year:

  • $1000 for project

  • $2000 for code sprint

  • Action: Ben/Simone to email board with budget request

GeoTools

  • Bonn sprint?

  • Related to JAI fix, but not directly

  • $2000 for travel

  • Action: Jody to email the board with budget request

GeoWebCache

  • If we do a GWC sprint, travel budget would be useful

  • Needs time rather than money

  • Request $1000 for possible sprint

  • Action: Kevin to email incubation list with budget request

Development Discussion

Windows developers making progress on the developer lists.

  • builds without tests

  • eclipse compiler protections change from error → warning

  • Action: Jody to reply to devel list about eclipse compiler protections

Java 9 compatibilities:

Try in December / January to build

A: Should be doable - Action: Nick/Torben - Install Java 9, add non-scheduled job. Make sure it doesn’t publish artifacts

2

On Tue, Nov 28, 2017 at 9:31 PM, Torben Barsballe <
tbarsballe@anonymised.com> wrote:

Action discussion:

   -

   JDBCConfig: community module shared to facilitate collaboration, not
   in position to support user list.

So next time someone starts bombarding the user list with requests about
jdbconfig I'll tell them that "the module is shared to facilitate
collaboration, but there is no one in position to support user list,
so don't wait for answers", and for pull request, we'll do the same? (the
pull requests about JDBCConfig are still there open by the way, no reviews
that I can see)
If that is the case and the only target are developers willing to pitch in
maybe it's best to remove it from the nightly builds so that simple users
don't grab it and get the false impression someone may care about it?

Ideas:

   - We probably need some way to ensure users understand that community
   modules are not supported in the common sense... maybe a wrapper page with
   a big red title stating that at the top, and the list of binary packages
   below? Or a warning at the top of the docs in each module that has no one
   caring about it? (which is not the whole list of community modules, mind)
   - Sharing a community module in packaged form is done to allow users to
   try it out, if there is no one willing to follow up on the user list, then
   it should be left in source form only, developers will be able to try it
   out anyways (and the docs can give support in that direction too, maybe
   just the command line needed to build the module, something like "mvn clean
   install -PmoduleProfile -DskipTests").

Some of the above needs to be handled, it is not fair for the people not
helping in the user list to take decision about
how the communication with users should be handled. First take the heat on
a daily basis, then you can speak with some knowledge of what you're
talking about.

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.

3

Hi all,
I agree with all that Andrea says.

My own opinion is that: creating \ keeping a community module in GeoServer with no intention to give support
to users at all or even review pull requests related to it doesn’t make any sense*,* this community module
should be removed*.*

If JDBC config module developers need a common place to store the code, mange issues, etc … then create a
repository for it, maybe under GeoServer ?

···

On 11/29/2017 07:49 AM, Andrea Aime wrote:

On Tue, Nov 28, 2017 at 9:31 PM, Torben Barsballe <tbarsballe@…3839…> wrote:

Action discussion:

  • JDBCConfig: community module shared to facilitate collaboration, not in position to support user list.

So next time someone starts bombarding the user list with requests about jdbconfig I’ll tell them that “the module is shared to facilitate collaboration, but there is no one in position to support user list, so don’t wait for answers”, and for pull request, we’ll do the same? (the pull requests about JDBCConfig are still there open by the way, no reviews that I can see)
If that is the case and the only target are developers willing to pitch in maybe it’s best to remove it from the nightly builds so that simple users don’t grab it and get the false impression someone may care about it?

Ideas:

  • We probably need some way to ensure users understand that community modules are not supported in the common sense… maybe a wrapper page with a big red title stating that at the top, and the list of binary packages below? Or a warning at the top of the docs in each module that has no one caring about it? (which is not the whole list of community modules, mind)
  • Sharing a community module in packaged form is done to allow users to try it out, if there is no one willing to follow up on the user list, then it should be left in source form only, developers will be able to try it out anyways (and the docs can give support in that direction too, maybe just the command line needed to build the module, something like “mvn clean install -PmoduleProfile -DskipTests”).
    Some of the above needs to be handled, it is not fair for the people not helping in the user list to take decision about

how the communication with users should be handled. First take the heat on a daily basis, then you can speak with some knowledge of what you’re talking about.

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.

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! [http://sdm.link/slashdot](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)


-- 
Regards,
Nuno Oliveira
==
GeoServer Professional Services from the experts! Visit [http://goo.gl/it488V](http://goo.gl/it488V) for more information.
==

Nuno Miguel Carvalho Oliveira
@nmcoliveira
Software Engineer

GeoSolutions S.A.S.
Via di Montramito 3/A
55054  Massarosa (LU)
Italy
phone: +39 0584 962313
fax:      +39 0584 1660272

[http://www.geo-solutions.it](http://www.geo-solutions.it)
[http://twitter.com/geosolutions_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

On Wed, Nov 29, 2017 at 1:28 PM, Nuno Oliveira <
nuno.oliveira@anonymised.com> wrote:

My own opinion is that: creating \ keeping a community module in GeoServer
with no intention to give support
to users at all or even review pull requests related to it doesn't make
any sense*, *this community module
should be removed*. *

If JDBC config module developers need a common place to store the code,
mange issues, etc ... then create a
repository for it, maybe under GeoServer ?

I would not mind keeping it there had the problem only been about users,
just remove the nightly packaging so that
users cannot get confused by it and leave "developer collaboration" to
flourish by mails/pull requests/whatever.

However, even developer collaboration requires effort... if there is really
no intention of supporting pull requests, then yes, we
have a problem ... now I do understand that time is limited for everybody,
but pull requests in questions are almost
2 months old...

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

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.