I just pointed a colleague to clowderframework.org and while doing so read up on the new news about clowder2, congratulations!
I then clicked through to the good first issues and have some suggestions.
I'll also note that it is only because of how awesome Clowder is, how well you have done so far in building up an open source community, that I wanted to make the following suggestions because I think it would be worth putting in the effort to streamline the process for new users and the community in general.
Here are some specific suggestions:
check recommendations under GitHub's 'community health' standards, and start with a CONTRIBUTING.md file.
Update the website homepage to use GitHub's simplified interface for new contributors that appears here: https://github.com/clowder-framework/clowder2/contribute. This link also appears to the outside community on the issues page, along with a link to the CONTRIBUTING.md file
Audit issues tagged 'good-first-issue' to ensure that 1) the work required is truly a good place to start for new users and 2) that the feature or task is clearly defined in terms of the desired outcome as well as where to get started, perhaps with links to CONTRIBUTING.md. I searched for specific recommendations in the GitHub docs - as well as the GSOC docs - but didn't find any. But this may contain some inspiration: https://dev.to/cerchie/what-makes-a-good-first-issue-4fn0
lmarini
commented
3 weeks ago
I just pointed a colleague to clowderframework.org and while doing so read up on the new news about clowder2, congratulations!
I then clicked through to the good first issues and have some suggestions.
I'll also note that it is only because of how awesome Clowder is, how well you have done so far in building up an open source community, that I wanted to make the following suggestions because I think it would be worth putting in the effort to streamline the process for new users and the community in general.
Here are some specific suggestions: