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

Address review comments for InnerSource Hackathon pattern #721

Merged
merged 16 commits into from
Nov 5, 2024
Merged
Changes from 12 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions patterns/1-initial/innersource-hackathon.md
Original file line number Diff line number Diff line change
Expand Up @@ -16,10 +16,10 @@ The company wants to adopt InnerSource as software development methodology but o

The senior leadership believes in InnerSource and wants to drive it throughout the company. The engineers who are familiar with open source principles and/or understand the benefits of InnerSource are the early adopters. There is success with these initial pilot project and teams. Now the next step is to drive it across the company. There might be reluctance from engineering teams due to various factors like:
spriya-m marked this conversation as resolved.
Show resolved Hide resolved

* not familiar with InnerSource and being ignorant to know about it
* not familiar with InnerSource and not aware about it
spriya-m marked this conversation as resolved.
Show resolved Hide resolved
* not enough time to prioritize InnerSource, given the regular work deliverables
* relunctance to changing ways of working when everything works well already
spier marked this conversation as resolved.
Show resolved Hide resolved
* perception that InnerSource requires more work and responsibilities
* unclear ROI for the upfront setup innersourcing takes
spriya-m marked this conversation as resolved.
Show resolved Hide resolved

### Scenario 2: Challenges in getting contributions and building community around InnerSource projects

Expand Down
Loading