Giuliano Maciocci | 2i2c

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.

Our Product and Service goals for Q3 2025

Tue, 22 Jul 2025 00:00:00 +0000

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 coming months.

⭐ Connect with us

Give us feedback about our direction and how it can improve.

Fund parts of this work if you’re interested in making something happen.

Demonstrable reliability of our infrastructure #

Hub management has many moving parts, and things can go wrong. We want tighter control over the reliability of our infrastructure and better visibility into the status of our community hubs for administrators and members. We will take steps to improve alerting, uptime, and overall platform reliability, as well as review our internal incident response practices. Our goal is to improve the reliability and responsivity of our interactive computing hubs for both administrators and users throughout their community hub lifecycle.

User-level costs monitoring and group-level usage monitoring #

We’ll build on our recent Grafana dashboard usage monitoring to add usage monitoring for user groups and begin work on user-level costs monitoring. These are steps toward group-level cost tracking, which will enable better management of team and departmental expenses, especially in large institutions.

Improving our Incident Response capability #

As a special-case of doubling down on infrastructure reliability, we’re making a concerted effort to improve our incident response processes. This will allow us to respond more reliably and transparently to issues as they arise, and to give our communities confidence about the steps we’re taking to resolve them. Our goal is to improve response time and quality, and connect this with infrastructure reliability improvements.

Piloting a feature co-funding model #

This year, 2i2c has experimented with a collaborative community funding model for platform development. This is a way to share funding across communities, and to invite community champions to co-fund projects on the 2i2c roadmap. Our goal is to accelerate upstream development with funded time while minimizing costs for each community. Over the next quarter, we’ll share more details on how the program works, how communities can participate, and what we’re learning along the way.

Early candidates for community funding:

Compute quotas: Building on our user and group management foundation, we aim to let admins assign compute quotas to users or groups, increasing cost control and easing departmental budgeting.
Canvas authentication: Integrating with Canvas will enable management of users and groups within Canvas, while using the same data for usage and cost tracking.
nbgitpuller UX improvements: Enhance nbgitpuller for sharing interactive projects via a simple link, focusing on error handling, conflict resolution, and per-user authentication for content retrieval.

As we develop this initiative, we’ll need to learn how to credit community partners who co-sponsor work and align our roadmap with the interests of the upstream communities we support.

If you have suggestions for improving this process, or if any features interest your community, reach out to us to discuss joining other 2i2c communities in funding and accelerating their development.

Another update coming in Q4 #

Each quarter, we’ll share an update like this to outline our product priorities and track progress. When planning for Q4, we’ll review what we’ve accomplished and provide a community update. Stay tuned!

Meanwhile, let us know what you think about our direction. Your feedback helps us provide the best value to our communities. Thank you!

Acknowledgements #

Our strategic and organization-level work is supported by a grant from The Navigation Fund and fees from our member organizations.

Product and team highlights from Q2 2025

Mon, 21 Jul 2025 00:00:00 +0000

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 into this approach as we work towards building a more standardized and sustainable service for our community network.

We’ve experienced some disruption and more uncertainty due to the current scientific funding climate, and we’re working hard to iterate on this model with feedback from our communities to find a path towards sustainability. We’re confident that we’ll get there, and improving the value our network of community hubs is a key way to do so.

With that in mind, here’s what stood out from the quarter:

⭐ Find our JupyterCon 2025 submissions here to see some other things we’re excited about sharing.

Group-level resource monitoring #

Building on our previous work delivering usage monitoring using Prometheus and Grafana, we’ve released jupyterhub-groups-exporter, allowing hub administrators to leverage the latest group management features in JupyterHub to monitor group-level resource usage effectively, making it easier to identify usage patterns across teams and departments.

⭐ Members of 2i2c’s community network can learn how to use this in our user guide to usage monitoring. See this blog post announcing jupyterhub-groups-exporter.

Last year we introduced customizable servers via profile lists. We’re building on that - servers can now be configured to allow users to dynamically specify, build, and share their own custom environment images without the need for a hub administrator. This will allow community champions with diverse user bases to give their users greater flexibility to support a wide variety of custom computational workflows, accelerating knowledge discovery and sharing. Look out for a blog post on this development in the coming weeks and months.

⭐ Members of 2i2c’s community network can learn how to use this in our dynamic image building quick start guide.

Co-located narrative content with out-of-the-box Jupyter Book support #

Central to our communities’ work is sharing new findings, best practices, and community resources. To facilitate that, we’ve added support for Jupyter Book 2 for all of our member communities. Our communities can rapidly build interactive starter documentation and provide users with a rich, interactive, and informative onboarding experience. With a suite of customizable landing-page layouts, colour themes, and component galleries ready to match a community’s branding, it’s now easier than ever to couple a hub with its own co-located narrative content.

⭐ Members of 2i2c’s community network can learn how to use this in our user guide to documentation and sharing. See this blog post for an announcement.

A better onboarding experience for our communities #

We have been working on a streamlined onboarding experience for communities, smoothing out the process of gathering requirements, customizing a hub for the community’s specific needs, and delivering new hubs more rapidly. We will be rolling out this process in the next few weeks for new communities onboarding the 2i2c network, and aim to continue learning and refining this process to deliver a faster, smoother onboarding experience for everyone.

⭐ Members of 2i2c’s community network will see changes to our process over the coming months that increase the speed and ease of hub delivery.

Efforts to improve and formalize the services we deliver to our communities #

As 2i2c has grown over the past few years, it organically developed internal processes for handling common tasks such as the management, rollout and maintenance of hubs, as well as expect consulting to help our communities get the most value out of their hubs. Earlier in the year, we realised it was time to review and refine these processes to better serve our growing community network. As a result of this exercise, we now have tighter service definitions and best practices which clarify what service levels our communities can expect, and how we can internally meet those expectations. We will be publishing our service definitions in the coming months as they are finalized, to ensure full transparency with our communities.

⭐ You can learn more about our efforts to standardize and scale our services by following the 2i2c blog, where we’ll share our work as it stabilizes.

Another update coming in Q3 #

We’ll be announcing the focus for our next quarter in a follow-up post, so stay tuned for our next roadmap update, and don’t forget to let us know what you think of our direction - we welcome your feedback!

Acknowledgements #

Thanks to The Navigation Fund for core support to 2i2c which funds this strategic and organizational work.

Our Product and Service goals for Q2 2025

Wed, 16 Apr 2025 00:00:00 +0000

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 should provide a high level view on how we plan to improve our product and services offerings in the next quarter. If your organization has funding available to support any of the enhancements below, reach out to us and we can discuss how you can shape our priorities and outcomes.

Give administrators more control #

The implementation of per-user storage quotas in Q1 was the start of a set of product initiatives aimed at giving hub administrators more control and peace of mind over unexpected cost overruns.

We aim to continue giving administrators more control by implementing the ability to associate users with groups for usage monitoring, and as a foundation for future improvements which will deliver group-level management of storage quotas, and later Compute and Dask quotas.

One of the wonderful things about shared open source JupyterHub infrastructure is that it allows community members to share their projects with each other in ways that ensure the work can be fully experienced by the recipient, complete with fully executable content.

In Q2, we aim to improve the ability for hub users to build custom environments in their hubs, and later to easily share those custom environments with others, ensuring their entire toolchain is replicated in full.

Out-of-the-box Jupyter Book support #

We have been working on scoping and building a default JupyterBook implementation using the new MyST document engine, aiming to deliver a default set of tools for authoring and sharing documentation, customizable landing pages and interactive training materials out of the box with new hub deployments.

In Q1 we delivered improvements to the JupyterBook launching interface to allow for automatic hub type detection, as well as landing page components, theming capabilities, galleries and more. We aim to complete this work in Q2.

A better onboarding experience for our communities #

As more communities in the research and education space join the 2i2c community network, it’s important for us to be ready to deliver the best value we can for them at scale. To that end, we’re streamlining the processes we use to onboard our communities, improving the touchpoints through which we engage with them when they join our community network, and ensuring we create opportunities to better understand their needs in order to set them up for success with their hubs right from the start.

Improve and formalize the services we deliver to our communities #

Together with an improved onboarding experience, we aim to improve how we deliver other key services to our communities, including expert consulting, hub management, and technical support, with the aim to offer more scalable, high-value services to address the needs of our communities in a sustainable way.

Some of the goals of this service revamp will include improving triaging of support tickets, shortening our issue response time, and providing our community champions with dedicated expertise on subjects including open source science and tools, community participation in open science, fundraising and grantsmanship co-creation, engineering consultancy and more.

Another update coming in Q3 #

We’ll use this blog post as an informal roadmap of our product goals for the quarter, striving to advance as many of the outlined areas as possible. During our Q3 planning, we’ll reflect on the achievements made in line with this initiative and share a progress update with our community. Keep an eye out for more details!

Acknowledgements #

Our strategic and organization-level work is supported by a grant from The Navigation Fund and fees from our member organizations.

Giuliano Maciocci

Mon, 01 Jan 0001 00:00:00 +0000

Giuliano is a product specialist with an extensive User Experience background and strong analytical skills, I help organisations define their product development roadmaps and customer engagement strategies with a user-focused, data-driven approach that starts by building a shared understanding of what constitutes value, then structures and empowers the organisational talent needed to deliver it. (from Giuliano’s LinkedIn profile)

Highlights:

10+ years experience driving growth in companies
Ex-Chief Product Officer at Ex Ordo
Ex-head of Product at eLife Sciences
Led the open science product Executable Research Article
Led Qualcomm to $65M platform sale
Contributed significantly to mobile design and innovation at Adobe.

Giuliano Maciocci | 2i2c

Announcing our public roadmap for open development

Why we’re opening up our roadmap #

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

Our Product and Service goals for Q3 2025

Demonstrable reliability of our infrastructure #

User-level costs monitoring and group-level usage monitoring #

Improving our Incident Response capability #

Piloting a feature co-funding model #

Another update coming in Q4 #

Acknowledgements #

Product and team highlights from Q2 2025

Group-level resource monitoring #

Improve creating and sharing custom environments #

Co-located narrative content with out-of-the-box Jupyter Book support #

A better onboarding experience for our communities #

Efforts to improve and formalize the services we deliver to our communities #

Another update coming in Q3 #

Acknowledgements #

Our Product and Service goals for Q2 2025

Give administrators more control #

Improve creating and sharing custom environments #

Out-of-the-box Jupyter Book support #

A better onboarding experience for our communities #

Improve and formalize the services we deliver to our communities #

Another update coming in Q3 #

Acknowledgements #

Giuliano Maciocci