[GRASS-dev] Documentation (and translation) team for git?

[Stefan Blumentrath]

Hi Markus,

Yes, a pull request is indeed relatively straightforward.

However, my thought was, that if one aim of moving to git is to get more active contributors, having a low barrier "committer group" for documentation could help to get people involved that do not feel like coders (yet)...

Translating the documentation / manuals would be another thing to think about (though I don`t know how much interest there is for translation of manuals).

Cheers
stefan
________________________________
Fra: Markus Neteler <neteler at osgeo.org>
Sendt: søndag 10. mars 2019 21.32
Til: Stefan Blumentrath
Kopi: GRASS developers list
Emne: Re: [GRASS-dev] Documentation (and translation) team for git?

Hi,

On Sun, Mar 10, 2019 at 1:18 PM Stefan Blumentrath
<Stefan.Blumentrath at nina.no> wrote:
>
> Hi,
>
> In #3766, Nikos raised a relevant point about access to documentation.
>
> Would it be feasible to ease access for contributions to documentation in the process of moving to git?
>
> E.g. could we create a documentation team, whos members can contribute to html files?

.. with github (gitlab, ...) isn't that then as simple as opening a
pull request when it comes to modify existing manual pages?
Or do you think of something else?

> Or creating a translation team...?
>
> That would probably require different repos?

Perhaps rather with language branches for translated manual pages?

> No idea if it would be worth the effort... Just so this is considered (also as a later option).

More opinions are welcome.

Markus
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/grass-dev/attachments/20190310/75545b8e/attachment-0001.html>