Pattern: All Roads Lead to InnerSource - further work

Worked on Context and Forces.

patterns/1-initial/all-roads-lead-to-innersource-contributions.md

@@ -4,6 +4,7 @@ All Roads Lead to InnerSource (Contributions)
 
 ## Patlet
 
+TODO
 Concise 1-2 sentence description of the problem and solution.
 Readers may quickly review dozens of these patlets to discover and browse the larger library of patterns.
 From http://wiki.c2.com/?PatLet
@@ -12,46 +13,50 @@ From http://wiki.c2.com/?PatLet
 
 Projects are adopting InnerSource, but struggling to convert users, consumers or stakeholders into contributors, or forming a community.
 
+In this context, the InnerSource Program is considered also an InnerSource Project.
+
 ## Story (optional)
 
+TODO
 Sometimes there is a story that helps people understand the pattern better.
 
 ## Context
 
-Where does the problem exist?
-What are the pre-conditions?
-**Unchangeable** before the solution goes into place.
-The content here is often tied to the applicability of the pattern for other readers: "Do I have this same particular situation?"
+Users of a service, library or application (software), as well as consumers of any kind of InnerSource content (e.g. documentation), are unaware of the InnerSource project behind the software or content, or even unaware of the InnerSource concept.
 
 ## Forces
 
-What makes the problem difficult?
-What are the trade-offs?
-These are constraints that **can be changed** at a cost.
-The solution might change one or more of these forces in order to solve the problem, while also in-turn changing the context.
+Project maintainers do not see the conversion of users, consumers and interested parties into contributors as a user experience challenge that they need to solve.
+
+Project maintainers are unaware that they potential contributors may not be familiar with InnerSource.
 
 ## Sketch (optional)
 
+TODO
 visual illustration
 
 ## Solutions
 
+TODO
 Verified resolutions and possible resolutions to the problem.
 
 ## Resulting Context
 
+TODO
 What is the situation after the problem has been solved?
 The original context is changed indirectly by way of the solution.
 Often this section can include discussion of the next possible Patterns/problems introduced.
 This section can be short in content - the solution may not introduce new problems or change much context.
 
 ## Rationale (optional)
 
+TODO
 Explains why this is the right solution; using totally different words WHY this solution balances these forces and this context to solve this problem.
 Can expand on what-if's or theories.
 
 ## Known Instances (optional)
 
+TODO
 Where has this been seen before?
 Helps to reinforce that this is a REAL pattern and that you match the context.
 
@@ -66,16 +71,16 @@ Initial
 
 ## Author(s) (optional)
 
-Often, this is yourself.
-If you need to, find someone in the InnerSource Commons to be the nominal author (As Told To).
-Could also be no-one if you do not want to take on authorship (common with a donut looking for a solution).
+Guilherme Dellagustin
 
 ## Acknowledgments (optional)
 
+TODO
 Include those who assisted in helping with this pattern - both for attribution and for possible future follow up.
 Though optional, most patterns should list who helped in their creation.
 
 ## Alias (optional)
 
+TODO
 If this pattern is also known under a different name than what is listed unter **Title**, please list those alternative titles here.
 e.g. if the pattern is named after the problem it solves, a helpful alias might be one that describes the solution that is applied.