Mauro's highlights from rstudio::global 2021
Open
Nobody has claimed this yet.
conference
rstudio
- Dominant language
- No language data
- Stars
- 17
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
- oRganization: How to make internal R packages part of your team.
- You're Already Ready: Zen and the Art of R Package Development. Moving from unstructured projects to R packages.
- Reporting on and visualising the pandemic. What is a good visualization? What can we learn from feedback?
- Mastering Shiny with Appsilon. What does it take to build robust apps?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue body lists four rstudio::global 2021 links; start by opening those linked pages and reviewing the requested resource context. No repository file, test, entry point, concrete change, or completion check is named.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- r
- Domain
- content, documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100