-
Notifications
You must be signed in to change notification settings - Fork 26
Create a lightweight governance model
InnerSource governance is about decision-making.
- What kind of decisions must be made?
- Why is the decision important?
- When does each decision happen?
- Who ⏤or which role ⏤makes decisions?
- Where in the product development and delivery lifecycle does a decision occur?
- How is each decision made and recorded?
- To what extent or degree does a decision affect the project/product?
A governance model defines decisions, as well as who or what role, when, where, how, and why those decisions are made during your InnerSource project's development and delivery lifecycle.
An InnerSource project can flourish when:
- Consumers use the product.
- Contributors (who are almost always consumers) work on the product.
- Maintainers (who are experienced contributors) govern product development and delivery.
It is important to encourage consumers to become contributors, who in turn become maintainers. This flow is called the contribution conversion funnel.
An effective governance supports product development and delivery with a decision-making framework that encourages contributor and maintainer conversions.
- Map your product development and delivery workflow into stages.
- Identify what decisions people make at each stage.
- Etc.
This work is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License.
CLI snippets for
git
.
Openly declare the health of your product, project, community, and source code with these essential badges. (GitHub SaaS only.)
- Badges by category: even more badges, arranged for your pleasure.
- Repo status badges 🌟 : a recommended suite of badges for your README, Project Dashboard, PULL_REQUEST_TEMPLATE (or merge_request_template), CONTRIBUTING guidelines, as well as the status checks behind them.
Icons, images, gists, code snippets, etc.
Stellar languages, frameworks, platform, techniques, and tools.