New content type - Scenario

In two recent conversations in PRs, we were unsure which content should go into which of our existing patterns. We ended up creating comparisons between the related patterns, partly supported by AI. These proved to be super helpful to figure out what the core focus of each of the existing patterns is, and how new patterns can add new insights to "fill the gaps" between the existing patterns.

Besides being useful for pattern maintainers in the context of a PR, I wonder if such overviews/comparisons could also be useful for regular readers of our patterns, to figure out how the patterns are related to each other.

Such a write-up does not feel like a pattern but rather like a new content type of our InnerSource patterns book. If I had to give such write-ups a name I might call it "scenario", "use case", or even just "article".

Example Scenarios

We could publish a scenario called "Enable project reuse". In that scenario we would incorporate this comparison table, and point to patterns immediately related to the scenario.

Recent conversations with pattern comparisons

• comparison of patterns related to the Governance Levels pattern - see comment / #765
• comparison of patterns related to the Discover your InnerSource - see comment / #780

Related

Two other things that this idea reminds me of:

• @rrrutledge had pitched the idea of an InnerSource handbook some time ago. The handbook also wanted to use a format that was less strict than our pattern format, while still reusing or referencing a lot of the content that our patterns provide.
• Our mindmap is already grouping the patterns into smaller groups. For each of these groups one might publish a scenario article. e.g. the "Discovery Challenges" group already contains some of the patterns that might be used in the "Enable project reuse" example above.

Out of scope (for now)

The new content type that we are exploring here could be integrated into one or multiple of our existing ISC assets. e.g. this could fit into the InnerSource Patterns book but also in the Learning Path, or even the Managing InnerSource Projects book.

I think that it would be best to first discuss which content would be helpful for the readers, and how hard it would be to generate such content (we have very few contributors, so I don't want to create an idea that cannot be implemented anyways because it requires too much effort).

Once that is clear, we could discuss again where that content should be published. It could even be integrated into multiple ISC assets.

Start by reviewing the pattern comparisons linked from PRs #765 and #780, then inspect the pattern-categorization/innersource-program-mind-map.png reference. The work is not yet scoped to a file or implementation path; done would require agreement on the scenario content type, its useful scope, and where it should be published.