from:"Peter Löwe"

Re: [GRASS-dev] [release planning] GRASS GIS 8.3.2

2024-03-14 Thread Peter Löwe via grass-dev

Hi Markus, all,

good news: 
Zenodo just fixed the issue for GRASS (an error on their side): 
https://zenodo.org/records/10817962

Best,
Peter




> Gesendet: Dienstag, 12. März 2024 um 18:23 Uhr
> Von: "Markus Neteler" 
> An: "Peter Löwe" 
> Cc: "GRASS developers list" 
> Betreff: Re: [GRASS-dev] [release planning] GRASS GIS 8.3.2
>
> Hi Peter, all,
> 
> So GRASS GIS 8.3.2 has been published and no trace of it in Zenodo:
> 
> https://zenodo.org/records/10685321
> 
> The GitHub-Zenodo bridge seems to be unstable?
> 
> Ideas welcome,
> Markus
>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [release planning] GRASS GIS 8.3.2

2024-03-12 Thread Peter Löwe via grass-dev

Hi Markus, all,

sorry to hear about this fuss. I will contact Zenodo asap.

On the bright side, this is another proof of the (frustrating) service quality 
hickups we encounter. 

EGU has invited me to talk about these issues in April and I will use this 
opportunity to demonstrate our case.
https://doi.org/10.5194/egusphere-egu24-6254.  

Best,
Peter




> Gesendet: Dienstag, 12. März 2024 um 18:23 Uhr
> Von: "Markus Neteler" 
> An: "Peter Löwe" 
> Cc: "GRASS developers list" 
> Betreff: Re: [GRASS-dev] [release planning] GRASS GIS 8.3.2
>
> Hi Peter, all,
> 
> So GRASS GIS 8.3.2 has been published and no trace of it in Zenodo:
> 
> https://zenodo.org/records/10685321
> 
> The GitHub-Zenodo bridge seems to be unstable?
> 
> Ideas welcome,
> Markus
>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] Stuck version DOI registration for 8.3.2. RC1: Feedback from Zenodo

2024-02-29 Thread Peter Löwe via grass-dev

Hi all,

here's feedback from Zenodo about the "stuck" version DOI registration for 
8.3.2. RC1:

"With these events it is often minor, unnoticeable, downtimes which prevents 
events from being sent or received which results in these failures.
In order to fix it we have to kickstart the DataCite DOI registration process 
again.
Hopefully we can do a better job catching these issues in the future, but in 
the meantime letting us know through support is ideal".

So there is nothing wrong with the current GitHub/Zenodo-bridge workflow :-)

Best,
Peter



___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [release planning] GRASS GIS 8.3.2

2024-02-29 Thread Peter Löwe via grass-dev

Hi Markus, all,

the friendly people at Zenodo fixed the issue: 
https://doi.org/10.5281/zenodo.10685321 now resolves to the GRASS GIS 8.3.2RC1 
codebase (timestamp: Feb 20 2024).

I have asked them for forensics/reasons why the issue occured and will report 
back once I get a response. 

Congratulations to this new version DOI for GRASS GIS !


Best,
Peter




> Gesendet: Montag, 26. Februar 2024 um 21:34 Uhr
> Von: "Markus Neteler" 
> An: "Peter Löwe" 
> Cc: "GRASS developers list" 
> Betreff: Re: Re: [GRASS-dev] [release planning] GRASS GIS 8.3.2
>
> Hi Peter,
> 
> On Sun, Feb 25, 2024 at 12:20 AM Peter Löwe  wrote:
> >
> > Markus, all,
> >
> > minting a DOI should take minutes/seconds, not days.
> >
> > Can more in depth info / metadata about the particular transaction be 
> > provided, which states that "https://doi.org/10.5281/zenodo.10685321; 
> > should be the new version DOI for GRASS GIS 8.3.2RC1 ?
> 
> Sure:
> 
> Version 8.3.2RC1: https://zenodo.org/records/10685321
> --> see left side
>--> DOI: https://doi.org/10.5281/zenodo.10685321
>  ---> still missing while advertised on the Zenodo page.
> 
> Not sure how that could happen?
> 
> Best,
> Markus
>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [release planning] GRASS GIS 8.3.2

2024-02-24 Thread Peter Löwe via grass-dev

Markus, all,

minting a DOI should take minutes/seconds, not days.

Can more in depth info / metadata about the particular transaction be provided, 
which states that "https://doi.org/10.5281/zenodo.10685321; should be the new 
version DOI for GRASS GIS 8.3.2RC1 ?

Best,
Peter




> Gesendet: Freitag, 23. Februar 2024 um 11:26 Uhr
> Von: "Markus Neteler" 
> An: "Peter Löwe" 
> Cc: "GRASS developers list" 
> Betreff: Re: [GRASS-dev] [release planning] GRASS GIS 8.3.2
>
> Dear Peter,
> 
> On Thu, Feb 22, 2024 at 7:33 PM Veronica Andreo  wrote:
> >
> > Markus, all,
> >
> > Great! Thanks a lot!
> >
> > Zenodo link works, but the doi link yields doi not found page... is it ok 
> > for the resolver link to take a couple of days?
> 
> Still not generated:
> https://doi.org/10.5281/zenodo.10685321
> 
> Peter, do you have an idea what could be wrong?
> 
> thanks,
> Markus
> 
> 
> > Vero
> >
> > El mar, 20 feb 2024 a las 19:45, Markus Neteler via grass-dev 
> > () escribió:
> >>
> >> Hi devs,
> >>
> >> On Thu, Feb 1, 2024 at 10:40 PM Markus Neteler  wrote:
> >> > We have accumulated a number of fixes in the past weeks.
> >> >
> >> > Here the milestone:
> >> > https://github.com/OSGeo/grass/milestone/24
> >>
> >> The RC1 release is now available, please test it:
> >> https://github.com/OSGeo/grass/releases/tag/8.3.2RC1
> >>
> >> The open issues/PR I have moved to a new 8.3.3 milestone. But let's
> >> focus on 8.4.0.
> >>
> >> And yay, the Zenodo bridge works again:
> >> Version 8.3.2RC1: https://zenodo.org/records/10685321
> >> DOI: https://doi.org/10.5281/zenodo.10685321 (resolver link will work
> >> in some hs from now)
> >>
> >> Hopefully no RC2 is needed.
> >>
> >> Thanks to all contributors,
> >> Markus
>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Version DOI missing for GRASS 8.3.0

2023-08-16 Thread Peter Löwe

+1

Best,
Peter




> Gesendet: Mittwoch, 16. August 2023 um 12:01 Uhr
> Von: "Markus Neteler" 
> An: "Peter Löwe" 
> Cc: "GRASS developers list" 
> Betreff: Re: Re: Re: [GRASS-dev] Version DOI missing for GRASS 8.3.0
>
> On Wed, Aug 16, 2023 at 8:31 AM Peter Löwe  wrote:
> >
> > Hi Markus,
> >
> > Zenodo says that another release by the GRASS project is necessary to 
> > retrieve the changes.
> 
> Well, so that sounds like manual upload if we want to see 8.3.0 there.
> 
> > Maybe a "minor technical maintenance" release could be considered ?
> 
> That would be 8.3.1 then, right? ... planned for Oct. 2023:
> https://github.com/OSGeo/grass/milestone/21
> 
> Best,
> Markus
> 
> > Other projects did such minor relase to obtain a DOI for the references in 
> > the Handbook of Geographic
> > Information, since the publication deadlines were not in synch with the 
> > release cycles of the projects.
> >
> > Best,
> > Peter
>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Version DOI missing for GRASS 8.3.0

2023-08-16 Thread Peter Löwe

Hi Markus,

Zenodo says that another release by the GRASS project is necessary to retrieve 
the changes.

Maybe a "minor technical maintenance" release could be considered ?

Other projects did such minor relase to obtain a DOI for the references in the 
Handbook of Geographic Information, since the publication deadlines were not in 
synch with the release cycles of the projects.

Best,
Peter








> Gesendet: Dienstag, 15. August 2023 um 22:27 Uhr
> Von: "Markus Neteler" 
> An: "Peter Löwe" 
> Cc: "GRASS developers list" 
> Betreff: Re: Re: [GRASS-dev] Version DOI missing for GRASS 8.3.0
>
> Hi Peter,
> 
> On Mon, Aug 14, 2023 at 2:50 PM Markus Neteler  wrote:
> >
> > Hi Peter,
> >
> > On Mon, Aug 14, 2023 at 1:23 PM Peter Löwe  wrote:
> > >
> > > Vacek, Markus, all,
> > >
> > > according to the Zenodo helpdesk there are still issues with the CFF file 
> > > of GRASS GIS 8.3:
> >
> > Ok, got it. And fixed:
> >
> > https://github.com/OSGeo/grass/pull/3123
> 
> Merged. The updated CITATION.cff is now in place in GitHub (main, 8.3,
> 8.2 branches).
> 
> For our case:
> https://github.com/OSGeo/grass/blob/releasebranch_8_3/CITATION.cff
> 
> May the Zenodo helpdesk try again?
> 
> Best,
> Markus
> 
> 
> -- 
> Markus Neteler, PhD
> https://www.mundialis.de - free data with free software
> https://grass.osgeo.org
> https://courses.neteler.org/blog
>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Version DOI missing for GRASS 8.3.0

2023-08-14 Thread Peter Löwe

Vacek, Markus, all,

according to the Zenodo helpdesk there are still issues with the CFF file of GRASS GIS 8.3:

---

Your CITATION.cff seems to be problematic still. You can validate it using tools like https://github.com/citation-file-format/cff-converter-python

jsonschema.exceptions.ValidationError: Additional properties are not allowed ('citation' was unexpected)

Failed validating 'additionalProperties' in schema:
    {'$id': 'https://citation-file-format.github.io/1.2.0/schema.json',

---

Best,

Peter

Gesendet: Dienstag, 08. August 2023 um 18:58 Uhr
Von: "Vaclav Petras" 
An: "Markus Neteler" 
Cc: "Peter Löwe" , "GRASS developers list" 
Betreff: Re: [GRASS-dev] Version DOI missing for GRASS 8.3.0

On Tue, 8 Aug 2023 at 12:26, Markus Neteler <nete...@osgeo.org> wrote:

Hi Peter,

On Tue, Aug 8, 2023 at 5:04 PM Peter Löwe <peter.lo...@gmx.de> wrote:
>
> Hi Markus,
> the licence ID for GRASS GIS 7.8.8. on its landing page reads:
> "Other (Open)"

I have seen it, too. Unfortunately not the precise licence description.

> This setting goes back to GRASS GIS 7.8.6.
> Since this is (just) landing page metadata, this can be changed after the minting of the DOI and the file upload into Zenodo.
>
> The landing page for GRASS GIS 8.2.0 (https://zenodo.org/record/6612307) has different licence metadata: "GNU General Public License v2.0 or later", which points to https://opensource.org/license/gpl-2-0/
>
> Did GRASS GIS 8.2.0 get maybe manually checked into Zenodo ?

I am not aware that anyone manually uploaded a GRASS GIS release to Zenodo.

> Otherwise this could be a Zenodo-sided bug ("worked before")..?

Probably they treated non-SPDX conformant license identifiers (here:
"GPL-2.0-or-later") differently?
Just guessing: In the past they changed it to "Other (Open)" and now
it is (randomly) failing?

I think it was two different things. The 7.8 branch info for Zenodo is just picked from GitHub metadata, while 8.2 and 8.3 are using the CFF file. Between the latest 8.2 and 8.3.0, Zenodo also happened to change how a non-conformat license entry is handled.

___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Version DOI missing for GRASS 8.3.0

2023-08-09 Thread Peter Löwe

Markus, all,
I have asked the Zenodo helpdesk to retrigger the deposit of GRASS8.3.0 and 
GRASS 8.3RC1.

Best,
Peter




> Gesendet: Dienstag, 08. August 2023 um 18:26 Uhr
> Von: "Markus Neteler" 
> An: "Peter Löwe" 
> Cc: "GRASS developers list" 
> Betreff: Re: Re: Re: Re: [GRASS-dev] Version DOI missing for GRASS 8.3.0
>
> Hi Peter,
> 
> On Tue, Aug 8, 2023 at 5:04 PM Peter Löwe  wrote:
> >
> > Hi Markus,
> > the licence ID for GRASS GIS 7.8.8. on its landing page reads:
> > "Other (Open)"
> 
> I have seen it, too. Unfortunately not the precise licence description.
> 
> > This setting goes back to GRASS GIS 7.8.6.
> > Since this is (just) landing page metadata, this can be changed after the 
> > minting of the DOI and the file upload into Zenodo.
> >
> > The landing page for GRASS GIS 8.2.0 (https://zenodo.org/record/6612307) 
> > has different licence metadata: "GNU General Public License v2.0 or later", 
> > which points to https://opensource.org/license/gpl-2-0/
> >
> > Did GRASS GIS 8.2.0 get maybe manually checked into Zenodo ?
> 
> I am not aware that anyone manually uploaded a GRASS GIS release to Zenodo.
> 
> > Otherwise this could be a Zenodo-sided bug ("worked before")..?
> 
> Probably they treated non-SPDX conformant license identifiers (here:
> "GPL-2.0-or-later") differently?
> Just guessing: In the past they changed it to "Other (Open)" and now
> it is (randomly) failing?
> 
> Anyway, we now have updated the CITATION.cff with the correct SPDX
> license identifier "GPL-2.0-or-later" in GRASS GIS 8.x.
> 
> It would be cool if Zenodo helpdesk could retrigger the 8.3.0 upload.
> 
> Best,
> Markus
>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Version DOI missing for GRASS 8.3.0

2023-08-08 Thread Peter Löwe

Hi Markus,
the licence ID for GRASS GIS 7.8.8. on its landing page reads:
"Other (Open)"
This setting goes back to GRASS GIS 7.8.6.
Since this is (just) landing page metadata, this can be changed after the 
minting of the DOI and the file upload into Zenodo.

The landing page for GRASS GIS 8.2.0 (https://zenodo.org/record/6612307) has 
different licence metadata: "GNU General Public License v2.0 or later", which 
points to https://opensource.org/license/gpl-2-0/

Did GRASS GIS 8.2.0 get maybe manually checked into Zenodo ? Otherwise this 
could be a Zenodo-sided bug ("worked before")..?

Best,
Peter




> Gesendet: Dienstag, 08. August 2023 um 12:33 Uhr
> Von: "Markus Neteler" 
> An: "Peter Löwe" 
> Cc: "GRASS developers list" 
> Betreff: Re: Re: Re: [GRASS-dev] Version DOI missing for GRASS 8.3.0
>
> HI Peter,
> 
> On Tue, Aug 8, 2023 at 11:24 AM Peter Löwe  wrote:
> >
> > Hi Markus, all,
> >
> > would it be feasible for the maintainers to do a manual Zenodo-check-in for 
> > GRASS GIS 8.3 similar  to GRASS GIS 7.8.8 ?
> 
> Well, the Zenodo part of 7.8.8 was automated.
> 
> > Alternatively I can contact the Zenodo helpdesk to get this fixed.
> 
> Hold on - I just checked it here:
> 
> https://zenodo.org/account/settings/github/repository/OSGeo/grass
> 
> 7.8.8 OSGeo/grass: GRASS GIS 7.8.8
> DOI: 10.5281/zenodo.8219486
> GRASS GIS 7.8.8
> Published
> a day ago
> 
> 
> 8.3.0 OSGeo/grass: GRASS GIS 8.3.0
> GRASS GIS 8.3.0
> Failed<<<<- !
> a month ago
> 
> 
> 8.3.0RC1 OSGeo/grass: GRASS GIS 8.3.0RC1
> GRASS GIS 8.3.0RC1
> Failed
> 2 months ago
> 
> 
> 8.2.1 OSGeo/grass: GRASS GIS 8.2.1
> DOI: 10.5281/zenodo.7764250
> GRASS GIS 8.2.1
> Published
> 4 months ago
> 
> 
> ...
> 
> In detail:
> 
> 8.3.0 OSGeo/grass: GRASS GIS 8.3.0
> GRASS GIS 8.3.0
> Failed
> 
> {
> "errors": "The license ID you have selected is not present in our
> system. For the available licenses please check in the following URL
> https://developers.zenodo.org/#licenses;
> }
> 
> https://github.com/OSGeo/grass/blob/4428fae82aba5e9033bae7ea4ba84da914949602/CITATION.cff#L109
> --> license: GNU General Public License v2 or later
> 
> I guess it dislikes the "... or later" part. How to write it properly?
> 
> Best,
> Markus
> 
> -- 
> Markus Neteler, PhD
> https://www.mundialis.de - free data with free software
> https://grass.osgeo.org
> https://courses.neteler.org/blog
>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Version DOI missing for GRASS 8.3.0

2023-08-08 Thread Peter Löwe

Hi Markus, all,

would it be feasible for the maintainers to do a manual Zenodo-check-in for 
GRASS GIS 8.3 similar  to GRASS GIS 7.8.8 ?

Alternatively I can contact the Zenodo helpdesk to get this fixed.

Best,
Peter




> Gesendet: Dienstag, 08. August 2023 um 09:40 Uhr
> Von: "Markus Neteler" 
> An: "Peter Löwe" 
> Cc: "GRASS developers list" 
> Betreff: Re: Re: [GRASS-dev] Version DOI missing for GRASS 8.3.0
>
> Hi Peter, all,
> 
> On Tue, Aug 8, 2023 at 9:37 AM Peter Löwe  wrote:
> >
> > Hi Markus, all,
> >
> > FWIW; the DOI minting _did_ work as expected for GRASS 7.8.8 on August 6: 
> > https://zenodo.org/record/8219486
> 
> Ok, that's good. I released it using the manual way of doing things.
> 
> > > On Mon, Aug 7, 2023 at 4:47 PM Peter Löwe  wrote:
> > > > I just noticed that GRASS 8.3. (https://github.com/OSGeo/grass) hasn't 
> > > > received a version DOI in Zenodo yet.
> ...
> > > > This is weird since the Zenodo - GitHub hookup used to be / is 
> > > > automated.
> 
> For GRASS GIS 8 we use the scripted/semi-automated way. However, I
> don't see why this should behave differently towards Zenodo.
> 
> Best,
> Markus
>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Version DOI missing for GRASS 8.3.0

2023-08-08 Thread Peter Löwe

Hi Markus, all,

FWIW; the DOI minting _did_ work as expected for GRASS 7.8.8 on August 6: 
https://zenodo.org/record/8219486



Best.
Peter





> Gesendet: Montag, 07. August 2023 um 17:25 Uhr
> Von: "Markus Neteler" 
> An: "Peter Löwe" 
> Cc: "GRASS developers list" 
> Betreff: Re: [GRASS-dev] Version DOI missing for GRASS 8.3.0
>
> On Mon, Aug 7, 2023 at 4:47 PM Peter Löwe  wrote:
> >
> > Hello List,
> >
> > I just noticed that GRASS 8.3. (https://github.com/OSGeo/grass) hasn't 
> > received a version DOI in Zenodo yet.
> > The latest version DOIs were minted for 7.8.8. and 8.2.1:
> > https://zenodo.org/search?page=1=20=conceptrecid:%225176030%22=mostrecent_versions=True
> >
> > This is weird since the Zenodo - GitHub hookup used to be / is automated.
> 
> Oh, too bad.
> 
> > Ideas, anyone ?
> 
> Maybe the "bridge" is broken again?
> Does it still work for others, e.g. GDAL?
> 
> Best,
> Markus
>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Version DOI missing for GRASS 8.3.0

2023-08-08 Thread Peter Löwe

Hi Markus, all,

GDAL minted its latest version DOI on July 13:
https://zenodo.org/record/8144520

Have there been any changes in the release process (GRASS-sided) ?

Best,
Peter




> Gesendet: Montag, 07. August 2023 um 17:25 Uhr
> Von: "Markus Neteler" 
> An: "Peter Löwe" 
> Cc: "GRASS developers list" 
> Betreff: Re: [GRASS-dev] Version DOI missing for GRASS 8.3.0
>
> On Mon, Aug 7, 2023 at 4:47 PM Peter Löwe  wrote:
> >
> > Hello List,
> >
> > I just noticed that GRASS 8.3. (https://github.com/OSGeo/grass) hasn't 
> > received a version DOI in Zenodo yet.
> > The latest version DOIs were minted for 7.8.8. and 8.2.1:
> > https://zenodo.org/search?page=1=20=conceptrecid:%225176030%22=mostrecent_versions=True
> >
> > This is weird since the Zenodo - GitHub hookup used to be / is automated.
> 
> Oh, too bad.
> 
> > Ideas, anyone ?
> 
> Maybe the "bridge" is broken again?
> Does it still work for others, e.g. GDAL?
> 
> Best,
> Markus
>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] Version DOI missing for GRASS 8.3.0

2023-08-07 Thread Peter Löwe

Hello List,

I just noticed that GRASS 8.3. (https://github.com/OSGeo/grass) hasn't received 
a version DOI in Zenodo yet.
The latest version DOIs were minted for 7.8.8. and 8.2.1:
https://zenodo.org/search?page=1=20=conceptrecid:%225176030%22=mostrecent_versions=True

This is weird since the Zenodo - GitHub hookup used to be / is automated.

Ideas, anyone ?

Best,
Peter





___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [release planning] Enable Zenodo before 7.8.6 and 8.0.0

2021-08-11 Thread Peter Löwe

Hi Vaclav, GRASS devs,

the MOSS project has successfully adopted a new Zenodo-related feature, which might simplify also the open access publishing of GRASS 7.8.6 and 8.0.0 via Zenodo.

- An additional file called ".zenodo.json" was added to the top level directory of the github repo of MOSS.

- This file (https://github.com/OSGeo/MOSS/blob/main/.zenodo.json) contains structured information about the project author and the developer team, but also maintainers with their specific roles. Individual ORCID IDs can be included.

- The general description how to set the webhooks connecting github and Zenodo (https://guides.github.com/activities/citable-code/) remains the same.

- New: Once a new release is done in github, Zenodo will harvest all metadata provided in .zenodo.json and will update the "cite as" section of the Zenodo landing page accordingly (https://doi.org/10.5281/zenodo.5140319)

- This is a significant improvement. Until now, only the names of the owners of the github repo and the Zenodo account were shown, which is inaccurate in most cases.

- Technical information about the JSON Schema followed by the ".zenodo.json" file is at https://zenodo.org/schemas/deposits/records/legacyrecord.json and is documented in the Zenodo developer docs at https://developers.zenodo.org/?python#deposit-metadata.

Best,

Peter

Gesendet: Sonntag, 06. Juni 2021 um 05:33 Uhr
Von: "Vaclav Petras"
An: "Peter Löwe"
Cc: "grass-dev@lists.osgeo.org"
Betreff: Re: Re: [release planning] Enable Zenodo before 7.8.6 and 8.0.0

Hi Peter, all, thanks for the answers. I have more questions assuming that's okay.

On Fri, Jun 4, 2021 at 2:57 AM Peter Löwe <peter.lo...@gmx.de> wrote:

==> the CodeMeta-Project is currenlty pushing software citation standards: https://codemeta.github.io/

Thanks. The roles there seem to be more clear. Any opinion on CodeMata versus CFF (see also below)?

BTW, ways to retro-provide DOI versioning for previous GRASS releases would be an rewarding topic to discuss with Data Cite (the DOI infrastructure community).

Any opinions on how useful this is? We want a good archive of old versions, but does someone need DOIs for old releases?

==> This depends on wether the community wants to give due credit by citation to the persons which were involved in the previous releases.

Currently, the author list maintained in the source code is cumulative as far as I know, so old authors are still included as authors, so only use cases for that would be citing old releases in paper or by the new versions of software software. None seem likely to me. What do you think?

Any suggestions on includings DOI into source code? It seems to me that you can only use the generic/concept one and tell people to get the recent one. I didn't figure out the DOI reservation for GitHub repos.

Rather than where to put it - although that's important, too - my question is about which DOI? The main one everywhere or somehow try to put there the version specific one if that's even possible. It seems to me that the main DOI is the only feasible option.

==> A JSON file could be included. This way, the information is both readable for humans and automated access: https://codemeta.github.io/codemeta-generator/

I was thinking about the Citation File Format as I have seen it used quite a bit. Any opinions on that?

___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [release planning] Enable Zenodo before 7.8.6 and 8.0.0

2021-06-08 Thread Peter Löwe

Hi Vaclav, all,

maybe helpful:

The transient MOSS repo has been updated for CFF and codemeta.json:

https://github.com/ploewe/MOSS

The online CFF-generator didn't accept some of the attributes. Doublechecking of the output is recommended.

Further, we hijacked the CFF affiliation tag to include MARC relator/ role terms (https://www.loc.gov/marc/relators/relaterm.html), like the R community has done:

https://r-pkgs.org/description.html

"... A three letter code specifying the role. There are four important roles:

cre: the creator or maintainer, the person you should bother if you have problems.

aut: authors, those who have made significant contributions to the package.

ctb: contributors, those who have made smaller contributions, like patches.

cph: copyright holder. This is used if the copyright is held by someone other than the author, typically a company (i.e. the author’s employer).

..."

I will talk to the software citation folks to see how this is perceived.