-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Archiving on Zenodo or elsewhere. #14
Comments
This I have to confess I'm not very familiar with... So essentially, I don't really know what I think --- but I sense you are about to enlighten me?... ;-) |
No problem 😄 So the idea is that you can archive and assign a DOI to each release (so version 1.0.0) for example. If I am doing analysis with your package I can then reference this version to get the exact code I used (rather than your updated code). It is similar to providing a version number but more formalized. It's also independent of GitHub which is probably sensible as a back up for versioning the software. An example is here. Happy to support implementing this. |
Sounds like a sensible idea/plan and happy for it to go ahead! |
Awesome - pleased your happy for me to have a stab at this stuff. Could you leave open the issues that you are interested in having implemented and just close that you are not? It would really help me keep track of things to do from a project management perspective. |
Done |
It can be really great to be able to link to specific package versions using a DOI. Zenodo is a nice tool for doing this. What do you think?
Linked to #6
The text was updated successfully, but these errors were encountered: