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 Attendees ~ 45-50 people, See bsipocz's photo

Description Core Project Endorsement Ecosystem Adoption Implementation Notes

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 Attendees Juanita Gomez Jarrod Millman Dan Schult

Trying to update numpydoc to be more explicit about single backticks to refer to parameters https://github.com/numpy/numpydoc/pull/525 and https://github.com/scientific-python/summit-2024/issues/22 PRs created:pydata-sphinx-theme issue backloghttps://github.com/pydata/pydata-sphinx-theme/pull/1849 https://github.com/pydata/pydata-sphinx-theme/pull/1850 https://github.com/pydata/pydata-sphinx-theme/pull/1867 https://github.com/pydata/pydata-sphinx-theme/pull/1861 https://github.com/scientific-python/upload-nightly-action/issues/82 Add prototype of static "intime" analysis -- docstub#2 Disable ruff/pyupgrade rule UP038 -- scikit-image#7430

title: "SPEC 8 — Securing the Release Process" number: 8 date: 2024-06-04 author: "Matthew Feickert matthew.feickert@cern.ch" "Pamphile Roy roy.pamphile@gmail.com" "Juanita Gomez juanitagomezr2112@gmail.com" "Seth Larson sethmichaellarson@gmail.com" "Lars Grüter lagru@mailbox.org"

Information Date: Friday, May 3rd 9AM - 10AM Pacific time (click for your timezone) Zoom Link: https://ucsc.zoom.us/j/91723472248?pwd=U2oyY0NScUZsWnY4UlFodkUwcFFUZz09 Discord invite link Participants Jarrod Millman Matthias Bussonnier Matthew Feickert (@matthewfeickert) Lars Grüter (@lagru)

The Scientific Python Community Coordination https://scientific-python.org/ - https://scientific-python.org/specs/ How can we know which projects support the spec? Projects can “Endorse” the spec.This does not mean that you implement, or can implement, but that you agree with the idea. There are a few “core” projects. Where can projects support the specs ? https://github.com/scientific-python/specs

Date: October 3rd 9:00AM PDT Topic: SPECs Attendees Jarrod Millman Madicken Munk Relevant Links Scientific Python - Scientific Python Ecosystem Coordination GitHub - scientific-python/specs: Scientific Python Ecosystem Coordination (SPEC) documents

The aim of the sprint is to provide a collaborative space where you can make progress on topics which are esencial for the Scientific Python ecosystem. Topics may include (but aren't limited to) tooling, release management, writing / implementing new SPECS, working on the SciPy sparse array interface, documentation, better integration of core packages. TODO (Before Sprint) [ ] Write a contributing guide to contribute to the learn repo (Contributing.MD) [ ] Open issues about things we think people can contribute with List of topics to work on during the sprint SPECs (both new and supporting infrastructure) Build Systems CI Infrastructure

This form is to request a time-slot for a Birds-of-a-Feather (Bof) session at SciPy 2023. The questions are meant to assist the organizers with scheduling BoFs, and should not be construed as “gate-keeping” questions. The organizers will prioritize a solution with a diverse set of BoF subjects that allows the highest expected level of attendee participation. The deadline to submit a BoF is June 17. Due to scheduling constraints, there are a limited number of BoF slots available and we might not be able to accept all submissions. Notifications of acceptance will be sent shortly after the deadline. Indicates required question Please provide a title of the BoF?* Governance in the scientific Python ecosystem Please provide the abstract describing your BoF?*

This form is to request a time-slot for a Birds-of-a-Feather (Bof) session at SciPy 2023. The questions are meant to assist the organizers with scheduling BoFs, and should not be construed as “gate-keeping” questions. The organizers will prioritize a solution with a diverse set of BoF subjects that allows the highest expected level of attendee participation. The deadline to submit a BoF is June 17. Due to scheduling constraints, there are a limited number of BoF slots available and we might not be able to accept all submissions. Notifications of acceptance will be sent shortly after the deadline. Indicates required question Please provide a title of the BoF?* Scientific Python Ecosystem Coordination Please provide the abstract describing your BoF?*

Date: Thursday 11:30 - 12:30 AM Topics: Documentation, Community Building, Tutorial Infrastructure (SciPy notes) Issues: #7, #9, #13, #21, #19 Attendees Juanita Gomez Dan McCloy Paul Ivanov Sanket Verma Matt Haberland

Date: Friday 1:00 - 2:00 PM Topics: Pytest plugins, Sphinx extensions Issues: #10 Attendees Juanita Gomez (async) Dan McCloy Jarrod Millman Ross Barnowski (rossbar) Brigitta Sipőcz

Date: Monday 9:00 - 10:00 AM Topics: Package Metrics and DevStats Issues: #12, #17 Attendees Juanita Gomez, Jim Pivarski (@jpivarski), Matthias Bussonnier, Tim H (@betatim), Madicken Munk, leah wasser (@lwasser), Henry Schreiner (@henryiii), Jarrod Millman (jarrodmillman), Inessa Pawson (inessapawson), Sebastian Berg (@seberg) Planning issues https://github.com/scientific-python/summit-2023/issues/17 https://github.com/scientific-python/summit-2023/issues/12

Information Date: Monday, February 27th 9AM - 10AM Pacific time (click for your timezone) Zoom Link: https://caltech.zoom.us/j/87686129450 Discord invite link Summit topic planner Participants Jarrod Millman Stéfan van der Walt Brigitta Sipőcz (@bsipocz)

Hi Andy, Thanks for considering our request. I've responded to your questions (inline) below. We are fairly flexible, so we are happy to work within your constraints. Since we are planning to ask a lot from attendees leading up to, during, and after the meeting, we won't know who can attend until we finalize the dates. And we won't know what we can work on until we know who is attending. I understand this makes planning difficult and we will need to be flexible. On Thu, Oct 20, 2022 at 10:46 AM Andrew J Connolly ajc@astro.washington.edu wrote: 1. Will you have parts of the meeting when everyone will be in the same room (e.g. opening discussions)

February 4--5th, 2023 https://fosdem.org/2023/news/2022-09-29-call_for_devrooms/ https://www.scipy2022.scipy.org/talk-poster-presentations Devroom 2019: https://archive.fosdem.org/2019/schedule/tracks/ pentabarf username: jarrodmillman, juanis2112, yuvipanda, tupui, stefanv

keep this authoritative (i.e., control authorship): small editorial board w/ long-term "chapter" authors / owners move old editors to emeritus, create new board: Pierre, Jarrod, Stefan, (and Nelle?) Jarrod will recruit (in consultation with board) new "chapter" authors / owners Use case

Project homepage BOF Slides Issue (Shirt raffle) https://github.com/scientific-python/scientific-python.org/issues/264 Social media YouTube ScientificPython-org Twitter @scientific_py

Intros - Ralf Background: discussion here: https://labs.quansight.org/blog/2021/11/pydata-extensibility-vision https://discuss.scientific-python.org/t/a-proposed-design-for-supporting-multiple-array-types-across-scipy-scikit-learn-scikit-image-and-beyond/131 Coordinated approach, break from the new-package-per-hardware paradigm Decision-making, timeframes - coordinated across projects