MetOffice / MetOffice/PyPRECIS
Issue Repo DOI
Nobody has claimed this yet.
- Dominant language
- Jupyter Notebook
- Stars
- 20
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
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
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the repository's GitHub release settings and the proposed Zenodo integration. Confirm how releases and contributors would be represented, then document the citation information and verify that a DOI is minted and linked to the repository. The issue provides no specific files or tests to run.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- documentation, release
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100