H.4.3 Contributions

recommended
Reading progress2 helpful
Article in preparation — showing conspect notes

Cross-team contribution removes handoffs while preserving responsibility boundaries.

  • Publish supported APIs, contribution expectations, proposal thresholds, compatibility guarantees, and escalation paths.
  • Let small compatible changes use ordinary review; escalate architectural, breaking, sensitive, or high-blast changes deliberately.
  • State whether the contributor, steward, or migration team updates consumers and completes cleanup.
  • Use collaboration, facilitation, or service-style interaction with an explicit duration and handoff.
  • Contribution permission does not grant approval authority or transfer long-term maintenance silently.