Contribute

<languages />

<translate> OpenVZ is open source software, and if you like it, the best thing you can do is help the project. There are many ways that you can contribute. Whether you are a normal user, a geek, or a hardcore developer, the one and most important thing you can do is to actually use OpenVZ.

The list below explains some of the ways that you can contribute.

Contribute code

If you want to become an OpenVZ developer, please subscribe to the devel mailing list and do one of the following:

• Tell what you want to do to community and suggest new features/ideas.
• Fix open bugs.
• Send patches for kernel and userspace code.
• Implement ideas from wishlist.
• Contribute to CRIU development.

Contribute quality

• Submit good bug reports.
• Help us to reproduce old bugs on latest OpenVZ versions.
• Participate in testing of new versions of kernel, ploop, vzctl and give us feedback about changes. Information required to testing is in QA section.
• Correct spelling and grammar mistakes in the documentation.
• Take a look at QA wishlist

Contribute documentation

• Help write good documentation.
• Help maintain the wiki.
• Send us corrections/additions to the existing manuals.
• Write your own guide or HOWTO, or help to expand stub articles.
• Translate the documentation into another language.
• Proofread existing documentation, follow the examples, and make corrections.
• Create screencasts, demo video, screenshots, and graphics for the documentation.
• Expand the of technical terms (so non-geeks can understand).

Contribute publicity

Note: As OpenVZ gets more popular, there will be more people wanting to contribute.

• Put an appropriate banner, button or just some text on your site linking back to openvz.org.
• Write reviews about new OpenVZ features.
• Spreading the word
• Convince people to use Vituozzo containers when possible.
• Write about new ways of using OpenVZ.
• Submit artwork (icons, backgrounds, logos).

Contribute appreciation

• Be polite when reporting bugs or asking for new features; after all, the developers have no obligation to do it.
• Express your appreciation to developers (through e-mail, bug reports, and IRC).
• Give the project or a developer a donation/gift (many of us have wish lists for this).

Contribute support

• Participate in the mailing lists, IRC channel, forums, if you know some the answer to a question asked, feel free to share it with others.
• Contribute to (or start) an online support group.
• Write HOWTOs and post them in the Tutorials and Howtos or your own blog.
• Setup a public OpenVZ mirror.
• Contribute new OS templates.

Contribute code of infrastructure (DevOps)

• Automate all the things
• Make packages with OpenVZ components

Contribute creativity

• Web design for OpenVZ services. See design tasks.
• OpenVZ T-shirt prints: new ideas
• Artwork: update OpenVZ logo (may be material design?)

See also

• Development portal
• Membership

</translate>