-
Notifications
You must be signed in to change notification settings - Fork 191
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
Create innersource-customer-interview-questions.md #485
Conversation
Submitting InnerSource Customer Interview Questions pattern
patterns/2-structured/innersource-customer-interview-questions.md
Outdated
Show resolved
Hide resolved
patterns/2-structured/innersource-customer-interview-questions.md
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for sharing this @kschueths!
I suspect this is related to your summit talk "InnerSource Sleuth: Identifying Your Pain Points", right? Nice!
We won't be able to merge this PR before the summit, hopefully this doesn't create any issues for you?
I left two quick comments inline. Fixing those in the rest of the file as well will get rid of most of the automatic formatting warnings.
Will read this again in more detail after the Summit :)
patterns/2-structured/innersource-customer-interview-questions.md
Outdated
Show resolved
Hide resolved
patterns/2-structured/innersource-customer-interview-questions.md
Outdated
Show resolved
Hide resolved
Video of the presentation by @kschueths that this PR is likely related to: |
edit Co-authored-by: Sebastian Spier <github@spier.hu>
edit Co-authored-by: Sebastian Spier <github@spier.hu>
formatting edits
patterns/2-structured/innersource-customer-interview-questions.md
Outdated
Show resolved
Hide resolved
patterns/2-structured/innersource-customer-interview-questions.md
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@kschueths thank you again for sharing this pattern.
I left some comments inline.
Looking forward to your feedback and to the discussion.
patterns/2-structured/innersource-customer-interview-questions.md
Outdated
Show resolved
Hide resolved
patterns/2-structured/innersource-customer-interview-questions.md
Outdated
Show resolved
Hide resolved
patterns/2-structured/innersource-customer-interview-questions.md
Outdated
Show resolved
Hide resolved
patterns/2-structured/innersource-customer-interview-questions.md
Outdated
Show resolved
Hide resolved
|
||
InnerSource can address a number of areas that impact collaboration. The problem is determining what organizational pain points to address first. People want every pain point that InnerSource can address, solved fast. Evaluating team needs can be ambiguous if the conversation is not structured around an InnerSource framework. | ||
|
||
## Context |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I recommend to format both Context and Forces with bullet points.
That makes it easier for readers to check these one-by-one to confirm if these points apply to them.
Also check Context and Forces for possible duplication between the two sections.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would still recommend to do this.
However now that this pattern is in status "Initial", we can work this out some time later.
Keeping this thread open for reference.
@@ -0,0 +1,74 @@ | |||
## Title | |||
|
|||
InnerSource Customer Interview Questions |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Any chance we can leave "InnerSource" out of the title?
We are frequently at risk of having this word in every pattern title, which then removes meaning from the word. So we try to use it less frequently if possible.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Clare had told me to add it in there on this one. I originally didn't have it in the title
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see. @claredillon anything you can add here about your reasoning around the title of this pattern?
FYI the title is less of a pressing issue, now that this pattern is in status "Initial".
We can work this out some time later.
Co-authored-by: Sebastian Spier <github@spier.hu>
Co-authored-by: Sebastian Spier <github@spier.hu>
Co-authored-by: Sebastian Spier <github@spier.hu>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As we agreed to keep this pattern as Initial for now, I am opting to merge this quickly, to give more exposure to the pattern. We can still improve this in subsequent PRs, before it moves to Structured and into our book.
Nice job on your first pattern @kschueths! |
Submitting InnerSource Customer Interview Questions pattern