Announcing our public roadmap for open development

Fri, 06 Feb 2026 00:00:00 +0000

At the core of 2i2c’s service is a commitment to doing our work in a way that follows open principles and practices. We commit to doing all of our work in the open and only managing and developing open infrastructure. As part of this effort, we’re shifting our strategy to lean more heavily into co-creation with member communities and open source communities.

Today we’re excited to share a first step towards making our development process more participatory, transparent, and useful: we’re opening up our initiatives roadmap. You can find it here:

👉 2i2c.org/roadmap

You can find all of our roadmap initiatives in this GitHub repository (please comment and engage with us there!):

👉 github.com/2i2c-org/initiatives

Moving forward, the roadmap will be a key part of our service to member organizations.

Why we’re opening up our roadmap #

At 2i2c, initiatives drive most of our work. They represent major chunks of value with multiple steps needed to implement and unlock it. They range from making core infrastructure improvements to our member network, to making upstream contributions that enable new functionality on behalf of our member communities. While initiatives are generally public, they are spread across many places, and we’ve managed their prioritization, sequencing, and refinement in internal team spaces. This made it difficult for others to follow along, signal-boost, and potentially support initiatives they wanted to see done.

For this reason, we decided to build a public view of our initiatives roadmap. This reflects our current team priorities and what is coming down the pipeline.

We’ve also put our platform initiatives in a public repository. This gives us a public space for member communities (or anybody else) to discuss, collaborate, and support ideas in the open.

By opening this up, we hope to accomplish these goals:

Make it easier for everyone to see and influence our priorities.
Make it easier for member organizations to fund or collaborate on work.
Make it easier for open source communities to see what’s driving our contributions.
Make it easier to give credit to member communities that fund work.

In short, we want to model what sustainable open development can look like. Our hope is that this will both create more transparency and trust with our stakeholder communities, and invite them to tell us how we can best use our team capacity.

We hope to use a shared roadmap to funnel more resources into open source #

We also hope we can leverage this as a shared roadmap across our member communities that helps focus our attention and drive fundraising for our work. To begin, we’re inviting any member community to provide financial support for these items as a way to influence our timelines and priorities, and we’re exploring ways to facilitate fractional co-funding across our member communities to help share the cost of development across many organizations.

This is an early experiment in collaborative and radically transparent development, and we will iterate and learn as we get feedback from member communities. We’re excited to see where this goes!

Please give feedback on this idea. If you’re interested in being a member organization of 2i2c, reach out to us about membership.

2026 Strategy Update: An increased focus on co-creation

Mon, 12 Jan 2026 00:00:00 +0000

As we wrapped up 2025, we felt compelled to incorporate what we learned over the year into our strategic direction, and to update our organizational documentation accordingly. Here’s a quick rundown of what we learned and how we’re adjusting.

You can check out all of our core strategy documentation in our Team Compass.

The macro view from 2025 #

2025 was a disruptive year. The shifting political and economic climate creates a lot of uncertainty around how the research and education space will be resourced and structured moving forward. Federal funding seems less likely in general, and private philanthropy has become more competitive as many organizations turn to these funding sources to make up the gap that the government has left.

At its core, this makes us more confident in our sustainability strategy, which is rooted in a self-sustaining service that delivers value to many different member organizations in exchange for funds to support our operations. In 2024 we received funding from The Navigation Fund to build this model, and it’s the path we’ve been exploring over the last year. We like the fact that this spreads the financial risk across many different organizations, rather than depending strategically on a single donor or government agency. That said, there may still be sector-wide changes that cause the entire ecosystem of research organizations to change behavior at once.

Frankly, it is hard to predict what the future is going to look like. 2i2c is a “second order” recipient of research funding, as our member organizations provide us support to manage infrastructure and facilitate open source contributions. How these institutions respond to funding cuts will have big implications for our sustainability. For example, these two outcomes both seem reasonable:

Scenario 1: Institutions cut all of their “nice-to-have” funding choices. That means 2i2c struggles to cover its costs under its current membership model.
Scenario 2: Funding cuts create an increased need for shared infrastructure and services, and 2i2c is seen as a more cost-effective provider compared with bespoke self-managed infrastructure.

Our goal is to learn which of these two realities will come to pass as quickly as possible, so that we can make the necessary organizational changes and get ahead of the outcomes.

We’re being conservative about our hiring and team structure - we don’t plan on making new hires until there’s more financial certainty. With our current membership and contract structure, we have somewhere around 10-11 months of runway. We consider ourselves lucky in the grand scheme of things, but this is still a shorter runway than we’re comfortable with in the long-term.

How member communities see value in our service #

We had a chance to test out several organizational hypotheses about the core value of our organization and service. We originally framed “premier” membership as a means of accessing “more” community hubs for larger communities. However, we learned that for many organizations “more hubs” is not what they want, even if they have a large community. It certainly isn’t the core driver of value for their service.

Instead, our most successful member organizations seemed to view their membership as a combination of a few things:

Collaboration with our team, and the ability to work with us in shaping and delivering open source work.
Proximity to others to learn from in open science and open source, and an ability to participate in open source spaces more effectively.
Managed infrastructure that acted as a technical scaffold to make iterations of development more efficient, and made new enhancements immediately accessible.

Managed infrastructure was a necessary, but not sufficient, part of our value proposition. This makes sense - managed open source infrastructure is a commodity, and our organization is simply not competitive on price when it comes to commodity-level infrastructure (even with constraints like the Right to Replicate).

At the same time, some of the biggest successes of last year came out of deeper partnerships and development efforts that were made more likely by membership. For example, we deepened our collaboration with NASA VEDA and Development Seed and created several interesting new pieces of technology, like jupyterhub-fancy-profiles. We also felt this strongly at JupyterCon 2025 - here’s a quote by Yuvi from our team’s JupyterCon retrospective:

The unique value we add is that we help communities navigate the fairly complex and fast moving ecosystem of interactive computing, by helping them make choices that work for them. We do this by understanding their needs, understanding the ecosystem, and both making connections when they exist, and creating new ones (in ways that integrate with the existing ecosystem) when necessary.

Historically, we’ve treated these kinds of deeper partnerships as “one-off” opportunities that we take on a case-by-case basis. Given the impact that we’ve seen out of these kinds of engagements, we’ve decided to incorporate them into our service and sustainability strategy directly.

How we’re adjusting the value proposition and operations of membership #

We’re updating our strategy to center the value of human connection, collaboration, and development as part of our service, and incorporating it in our business objectives as well. This is a way to dedicate more organizational resources to this kind of impactful work, and helps us hedge our bets against a slower potential growth from standardized memberships.

Here are a few highlights from these changes (taken from our core strategy):

Our theory of impact now includes an explicit callout to the need for 2i2c to facilitate an exchange of ideas and resources between research communities and open source communities.
We’ve adjusted the language of our strategy such that managed infrastructure is a “necessary but not sufficient” aspect of member value. Members must be able to trust their infrastructure, but the real value comes from cycles of development and collaboration that is made easier by managed infrastructure.
Our key challenge is thus building a shared “development and operations” service in a way that serves multiple communities without the cost structure of a bespoke consultancy.
We have a few ideas for how to do this, and a key starting point is to define a shared roadmap and a selective group of member organizations that we can engage collectively.

Or, if you’d like to just get a quick summary, here is the strategic approach that we’ve defined for the team:

We serve independent communities with a single roadmap and service team.

Operations must use the same 80% infrastructure stack across all communities. Say no to communities that need infrastructure that deviates from this rule.

Development work must be attached to roadmap items. Roadmap items must deliver value to many communities instead of just one. Say no to project opportunities that deviate from this rule.

Our assumption is that by constraining ourselves to serve multiple member communities, we’ll force ourselves to make the technology useful for the broader open source user ecosystem as well. By choosing communities that are aligned in their workflows and values, we’ll be able to do this with a single team and roadmap in a cost-effective way.

Hypotheses we’d like to test next #

You can find more information about how we’re operationalizing this in our service model and annual plan pages - we’ll adjust these as we learn. Our next step is to test these hypotheses as quickly as we can:

By choosing the right communities for membership and building an accessible process around our team’s priorities, we can define a shared roadmapping and development system that is scalable to all of our members, and that they all view as valuable.
By engaging member communities in this way, we will have a significant new stream of revenue to sustain the organization while making open source improvements that are broadly useful.
By engaging member communities in this way, we’ll be able to advertise the value of this service as collectively improving a public good. This will increase our hit-rate for new member growth and participation.

What we’re watching for in 2026 #

2026 is going to be a pivotal year for the organization - I suspect it’ll force us to either double down on our current sustainability model, or to pivot towards something that is lighter given the new funding realities that the sector is facing. We are watching for whether research institutions begin cancelling or scaling back their contract work en-masse, and we’re also being mindful for whether our assumptions about a “shared roadmap” across our communities are actually delivering the value to them that we’d expect.

We’re excited to lean into this more active and collaborative aspect of our service. We’re confident this will be more impactful for our member organizations, and for the broader ecosystem. We’ll keep folks updated with our progress via our blog and our mailing list as always.

Strategy | 2i2c