On Mon, May 31, 2021 at 4:10 PM Markus Neteler wrote:
>
> ... unless we modify g.extension for now to continue to read from
> "grass-addons/grass7/"...
>
> Opinions?
>
+1 for "grass-addons/grass7/". Confusing for those who see the URL, but
good enough for now.
I started the transition for addon
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
_
On Mon, May 31, 2021 at 9:13 PM Markus Neteler wrote:
>
> Hi devs,
>
> First step done:
> GRASS GIS 8.0 changes in master
> (https://github.com/OSGeo/grass/pull/1597) are merged!
One problem to address soon is the absence of "grass8" in the Addons
repo, leading to errors in the CI and all related
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 wil
Peter,
On Tue, May 25, 2021 at 8:30 AM Peter Löwe wrote:
>
> The MOSS project minted its first DOI as a proof concept in the process of
> becoming a OSGeo heritage project (
> https://zenodo.org/record/4719685#.YKzpGKgzaUk). For this, we
> used stakeholders roles according to MARC21 like the R p
Hi devs,
First step done:
GRASS GIS 8.0 changes in master
(https://github.com/OSGeo/grass/pull/1597) are merged!
Next step: test compilation and soonish create a "throw-away"
8.0.0alpha branch for testing.
cheers,
Markus
___
grass-dev mailing list
gras
