git migration

classic Classic list List threaded Threaded
41 messages Options
123
Reply | Threaded
Open this post in threaded view
|

Re: git migration: the Zenodo option

Markus Neteler
Hi Peter,

On Mon, Apr 1, 2019 at 9:35 AM "Peter Löwe" <[hidden email]> wrote:
>
> Hello PSC,
>
> before we actually venture into GitHub, I propose we should consider beforehand how the GRASS repo(s) *could* make use  of the Zenodo archive in the future, so we can set up things in a way that this option can be used (setting up of credentials, etc.). Zenodo is a open-access long term scientific archive (https://en.wikipedia.org/wiki/Zenodo), operated and maintained by CERN. The Zenodo software itself is also FOSS.
> Connecting repos on GitHub with Zenodo is easy: https://guides.github.com/activities/citable-code/
>
> IMHO we could use this mechanism to provide scientific citability and long term preservation for the old stable releases GRASS 4.x, 5.x and 6.x.

A very good idea.
Just curious: why is this needed to be done (?) *before* migrating to
GitHub? I'd rather get that done first, then put cool stuff on top.

Best
Markus
_______________________________________________
grass-psc mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/grass-psc
Reply | Threaded
Open this post in threaded view
|

Re: git migration

Martin Landa
In reply to this post by Anna Petrášová
Hi,

st 27. 3. 2019 v 14:30 odesílatel Anna Petrášová <[hidden email]> napsal:
>>> I opened a thread for discussion about labels and priorities for issues in the RFC, but there was not so much interest apparently [1]. I still believe that we should keep
>>> raster(3d), vector, temporal and so on as components. I think those are useful and make search easier. Modules is maybe too general, IMO.

right, modules are too generic.

* raster (everything raster related -> 2d, 3d, imagery)
* vector (everything vector related -> 2d, 3d)
* temporal

would be enough?

> I agree, although with raster, vector etc it's not quite clear if it should refer to modules or libraries or both. Also don't forget labels work differently than trac categories.
>
> I would also add 'Mac specific', (I don't think we need also Linux specific) and maybe just shorten it to 'MacOS' and 'Windows'.

Sound reasonable.

> Also I would add a label 'beginner'.

Why not :-) Ma

--
Martin Landa
http://geo.fsv.cvut.cz/gwiki/Landa
http://gismentors.cz/mentors/landa
_______________________________________________
grass-psc mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/grass-psc
Reply | Threaded
Open this post in threaded view
|

git migration: Zenodo optionS

"Peter Löwe"
In reply to this post by Markus Neteler
Hi Markus, hi list,

I was raising the Zenodo-topic, since this might strategically affect how we need to structure the GRASS repository / repositories on GitHub, so we can make the most out of Zenodo for scientific citation later.

Zenodo currenlty mints for EACH SINGLE GitHub-project which is checked in EXACTLY ONE persistent identifier ("unbreakable Web-link"), a Digital Object Identifier (DOI). DOI have become crucial for scientific citation and indirectly also for the careers of early career scientists (who need lots a citations to eventually get tenure/rich)

Whenever there's a new release of the project repo on GitHub, the corresponding repo- instance in Zenodo is updated accordingly and the DOI is also updated to a new version (note: it's the same DOI, NOT a new/different DOI). This compares to the update note on GRASS man pages ("Note: A new GRASS GIS stable version has been released: GRASS GIS 7.6, available here. Updated manual page: here").

In this manner we're dealing with two different flavours of DOI-based reference: 1.) The "overall" DOI for the archived (GRASS-)software repo and 2.) the continuously increased version/release numbers (e.g. citing "GRASS GIS" versus a particular release "GRASS 4.2.1"; "GRASS 5.3", "GRASS 7.4", etc.).

So from the Zenodo/DOI perspective need to consider (at least) two options for using GitHub:

a) We could _SPLIT_ the overall GRASS repo and create individual GitHub repos for each currently existing GRASS release, so each gets its own distinct DOI (this would allow for backports to be considered new (DOI)versions of the particular GRASS releases).

b) We keep __ONE__ GRASS project GUI, and get __ONE__ DOI for the greater GRASS project wich has LOTS of versions. Suggestion: We could start filling the repo (already linked with Zenodo) consecutively, beginning with the oldest archived GRASS releases, minting a DOI-version for each one. In this manner, each old GRASS release will receive it's own  distinct __version__ of the overall DOI. Things could get messy lateron, when backports to previous releases are made, which will also cause DOI version updates, but AFAIK there's no way yet to sort through all DOI versions (just) for a specific GRASS release.

We also should consider that Zenodo currently can't handle fine-grained DOI, to cite a particular GRASS module within a certain GRASS release. There's still a lot of development going on both in the DOI infrastructure and Zenodo, so this might come as a later step.

Another interesting aspect is the issue of ownership and due credit: Both the GRASS repo(s) on GitHub and the corresponding Zendo-archive(s) must have owners. This should be IMHO the "GRASS Development Team". Therefore the GRASS-related DOI(s) will be attributed to the GRASS Developer Team. We should think about a way, to link the ORCIDs of team members ("persitent identifiers for individual persons" https://orcid.org) to the GRASS DOI(s). This is not trivial (but innovative), but can be tackled later.  

best,
Peter

<[hidden email]>


> Gesendet: Montag, 01. April 2019 um 11:13 Uhr
> Von: "Markus Neteler" <[hidden email]>
> An: "Peter Löwe" <[hidden email]>
> Cc: GRASS-PSC <[hidden email]>
> Betreff: Re: git migration: the Zenodo option
>
> Hi Peter,
>
> On Mon, Apr 1, 2019 at 9:35 AM "Peter Löwe" <[hidden email]> wrote:
> >
> > Hello PSC,
> >
> > before we actually venture into GitHub, I propose we should consider beforehand how the GRASS repo(s) *could* make use  of the Zenodo archive in the future, so we can set up things in a way that this option can be used (setting up of credentials, etc.). Zenodo is a open-access long term scientific archive (https://en.wikipedia.org/wiki/Zenodo), operated and maintained by CERN. The Zenodo software itself is also FOSS.
> > Connecting repos on GitHub with Zenodo is easy: https://guides.github.com/activities/citable-code/
> >
> > IMHO we could use this mechanism to provide scientific citability and long term preservation for the old stable releases GRASS 4.x, 5.x and 6.x.
>
> A very good idea.
> Just curious: why is this needed to be done (?) *before* migrating to
> GitHub? I'd rather get that done first, then put cool stuff on top.
>
> Best
> Markus
>
_______________________________________________
grass-psc mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/grass-psc
Reply | Threaded
Open this post in threaded view
|

Re: git migration

Markus Neteler
In reply to this post by Markus Neteler
Hi PSC,

a months has passed since the publication of the draft

RFC 6: Migration from SVN to GitHub
https://trac.osgeo.org/grass/wiki/RFC/6_MigrationGitHub

Since then comments have been received and integrated into the document.

Let me suggest to come to a vote in the next days in order to move on
with the SVN to git migration.

I would also suggest to postpone
- label details in the issue tracker (can be done later)
- trac wiki migration (can be done later)
to a date after the git migration has been done, otherwise we remain stuck.

In a nutshell: RFC6 proposes to migrate to github under OSGeo
organization. It also proposes an exit strategy incl. to implement a
continuous mirror on GitLab.com.

Best
Markus
_______________________________________________
grass-psc mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/grass-psc
Reply | Threaded
Open this post in threaded view
|

Re: git migration

Martin Landa
Dear PSC,

ne 7. 4. 2019 v 22:02 odesílatel Markus Neteler <[hidden email]> napsal:
> Let me suggest to come to a vote in the next days in order to move on
> with the SVN to git migration.

agreed. We need to come with decision. Ma

--
Martin Landa
http://geo.fsv.cvut.cz/gwiki/Landa
http://gismentors.cz/mentors/landa
_______________________________________________
grass-psc mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/grass-psc
Reply | Threaded
Open this post in threaded view
|

Re: git migration

Moritz Lennert
In reply to this post by Markus Neteler
On 7/04/19 22:02, Markus Neteler wrote:

> Hi PSC,
>
> a months has passed since the publication of the draft
>
> RFC 6: Migration from SVN to GitHub
> https://trac.osgeo.org/grass/wiki/RFC/6_MigrationGitHub
>
> Since then comments have been received and integrated into the document.
>
> Let me suggest to come to a vote in the next days in order to move on
> with the SVN to git migration.

+1

>
> I would also suggest to postpone
> - label details in the issue tracker (can be done later)
> - trac wiki migration (can be done later)
> to a date after the git migration has been done, otherwise we remain stuck.

+1

Moritz
_______________________________________________
grass-psc mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/grass-psc
Reply | Threaded
Open this post in threaded view
|

Re: git migration

Anna Petrášová
+1

On Mon, Apr 8, 2019 at 4:49 AM Moritz Lennert <[hidden email]> wrote:
On 7/04/19 22:02, Markus Neteler wrote:
> Hi PSC,
>
> a months has passed since the publication of the draft
>
> RFC 6: Migration from SVN to GitHub
> https://trac.osgeo.org/grass/wiki/RFC/6_MigrationGitHub
>
> Since then comments have been received and integrated into the document.
>
> Let me suggest to come to a vote in the next days in order to move on
> with the SVN to git migration.

+1

>
> I would also suggest to postpone
> - label details in the issue tracker (can be done later)
> - trac wiki migration (can be done later)
> to a date after the git migration has been done, otherwise we remain stuck.

+1

Moritz
_______________________________________________
grass-psc mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/grass-psc

_______________________________________________
grass-psc mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/grass-psc
Reply | Threaded
Open this post in threaded view
|

Re: git migration

"Peter Löwe"
In reply to this post by Markus Neteler
Hi Markus, all,

> Gesendet: Sonntag, 07. April 2019 um 22:02 Uhr
> Von: "Markus Neteler" <[hidden email]>
> An: "GRASS PSC list" <[hidden email]>
> Betreff: Re: [GRASS-PSC] git migration
>
> Hi PSC,
>
> a months has passed since the publication of the draft
>
> RFC 6: Migration from SVN to GitHub
> https://trac.osgeo.org/grass/wiki/RFC/6_MigrationGitHub
>
> Since then comments have been received and integrated into the document.
>
> Let me suggest to come to a vote in the next days in order to move on
> with the SVN to git migration.
>

+ 1 (we should not forget about the Zenodo option)

> I would also suggest to postpone
> - label details in the issue tracker (can be done later)
> - trac wiki migration (can be done later)
> to a date after the git migration has been done, otherwise we remain stuck.

+ 1
> In a nutshell: RFC6 proposes to migrate to github under OSGeo
> organization. It also proposes an exit strategy incl. to implement a
> continuous mirror on GitLab.com.

+1

best
peter
_______________________________________________
grass-psc mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/grass-psc
Reply | Threaded
Open this post in threaded view
|

Re: git migration

Michael Barton
In reply to this post by Markus Neteler
1+ since we have an exit strategy if GitHub becomes too commercial.

Michael
____________________
C. Michael Barton
Director, Center for Social Dynamics & Complexity 
Professor of Anthropology, School of Human Evolution & Social Change
Head, Graduate Faculty in Complex Adaptive Systems Science
Arizona State University

voice:  480-965-6262 (SHESC), 480-965-8130/727-9746 (CSDC)
fax: 480-965-7671 (SHESC),  480-727-0709 (CSDC)















On Apr 7, 2019, at 10:02 PM, Markus Neteler <[hidden email]> wrote:

Hi PSC,

a months has passed since the publication of the draft

RFC 6: Migration from SVN to GitHub
https://urldefense.proofpoint.com/v2/url?u=https-3A__trac.osgeo.org_grass_wiki_RFC_6-5FMigrationGitHub&d=DwIGaQ&c=l45AxH-kUV29SRQusp9vYR0n1GycN4_2jInuKy6zbqQ&r=lk-7X7CEOMDN8GaGVhiDsuO6gEp1wbG6nfT1XEEEtR0&m=ZFdNItSY-vZfmG2phTQm2mCpnH0h8tQuydlwxNFLKdE&s=RMXSrcrPAxQCW4zlEAduHDzX8tPmxTYGs285jwEhBxI&e=

Since then comments have been received and integrated into the document.

Let me suggest to come to a vote in the next days in order to move on
with the SVN to git migration.

I would also suggest to postpone
- label details in the issue tracker (can be done later)
- trac wiki migration (can be done later)
to a date after the git migration has been done, otherwise we remain stuck.

In a nutshell: RFC6 proposes to migrate to github under OSGeo
organization. It also proposes an exit strategy incl. to implement a
continuous mirror on GitLab.com.

Best
Markus
_______________________________________________
grass-psc mailing list
[hidden email]
https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.osgeo.org_mailman_listinfo_grass-2Dpsc&d=DwIGaQ&c=l45AxH-kUV29SRQusp9vYR0n1GycN4_2jInuKy6zbqQ&r=lk-7X7CEOMDN8GaGVhiDsuO6gEp1wbG6nfT1XEEEtR0&m=ZFdNItSY-vZfmG2phTQm2mCpnH0h8tQuydlwxNFLKdE&s=CQ94SbB5oRwtrvm3W9x-qHu5p2b9IioFzwszzqJj-FU&e=


_______________________________________________
grass-psc mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/grass-psc
Reply | Threaded
Open this post in threaded view
|

Re: git migration

Martin Landa
Hi,

please be aware, this is not an official (clearly defined) vote thread.

Ma

út 9. 4. 2019 v 22:09 odesílatel Michael Barton <[hidden email]> napsal:

>
> 1+ since we have an exit strategy if GitHub becomes too commercial.
>
> Michael
> ____________________
> C. Michael Barton
> Director, Center for Social Dynamics & Complexity
> Professor of Anthropology, School of Human Evolution & Social Change
> Head, Graduate Faculty in Complex Adaptive Systems Science
> Arizona State University
>
> voice:  480-965-6262 (SHESC), 480-965-8130/727-9746 (CSDC)
> fax: 480-965-7671 (SHESC),  480-727-0709 (CSDC)
> www: http://www.public.asu.edu/~cmbarton, http://csdc.asu.edu
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> On Apr 7, 2019, at 10:02 PM, Markus Neteler <[hidden email]> wrote:
>
> Hi PSC,
>
> a months has passed since the publication of the draft
>
> RFC 6: Migration from SVN to GitHub
> https://urldefense.proofpoint.com/v2/url?u=https-3A__trac.osgeo.org_grass_wiki_RFC_6-5FMigrationGitHub&d=DwIGaQ&c=l45AxH-kUV29SRQusp9vYR0n1GycN4_2jInuKy6zbqQ&r=lk-7X7CEOMDN8GaGVhiDsuO6gEp1wbG6nfT1XEEEtR0&m=ZFdNItSY-vZfmG2phTQm2mCpnH0h8tQuydlwxNFLKdE&s=RMXSrcrPAxQCW4zlEAduHDzX8tPmxTYGs285jwEhBxI&e=
>
> Since then comments have been received and integrated into the document.
>
> Let me suggest to come to a vote in the next days in order to move on
> with the SVN to git migration.
>
> I would also suggest to postpone
> - label details in the issue tracker (can be done later)
> - trac wiki migration (can be done later)
> to a date after the git migration has been done, otherwise we remain stuck.
>
> In a nutshell: RFC6 proposes to migrate to github under OSGeo
> organization. It also proposes an exit strategy incl. to implement a
> continuous mirror on GitLab.com.
>
> Best
> Markus
> _______________________________________________
> grass-psc mailing list
> [hidden email]
> https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.osgeo.org_mailman_listinfo_grass-2Dpsc&d=DwIGaQ&c=l45AxH-kUV29SRQusp9vYR0n1GycN4_2jInuKy6zbqQ&r=lk-7X7CEOMDN8GaGVhiDsuO6gEp1wbG6nfT1XEEEtR0&m=ZFdNItSY-vZfmG2phTQm2mCpnH0h8tQuydlwxNFLKdE&s=CQ94SbB5oRwtrvm3W9x-qHu5p2b9IioFzwszzqJj-FU&e=
>
>
> _______________________________________________
> grass-psc mailing list
> [hidden email]
> https://lists.osgeo.org/mailman/listinfo/grass-psc



--
Martin Landa
http://geo.fsv.cvut.cz/gwiki/Landa
http://gismentors.cz/mentors/landa
_______________________________________________
grass-psc mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/grass-psc
Reply | Threaded
Open this post in threaded view
|

Re: git migration

Michael Barton
Just want to show my support
____________________
C. Michael Barton
Director, Center for Social Dynamics & Complexity 
Professor of Anthropology, School of Human Evolution & Social Change
Head, Graduate Faculty in Complex Adaptive Systems Science
Arizona State University

voice:  480-965-6262 (SHESC), 480-965-8130/727-9746 (CSDC)
fax: 480-965-7671 (SHESC),  480-727-0709 (CSDC)















On Apr 10, 2019, at 1:19 AM, Martin Landa <[hidden email]> wrote:

Hi,

please be aware, this is not an official (clearly defined) vote thread.

Ma

út 9. 4. 2019 v 22:09 odesílatel Michael Barton <[hidden email]> napsal:

1+ since we have an exit strategy if GitHub becomes too commercial.

Michael
____________________
C. Michael Barton
Director, Center for Social Dynamics & Complexity
Professor of Anthropology, School of Human Evolution & Social Change
Head, Graduate Faculty in Complex Adaptive Systems Science
Arizona State University

voice:  480-965-6262 (SHESC), 480-965-8130/727-9746 (CSDC)
fax: 480-965-7671 (SHESC),  480-727-0709 (CSDC)
www: https://urldefense.proofpoint.com/v2/url?u=http-3A__www.public.asu.edu_-7Ecmbarton&d=DwIFaQ&c=l45AxH-kUV29SRQusp9vYR0n1GycN4_2jInuKy6zbqQ&r=lk-7X7CEOMDN8GaGVhiDsuO6gEp1wbG6nfT1XEEEtR0&m=-H_szqKh1k7dCd-4e9E0gcrFLv6phnmrdJWT6dj8SoQ&s=fAjJRjCEB8IGBfdd5wjXviSg6Etw3szrZ83T9nAQW-w&e=, https://urldefense.proofpoint.com/v2/url?u=http-3A__csdc.asu.edu&d=DwIFaQ&c=l45AxH-kUV29SRQusp9vYR0n1GycN4_2jInuKy6zbqQ&r=lk-7X7CEOMDN8GaGVhiDsuO6gEp1wbG6nfT1XEEEtR0&m=-H_szqKh1k7dCd-4e9E0gcrFLv6phnmrdJWT6dj8SoQ&s=AgBVevrUG7y8FCr0huaHx5a8dhhyC9WC50ltoeLBvag&e=















On Apr 7, 2019, at 10:02 PM, Markus Neteler <[hidden email]> wrote:

Hi PSC,

a months has passed since the publication of the draft

RFC 6: Migration from SVN to GitHub
https://urldefense.proofpoint.com/v2/url?u=https-3A__trac.osgeo.org_grass_wiki_RFC_6-5FMigrationGitHub&d=DwIGaQ&c=l45AxH-kUV29SRQusp9vYR0n1GycN4_2jInuKy6zbqQ&r=lk-7X7CEOMDN8GaGVhiDsuO6gEp1wbG6nfT1XEEEtR0&m=ZFdNItSY-vZfmG2phTQm2mCpnH0h8tQuydlwxNFLKdE&s=RMXSrcrPAxQCW4zlEAduHDzX8tPmxTYGs285jwEhBxI&e=

Since then comments have been received and integrated into the document.

Let me suggest to come to a vote in the next days in order to move on
with the SVN to git migration.

I would also suggest to postpone
- label details in the issue tracker (can be done later)
- trac wiki migration (can be done later)
to a date after the git migration has been done, otherwise we remain stuck.

In a nutshell: RFC6 proposes to migrate to github under OSGeo
organization. It also proposes an exit strategy incl. to implement a
continuous mirror on GitLab.com.

Best
Markus
_______________________________________________
grass-psc mailing list
[hidden email]
https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.osgeo.org_mailman_listinfo_grass-2Dpsc&d=DwIGaQ&c=l45AxH-kUV29SRQusp9vYR0n1GycN4_2jInuKy6zbqQ&r=lk-7X7CEOMDN8GaGVhiDsuO6gEp1wbG6nfT1XEEEtR0&m=ZFdNItSY-vZfmG2phTQm2mCpnH0h8tQuydlwxNFLKdE&s=CQ94SbB5oRwtrvm3W9x-qHu5p2b9IioFzwszzqJj-FU&e=


_______________________________________________
grass-psc mailing list
[hidden email]
https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.osgeo.org_mailman_listinfo_grass-2Dpsc&d=DwIFaQ&c=l45AxH-kUV29SRQusp9vYR0n1GycN4_2jInuKy6zbqQ&r=lk-7X7CEOMDN8GaGVhiDsuO6gEp1wbG6nfT1XEEEtR0&m=-H_szqKh1k7dCd-4e9E0gcrFLv6phnmrdJWT6dj8SoQ&s=0jLvk6QHl6rlqTW6l3h_R3SLPh5TrhVJ6H_pZAGpC1I&e=



-- 
Martin Landa
https://urldefense.proofpoint.com/v2/url?u=http-3A__geo.fsv.cvut.cz_gwiki_Landa&d=DwIFaQ&c=l45AxH-kUV29SRQusp9vYR0n1GycN4_2jInuKy6zbqQ&r=lk-7X7CEOMDN8GaGVhiDsuO6gEp1wbG6nfT1XEEEtR0&m=-H_szqKh1k7dCd-4e9E0gcrFLv6phnmrdJWT6dj8SoQ&s=qBprM4aqB7-hm0PJT70il6OA22ZfsFaHcRsp_Layad8&e=
https://urldefense.proofpoint.com/v2/url?u=http-3A__gismentors.cz_mentors_landa&d=DwIFaQ&c=l45AxH-kUV29SRQusp9vYR0n1GycN4_2jInuKy6zbqQ&r=lk-7X7CEOMDN8GaGVhiDsuO6gEp1wbG6nfT1XEEEtR0&m=-H_szqKh1k7dCd-4e9E0gcrFLv6phnmrdJWT6dj8SoQ&s=RlroQK6rNCwVVva0sZsUhWofv7TbT1so1QE-vJgHU3I&e=


_______________________________________________
grass-psc mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/grass-psc
Reply | Threaded
Open this post in threaded view
|

Re: git migration

Martin Landa
Hi,

st 10. 4. 2019 v 9:29 odesílatel Michael Barton <[hidden email]> napsal:

> Just want to show my support

sure, thanks! Ma

--
Martin Landa
http://geo.fsv.cvut.cz/gwiki/Landa
http://gismentors.cz/mentors/landa
_______________________________________________
grass-psc mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/grass-psc
Reply | Threaded
Open this post in threaded view
|

Re: git migration

wenzeslaus
In reply to this post by Markus Neteler


On Sun, Apr 7, 2019 at 4:02 PM Markus Neteler <[hidden email]> wrote:

RFC 6: Migration from SVN to GitHub
https://trac.osgeo.org/grass/wiki/RFC/6_MigrationGitHub

Looks great. Thanks!

One thing it lacks are best practices for using Git. Git is not Subversion and we just can't use it as Subversion. Specific difference are the automatic merge commits due to un-synchronous nature of Git. Do we want to avoid those (git pull --rebase)? [Discussion for grass-dev ML]

It also proposes an exit strategy incl. to implement a
continuous mirror on GitLab.com.

How realistic is the continuous mirror? I know GitLab has migration tools, but does it have sync as well?

_______________________________________________
grass-psc mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/grass-psc
Reply | Threaded
Open this post in threaded view
|

Re: git migration

Markus Neteler
On Wed, Apr 10, 2019 at 4:58 PM Vaclav Petras <[hidden email]> wrote:
> On Sun, Apr 7, 2019 at 4:02 PM Markus Neteler <[hidden email]> wrote:
>>
>>
>> RFC 6: Migration from SVN to GitHub
>> https://trac.osgeo.org/grass/wiki/RFC/6_MigrationGitHub
>
> Looks great. Thanks!
>
> One thing it lacks are best practices for using Git. Git is not Subversion and we just can't use it as Subversion.

Please suggest a text snippet to add there (or add directly).

> Specific difference are the automatic merge commits due to un-synchronous nature of Git. Do we want to avoid those (git pull --rebase)? [Discussion for grass-dev ML]

Yes, let's discuss there.
Even recently gave some insights into a git bot for backports which
sounds very interesting.
But: grass-dev is the place to talk about it.

>> It also proposes an exit strategy incl. to implement a
>> continuous mirror on GitLab.com.
>
> How realistic is the continuous mirror? I know GitLab has migration tools, but does it have sync as well?

https://docs.gitlab.com/ee/workflow/repository_mirroring.html
"
Repository mirroring allows for mirroring of repositories to and from
external sources. It can be used to mirror branches, tags, and commits
between repositories.
A repository mirror at GitLab will be updated automatically. You can
also manually trigger an update at most once every 5 minutes.
"

... looks fine.

Markus
_______________________________________________
grass-psc mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/grass-psc
Reply | Threaded
Open this post in threaded view
|

Re: git migration: the Zenodo option

Markus Neteler
In reply to this post by Markus Neteler
On Mon, Apr 1, 2019 at 11:13 AM Markus Neteler <[hidden email]> wrote:

>
> Hi Peter,
>
> On Mon, Apr 1, 2019 at 9:35 AM "Peter Löwe" <[hidden email]> wrote:
> >
> > Hello PSC,
> >
> > before we actually venture into GitHub, I propose we should consider beforehand how the GRASS repo(s) *could* make use  of the Zenodo archive in the future, so we can set up things in a way that this option can be used (setting up of credentials, etc.). Zenodo is a open-access long term scientific archive (https://en.wikipedia.org/wiki/Zenodo), operated and maintained by CERN. The Zenodo software itself is also FOSS.
> > Connecting repos on GitHub with Zenodo is easy: https://guides.github.com/activities/citable-code/
> >
> > IMHO we could use this mechanism to provide scientific citability and long term preservation for the old stable releases GRASS 4.x, 5.x and 6.x.
>
> A very good idea.
> Just curious: why is this needed to be done (?) *before* migrating to
> GitHub?

... still an open question...

> I'd rather get that done first, then put cool stuff on top.

In any case, I have added it to

https://trac.osgeo.org/grass/wiki/GitMigration#FutureplansnotbeingpartofthisRFC

Best,
Markus
_______________________________________________
grass-psc mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/grass-psc
Reply | Threaded
Open this post in threaded view
|

git migration: Zenodo and versioned DOI for GRASS releases

"Peter Löwe"
Hi Markus, hi PSC,

the reason why I believe we should consider the Zenodo option (for long term archiving and DOI-based scientific recognition/citation) before making the switch to GitHub is the DOI versioning capability of Zenodo (https://blog.zenodo.org/2017/05/30/doi-versioning-launched/). This is similar to the mechanism implented for the GRASS module manual pages, where references from outdated versions point to the current release of the module (and man page). The DOI-versioning mechanism in Zenodo additionally implements a version history as a hsitorical sequence of releases. This means that the DOI version for GRASS 4.2.1 predates GRASS 4.3, which predates GRASS5.x, etc. etc. and all also point to the latest release.

The GRASS SVN contains the release branches dating back to GRASS 5. In addition there are tarballs from the GRASS 4.x era (-> what about GRASS 3.x or earlier ?).

Making all these releases available for scientific citation (and recognition) through one versioned DOI in the described "timely sequence" is a more complex task than what's covered in the how-to guides for GitHub-Zenodo-integration (https://genr.eu/wp/cite/).

I've contacted the Zenodo helpdesk for advice how this should be approached and will report back ASAP.

It would be a pity (and waste of ressources) if we make the effort to create a GitHub repo for GRASS once and then having to redo it because of some pecularities of the DOI-versioning mechanism.

best,
peter
   

<[hidden email]>


> Gesendet: Samstag, 13. April 2019 um 22:35 Uhr
> Von: "Markus Neteler" <[hidden email]>
> An: "Peter Löwe" <[hidden email]>
> Cc: GRASS-PSC <[hidden email]>
> Betreff: Re: git migration: the Zenodo option
>
> On Mon, Apr 1, 2019 at 11:13 AM Markus Neteler <[hidden email]> wrote:
> >
> > Hi Peter,
> >
> > On Mon, Apr 1, 2019 at 9:35 AM "Peter Löwe" <[hidden email]> wrote:
> > >
> > > Hello PSC,
> > >
> > > before we actually venture into GitHub, I propose we should consider beforehand how the GRASS repo(s) *could* make use  of the Zenodo archive in the future, so we can set up things in a way that this option can be used (setting up of credentials, etc.). Zenodo is a open-access long term scientific archive (https://en.wikipedia.org/wiki/Zenodo), operated and maintained by CERN. The Zenodo software itself is also FOSS.
> > > Connecting repos on GitHub with Zenodo is easy: https://guides.github.com/activities/citable-code/
> > >
> > > IMHO we could use this mechanism to provide scientific citability and long term preservation for the old stable releases GRASS 4.x, 5.x and 6.x.
> >
> > A very good idea.
> > Just curious: why is this needed to be done (?) *before* migrating to
> > GitHub?
>
> ... still an open question...
>
> > I'd rather get that done first, then put cool stuff on top.
>
> In any case, I have added it to
>
> https://trac.osgeo.org/grass/wiki/GitMigration#FutureplansnotbeingpartofthisRFC
>
> Best,
> Markus
>
_______________________________________________
grass-psc mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/grass-psc
Reply | Threaded
Open this post in threaded view
|

Re: git migration: Zenodo and versioned DOI for GRASS releases

Markus Neteler
Hi Peter,


"Peter Löwe" <[hidden email]> schrieb am Mi., 17. Apr. 2019, 12:15:
Hi Markus, hi PSC,

the reason why I believe we should consider the Zenodo option (for long term archiving and DOI-based scientific recognition/citation) before making the switch to GitHub is the DOI versioning capability of Zenodo (https://blog.zenodo.org/2017/05/30/doi-versioning-launched/). This is similar to the mechanism implented for the GRASS module manual pages, where references from outdated versions point to the current release of the module (and man page). The DOI-versioning mechanism in Zenodo additionally implements a version history as a hsitorical sequence of releases. This means that the DOI version for GRASS 4.2.1 predates GRASS 4.3, which predates GRASS5.x, etc. etc. and all also point to the latest release.


Yes: each release is a point in time.

The GRASS SVN contains the release branches dating back to GRASS 5. In addition there are tarballs from the GRASS 4.x era (-> what about GRASS 3.x or earlier ?).

Please check our work already done:
I have reconstructed the releases back to 3.2 including time stamps at file level.



Note that the URL will change to OSGeo organization soon.


Making all these releases available for scientific citation (and recognition) through one versioned DOI in the described "timely sequence" is a more complex task than what's covered in the how-to guides for GitHub-Zenodo-integration (https://genr.eu/wp/cite/).

We have all branches there, since 1987.


I've contacted the Zenodo helpdesk for advice how this should be approached and will report back ASAP.

It would be a pity (and waste of ressources) if we make the effort to create a GitHub repo for GRASS once and then having to redo it because of some pecularities of the DOI-versioning mechanism.


Still I don't see why we should redo it.
Does the new structure not address it?
Did you check it?

Best,
Markus

_______________________________________________
grass-psc mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/grass-psc
Reply | Threaded
Open this post in threaded view
|

Re: git migration: Zenodo and versioned DOI for GRASS releases

Martin Landa
Hi,

st 17. 4. 2019 v 16:29 odesílatel Markus Neteler <[hidden email]> napsal:
> Please check our work already done:
> I have reconstructed the releases back to 3.2 including time stamps at file level.
>
>
> https://github.com/grass-svn2git/grass-legacy

note that this repo lack releases [0] (=git tags). This need to be
fixed. Compare with grass repo [1]. Ma

[0] https://github.com/grass-svn2git/grass-legacy/releases
[1] https://github.com/grass-svn2git/grass/releases

--
Martin Landa
http://geo.fsv.cvut.cz/gwiki/Landa
http://gismentors.cz/mentors/landa
_______________________________________________
grass-psc mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/grass-psc
Reply | Threaded
Open this post in threaded view
|

Re: git migration: Zenodo and versioned DOI for GRASS releases

Markus Neteler
On Wed, Apr 17, 2019 at 7:53 PM Martin Landa <[hidden email]> wrote:
> st 17. 4. 2019 v 16:29 odesílatel Markus Neteler <[hidden email]> napsal:
> > Please check our work already done:
> > I have reconstructed the releases back to 3.2 including time stamps at file level.
> >
> >
> > https://github.com/grass-svn2git/grass-legacy
>
> note that this repo lack releases [0] (=git tags). This need to be
> fixed.

Good point.
Fixed.

> Compare with grass repo [1]. Ma
>
> [0] https://github.com/grass-svn2git/grass-legacy/releases
> [1] https://github.com/grass-svn2git/grass/releases

Enjoy the "new" branches
https://github.com/grass-svn2git/grass-legacy/branches
and releases
https://github.com/grass-svn2git/grass-legacy/releases

cheers
Markus

--
Markus Neteler, PhD
https://www.mundialis.de - free data with free software
https://grass.osgeo.org
https://courses.neteler.org/blog
_______________________________________________
grass-psc mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/grass-psc
Reply | Threaded
Open this post in threaded view
|

Re: git migration

wenzeslaus
In reply to this post by Markus Neteler


On Thu, Apr 11, 2019 at 4:40 PM Markus Neteler <[hidden email]> wrote:
On Wed, Apr 10, 2019 at 4:58 PM Vaclav Petras <[hidden email]> wrote:
> On Sun, Apr 7, 2019 at 4:02 PM Markus Neteler <[hidden email]> wrote:
>>
>>
>> RFC 6: Migration from SVN to GitHub
>> https://trac.osgeo.org/grass/wiki/RFC/6_MigrationGitHub
>
> Looks great. Thanks!
>
> One thing it lacks are best practices for using Git. Git is not Subversion and we just can't use it as Subversion.

Please suggest a text snippet to add there (or add directly).

Added.
 
>> It also proposes an exit strategy incl. to implement a
>> continuous mirror on GitLab.com.
>
> How realistic is the continuous mirror? I know GitLab has migration tools, but does it have sync as well?

https://docs.gitlab.com/ee/workflow/repository_mirroring.html
"
Repository mirroring allows for mirroring of repositories to and from
external sources. It can be used to mirror branches, tags, and commits
between repositories.
A repository mirror at GitLab will be updated automatically. You can
also manually trigger an update at most once every 5 minutes.
"

... looks fine.

The mirroring covers only the code, but not the issues which we are also migrating. The migration does cover them, but the problem is the guarantee of being able to do the migration when needed. A periodical backup from GitHub would be probably fine.


_______________________________________________
grass-psc mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/grass-psc
123