Difference between revisions of "Contribute"
(dot) |
(libct todo) |
||
| Line 10: | Line 10: | ||
* How to submit [[kernel patches]] | * How to submit [[kernel patches]] | ||
* create new [[OS template]] | * create new [[OS template]] | ||
| + | * LibCT [[LibCT|TODO]] | ||
== Non-programmer == | == Non-programmer == | ||
Revision as of 15:11, 30 April 2015
OpenVZ is open source, and if you like it, the best thing you can do is help the project. There are several possibilities.
Developer
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
- ask what needs to be done
- check Bugzilla for opened bugs
- How to submit kernel patches
- create new OS template
- LibCT TODO
Non-programmer
If you are not a programmer, there are still many other ways to help the project.
- Documentation
- Send us corrections/additions to the existing manuals, write your own guide or HOWTO, or help to expand stub articles. The best place to start is this wiki.
- Testing
- Participate in testing of new versions of kernel, ploop, vzctl and give us feedback about changes. Join the QA team!
- Links
- If you are using OpenVZ, please put an appropriate banner, button or just some text on your site linking back to openvz.org.
- Communication
- Participate in the mailing lists, forums, and this wiki; if you know some the answer to a question asked, feel free to share it with others.
- Donation
- You can donate to OpenVZ.
- Download mirror
- You can setup a public OpenVZ mirror.
