2019-04-08 16:08 UTC-04, Terri Yu <[email protected]>: > I forgot to say that yes, I am the owner of the GitHub repo and I recently > got a request from a scientist asking how they could cite my software. > That's what prompted this question. > > This is software that is under development, so I don't have a paper and I > don't want to spend a lot of time maintaining citations. > > It sounds like generating a DOI via Zenodo is the easiest and most common > way to take care of this issue, if your repo is on GitHub ? >
Also note the nice CiteAs tool that can find citations automatically for repository or website: http://citeas.org/. I would recommend adding a CITATION.txt to your repository (or a CodeMeta file <https://codemeta.github.io/user-guide/>, but that is more involved) next to your LICENSE.txt, listing the main contributors of the project and your preferred citation if any (if you have a paper associated with it, or your Zenodo DOI). Once integrated, Zenodo will automatically archive your code and create a new DOI (or rather, a new version of the same record) every time you create a release on GitHub, so this is really a setup & forget solution that you shouldn't have to worry about down the road. I am skeptical of the FORCE11 principles, that recommend yet another JSON-LD format, which seems to have much lower adoption than CodeMeta. Best -- Rémi ------------------------------------------ The Carpentries: discuss Permalink: https://carpentries.topicbox.com/groups/discuss/T33d60669d32ac1d7-M8789ba37353cfc9184721247 Delivery options: https://carpentries.topicbox.com/groups/discuss/subscription
