-
Notifications
You must be signed in to change notification settings - Fork 25
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
Add citation.cff and core team guide in order to get a DOI #340
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is great @maxrjones ! (I mean I did write this guide orginally haha)
I think it kind of needs to be a manually-chosen list. I added somewhat random (trusted) people to that list the core-devs github team to reduce the bus factor initially. And there are people I think deserve to get the citations who haven't actually contributed code to this library directly and aren't on that core-devs list (I'm thinking mainly of @martindurant). |
Co-authored-by: Tom Nicholas <[email protected]>
Sounds good, sorry to put this on you but I think you and @norlandrhagen should come up with this initial list as the most consistent VirtualiZarr developers so far (as shown by https://github.com/zarr-developers/VirtualiZarr/graphs/contributors). |
No worries - I literally already have a written ToDo somewhere where I started doing this. |
@TomNicholas @norlandrhagen should the authors in citations.cff be based on https://github.com/orgs/zarr-developers/teams/virtualizarr-core-devs,
git shortlog -sne
, or some combination?p.s. if you write a JOSS article it could be added as the preferred citation similar to Xarray's Journal of Open Research Software article
Closes #305