Skip to content
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

Merged
merged 5 commits into from
Sep 23, 2024

Conversation

vmartinez-cu
Copy link
Collaborator

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.

Copy link
Member

@bourque bourque left a 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
Copy link
Member

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.

Copy link
Collaborator Author

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!

docs/source/workflows/open_source/citing_software.md Outdated Show resolved Hide resolved
docs/source/workflows/open_source/citing_software.md Outdated Show resolved Hide resolved
* 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.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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)

@vmartinez-cu vmartinez-cu merged commit 338ae9a into lasp:main Sep 23, 2024
7 checks passed
@vmartinez-cu vmartinez-cu deleted the software_citation_guide branch September 23, 2024 21:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants