[OSDU Data Flow] Project Consensus Model and Voting

Consensus model and Voting

Ideally Open Source projects operate on a daily basis with very little formality. However, the diversity of deployment environments and associated impact on technical architecture and sustainability will lead to inevitable conflict. When these arise, we will follow a decision process that is driven by trade-off analysis, resolved through voting and documented via decision records.

Trade-off analysis

When consensus is not met we will follow a trade-off analysis in which competing ideas are assessed against project goals on the principle that the health of the entire system and subsequent and sustainable adoption by customers is more valuable than any single technical decision.

Voting

• Simple majority (51%) for any decision that does not introduce a breaking change to a commitment or deployed production version of the system
• Super majority (75%) plus escalation to the PMC for any decision that does introduce a breaking change to a commitment or deployed production version of the system