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

(JOSS) Statement of Need and Community Guidelines in the Documentation #110

Closed
fb456 opened this issue Feb 2, 2024 · 4 comments · Fixed by #114
Closed

(JOSS) Statement of Need and Community Guidelines in the Documentation #110

fb456 opened this issue Feb 2, 2024 · 4 comments · Fixed by #114

Comments

@fb456
Copy link

fb456 commented Feb 2, 2024

At the moment, the documentation is missing the Statement of Need and Community Guidelines sections.

@cfarm6 cfarm6 linked a pull request Feb 2, 2024 that will close this issue
@cfarm6
Copy link
Member

cfarm6 commented Feb 2, 2024

@fb456 Thank you. This has been addressed.

@fb456
Copy link
Author

fb456 commented Feb 2, 2024

Hi. I don't think you've added a Community Guidelines section, something like the link that says:

Community guidelines (https://joss.readthedocs.io/en/latest/review_criteria.html#community-guidelines)
There should be clear guidelines for third-parties wishing to:

Contribute to the software
Report issues or problems with the software
Seek support

@cfarm6 cfarm6 reopened this Feb 2, 2024
@cfarm6
Copy link
Member

cfarm6 commented Feb 2, 2024

@fb456 Thank you for the link. I think that the Community Guidelines have now been addressed. Please let me know if there are any changes that you would like to see. It may take a couple minutes for the updated documentation to deploy.

@SotaYoshida
Copy link

Let me jump in to give a minor comment.
For the first item in the Community Guidelines, the brackets [],() used to specify links are reversed.

@cfarm6 cfarm6 closed this as completed Apr 3, 2024
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 a pull request may close this issue.

3 participants