Colors and major teams

Service Applications Team

Content + training

Cloud Engineering Team

Cloud development + operations

Community Guidance Team�Bridge to communities + leadership support

Community of Practice

Goal 1

Goal 2

Goal 3

Goal 4

Connections provided via bridges to key communities

Connections grown through training and community guidance

Team and Project Management

Governance and Sustainability

Collaboration Strategy

Cloud Engineering Team

Service Applications Team

Community Guidance Team

Expertise in cloud infrastructure operations and open source development to provide infrastructure

Expertise in intended workflows and applications of cloud infrastructure and open science to guide usage.

Experts in community-centric management and leadership, bridge to leaders of a community.

Communicate around infrastructure and incidents

Co-develop Open Source Software

Share infrastructure management skills

Refine and discuss issues to improve service

Align on direction of service and tools

Prioritize and plan development efforts

Communicate change requests and issues

Co-create content to guide users

Teach workshops around cloud workflows

Cloud service collaboration model

Community Leaders

Formal and informal leaders that are interested in representing their community and guiding others.

Identify and Onboard community leaders

Pedagogy training so leaders can teach others

Leadership training to improve connections and open practices

Key points of collaboration between teams

2i2c-org/docs

2i2c-org/infrastructure

af.2i2c.cloud

Cloud Engineering Team

Community Guidance Team

sa.2i2c.cloud

Service Applications Team

…

…

Cloud Infrastructure and Materials

Latin American Communities

African�Communities

hubB.af.2i2c.cloud

hubA.af.2i2c.cloud

hubA.sa.2i2c.cloud

hubB.sa.2i2c.cloud

community docs

🌎

Documentation�and Training Material

Community Hubs

Cloud Infrastructure

Kubernetes Clusters

Community Leaders

Shared

responsibility model - infrastructure

Hub administration

Environment + data

Infrastructure support

Software development

Use-cases

Hub configuration

Kubernetes Cluster

Incident response

Community Responsibility

2i2c Responsibility

Community Leaders

Cloud�Engineer Team

Collaboration and discussion

Community Responsibility

2i2c Responsibility

Shared Responsibility

Shared

responsibility model - community

Represent community needs

Community communications

Community Workshops

User Support

Manage community structure

Guide community leaders

2i2c documentation

Content and Docs

2i2c

Community Leaders

Community Infrastructure Team

Collaboration and discussion

Community

Community Responsibility

2i2c Responsibility

Shared Responsibility

Raw figures and brainstorms

Community connection cycle

• ​
• Connect with a new community (who would do it, how would they get connected etc)
• Decide what kind of infrastructure to serve them (do they need their own hub, join a pre-existing hub, etc?)
• Connect them with documentation (e.g., does this content live in a 2i2c space? A community space?)
• Set up a plan for training and make an event (e.g. do we do workshops in batches or have one per community)
• Run the event (e.g., who is the one running the actual workshops)
• Do a follow-up (e.g., do they continue using the hub if they wish? How do we remain engaged with them?)

Timeline of major actions

Y0

Y1

Y2