[OSGeoLive] Motion OSGeoLive monthly updating and versioning of the documentation

Ben Caradoc-Davies ben at transient.nz
Tue Sep 11 15:06:48 PDT 2018

-0. I think diverging from the iso versioning could be confusing.

We could leave the iso as 12.0, 12.1, or 12.5, and add extra terms for 
the documentation. But what happens if documentation is written for 
12.0, a new language is added (12.0.1), and some files are updated 
(, and a new iso 12.1 is released with a different software 
version which makes the original documentation slightly out-of-date? Is 
this Or I am not sure that versioning helps.

GeoTools once used a star system to communicate module/plugin quality:

Kind regards,

On 12/09/2018 07:49, Astrid Emde (OSGeo) wrote:
> Hello,
> while some of you left already we discussed 3. Translations update (at 
> 20:39:55)
> see irc log http://irclogs.geoapt.com/osgeolive/%23osgeolive.2018-09-10.log
> I will explain what we discussed and would like to make a motion at the 
> end.
> This would be the process:
> 1. Monthly update of the documentation files from transifex at 
> https://live.osgeo.org/en/index.html
> (reason: to encourage the translators to work on the translation. Else 
> they would have to wait till Version 13.0 in 1 year)
> 2. we would like to defined version numbers for the monthly updates f.e.
> * v12.0.1 -> more translations on existing languages (micros when more 
> files are translated)
> * v12.1.0 -> if a new language(s) is added (minors when a language has 
> completed overviews)
> Vicky and Bakaniko would work on the update of the documentation.
> Astrid could help if we write a press release / news about it.
> MOTION: OSGeoLive monthly updating and versioning of the documentation 
> in the above explained way
> Best Astrid

Ben Caradoc-Davies <ben at transient.nz>
Transient Software Limited <https://transient.nz/>
New Zealand

More information about the osgeolive mailing list