Skip to content

Commit 0f547b6

Browse files
authored
Merge pull request #172 from spier/explain-pattern-categorization
Document the approach used for the pattern categorization
2 parents 791c415 + 66a6ec6 commit 0f547b6

File tree

3 files changed

+28
-0
lines changed

3 files changed

+28
-0
lines changed

pattern-categorization/README.md

Lines changed: 28 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,28 @@
1+
# Pattern Categorization
2+
3+
We see more and more patterns being contributed by the InnerSource community. That is awesome!
4+
5+
Now how do we make it easier for readers to discover the patterns that can help them in their particular situation?
6+
7+
## InnerSource Program Mind Map
8+
9+
This first categorization effort uses a mind map to categorize patterns based on the different phases of an InnerSource Program, and the challenges that might appear in the respective phases. See [innersource-program-mind-map.html](innersource-program-mind-map.html). Note that this is still in incomplete visualization i.e. it does not contain all of our patterns.
10+
11+
To add new patterns to the mind map, edit the source file `innersource-program-mind-map.md`, and then regenerate the visualization like this:
12+
13+
```
14+
npm install markmap-lib -g
15+
markmap innersource-program-mind-map.md
16+
```
17+
18+
## Future Ideas for Categorization
19+
20+
We have some other ideas for categories by which the InnerSource Patterns could be grouped.
21+
22+
One is **management and empowerment**. Some patterns help to manage, govern, mitigate risk. Some other patterns help to empower, attract, build communities. This categorization can help others to quickly find the group of patterns that fit their needs.
23+
24+
Another angle is **single project vs organization**. Some patterns are applicable to single project, while others are organizational effort. For people working on specific initiative, single project level patterns might be more interesting. For people working on scaling InnerSource, organizational patterns are important.
25+
26+
## References
27+
28+
The idea for categorizing patterns is loosely based a description in [Thoughts on an InnerSource Pattern Language](https://drive.google.com/file/d/13AY8glCOdpLOVuz7cVD6QOB8d2xbHCS1/view) by Tim Yao, Bob Hanmer and Padma Sudarsan (2018). For specifics see slide 15 in that slide deck.
File renamed without changes.
File renamed without changes.

0 commit comments

Comments
 (0)