scientific-python · jarrodmillman · May 18, 2023 · May 18, 2023
diff --git a/content/summits/developer/2023/_index.md b/content/summits/developer/2023/_index.md
@@ -7,29 +7,79 @@ authors: ["Brigitta Sipőcz", "K. Jarrod Millman", "Stéfan van der Walt"]
 date: 2023-01-11
 ---
 
-## 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 coordinate core projects
-
-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.
+## Agenda
+
+The event is held at the [eScience Institute, UW Physics/Astronomy Tower, 6th Floor, 3910 15th Ave NE, Seattle](https://goo.gl/maps/EfkoHtvZad3fYMx77).
+
+_A friendly reminder that we are guests of the eScience Institute, and
+that some members of their research staff will continue working in the space
+during our event._
+
+{{< details "**Sunday**" >}}
+| Time | Description |
+|------|-------------|
+| | Arrive |
+| | Dinner (self organized) |
+{{< /details >}}
+
+{{< details "**Monday**" >}}
+| Time | Description |
+|------|-------------|
+| 9:00 | Breakfast |
+| 9:00--9:30 | Welcome & coordination |
+| 9:30--13:00 | Work session |
+| 13:00--14:30 | Lunch & campus walk |
+| 14:30--18:00 | Work session |
+| 19:00 | Dinner at [Eureka!](https://goo.gl/maps/g45EmtFn6bjUJSoS6) |
+{{< /details >}}
+
+{{< details "**Tuesday**" >}}
+| Time | Description |
+|------|-------------|
+| 9:00 | Breakfast |
+| 9:30--13:00 | Work session |
+| 13:00--14:30 | Lunch & campus walk |
+| 14:30--17:45 | Work session |
+| 18:30 | Dinner at [Kate's Pub](https://goo.gl/maps/HBFdQSzNkfKY427W9) |
+{{< /details >}}
+
+{{< details "**Wednesday**" >}}
+| Time | Description |
+|------|-------------|
+| 9:00 | Breakfast |
+| 9:30--13:00 | Work session |
+| 13:00--14:30 | Lunch & campus walk |
+| 14:30-- | Work session |
+| | Dinner (self organized) |
+{{< /details >}}
+
+{{< details "**Thursday**" >}}
+| Time | Description |
+|------|-------------|
+| 9:00 | Breakfast |
+| 9:30--13:00 | Work session |
+| 13:00--14:30 | Lunch & campus walk |
+| 14:30--18:00 | Work session |
+| 19:00 | Dinner at [Big Time Brewery & Alehouse](https://goo.gl/maps/E55tA1vifpX9CeC76) |
+{{< /details >}}
+
+{{< details "**Friday**" >}}
+| Time | Description |
+|------|-------------|
+| 9:00 | Breakfast |
+| 9:30--13:00 | Work session |
+| 13:00--14:30 | Lunch & campus walk |
+| 14:30--16:00 | Work session |
+| 16:00--17:30 | Closing discussion |
+| 18:00 | Dinner (self organized) |
+{{< /details >}}
+
+{{< details "**Saturday**" >}}
+| Time | Description |
+|------|-------------|
+| | Depart |
+| | Breakfast (self organized) |
+{{< /details >}}
 
 ## Logistics
 
@@ -50,7 +100,9 @@ The closest station to the hotel is "U-District" (0.3mi away), which is a new st
 
 #### Food
 
-TBA
+We have group dinners Monday, Tuesday, and Thursday.
+For other evenings (Sunday, Wednesday, Friday), as well as Saturday breakfast, you can request reimbursement.
+Please keep all slips, no alcoholic beverages covered, max 20 USD per dinner and 15 USD per breakfast.
 
 ### Participants
 
@@ -59,6 +111,8 @@ 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.
 
+{{< details "**List of participants**" >}}
+
 - Anderson Banihirwe ([@andersy005](https://github.com/andersy005))
 - Brigitta Sipőcz ([@bsipocz](https://github.com/bsipocz))
 - CJ Carey ([@perimosocordiae](https://github.com/perimosocordiae))
@@ -95,28 +149,50 @@ scikit-HEP.
 - Tim Head ([@betatim](https://github.com/betatim))
 - Tyler Reddy ([@tylerjereddy](https://github.com/tylerjereddy))
 
+{{< /details >}}
+
+## 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 coordinate core projects
+
+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.
+
 ### Dates
 
-Participants will be expected to participate in two of the three planning meetings
-and the weekly long summit.
+Participants will be expected to participate in at least two planning meetings
+as well as the weekly long summit.
 
-- February planning meeting (2023-02-27), see `Meeting 1` below for more info
-- March planning meeting (TBD)
-- April planning meeting (TBD)
-- May 22-26, 2023 Summit
+The summit is held May 22-26, 2023 in Seattle, WA.
 
-The planning meetings will have two or three "parallel tracks" so that smaller groups can focus on their subprojects.
-Attendees would preferably arrive the day before the summit starts, and stay for the entire duration of the summit.
+Attendees should preferably arrive the day before the summit starts, and stay for the entire duration of the summit.
 
 ### Pre-Summit Planning
 
+See [planning issues](https://github.com/scientific-python/summit-2023/issues).
+
 Participants will be responsible for attending two or more one-hour video meetings (the planning meetings mentioned above) and for
 participating in a planning repository via PRs, issues—as both contributors and reviewers.
 There is no heavy top-down structure: participants themselves will organize the work that needs to be done ahead of time.
 They will deciding on topics, divide the work, and schedule the meeting.
 
-See the [GitHub issues](https://github.com/scientific-python/summit-2023/issues) for the main topics.
-
 ### Summit Execution
 
 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
 
 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.
+
+## Meeting notes
+
+- [General (2023-02-27)](general-planning)
+- [May 15, Package metrics, DevStats](https://hackmd.io/UNwG2BjJSxOUJ0M1iWI-nQ)
+- [May 15, SPECs](https://hackmd.io/MmbP4VTATyG129_U56xdJQ)
+- [May 18, Community & Documentation](https://hackmd.io/YL5DNtsaSsS-1ZU3Pxkrxg)
+- [May 19, Build Systems & CI Infrastructure](https://hackmd.io/0M1Yh7KwTnaXSsU14BiyQw)
+- [May 19, PyTest plugins & Sphinx extentions](https://hackmd.io/JL5slkxORA-q7VRN79v1sA)
diff --git a/content/summits/developer/2023/meeting1.md → ...ummits/developer/2023/general-planning.md b/content/summits/developer/2023/meeting1.md → ...ummits/developer/2023/general-planning.md
@@ -1,5 +1,5 @@
 ---
-title: "Meeting 1"
+title: "General Planning Meeting"
 ---
 
 ## Information

diff --git a/layouts/shortcodes/details.html b/layouts/shortcodes/details.html
@@ -0,0 +1,8 @@
+{{ $summary:= .Get 0 | markdownify }}
+{{ $content := .Inner | markdownify }}
+<p>
+  <details>
+      <summary>{{$summary}}</summary>
+      <p>{{$content}}</p>
+  </details>
+</p>