Service model#

What 2i2c does for member communities, and how we fund it. See Pricing strategy for numbers and Value proposition for persona messaging.

Areas of service: DOCS#

We support member communities in four key areas, which we call DOCS: Develop, Operate, Connect & Advise, and Steward. Memberships blend all four, while directed engagements usually emphasize a subset of them.

Area

What it is

Develop

Develop and customize software to meet community needs, usually via upstream open source contributions.

Operate

Deploy and run infrastructure on behalf of communities, usually via one or more JupyterHubs on a cloud service.

Connect & Advise

Connect communities and funders, sense shared problems, and advise on strategy and design with our communities.

Steward

Maintain and lead the upstream open source projects our communities depend on. This includes both technical and social support.

Develop covers member-driven contributions that address a specific member community’s need. Steward covers foundational contributions that keep the ecosystem healthy regardless of any one member’s need, along with broader project leadership and community support.

Membership and directed engagements#

There are two ways to support our work - membership is a common base for every contract, and directed engagements stack in addition.

General Membership

sustains a shared baseline across all four areas, renewed annually. See the service description for what each tier includes. It keeps hubs running and funds upstream work.

Premier membership

adds additional capacity for our impact, provides deeper roadmap influence, as well as additional time for engaging in the four areas described above.

Directed engagements

add dedicated capacity on top, at our rate. A member puts extra funding behind one or more areas and helps steer it.

Example 1: a member community co-funds roadmap project that leads with Develop, but also involves running a prototype hub (Operate) and extra upstream engagement (Steward) as result.

Example 2: A member with no hub points a directed engagement entirely at Steward because they wish for directed support to go towards an upstream community they depend on.

Example 3: A member joins another community’s hub. They share the cost of that community’s Operate and use Connect & Advise to design their shared sociotechnical community.