liveBook · Manning

Governance model

As explained in Decision Engineering

The structure that determines who has decision-making rights over a project and whose interests guide its direction.

A governance model determines who holds commit rights, sets a project's roadmap, and whose interests guide it. It helps explain why a project is developing as it is and what to reasonably expect next; maintainability signals describe its current condition. section 4.3.2

Two recurring open-source patterns illustrate different levels of maintainer concentration:

  • Single-maintainer projects depend on one person. The risk depends partly on how deeply the project is woven into your codebase: a replaceable leaf utility differs from a dependency spread across many components. section 4.3.2
  • Small-team community projects have a handful of contributors and no formal governance; multiple active maintainers provide a higher safety net. section 4.3.2

Dependency risk

Core-js illustrates single-maintainer concentration. Assessing its risk means considering how extensively the dependency is woven into your code, not treating every use as equally difficult to replace. section 4.3.2

How Decision Engineering covers it

How deep it goes
Defines decision rights and compares maintainer patterns, but does not develop a formal governance assessment procedure.
Examples
Uses core-js for single-maintainer risk and Preact and vanilla-extract for small-team projects.
What you can do after
Evaluate dependency risk by relating maintainer concentration to how deeply the dependency is woven into your codebase.
How it connects
Connects governance with project maintainability, commit rights, roadmaps, and bus factor.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Decision Engineering. The section links point to the parts of the book it draws on.