Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • H Home
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 15
    • Issues 15
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • Open Subsurface Data Universe SoftwareOpen Subsurface Data Universe Software
  • Platform
  • Data Flow
  • Data IngestionData Ingestion
  • Home
  • Issues
  • #25
Closed
Open
Issue created Jun 24, 2020 by Stephen Whitley (Invited Expert)@stephenwhitley

[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
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking