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? Or creating a translation team…?
That would probably require different repos?
No idea if it would be worth the effort… Just so this is considered (also as a later option).
Cheers,
Stefan
Hi,
On Sun, Mar 10, 2019 at 1:18 PM Stefan Blumentrath
<Stefan.Blumentrath@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
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@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@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