Sustainable InnerSource donut pattern #453
Conversation
|
Capturing a conversation with @voongc: Are sustainability and scaling two separate donut patterns? |
|
Assumptions on what the solution may contain:
|
spier
added
1-initial
|
Interesting topic @tsadler1988. Looking forward to seeing your first draft. One initial concern that I have is that the topic may run at risk of becoming too large for a single pattern. We captured the idea of a pattern dedicated to ISPO here but that idea wasn't super clear yet either. But take a look: |
Yes I could see this being separate patterns, with ISPO being one potential solution to the problem of scaling and sustaining. We mainly wanted to frame the problem of scaling/sustaining and see what the community can advise. |
|
Also see extensions-to-manage-contributions-at-scale for a project but some items can be applicable to a program |
tsadler1988
requested review from
lenucksi,
NewMexicoKid,
cewilliams,
spier and
robtuley
as code owners
|
Marked this donut pattern as ready for review, and updated the description. |
There was a problem hiding this comment.
Interesting donut pattern.
Would be good to link to other related ideas, including the ISPO pattern idea that @spier mentioned.
There was a problem hiding this comment.
Nice work @tsadler1988 and @voongc .
Please take a look at my comments. If you could add a link to this from this README section that would be great too.
Once those are done, I am happy to merge this quickly.
Having the pattern donut in the repo should allow us to chat about in more in Slack and elsewhere, to see what solutions to this people may hahve found.
|
|
||
| ## Forces | ||
|
|
||
| * The problem exists in fledgling InnerSource programmes/communities |
There was a problem hiding this comment.
This might be Context rather, as it describes the state of your InnerSource initiative, and it isn't "something that you can change at a cost" (which would make it a Force).
There was a problem hiding this comment.
Addressed by faecab8
Removed sketch and duplicate solutions Co-authored-by: Sebastian Spier <github@spier.hu>
Removes status Co-authored-by: Sebastian Spier <github@spier.hu>
Removed acknowledgments and alias Co-authored-by: Sebastian Spier <github@spier.hu>
Added a note that this still needs to be done Co-authored-by: Sebastian Spier <github@spier.hu>
Add note that this still needs to be done Co-authored-by: Sebastian Spier <github@spier.hu>
Add note that this still needs to be done Co-authored-by: Sebastian Spier <github@spier.hu>
Added authors and updated reference
removed trailing spaces
|
@tsadler1988 looks like we forgot about this Donut a bit :) As this was meant to be contributed as a Donut (i.e. no proven solution yet), shall we try to get it merged, to allow for others to find it more easily. If you could review the comments on this PR, that would be awesome. |
|
@spier I think comments are now addressed and ready for another iteration of reviews :) |
There was a problem hiding this comment.
@tsadler1988 thank you for another round of work here!
I left two minor comments.
Am happy to merge this as soon as you are ready.
|
@tsadler1988 forgot to mention that I changed the filename of the pattern. Please pull the latest commits before making further changes. |
Co-authored-by: Sebastian Spier <github@spier.hu>
|
Suggestion added for the in-line citation styling, otherwise I think this is done now. |
Co-authored-by: Tom Sadler <thomas.sadler@bbc.co.uk>
Sustainable InnerSource Program - donut pattern --------- Co-authored-by: Chan Voong <Chan_Voong@comcast.com> Co-authored-by: Chan Voong <34136874+voongc@users.noreply.github.com>
At the InnerSource Gathering last month we identified a common problem of sustaining an InnerSource programme beyond the initial push. @voongc and I volunteered to structure this as a donut pattern, in the hope that the community can provide one or more patterns than can aid this.