[GRASS-dev] svn/trac -> git/github migration plan

[Stefan Blumentrath]

Hi,

Being no developer by education I can only second this!

Guidelines and simple, minimal example workflows would be very, very welcome (we learned fork->branch->commit->pull request (and then?, how do I keep my fork in sync, ...) ! I also agree that we should be vary of duplicating git documentation but rather have minimal description of recommended workflows, starting with the most common cases (which of course can evolve over time) and point to more lengthy explanations other places. Just like: https://trac.osgeo.org/grass/wiki/HowToSVN#SVNusage

git also has some pitfalls people should be aware of, like e.g. handling of line endings:
https://help.github.com/en/articles/dealing-with-line-endings
These can be pretty annoying, but circumvented if taken into account early on...

And then there are some more possible git adjustments (in the codebase), like proper markdown formating of the README as well as probably some stuff from here:
https://github.com/grass-svn2git/grass/community (yes, I am aware that this is not the final repo)

Thanks for the massive work, Martin (and others involved). Looking forward to GRASS on git!

Cheers
Stefan



Currently, I am struggling in another project with line endings which makes contributions across plattforms complicated...


-----Original Message-----
From: grass-dev <grass-dev-bounces at lists.osgeo.org> On Behalf Of Luca Delucchi
Sent: onsdag 15. mai 2019 22:21
To: Veronica Andreo <veroandreo at gmail.com>
Cc: Martin Landa <landa.martin at gmail.com>; grass-dev <grass-dev at lists.osgeo.org>
Subject: Re: [GRASS-dev] svn/trac -> git/github migration plan

On Wed, 15 May 2019 at 21:40, Veronica Andreo <veroandreo at gmail.com> wrote:
>
> Hi,
>

Hi,


>> Another thing is the need for new contributing guidelines. Git is not Subversion and committing to master won't work (please, let me know if you want me to show some examples).
>
>
> I am very interested in such examples, esp. how the workflow will be from now on for example when making a small change in manuals.
>

Yes, it is important to know this. How to use branches and also how to update local version from the master one. Should we use a private clone and make pull request to the main repository o use the main repository directly?

> I think it is very important that those of you more familiar with git and GitHub develop or show example workflows of how to contribute, backport (if that will be still called like that), and so on.
>

+1

> my 0.01 cent
> Vero
>

--
ciao
Luca

www.lucadelu.org
_______________________________________________
grass-dev mailing list
grass-dev at lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev