Much of this developer documentation provides historical context but may not reflect the current state of the project.
If you see outdated content please navigate to the page footer and click "Report an issue on GitHub".
It is not user documentation and should not be treated as such.
User Documentation is available here.
If you see outdated content please navigate to the page footer and click "Report an issue on GitHub".
It is not user documentation and should not be treated as such.
User Documentation is available here.
Infrastructure
Here is the Infrastructure Team and what we work on for the oVirt project.
Mission Statement
The oVirt Infra Team is a volunteer effort to provide community infrastructure services by following the tenets of open source and accepted professional standards of system administrators.
Team
The list of the maintainers of the Infrastructure project is maintained as GitHub oVirt Team: @oVirt/Infrastructure
Read Becoming an Infrastructure team member for details on joining this project.
Decision process
- The Infra team generally follows the principle that if it wasn’t discussed on the mailing list it didn’t really happen.
- This means all important or broad-reaching decisions are discussed and decided on the mailing list.
- The team uses the same collaborative decision process that other oVirt teams use, with some lightweight elements added to move along minor votes
- +1 is a vote in favor of a proposition
- -1 is a vote against a proposition, must be accompanied with an explanation of the negative vote
- +/-0 is an abstention
- 3 or more +1 votes are required for anything substantial, important, or far-reaching
- 0 or more votes will pass a minor proposition - “If no one objects, it passes.”
Documentation
We are in the process of moving all our documentation to be inside our git repos, and published as HTML. You can find the published docs at: http://ovirt-infra-docs.readthedocs.org/en/latest/