The goal of the InnerSource patterns working group is to collect, document, and publish InnerSource best practices. To make the best practices easy to comprehend, evaluate, and apply, we codify them in a specific structure - the patterns format. More infos on the working group can be found in our README.md file.
For this working group to thrive, we welcome your contribution - be it small or huge.
Please consider contributing to the InnerSource Patterns. Here some suggestions on how you can contribute.
-
Share your thoughts & spark discussion: A fresh perspective, an interesting thought, or an early novel idea can spark discussions and yield unforeseeable results. We invite you to share your thoughts on InnerSource-related topics at any time by creating an issue or via Slack.
-
Read & improve existing patterns: If you want to get started, we encourage you to read through the existing patterns and materials in this repository. Found a misleading phrase or phony grammar? A mistake in the content? Let us know by creating an issue or directly propose your fix as a pull request.
-
Confirm that you are using a pattern: When multiple organisations confirm that they are using a pattern, that increases the relevance of the pattern as it lets other adopters known that this pattern is proven. If you are using one of our patterns, you can list your org as Known Instance on the given pattern, together with a description of the experiences that you made applying it. Here some examples of great Known Instances descriptions.
-
Translate existing patterns: When implementing InnerSource practices in your region, there can be language barriers for people as most of the InnerSource content is available in English. Therefore we see great value in getting people in your region/organization to understand InnerSource in their own language. To help us translate patterns to other languages please refer to these translation instructions.
-
Review open pull requests: Even without knowing all the specifics of the patterns working group, your feedback on existing pull requests (especially those proposing changes to pattern contents) will be valuable to its authors: As somebody who wants to learn more about InnerSource, you can give input from the perspective of a future reader. As somebody with own InnerSource experiences, you can share your experience with the authors.
-
Contribute a new pattern: A key contribution you can make is to document an InnerSource best practice you experienced or know about. We defined different maturity levels for the contents in this repository: First time contributors should aim for maturity levels
1: initial(for unstructured experience reports or what we call donuts - patterns with missing pieces) and2: structured(for best practices adhering to the patterns format and following basic writing style conventions). Our Contributor Handbook discusses all this in more detail. You don't feel ready yet to contribute a new pattern? Please start a discussion by creating an issue. -
Be a patterns advocate: The patterns will become better and cover more topics the more people contribute their perspective and experience. A colleague told you about a novel InnerSource best practice? Please invite her/him to contribute to this repository!
We are happy to support you in contributing to the InnerSource patterns or to just chat with you.
You can best reach out to us via Slack:
Join the InnerSource Commons Slack instance and enter the #innersource-patterns channel there.
The contents of this repository are licensed under CC-BY-SA-4.0. By contributing to this repository, you grant us (and everyone else for that matter) the right to use your contribution in accordance with that license.
If you list yourself as the author of a pattern, we assume we have your permission to mention you when referring to the respective pattern.
We do not yet have a fully formalized code of conduct yet. We expect all contributors to treat each other respectfully and help us to keep this community free of harassment and discrimination.