Contributing/pt-br

Miraheze is made up of volunteers, ordinary people just like you!

Como você sabe, Miraheze é uma wikifarm administrada pela comunidade, operada por voluntários. Você também pode ajudar! Se você quiser nos ajudar a assumir diferentes papéis (técnicos/não técnicos), veja abaixo e nossa página Miraheze Vacancies para formas de ajudar.

Usando nossos serviços
Uma das maneiras mais fáceis que qualquer usuário pode ajudar Miraheze é solicitando um wiki e utilizando-o. Seja ativo, desenvolva sua própria sub-comunidade. Traga pessoas que você conhece para Miraheze. Além disso, sinta-se à vontade para olhar WikiDiscover e Gazetteer de wikis para encontrar wikis em que você possa estar interessado.

{{new collapse
 * headline =

... contribuindo no Meta
Outro caminho fácil de ajudar é contribuir neste wiki, Miraheze Meta. No Miraheze Meta, são discutidas questões pertencentes à comunidade global. Você pode ajudar respondendo a qualquer pergunta para a qual saiba a resposta. A maioria das perguntas no Miraheze Meta são feitas nos quadros de avisos. Existem atualmente 3 quadros de avisos onde os usuários podem solicitar ajuda, cada um enfocando um tópico diferente e são identificados de acordo: 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:
 * content =


 * 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!

Se você alguma vez vir uma pergunta feita no quadro de avisos errado (como um bloqueio global solicitado no quadro de avisos dos Meta Administradores em vez do quadro de avisos dos administradores), seja bold e mova-o para o quadro de avisos apropriado. Mesmo que sua edição seja revertida, pelo menos você ganha experiência e aprende como classificar os problemas! }}

{{new collapse Enquanto as formas anteriores de contribuir eram algumas que não requerem conhecimento técnico, as seguintes requerem. Se você sabe como ajudar tecnicamente, você é mais que bem-vindo! 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!
 * headline = === ...ajudando tecnicamente ===
 * content =

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!
 * Help on GitHub

Qualquer pessoa com uma conta no GitHub (disponível gratuitamente) pode propor alterações no arquivo.

Diretrizes e dicas
A maior parte desta seção (exceto um pouco no final) é fácil de entender. Ele usa matrizes aninhadas para aplicar configurações a todos os wikis por padrão, ou alguns wikis conforme codificados.

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. Can be a number, true/false, or an array, depending on the setting.)

Some of the easier things to do is enabling extensions that are already installed (See the section of wgConf called extensions, which follows the format above where "Setting name" will be something like 'wmgUse Extension ' where Extension is the name of the extension to enable.

Some extensions require additional setup to work. In that case, a system administrator will handle the change.

Instalando uma nova extensão ou 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.

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. }}
 * Help out internally