Attendee’s: Michelle Guy ( firstname.lastname@example.org );
Madison Langseth (email@example.com)
Eric Martinez ( firstname.lastname@example.org )
Blake Draper (email@example.com)
Scott Whitaker ( firstname.lastname@example.org )
Robert Djurasaj ( email@example.com )
Rob Miller ( firstname.lastname@example.org )
Joseph Pantoga ( email@example.com )
Phone: passcode 17803786
x4848 From the Reston National Center
703-648-4848 From other DOI locations.
1-855-547-8255 (855-5GS-TALK) From non-DOI locations including cell phones
Meeting Notes in Google Docs: https://docs.google.com/document/d/10I5JsCDqyp-yxABbhgrFN_XBQ9ORmV_F5tsWy_GYmCU/edit
○ Our CDI page: https://my.usgs.gov/confluence/display/cdi/Software+Development+Cluster
● Software repository requirements and recommendations
○ Metadata https://github.com/usgs/best-practices/blob/master/software/metadata.md
○ Contributing https://github.com/usgs/best-practices/blob/master/CONTRIBUTING.md
○ Code of conduct https://github.com/usgs/best-practices/blob/master/CODE_OF_CONDUCT.md
● Software releases and DOI’s https://github.com/usgs/best-practices/blob/dede3aa417b83e48a32ca3ad1a0eec5f23d3f483/doi.md
○ What to point a DOI at? only at release on a “tag” version?
● Credit for original authors, especially as we work in public domain? We can request, encourage, we cannot enforce.
○ Seek help from office of Science Quality and Integrity
○ Provide a recommended citation for users of our software.
■ Where should we put this in our repositories? Maybe in Readme, and/or disclaimer, or contributing.md or codeofconduct.md, include DOI of reviewed release, but what about of master/head (commit hash?), On release tags you can put comments, maybe include citations/DOI’s; Maybe DOI + commit hash or tag+commit hash
■ Educate our community; Open source coffee talks with Cassandra Ladino on CDI; Research data alliance meeting talked about citations ( Software Source Code Interest Group , notes from meeting last week , Leslie is on their email list and will try to make the useful connections between groups); What else is community doing? Cut a tag and site the tag. Look at github themselves
■ Do citations yourself
■ Follow examples where relevant, if possible: https://guides.github.com/activities/citable-code/ (Digital Object Identifier process may vary for USGS model, but this may provide a template)
■ Tracking downstream use of software products efficiently may also be worth considering. ( https://blog.datacite.org/software-citation-workflows/ , https://github.com/force11/force11-sciwg/issues/14 )
■ There are many ways to get a DOI for software, there’s a Github best-practices page about this: ( https://github.com/usgs/best-practices/blob/master/doi.md )
■ Varies per software project
● Should github.com/usgs/best-practices be moved to code.usgs.gov? Who has “authority” to answer?
● Code.usgs.gov (Eric Martinez)
○ soon to migrate to CHS (cloud hosting services) which aside from small downtime will be seamless to users
○ Unauthenticated users can only see “public” projects which will be publicly released projects
○ Reviewed/Released projects with DOI’s will be sync’d from github.com/usgs (this does not include projects under “individual” accounts on github)
○ Can do internal projects (AD authentication to USGS) - default
○ Can do private projects with access list essentially
○ Establishing a governing body - if you want to help email firstname.lastname@example.org