WIP: I am drafting this issue to describe the work required to level up a given pattern from Initial (Level 1) to Structured (Level 2). I am using the "Extensions to Manage Contributions at Scale" pattern as an example for this. I am hoping that later we can extract generalizable points into a GitHub issue template, that we can use whenever we want to do such "leveling up" for other patterns.

Meta

• Pattern: Standard Release Process and Published Artifacts
• Previous PR: Add new pattern for Release Process/Published Artifacts #332

Goal

Improve the given pattern to get it published in our InnerSource patterns online book at patterns.innersourcecommons.org.

Once published in the book, the pattern can be discovered more easily by people looking to improve their InnerSource practices. The upside for pattern authors and their orgs is an increased brand recognition, and positioning themselves as an InnerSource thought leader.

Getting Started

• We recommend that you review the Structured (L2) Requirements to understand the quality expectations we have set for the patterns in our book.
• Double check if there were any open discussion points in previous PRs about this pattern. You might built on these discussion points to improve the pattern further.

Possible Improvements

Here some examples of possible activities that might improve this pattern:

• The Context section doesn't contain the type of content that the pattern template asks for, yet. The two sections Context and Forces are often the hardest to write for new pattern authors, so we would be more than happy to help you to improve this section.
• Since publishing this pattern as Initial, did you make any new experiences while applying this pattern?
• Are there any other authors from within your org that you would like to get involved?
• The current title isn't super long. Just a bit maybe :) Once we have published the pattern in the book it becomes harder to change the title (and filename) without breaking URLs. Therefore we recommend to take another look at title and file name. For further tips see Naming Patterns.
• Are there any other L2/Structured patterns that you could link to from within this pattern?
• Are there any resources that you could link to that would help to either validate your pattern, or make it easier for the readers to understand it? Please confirm that these are resources that you trust.
• Determine to which phase of the InnerSource Program Mind Map the pattern should be added to (add it to at least one phase). This makes it easier for readers to discover your pattern as well.
• (optional) Do you know any other organizations using this pattern? Getting them to contribute their knowledge to the pattern and adding them as a Known Instance significantly hardens the pattern. Activities around this can also happen in a new issue/PR.

The above are just some suggestions.

You are the expert on your pattern, so please make your own judgement calls about how your pattern can be improved.