InnerSourcePatterns
InnerSourcePatterns copied to clipboard
InnerSourceCommons
Proven approaches that can guide you through applying open source best practices within your organization
This pull request continues the work of #102 that became unavailable for edits due to no access to the originating `fmr-llc` org. Please add any additions you may come up...
The Contracted Contributor Pattern mentions an **InnerSource governance office (ISGO)**. See [code](https://github.com/InnerSourceCommons/InnerSourcePatterns/blame/master/patterns/2-structured/contracted-contributor.md#L55-L58). I wonder if that is another name for the [Review Committee](https://github.com/InnerSourceCommons/InnerSourcePatterns/blob/master/patterns/2-structured/review-committee.md)?
Many of the patterns don't have any visuals today. That makes them a bit boring to look at, and it is also harder to remember a pattern that you have...
This idea comes from breakout #3 of the ISC Fall Summit 2020, documenting it here so that it does not get lost: Offer additional visual mindmaps like the pattern categorization...
Story provides a more narrative, less academic description to a pattern. When a pattern has a good narrative description at the first few sections, it helps people deciding quickly whether...
Going straight from closed-source to Open Source is not always possible, and it can also be a hard transition for the maintaining team as the required processes are very different....
# Problem - Teams with resource constraints may be reluctant to adopt InnerSource (accept contributions), due to fear of missing resources to review and integrate them in reasonable time -...
I noticed that the markdownlint GitHub Action that we have is running twice on the same PR. It is mostly a cosmetic problem and it also might be a bit...
Idea: how about we add a _Revision History_ section, @spier , @lenucksi ? I feel it's kinda odd to have more than one entry in the _Status_ section. Just my...
Metadata
Owner
Metadata
Proven approaches that can guide you through applying open source best practices within your organization