Skip to content

Commit 3fead95

Browse files
committed
Moving wiki pages to repo. Block: "Pattern Donuts (needing a solution)".
Details: - port 3 wiki pages into this repo - remove "Donut:" prefix in README - link one Donut to it's PR - last Donut could not be found in the wiki: [Donut 8: Not Invented Here](https://github.com/InnerSourceCommons/innersourcecommons.org/wiki/Donut-8:-Not-invented-here)
1 parent 5dc6ae9 commit 3fead95

File tree

4 files changed

+141
-4
lines changed

4 files changed

+141
-4
lines changed

README.md

Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -48,11 +48,11 @@ possible to either deploy the same service in independent environments with sepa
4848

4949
#### Pattern Donuts (needing a solution)
5050

51-
* [Donut 3: How to Defeat the Hierarchical Constraints](https://github.com/InnerSourceCommons/innersourcecommons.org/wiki/Donut-3%3A-how-to-defeat-the-hierarchical-constraints)
52-
* [Donut 5: Project Management Time Pressures](https://github.com/InnerSourceCommons/innersourcecommons.org/wiki/Donut-5:-project-management-time-pressures)
53-
* [Donut 6: Organizational Mindset Change](https://github.com/InnerSourceCommons/innersourcecommons.org/wiki/Donut-6:-organizational-mindset-change)
51+
* [How to Defeat the Hierarchical Constraints](defeat-hierarchical-constraints.md)
52+
* [Project Management Time Pressures](https://github.com/InnerSourceCommons/InnerSourcePatterns/pull/47)
53+
* [Organizational Mindset Change](organizational-mindset-change.md)
5454
* [Donut 8: Not Invented Here](https://github.com/InnerSourceCommons/innersourcecommons.org/wiki/Donut-8:-Not-invented-here)
55-
* [Donut: Bad Weather For Liftoff](https://github.com/InnerSourceCommons/innersourcecommons.org/wiki/Donut:-Bad-weather-for-liftoff)
55+
* [Bad Weather For Liftoff](bad-weather-for-liftoff.md)
5656
* [Get Contributions Despite Silo Thinking](https://github.com/InnerSourceCommons/InnerSourcePatterns/pull/38)
5757

5858

@@ -95,6 +95,7 @@ The topics below cover information about how we define, operate, and upkeep this
9595
* [Meetings](meta/meetings.md) - Become involved with the people and communications of the Inner Source Patterns group
9696

9797
# Related References
98+
9899
* [A pattern language for pattern writing](http://hillside.net/index.php/a-pattern-language-for-pattern-writing), Meszaros and Doble
99100

100101
# Licensing

bad-weather-for-liftoff.md

Lines changed: 52 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,52 @@
1+
## Title
2+
3+
Bad weather for liftoff
4+
5+
## Patlet
6+
7+
TBD
8+
9+
## Problem
10+
11+
- The team is not able to demonstrate any increases in quality or speed, because they did not adopt any of the principles of OSS development.
12+
- As a result, the InnerSource approach is discredited.
13+
14+
## Context
15+
16+
- Company A would like to start an InnerSource initiative in order to increase development speed and quality of software artifacts.
17+
- There are not many developers in company A, which are experienced in OSS development practices.
18+
- The company was not able to contract or hire an experienced InnerSourcerer.
19+
- Company A has put together a small team of software developers to work on a single project InnerSource style. The project has tight deadlines to meet.
20+
21+
## Forces
22+
23+
- By default, humans will be resistant to change if they have no compelling reason to change.
24+
- Pressure (in this case induced by the project being a pilot and also induced by the deadline) reduces the ability to change and explore new ways of working.
25+
- There is a natural tendency to pick low hanging fruits (e. g. tooling) and stop there.
26+
- For InnerSource to blossom, a critical mass of experienced developers which can walk the talk is required.
27+
28+
## Sketch (optional)
29+
30+
## Solution
31+
32+
TBD
33+
34+
## Resulting Context
35+
36+
## Rationale (optional)
37+
38+
## Known Instances (optional)
39+
40+
## Status
41+
42+
Donut
43+
44+
## Author(s)
45+
46+
* Georg Grütter, Wyane DuPont, Michael Dorner
47+
48+
## See Also
49+
50+
This pattern was originally created in this wiki and then ported here.
51+
Original wiki page:
52+
https://github.com/InnerSourceCommons/innersourcecommons.org/wiki/Donut:-Bad-weather-for-liftoff

defeat-hierarchical-constraints.md

Lines changed: 41 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,41 @@
1+
## Title
2+
3+
Defeat Hierarchical Constraints
4+
5+
## Patlet
6+
7+
TBD
8+
9+
## Problem
10+
11+
Corporate culture constrains people to hierarchical goals.
12+
13+
## Context
14+
15+
In strongly hierarchical organizations, developers want to please their managers. Their managers may not support their people spending time on inner sourcing even if someone higher up does. In some countries, there is a strong cultural force to respect and obey authority.
16+
17+
## Forces
18+
19+
To make inner sourcing work, you need to allow some developers outside your org to participate in your development.
20+
Managers have deadlines and they don’t see how having their people will help them achieve *their* goals and objectives. They may feel it slows them down.
21+
Even if there is nominal higher support for the goals, developers may still feel afraid to take that step.
22+
23+
## Solutions
24+
25+
TBD
26+
27+
## Resulting Context
28+
29+
Developers feel empowered to spend at least 20% of their time on inner sourcing
30+
31+
## Status
32+
33+
Donut
34+
35+
## Author(s)
36+
37+
## See Also
38+
39+
This pattern was originally created in this wiki and then ported here.
40+
Original wiki page:
41+
https://github.com/InnerSourceCommons/innersourcecommons.org/wiki/Donut-3%3A-how-to-defeat-the-hierarchical-constraints

organizational-mindset-change.md

Lines changed: 43 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,43 @@
1+
## Title
2+
3+
Organizational Mindset Change
4+
5+
## Patlet
6+
7+
TBD
8+
9+
## Problem
10+
11+
How do you effect an organizational mindset change to support inner sourcing?
12+
13+
## Context
14+
15+
Upper management, middle management and developers are not convinced to fully support inner sourcing. They are used to doing software development in the old way.
16+
17+
## Forces
18+
19+
Changing an organizational mindset takes time and effort, which most organizations (feel they) cannot afford.
20+
Inner sourcing could bring about a lot of desirable benefits, but it takes time to ramp up to deliver them.
21+
Changing executive mindsets usually requires hype which then is hard deliver on.
22+
KPIs to prove the benefits are often required early but choosing the wrong KPIs can severely warp the program.
23+
Pressure from competitors and the market place makes management less willing to try significant change (deemed too risky).
24+
25+
## Solutions
26+
27+
TBD
28+
29+
## Resulting Context
30+
31+
All of the company heartily adopts inner sourcing! Cake for everyone!
32+
33+
## Status
34+
35+
Donut
36+
37+
## Author(s)
38+
39+
## See Also
40+
41+
This pattern was originally created in this wiki and then ported here.
42+
Original wiki page:
43+
https://github.com/InnerSourceCommons/innersourcecommons.org/wiki/Donut-6:-organizational-mindset-change

0 commit comments

Comments
 (0)