InnerSourcePatterns
InnerSourcePatterns copied to clipboard
Proven approaches that can guide you through applying open source best practices within your organization
* Inter-team collaboration can work by exposing code, documentation, roadmaps, backlogs, and sprint plans. The data is made openly available to drive the discussions between the teams. * Keep your...
I'm working with @MaineC on a paper about open source ideas, and need a citable resource for the work. So, I'm going to make a contribution in [/patterns/1-initial](https://github.com/InnerSourceCommons/InnerSourcePatterns/tree/master/patterns/1-initial) about what...
Likely a lot can be taken from https://tech.europace.de/voting-in-new-trusted-committers/ as well as from http://community.apache.org/newcommitter.html This information needs to be translated into pattern format though.
To start using the [new pattern maturity levels](https://github.com/InnerSourceCommons/InnerSourcePatterns/blob/master/meta/contributor-handbook.md#maturity-levels) outlined as part of the new contribution process, we want to move all existing patterns to a folder structure, indicating which maturity...
It would be nice to recognize all contributors to our InnerSource Patterns in a public way. A couple of ideas why that might be useful: - people that have committed...
Regarding code quality improvement, the rework rate captures several software engineering elements. It helps to observe the practical effects of increased code quality, allowing teams to spend most of their...
Our fantastic Japanese InnerSource community has translated all current Level 2+ patterns to Japanese. 🇯🇵 🥳 Now what if the original English patterns are improved further? Common changes are: *...
Summarizing from a slack conversation: > We have a pattern for an [innersource portal](https://github.com/InnerSourceCommons/InnerSourcePatterns/blob/main/patterns/2-structured/innersource-portal.md), but no pattern for a **developer portal** to layer on top of it to act as...