|
| 1 | +--- |
| 2 | +title: 2023 Developer Summit |
| 3 | +subtitle: The First Annual Scientific Python Developer Summit |
| 4 | +summary: | |
| 5 | + The first annual Scientific Python Developer Summit (May 22-26, 2023) 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: 2023-01-11 |
| 8 | +--- |
| 9 | + |
| 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. |
| 33 | + |
| 34 | +## Logistics |
| 35 | + |
| 36 | +We have funding (i.e., for travel, food, and lodging) and space for 40 participants for five days and six nights. |
| 37 | +This will be an invite-only event that requires upfront agreement to: |
| 38 | +(a) take part in two of the three one-hour pre-summit planning meetings, |
| 39 | +(b) collaborate with fellow participants on a work plan, |
| 40 | +(c) attend the one-week summit in-person, and |
| 41 | +(d) participate, to whatever degree possible, in several months of post-summit implementation. |
| 42 | + |
| 43 | +### Participants |
| 44 | + |
| 45 | +Participants will be recruited from the community of developers of packages |
| 46 | +such as NumPy, SciPy, matplotlib, xarray, pandas, scikit-image, scikit-learn, |
| 47 | +NetworkX, and IPython, as well as domain stacks including Astropy, Pangeo, and |
| 48 | +scikit-HEP. |
| 49 | + |
| 50 | +### Dates |
| 51 | + |
| 52 | +Participants will be expected to participate in two of the three planning meetings |
| 53 | +and the weekly long summit. |
| 54 | + |
| 55 | +- February planning meeting (TBD) |
| 56 | +- March planning meeting (TBD) |
| 57 | +- April planning meeting (TBD) |
| 58 | +- May 22-26, 2023 Summit |
| 59 | + |
| 60 | +The planning meetings will have two or three "parallel tracks" so that smaller groups can focus on their subprojects. |
| 61 | +Attendees would preferably arrive the day before the summit starts, and stay for the entire duration of the summit. |
| 62 | + |
| 63 | +### Pre-Summit Planning |
| 64 | + |
| 65 | +Participants will be responsible for attending two or more one-hour video meetings (the planning meetings mentioned above) and for |
| 66 | +participating in a planning repository via PRs, issues—as both contributors and reviewers. |
| 67 | +There is no heavy top-down structure: participants themselves will organize the work that needs to be done ahead of time. |
| 68 | +They will deciding on topics, divide the work, and schedule the meeting. |
| 69 | + |
| 70 | +### Summit Execution |
| 71 | + |
| 72 | +The goal of the summit is to be a hands-on work meeting. |
| 73 | +That said, there will be some free time scheduled to brainstorm new ideas, and to discuss current community projects and activities. |
| 74 | + |
| 75 | +### Post-Summit Implementation |
| 76 | + |
| 77 | +After the meeting, attendees will collaborate on their assigned tasks until completion. |
| 78 | +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. |
0 commit comments