I've always admired Project Jupyter from afar and to join as a JupyterHub maintainer is definitely a LIFE GOALS achievement for me. The difference between then and now is that I better understand the power and impact of the open source community and *people*
it's aaron!
This is part of our open practices: doing our work in the open, inviting feedback, and making it easier for communities to see and influence priorities.
2i2c.org/open-practices
We also want to use this to experiment with fractional co-funding, so multiple member communities can share the cost of impactful work. You can learn more about how our membership model works here:
2i2c.org/membership
Our roadmap is how we deliver the most value to our member communities - roadmap initiatives focus upstream contributions in open source to enhance infrastructure for research and education.
Our roadmap is here 👉 2i2c.org/roadmap
Comment on our initiatives here 👉 github.com/2i2c-org/ini...
We’re proud to share a public roadmap for 2i2c's team - it's a step toward more participatory, transparent open development with our member and upstream communities.
👉 2i2c.org/blog/public-...
Huge congrats, Jenny. And thank you to the JupyterHub community for building an open, welcoming culture that creates real pathways for contributors to grow into leadership.
You can learn more about JupyterHub's team here: compass.hub.jupyter.org
We’ve enjoyed seeing Jenny bring care, follow-through, and a collaborative mindset to her upstream work. That’s what makes someone a great maintainer <3.
This kind of recognition comes from showing up with consistent, trusted work over time. Jenny’s contributions span nbgitpuller and grafana-dashboards, plus active participation in project meetings and community planning.
We’re incredibly proud to announce that Jenny Wong was invited to join the JupyterHub team as a contributor and maintainer!
2i2c.org/blog/jenny-j...
If you want the full context, the SciPy 2025 paper is the best deep dive:
proceedings.scipy.org/articles/hwc...
Watch the full FOSDEM talk recording:
video.fosdem.org/2026/aw1120/...
In short: Jupyter Book 2 (now built on the MyST Document Engine) gives communities a better path to publish and maintain computational narratives without locking content into one format or workflow.
Angus just gave a FOSDEM 2026 talk on Introducing Jupyter Book 2 and why this stack matters for reusable, reproducible computational publishing.
2i2c.org/blog/fosdem-...
Thanks to Eric, Sean, and Balaji at UC Berkeley for sharing the data and feedback that drove these changes, and BIDS for facilitating collaborations like these.
The pre-release (v1.3.0b1) is available now. Feedback welcome via GitHub issues.
2i2c.org/blog/nbgitpu...
Instead of showing every user the same raw git output, nbgitpuller now detects the error type and displays a targeted, human-readable message with specific steps to resolve it. The terminal log is still available - just tucked behind a toggle.
The Berkeley DataHub team shared over 2,000 error logs with us! This real-world data revealed the most common failure patterns: merge conflicts (45%), fetch errors (23%), and URL mistakes by instructors (22%). Each category needed a different solution.
UC Berkeley's DataHub team shared error log data that helped us redesign error handling in nbgitpuller - a tool used across education and research to distribute Jupyter content via a single link.
2i2c.org/blog/nbgitpu...
More details about how we put it all together in the blog post.
2i2c.org/blog/strudel...
If you're thinking about running workshops that need pre-configured environments, this setup might be useful. Tips on using STRUDEL with AI assistants here:
github.com/strudel-scie...
What we found interesting: this shows how JupyterHub can support more than just notebooks. The same patterns we use for Jupyter environments work for modern web development tools and AI assistants too.
People built prototypes for real work in astrophysics, genomics, energy, water quality, and light sources. The hub gave them space to experiment without worrying about infrastructure.
strudel.science/engage/news/...
We pre-configured Cline with OpenRouter, which let the workshop team manage AI costs centrally with a shared API key. Participants got access to premium models without needing their own accounts or API setup.
Our goal was to provide an AI-assistant environment with zero friction. We configured a JupyterHub with VS Code for the Web and Cline (an AI coding assistant) so participants could start building with AI help immediately instead of spending hours on environment setup.
We helped STRUDEL run a workshop where 30+ researchers prototyped building scientific web applications in a single day. Everyone left with a working prototype, even folks who'd never built a web app before!
2i2c.org/blog/strudel...
If you’re curious what the group does (and how it reports out), the charter is a great place to start:
jupyter.org/governance/c...
Thanks to Project Jupyter for the leadership and time that goes into community building, and for bringing more people into this work.
This kind of thing is a key part of the foundational impact 2i2c wants to have for open source communities: not just technical and infrastructure work, but also bringing expertise and support in community and governance. We're proud April was willing to step into this role!
Community work is infrastructure work. It’s how open source projects stay healthy, resilient, and welcoming over the long term. We're proud to share that our April (our People Lead) has joined the Jupyter Community Building Working Group!
2i2c.org/blog/april-j...
This is nuanced and complex, so if you'd like to learn more, see discussion about how to do this here: github.com/2i2c-org/inf...
This is part of how we think about agency vs safety on a shared open platform, give partners control in a way that's safe for other member organizations. As a result, CloudBank can run routine Terraform changes, and they validated it by deploying a hub without 2i2c in the loop.
