|
| 1 | +--- |
| 2 | +title: 2025 Developer Summit |
| 3 | +subtitle: | |
| 4 | + The Third Scientific Python Developer Summit |
| 5 | + 11-15 May 2025 – Seattle, WA |
| 6 | +summary: | |
| 7 | + The third Scientific Python Developer Summit (May 11-15, 2025) will be hosted by the eScience Institute at the University of Washington. The week-long summit will bring together forty participants, who will develop shared infrastructure for libraries in the Scientific Python ecosystem. |
| 8 | +authors: |
| 9 | + [ |
| 10 | + "Brigitta Sipőcz", |
| 11 | + "K. Jarrod Millman", |
| 12 | + "Kirstie Whitaker", |
| 13 | + "Stéfan van der Walt", |
| 14 | + ] |
| 15 | +date: 2025-03-05 |
| 16 | +--- |
| 17 | + |
| 18 | +## During the event |
| 19 | + |
| 20 | +Coming soon. |
| 21 | + |
| 22 | +## Agenda |
| 23 | + |
| 24 | +<style type="text/css"> |
| 25 | +table { |
| 26 | + margin-left: 0 !important; |
| 27 | +} |
| 28 | +</style> |
| 29 | + |
| 30 | +{{< details "**Saturday**" >}} |
| 31 | +| Time | Description | |
| 32 | +|------|-------------| |
| 33 | +| | Arrive | |
| 34 | +{{< /details >}} |
| 35 | + |
| 36 | +{{< details "**Sunday**" >}} |
| 37 | +| Time | Description | |
| 38 | +|------|-------------| |
| 39 | +| 09:00 | Meet at eScience | |
| 40 | +{{< /details >}} |
| 41 | + |
| 42 | +{{< details "**Monday**" >}} |
| 43 | +| Time | Description | |
| 44 | +|------|-------------| |
| 45 | +| 09:00 | Meet at eScience | |
| 46 | +{{< /details >}} |
| 47 | + |
| 48 | +{{< details "**Tuesday**" >}} |
| 49 | +| Time | Description | |
| 50 | +|------|-------------| |
| 51 | +| 09:00 | Meet at eScience | |
| 52 | +{{< /details >}} |
| 53 | + |
| 54 | +{{< details "**Wednesday**" >}} |
| 55 | +| Time | Description | |
| 56 | +|------|-------------| |
| 57 | +| 09:00 | Meet at eScience | |
| 58 | +{{< /details >}} |
| 59 | + |
| 60 | +</div> |
| 61 | + |
| 62 | +The event is held at the [eScience Institute, UW Physics/Astronomy Tower, 6th Floor, 3910 15th Ave NE, Seattle](https://goo.gl/maps/EfkoHtvZad3fYMx77). |
| 63 | + |
| 64 | +_A friendly reminder that we are guests of the eScience Institute, and |
| 65 | +that some members of their research staff will continue working in the space |
| 66 | +during our event._ |
| 67 | + |
| 68 | +<br/> |
| 69 | +<iframe |
| 70 | + src="https://www.google.com/maps/d/embed?mid=1eWqjU_k7dkYF8Z58sNQ9zJaYbR8HXPM&ehbc=2E312F" |
| 71 | + width="100%" height="480" |
| 72 | +> |
| 73 | +</iframe> |
| 74 | +
|
| 75 | +## Funding |
| 76 | + |
| 77 | +Unlike previous years, participation costs for this year's summit are covered |
| 78 | +only for those invited as part of the special track on statistics (for that, we have targeted grant funding). |
| 79 | + |
| 80 | +Project maintainers, please reach out to your individual projects to determine |
| 81 | +whether they have funds to sponsor your attendance. |
| 82 | + |
| 83 | +## Logistics |
| 84 | + |
| 85 | +We have space for 40 participants for three days and four nights. |
| 86 | +This will be an invite-only event that requires upfront agreement to: |
| 87 | +(a) take part in one or more pre-summit planning meetings, |
| 88 | +(b) collaborate with fellow participants on a work plan, |
| 89 | +(c) attend the summit in-person, and |
| 90 | +(d) participate, to whatever degree possible, in several months of post-summit implementation. |
| 91 | + |
| 92 | +### Airport to hotel |
| 93 | + |
| 94 | +There is no need to get a rental car or taxi/ride-share, as the airport and the UW campus area is well-served by bus and rail. |
| 95 | +We recommend using Link Light Rail to get from the airport to the hotel. It takes approximately an hour and costs $3.25. |
| 96 | +The closest station to the hotel is "U-District" (0.3mi away), which is a new station opened in 2021 and is not to be confused with the station in Downtown called, "University St", neither with "University of Washington". |
| 97 | + |
| 98 | +### Food |
| 99 | + |
| 100 | +Coming soon |
| 101 | + |
| 102 | +### Participants |
| 103 | + |
| 104 | +Participants are recruited from the community of developers of packages |
| 105 | +such as NumPy, SciPy, matplotlib, xarray, pandas, scikit-image, scikit-learn, |
| 106 | +NetworkX, and IPython, as well as domain stacks including Astropy, Pangeo, and |
| 107 | +scikit-HEP. |
| 108 | + |
| 109 | +{{< details "**List of participants** (we add names to the list as they confirm attendance)" >}} |
| 110 | + |
| 111 | +- Brigitta Sipőcz ([@bsipocz](https://github.com/bsipocz)) |
| 112 | +- Jarrod Millman ([@jarrodmillman](https://github.com/jarrodmillman)) |
| 113 | +- Kirstie Whitaker ([@KirstieJane](https://github.com/KirstieJane)) |
| 114 | +- Stéfan van der Walt ([@stefanv](https://github.com/stefanv)) |
| 115 | + |
| 116 | +{{< /details >}} |
| 117 | + |
| 118 | +## About |
| 119 | + |
| 120 | +### Goals |
| 121 | + |
| 122 | +The 2025 Scientific Python Developer Summit will focus on statistics, optimization, sparse data, plotting, and dataframes. |
| 123 | + |
| 124 | +The Developer Summit provides an opportunity for core developers |
| 125 | +from the scientific Python ecosystem to come together to: |
| 126 | + |
| 127 | +#### 1. Improve joint infrastructure |
| 128 | + |
| 129 | +Collaborate to adopt and improve infrastructure, tools, and processes |
| 130 | +used across projects. This includes infrastructure already described |
| 131 | +in Scientific Python Ecosystem Coordination documents (SPECs), as well |
| 132 | +as, but not limited to, tools for documentation, testing, benchmarking, |
| 133 | +packaging, and Continuous Integration (CI). |
| 134 | + |
| 135 | +#### 2. Better coordination of the ecosystem |
| 136 | + |
| 137 | +A central goal of the Scientific Python project and, by implication, the summit, is to better coordinate maintenance of the different projects. |
| 138 | + |
| 139 | +#### 3. Work on shared strategic goals |
| 140 | + |
| 141 | +A strategic plan would identify core needs and future challenges of the scientific Python community. |
| 142 | +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. |
| 143 | +The plan can be used by the community as supporting evidence when applying for grants. |
| 144 | + |
| 145 | +### Dates |
| 146 | + |
| 147 | +The summit is held May 11-15, 2025 in Seattle, WA. |
| 148 | + |
| 149 | +Attendees should preferably arrive the day before the summit starts, and stay for the entire duration of the summit. |
| 150 | + |
| 151 | +### Pre-Summit Planning |
| 152 | + |
| 153 | +See [planning issues](https://github.com/scientific-python/summit-2025/issues). |
| 154 | + |
| 155 | +Participants will be responsible for attending two or more one-hour video meetings (the planning meetings mentioned above) and for |
| 156 | +participating in a planning repository via PRs, issues—as both contributors and reviewers. |
| 157 | +There is no heavy top-down structure: participants themselves will organize the work that needs to be done ahead of time. |
| 158 | +They will decide on topics, divide the work, and schedule the meeting. |
| 159 | + |
| 160 | +### Summit Execution |
| 161 | + |
| 162 | +The goal of the summit is to be a hands-on work meeting. |
| 163 | +That said, there will be some free time scheduled to brainstorm new ideas, and to discuss current community projects and activities. |
| 164 | + |
| 165 | +### Post-Summit Implementation |
| 166 | + |
| 167 | +After the meeting, attendees will collaborate on their assigned tasks until completion. |
| 168 | + |
| 169 | +## Meeting notes |
| 170 | + |
| 171 | +To be posted. |
0 commit comments