SciPy 2022 Proposal

Jul 11-17, 2022

https://www.scipy2022.scipy.org/talk-poster-presentations

Scientific Python - By maintainers and for maintainers

Short Summary

The future of Scientific Python is here. Behind the scenes, core scientific projects have started coordinating to better unify the community. Learn more about the goals of this unification effort, opportunities that exist, and, most importantly, how to join the adventure.

Abstract

The Scientific Python project's vision is to help pave the way towards a unified, expanded scientific Python community. It focuses its efforts along two primary axes: (i) to create a joint community around all scientific projects and (ii)_to support maintainers by building cross-cutting technical infrastructure and tools. This talk will focus on the second aspect, presenting current and future initiatives.

The project has already launched a process whereby projects can, voluntarily, adopt reference guidelines; these are known as SPECs or Scientific Python Ecosystem Coordination documents. SPECs are similar to projects specific guidelines like PEPs, NEPs, SLEPs, and SKIPs, to name a few. The distinction being that SPECs have a broader scope, targeted at all (or most) projects from the scientific Python ecosystem.

The project also provides and maintains tools to help maintainers. This includes a theme for the project websites (currently used on, e.g., numpy.org and scipy.org), a self-hosted privacy-friendly web analytics platform, a community discussions forum, a technical blog, and project development statistics.

We present all these tools, discuss various upcoming SPECs, and highlight the project's future potential.

The talk closes with a general call to action. The Scientific Python project is already supported by eight core projects: IPython, Matplotlib, NetworkX, NumPy, pandas, scikit-image, scikit-learn, and SciPy. The organization has spent the last several months working on the infrastructure, and is now ready to engage more widely to help grow and support the community.

Other information

Track: Maintainers
Author: Pamphile T. Roy
Keywords: Scientific Python, Community
Type: Talk

Random stuff to talk about during the presentation?

Activities:

  • Community owned blog
  • SPECs
  • Theme for org websites
  • Hosted metrics
  • devstats
  • numpydoc ?? What about it? Linked to the project?

Example of ideas for SPECs (or other):

  • security auditing
  • community wide maintainers: separate relationship of people. Ex. commit rights does not mean "core" maintainer.
  • accessibility on images
  • release flow
  • CI (shared GH actions? imagine CD of all the stack on some events 🤯)
  • shared dockerfiles and other devOps things
  • general guidelines
  • formatting guidelines -> black like everyone right now…
  • guidelines for contributing
  • … more in my head if I give it more time 😅
Select a repo