owned this note changed 3 years ago
Published Linked with GitHub

Annual Developer Sprint Week


Hi Andy,

Thanks for considering our request. I've responded to your questions (inline) below. We are fairly flexible, so we are happy to work within your constraints.

Since we are planning to ask a lot from attendees leading up to, during, and after the meeting, we won't know who can attend until we finalize the dates. And we won't know what we can work on until we know who is attending. I understand this makes planning difficult and we will need to be flexible.

On Thu, Oct 20, 2022 at 10:46 AM Andrew J Connolly ajc@astro.washington.edu wrote:

​​​​1. Will you have parts of the meeting when everyone will be in the same room (e.g. opening discussions)

We could, but hadn't planned on it. We will do a lot of pre-meeting work organization and planning, so folks will have a clear idea of what they will be working on and with who. If there is a space we can all be in, it could be useful. But it is not a requirement by any means.

​​​​2. When people are working together what is the maximum size of room/space you will need (e.g. is it lots of 1:1 or will there be groups of people who will need a separate space)

We expect the work group sizes to be between 2 and 10 people. The workgroups will likely not stay the same for the entire week. Ideally, we would have access to:

  • one to two rooms that fit up to 10 people
  • two to three rooms that fit up to 6 people
  • four to five rooms that fit up to 4 people

We can also use a bigger room and just separate ourselves into smaller groups.

​​​​3. Would some of the participants be open to giving a talk about Scientific Python or some aspect of it as I think there would be a fair amount of interest in folks at UW who work in the open source space.

We'd be happy to give one or two talks on Scientific Python, NetworkX, scikit-image, etc., as long as the other summit participants can keep working during that time.

Best regards,
Jarrod

Moved to the SP archive

brigitta
Two main things we need to cover here:

  • scope
  • size

Goals of the meeting

The developer sprint week (i.e., 5 days and 6 nights) aims to provide an opportunity for ~30-50 developers from across the core scientific python libraries to produce significant progress in the following 3 areas:

Joint infrastructure sprint

  • Join efforts and resources to adopt and improve infrastructre and processes that are used by projects across the board. These include infrastructure covered by SPECS protocols already, including but not limited to documentation, testing, packaging, and CI infrastructure.
Re-usable libraries with commonly used functionality
Shared build system for binary packaging
Integrated websites and expanded documentation
Shared benchmarking
Developer Operations (DevOps)

Better coordination of core projects

​​​​Community best operating and development practices manual
​​​​Coordinated release schedule
​​​​Regular cross-project communication
​​​​Joint governance structures

Shared development vision

Strategic plan for the next decade

Brigitta Sipőcz text pulled and edited from the grant

Our community has never before engaged in a deliberative pro-
cess to try and anticipate future challenges.
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 core project, the strategic plan would discuss the challenges shared by more projects. The plan will also be used by the community
for support when applying for federal grants.

Participants

Q: ~30-40 seems to trivially fit into eScience space. What is the real maximum number, if we don't need to fit everyone in the same room at once? (if no talks are planned?)

scienfic python ecosystem steering committee

Brigitta Sipőcz
do we want only the developers there, or this would be a blanket inclusion of all named people incl community people and editors, etc?

Current list below is from SPECS repo, steering committee dir:
cat *md | grep title | grep -v SPEC| gawk -F : '{print NR,$2}'

1 Anderson Banihirwe (core: xarray)
2 Brigitta Sipőcz (ecosystem, domain: astropy)
3 Elliott Sales de Andrade (core: mpl)
4 Georgiana Dolocan (core: jupyter)
5 Jarrod Millman (core: networkx)
6 Joris Van den Bossche (core: pandas/scikit-learn)
7 Juan Nunez-Iglesias (core: scikit-image)
8 Juanita Gomez (ecosystem community)
9 Kira Evans (domain: napari)
10 Kristen Thyng (?? JOSS)
11 Lucy Liu (?? scikit-learn contributor experience)
12 Madicken Munk (domain: yt)
13 Matthias Bussonnier (core: ipython)
14 Melissa Weber Mendonça (core: numpy/scipy)
15 Paul Ivanov (core: jupyter)
16 Ralf Gommers (core: numpy/scipy)
17 Ross Barnowski (core: numpy/networkx)
18 Stéfan van der Walt (core: scikit-image/numpy)

community managers

https://scientific-python.org/about/#community-managers

  1. Davina Zaman
  2. Marianne Corvellec
  3. Mridul Seth
  4. Pamphile Roy

TBD core scientific python projects, people not already in the list above

  • numpy
    • Matti Picus
    • Sebastian Berg
  • scipy
    • Pamphile Roy
  • matplotlib
    • Tom Caswell
  • networkx
    • Dan Schult
    • Mridul Seth
  • scikit-image
  • scikit-learn
    • Olivier Grisel
  • ipython
    • Fendando Perez
  • xarray
    • Stephan Hoyer

TBD domain projects (still, we need developers from those projects and not the PIs/scientists/etc)

  • Jim Pivarski (pyHEP awkward array)
  • Pey Lian Lim (astropy)
  • Ryan May (metpy + (matplotlib?))
Select a repo