People
Spyder grows because educators, researchers, and industry contributors invest time in documentation, translations, and careful issue reports. This page outlines how you can help without needing to ship a massive feature on day one.
Translate short tutorials, record silent walkthroughs, or add worked examples that match the courses you already teach. Link peers to the documentation hub on this site so everyone shares the same baseline steps.
Open documentation hubWhen you find a regression, capture your Spyder version, Python version, operating system, and minimal script. Structured reports help maintainers reproduce bugs quickly.
See FAQ for diagnosticsHost brown bag sessions that walk through the variable explorer, debugger, and plotting panes. Pair newcomers with a checklist so they feel confident before touching production data.
Browse workflow articlesOpen source projects need predictable funding for CI machines, security reviews, and contributor travel. Consider recurring support through your organization’s philanthropy budget.
Read donate guidance