stan-dev/bayesplot

Good First Issues for New Contributors

Open

#365 opened on Aug 11, 2025

View on GitHub
 (5 comments) (1 reaction) (0 assignees)R (93 forks)github user discovery
good first issue

Repository metrics

Stars
 (439 stars)
PR merge metrics
 (PR metrics pending)

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

Research direction
Look through the bayesplot repository for small documentation fixes or minor enhancements, and follow the CONTRIBUTING.md guidelines to contribute.
Tech stack
r
Domain
documentation
Issue type
Documentation
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
1
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitR
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
90