Move remaining patterns from sub-group "Pattern Ideas (not yet proven…

…; brainstormed)" to "Maturity Level 1: Initial". Also updating the Status in the patterens themselves. Rational: * These patterns were not all that different from the ones directl in "Maturity Level 1: Initial". * Often times they don't have a solution yet, or just a brainstormed solution. * Many of them don't have a Patlet, likely because they were written at a time when the Pattern Template didn't ask for that yet
InnerSourceCommons · Dec 26, 2020 · 262da4b · 262da4b
1 parent 1b4214b
commit 262da4b
Show file tree

Hide file tree

Showing 9 changed files with 30 additions and 23 deletions.
diff --git a/README.md b/README.md
@@ -63,9 +63,6 @@ possible to either deploy the same service in independent environments with sepa
 * [Introducing Metrics in InnerSource](patterns/1-initial/introducing-metrics-in-innersource.md) - *Involve all stakeholders in designing and interpreting metrics to measure the current status in terms of health and performance of the InnerSource initiative.*
 * [Shared Code Repo Different from Build Repo](patterns/1-initial/shared-code-repo-different-from-build-repo.md) - *Deal with the overhead of having shared code in a separate repository that isn't the same as the project-specific one that is tied to production builds.*
 * [InnerSource Portal - Hygiene](patterns/1-initial/innersource-portal-hygiene.md) - *Allow generation of an official badge for projects intending to be recognised as InnerSource project within your company.*
-
-#### Pattern Ideas (not yet proven; brainstormed)
-
 * [Overcome Acquisition Based Silos - Developers](patterns/1-initial/overcome-acquisition-based-silos-developer.md)
 * [Overcome Acquisition Based Silos - Managers](patterns/1-initial/overcome-acquisition-based-silos-manager.md)
 * [Discover Your InnerSource](patterns/1-initial/discover-your-innersource.md)

diff --git a/patterns/1-initial/change-the-developers-mindset.md b/patterns/1-initial/change-the-developers-mindset.md
@@ -51,10 +51,11 @@ TBD
 
 ## Status
 
-Unproven
-
-Old status: Pattern Idea
+* Initial
+* Old status: Unproven
+* Old status: Pattern Idea
 
 ## See Also
 
-This pattern has been moved for discussion at https://github.com/InnerSourceCommons/InnerSourcePatterns/issues/39
+This pattern has been moved for discussion at
+https://github.com/InnerSourceCommons/InnerSourcePatterns/pull/63
diff --git a/patterns/1-initial/code-consumers.md b/patterns/1-initial/code-consumers.md
@@ -42,5 +42,5 @@ _needs work...?_
 * Katrina Novakovic (RedHat)
 
 # Status
-Drafted at the 2019 Spring InnerSource Commons Summit in Galway - 10 April 2019
-
+* Initial
+* Drafted at the 2019 Spring InnerSource Commons Summit in Galway - 10 April 2019
diff --git a/patterns/1-initial/developer-incentive-alignment-for-innersource-contribution.md b/patterns/1-initial/developer-incentive-alignment-for-innersource-contribution.md
@@ -69,9 +69,9 @@ TBD
 
 ## Status  
 
-Unproven
-
-Old status: brainstormed solution
+* Initial
+* Old status: Unproven
+* Old status: brainstormed solution
 
 ## Author   
 

diff --git a/patterns/1-initial/discover-your-innersource.md b/patterns/1-initial/discover-your-innersource.md
@@ -1,6 +1,9 @@
 ## Title
 Discover Your InnerSource
 
+## Patlet
+TBD
+
 ## Also Known As
 * Not looking for stuff internally
 * Don't bother looking
@@ -58,7 +61,8 @@ Make it easy to find the reusable code.
 * See [Improved Findability](improve-findability.md) (aka Poor Naming Conventions or Badly Named Piles) as a related pattern.
 
 ## Status
-Brainstormed pattern idea in progress
+* Initial
+* Brainstormed pattern idea in progress
 
 ## Authors
 * Georg Grutter

diff --git a/patterns/1-initial/junkyard-styled-innersourcing.md b/patterns/1-initial/junkyard-styled-innersourcing.md
@@ -2,6 +2,9 @@
 * Junkyard styled inner sourcing
 * Finding but deciding not to use the internal component
 
+## Patlet
+TBD
+
 ## Context
 Two situations:
 
@@ -25,7 +28,9 @@ Two situations:
 * Provide some sort of grading (Alexander marked his patterns with 0, 1 or 2 stars depending upon how convinced he was that it was a good pattern), so that the reader can be aware of what to expect. But how to do that without insulting the contributor? (solution: engage them in the process -- have 2 scores, what they think, and what users think or how many times its been used)
 
 ## Status
-Brainstormed pattern idea in progress
+
+* Initial
+* Brainstormed pattern idea in progress
 
 ## Authors
 * Georg Grutter

diff --git a/patterns/1-initial/overcome-acquisition-based-silos-developer.md b/patterns/1-initial/overcome-acquisition-based-silos-developer.md
@@ -67,9 +67,9 @@ Partially validated. Validated means this has been seen to work in similar scena
 
 ## Status
 
-Unproven (not reviewed)
-
-Old Status: Pattern Idea - Draft In Progress
+* Initial
+* Old Status: Unproven (not reviewed)
+* Old Status: Pattern Idea - Draft In Progress
 
 ## Author
 

diff --git a/patterns/1-initial/overcome-acquisition-based-silos-manager.md b/patterns/1-initial/overcome-acquisition-based-silos-manager.md
@@ -70,9 +70,9 @@ Partially validated. Validated means this has been seen to work in similar scena
 
 ## Status
 
-Unproven (not reviewed)
-
-Old Status: Pattern Idea - Draft In Progress
+* Initial
+* Old Status: Unproven (not reviewed)
+* Old Status: Pattern Idea - Draft In Progress
 
 ## Author
 

diff --git a/patterns/1-initial/share-your-code-to-get-more-done.md b/patterns/1-initial/share-your-code-to-get-more-done.md
@@ -52,9 +52,9 @@ TBD
 
 ## Status
 
-Unproven
-
-Old status: Idea
+* Initial
+* Old status: Unproven
+* Old status: Idea
 
 ## Author