Good First Issues for New Contributors
Nobody has claimed this yet.
- Dominant language
- R
- Stars
- 442
- Forks
- 93
- Avg merge
- 3h 11m
- Merged PRs (30d)
- 1
Description
As bayesplot grows, the number of small issues that can be easily fixed increases. These tasks are often related to fixing a part of the documentation or adding a small new capability to a function. Even though they are not complicated tasks to do, some people need to work on fixing and creating PRs for them.
To make it easier for new contributors to find those issues and keep the contribution threshold low for everyone, we are gathering such issues/tasks under this master issue. If you are new to contributing to bayesplot or open-source projects in general, please check CONTRIBUTING.md. If you find such things that can be easily fixed but you don't have time to do it yourself, please create a sub-issue for them under this issue so that other people can pick up the task.
Hope you have a good time using bayesplot and enjoy being part of it!
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
This is a master tracking issue rather than a specific implementation task, and it names no source file or test to change. Read .github/CONTRIBUTING.md first, then identify or create a concrete sub-issue with a defined documentation or function change and an observable completion condition.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- r
- Domain
- developer-experience
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100