Who decides.
Inflexa is a company-led open-source project. That has real consequences, and you should understand them before you build on it.
We won’t pretend to be vendor-neutral.
Inflexa, Inc. funds and leads development, and holds final decision authority. This is not a foundation. It is not governed by a neutral board. Pretending otherwise would be the kind of thing that erodes exactly the trust we are asking you for.
What protects you is not our good intentions. It is the licence. Apache 2.0 means that if we make a decision you cannot live with, you can fork the project and carry on without asking us.
Three of them.
Contributors
Anyone who opens a pull request. You do not need permission, and you do not need to be employed by us.
Maintainers
Review and merge. Earned by sustained, good contribution to an area of the codebase.
Core team
Employed by Inflexa, Inc. Sets direction and makes the final call when consensus does not arrive.
Most decisions run on lazy consensus: a proposal sits in the open, and if nobody objects with a reason, it lands. When a decision is genuinely contested and does not resolve, the core team decides.
Sign off your commits.
Inflexa uses the Developer Certificate of Origin. There is no CLA. We do not ask you to assign us your copyright. You keep it. The DCO is a one-line statement that you wrote the code and have the right to contribute it.
git commit -s -m 'fix: your change'CI checks for the sign-off, so an unsigned commit will fail before a human sees it.
Where extra care is expected
Changes to the sandbox, the provenance substrate, or an analytical method get more scrutiny than the rest of the codebase. These are the parts where a quiet mistake becomes a wrong scientific result that nobody catches, so they are reviewed as if that were the likely outcome.