[GRASS-dev] grass-addons on github

[Vaclav Petras]

On Fri, May 24, 2019 at 2:48 AM Paulo van Breugel <p.vanbreugel at gmail.com>
wrote:

>
> Are we working with a central repository (OSGeo/grass-addons) and follow
> the same protocol as for OSGEO/grass. If so, who will be responsible for
> approving pull requests? An alternative more like the old situation is that
> authors will be able to directly commit to the addon repository.
>
> Or should add-on authors maintain their own repositories, and will there
> be a way to provide links to the authors repositories in a central place?
>
> With a central repository for all add-ons I guess it will be easier to
> maintain an overview like https://grass.osgeo.org/grass76/manuals/addons/
> and to create the windows binaries?
>


I think the first question to ask is if there are other reasons than
technical ones to have all* addons in one repo. Having it in one
(Subversion) repo meant that core devs can do general changes in all addons
at once if needed and that all people can contribute to any other addon
even when the original author doesn't make any changes anymore** to the
code. If the addons are individual repos, this would work only if
maintainers are given access to them, e.g. by transferring ownership to the
organization (which is what e.g. LANDIS-II seems to be doing [1]).


* Not all 3rd party modules are of course there, just those from authors
who choose to do that.
** Because of code was abandoned or the author simply does not have any
time.

[1] https://github.com/LANDIS-II-Foundation
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/grass-dev/attachments/20190524/74641889/attachment.html>