# Scientific Python Lorentz workshop

===========

## Deadline: 30 January
### Resources
https://www.lorentzcenter.nl/organize-a-workshop.html

application instructions: https://www.lorentzcenter.nl/uploadedfiles/lorentz%20center%20workshop%20application%20instructions%20-%20nov2023%20-%20648ad4fc4e420%20-%206552296d4e541.pdf

===========

## Proposal

### Title
Scientific Python Developer Summit

(first to be held in Europe)

### Organizers

- Jarrod
- Stéfan
- Brigitta

### Scientific case

#### Background

#### Aims and scope

The Scientific Python Developer Summit provides an opportunity for core developers from the scientific Python ecosystem to come together to 1) better coordinate the ecosystem, 2) improve joint infrastructre 3) work on shared strategic plan

#### Previous successes

In 2023 we held the first Scientific Python Developer Summit at the eScience Institue at the University of Washington in Seattle.

https://scientific-python.org/summits/developer/2023/
https://blog.scientific-python.org/scientific-python/dev-summit-1/

#### Challenges

(trying to come up with phrasing challanges)
- geographical -- having a summit not at west coast USA will make it better/easier for a lot of people traveling wise (maybe for visa, too?)
- finding unique spaces that are suitable for the highly collaborative dinamics where the group most thrive on
- individal libraries to pull resources into an upstream, shared infrastructure and policies

=====

#### notes from previous year

Goals

The Scientific Python Developer Summit provides an opportunity for core developers from the scientific Python ecosystem to come together to:

1. Improve joint infrastructure
Collaborate to adopt and improve infrastructure, tools, and processes used across projects. This includes infrastructure already described in Scientific Python Ecosystem Coordination documents (SPECs), as well as, but not limited to, tools for documentation, testing, benchmarking, packaging, and Continuous Integration (CI).

2. Better coordination of the ecosystem
A central goal of the Scientific Python project and, by implication, the summit, is to better coordinate maintenance of the different projects. We want to write up a maintenance manual with community best practices, agree on a common release schedule, establish channels for regular cross-project communication, and decide on joint governance structures.

3. Work on a shared strategic plan
The strategic plan will identify core needs and future challenges of the scientific Python community. Rather than focusing on the technical details of one particular project or domain area, the strategic plan would discuss the challenges shared across projects and domains. The plan will also be used by the community for support when applying for federal grants.

=====

### Program

=====
copied from eScience

Pre-Summit Planning
Participants will be responsible for attending two or more one-hour
video meetings and for participating in a planning repository via
PRs, issues—as both contributors and reviewers. The work plan
will be decided before the meeting, and includes deciding on topics,
dividing the work, and scheduling the meeting.

Summit Execution
We do not need the entire group to meet in one room at the same
time, because work will be planned and subdivided beforehand.

Post-Summit Implementation
After the meeting, attendees will collaborate on their assigned tasks
until completion. The Scientific Python project also has funding to
further develop some of these tasks, and will apply for additional
funds to complete some of the rest.

====

https://scientific-python.org/summits/developer/2023/
https://blog.scientific-python.org/scientific-python/dev-summit-1/

### Participants

Participants will be recruited from the community of developers al-
ready actively engaged with the Scientific Python project. Developers
will represent packages such as NumPy, SciPy, matplotlib, xarray,
pandas, scikit-image, scikit-learn, NetworkX, and IPython, as well as
domain stacks including Astropy, Pangeo, and scikit-HEP.

Key participants:

(*** copy paste from the first summit, to be adjusted)

Anderson Banihirwe (@andersy005)
Brigitta Sipőcz (@bsipocz)
CJ Carey (@perimosocordiae)
Dan Allan (@danielballan)
Dan McCloy (@drammock)
Dan Schult (@dschult)
Greg Lee (@grlee77)
Henry Schreiner (@henryiii)
Inessa Pawson (@InessaPawson)
Isaac Virshup (@ivirshup)
Jarrod Millman (@jarrodmillman)
Jim Pivarski (@jpivarski)
John Kirkham (@jakirkham)
Juanita Gomez (@juanis2112)
Julien Jerphanion (@jjerphan)
Kira Evans (@kne42)
Kyle Sunden (@ksunden)
Lars Grüter (@lagru)
Leah Wasser (@lwasser)
Levi Wolf (@ljwolf)
Madicken Munk (@munkm)
Martin Fleischmann (@martinfleis)
Matt Haberland (@mdhaber)
Matthias Bussonnier (@Carreau)
Mridul Seth (@MridulS)
Pamphile Roy (@tupui)
Paul Ivanov (@ivanov)
Pey Lian Lim (@pllim)
Ross Barnowski (@rossbar)
Sanket Verma (@MSanKeys963)
Sarah Kaiser (@crazy4pi314)
Sebastian Berg (@seberg)
Stéfan van der Walt (@stefanv)
Tim Head (@betatim)
Tyler Reddy (@tylerjereddy)

### Budget

For the first Scientific Python Developer Summit the eScience institute provided the space while we covered catering, travel, and accommodation costs of most participants. We worked off the following budget:

...

### Dates