2i2c

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-ro…

The Jupyter Book and Jupyter Hub teams are hiring a community manager! This is a one-year contract to help us pioneer this critical role by improving and growing our community. Read more here, and please share and apply! blog.jupyter.org/call-for-appli…

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

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-ro…

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.

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-jup…

If you want the full context, the SciPy 2025 paper is the best deep dive: proceedings.scipy.org/articles/hwcj9… Watch the full FOSDEM talk recording: video.fosdem.org/2026/aw1120/ZY…

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-ju…

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/nbgitpull…

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.

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/nbgitpull…

More details about how we put it all together in the blog post. 2i2c.org/blog/strudel-g…

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-scienc…

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-g…