From 44b0d519bd3bf7385adfaaff14cd3e5095bcd787 Mon Sep 17 00:00:00 2001 From: Jarrod Millman Date: Tue, 9 Sep 2025 16:07:19 -0700 Subject: [PATCH 1/2] Add develope summit description and criteria --- content/summits/developer/_index.md | 14 +++++++++++++- 1 file changed, 13 insertions(+), 1 deletion(-) diff --git a/content/summits/developer/_index.md b/content/summits/developer/_index.md index a0ed4f0..45885db 100644 --- a/content/summits/developer/_index.md +++ b/content/summits/developer/_index.md @@ -2,4 +2,16 @@ title: "Developer Summits" --- -The Developer Summits provide a venue for in-person collaboration on issues that affect the scientific Python ecosystem. +Scientific Python Developer Summits are focused, in-person, invitation-only gatherings of core developers and maintainers from across the ecosystem. +These are working meetings---not beginner-oriented events---and they typically do not include talks or tutorials. +Instead, summits provide a collaborative and self-organized space to make progress on shared technical challenges, strengthen coordination between projects, and advance the long-term sustainability of the ecosystem. + +Participants coordinate in advance to identify priorities and plan concrete work, ensuring that in-person time is spent effectively. +Work at summits often involves improving joint infrastructure (e.g., testing, packaging, documentation), aligning developer practices (e.g., governance, release management, community guides), and developing a shared strategic plan to guide the future of scientific Python. + +To qualify as a Developer Summit, the event should: + +- Convene core developers and maintainers from multiple scientific Python projects. +- Be participant-driven and self-organized, with priorities set by attendees. +- Allocate time for both concrete technical work and higher-level strategic planning. +- Focus on issues with cross-project impact rather than those of a single package. From bdef5818550892efa7e70f3693c8c66e7b3f8348 Mon Sep 17 00:00:00 2001 From: Jarrod Millman Date: Wed, 10 Sep 2025 10:37:18 -0700 Subject: [PATCH 2/2] Incorporate feedback --- content/summits/developer/_index.md | 18 ++++++++++-------- 1 file changed, 10 insertions(+), 8 deletions(-) diff --git a/content/summits/developer/_index.md b/content/summits/developer/_index.md index 45885db..fc20a67 100644 --- a/content/summits/developer/_index.md +++ b/content/summits/developer/_index.md @@ -3,15 +3,17 @@ title: "Developer Summits" --- Scientific Python Developer Summits are focused, in-person, invitation-only gatherings of core developers and maintainers from across the ecosystem. -These are working meetings---not beginner-oriented events---and they typically do not include talks or tutorials. -Instead, summits provide a collaborative and self-organized space to make progress on shared technical challenges, strengthen coordination between projects, and advance the long-term sustainability of the ecosystem. - +These are working meetings---not beginner- or newcomer-oriented events---and they typically do not include talks or tutorials. +Instead, summits provide a collaborative and self-organized space to address shared technical challenges, strengthen coordination between projects, and support the long-term sustainability of the ecosystem. Participants coordinate in advance to identify priorities and plan concrete work, ensuring that in-person time is spent effectively. -Work at summits often involves improving joint infrastructure (e.g., testing, packaging, documentation), aligning developer practices (e.g., governance, release management, community guides), and developing a shared strategic plan to guide the future of scientific Python. +Work at summits often involves improving shared infrastructure (e.g., testing, packaging, documentation), aligning developer practices (e.g., governance, release management, community guides), and developing a collective strategic vision for the future of scientific Python. -To qualify as a Developer Summit, the event should: +For an event to be considered a Developer Summit, it should: - Convene core developers and maintainers from multiple scientific Python projects. -- Be participant-driven and self-organized, with priorities set by attendees. -- Allocate time for both concrete technical work and higher-level strategic planning. -- Focus on issues with cross-project impact rather than those of a single package. +- Be participant-driven and self-organized, with priorities defined by attendees. +- Provide time for substantial collaborative technical work, while also leaving space for higher-level discussions where relevant. +- Focus on issues with cross-project impact, rather than narrowly scoped tasks that impact only a single package or work that one person could reasonably pursue independently. + +The Scientific Python project welcomes and endorses many forms of collaborative events and developer meetings. +However, to preserve a clear scope and shared understanding, only gatherings that meet the above criteria should be referred to as a **Scientific Python Developer Summit**.