Difference between revisions of "Contribute"

From OpenVZ Virtuozzo Containers Wiki
Jump to: navigation, search
(Add stub articles)
(rm translate tags)
 
(37 intermediate revisions by 3 users not shown)
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 several possibilities.
+
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.
  
== Developer ==
+
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
+
* Tell what you want to do to [[Contacts|community]] and suggest new [[Wishlist|features/ideas]].
* ask what needs to be done
+
* Fix open [https://bugs.openvz.org/ bugs].
* check [http://bugzilla.openvz.org/ Bugzilla] for opened bugs
+
* [[How_to_submit_patches|Send patches]] for kernel and userspace code.
 +
* Implement ideas from [[wishlist]].
 +
* Contribute to [http://criu.org/TODO CRIU] development.
 +
 
 +
== 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 [[:Category:Sub-projects | OpenVZ/Virtuozzo components]] and give us [[Contacts|feedback]] about changes. Information required to testing is in [[QA|QA section]].
 +
* Correct spelling and grammar mistakes in the documentation.
 +
* Take a look at [[Wishlist#Software_testing|QA wishlist]]
 +
 
 +
== Contribute documentation ==
 +
 
 +
* Help write good documentation.
 +
* Help [[Wiki maintenance|maintain]] the wiki.
 +
* Send us corrections/additions to the existing manuals.
 +
* Write your own guide or [[:Category:HOWTO|HOWTO]], or help to expand [[:Category:Stubs|stub articles]].
 +
* [https://www.mediawiki.org/wiki/Help:Extension:Translate/Page_translation_example Translate] the documentation into another language.
 +
* '''Proofread''' existing documentation, follow the examples, and make corrections.
 +
* Create [[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 ==
 +
 
 +
{{Out|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]].
 +
* [[Spreading the word]]
 +
* 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).
  
== Non-programmer ==
+
== Contribute support ==
  
If you are not a programmer, there are still many other ways to help the project.
+
* 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 [http://mirrors.openvz.org/ public OpenVZ mirror].
 +
* Contribute new [[How to create OS template|OS templates]].
  
; Documentation: Send us corrections/additions to the existing manuals, write your own guide or [[:Category:HOWTO|HOWTO]], or help to expand [https://openvz.org/w/index.php?search=%7B%7Bstub%7D%7D&title=Special%3ASearch&go=Go stub articles]. The best place to start is this wiki.
+
== Contribute code of infrastructure (DevOps) ==
  
; Testing: Participate in testing of new versions of [[Download/kernel|kernel]], [[Download/ploop|ploop]], [[Download/vzctl|vzctl]] and give us feedback about changes. Join the [[QA]] team!
+
* Automate [[Wishlist#DevOps|all the things]]
 +
* Make [[packages]] with OpenVZ components
  
; Links: If you are using OpenVZ, please put an appropriate [[Artwork|banner, button]] or just some text on your site linking back to [https://openvz.org/ openvz.org].
+
== Contribute creativity ==
  
; Communication: Participate in the [[mailing lists]], [http://forum.openvz.org/ forums], and this wiki; if you know some the answer to a question asked, feel free to share it with others.
+
* Web design for [[OpenVZ_infrastructure|OpenVZ services]]. See [[design tasks]].
 +
* OpenVZ [http://store.openvz.org T-shirt] prints: [[T-Shirt ideas|new ideas]]
 +
* [[Artwork]]: update OpenVZ logo (may be material design?)
  
 
== See also ==
 
== See also ==
  
 
* [[Development portal]]
 
* [[Development portal]]
 +
* [[Membership]]
  
 
[[Category: Infrastructure]]
 
[[Category: Infrastructure]]
 
[[Category: Development]]
 
[[Category: Development]]
 +
[[Category: Contributions]]

Latest revision as of 02:43, 27 November 2018

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[edit]

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

Contribute quality[edit]

Contribute documentation[edit]

  • 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[edit]

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

Contribute appreciation[edit]

  • 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[edit]

Contribute code of infrastructure (DevOps)[edit]

Contribute creativity[edit]

See also[edit]