feat: Improve content of discover-your-innersource (#780)

Various improvements to the discover-your-innersource pattern.
Not yet ready to level it up to Structured, so keeping it as Initial for now.

---------

Co-authored-by: Sebastian Spier <github@spier.hu>
Co-authored-by: Isabel Drost-Fromm <isabel.drostfromm@gmail.com>

Author: 3 people

patterns/1-initial/discover-your-innersource.md

@@ -4,62 +4,53 @@ Discover Your InnerSource
 
 ## Patlet
 
-TBD
+When developers don't look for or can't find internally developed solutions, they may waste time and resources creating redundant software. To solve this, implement a robust internal search engine and processes that encourage the discovery and reuse of internal code.
 
-## Also Known As
+## Problem
 
-* Not looking for stuff internally
-* Don't bother looking
-* Find it Inside
+People don't bother looking for internally developed solutions - they might not find the repo at all or be aware of its existence.
 
 ## Context
 
 * Software component(s) are available internally but users can't easily find these.
 * This problem is more likely to occur in large, federated companies where different organizational units operate as silos.
 * Historically, the company does not have a culture of sharing code across silos.
 
-## Discussion on
-
-* Comments may appear in the timeline but not with the file once it is edited (github)?
-* https://github.com/InnerSourceCommons/InnerSourcePatterns/pull/60
-* If only X knew what X knew; the internal search engine is bad. No one can find anything because it is difficult to add things  to the search index.
-* We have similar challenges getting data sources pulled into the search engine. PayPal is building a project called Agora to do this and they are planning to open source it.
-* Github Enterprise and npmjs have built-in searches on meta-data. Enterprise that opts into these tooling will get some of that functi
-* Software component(s) are available internally but users can't easily find these.
-* This problem is more likely to occur where there are silos in the company (e.g., larger companies; smaller companies may have fewer opportunities for reuse of internally developed software).
-* The company traditionally has been bad at sharing across silos (people don't have the culture of sharing).
-
-## Problem
-
-People don't bother looking for internally developed solutions - they might not find the repo at all or be aware of its existence.
-
 ## Forces
 
 * No good internal search engine (or not connected to git repositories; and difficult to make this change happen)
 * Users may not know there are common places to find internally developed solutions.
 * People don't expect to find solutions internally.
 * Many silos in the company; difficult to reach the developer base across those silos (a communications problem).
-* People might not want to use internal SW because they don't believe it will be helpful
+* People might not want to use internal software because they don't believe it will be helpful
     - might not be maintained
     - might have poor reusability
-    - if someone put out a SW internally, the expectation is that they wouldn't have time to support it (vs. open source options)
+    - if someone put out a software internally, the expectation is that they wouldn't have time to support it (vs. open source options)
+* Difficulty in adding content to the search index makes it hard for people to find anything
 
 ## Solution
 
 Make it easy to find the reusable code.
 
-* Pull in Repo names, descriptions and README.md files into the search engine assuming that a search engine exists. Note: a one-stop-shop kind of search engine for all relevant communication and documentation is difficult to attain. Even when using Github's enterprise offering, people often deploy additional systems like wikis to host content orthogonal to what is in the code repositories, slack channels (or IRC), mailing lists (or even nntp servers), some place to store stuff written down in office formats, search over personal e-mail etc. Several of these systems come with search built-in, but integrating this content in one search box or even just deploying a federated search engine across all sources often doesn't come off-the-shelf.
-* Implement process change to first check for internal solutions for this problem.
-* Tool with a central view (but people are more inclined to google externally than look internally)
+### Behavior and Process Changes
+
+* Implement process change to motivate developers to first check for internal solutions for problems that they need to solve.
 * Concierge service (guide) to help product people find stuff. Might not scale but could be helpful in the beginning.
-* Need some very visible lighthouse projects that start using inner source components and make positive statements about the inner source program.
-* Establish a common, asynchronous communication channel (e.g., like slack or metamorph or yammer) across team boundaries. This might not scale beyond a certain organization size. It is possible people will start splitting this one channel into multiple channels by topic once traffic gets too high. Note: having one channel for many users of one tool might be considered an anti-pattern because they can't find it unless they already know about it.
+* Need some very visible lighthouse projects that start using InnerSource components and make positive statements about the InnerSource program (to increase the trust of your developers in your InnerSource components.
 * Encourage (and reward) owners of reusable code to use the same search engine to continually search for products that are candidates for use and adoption of the reusable code but not currently doing so.
-* Consider creating a marketplace for marketing InnerSource programs (management can use this mechanism to know which InnerSource projects to fund, but seeing how the marketplace reacts).
 
-## Known Instances
+### Tooling Changes
 
-TBD
+* Pull in repo names, descriptions and `README.md` files into the search engine assuming that a search engine exists. Note: a one-stop-shop kind of search engine for all relevant communication and documentation is difficult to attain. Even when using GitHub's enterprise offering, people often deploy additional systems like wikis to host content orthogonal to what is in the code repositories, slack channels (or IRC), mailing lists (or even NNTP servers), some place to store stuff written down in office formats, search over personal e-mail etc. Several of these systems come with search built-in, but integrating this content in one search box or even just deploying a federated search engine across all sources often doesn't come off-the-shelf.
+* Consider using existing tools:
+  * GitHub Enterprise and npmjs have built-in searches on meta-data
+  * PayPal's [SeazMe](https://github.com/paypal/seazme) project (previously called Agora) addresses similar challenges with data source integration
+* Tool with a central view (but people are more inclined to google externally than look internally)
+* Establish a common, asynchronous communication platform (e.g., chat based) across team boundaries.
+  * This might not scale beyond a certain organization size.
+  * Start with a single chat channel for the InnerSource project, splitting into multiple only when traffic is high. This keeps the channel active and minimizes channels for the host team. Mention this channel clearly in key docs like README.md, CONTRIBUTING.md, and onboarding materials to help users find and join the conversation.
+  * Note: having one channel for many users of one tool might be considered an anti-pattern because they can't find it unless they already know about it.
+* Create a marketplace for marketing InnerSource programs (management can use this mechanism to know which InnerSource projects to fund, by seeing how the marketplace reacts). - see [Gig Marketplace](../2-structured/gig-marketplace.md)
 
 ## Resulting Context
 
@@ -68,11 +59,21 @@ TBD
 * Developers are now looking internally for software components
 * Search results are combined (internal and external)
 * Process changes, establishing a common communications channel, and encouraging and rewarding owners of reusable code to use the same search engine can contribute to changing the corporate culture. Transformation begins from the grassroots but requires strategic involvement of thought leaders.
-* See [Improved Findability](improve-findability.md) (aka Poor Naming Conventions or Badly Named Piles) as a related pattern.
+
+<!--
+// we don't want to link from Structured patterns to Initial patterns. hence removing this link.
+// we can add this back in if the "Improved Findability" pattern is leveled up to maturity Structured
+* See [Improved Findability](../1-initial/improve-findability.md) (aka Poor Naming Conventions or Badly Named Piles) as a related pattern.
+-->
+
+## Known Instances
+
+* Nike Inc.
+* WellSky
 
 ## Status
 
-* Initial (brainstormed solution)
+* Initial
 
 ## Authors
 
@@ -83,4 +84,12 @@ TBD
 
 ## Acknowledgements
 
-* Contributions from Russ Rutledge, Ofer Hermoni and Robert Hanmer
+* Russ Rutledge
+* Ofer Hermoni
+* Robert Hanmer
+
+## Alias
+
+* Not looking for stuff internally
+* Don't bother looking
+* Find it Inside

patterns/1-initial/include-product-owners.md

@@ -57,7 +57,7 @@ Key Performance Indicators (KPIs) for Product Owners are primarily product focus
 
 ## Known Instances
 
-* PayPal is looking into finding a search solution for their project Agora. They are collaborating with other teams pursuing a similar mission, eliminating redundancy and inefficiency regarding effort and tools.
+* PayPal is looking into finding a search solution for their project [SeazMe](https://github.com/paypal/seazme) (previously called Agora). They are collaborating with other teams pursuing a similar mission, eliminating redundancy and inefficiency regarding effort and tools.
 
 ## Status