Skip to content

Commit e6bb92e

Browse files
committed
enh(blog): more updates
1 parent c09aef0 commit e6bb92e

1 file changed

Lines changed: 34 additions & 34 deletions

File tree

_posts/2026-01-22-building-resilience-2026.md

Lines changed: 34 additions & 34 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
layout: single
33
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."
55
author: "pyopensci"
66
permalink: /blog/2026-building-resilience-together.html
77
header:
@@ -20,11 +20,11 @@ last_modified: 2026-01-22
2020
I'm not going to sugarcoat it—2025 was hard.
2121

2222
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.
2424

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 didnt 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.
2626

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.
2828

2929
And yet, something important happened.
3030

@@ -84,9 +84,9 @@ They just dove in and began to help each other. It was magic.
8484
That day felt like a blueprint. It showed what happens when you create the
8585
right environment and empower a community to help each other. That model—
8686
shared ownership, peer learning, mutual support—changed how I think about
87-
building sustainable infrastructure.
87+
building sustainable infrastructure and community.
8888

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.
9090

9191
## What we're building in 2026
9292

@@ -115,23 +115,25 @@ best practices *and* the responsible use of generative AI in scientific and
115115
open source workflows. The training will be held asynchronously to reduce barriers
116116
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.
117117

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
125127
open source ecosystem and are also straining the fragile social web that supports it.
126128

127129
We're piloting this new training format through our [partnership with
128130
Stanford's Open Source Program Office](https://www.pyopensci.org/events/pyopensci-stanford-create-python-package-workshop.html),
129131
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
131133
organizational membership program that supports researchers at scale.
132134

133135
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
135137
communities behind scientific software.
136138

137139
<figure>
@@ -147,17 +149,15 @@ communities behind scientific software.
147149

148150
### Mission-aligned corporate sponsorship
149151

150-
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
152154
tools and values align with our community.
153155

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.
161161

162162
### Rethinking how we communicate and stay connected
163163

@@ -176,16 +176,16 @@ None of what we learned in 2025—or what we're building toward in 2026—
176176
happened in isolation.
177177

178178
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
180180
and support as we navigated a challenging year. They encouraged me to embrace
181181
sustainable leadership and supported me as I developed new programs to ensure
182182
our long-term sustainability.
183183

184184
Our Editors-in-Chief—**[James Balamuta](https://github.com/coatless),
185-
[Eliot Robson](https://github.com/erobson), and [Lauren Yee](https://github.com/laurenyee)**
185+
[Eliot Robson](https://github.com/eliotwrobson), and [Lauren Yee](https://github.com/yeelauren)**
186186
led the peer review process through a period of rapid change, navigating
187187
AI-fueled submissions while keeping quality and care at the center.
188-
**[Carter Rhea](https://github.com/CartWheel65)** stepped up as an editor
188+
**[Carter Rhea](https://github.com/crhea93)** stepped up as an editor
189189
numerous times, supporting volunteers who were overburdened and leading one
190190
of our largest reviews—Astropy—which was just accepted in early 2026.
191191

@@ -213,19 +213,19 @@ with wisdom and generosity.
213213
alt="Carol Willing presenting on micromentoring">
214214
</picture>
215215
<figcaption>Carol Willing from our Advisory Council presenting on
216-
micromentoring at SciPy 2025.</figcaption>
216+
micromentoring at PYCON US 2025.</figcaption>
217217
</figure>
218218

219219
And to the many community members who contributed through reviews, workshops,
220220
sprints, writing, mentoring, and quiet acts of support—thank you. This
221221
organization exists because you choose to show up.
222222

223-
## This is how we help
223+
## Navigating uncertainty in 2026
224224

225-
When things are uncertain, community infrastructure matters more, not less.
226-
It's how people find support when institutions can't provide it. It's how
227-
knowledge gets shared when traditional pathways break down. It's how we take
228-
care of each other.
225+
When things are uncertain, community infrastructure matters most.
226+
It's how people find support that institutions can't currentlyprovide. It's how
227+
knowledge gets shared when traditional collaboration pathways break down.
228+
It's how we take care of each other.
229229

230230
That SciPy sprint showed me what's possible. When you create spaces where
231231
people can show up, learn together, and support each other—when you do that
@@ -236,4 +236,4 @@ researchers across the world. Sponsorship models that align values with
236236
action. Spaces—both online and in-person—where beginners and experts learn
237237
side by side.
238238

239-
This is how we build resilience. This is how we help. Together.
239+
This is how we build resilience. This is how we help make the world better. Together.

0 commit comments

Comments
 (0)