Shared responsibility model #144
Conversation
Good since we refer to this elsewhere in our text
There was a problem hiding this comment.
I absolutely love the text here!!!!
I just put numbers on the list as it made it easier for me to review in the PR.
I also deeply appreciate the fact that the word 'tier' isn't present, as i think it's an antipattern we must avoid - I like the splitting out of 'simple' and 'complex' environment changes instead. https://ckrybus.com/static/papers/Bainbridge_1983_Automatica.pdf is a good read on why 'tiers' are an anti pattern.
Thanks a lot for working on this!
about/shared-responsibility.md
Outdated
|
|
||
| Our challenge is to figure out which responsibiltiies should lie with the community, and which should lie with the 2i2c team, to strike this balance of impact and efficiency. | ||
|
|
||
| The other reason we follow this model is that it helps us follow the [Community Right to Replicate](https://2i2c.org/right-to-replicate) their infrastructure. We think of our community hubs as being a collaboration between 2i2c and the communities that use it, and this framing helps us be explicit about where we fit into the picture. |
There was a problem hiding this comment.
This first sentence doesn't quite make sense to me. Is it supposed to say "it helps us allow the Community Right to Replicate their infrastructure"?
|
Thanks for the comments @yuvipanda and @sgibson91 - I've made some minor wording edits to address your comments! @yuvipanda I also added a reference to that paper and two blog posts about it, which I think is a really nice justification for these practices in general. |
There was a problem hiding this comment.
Looks great to me, I love the direct references to one of my favorite papers too. I've made a suggested edit to address something @sgibson91 bought up, but otherwise LGTM.
Co-authored-by: Yuvi Panda <[email protected]>
|
\o/ |
|
This is a great start, @choldgraf. |
We had a recent conversation with Berkeley where it was helpful to describe the "shared responsibility model" that 2i2c follows. We thought that this might be a helpful way to describe our various services and costs, so this PR takes a first pass at adding this to our docs and we can refine it from there.