Update shared responsibility and service docs

[choldgraf]

This is an update to the language around our Service Docs and Shared Responsibility Model. There are a number of changes in here to reflect how our discussions around the service have evolved. I'll try to summarize some main points below:

• Reframe the service as a collaboration between us and other communities, in general try not to use language like "customer" and re-frame from a business transaction towards a collaboration w/ a shared goal
• Define team structures around the service inspired by our recent CZI grant. This now includes 3 sub-teams: "Community Leadership" (community), "Community Support" (2i2c), and "Cloud Infrastructure" (2i2c).
• Structure our "about the service" docs to have sections that naturally map onto the sub-teams that are a part of the service.
• Reorganize some redundant definitions between these docs and our Team Compass (cross-ref https://github.com/2i2c-org/team-compass/pull/422 because there will be some intersphinx errors until we merge the two PRs).

[choldgraf]

@yuvipanda re: collaborative, I think the use of that word came in-part out of the conversations we've had with Berkeley as well as with other communities. The goal is to try and frame the service as a two-way collaboration with "shared responsibilities", as opposed to a "managed service" which feels more like SaaS.

So I guess the challenge is that "collaborative" feels a bit vague, but "managed" evokes some of the wrong ideas about the nature of the service. Does that make sense? I think we'll need to explain what "collaboration" means via our documentation, shared responsibility diagrams, etc...but do you think it's important to use a different term?

[yuvipanda]

@choldgraf yeah, collaborative is IMO way too vague. But can we do that in a separate PR instead of blocking this one?

[choldgraf]

More than happy to do that 🙂 I'll open an issue to track terminology then:

I opened up the issue below to discuss terminology etc, so we can merge this one in:

• https://github.com/2i2c-org/infrastructure/issues/1473