If you’ve worked with GitHub Actions in open source projects, you might encounter a hard-to-debug error where repository secrets are simply empty. That’s probably because the PR is from a forked repository! Here’s a little learning we had after losing a bunch of time figuring this out: Our PR from a fork was using empty strings for repository secrets # github-activity is a tool we help maintain for generating changelogs from a wider variety of contributions than GitHub’s defaults. We ...| 2i2c
Openscapes is hiring a NASA Openscapes Suborbital Team Member to engage with NASA suborbital science teams and support open science practices. This is a part-time contract position (20 hrs/week) starting as early as December 1, 2025, with a 6-month initial term and potential for extension. The position is fully remote ($100/hr) with applications due by October 26, 2025. Learn more # Openscapes job posting Acknowledgements # Openscapes for their continued work in empowering the research community| 2i2c
We are excited to announce that dashboards to monitor cloud usage and costs at a per-user level are now available! See the cost monitoring documentation for more information. A key goal of 2i2c is to make the cloud safe for science. By providing transparent cost monitoring, we give communities the confidence that they won’t face unexpected bills and can better understand how their usage patterns translate to cloud costs. This visibility is especially valuable in our shared platform model, w...| 2i2c
Over the past year we’ve experimented with being more strategic about supporting upstream communities as a team. This post summarizes our current plan, including team targets and practices we’ll continue to pilot. We’ll revisit this as we learn more. Note: This document is about the Foundational contributions we make so that open source communities are healthier and more impactful. It is not about Directed upstream contributions we make as part of our own product work. See On being a go...| 2i2c
One of 2i2c’s goals is to make the cloud safe for science. A big part of this is making the black box of commercial cloud infrastructure more predictable and reliable for our member communities, across our network of community hubs that all operate autonomously. Give us feedback! Click here to provide feedback that will help us make this more impactful. To that end, we’ve created a status page for 2i2c’s network of community hubs. This is a source of truth to provide a high-level pictur...| 2i2c
This is a running blog post for Chris to share out community updates from his time on the Jupyter Executive Council. See context for this page. Updates for the Jupyter community from Chris # Chris aims to write monthly updates for Jupyter’s community in the Jupyter Community Forum to share his perspective on what the council is up to.| 2i2c
We’ve been working to reduce the base costs of running our cloud infrastructure on AWS by switching to more efficient instance types for our core nodes. This is the core infrastructure we use to ensure hubs are “always available” for users, even when no one is actively using a hub. By moving from older r5.xlarge instances to newer, more efficient r8i-flex.large instances, we’ve significantly reduced these baseline costs while maintaining the same level of service. Here’s a plot of d...| 2i2c
On August 29, 2025 our cloud infrastructure team experienced an incident with the UC Merced community hub when students tried to login simultaneously at the start of class. For more detailed technical information about this incident, see our full incident report. What happened # Students experienced issues when trying to login to the hub at the same time during the start of class. The concurrent spawn limit was reached quickly due to the large number of users starting up simultaneously. New n...| 2i2c
At 2i2c, we aim to be an exemplar organization in working openly, supporting open science, and supporting open source communities in everything that we do. We believe that open science is a process, not a product, and commit to following practices that align with open principles throughout our work. A key principle for our team has always been working in the open. We do almost all of our work in our own public repositories or in upstream community spaces. However, still struggle to communicat...| 2i2c
Any organization building on open source faces a fundamental tension: how do you serve the needs of your organizational stakeholders while also acting as a responsible steward of the upstream projects you depend on? This is harder than it looks - simply “making PRs” leaves a number of open source needs unaddressed, and can burn out both your team members and the open source maintainers. We think about this a lot at 2i2c, and want to share our framework to navigate this challenge intention...| 2i2c
Our Technical Lead Yuvi Panda recently gave a talk at the doepy meetup about JupyterHub’s interest in moving beyond the “single-user notebook application” and towards a more flexible approach to enabling administrators to deploy many different types of applications and environments. Check out a video of the talk here: This is an important step for the JupyterHub project in order to support the many different kinds of workflows that data scientists need to use in their work. We hope that...| 2i2c
2i2c has successfully completed a hardware exchange with Universidad Nacional de Córdoba’s Centro de Computación de Alto Desempeño (CCAD) through funding from the Catalyst Project. CCAD used funding to purchase new on-prem computing infrastructure, significantly expanding their computing capabilities.| 2i2c
Documentation is incredibly important for open source projects to communicate their value and show users how to make the most of their tools. However, it’s one of those things that often gets de-prioritized with all of the other work that needs to happen in a project.| 2i2c
As we enter Q3 2025, our focus remains on enabling better cost controls for our communities and increasing flexibility for end-users. In line with our commitment to transparency, we’re sharing our platform and service objectives for the quarter and inviting feedback to ensure our direction reflects what matters most to the communities we serve. See our product goals from the previous quarter here. The themes below offer a high-level snapshot of where we aim to evolve our offerings in the co...| 2i2c
This post highlights what stood out to us from last quarter and reflects on the targets we set at the start of the quarter. This quarter, our team learned the importance of shipping iteratively and inviting feedback frequently. In some cases, we learned this the hard way - having spent multiple cycles developing without feedback from community representatives. In other cases, we made rapid progress by working in collaboration with community members in our network. next quarter, we are leaning...| 2i2c
We were excited to hear that JupyterCon is happening again in 2025. The Call for Proposals just wrapped up, and our team was involved in preparing and submitting several directly from 2i2c as well as from the ecosystem in general.| 2i2c
Managing user groups in JupyterHub can be a challenging task, especially in environments with dynamic user bases and complex group structures. This post describes how we can leverage the latest group management features in JupyterHub, along with Prometheus and Grafana, to monitor group-level resource usage effectively. Motivation # Hub admins have a strong impetus to monitor usage and costs by user groups because it allows them to advocate for better funding and cost recovery models based on ...| 2i2c
The Problem # Two of our the communities we serve ( NMFS Openscapes and CryoCloud) reported issues with starting GPU nodes on their hubs. Upon investigation, I discovered that the cluster autoscaler seems to not recognize that GPUs were available in the cluster at all suddenly, and hence wasn’t provisioning the nodes.| 2i2c
A post on the Jupyter Book blog about the recent Scientific Python 2025 Developer Summit.| 2i2c
A core component of our mission to make research and education more impactful, accessible, and delightful is leveraging our unique global network of communities to make meaningful improvements to the open-source tools that power their work.| 2i2c
When we first committed to offer Jetstream2 support at 2i2c, Jetstream2, Magnum, OpenStack, ClusterAPI were all new concepts that we hadn’t used at 2i2c before. And although the initial exercise of reading about each of them independently was confusing, learning how they actually glued together was the key.| 2i2c
This is a summary of major progress we made in Q1 of 2025. Its goal is to summarize our major accomplishments and important context before we prioritize for Q2. We hope this gives our community stakeholders a more strategic-level insight into our progress and organizational plans. See our Product Highlights for 2025Q1 for a product-focused review. Please give us feedback for how we can provide more useful information. Heading into Q1 2025, we had just completed an organizational re-structurin...| 2i2c
As we head into Q2 of 2025, we continue to focus our work delivering on a small set of core themes that reflect our communities’ most pressing needs. As a part of this process, we want to continue sharing our platform and service goals in an effort to remain transparent, as well as to provide our communities with an opportunity to give us feedback on our direction, and on what’s important for them. See last quarter’s product goals here. The following themes are not guarantees, but shoul...| 2i2c
These describe the major service improvements that we rolled out in Q1 2025. See this blog post describing our product enhancement goals in Q1 2025 for the targets we intended to hit this quarter.| 2i2c
A blog post on the Jupyter blog about a recent experiment to significantly reduce the cost of runnign a node on the mybinder.org federation.| 2i2c
Thank you to Emilio Mayorga for sharing this publication. Several community members, including Paige Martin (Australian Climate Simulator), Eli Holmes (NOAA Fisheries), and Emilio Mayorga (University of Washington) published case studies in Oceanography magazine’s “Vision for Capacity Sharing” issue. Their article Harnessing Marine Open Data Science for Ocean Sustainability in Africa, South Asia, and Latin America highlights the benefits of hackweek-style collaboration and learning even...| 2i2c
We are proud to announce that 2i2c’s Executive Director, Chris Holdgraf, was recently elected to Jupyter’s Executive Council. The 2i2c team discussed whether Chris should run for this position last year, and concluded that it was a way for our non-profit to both support Jupyter’s mission at a strategic level, and represent the interests of research and education communities in Jupyter’s direction.| 2i2c
This quarterly post is coming out a little bit late - our goal was to post this in early January, but the year has been more complicated than we bargained for :-)| 2i2c
Building upon our previous work developing per-user storage quotas for our AWS infrastructure, we are pleased to announce that this feature is now available for GCP-hosted hubs! To provide this feature on this vendor, we have updated our infrastructure provisioning system to create persistent disks, and enable automatic backups of the disk for disaster recovery purposes.| 2i2c
Project Pythia and the “Jupyter notebook obsolescence” problem # Project Pythia provides educational resources for essential software tools that enable open, reproducible and scalable geoscience, such as the Pangeo stack of packages (Xarray, Dask, Jupyter).| 2i2c
Last December I had an opportunity to discuss the current and future state of the open publishing ecosystem at a workshop hosted by HHMI1. While 2i2c doesn’t primarily focus on “publishing” workflows, we do support communities on a journey that often leads to publishing, and we make choices about technology in our community hub platform that can support different kinds of publishing outcomes.| 2i2c
2i2c are pleased to announce the development and deployment of automated backups of home directories on GCP-hosted hubs! We have developed the gcp-filestore-backups project that regularly creates backups of JupyterHub home directories for disaster recovery purposes.| 2i2c
