Re: [Geoserver-devel] GSIP-221 mkdocs proposal (closing January 3rd)

2024-01-02 Thread Nuno Oliveira 
+1

On Tue, Jan 2, 2024 at 11:15 AM Rahkonen Jukka <
jukka.rahko...@maanmittauslaitos.fi> wrote:

> +1
>
>
>
> -Jukka Rahkonen-
>
>
>
> *Lähettäjä:* Torben Barsballe 
> *Lähetetty:* tiistai 2. tammikuuta 2024 4.30
> *Vastaanottaja:* Jody Garnett 
> *Kopio:* Geoserver-devel 
> *Aihe:* Re: [Geoserver-devel] GSIP-221 mkdocs proposal (closing January
> 3rd)
>
>
>
> +1
>
>
>
> Cheers,
>
> Torben
>
>
>
> On Sun, Dec 31, 2023 at 12:11 PM Jody Garnett 
> wrote:
>
> 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
>
>
>
>
> Thanks to Krishna Lodha (rottengrapes.tech) for woking on this proposal
> with me.
>
>
>
> Our policy
>  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
>
> ___
> 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] [Geotools-devel] GeoTools / GeoServer PMC meeting - 2024-01-02

2024-01-02 Thread Brad Hards 
On Wednesday, 3 January 2024 5:35:42 AM AEDT Torben Barsballe wrote:
> Wicket 9 upgrade
> 
> https://github.com/geoserver/geoserver/pull/7154
> 
> Need to collect all pages and panels that need to be tested, make a list,
> and divide the list amongst participants to the testing effort. First we
> need Brad’s ok to move on.

Part of the Wicket 9 changes is a (strict) Content Security Policy.
See
https://nightlies.apache.org/wicket/guide/9.x/single.html#_content_security_policy_csp

CSP could help us a lot with security. See
https://developer.mozilla.org/en-US/docs/Web/HTTP/CSP
for what it does. The TL;DR; version is it blocks most XSS attacks.

It doesn't come for free though. We need to move or remove all the
inline styling and javascript. For inline javascript, it
needs to go into a "renderHead()" method.

We also need to remove inline event handlers.

I would like help to do that work, although I will get some of it done soon.
Please let me know if you can help

Since this stands a pretty good chance of breaking stuff,
we should defer the manual testing.

The only good news I have is that it looks like there will be automation
support for getting from Wicket 9 to Wicket 10.
https://cwiki.apache.org/confluence/display/WICKET/Migration+to+Wicket+10.0#MigrationtoWicket10.0-AddmigrationrecipestoWicket10WICKET-7029

Brad




___
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?

2024-01-02 Thread Torben Barsballe 
That plan sounds good to me. I've been using a 120 char line length on
other projects, and it's been good, so +1 to the Palantir format.

Cheers,
Torben

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
> .
> 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] Time to upgrade Spotless... and maybe take advantage of the break?

2024-01-02 Thread Jody Garnett 
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
> .
> 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] Time to upgrade Spotless... and maybe take advantage of the break?

2024-01-02 Thread Ian Turton 
Sounds good to me, not too bothered by which one we go with.

Ian

On Tue, 2 Jan 2024, 17:06 Andrea Aime, 
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
> .
> 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

[Geoserver-devel] GeoTools / GeoServer PMC meeting - 2024-01-02

2024-01-02 Thread Torben Barsballe 
Attending

   -

   Torben Barsballe
   -

   Andrea Aime
   -

   Peter Smythe
   -

   Jukka Rahkonen

Actions from prior meetings:

   -

   [DONE] Jody: Call for vote on GSIP 221, plan to update early Jan
   -

   [DONE] Andrea: warn people about Java 21 build requirements and start
   merging PRs. Also make a GWC 21 PR.

Agenda

   -

   2024 Roadmap blogpost is ready (planned for tomorrow)
   -

   GSIP 221 ready - votes requested
   -

   JIRA Licence limit
   -

   Wicket 9 upgrade
   -

   Spotless/Palantir upgrade
   -

   Some thoughts about JAI to ImageN upgrade


Actions

   -

   Andrea: Look into JIRA license limit
   -

   Brad: Give the OK on the Wicket 9 Upgrade


2024 Roadmap blogpost is ready (planned for tomorrow)

Blog post is ready:

https://github.com/geoserver/geoserver.github.io/pull/175 describing 2024
roadmap

Planned to merge and publish January 3

All looks ready to go. No further feedback needed
GSIP 221 ready - votes requested

GSIP is ready:

https://github.com/geoserver/geoserver/wiki/GSIP-221

We now have 5 votes, which is sufficient to pass. But still please vote if
you haven’t yet.

Example of outstanding work:

https://jodygarnett.github.io/geoserver/installation/docker/#adding-geoserver-extensions

JIRA Licence limit

We hit the JIRA Licence limit 5 days ago.

Manual clean-up has been the fix in the past, but is not really practical
long-term

We should consider migrating to github issues (eventually), but that will
be fairly involved, even with available automation.

Shorter term, can we contact Atlassian support to get our limit increased
slightly?

Jira has a feature request to handle this, still open
.

Action: Andrea will look into workarounds, no guarantees through…
Wicket 9 upgrade

https://github.com/geoserver/geoserver/pull/7154

Need to collect all pages and panels that need to be tested, make a list,
and divide the list amongst participants to the testing effort. First we
need Brad’s ok to move on.
Spotless/Palantir upgrade

Current status, Spotless and Google Java Format.

Using older version of them, that still support Java 8.

Example Geotools upgrade:
https://github.com/aaime/geotools/tree/spotless_upgrade

More examples in a geoserver-devel mail.

No objections during the meeting

Some discussion on workarounds to the git history pollution issue here:
https://gdal.org/development/rfc/rfc69_cplusplus_formatting.html#big-reformat

Some thoughts about JAI to ImageN upgrade

Part of the Jakarta EE upgrade plan
.

ImageN as it stands today
.

Some considerations and a plan here

.

Positive comments during the meeting.
___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

[Geoserver-devel] Time to upgrade Spotless... and maybe take advantage of the break?

2024-01-02 Thread Andrea Aime 
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
.
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
___
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)

2024-01-02 Thread Rahkonen Jukka 
+1

-Jukka Rahkonen-

Lähettäjä: Torben Barsballe 
Lähetetty: tiistai 2. tammikuuta 2024 4.30
Vastaanottaja: Jody Garnett 
Kopio: Geoserver-devel 
Aihe: Re: [Geoserver-devel] GSIP-221 mkdocs proposal (closing January 3rd)

+1

Cheers,
Torben

On Sun, Dec 31, 2023 at 12:11 PM Jody Garnett 
mailto:jody.garn...@gmail.com>> wrote:
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 
mailto:jody.garn...@gmail.com>> wrote:
I would like to make the following proposal:


  *   GSIP-222 mkdocs

Thanks to Krishna Lodha (rottengrapes.tech) for woking on this proposal with me.

Our policy 
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
___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel