Issues labelled sprint
or good-first-issue
on the SciPy issue tracker are a mix of code (mostly Python-level) and documentation issues selected for today's sprint.
If you do not see a suitable issue or you are interested in a particular SciPy submodule, please look at the relevant submodule label or ask a mentor for a suggestion.
The following documentation will help you set up and build a local development environment:
Please comment on the issue that you are working on to avoid multiple people taking on the same issue. We do not assign issues.
There are a lot of issues 😅! The selections labelled sprint
and good first issue
are focused on beginner-to-intermediate-friendly issues that are actionable and should be doable today. If you want to take on something a little more challenging, there are a lot of issues in the repo to choose from. If you search for an issue not labelled sprint
or good first issue
, try to choose issues that (from the title or labels) seem to be bugs, and don't have more than 5 comments - those are most likely to be actionable (old issues are often difficult to solve or unresolvable which is why they still remain.)
If you are working on documentation, remember to check against https://scipy.github.io/devdocs/index.html. This is the version of the documentation corresponding to the latest development version (aka what is merged on the main branch on GitHub).
If you worked in a pair/group and would like to acknowledge multiple authors on the PR, find some helpful documentation here.
Commit messages should be clear and follow a few basic rules. Please try to label your commits with an indicative label. Here's the SciPy guide.
TODO