2i2c

This page has our licensing policy: https://compass.2i2c.org/open-source/ip/#intellectual-property

Our Right to Replicate describes the principles we follow in how we choose to design the infrastructure and service model: https://2i2c.org/right-to-replicate/

Cloud S3 storage Kubernetes layers in major commercial cloud providers GitHub

There are a lot of different kinds of communities we might use to answer this, but here are some relevant pages for a few key types of communities.

Our key stakeholders page defines the types of communities we aim to serve: https://compass.2i2c.org/organization/mission/

Our shared responsibility model page describes the kinds of roles that exist in the service and how we aim to share them with communities: https://docs.2i2c.org/about/service/

Our Open Source Strategy section describes the approach we take towards engaging with and supporting OS communities: https://compass.2i2c.org/open-source/

All of these are continually evolving, but are a good first start. See also calendars and meetings: https://compass.2i2c.org/reference/calendar/

We take a lot of inspiration from the Principles of Open Scholarly Infrastructure, though we have not formally audited ourselves in comparison to those criteria. This is something we'd love to do, just haven't had time yet (and feel like an external org should do the auditing, not us).

2i2c is governed by a Steering Council, and is a fiscally sponsored project of Code for Science & Society, a US-based 501(c)3. Additional governance development is in progress.

2i2c was created by its current Steering Council, who also act as its founding partners. This group roughly came from three projects that similarly operated cloud infrastructure for interactive computing:

• The Berkeley DataHub is an institution-wide JupyterHub that was led in-part by Yuvi Panda, Chris Holdgraf, Cathryn Carson, and Fernando Perez.
• The Syzygy project (https://syzygy.ca) is a network of JupyterHubs for Canadian universities that was led in-part by Jim Colliander.
• The Pangeo project (https://pangeo.io) is a community platform for Big Data geoscience that is built on a JupyterHub and cloud computing, and is led in-part by Ryan Abernathey.

Each of these projects demonstrated considerable value for the communities it served, but it was also clear that this model was unsustainable for most other communities of practice due to difficulties in hiring for cloud engineering skills.

As a result, communities tended to use proprietary services that weren't aligned with the values many of us identified with (e.g., community-driven infrastructure, values-based organizations, non-profit structures, etc).

We created 2i2c in order to have a mission-driven and community-focused organization that could design and manage cloud infrastructure on behalf of communities of practice, but that framed the partnership as a collaboration based around shared responsibility and transparency rather than a pure "consumer / producer relationship". We also wanted to ensure that 2i2c would commit to making upstream contributions and support as part of its key mission, in order to avoid the extractive relationship many organizations have with open source.

2i2c aims to identify a self-sustaining cost recovery model with ongoing service fees for communities that it partners with in managing cloud infrastructure. We also pursue several other funding streams to advance our mission in open infrastructure for open science.

Below are a few areas where we are actively seeking funding.

• Cloud and service costs for one or more communities that cannot afford the full price of a monthly service.
• Development projects to enhance open source technology that is critical for open science and education.
• Broader community and technical support for the key open source communities in which we participate.
• Organizational service development funding runway to explore and refine our model for sustainably serving infrastructure.