oVirt is a community-driven virtualization project and people just like you are making it happen.
The oVirt community is a group of multidisciplinary individuals who are contributing code, writing documentation, reporting bugs, contributing UX and design expertise, and engaging with the community.
Before getting started, we recommend that you:
- Sign up for the firstname.lastname@example.org mailing list and send us an email saying how you would like to contribute. Visit our mailing lists page for other oVirt mailing lists to sign up for.
- For fluent, real time communication, join us on IRC
- Please read our community etiquette guidelines. (Quick summary: Be nice!)
oVirt is a community project, and we welcome contributions from everyone! If you’d like to write code, report bugs, contribute designs, or enhance the documentation, we would love your help!
There are a few ways to engage with the oVirt Community:
- Archived Conferences Presentations
- Forums / Mailing lists
- oVirt Facebook group
- IRC –
Before getting started, please read our community etiquette guidelines.
Do you want to let other to know you’re using oVirt? You can add your deployment to the oVirt counter!
If you’d like to contribute code to oVirt, visit the Developer section of the site for guidelines. All of our projects use git and are hosted at https://github.com/oVirt.
We’re always eager to have new contributors to the oVirt Quality Assurance project, no matter your experience level. If you’d like to get involved with helping to make oVirt better, read the QA project page to find out how to join in with QA activities. There are tasks available for every level of expertise and available spare time.
oVirt’s user interface and documentation are available in multiple languages for users around the globe. Examples include Italian, Portuguese, Chinese, Japanese, Korean, and more. To contribute translations, please follow our How-To.
oVirt needs concise, user-friendly, up-to-date installation and usage documentation. To contribute, visit the documentation repository and the documentation issues tracker. You can also report any documentation issues you find by clicking “Report an issue with this page” at the bottom of the documentation.
Report Bugs and New Feature Requests (RFEs)
Reporting bugs is one of the most valuable ways you can contribute! Ideas for new features are also very welcome. Report bugs and RFEs using the following issue trackers:
- Bugzilla - how to report a bug
- VM Portal GitHub - bugs and RFEs in VM Portal
- oVirt Documentation GitHub - Documentation issues
- Security issues follow a special reporting procedure.
Monitor security reports for oVirt Node
oVirt Node contains hundreds of packages: some of them may be affected by vulnerabilities which may have critical impact. You can help keeping oVirt Node secure by monitoring security reports and open oVirt Node trackers using Bug 2074469 as template.
Once the tracker is open you can help monitoring progress of the security fix. Look at existing security reports in oVirt Node and check corresponding package on CentOS Stream 8 Koji. If a fix for the CVE is available, update Bugzilla accordingly. As an example you can see Bug 2074469 handling
Participate in the oVirt infrastructure
Our project infrastructure can always benefit from extra people, hardware and network bandwidth. First of all, consider hosting a public mirror of oVirt repositories. You can also become an infra team member or donate GitHub runners to the project to improve our capacity and redundancy.
Supporters, Sponsors, and Providers
oVirt has a broad community of supporters, sponsors, and providers.
Follow us on:
Community projects related to oVirt
oVirt community shares scripts, tools, add-ons and plugins that didn’t reach enough interest or stability to get included into the oVirt project. You can find some of them listed here: