Skip to content

Commit 6a58f46

Browse files
Agenda for first meeting (#365)
* Add notes from first meeting * Adding infra topics --------- Co-authored-by: Brigitta Sipőcz <b.sipocz@gmail.com>
1 parent 83cc54d commit 6a58f46

2 files changed

Lines changed: 67 additions & 0 deletions

File tree

Lines changed: 67 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,67 @@
1+
---
2+
title: "Meeting 1"
3+
---
4+
5+
## Information
6+
7+
- Date: Monday, [February 27th 9AM - 10AM Pacific time (click for your timezone)](https://www.timeanddate.com/worldclock/converter.html?iso=20230227T170000&p1=224)
8+
- Zoom Link: https://caltech.zoom.us/j/87686129450
9+
10+
## Participants
11+
12+
- Jarrod Millman
13+
- Stéfan van der Walt
14+
- Brigitta Sipőcz
15+
- Juanita Gomez
16+
17+
## Agenda
18+
19+
The summit is scheduled for 1 hour and will consist of a series of high-level
20+
birds-of-a-feather (BoF)-style talks, followed by more focused discussion.
21+
22+
1. (5 min) Welcome & Introductions (Jarrod Millman)
23+
24+
2. (10 min) Logistics
25+
26+
3. (30) Meeting Topics
27+
28+
- Jarrod Millman: Goal
29+
30+
- Unique opportunity to work on cross-project concerns
31+
- We should think big, but focus on achievable short-term goals
32+
33+
- Stéfan van der Walt: Build systems
34+
35+
- Starting to see Meson emerge as an excellent build option for compiled Scientific Python libraries
36+
- But there's no "standard" configuration/documentation for standard workflows yet; numpy/scipy/scikit-image are all feeling it out
37+
- Editable installs just arrived, but work slightly differently to what we're used to with pip install -e ..
38+
- Also starting to see more usage of dev.py as a convenient developer interface for various tasks
39+
- Still in alpha; tool is quite general so takes some figuring out what commands should be provided / which flags to support
40+
- Leah Wasser & PyOpenSci is working on community guidelines for packaging
41+
- One part of that is setting up small packages that use different tooling for comparison
42+
- This may be a good place to capture some of the Meson workflows mentioned
43+
- There is therefore technical, user interface, and documentation work to be done
44+
45+
- Stéfan van der Walt: Sparse work
46+
47+
- In the previous release of SciPy we introduced experiemental Sparse Arrays
48+
- These arrays are limited to 2D, since they are built on top of Sparse Matrices
49+
- We hope to refactor scipy.sparse:
50+
- matrices should be built on top of arrays (if not deprecated entirely)
51+
- sparse arrays should support 1D and, eventually, N-D
52+
- sparse arrays should closely follows numpy array semantics
53+
54+
- Brigitta Sipőcz: Shared infrastructure for SPECS and beyond
55+
56+
- SPECs: The current SPEC drafts are documents about policies the core libraries opt-in to follow (e.g. producing and using developer versions in testing), however, template implementation / suggested examples are needed to work out.
57+
- Testing: Libraries facing the same or very similar doctesting and docs building challenges, aggregating the needs and centralizing these efforts
58+
- Tutorial infrastructure
59+
60+
- Juanita Gomez: Community
61+
62+
- Community management
63+
- Documentation
64+
65+
4. (10 min) Discussion
66+
67+
5. (5 min) Wrap up and next steps

0 commit comments

Comments
 (0)