This repository serves as the collection-point, ideation hub, and process behind the InnerSource Commons' InnerSource Patterns--a set of proven and reviewed solutions to InnerSource problems. These patterns illustrate beneficial activities and behaviors found in organizations who apply InnerSource methodologies. See below the list for more on what a pattern is, how to use them in your organization, and how to get involved.

The below lists all known patterns. They are grouped into four stages of maturity.

• 30 Day Warranty - a pattern for getting a reluctant code-owning team to accept code submissions from outside their team.
• Common Requirements - Common code in a shared repository isn't meeting the needs of all the project-teams that want to use it; this is solved through requirements alignment and refactoring.
• Contracted Contributor - Associates wanting to contribute to InnerSource are discouraged from doing so by their line management. Relief is provided by formal contracts and agreements.
• Dedicated Community Leader - Select people with both communications and technical skills to lead the communities to ensure success in starting an InnerSource initiative.
• Gig Marketplace - Establish a marketplace by creating an intranet website that lists specific InnerSource project needs as "Gigs" with explicit time and skill requirements. This will enable managers to better understand their employee’s time commitment and professional benefits thereby increasing the likelihood of garnering approval to make InnerSource contributions.
• InnerSource Portal - Create an intranet website that indexes all available InnerSource project information. This will enable potential contributors to more easily learn about projects that might interest them and for InnerSource project owners to attract an outside audience.
• Praise Participants - Thank contributors effectively to engender further engagement from them and to encourage others to contribute
• Review Committee - A formal review committee is setup within an org to "officiate" particular inner source projects with resources, etc.
• Service vs. library: It's inner source, not inner deployment - Teams in a DevOps environment may be reluctant to work across team boundaries on common code bases due to ambiguity over who will be responsible for responding to service downtime. The solution is to realize that often it's possible to either deploy the same service in independent environments with separate escalation chains in the event of service downtime or factor a lot of shared code out into one library and collaborate on that.
• Trusted Committer - Many inner-source projects will find themselves in a situation where they consistently receive feedback, features, and bug-fixes from contributors. In these situations project maintainers seek ways to recognize and reward the work of the contributor above and beyond single contributions.

• Modular Code - Management does not want to spend the extra resources needed to develop modular components and make them available in a visible repository for others to use.
• Improve Findability - People can't find the internally developed solutions that they need due to poor naming conventions. This causes frustration in finding inner source solutions and a reduction in code reuse.

• Assisted Compliance - Helping repo owners be compliant by writing their CONTRIBUTING.md for them as a pull request.
• Cross-Team Project Valuation - It's hard to sell the value of cross-team, inner sourced projects that don't provide a direct impact on company revenue. Here's a data-driven way to represent your project that both articulates its value and amplifies it.
• Reluctance to Receive Contributions - Core owner of shared asset is reluctant to take contributions due to the required maintenance that comes with them.
• What Before How or Services Documentation - A lack of common understanding between different management tiers creates funding barriers and increases the risk that solutions will not deliver required business outcomes.
• Overcome Acquisition Based Silos - Developers
• Overcome Acquisition Based Silos - Managers
• Open Source Trumps InnerSource - People find the InnerSource project but, after all things are considered, even if the InnerSource component meets their needs, they still go with the open source component.
• Overcoming Project Management Time Pressures - Project management believes timeline pressure and commitments on feature content does not allow for developers to spend the time needed to develop shareable code and provide support.
• Start as Experiment - An inner source initiative is considered but not started, because management is unsure about its outcome and therefore unwilling to commit to the investment.
• Include Product Owners - Key Performance Indicators (KPIs) for Product Owners are primarily product focused, and don't consider areas such as collaborative development. This results in a lower level of engagement with inner source projects.

• Don't Bother Looking
• Junkyard Styled Inner Sourcing
• Shared Code Repo Different from Build Repo - 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.
• Incentive Alignment
• Change the Developers Mindset
• Share Your Code to Get More Done - Likely Contributors Variant

• Donut 3: How to Defeat the Hierarchical Constraints
• Donut 5: Project Management Time Pressures
• Donut 6: Organizational Mindset Change
• Donut 8: Not Invented Here
• Donut: Bad Weather For Liftoff
• Get Contributions Despite Silo Thinking

Patterns are a way of describing a repeatable, proven solution to a problem with a context. They follow a simple form that helps people wanting to implement the solution to understand the constraints on the problem, the forces that must be balanced and the resulting context (the situation you are left with after the solution is applied). In inner sourcing, patterns can provide a way for the InnerSource Commons participants to concisely share information with each other, improving the practice of inner sourcing. Each of the patterns are divided into Title, Problem Statement, Context, Forces, and Solutions as their main sections.

• What are patterns? Youtube videos - Watch a set of 2-5 min youtube videos explaining Inner Source Patterns
• Pattern Discussion Webinar - We held a webinar 2017-03-16 to live-discuss a donut pattern (go to 24:30 for the discussion). This is an illustration of the review process we follow. Also see the June 1, 2017 O'Reilly Webinar on InnerSource Patterns.
• Pattern Template File - View a skeleton inner source pattern to get an idea on what goes into a new pattern!
• Introduction to InnerSource Patterns (2016 Fall Summit presentation) - Tim Yao and Padma Sudarsan (PDF). Detailed pattern background and examples -- Get a detailed understanding of why and how to interact with our patterns.

Patterns must be used in a thoughtful manner. They cannot be blindly applied. In most cases, you will need to adapt the given solution to your own situation; but the information given in the pattern, defining the context (immovable constraints) and forces (constraints that can be changed and balanced against each other), should help you do this. Note that you will also need to determine if there are additional constraints (company context and company forces) that apply to your particular company/organization that must be added to the pattern (as a kind of filter). These additional constraints may require additional solution steps to be applied.

The pattern form is useful for describing proven patterns but it can also be used for brainstorming solutions where patterns are not yet established, since the form gives a structured way for thinking about a problem. You could also create a donut pattern (filling in the problem, context, forces and resulting context fields but leaving the solution blank) as a way of asking the InnerSource Commons community for help (to find a proven solution or to brainstorm things to try).

See our CONTRIBUTING.md for details on getting involved

We encourage beginners seeking answers to jump in by creating ''donuts'' (problems without solutions). We encourage experts to pad their experience - these are hoped to become part of a book one day. Anyone can offer reviews and comments for in-progress patterns.

We work together via Github, Webex, Slack, etc. Do not hesitate to join the #innersourcecommons or #innersource-patterns slack channels and ask to be included in the patterns meetings (there is an email list).

The topics below cover information about how we define, operate, and upkeep this collection of patterns.

• Pattern Template - Start a new pattern with a copy of this
• Pattern States - Definitions of the various states and review steps a pattern can be in
• Trusted Collaborators - Who these people are, what elevated rights they get, and how you can become one
• Publishing - How we take completed, reviewed, proven patterns and publish them toward an online book
• Markdown Info - Markdown is the ascii text format our patterns are written in; this document briefly defines how we use it
• Contributing - How to interact with our group, create your own patterns, or take part in our review-process; Github / Web centric instructions
  • Alternate Command-line steps - If you want to contribute a pattern using git from the command-line, this is your document
  • Meetings - Become involved with the people and communications of the Inner Source Patterns group

• A pattern language for pattern writing, Meszaros and Doble

InnerSourcePatterns by InnerSourceCommons.org is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License.