Содействие

From Meta
This page is a translated version of the page Contributing and the translation is 6% complete.
Outdated translations are marked like this.


System-users-3.svg
Love Miraheze?
Volunteer!
Miraheze is made up of volunteers, ordinary people just like you!


Как вы знаете, Miraheze - это викифарма, управляемая сообществом и управляемая волонтерами. Вы тоже можете помочь! Если вы хотите помочь нам в выполнении различных ролей (технических / нетехнических), пожалуйста, см. Ниже и нашу страницу Miraheze Vacancies, чтобы узнать, как помочь.

Пользование нашими услугами

Один из самых простых способов, которыми любой пользователь может помочь Miraheze — запросить вики и использовать ее. Будьте активны, развивайте собственное подсообщество. Приводите в Miraheze знакомых. Кроме того, не стесняйтесь исследовать WikiDiscover и справочник вики, чтобы найти вики, которые могут быть вам интересны.

Help local communities!  

One of the easiest ways that anyone can help Miraheze is by requesting a wiki and using it. Be active, develop your own community, bring people to Miraheze!

Don't want to create a wiki? Look for a wiki that already exists on your topic! Miraheze hosts a variety of wikis, from computers to TV shows, you're sure to find a wiki that suits your needs! Check out WikiDiscover and the Gazetteer of wikis to find wikis you might be interested in.

Help on Meta (this wiki)!

 

Another easy way of helping out is by helping out on this wiki, Miraheze Meta. On Miraheze Meta, issues pertaining to the global community are discussed. You can help out by answering any question which you may know the answer to. Most questions on Miraheze Meta are asked on the noticeboards. There are currently 3 noticeboards where users can solicit help, each one focuses on a different topic and are labeled accordingly:

  • Community noticeboard - Any general question is asked on here such as questions about ManageWiki, CSS, templates, etc. This noticeboard also serves to help start community discussion about topics that concern the global community. If you know the answer to anything, don't be afraid to reply!
  • Meta Administrators' noticeboard - Any issue regarding this wiki (Meta) is discussed on here, such as requesting a ban on a user, marking pages as translatable, asking for local permissions which can be granted at administrator discretion, among other local things. This noticeboard is not for global actions.
  • Stewards' noticeboard - Any question or issue that needs Steward intervention (like requesting a lock for a vandalism-only accounts, requesting a CheckUser, etc.) is asked on here. Sometimes, what users ask isn't necessarily something that needs a Steward's reply, it can be as simple as asking for help to change a logo. Even though it is the Stewards' noticeboard, that doesn't mean you can't help anyone on there yourself; don't be afraid to reply, move their post if needed, and guide them!

If you ever see a question that was asked on the wrong noticeboard (like a global lock requested on the Meta Administrators' noticeboard instead of the Stewards' noticeboard), be bold and move it to the appropriate noticeboard. Even if your edit is reverted, at least you gain experience and learn how to sort issues!

Help on Discord and IRC  
Not all questions are asked on Meta, many prefer to ask on Discord or IRC. Don't be afraid to stop by and help out over there. Most IRC channels relay to Discord meaning that you can talk with people on IRC in real time while on Discord and vice-versa. For more info on connecting to Discord and IRC, check out their respective pages.
Help fight global vandalism!  

While fighting global vandalism may seem hard, especially because Miraheze hosts 5375 wikis, it actually isn't! Miraheze employs AbuseFilter which stops most vandalism before it can even occur. This, along with other suspicious activity, is reported on the #miraheze-cvt-feed connect IRC channel. You can monitor this feed for any possible vandalism or spam and report it on #miraheze-cvt connect. Note that both channels are relayed on Discord. A Steward or Global Sysop will review your report and action it accordingly. If an edit isn't stopped by AbuseFilter, you can also manually go into the wiki and revert it yourself. If you do, just make sure to include in the summary that you were reverting vandalism or else you may be erroneously labeled a vandal yourself!

Even if a vandalism-only account is stopped by AbuseFilter, you should still report it to the Stewards to prevent the account from trying to bypass the filter, succeeding and flooding a wiki. To report them, you can make a new section on the Stewards' noticeboard or you can report them on #miraheze-cvt connect.

Pictogram voting info.svg Note: Not all wikis are enrolled in the global anti-vandalism program, some have purposefully opted-out of Global Sysop intervention. Also note that private wikis are also not reported on the CVT feed. For more info on this, see Counter Vandalism Team.

Help out on Phabricator!  

Phabricator is Miraheze's task tracking system. While most tasks on there require a system administrator, some don't. A user might need help enabling an extension or might have not been able to find a setting in ManageWiki. In these cases, if you know the answer, you're more than welcome to reply to the task. In some cases, if you are certain that the issue has been resolved, you can close the task. If you're new on Phabricator, it is recommended that you wait and learn what types of tasks are closed when, to prevent you from accidentally closing a task that hasn't actually been resolved.

Even if a task involves something technical like importing a database dump, you can still help on the task by sorting the tags correctly for the task. For more information on tags, see Phabricator.

Help out technically!  

While the previous ways to contribute were some that don't require technical expertise, the following do. If you know how to help out technically, you're more than welcome to!

Help on GitHub

Miraheze hosts all of its configurations in a GitHub config repo (see this page for additional info). Whenever a change needs to be done, these configuration files are updated. When these configurations are updated in any of the repositories hosted on GitHub, the changes are automatically deployed to the servers hosting Miraheze. Historically, feature changes were done by sending a request on the Request features page or by adding a GitHub merge request. This is no longer the case, you can do most configuration changes on ManageWiki. That doesn't mean you can't help out on GitHub though, it's not rocket science!

Любой с аккаунтом на GitHub (доступен бесплатно) может предлагать изменения файлов.

=== Простое начало ===

Один из самых простых способов начать работу — это просмотреть запросы функций и затем отредактировать файл LocalSettings.php в нашем репозитории Miraheze/mw-config. Бо́льшая часть этого файла (за исключением небольшой части в конце) должна быть более простой для понимания. Он использует вложенные массивы для применения настроек ко всем вики по умолчанию или некоторым вики, как написано.

Most of this section (except for a little at the end) is easy to understand. It uses nested arrays to apply settings to all wikis by default, or some wikis as coded.

Базовая схема вложений выглядит следующим образом:

  • Определение переменных пространства имен (ближе к началу, после вложений)
  • wgConf (самый большой массив)
    • Название настройки (в форме 'wgVariable' или 'wmgVariable')
      • Затронутые вики (в форме 'dbname' или 'default', где dbname - это поддомен сайта с добавлением wiki в конце)
        • Значения настроек (что поставить. Могут быть числом, истиной/ложью или массивом, в зависимости от настройки.)
Pictogram voting info.svg Note:

Обратите внимание, что некоторые расширения, такие как Flow и VisualEditor, требуют дополнительной настройки.

=== Установка нового расширения или темы оформления ===

Кто угодно может предложить изменения в репозитории Miraheze/mediawiki. Чтобы установить новое расширение или тему оформления, которые еще не установлены (не включить их в вики), см. эту страницу.

== Настройка серверов ==

Miraheze работает 15 VPS на Debian , размещенных на $ramnode, и 1 VPS, размещенной на $backupsy (хранение резервных копий) - в основном на OpenVZ, в очень редких случаях на KVM. Наша конфигурация сервера управляется Puppet, и мы работаем с различными технологиями. Мы используем $mediawiki с $apache, $gdnsd, $mariadb, $nginx и $varnish для поддержки веб-стека. Если вы знакомы с одной или несколькими упомянутыми выше программами, мы будем рады узнать о вашем опыте! Дополнительная помощь всегда приветствуется, и даже самые незначительные улучшения (исправленные ошибки/оптимизация и т.д.) могут стать для нас большими улучшениями. Пожалуйста, свяжитесь с системными администраторами, если вы хотите внести свой вклад в эту область, или просто создайте задачу на Phabricator для этого.

Miraheze runs on Debian and uses a multitude of servers. Our server configuration is managed by Puppet, and we work with various kinds of technologies. We use MediaWiki with Apache, GDNSD, MariaDB, NGINX and Varnish to power the web stack. If you are familiar with one or more of the software mentioned above, we would love to hear about your experience! Extra help is always welcome, and even the smallest improvements (fixed bugs/performance, etc.) for you, can be a big improvement for us. Please get in touch with the System administrators if you would like to contribute in this area or simply make a Phabricator task for it.