Difference between revisions of "Contribute"
(libct todo) |
(Improve list of possible contributions) |
||
| Line 1: | Line 1: | ||
| − | OpenVZ is open source, and if you like it, the best thing you can do is help the project. There are | + | 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 [http://openvz.org/mailman/listinfo/devel devel mailing list] and do one of the following: | If you want to become an OpenVZ developer, please subscribe to the [http://openvz.org/mailman/listinfo/devel devel mailing list] and do one of the following: | ||
| − | * | + | * Tell what you want to do to [[Contacts|community]] and suggest new [[Wishlist|features/ideas]]. |
| − | * | + | * Fix open [http://bugzilla.openvz.org/ bugs]. |
| − | + | * How to submit [[kernel patches]]. | |
| − | * How to submit [[kernel patches]] | + | * Implement ideas from [[wishlist]]. |
| − | * | + | |
| − | * | + | == Contribute quality == |
| + | |||
| + | * Submit [[Reporting_OpenVZ_problem|good]] [https://bugzilla.openvz.org/ bug reports]. | ||
| + | * Help us to reproduce old bugs on latest OpenVZ versions. | ||
| + | * Participate in testing of new versions of [[Download/kernel|kernel]], [[Download/ploop|ploop]], [[Download/vzctl|vzctl]] and give us [[Contacts|feedback]] about changes. | ||
| + | * Correct spelling and grammar mistakes in the documentation. | ||
| + | |||
| + | == Contribute documentation == | ||
| + | |||
| + | * Help write good documentation. | ||
| + | * Send us corrections/additions to the existing manuals. | ||
| + | * Write your own guide or [[:Category:HOWTO|HOWTO]], or help to expand [[:Category:Stubs|stub articles]]. | ||
| + | * '''Translate''' the documentation into another language. | ||
| + | * '''Proofread''' existing documentation, follow the examples, and make corrections. | ||
| + | * Create [http://criu.org/Asciinema screencasts], [https://www.youtube.com/playlist?list=PL86FC0XuGZPIhm6Uva2e3XcehdHaOVMCg demo video]], screenshots, and graphics for the documentation. | ||
| + | * Expand the [[Category:Definitions|Glossary]] 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 [[Artwork|banner, button]] or just some text on your site linking back to [https://openvz.org/ openvz.org]. | |
| + | * Write '''reviews''' about [[QA_TODO_list|new OpenVZ features]]. | ||
| + | * Convince people to use Vituozzo containers when possible. | ||
| + | * Write about [[Use_cases|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). | ||
| + | * [[Donate|Give the project or a developer a donation/gift]] (many of us have wish lists for this). | ||
| + | * Contribute to [http://criu.org/ CRIU] development. | ||
| − | + | == Contribute support == | |
| − | + | * Participate in the [[mailing lists]], [[IRC|IRC channel]], [http://forum.openvz.org/ 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 [[:Category:HOWTO|Tutorials and Howtos]] or your own blog. | ||
| + | * [[Setting up a mirror|Setup]] a public OpenVZ mirror. | ||
| + | * Contribute new [[OS template]]. | ||
| − | |||
== See also == | == See also == | ||
Revision as of 14:18, 28 May 2015
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.
Contents
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.
- How to submit kernel patches.
- Implement ideas from wishlist.
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.
- Correct spelling and grammar mistakes in the documentation.
Contribute documentation
- Help write good documentation.
- 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.
- 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 to CRIU development.
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 template.
