Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make our Shared Responsibility Model more granular and link it to what kind of support we offer #173

Open
choldgraf opened this issue Nov 17, 2022 · 1 comment
Labels
Enhancement An improvement to something or creating something new. Product User-facing features, behavior, UX, etc

Comments

@choldgraf
Copy link
Member

Context

We define our Shared Responsibility Model here. In that model, we break down several different tasks along a spectrum of 2i2c <--> Community.

We ways to ask for Support here but do not provide an overview of what kinds of support we offer or the model we follow. We also discuss support in our SLOs page.

There are a few challenges with this:

  • Because our SRM is not granular enough, it is hard to tie its items to specific things that we might do, or that others might do. This leads to mismatches in expectations of when something is our responsibility vs. others'.
  • Because we don't provide a high-level description of the support model, communities may not have the right mental model in understanding what they should do vs. what we should do.
  • Because our SRM only discusses 2i2c and other communities, we may miss opportunities to partner with multiple communities in one service.

Proposal

Refine our Shared Responsibility and Support models to be more explicit about what needs to be done and who is in charge of what, with the goal of resolving some of the problems described above. We should define the description in docs.2i2c.org as the "source of truth", and refer to it from our Team Compass (I think this should live underneath Product in the TC).

Updates and actions

No response

@choldgraf
Copy link
Member Author

Update

This PR addressed some of this, but we should assess what, if any, other things we need to improve to make this clearer:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Enhancement An improvement to something or creating something new. Product User-facing features, behavior, UX, etc
Projects
None yet
Development

No branches or pull requests

1 participant