If we are not worried about creating ‘proper’ GitHub/Zenodo sequential versioning for legacy versions of GRASS, we can simply submit each one as a release under its own repository or subdirectory of a repository. Then we could easily get DOI’s for each release.
MIchael
C. Michael Barton
Director, Center for Social Dynamics & Complexity
Director, Network for Computational Modeling in Social & Ecological Sciences
Associate Director, School of Complex Adaptive Systems
Professor, School of Human Evolution & Social Change
Arizona State University
Tempe, AZ 85287-2402
USA
voice: 480-965-6262 (SHESC), 480-965-8130/727-9746 (CSDC)
fax: 480-965-7671(SHESC), 480-727-0709 (CSDC)
www: http://shesc.asu.edu, https://complexity.asu.edu, http://www.public.asu.edu/~cmbarton
On May 31, 2021, at 1:10 PM, grass-dev-request@lists.osgeo.org wrote:
Date: Mon, 31 May 2021 15:25:16 -0400
From: Vaclav Petras <wenzeslaus@gmail.com>
To: grass-dev <grass-dev@lists.osgeo.org>
Subject: Re: [GRASS-dev] [release planning] Enable Zenodo before 7.8.6
and 8.0.0
Message-ID:
<CABo5uVu9uOFKw0cxCWcdjr+7KYXMPL1PwgwDbHQwqHF9VyJKnw@mail.gmail.com>
Content-Type: text/plain; charset=“utf-8”Dear all,
Zenodo-GitHub link is enabled. There is nothing to see or customize on
Zenodo.org until a release happens. It is important that every release is a
GitHub release rather than just a tag, but other than that, it will work
automatically.I won’t be creating .zenodo.json right away, but will probably wait until
7.8.6 or 8.0.alpha happens to see how good or bad the metadata is. Then we
will see what priority to assign to creating .zenodo.json.Best,
Vaclav