Difference between revisions of "Contribute"

From OpenVZ Virtuozzo Containers Wiki
Jump to: navigation, search
m
m
Line 22: Line 22:
  
 
* Help write good documentation.
 
* Help write good documentation.
 +
* Help [[Wiki maintenance|maintain]] the wiki.
 
* Send us corrections/additions to the existing manuals.
 
* Send us corrections/additions to the existing manuals.
 
* Write your own guide or [[:Category:HOWTO|HOWTO]], or help to expand [[:Category:Stubs|stub articles]].
 
* Write your own guide or [[:Category:HOWTO|HOWTO]], or help to expand [[:Category:Stubs|stub articles]].
Line 37: Line 38:
 
* Convince people to use Vituozzo containers when possible.
 
* Convince people to use Vituozzo containers when possible.
 
* Write about [[Use_cases|new ways]] of using OpenVZ.
 
* Write about [[Use_cases|new ways]] of using OpenVZ.
* Submit artwork (icons, backgrounds, logos).
+
* Submit [[artwork]] (icons, backgrounds, logos).
  
 
== Contribute appreciation ==
 
== Contribute appreciation ==

Revision as of 14:32, 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.

Contribute code

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

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.
  • 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.

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


See also