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.
We have funding (i.e., for travel, food, and lodging) and space for 40 participants for three days and four nights.
This will be an invite-only event that requires upfront agreement to:
(a) take part in one or more pre-summit planning meetings,
(b) collaborate with fellow participants on a work plan,
(c) attend the summit in-person, and
(d) participate, to whatever degree possible, in several months of post-summit implementation.
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.
We recommend using Link Light Rail to get from the airport to the hotel. It takes approximately an hour and costs $3.25.
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”.
We provide most meals, but if you incur extra travel costs that you need covered, we are able to reimburse you.
Please keep all slips, no alcoholic beverages covered, max 25 USD per dinner and 20 USD per breakfast.
Participants are recruited from the community of developers of packages
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.
List of participants (we add names to the list as they confirm attendance)
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).
A strategic plan would 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 can be used by the community as supporting evidence when applying for grants.
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 decide on topics, divide the work, and schedule the meeting.
The goal of the summit is to be a hands-on work meeting.
That said, there will be some free time scheduled to brainstorm new ideas, and to discuss current community projects and activities.
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.