[GRASS-dev] Migration to git, use addons as test case?

[Vaclav Petras]

On Thu, Jan 24, 2019 at 3:12 AM Luca Delucchi <lucadeluge at gmail.com> wrote:

>
>
> On Tue, 22 Jan 2019 at 08:09, Stefan Blumentrath <
> Stefan.Blumentrath at nina.no> wrote:
>
>>
>> Just wondering, regarding migration to git, would it be helpful to use
>> AddOns (and possibly sandbox) as a test case?
>>
>>
> yes this could be a good idea,
>

There is couple of different workflows which could be used for Addons
besides one big repo considering what you can do with Git and Git hosting
platforms, e.g. submodules. It would be good to collect advantages and
disadvantages (e.g. on Trac wiki).

I'm not sure if sandbox is that interesting now, because on most platforms,
even the self-hosted, you will probably have the option of personal repos.

One thing to figure out with both of them is that with Subversion, we you
can just do `svn cp` to get data from one to the other when you promoting
or depreciating modules (sandbox->addons->core, core->addons) when you had
a checkout (svn checkout) of the whole repo (with grass, grass-addons,
...). One command, all history preserved. What would be a Git equivalent of
this?


> but first probably we have to choose which git platform to use. There are
> many possible options right now
>

There were discussions about this at osgeo-discuss and here probably as
well. If somebody would be willing to summarize it, it may help us to get
started. Point of view of occasional contributors would be quite helpful
here.

Thanks,
Vashek
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/grass-dev/attachments/20190124/4e1fc104/attachment.html>