-
Notifications
You must be signed in to change notification settings - Fork 14
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
additional minor JOSS issue #80
Labels
documentation
Improvements or additions to documentation
Comments
Merged
Reopened for JOSS review. |
alexzwanenburg
added
documentation
Improvements or additions to documentation
and removed
bug
Something isn't working
labels
May 16, 2024
I do prefer using GitHub issues section as a centralised place communicate. I added two more templates: one for documentation and one for new features and enhancements. I will add a question template. |
alexzwanenburg
added a commit
that referenced
this issue
May 16, 2024
@alexzwanenburg good enough for me....should I close this issue? |
Thanks for checking. I will close the issue. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Technically, it would be nice in terms of community guidelines if there was a clear statement about the maintainer and how to contact them. This is for me implied when they ask for "clear guidelines for third parties wishing to 1) Contribute to the software 2) Report issues or problems with the software 3) Seek support" on my checklist. To make it perfect you could either A. add a third issue template for questions (not labelled bugs?) or B (I personally think this is better) just put the email of some people with ownership who will not go away. Some students come and go, but a package like this should really be left in the hands of someone who can be in charge of maintaining it for the sake of the community. There is also option C which is to have some kins of communication board. I realize this is a small and nit-picking point, but I've wanted radiomics standards for the better part of a decade, so I want your package to suceed!
The text was updated successfully, but these errors were encountered: