For general software citation questions, the Force11 Software Citation Principles are a great reference: https://www.force11.org/software-citation-principles
And if you’re interested in discussing recommendations for software citation, you can join the working group: https://www.force11.org/group/software-citation-implementation-working-group Tom Morrell | Research Data Specialist | Caltech Library<https://library.caltech.edu> Mail Code 2-32, Pasadena CA 91125 | 626-395-3827 | data.caltech.edu<https://data.caltech.edu> On Apr 7, 2019, at 9:12 PM, C. Titus Brown <[email protected]<mailto:[email protected]>> wrote: Hi Terri, That’s what we do! See for example, https://www.biorxiv.org/content/10.1101/462788v2 where we say: Software. The source code for the index construction and search is available at https://github.com/spacegraphcats/spacegraphcats (23). It is implemented in Python 3 under the 3-Clause BSD License. Version 1.1, used in this paper, is archived at DOI: 10.5281/zenodo.2505206 best, —titus On Apr 7, 2019, at 8:58 PM, Terri Yu <[email protected]> wrote: Hi all, I found this GitHub Guide about producing a DOI for a GitHub repo through Zenodo. https://guides.github.com/activities/citable-code/ Is that the recommended way to cite open source software that is under development on GitHub? Thanks for your help, Terri The Carpentries / discuss / see discussions + participants + delivery options Permalink ------------------------------------------ The Carpentries: discuss Permalink: https://carpentries.topicbox.com/groups/discuss/T33d60669d32ac1d7-M285a351d7d851eba15f5745e Delivery options: https://carpentries.topicbox.com/groups/discuss/subscription
