Skip to content

Pattern idea: Crossing the chasm #368

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

Merged
merged 13 commits into from
May 14, 2022

Conversation

MaineC
Copy link
Member

@MaineC MaineC commented Nov 18, 2021

On slack a presentation was shared on the adoption cycle for InnerSource: https://innersourcecommons.slack.com/archives/C04PXKRN4/p1636027720045600?thread_ts=1636027623.045400&cid=C04PXKRN4

This pull request is a first draft at providing a pattern for what InnerSource initiatives can do to reach teams and people at different places on the adoption curve.

ping @rrrutledge

@MaineC MaineC added the 1-initial Donuts, Early pattern ideas, ... (Please see our contribution handbook for details) label Nov 18, 2021
@MaineC MaineC requested review from spier and rrrutledge November 18, 2021 18:03
@rrrutledge
Copy link
Contributor

Neat! Will take a look maybe next week sometime.

@spier
Copy link
Member

spier commented Nov 21, 2021

@MaineC thanks for pushing this idea from the slack conversation more into the open.

The pattern would be a lot easier to understand if the reader could see the adoption curve and resulting chasms visually (such visuals are referenced in the Slack thread).

Do you think we should try to contact the original author, to see if we would be able to use those visuals and also reference them as a known instance? Of course it would also be great if the author could review this pattern draft, to make sure that we are capturing the ideas correctly.

@spier spier added the 📖 Type - Content Work Working on contents is the main focus of this issue / PR label Nov 21, 2021
@MaineC
Copy link
Member Author

MaineC commented Nov 22, 2021

@spier First of all thank for filling in the references to existing patterns - I pushed the draft before fixing those todos ...

I agree with you that the patterns would be easier to understand if it used the visuals we had in the slack conversation from the talk. The visuals in the talk themselves actually are older coming from a book that is still on my (way too high) pile of books to read:

https://www.goodreads.com/book/show/61329.Crossing_the_Chasm

It would be awesome to have the original author of the slides engage here. I haven't seen them active on Slack (maybe I have missed that), but I'll get in touch with them through e-mail.

Thanks for the early review.

MaineC and others added 2 commits November 29, 2021 09:00
Co-authored-by: Johannes Tigges <lenucksi@users.noreply.github.com>
@spier spier changed the title Crossing the chasm Pattern ideaL: Crossing the chasm Dec 14, 2021
@spier spier changed the title Pattern ideaL: Crossing the chasm Pattern idea: Crossing the chasm Dec 14, 2021
@spier
Copy link
Member

spier commented Dec 14, 2021

@MaineC are you open to merging this pattern relatively quickly, so that it becomes easier for readers to discover this pattern idea?

We can and should still improve the pattern in subsequent PRs.
And of course if we could get other people involved that would be awesome too.

@MaineC
Copy link
Member Author

MaineC commented May 13, 2022

I think given that all conversations are resolved we should merge this pattern to make it visible to others. We can improve it going forward from there.

@spier spier merged commit fcc8389 into InnerSourceCommons:main May 14, 2022
@spier
Copy link
Member

spier commented May 14, 2022

Sounds good. Done!

FYI I will also add a link to the pattern from the main README, so that people can more easily find it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1-initial Donuts, Early pattern ideas, ... (Please see our contribution handbook for details) 📖 Type - Content Work Working on contents is the main focus of this issue / PR
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants