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.

Sign up for GitHub

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

Jump to bottom

Address review comments for InnerSource Hackathon pattern #721

Open
wants to merge 13 commits into
base: main
Choose a base branch
from
Open

Address review comments for InnerSource Hackathon pattern #721

Changes from 12 commits
Commits
Show all changes
13 commits
Select commit Hold shift + click to select a range
12b38c1
create innersource-hackathon.md
spriya-m Jun 27, 2024
e095c2e
fix lint issues
spriya-m Jun 27, 2024
b35000f
fix markdown lint issues
spriya-m Jun 27, 2024
8e00bad
fix markdown lint issues
spriya-m Jun 27, 2024
04bee50
update patterns/1-initial/innersource-hackathon.md
spriya-m Jun 29, 2024
380725d
update patterns/1-initial/innersource-hackathon.md
spriya-m Jun 29, 2024
c989135
Update patterns/1-initial/innersource-hackathon.md
spriya-m Jul 1, 2024
f0c4f93
Update patterns/1-initial/innersource-hackathon.md
spriya-m Jul 1, 2024
01db7de
Expand subsection headers
spier Jul 1, 2024
130e45f
Expand subsection headers
spier Jul 1, 2024
39a7c9f
Merge branch 'InnerSourceCommons:main' into main
spriya-m Oct 7, 2024
6343833
Update innersource-hackathon.md
spriya-m Oct 7, 2024
800705a
Fixing typo - reluctance
spier Oct 9, 2024
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
View file
Open in desktop
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:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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:
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:

Splitting this into 2 paragraphs to make it easier to read.


* not familiar with InnerSource and being ignorant to know about it
* not familiar with InnerSource and not aware about it
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"not familiar" and "not aware" sounds like saying the same thing twice now. I am not sure though.

I have also asked in the thread in slack if anybody has a better proposal.

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

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
* unclear ROI for the upfront setup innersourcing takes
* unclear return on investment for the upfront setup costs that an InnerSource project takes

We try to stick to the spelling InnerSource, wherever possible. See explanation.

Also I removed an acronym and elaborated on the sentence a bit


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

Expand Down
Loading