Re: [Geoserver-devel] 2024 roadmap - wiki pages

[Jody Garnett]

Thanks Peter for getting organized (my brain is fuzzy from doing regular
expressions for several weeks).

Here is a google spreadsheet which people can contribute to (just ask for
access to edit). That way we can avoid multiple people checking the same
page (and we can also know when we are done).

https://docs.google.com/spreadsheets/d/1HMqUpTirEwwSQfeNYikPjU0aFMl0-W4Xj44cg8V_VJA/edit?usp=sharing

There are instructions on that spreadsheet for how to sign up (first tab),
and how to record problems (second tab), and provide feedback (third tab).

Have a look, and request edit access to volunteer.
--
Jody Garnett


On Thu, Feb 22, 2024 at 7:56 AM Peter Smythe  wrote:

> Good day GeoServer users
>
> Here's a quick update to the effort coordination for the 2024 roadmap.
> Thank you to the few individuals who have responded with offers of
> assistance.
>
> The 9 tasks have been broken up into individual wiki pages, all linked
> from
> https://github.com/geoserver/geoserver/wiki/Maintenance-%26-Roadmap#2024-roadmap
> .
> Please take a look at them, see which ones interest you and your company
> the most, and put your name down to assist**
>
> One current task that I would like to highlight is the effort by Jody
> (GeoCat) to migrate all the brilliant GeoServer documentation (that you
> reference every week!) from sphinx to mkdocs:
> https://github.com/geoserver/geoserver/wiki/Migrate-documentation-to-mkdocs
> 
>
> He has now asked for users to compare the old documentation to the new
> documentation (preview found here:
> https://jodygarnett.github.io/geoserver/
> )
> and to let us know if there are any glaring issues, like broken links or
> elements that are not properly rendered.  He has done a fantastic job so
> far of automating the migration, but *we need your eyes on the new
> documentation*, please, for the final acceptance.
>
> *This is something that you can all get involved in!*
>
> ** How to make a wiki edit
> Hmm, we're working on that.  For now, please just reply by email with your
> offer to help.
>
> ** How to report an issue with mkdocs
> If you have a GitHub account, make a detailed comment in the pull request:
> https://github.com/geoserver/geoserver/pull/7429
> 
> If you don't have a GitHub account, we would love you to make one, so that
> you can contribute more easily: https://github.com/signup
> 
> (3 minutes, plus it is visually fun!)
> If you really don't want to sign up, you can reply publically (preferably
> not privately) and I will capture your feedback in the pull request for you.
>
> Thanks for your time!
>
> Peter
>
> GeoServer PSC
> AWS Solutions Architect
> https://github.com/petersmythe
> 
>
>
> On Thu, 11 Jan 2024 at 09:37, Peter Smythe  wrote:
>
>> Good day GeoServer users
>>
>> Happy new year an

[Geoserver-devel] 2024 roadmap - wiki pages

[Peter Smythe]

Good day GeoServer users

Here's a quick update to the effort coordination for the 2024 roadmap.
Thank you to the few individuals who have responded with offers of
assistance.

The 9 tasks have been broken up into individual wiki pages, all linked from
https://github.com/geoserver/geoserver/wiki/Maintenance-%26-Roadmap#2024-roadmap.
Please take a look at them, see which ones interest you and your company
the most, and put your name down to assist**

One current task that I would like to highlight is the effort by Jody
(GeoCat) to migrate all the brilliant GeoServer documentation (that you
reference every week!) from sphinx to mkdocs:
https://github.com/geoserver/geoserver/wiki/Migrate-documentation-to-mkdocs

He has now asked for users to compare the old documentation to the new
documentation (preview found here: https://jodygarnett.github.io/geoserver/)
and to let us know if there are any glaring issues, like broken links or
elements that are not properly rendered.  He has done a fantastic job so
far of automating the migration, but *we need your eyes on the new
documentation*, please, for the final acceptance.

*This is something that you can all get involved in!*

** How to make a wiki edit
Hmm, we're working on that.  For now, please just reply by email with your
offer to help.

** How to report an issue with mkdocs
If you have a GitHub account, make a detailed comment in the pull request:
https://github.com/geoserver/geoserver/pull/7429
If you don't have a GitHub account, we would love you to make one, so that
you can contribute more easily: https://github.com/signup (3 minutes, plus
it is visually fun!)
If you really don't want to sign up, you can reply publically (preferably
not privately) and I will capture your feedback in the pull request for you.

Thanks for your time!

Peter

GeoServer PSC
AWS Solutions Architect
https://github.com/petersmythe


On Thu, 11 Jan 2024 at 09:37, Peter Smythe  wrote:

> Good day GeoServer users
>
> Happy new year and welcome to 2024 from the GeoServer team!
>
> I wonder how many of you keep an eye on the GeoServer blog
> ?
>
> This year the Project Steering Committee has put a lot of effort into
> documenting the plans for 2024 as there are a lot of technology upgrades
> that must be made: spring-framework 6, spring-security 6, wicket 10,
> JakartaEE, Java 17, ImageN, the list is very long ...
>
> Please take  a few minutes to read Jody's detailed post, so that you know
> what help we need:
> https://geoserver.org/behind%20the%20scenes/2024/01/03/roadmap.html
>
> If you're not a developer, don't worry! We need testers - users like you
> who are familiar with GeoServer's GUI and functionality. We would love you
> to reply to this email with an offer to help.
>
> Oh, and we're fund raising too - please read that section too, and make a
> request to your company's finance department.
>
> Here's to an extra successful GeoServer community in 2024!
>
> Peter
>

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