Difference between revisions of "Contribute"

From OpenVZ Virtuozzo Containers Wiki
Jump to: navigation, search
(added new section (creativity))
(rm translate tags)
 
(15 intermediate revisions by 3 users not shown)
Line 8: Line 8:
  
 
* Tell what you want to do to [[Contacts|community]] and suggest new [[Wishlist|features/ideas]].
 
* Tell what you want to do to [[Contacts|community]] and suggest new [[Wishlist|features/ideas]].
* Fix open [http://bugzilla.openvz.org/ bugs].
+
* Fix open [https://bugs.openvz.org/ bugs].
 
* [[How_to_submit_patches|Send patches]] for kernel and userspace code.
 
* [[How_to_submit_patches|Send patches]] for kernel and userspace code.
 
* Implement ideas from [[wishlist]].
 
* Implement ideas from [[wishlist]].
 +
* Contribute to [http://criu.org/TODO CRIU] development.
  
 
== Contribute quality ==
 
== Contribute quality ==
Line 16: Line 17:
 
* Submit [[Reporting_OpenVZ_problem|good]] [https://bugzilla.openvz.org/ bug reports].
 
* Submit [[Reporting_OpenVZ_problem|good]] [https://bugzilla.openvz.org/ bug reports].
 
* Help us to reproduce old bugs on latest OpenVZ versions.
 
* 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. Information required to testing is in [[QA|QA section]].
+
* 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.
 
* Correct spelling and grammar mistakes in the documentation.
 
* Take a look at [[Wishlist#Software_testing|QA wishlist]]
 
* Take a look at [[Wishlist#Software_testing|QA wishlist]]
Line 26: Line 27:
 
* 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]].
* '''Translate''' the documentation into another language.
+
* [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.
 
* '''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.
+
* 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).
 
* Expand the [[Category:Definitions|Glossary]] of technical terms (so non-geeks can understand).
  
Line 47: Line 48:
 
* Express your appreciation to developers (through e-mail, bug reports, and IRC).
 
* 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).
 
* [[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 ==
 
== Contribute support ==
Line 54: Line 54:
 
* Contribute to (or start) an online support group.
 
* Contribute to (or start) an online support group.
 
* Write '''HOWTOs''' and post them in the [[:Category:HOWTO|Tutorials and Howtos]] or your own blog.
 
* 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.
+
* [[Setting up a mirror|Setup]] a [http://mirrors.openvz.org/ public OpenVZ mirror].
* Contribute new [[OS template]].
+
* Contribute new [[How to create OS template|OS templates]].
  
 
== Contribute code of infrastructure (DevOps) ==
 
== Contribute code of infrastructure (DevOps) ==
  
 
* Automate [[Wishlist#DevOps|all the things]]
 
* Automate [[Wishlist#DevOps|all the things]]
 
+
* Make [[packages]] with OpenVZ components
  
 
== Contribute creativity ==
 
== Contribute creativity ==
  
* Web design for [[OpenVZ_infrastructure|OpenVZ services]]
+
* Web design for [[OpenVZ_infrastructure|OpenVZ services]]. See [[design tasks]].
* OpenVZ [http://store.openvz.org T-shirt] prints
+
* OpenVZ [http://store.openvz.org T-shirt] prints: [[T-Shirt ideas|new ideas]]
* OpenVZ [[artwork]]
+
* [[Artwork]]: update OpenVZ logo (may be material design?)
 
 
  
 
== See also ==
 
== See also ==

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]