Add a page on when and how to report issues
@rgommers is already working on this.
Since Nov 15, 2019.
Assessment
This issue has not been assessed yet.
Description
See user story at https://github.com/numpy/numpy.org/issues/42#issuecomment-540139059. Having good issue reporting guidelines is quite important, and our current content is insufficient probably.
What we have today:
- https://github.com/numpy/numpy/blob/master/.github/ISSUE_TEMPLATE.md
- https://numpy.org/devdocs/bugs.html
- https://scipy.org/bug-report.html
It should end up in a sub-page or in the docs, and linked from Contribute, Community and Install probably.
- Dominant language
- Shell
- Stars
- 128
- Forks
- 132
- Avg merge
- 1d 18h
- Merged PRs (30d)
- 3
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.
More from numpy/numpy.org
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
sustain-2026
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
sustain-2026 translations
Difficulty 3/5 1-2 days Newbie friendliness 30/100
-
Difficulty 4/5 3-5 days Newbie friendliness 20/100
-
translations
Difficulty 4/5 3-5 days Newbie friendliness 38/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
bug easy help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
lacs-project/sysknife#503 ·
-
help wanted kind/documentation
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
liquidmetal-dev/flintlock#1239 ·