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

Create innersource-customer-interview-questions.md #485

Merged
merged 18 commits into from
Dec 5, 2022

Conversation

kschueths
Copy link
Contributor

Submitting InnerSource Customer Interview Questions pattern

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
Submitting InnerSource Customer Interview Questions pattern

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
Copy link
Member

@spier spier left a 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 :)

@spier
Copy link
Member

spier commented Nov 26, 2022

Video of the presentation by @kschueths that this PR is likely related to:
https://www.youtube.com/watch?v=Et7-DzdY2yw

kschueths and others added 4 commits November 30, 2022 09:07

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
edit

Co-authored-by: Sebastian Spier <github@spier.hu>

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
edit

Co-authored-by: Sebastian Spier <github@spier.hu>

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
formatting edits

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
Copy link
Member

@spier spier left a 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.


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
Copy link
Member

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.

Copy link
Member

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
Copy link
Member

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.

Copy link
Contributor Author

@kschueths kschueths Dec 5, 2022

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

Copy link
Member

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.

@spier spier added the 📖 Type - Content Work Working on contents is the main focus of this issue / PR label Nov 30, 2022
kschueths and others added 7 commits December 5, 2022 11:43

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
Co-authored-by: Sebastian Spier <github@spier.hu>

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
Co-authored-by: Sebastian Spier <github@spier.hu>

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
Co-authored-by: Sebastian Spier <github@spier.hu>

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
@spier spier added the 1-initial Donuts, Early pattern ideas, ... (Please see our contribution handbook for details) label Dec 5, 2022
Copy link
Member

@spier spier left a 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.

@spier spier merged commit 0ff3925 into InnerSourceCommons:main Dec 5, 2022
@spier
Copy link
Member

spier commented Dec 5, 2022

Nice job on your first pattern @kschueths!
Thanks for sharing this with the community.

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.

None yet

2 participants