Re: [Geoserver-devel] mkdocs updates and before/after

[Jody Garnett]

Thanks for asking,

I would like to ask people to check new pages so I can have a lot of
content to work on and detect the same kind of problems occurring multiple
times.

If there was a page previously reported with errors I will mark it fixed
when I have addressed the problem.



If I marked a page you reviewed a fixed, you are welcome to go back and see
how it turned out of course.
As time goes on checking each page will be faster and faster, as I learn
how to automate more fixes.
--
Jody Garnett


On Feb 28, 2024 at 9:56:24 PM, Alexandre Gacon 
wrote:

> Hello Jody,
>
> Do you want reviewers to check again pages with errors after some changes
> of your own or should we focus on reviewing more pages?
>
> Regards
> Alexandre
>
> Le mer. 28 févr. 2024 à 08:22, Jody Garnett  a
> écrit :
>
>> Good evening GeoServer community,
>>
>> To start out with I would like to thank everyone who has signed up and
>> tested a few pages:
>>
>>- Alexandre Gacon
>>- Peter Smythe
>>- Andrea Aime
>>- GeoSpatial Techno
>>- Marcus Lingenfelder
>>
>>
>> With their help we about 1/4 of the way through reviewing the pages:
>>
>>- We identified a consistent problem with complicated tabes not
>>rendering (tables with. Nested notes and figures), these are now processed
>>into definition lists.
>>
>>
>> https://jodygarnett.github.io/geoserver/data/raster/imagemosaic/configuration/#primary-configuration-file
>>- Definition lists are styled to look like tables (see what I did
>>there!) which works out great for documenting step by step instructions
>>where field entry is needed.
>>https://jodygarnett.github.io/geoserver/
>>- Examples that change based on version and release are correct (big
>>improvement, you can now cut and paste command line examples):
>>https://jodygarnett.github.io/geoserver/installation/docker/
>>- The download, download extension and download community modules
>>external links look good (we can give it the nice appearance like the
>>docker page later):
>>
>>https://jodygarnett.github.io/geoserver/extensions/geopkg-output/install/
>>
>>
>> While I think we are through the big problems I still need to ask for
>> your help:
>>
>>
>>1. I would like to ask 10 volunteers
>>2. If everyone can review 30 pages each we will be done
>>3. Lots of pages can be reviewed in under 1-2 mins:
>>- locate a row that "needs review"
>>- click on the "origional" link and open in an other tab
>>- click on the "migrated" link and open in an other tab
>>4. Swap between the pages to check
>>5. If they are the same (no content is lost), update the review
>>column to be done
>>6. If they are different change "needs review" to describing what is
>>different:
>>- many pages will have "block quotes" when none were intended (this
>>is something we need to fix by hand before conversion)
>>
>>
>> *Popular request BEFORE / AFTER *
>>
>> Reviewers asked to "see the markdown" that was generated.
>>
>>- Each page has a view source button at the top showing the generated
>>markdown
>>- Links to both the original rst and generated md are now available
>>in the review spreadsheet
>>
>>
>> *Sign up sheet*
>>
>> I am going to be focused on the 2.25-RC release candidate this week; but
>> I would like to check back next week with a list of things to fix.
>>
>> The sign up spreadsheet is here: mkdocs review
>> 
>>  (open
>> spreadsheet and ask for edit access).
>>
>> Please reply if you have any questions - I appreciate your help.
>>
>> Thanks to my employer, and GeoCat Live product, for the opportunity to
>> work on this activity.
>> --
>> Jody Garnett
>> ___
>> Geoserver-devel mailing list
>> Geoserver-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>>
>
>
> --
> Alexandre Gacon
>
___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Re: [Geoserver-devel] mkdocs updates and before/after

[Alexandre Gacon]

Hello Jody,

Do you want reviewers to check again pages with errors after some changes
of your own or should we focus on reviewing more pages?

Regards
Alexandre

Le mer. 28 févr. 2024 à 08:22, Jody Garnett  a
écrit :

> Good evening GeoServer community,
>
> To start out with I would like to thank everyone who has signed up and
> tested a few pages:
>
>- Alexandre Gacon
>- Peter Smythe
>- Andrea Aime
>- GeoSpatial Techno
>- Marcus Lingenfelder
>
>
> With their help we about 1/4 of the way through reviewing the pages:
>
>- We identified a consistent problem with complicated tabes not
>rendering (tables with. Nested notes and figures), these are now processed
>into definition lists.
>
>
> https://jodygarnett.github.io/geoserver/data/raster/imagemosaic/configuration/#primary-configuration-file
>- Definition lists are styled to look like tables (see what I did
>there!) which works out great for documenting step by step instructions
>where field entry is needed.
>https://jodygarnett.github.io/geoserver/
>- Examples that change based on version and release are correct (big
>improvement, you can now cut and paste command line examples):
>https://jodygarnett.github.io/geoserver/installation/docker/
>- The download, download extension and download community modules
>external links look good (we can give it the nice appearance like the
>docker page later):
>
>https://jodygarnett.github.io/geoserver/extensions/geopkg-output/install/
>
>
> While I think we are through the big problems I still need to ask for your
> help:
>
>
>1. I would like to ask 10 volunteers
>2. If everyone can review 30 pages each we will be done
>3. Lots of pages can be reviewed in under 1-2 mins:
>- locate a row that "needs review"
>- click on the "origional" link and open in an other tab
>- click on the "migrated" link and open in an other tab
>4. Swap between the pages to check
>5. If they are the same (no content is lost), update the review column
>to be done
>6. If they are different change "needs review" to describing what is
>different:
>- many pages will have "block quotes" when none were intended (this is
>something we need to fix by hand before conversion)
>
>
> *Popular request BEFORE / AFTER *
>
> Reviewers asked to "see the markdown" that was generated.
>
>- Each page has a view source button at the top showing the generated
>markdown
>- Links to both the original rst and generated md are now available in
>the review spreadsheet
>
>
> *Sign up sheet*
>
> I am going to be focused on the 2.25-RC release candidate this week; but I
> would like to check back next week with a list of things to fix.
>
> The sign up spreadsheet is here: mkdocs review
> 
>  (open
> spreadsheet and ask for edit access).
>
> Please reply if you have any questions - I appreciate your help.
>
> Thanks to my employer, and GeoCat Live product, for the opportunity to
> work on this activity.
> --
> Jody Garnett
> ___
> Geoserver-devel mailing list
> Geoserver-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>


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

Re: [Geoserver-devel] GeoServer 2.25-RC0 PR roundup

[Jody Garnett]

 I will be merging the RST changes on the PR ahead of the 2.25-RC this week:


   - 7429 [GEOS-11221] mkdocs preflight rst fixes
   


These changes are all formatting to make content migration easier. In some
cases they are fixing broken links (to OGC standards that have changed or
dead Wikipedia pages).
Can I ask for a review please.
--
Jody Garnett


On Feb 27, 2024 at 3:26:12 PM, Jody Garnett  wrote:

> I have a small PR for this weeks release-candidate:
>
>
>- https://github.com/geoserver/geoserver/pull/7444
>- https://osgeo-org.atlassian.net/browse/GEOS-10438
>
>
> This changes the default behaviour entity resolution allow list, something
> I have  been intended to do for several release cycles now.
> --
> Jody Garnett
>
___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel