Within a Resource section, links to THAT resource, actually link externally to the resource \
i.e. in the blog resource section, links to the blog link to https://ropensci.org/blog
Links to a Resource in a DIFFERENT section link to that section
i.e. in the blog resource section, links to the blog guide link to #blogguide
Text in the MAIN bullet is the "common" action text, and ALSO the text to be inserted into Motivations Chapter.
Text in SUB bullets is either for Resources Chapter (noted Chp 3) with additional details that may differ depending on the section but which are easier to keep consistent if we have it here (e.g., for the "Write a blog post" text which occurs in three different sections), OR it shows slightly different variations on the action depending on the specific "I want to.."
- Meet the Humans of rOpenSci and learn about their roles, their research, career paths, and contributions
- Read our Code of Conduct to ensure you're prepared to participate
- Follow rOpenSci on Mastodon
- Subscribe to our Newsletter
- Engage with us on Mastodon. Amplify best practices from our social media to your networks. Reply to a post to share your experience or expertise on a topic
- Ask or answer questions in the forum or on Slack
- Read or ask questions in the "Best Practices" category in our forum or on Slack
- Read or ask questions in the "Packages" category in our forum or on Slack
- Follow discussions about statistical software peer review, best practices, and Q & A in the forum or on Slack
- Support fellow community members (e.g., by welcoming newcomers, giving credit, connecting members with people or resources)
- Try a 2-hour remote co-working session with someone in our SlaSlackck #co-working channel. Read about contributions required to join rOpenSci Slack.
- Seek community feedback on your package ideas in the "Packages" category in our forum. Ideas for new packages, package updates, or package features.
- Browse the Jobs category in our public forum or in **Slack
- Attend a Community Call
- Watch recordings and read collaborative notes from past Community Calls
- Recommend topics or speakers for Community Calls
- Help organize a Community Call
- Propose your idea for a Community Call summary post for our blog
- (Chp3 text) Take a look at examples of community call posts in the blog, consult the blog guide to see what's involved then contact our Community Manager via our contact form to discuss your idea.
- Submit a correction
- (Chp3 text) See a typo or broken link in the Blog? Submit a correction. Open an issue in the blog repository or make a pull request with your suggestion and our Community Manager will review it. GitHub has helpful documentation for opening issues and making pull requests.
- Read blog posts or tech notes
- Read blog posts or tech notes, particularly those tagged with "Welcome"
- Read blog posts or tech notes, particularly those tagged with "Reviewer"
- Read blog posts or tech notes, particularly those tagged with "Interviews"
- Read blog posts or tech notes about specific rOpenSci packages, or about creative use cases for multiple rOpenSci packages
- Share posts with your network
- Comment on a post to share your perspective or to ask a question
- Write a blog post or tech note (see both the Blog and the Blog Guide)
- (Chp3 text) Take a look at examples of posts above and on the blog, consult the blog guide to see what's involved then contact our Community Manager via our contact form to discuss your idea.
- Submit a correction
- (Chp3 text) See a typo or something that's not clear? Submit a correction. Open an issue in the blog guide repository or make a pull request with your suggestion and one of the authors will review it. GitHub has helpful documentation for opening issues and making pull requests.
- Write a blog post or tech note (see both the Blog and the Blog Guide)
- (Chp3 text) Read about some blog themes, browse the Blog Guide to see what's involved, then contact our Community Manager our contact form to discuss your idea.
- Browse rOpenSci packages
- Use an rOpenSci package
- Tell a friend about an rOpenSci package that may be useful for their work
- Browse citations of rOpenSci packages to find interesting applications
- Cite rOpenSci packages** in manuscripts and presentations and encourage your colleagues to cite software. Highlighting software and its maintainers will help promote software behind research
- Write a post about using rOpenSci packages** on your own blog
- Report a bug by opening an issue. If you're asking for R help, reporting a bug, or requesting a new feature, you're more likely to succeed if you include a good reprex (a reproducible example).
- Make a pull request
- To fix a bug
- To add/fix examples
- To add/clarify documentation
- Make a feature request
- Review the documentation
- Write a vignette/article for a package
- Browse package Task Views to discover packages to use
- Make a pull request to add packages or details to an existing task view after discussing your approach with the maintainer
- Label your issues
- Include future plans for your package
- Address a "Help wanted" issue
- Address any open issue. Explore open issues in rOpenSci packages and consider submitting a fix.
- Read the Dev Guide
- Read the Dev Guide, especially the Reviewer Guide section
- Read the Dev Guide, especially the CRAN Gotchas section
- Volunteer to review a package
- Submit your package for peer review after determining whether it's in scope for rOpenSci
- Acknowledge your reviewers in your package DESCRIPTION (with their consent). Read about this in Thanking Your Reviewers: Gratitude through Semantic Metadata.
- Ensure your package is easily citable
- Volunteer to maintain or co-maintain a package
- Request a co-maintainer for your package
- Publish a paper about your package
- Weigh in on tough technical issues on software review threads
- Submit a correction
- (Chp3 text) See a typo or broken link in the Dev Guide? Submit a correction. Open an issue in the dev guide repository or make a pull request with your suggestion and our Community Manager will review it. GitHub has helpful documentation for opening issues and making pull requests.
- Explore the R-universe
- Explore the R-universe and share your findings with colleagues
- Create your own R-universe
- Read/Contribute to the R-universe discussion
- Report a bug in the R-universe