Issue Repo DOI

[hsteptoe]

I think this repo/project is now seeing sufficient development that we should issue it with a DOI. This would: (a) provide it with a permanent and persistent point of reference, (b) make it clear how it should be cited or referenced and (c) allow us to acknowledge all the contributors past and present who have got us to where we are today.

We already have an agreed licence for the whole repo, so this shouldn't require any further approvals. This is simply an labelling procedure.

I would suggest Zenodo as the DOI mint, as it has nice integration with github and keeps track of difference releases etc. but other mints may also be available.

Thoughts? @nhsavage @zmaalick @gredmond-mo

[zmaalick]

Good suggestion, we can go with DOI mint. But, at v3.0. we are about to merge cordex updated worksheets.

…

________________________________ From: Hamish Steptoe ***@***.***> Sent: 21 March 2022 17:07 To: MetOffice/PyPRECIS ***@***.***> Cc: Maalick, Zubair ***@***.***>; Mention ***@***.***> Subject: [MetOffice/PyPRECIS] Issue Repo DOI (Issue #122) This email was received from an external source. Always check sender details, links & attachments. I think this repo/project is now seeing sufficient development that we should issue it with a DOI. This would: (a) provide it with a permanent and persistent point of reference, (b) make it clear how it should be cited or referenced and (c) allow us to acknowledge all the contributors past and present who have got us to where we are today. We already have an agreed licence for the whole repo, so this shouldn't require any further approvals. This is simply an labelling procedure. I would suggest Zenodo and the DOI mint, as it has nice integration with github and keeps track of difference releases etc. but other mints may also be available. Thoughts? @nhsavage<https://github.com/nhsavage> @zmaalick<https://github.com/zmaalick> @gredmond-mo<https://github.com/gredmond-mo> — Reply to this email directly, view it on GitHub<#122>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AN2CPNBYDAKQM5T43PPHHVDVBCUGXANCNFSM5RIKZQLA>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[nhsavage]

We should close #123 on the updated README and agree a new name before moving this forwards