貢獻
 齊來貢獻！ |
貢獻方法
您不想申請wiki？沒關係！您也可以幫助打造現有的wiki！找到您想協助編輯的wiki，電腦、電視節目、游戲……應有盡有！查看WikiDiscover 和wiki索引來尋找您剛興趣的wiki。
另一種簡單的貢獻方法就是在此wiki——Miraheze Meta上幫助。Miraheze Meta，探討和協助全球社區事宜。您可以透過解答他人疑問來提供幫助。多數人會在公告欄上提出相關問題。目前有3個公告欄，用戶可以在其中尋求幫助，每個公告欄用於探討、討論不同的主題：
- 社區公告欄 - 您可於此詢問任何有關管理此wiki的設定（ManageWiki），CSS，模板等的一般問題。此公告欄也會討論關於全域的事宜，歡迎您回答任何您所知的問題！
- Meta管理員公告欄 - 您可於此討論任何有關此wiki的事宜，諸如請求封禁其他用戶，將頁面標記為可翻譯，向管理員申請授予本地權限。此公告欄不適用於討論全域事宜。
- 監管員公告欄 - 您可於此請求監管員介入（比如申請全域封禁破壞者，申請用戶查核等）。
如果您看到其他用戶誤用公告欄（例如，用戶可能監管員公告欄提出無需監管員介入的問題，如請求更改徽標；又或在元管理員公告欄申請全域封禁）。請勇於移動他們的問題至合宜的公告欄，並引導他們。儘管最後可能是您自己搞錯了，但您也會得到一定的學習經驗！
While fighting global vandalism may seem hard, especially because Miraheze hosts 6711 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 labelled 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.
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 not reported on the CVT feed. For more info on this, see Counter Vandalism Team.
Phorge 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 to Phorge, 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 Phorge.
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!
Anyone with a GitHub account (available for free) can propose file changes.
- Guidelines & Tips
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.
The basic nesting layout is as follows:
- Define namespace variables (close to the start, after includes)
- wgConf (largest array)
- Setting name (in the form of 'wgVariable' or 'wmgVariable')
- Wiki's affected (in the form of 'dbname' or 'default' where dbname is the site's subdomain with "wiki" added to the end)
- Setting value (the values to set. It can be a number, true/false, or an array, depending on the setting.)
- Wiki's affected (in the form of 'dbname' or 'default' where dbname is the site's subdomain with "wiki" added to the end)
Note: Some extensions require additional setup to work. In that case, a system administrator will handle the change.
- Installing a new extension or skin
Anyone can propose changes to the Miraheze/mediawiki repo. To install a new extension or skin not already installed (not enable one on a wiki), please see Adding a new extension.
- Help out internally
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 Technical Team if you would like to contribute in this area or simply make a Phorge task for it.