Skip to main content
Project stewardship

Governance

The product is governed by the Linux Foundation Antitrust Policy, and the FINOS IP Policy, Code of Conduct, Collaborative Principles, and Meeting Procedures.

PoliciesPublicFINOS · LINUX FOUNDATION
Lead MaintainerFINOS liaison · tie-breakMaintainersReview · merge · stewardContributorsCode · docs · issues · design
Meritocratic and public

Roles

Fluxnova is a meritocratic, consensus-driven platform. Decisions are made in public — through Working Groups and public issues after open discussion and community input. No major changes to direction, features or fixes are made privately. We open proposals early and keep the community involved throughout the decision process. Maintainers document outcomes and broad consensus.

Who stewards the project

Roles in detail

Everyone

Contributors

Anyone who submits a contribution — code, issues, documentation, comments, tests, or design input.

  • Must be covered by a FINOS Contributor License Agreement (CLA)
  • Uncovered contributions are blocked by EasyCLA

See FINOS Software Project Governance for CLA details.

Trusted

Maintainers

Contributors granted write access based on sustained contributions and community trust.

  • Reviewing and merging pull requests
  • Managing GitHub issues and labels
  • Participating in community discussions
  • Ensuring adherence to project standards
Elected

Lead Maintainers

Primary liaison(s) with the FINOS team and FINOS Board, elected by majority vote of Maintainers.

  • Approving and submitting reports to FINOS
  • Representing the project at FINOS-wide forums
  • Facilitating consensus across Maintainers
  • Casting tie-breaking votes if needed
Stewardship

Maintainer lifecycle

Fluxnova encourages community-driven stewardship. These practices keep the Maintainer group active, representative, and aligned with project goals.

  1. AppointmentAny contributor with a sustained track record may be nominated or apply. Approval requires maintainer consensus (or a vote if consensus cannot be reached).
  2. Annual reviewMaintainers are reviewed annually (next refresh Q1 2026 unless otherwise agreed). New maintainers may still be added anytime with consensus or a vote.
  3. Lead re-electionLead Maintainer(s) are re-elected annually, or earlier if required. Any current Maintainer may nominate themselves or others.
  4. TransparencyAll discussions and decisions on appointments, removals, or Lead elections are recorded and minuted publicly.
  5. OffboardingMaintainers may step down anytime. After 6+ months of inactivity (no PR reviews, governance participation, or meetings), respectful offboarding may follow by consensus, aligned with FINOS policies.
How decisions happen

Contribution & decision making

Contributions must abide by the guidelines in Contribution Documentation.

Consensus model

  • Preferred: all relevant Maintainers agree
  • Acceptable: majority agrees, no strong objections
  • If consensus cannot be achieved, Maintainers vote per the voting rules below

Maintainer voting

  • 36 hours to vote: +1 (Agree), −1 (Disagree), +0 (Abstain)
  • Majority of votes cast determines the outcome
  • Ties broken by the Lead Maintainer
  • Votes are public via GitHub, mailing list, or minuted meetings

Always public · GitHub & minutes

ProposalOpen earlyConsensusPreferredVote+1 / −1

36-hour maintainer voting window when needed

Maintainers WGTechnical · 60 minPRs · architecture · CIGeneral WGProgramme · 30 minRoadmap · delivery
Collaboration forums

Working group structure

Fluxnova operates two standing Working Groups to streamline technical collaboration and strategic oversight. Additional groups may form for specific topics.

Maintainers Working Group

Technical forum · 60 minutes

  • Review and merge open pull requests
  • Discuss architecture and design proposals
  • Ensure compliance with FINOS governance and open-source best practices

General Working Group

Programme forum · 30 minutes

  • Oversee roadmap milestones and delivery targets
  • Review and approve major technical changes that require wider agreement
  • Ensure ongoing alignment with FINOS governance and open-source best practices
Participation

Community principles

Fluxnova follows consensus-based decision-making. Guiding principles for participation:

Openness

Participation is open to all who are materially affected by Fluxnova’s direction. There are no financial barriers or affiliation requirements to contribute.

Lack of dominance

No single individual, company, or interest group shall dominate decision making. Contributions are considered on their merit.

Balance

Efforts are made to involve diverse stakeholders across industry sectors to ensure well-rounded and equitable outcomes.

Consideration of views

All feedback, objections, and comments from contributors are thoroughly reviewed. Maintainers record responses and actions.

This document may be amended by consensus of the Maintainers — see Decision Making Process.