Translation of the "How to Contribute to Numpy" comic
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 38/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Stale
- Domain
- content, documentation, localization
Research direction
Start with the English comic script and the comic pages with blank speech bubbles linked in the issue. Choose a target language, translate and review the script, then use a graphics editor to update the speech bubbles and check the typesetting. The work is done when the translated script and comic pages have been reviewed and released.
Written by the indexing model from the issue text.
Description
Hi all, this is a tracking isuse on translating the "How to Contribute to Numpy" comic.
These comics aim to show newcomers that NumPy is driven by people who use it: in this case, scientists! These comics will show grad students finding a usability problem in NumPy, working together to submit an issue, and talking to community members.
Here's a link to the comic.
This is following similar efforts to translate the NumPy documentation at #55
Timeline
I will be able to help with translation after December, since I am finishing up the comic before then.
Languages
- We'll probably start with a Portuguese translation.
- @joao-antonio-gg expressed interest in translating the comics to Portuguese in a previous issue about the comics
- I welcome other languages as well! Just comment here with your interest and language.
Process
- Translate the English script into the target language (note: this is not the final script but close to final)
- Review the translation
- Update the text in a graphics editor (such as GIMP, Inkscape or Krita)
- Review the typesetting (does the translated text fit in the speech bubbles?)
- Release translated comic
Items:
- Comic script in English
- Comic pages with blank speech bubbles
- Comic script in target language
- Comic pages with target language
- 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
-
sustain-2026
Difficulty 3/5 1-2 days Newbie friendliness 48/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
community-scripts/ProxmoxVE#17425 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
danielmiessler/LifeOS#2218 ·
-
docs(agents): strengthen the no-backslash-escaped-backticks rule with an issue-creation example Open
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
technical-debt
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
ll7/robot_sf_ll7#9560 ·
-
package-update
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
oSoWoSo/vOid_Community_repOsitory#148 · 1 comment ·