
Executive Director @2i2c_org Executive Council @ProjectJupyter co-lead JupyterHub and JupyterBook open communities 🙌 open infrastructure 💻 open science 🧪
Berkeley, California
Joined November 2009
- Tweets21.8K
- Following1.4K
- Followers8K
- Likes9.5K
Pinned Tweet
After many months of work we are excited to announce the new Jupyter Book!
blog.jupyter.org/announcing-…
This is a complete re-write of Jupyter Book to make it more modular, powerful, customizable, and easy to use. See this 🧵 for some highlights!
We spent a bit of time updating Jupyter Book's landing page documentation, and making it more useful for communities with multiple content repositories under one domain. Here's a little post about it:
2i2c.org/blog/jupyterbook-mu…
Love this vision of "Backseat software". We need more software that's useful on its own right, and doesn't constantly try to inject itself into your life.
blog.mikeswanson.com/backsea…
I'm really excited to see 2i2c leaning more into open product development practices by building a public roadmap. This is a way for us to find more common ground between the needs of our member communities, and opportunities to support open source.
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-roadmap…
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-roadmap…
It's been so cool seeing new contributions in jupyterhub from Jenny. She's brought a creative and collaborative spirit that I really appreciate! Congrats on joining the team!
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-jupyterh…
Check out Angus' talk about the Jupyter Book re-write, and the new MyST Document Engine! Thanks for repping the jupyter book project at FOSDEM, Angus!
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-jupyter…
This was an exciting round of UX improvements to nbgitpuller thanks to feedback from the team at UC Berkeley. Thanks to the CloudBank team and to @UCBIDS for facilitating collaborations like this!
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/nbgitpuller-be…
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-gui-pr…
This was an interesting experiment in using JupyterHub to deploy a *data science design* environment, for a user workshop, rather than a typical "notebook analytics" environment. You can serve all kinds of interfaces and side-applications with JupyterHub!
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-gui-pr…
I'm proud that 2i2c is able to make space for more people to participate in open source leadership and community building in this way! Jupyter is lucky to have April helping out :-)
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-jupyter-…
We helped empower CloudBank to provision and manage their own infrastructure on our shared platform. Instead of waiting on 2i2c engineers, they can now handle these changes themselves.
2i2c.org/blog/cloudbank-self…
I find this kind of thing really exciting - 2i2c is basically a centralized shared infrastructure team, running independent community hubs, in a way where we can directly give others control over their own infrastructure in a safe way.
We helped empower CloudBank to provision and manage their own infrastructure on our shared platform. Instead of waiting on 2i2c engineers, they can now handle these changes themselves.
2i2c.org/blog/cloudbank-self…
You would be surprised how quickly people run into disk usage issues in data science environments in the cloud! We have been trying to make the cloud safer for research and education by giving jupyterhub admins more rapid visibility into the usage of all of their users.
We improved jupyterhub-home-nfs so that admins can now see per-user home directory usage within minutes (not hours) and get quota limits as metrics, so it’s easier to spot disk usage problems early and create alerts.
2i2c.org/blog/faster-home-di…
You would be surprised how quickly people run into disk usage issues in data science environments in the cloud! We have been trying to make the cloud safer for research and education by giving jupyterhub admins more rapid visibility into the usage of all of their users.
We improved jupyterhub-home-nfs so that admins can now see per-user home directory usage within minutes (not hours) and get quota limits as metrics, so it’s easier to spot disk usage problems early and create alerts.
2i2c.org/blog/faster-home-di…
We improved jupyterhub-home-nfs so that admins can now see per-user home directory usage within minutes (not hours) and get quota limits as metrics, so it’s easier to spot disk usage problems early and create alerts.
2i2c.org/blog/faster-home-di…
2025 had a lot of learning for us - in part, we learned that it is really hard to balance both a shared infrastructure platform *and* a collaborative development service! Here are a few thoughts about the tension between these, and our plan to leaning into that tension in 2026.
We just shared our 2026 strategy update: what we learned in 2025, and how that’s shifting 2i2c toward co-creation (human connection, collaboration, and development) alongside managed infrastructure.
2i2c.org/blog/strategy-updat…
Chris Holdgraf retweeted
"Who is using the most resources?" is a common question for cloud admins. With our new user group cost dashboards, you can answer that question with more granularity!
2i2c.org/blog/2025/cloud-cos…
This is a pattern I'm excited to lean into - many communities get opportunities to use cloud resources ad-hoc. We'd like our membership to be an easy way to quickly get resources when you need them, when credits / access / etc is available by government/state resources.
2i2c recently helped the IHDEA working group to showcase their Heliophysics computing environments at two major conferences in Madrid and San Antonio.
2i2c.org/blog/2025/ihdea-wor…
I'm really excited to welcome @UCBIDS as our founding premier member organization for 2i2c. It has been one a key strategic partner ever since our creation and I look forward to many more years of impact!
We're thrilled to announce that the Berkeley Institute for Data Science has joined as 2i2c's first premier member organization!
👉 2i2c.org/blog/2025/bids-prem…
Me every time I interact with an LLM
youtube.com/watch?v=jcreMkMF…

