Permalink
Browse files

- added categorization proposal. Thanks Ofer!

- added categorizations for Tims and Georgs proposal based on discussion in 2017-12-01 patterns group meeting
  • Loading branch information...
gruetter committed Dec 1, 2017
1 parent e890ec9 commit d5b452d130b131427da78b5ac2c9f27c0924f8fd
Showing with 43 additions and 27 deletions.
  1. +43 −27 pattern-system.md
@@ -93,11 +93,14 @@ I propose we use a classification of the problem, a pattern tries to solve as
the main criteria for organizing our list of patterns. The following
classifications come to mind:
- Getting started with InnerSource
- Getting sustainable middle management buy-in and support
- Getting buy-in of developers
- Fostering contributions
- Interfacing with traditional, non-InnerSource projects
- 1. Getting started with InnerSource
- 2. Getting sustainable middle management buy-in and support
- 3. Getting buy-in of developers
- 4. Fostering contributions
- 5. Interfacing with traditional, non-InnerSource projects
Tim: Could be tags, instead of (orthogonal) planes
Ofer: Ideas for vectors: Timeline, adoption, ...
As an additional category, we might classify the solutions provided by the
patterns into:
@@ -107,15 +110,15 @@ patterns into:
#### Test run
- 30 Day Warranty
- Common Requirements
- Contracted Contributor
- Dedicated Community Leader
- Discover Your InnerSource
- Improve Findability
- Junkyard Styled InnerSource
- Modular Code
- Review Committee
- 30 Day Warranty;1/2/3/4/5
- Common Requirements;1/4
- Contracted Contributor;1/2/4
- Dedicated Community Leader;1/4
- Discover Your InnerSource;1/4/5
- Improve Findability;? (similar to "Discover your InnerSource"?)
- Junkyard Styled InnerSource;3/4
- Modular Code;1/2/3/4/5
- Review Committee;1/2
- Change Middle Management Mindset
- Assisted Compliance
@@ -133,10 +136,11 @@ patterns into:
Another plane that would be useful is the plane of type of InnerSource.
InnerSource programs can be structured to accomplish different goals: e.g.,
* Product Development
* Tools Development
* Innovation (Proof of concepts, demos)
* Shared components development
* P: Product Development
* T: Tools Development
* I: Innovation (Proof of concepts, demos)
* S: Shared components development
* C: Culture
Each of these programs have some unique characteristics. E.g., sometimes in
Product Development, the open source characteristic of voluntariness has to be
@@ -148,15 +152,15 @@ different business lines.
#### Test run
- 30 Day Warranty
- Common Requirements
- Contracted Contributor
- Dedicated Community Leader
- Discover Your InnerSource
- Improve Findability
- Junkyard Styled InnerSource
- Modular Code
- Review Committee
- 30 Day Warranty;P/T/S
- Common Requirements;P/I/S
- Contracted Contributor;P/T/I/S
- Dedicated Community Leader;P/T/I/C
- Discover Your InnerSource;T/S
- Improve Findability (s. above)
- Junkyard Styled InnerSource;T/S/C
- Modular Code;P/T/S
- Review Committee;I/S/C
- Change Middle Management Mindset
- Assisted Compliance
@@ -271,3 +275,15 @@ I like a lot of the other planes suggestions. Wanted to add one more - the poin
- Contained InnerSource
### Ofer Hermoni
tools
security
Culture change (probably need to separate into multiple categories)
buy in
trust
etc.
Processes / Methodology
Coding practices

0 comments on commit d5b452d

Please sign in to comment.