This document: https://hackmd.io/@scientific-python/bof2024

Scientific Python Ecosystem Coordination (SPEC) documents (https://scientific-python.org/specs/) provide operational guidelines for projects in the scientific Python ecosystem. SPECs are similar to project-specific guidelines (like PEPs, NEPs, SLEPs, and SKIPs), but are opt-in, have a broader scope, and target all (or most) projects in the scientific Python ecosystem. Come hear more about what we are working on and planning. Better yet, come share your ideas for improving the ecosystem!

SPEC repository: https://github.com/scientific-python/specs

- [Link to Slides](https://docs.google.com/presentation/d/1X3gb4qWu5Ui8AzvSkkwosJ6ookmqwIRPZ8-XFBQ7FBQ/edit#slide=id.g13b5fa603fb_0_0)

## Attendees

~ 45-50 people, See bsipocz's photo

## Goal:

Determine some potential action points that we can get collaboration with from the community.

## Current specs

SPEC 0 — Minimum Supported Versions
SPEC 1 — Lazy Loading of Submodules and Functions
SPEC 2 — API Dispatch
SPEC 3 — Accessibility
SPEC 4 — Using and Creating Nightly Wheels

## In progress specs

SPEC 7 — Seeding pseudo-random number generation
SPEC 8 — Securing the Release Process
SPEC 9 — Governance
SPEC 10 — Release documentation
SPEC 11 — ~~API observability~~ Vulnerability Disclosure
SPEC 12 — Math Formatting
SPEC 13 — Recommended targets and naming conventions
SPEC 14 — GitHub Enterprise
SPEC 15 — Vulnerability Disclosure
SPEC .. — CI best practices for Tutorials

## Discussion topics

-  is for new SPEC ideas

- Where is SP located, is it Berkeley?
- various places
- not with the goal of centralize it
- initial funding by Moore Foundation
- Project layout / template
- We do have learn.scientific-python.org
- for package template/layout/best-practices: https://github.com/scientific-python/cookie

- Project Governance
- There is a [SPEC draft for Governance](https://github.com/scientific-python/specs/pull/323), see the list above

-  What about a policy for AI generated code
- Came up already within numpy, and also scikit-learn
- 🔧 That should probably a SPEC.

- Something about downstream testing/coordinated cross project testing.

-  SPEC (or maybe it's a NEP scope) for exotic dtypes

- Question to show what's in SPEC 12
- Formatting math-operators https://discuss.scientific-python.org/t/how-to-format-mathematical-expressions/62

- SPEC0
- The SPEC0 is a recommendation to support the maintainers of libraries, you can always maintain older versions if you have the bandwidth to do it.

- Analytics
- https://github.com/scientific-python/summit-2024/issues/1

- Open SSF, what about the intersection, are there any plans for closer collaboration?
- The goal is to reduce duplication of efforts. Open to collaborations. Feel free to bring ideas.

- Standardization of APIs
- There were talks last year's SciPy around standardization of the array specification

- Any tools to automate checking of SPEC compliance (at least for the ones that is possible)?
- for SPEC0 drop schedule there is a short script that lists versions to drop by quarters
- There's one for checking the structure of the repository
- Repo review: https://learn.scientific-python.org/development/guides/repo-review/

- ? Centralize the Code of Conduct?
- Something similar to https://www.contributor-covenant.org/?
- audience is skeptical that this should be done by scientific python, it should go upstream and we should instead use contributor-covenant/PSF/NF etc.
- Scientific Python can recommend certain CoC structure as part of a SPEC. That doesn't mean that SP will enforce CoC on projects that follow those recommendations, nor have responsability for any non-enforced CoC.