Date: Thursday 11:30 - 12:30 AM
Topics: Documentation, Community Building, Tutorial Infrastructure (SciPy notes)
Issues: #7, #9, #13, #21, #19
Sanket: Building an onboarding guide for newcomers and creating a guide/manual for scientific community managers
lots of documentation on how to begin contributing, but not how to do other things, that does not involve writing code
SPEC for community building and outreach
Sanket has good recommendations on
Juanita has similar document about role of community managers
Sanket
Dan McCloy
Dan Allan
Juanita
Jarrod and Isaac
Ross: One thing I'd personally be interested in is seeing whether/how various tools can be used in conjunction with one another. For example, there are several tutorials sites (numpy-tutorials, nx-guides) built on top of the executable books stack that would also benefit from e.g. the thumbnail feature from sphinx-gallery. It's not immediately obvious how the executablebook sphinx extensions & sphinx-gallery can be used together.
In a similar but broader vein - I'd like to investigate the browser-native tooling and see how well/easily existing tutorial content (based on static site generation) is supported.
Daniel McCloy: There are lots of things that don't need separate documentation for each package; things like
obviously there will be some degree of variability across packages in how each of these things are done, but that's an opportunity for figuring out which ones have a clear best-practice (that could be codified in a SPEC?) and which are cases of "reasonable packages will disagree". For the latter cases, the ecosystem-level tutorial would be either more conceptual (individual package docs fill in the details) or simply not exist.
https://scipy-lectures.org/ (rendered)
Goals
Update sparse
, random, statistics, newer APIs, etc.
May be worth transitioning to Markdown in the long run (myst or similar)
Remove the Py2/Py3 chapter