|
47 | 47 | opportunities abound.</p><h3id=translating-website-content>Translating website content<aclass=headerlinkhref=#translating-website-contenttitle="Link to this heading">#</a></h3><p>We are working on translating<ahref=https://numpy.org>numpy.org</a> into multiple languages to make |
48 | 48 | its content more accessible to NumPy users all over the globe. (See |
49 | 49 | <ahref=https://numpy.org/neps/nep-0028-website-redesign.html#translation-multilingual-i18n>NEP 28</a> |
50 | | -for background.) Volunteer translators are at the heart of this effort. If you’d like to help, join the |
51 | | -<em>translation</em> channel on the |
52 | | -<ahref=https://discord.com/channels/786703927705862175/1131695137370669158>Scientific Python Discord server</a>.</p><p>To get familiar with our translation process, read the guide |
| 50 | +for background.) Volunteer translators are at the heart of this effort. If you’d like to help, |
| 51 | +join the<em>translation</em> channel on the |
| 52 | +<ahref=https://discord.com/invite/vur45CbwMz>Scientific Python Discord server</a>.</p><p>To get familiar with our translation process, read the guide |
53 | 53 | <ahref=https://scientific-python-translations.github.io/translate/>How to translate content using Crowdin</a>.</p><h3id=community-coordination-and-outreach>Community coordination and outreach<aclass=headerlinkhref=#community-coordination-and-outreachtitle="Link to this heading">#</a></h3><p>Through community contact we share our work more widely and learn where we’re |
54 | 54 | falling short. We’re eager to get more people involved in efforts like organizing NumPy<ahref=https://scisprints.github.io/>code |
55 | 55 | sprints</a>, a newsletter, and perhaps a blog.</p><h3id=fundraising>Fundraising<aclass=headerlinkhref=#fundraisingtitle="Link to this heading">#</a></h3><p>For many years, NumPy was maintained by dedicated volunteers, but as its importance grew it |
|