Skip to content

Commit 17d6762

Browse files
jeffabaileyMaineC
andauthored
Update patterns/2-structured/discover-your-innersource.md
Co-authored-by: Isabel Drost-Fromm <[email protected]>
1 parent ba32a05 commit 17d6762

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

patterns/2-structured/discover-your-innersource.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -42,7 +42,7 @@ Make it easy to find the reusable code.
4242
* Need some very visible lighthouse projects that start using InnerSource components and make positive statements about the InnerSource program.
4343
* Establish a common, asynchronous communication platform (e.g., chat based) across team boundaries.
4444
* This might not scale beyond a certain organization size.
45-
* It is possible people will start splitting this one channel into multiple channels by topic once traffic gets too high.
45+
* When using common chat systems, start with one single chat channel for the InnerSource project, only split into multiple channels by topic once traffic gets too high. This way the channel feels alive. In addition the number of input channels to watch is kept at a minimum for the host team.
4646
* 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.
4747
* 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.
4848
* 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). - see [Gig Marketplace](../2-structured/gig-marketplace.md)

0 commit comments

Comments
 (0)