-
Notifications
You must be signed in to change notification settings - Fork 4
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 guide on citing software #32
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 looks great! I just have a few minor suggestions.
good example of this second approach, which follows guidance from the [Turing Way](https://the-turing-way.netlify.app/communication/aa/aa-equitable) | ||
project. | ||
|
||
Credit: Content taken from a Confluence guide written by Veronica Martinez |
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.
I have been adding an "Acronyms" section at the bottom of pages that spell out any acronyms used within the document. There are a few here that I think could be mentioned: DOI, SMD, and API.
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.
I like what you did for the docker guides. I'll add a section on acronyms here!
* There are multiple ways to cite authors for software. One method is to list the name of each contributor. | ||
Since the list of contributors may change from release to release, a contributors list in the repository | ||
can help track these updates and ensure proper attribution. Another option is to list a group or organization | ||
as the author (i.e. <project name> Developers) and recognize individual contributors via the all-contributors bot. |
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.
as the author (i.e. <project name> Developers) and recognize individual contributors via the all-contributors bot. | |
as the author (i.e. `<project name>` Developers) and recognize individual contributors via the all-contributors bot. |
This might be needed. Without it, I think markdown is treating it in some strange way (I see that it doesn't show up in the RtD page)
Co-authored-by: Matthew Bourque <[email protected]>
Co-authored-by: Matthew Bourque <[email protected]>
This guide covers content from this confluence page that I created a few months back. It only covers using Zenodo. Any other methods for citing software will need to be added.