Difference between revisions of "Contribute/ru"
(Created page with "Этот список содержит часть способов поддержать проект.") |
(Created page with "== Вклад в исходный код проекта ==") |
||
Line 4: | Line 4: | ||
Этот список содержит часть способов поддержать проект. | Этот список содержит часть способов поддержать проект. | ||
− | == | + | == Вклад в исходный код проекта == |
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: |
Revision as of 23:51, 29 December 2015
OpenVZ это продукт с открытым исходным кодом.И если он Вам нравится, то лучше что вы можете сделать - это помочь проекту. Есть много способов помочь проекту. И не важно являетесь ли Вы обычным пользователем, гиком или хардкорным разработчиком - всегда есть одна или больше важных вещей, которые Вы можете сделать для OpenVZ.
Этот список содержит часть способов поддержать проект.
Contents
Вклад в исходный код проекта
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.
- Send patches for kernel and userspace code.
- Implement ideas from wishlist.
- Contribute to CRIU development.
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. Information required to testing is in QA section.
- Correct spelling and grammar mistakes in the documentation.
- Take a look at QA wishlist
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.
- Put an appropriate banner, button or just some text on your site linking back to openvz.org.
- Write reviews about new OpenVZ features.
- Spreading the word
- 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 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 templates.
Contribute code of infrastructure (DevOps)
- Automate all the things
- Make packages with OpenVZ components
Contribute creativity
- Web design for OpenVZ services. See design tasks.
- OpenVZ T-shirt prints: new ideas
- Artwork: update OpenVZ logo (may be material design?)