Skip to content

Commit f631ca3

Browse files
stefanvstefanv
authored
Add agenda; update planning meeting links (#391)
1 parent b633585 commit f631ca3

3 files changed

Lines changed: 128 additions & 35 deletions

File tree

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

Lines changed: 119 additions & 34 deletions
Original file line numberDiff line numberDiff line change
@@ -7,29 +7,79 @@ authors: ["Brigitta Sipőcz", "K. Jarrod Millman", "Stéfan van der Walt"]
77
date: 2023-01-11
88
---
99

10-
## Goals
11-
12-
The Scientific Python Developer Summit provides an opportunity for core developers
13-
from the scientific Python ecosystem to come together to:
14-
15-
### 1. Improve joint infrastructure
16-
17-
Collaborate to adopt and improve infrastructure, tools, and processes
18-
used across projects. This includes infrastructure already described
19-
in Scientific Python Ecosystem Coordination documents (SPECs), as well
20-
as, but not limited to, tools for documentation, testing, benchmarking,
21-
packaging, and Continuous Integration (CI).
22-
23-
### 2. Better coordinate core projects
24-
25-
A central goal of the Scientific Python project and, by implication, the summit, is to better coordinate maintenance of the different projects.
26-
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.
27-
28-
### 3. Work on a shared strategic plan
29-
30-
The strategic plan will identify core needs and future challenges of the scientific Python community.
31-
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.
32-
The plan will also be used by the community for support when applying for federal grants.
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+
_A friendly reminder that we are guests of the eScience Institute, and
15+
that some members of their research staff will continue working in the space
16+
during our event._
17+
18+
{{< details "**Sunday**" >}}
19+
| Time | Description |
20+
|------|-------------|
21+
| | Arrive |
22+
| | Dinner (self organized) |
23+
{{< /details >}}
24+
25+
{{< details "**Monday**" >}}
26+
| Time | Description |
27+
|------|-------------|
28+
| 9:00 | Breakfast |
29+
| 9:00--9:30 | Welcome & coordination |
30+
| 9:30--13:00 | Work session |
31+
| 13:00--14:30 | Lunch & campus walk |
32+
| 14:30--18:00 | Work session |
33+
| 19:00 | Dinner at [Eureka!](https://goo.gl/maps/g45EmtFn6bjUJSoS6) |
34+
{{< /details >}}
35+
36+
{{< details "**Tuesday**" >}}
37+
| Time | Description |
38+
|------|-------------|
39+
| 9:00 | Breakfast |
40+
| 9:30--13:00 | Work session |
41+
| 13:00--14:30 | Lunch & campus walk |
42+
| 14:30--17:45 | Work session |
43+
| 18:30 | Dinner at [Kate's Pub](https://goo.gl/maps/HBFdQSzNkfKY427W9) |
44+
{{< /details >}}
45+
46+
{{< details "**Wednesday**" >}}
47+
| Time | Description |
48+
|------|-------------|
49+
| 9:00 | Breakfast |
50+
| 9:30--13:00 | Work session |
51+
| 13:00--14:30 | Lunch & campus walk |
52+
| 14:30-- | Work session |
53+
| | Dinner (self organized) |
54+
{{< /details >}}
55+
56+
{{< details "**Thursday**" >}}
57+
| Time | Description |
58+
|------|-------------|
59+
| 9:00 | Breakfast |
60+
| 9:30--13:00 | Work session |
61+
| 13:00--14:30 | Lunch & campus walk |
62+
| 14:30--18:00 | Work session |
63+
| 19:00 | Dinner at [Big Time Brewery & Alehouse](https://goo.gl/maps/E55tA1vifpX9CeC76) |
64+
{{< /details >}}
65+
66+
{{< details "**Friday**" >}}
67+
| Time | Description |
68+
|------|-------------|
69+
| 9:00 | Breakfast |
70+
| 9:30--13:00 | Work session |
71+
| 13:00--14:30 | Lunch & campus walk |
72+
| 14:30--16:00 | Work session |
73+
| 16:00--17:30 | Closing discussion |
74+
| 18:00 | Dinner (self organized) |
75+
{{< /details >}}
76+
77+
{{< details "**Saturday**" >}}
78+
| Time | Description |
79+
|------|-------------|
80+
| | Depart |
81+
| | Breakfast (self organized) |
82+
{{< /details >}}
3383

3484
## Logistics
3585

@@ -50,7 +100,9 @@ The closest station to the hotel is "U-District" (0.3mi away), which is a new st
50100

51101
#### Food
52102

53-
TBA
103+
We have group dinners Monday, Tuesday, and Thursday.
104+
For other evenings (Sunday, Wednesday, Friday), as well as Saturday breakfast, you can request reimbursement.
105+
Please keep all slips, no alcoholic beverages covered, max 20 USD per dinner and 15 USD per breakfast.
54106

55107
### Participants
56108

@@ -59,6 +111,8 @@ such as NumPy, SciPy, matplotlib, xarray, pandas, scikit-image, scikit-learn,
59111
NetworkX, and IPython, as well as domain stacks including Astropy, Pangeo, and
60112
scikit-HEP.
61113

114+
{{< details "**List of participants**" >}}
115+
62116
- Anderson Banihirwe ([@andersy005](https://github.com/andersy005))
63117
- Brigitta Sipőcz ([@bsipocz](https://github.com/bsipocz))
64118
- CJ Carey ([@perimosocordiae](https://github.com/perimosocordiae))
@@ -95,28 +149,50 @@ scikit-HEP.
95149
- Tim Head ([@betatim](https://github.com/betatim))
96150
- Tyler Reddy ([@tylerjereddy](https://github.com/tylerjereddy))
97151

152+
{{< /details >}}
153+
154+
## Goals
155+
156+
The Scientific Python Developer Summit provides an opportunity for core developers
157+
from the scientific Python ecosystem to come together to:
158+
159+
### 1. Improve joint infrastructure
160+
161+
Collaborate to adopt and improve infrastructure, tools, and processes
162+
used across projects. This includes infrastructure already described
163+
in Scientific Python Ecosystem Coordination documents (SPECs), as well
164+
as, but not limited to, tools for documentation, testing, benchmarking,
165+
packaging, and Continuous Integration (CI).
166+
167+
### 2. Better coordinate core projects
168+
169+
A central goal of the Scientific Python project and, by implication, the summit, is to better coordinate maintenance of the different projects.
170+
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.
171+
172+
### 3. Work on a shared strategic plan
173+
174+
The strategic plan will identify core needs and future challenges of the scientific Python community.
175+
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.
176+
The plan will also be used by the community for support when applying for federal grants.
177+
98178
### Dates
99179

100-
Participants will be expected to participate in two of the three planning meetings
101-
and the weekly long summit.
180+
Participants will be expected to participate in at least two planning meetings
181+
as well as the weekly long summit.
102182

103-
- February planning meeting (2023-02-27), see `Meeting 1` below for more info
104-
- March planning meeting (TBD)
105-
- April planning meeting (TBD)
106-
- May 22-26, 2023 Summit
183+
The summit is held May 22-26, 2023 in Seattle, WA.
107184

108-
The planning meetings will have two or three "parallel tracks" so that smaller groups can focus on their subprojects.
109-
Attendees would preferably arrive the day before the summit starts, and stay for the entire duration of the summit.
185+
Attendees should preferably arrive the day before the summit starts, and stay for the entire duration of the summit.
110186

111187
### Pre-Summit Planning
112188

189+
See [planning issues](https://github.com/scientific-python/summit-2023/issues).
190+
113191
Participants will be responsible for attending two or more one-hour video meetings (the planning meetings mentioned above) and for
114192
participating in a planning repository via PRs, issues—as both contributors and reviewers.
115193
There is no heavy top-down structure: participants themselves will organize the work that needs to be done ahead of time.
116194
They will deciding on topics, divide the work, and schedule the meeting.
117195

118-
See the [GitHub issues](https://github.com/scientific-python/summit-2023/issues) for the main topics.
119-
120196
### Summit Execution
121197

122198
The goal of the summit is to be a hands-on work meeting.
@@ -126,3 +202,12 @@ That said, there will be some free time scheduled to brainstorm new ideas, and t
126202

127203
After the meeting, attendees will collaborate on their assigned tasks until completion.
128204
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.
205+
206+
## Meeting notes
207+
208+
- [General (2023-02-27)](general-planning)
209+
- [May 15, Package metrics, DevStats](https://hackmd.io/UNwG2BjJSxOUJ0M1iWI-nQ)
210+
- [May 15, SPECs](https://hackmd.io/MmbP4VTATyG129_U56xdJQ)
211+
- [May 18, Community & Documentation](https://hackmd.io/YL5DNtsaSsS-1ZU3Pxkrxg)
212+
- [May 19, Build Systems & CI Infrastructure](https://hackmd.io/0M1Yh7KwTnaXSsU14BiyQw)
213+
- [May 19, PyTest plugins & Sphinx extentions](https://hackmd.io/JL5slkxORA-q7VRN79v1sA)

content/summits/developer/2023/meeting1.md renamed to content/summits/developer/2023/general-planning.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: "Meeting 1"
2+
title: "General Planning Meeting"
33
---
44

55
## Information

‎layouts/shortcodes/details.html‎

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,8 @@
1+
{{ $summary:= .Get 0 | markdownify }}
2+
{{ $content := .Inner | markdownify }}
3+
<p>
4+
<details>
5+
<summary>{{$summary}}</summary>
6+
<p>{{$content}}</p>
7+
</details>
8+
</p>

0 commit comments

Comments
 (0)