Skip to content

Commit dae512a

Browse files
jarrodmillmanbsipocz
jarrodmillman
and
bsipocz
authored
Add summit 2024 page (#584)
* Add summit 2024 page * Update content/summits/developer/2024/_index.md Co-authored-by: Brigitta Sipőcz <b.sipocz@gmail.com> --------- Co-authored-by: Brigitta Sipőcz <b.sipocz@gmail.com>
1 parent d258a1b commit dae512a

1 file changed

Lines changed: 194 additions & 0 deletions

File tree

‎content/summits/developer/2024/_index.md‎

Lines changed: 194 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,194 @@
1+
---
2+
title: 2024 Developer Summit
3+
subtitle: The Second Scientific Python Developer Summit
4+
summary: |
5+
The second Scientific Python Developer Summit (June 3-7, 2024) 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.
6+
authors: ["Brigitta Sipőcz", "K. Jarrod Millman", "Stéfan van der Walt"]
7+
date: 2024-03-05
8+
---
9+
10+
## Agenda
11+
12+
The event is held at the [eScience Institute, UW Physics/Astronomy Tower, 6th Floor, 3910 15th Ave NE, Seattle](https://goo.gl/maps/EfkoHtvZad3fYMx77).
13+
14+
<br/>
15+
<iframe
16+
src="https://www.google.com/maps/d/embed?mid=1eWqjU_k7dkYF8Z58sNQ9zJaYbR8HXPM&ehbc=2E312F"
17+
width="100%" height="480"
18+
>
19+
</iframe>
20+
&nbsp;<br/>
21+
22+
_A friendly reminder that we are guests of the eScience Institute, and
23+
that some members of their research staff will continue working in the space
24+
during our event._
25+
26+
&nbsp;<br/>
27+
28+
{{< details "**Sunday**" >}}
29+
| Time | Description |
30+
|------|-------------|
31+
| | Arrive |
32+
| | Dinner (self organized) |
33+
{{< /details >}}
34+
35+
{{< details "**Monday**" >}}
36+
| Time | Description |
37+
|------|-------------|
38+
| 08:40 | Meet in hotel lobby (or 9am at eScience) |
39+
| 9:00 | Breakfast |
40+
| 9:00--9:30 | Welcome & coordination |
41+
| 9:30--13:00 | Work session |
42+
| 13:00--14:30 | Lunch & campus walk |
43+
| 14:30--17:00 | Work session |
44+
| 17:30--18:00 | Check-in |
45+
| 16:00--17:30 | Closing discussion |
46+
| 18:00 | Dinner (self organized) |
47+
{{< /details >}}
48+
49+
{{< details "**Tuesday**" >}}
50+
| Time | Description |
51+
|------|-------------|
52+
| 9:00 | Breakfast |
53+
| 9:30--13:00 | Work session |
54+
| 13:00--14:30 | Lunch & campus walk |
55+
| 14:30--17:00 | Work session |
56+
| 17:15--17:45 | Check-in |
57+
| 16:00--17:30 | Closing discussion |
58+
| 18:00 | Dinner (self organized) |
59+
{{< /details >}}
60+
61+
{{< details "**Wednesday**" >}}
62+
| Time | Description |
63+
|------|-------------|
64+
| 9:00 | Breakfast |
65+
| 9:30--13:00 | Work session |
66+
| 13:00--14:30 | Lunch & campus walk |
67+
| 14:30--17:00 | Work session |
68+
| 17:30--18:00 | Check-in |
69+
| 16:00--17:30 | Closing discussion |
70+
| 18:00 | Dinner (self organized) |
71+
{{< /details >}}
72+
73+
{{< details "**Thursday**" >}}
74+
| Time | Description |
75+
|------|-------------|
76+
| 9:00 | Breakfast |
77+
| 9:30--13:00 | Work session |
78+
| 13:00--14:30 | Lunch & campus walk |
79+
| 14:30--17:00 | Work session |
80+
| 17:30--18:00 | Check-in |
81+
| 16:00--17:30 | Closing discussion |
82+
| 18:00 | Dinner (self organized) |
83+
{{< /details >}}
84+
85+
{{< details "**Friday**" >}}
86+
| Time | Description |
87+
|------|-------------|
88+
| 9:00 | Breakfast |
89+
| 9:30--13:00 | Work session |
90+
| 13:00--14:30 | Lunch & campus walk |
91+
| 14:30--16:00 | Work session |
92+
| 16:00--17:30 | Closing discussion |
93+
| 18:00 | Dinner (self organized) |
94+
{{< /details >}}
95+
96+
{{< details "**Saturday**" >}}
97+
| Time | Description |
98+
|------|-------------|
99+
| | Depart |
100+
| | Breakfast (self organized) |
101+
{{< /details >}}
102+
103+
## Logistics
104+
105+
We have funding (i.e., for travel, food, and lodging) and space for 40 participants for five days and six nights.
106+
This will be an invite-only event that requires upfront agreement to:
107+
(a) take part in two of the three one-hour pre-summit planning meetings,
108+
(b) collaborate with fellow participants on a work plan,
109+
(c) attend the one-week summit in-person, and
110+
(d) participate, to whatever degree possible, in several months of post-summit implementation.
111+
112+
### Local Logistics
113+
114+
#### Airport to hotel
115+
116+
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.
117+
We recommend using Link Light Rail to get from the airport to the hotel. It takes approximately an hour and costs $3.25.
118+
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".
119+
120+
#### Food
121+
122+
Please keep all slips, no alcoholic beverages covered, max 20 USD per dinner and 15 USD per breakfast.
123+
124+
### Participants
125+
126+
Participants are recruited from the community of developers of packages
127+
such as NumPy, SciPy, matplotlib, xarray, pandas, scikit-image, scikit-learn,
128+
NetworkX, and IPython, as well as domain stacks including Astropy, Pangeo, and
129+
scikit-HEP.
130+
131+
{{< details "**List of participants** (we add names to the list as they confirm attendance)" >}}
132+
133+
- Brigitta Sipőcz ([@bsipocz](https://github.com/bsipocz))
134+
- Jarrod Millman ([@jarrodmillman](https://github.com/jarrodmillman))
135+
- Matthias Bussonnier ([@Carreau](https://github.com/Carreau))
136+
- Stéfan van der Walt ([@stefanv](https://github.com/stefanv))
137+
138+
{{< /details >}}
139+
140+
## Goals
141+
142+
The Scientific Python Developer Summit provides an opportunity for core developers
143+
from the scientific Python ecosystem to come together to:
144+
145+
### 1. Improve joint infrastructure
146+
147+
Collaborate to adopt and improve infrastructure, tools, and processes
148+
used across projects. This includes infrastructure already described
149+
in Scientific Python Ecosystem Coordination documents (SPECs), as well
150+
as, but not limited to, tools for documentation, testing, benchmarking,
151+
packaging, and Continuous Integration (CI).
152+
153+
### 2. Better coordination of the ecosystem
154+
155+
A central goal of the Scientific Python project and, by implication, the summit, is to better coordinate maintenance of the different projects.
156+
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.
157+
158+
### 3. Work on a shared strategic plan
159+
160+
The strategic plan will identify core needs and future challenges of the scientific Python community.
161+
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.
162+
The plan will also be used by the community for support when applying for federal grants.
163+
164+
### Dates
165+
166+
Participants will be expected to participate in at least two planning meetings
167+
as well as the weekly long summit.
168+
169+
The summit is held June 3-7, 2024 in Seattle, WA.
170+
171+
Attendees should preferably arrive the day before the summit starts, and stay for the entire duration of the summit.
172+
173+
### Pre-Summit Planning
174+
175+
See [planning issues](https://github.com/scientific-python/summit-2024/issues).
176+
177+
Participants will be responsible for attending two or more one-hour video meetings (the planning meetings mentioned above) and for
178+
participating in a planning repository via PRs, issues—as both contributors and reviewers.
179+
There is no heavy top-down structure: participants themselves will organize the work that needs to be done ahead of time.
180+
They will deciding on topics, divide the work, and schedule the meeting.
181+
182+
### Summit Execution
183+
184+
The goal of the summit is to be a hands-on work meeting.
185+
That said, there will be some free time scheduled to brainstorm new ideas, and to discuss current community projects and activities.
186+
187+
### Post-Summit Implementation
188+
189+
After the meeting, attendees will collaborate on their assigned tasks until completion.
190+
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.
191+
192+
## Meeting notes
193+
194+
...

0 commit comments

Comments
 (0)