Pattern Idea: InnerSource Program Office

In our Slack this conversation happened:

Q: Is there a place where I can find a charter for an InnerSource program office?
A: The “charter for InnerSource Program Office” depends on the situation your company is in and where it wants to go — there are as many designs as there are members in the InnerSource Commons. Do you have an effort with top-level management support or more a grassroots movement? Are you trying to improve transparency, cross collaboration, communication, reuse, time to market, reduced defects, or something else? Do you have a picture of the current barriers and what capabilities need to be developed for your next low hanging fruits?

We have some patterns that either mention an InnerSource Program Office (ISPO), or are written from the perspective of an ISPO. Of particular interest could be the Explicit InnerSource Principles pattern that has a section on "Why does the organisation want to adopt InnerSource?".

However we don't have a pattern describing what an ISPO is, how to establish one, and what problems can be addressed through it.

We recognize that there may be different reasons for establishing an ISPO, as well as different charters that an ISPO may follow. However we think that it is possible to describe the main building blocks for establishing an ISPO in the form of a pattern.

Things that could support the creation of such a pattern

• list the patterns that mention an ISPO already (or similar concepts) => allows us to understand whether we even mean the same thing when talking about an ISPO in the existing patterns
• review content from the TODO Group on how to create an OSPO. That might be similar to the creation of an ISPO.

首先審閱 Explicit InnerSource Principles 模式以及 issue 中連結的 TODO Group OSPO 指南。盤點提到 ISPO 或類似概念的現有模式，然後利用這項研究定義該模式的主要構建模組。當一個模式解釋 ISPO 是什麼、如何建立 ISPO，以及它可以解決哪些問題時，即視為完成。