You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: _posts/2026-01-22-building-resilience-2026.md
+34-34Lines changed: 34 additions & 34 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
---
2
2
layout: single
3
3
title: "Building Resilience: pyOpenSci in 2026"
4
-
excerpt: "2025 taught us that sustainable infrastructure requires more than grants. As we navigate generative AIs impact on scientific open source and shifting funding landscapes, pyOpenSci is building resilience through training, sponsorship, and community-centered leadership."
4
+
excerpt: "pyOpenSci learned a lot about resilience in 2025. As we navigate generative AIs impact on scientific open source and shifting funding landscapes, pyOpenSci is building resilience through training, sponsorship, and community-centered leadership. Learn more about our plan."
Watching organizations like the [Python Software Foundation turn down million-dollar NSF grants](https://pyfound.blogspot.com/2025/10/NSF-funding-statement.html)
23
-
because DEIA work was no longer supported made something painfully clear: the funding landscape that many of us built on is no longer stable.
23
+
because DEIA work was no longer supported made something painfully clear: the funding landscape that has grounded so many of us is no longer reliable.
24
24
25
-
At the same time, the rapid spread of generative AI use fundamentally changed how open source work happens. GenAI didn’t just change how we code--seemingly overnight, it taxed the human systems that sustain open source. Volunteer reviewers and maintainers were asked to evaluate more code than ever--often machine-generated code generated. Maintainers faced ethical and licensing questions they didn’t sign up to solve alone. Long-standing norms around learning, critical thinking, authorship, and responsibility began to blur.
25
+
At the same time, generative AI fundamentally changed how open source work happens. Maintainers found themselves reviewing more code than ever—much of it machine-generated—while navigating ethical questions about authorship and responsibility they didn't sign up to solve on their own.
26
26
27
-
These pressures revealed a fundamental shift in the scientific open source ecosystem—one that challenges how we fund, support, and sustain our communities. For many if not most of us, this changed how we worked. The ground often felt unstable—not just months out, but sometimes day to day.
27
+
For many of us, the ground felt unstable—not just months out, but sometimes day to day.
28
28
29
29
And yet, something important happened.
30
30
@@ -84,9 +84,9 @@ They just dove in and began to help each other. It was magic.
84
84
That day felt like a blueprint. It showed what happens when you create the
85
85
right environment and empower a community to help each other. That model—
86
86
shared ownership, peer learning, mutual support—changed how I think about
87
-
building sustainable infrastructure.
87
+
building sustainable infrastructure and community.
88
88
89
-
Resilience is about building spaces for people to engage and support each other.
89
+
Resilience is about building spaces for people to both engage, learn, and support each other.
90
90
91
91
## What we're building in 2026
92
92
@@ -115,23 +115,25 @@ best practices *and* the responsible use of generative AI in scientific and
115
115
open source workflows. The training will be held asynchronously to reduce barriers
116
116
to participation and increase accessibility. And it will feature leaders in the open source community in an effort to connect learners to the real heart of Open Source--people.
117
117
118
-
While our courses will initially be designed for researchers, university Open Source Program Offices
119
-
(OSPOs), and anyone looking to develop open source skills that are in high
120
-
demand in today's tech-driven job market. Based on what we learned in 2025, these
121
-
trainings will emphasize foundational skills, critical thinking and judgment, and shared
122
-
norms. Generative AI can support open source workflows, but it can't replace
123
-
the critical thinking that only a human can do. It also can't replace
124
-
mentorship, care and compassion—human parts of the tech world that both fuel the
118
+
While our courses will initially be designed for researchers at university Open Source Program Offices
119
+
(OSPOs) we see them as becoming valuable to anyone looking to develop the open source and generative
120
+
AI skills that are in high demand in today's tech-driven job market.
121
+
122
+
Based on what we learned in 2025, these
123
+
trainings will emphasize foundational skills, critical thinking (particularly as it relates to using generative AI tools), and shared
124
+
norms. Generative AI can support open source workflows, but it can't fully replace
125
+
the thought, design, and vision that only a human can implement. It also can't replace
126
+
mentorship, care, and compassion—human parts of the tech world that both fuel the
125
127
open source ecosystem and are also straining the fragile social web that supports it.
126
128
127
129
We're piloting this new training format through our [partnership with
128
130
Stanford's Open Source Program Office](https://www.pyopensci.org/events/pyopensci-stanford-create-python-package-workshop.html),
129
131
where we ran successful workshops in 2025. In 2026, we're expanding this
130
-
model to other OSPOs through the CURIOSS network and building an
132
+
model to other OSPOs, hopefully leveraging the strong connections within the [CURIOSS network](https://curioss.org/) and building an
131
133
organizational membership program that supports researchers at scale.
132
134
133
135
Our goal is to create learning spaces that reduce isolation, build
134
-
confidence, connect learners to the open source community, and strengthen the
136
+
confidence, connect learners to the humans that drive open source, and strengthen the
We're leaning into corporate sponsorship to support scientific software
151
-
infrastructure while building deeper relationships with organizations whose
152
+
We're also leaning into corporate sponsorship to support scientific software
153
+
infrastructure. We will build deeper relationships with organizations whose
152
154
tools and values align with our community.
153
155
154
-
Value alignment matters—from [how we choose the tools we teach]({{ site.url }}/blog/how-we-choose-python-tools.html)
155
-
to the partners we work with. We prioritize organizations that support open
156
-
source, open science, and inclusive practices. Sponsorship allows companies to
157
-
invest meaningfully in the ecosystems they rely on while helping sustain
158
-
pyOpenSci's work. We're especially excited about partnerships that feel
159
-
reciprocal—supporting our mission while strengthening the tools and practices
160
-
we teach and use together.
156
+
Value alignment matters—from [how we choose the tools we teach]({{ site.url }}/blog/how-we-choose-python-tools.html) to the partners we work with. We prioritize organizations that support open source, open science, and inclusive practices.
157
+
158
+
Corporate sponsorship allows companies to invest meaningfully in the ecosystems they rely on. It helps sustain pyOpenSci's work in [software peer review](https://www.pyopensci.org/about-peer-review/index.html) and development of [open education resources](https://www.pyopensci.org/python-packaging-science.html) that support researchers in making their scientific workflows more open and accessible.
159
+
160
+
We're especially excited about partnerships that feel reciprocal—supporting our mission while strengthening the tools and practices we teach and use together.
161
161
162
162
### Rethinking how we communicate and stay connected
163
163
@@ -176,16 +176,16 @@ None of what we learned in 2025—or what we're building toward in 2026—
176
176
happened in isolation.
177
177
178
178
I'm deeply grateful to our 2025 Executive Council, **[Karen Cranston](https://github.com/kcranston)
179
-
and [April Johnson](https://github.com/aprilcs)**, for their steady guidance
179
+
and [April Johnson](https://github.com/aprilmj)**, for their steady guidance
180
180
and support as we navigated a challenging year. They encouraged me to embrace
181
181
sustainable leadership and supported me as I developed new programs to ensure
0 commit comments