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

Nicolas Roelandt roelandtn.pro at gmail.com
Wed Sep 12 01:39:51 PDT 2018


Hi all,

Thanks for the motion, Astrid.

I think there is 2 things going on:
- Monthly update of the website: +1 for me. I think we can automate the
process then manually deploy once a month, during a meeting for example.
Maybe we can ask more rights so that we don't depend only on Brian (thanks
to him)
- Version number: We didn't though about it and thanks for rising up the
concern. I'm more on a simpler version: 12.0.m as 12.0: number of current
iso and m: number of the current month (kinda like ubuntu versioning).

I think adding a language can wait for the next month. It is the same for
software, new translations waits for the next release.
So I propose we don't distinguish minor and / or  major changes, we just
update monthly our website.

For people who want to see their changes more often, as discussed on the
channel, I think we can deploy on github pages an automated build. Maybe a
daily or weekly one ? I think that waiting merging PR won't be efficient.
In an ideal world, we can even pick the latest archive for the ISO building
and the monthly update, with the right tags.

We will work on it with Vicky and when we'll have something working, no
need to stress it before we can do that.

Thanks for your comments.

Best,

Nicolas



Le mer. 12 sept. 2018 à 00:06, Ben Caradoc-Davies <ben at transient.nz> a
écrit :

> -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
> (12.0.1.1), and a new iso 12.1 is released with a different software
> version which makes the original documentation slightly out-of-date? Is
> this 12.1.1.1? Or 12.1.0.0? I am not sure that versioning helps.
>
> GeoTools once used a star system to communicate module/plugin quality:
> http://docs.geotools.org/latest/developer/procedures/check.html
>
> Kind regards,
> Ben.
>
> 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>
> Director
> Transient Software Limited <https://transient.nz/>
> New Zealand
> _______________________________________________
> osgeolive mailing list
> osgeolive at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/osgeolive
>


-- 
Bien cordialement,

Nicolas Roelandt
mail: roelandtn.pro at gmail.com
mobile: +33 (0)6 42 40 42 55
twitter: @*RoelandtN42* <https://twitter.com/RoelandtN42>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/osgeolive/attachments/20180912/ae360060/attachment-0001.html>


More information about the osgeolive mailing list