Contributing/it

Come sai, Miraheze è una wikifarm gestita da volontari. Anche tu puoi aiutare! Se vuoi aiutarci assumendo diversi ruoli (tecnici/non tecnici) vedi sotto e la nostra pagina Miraheze Vacancies per i modi per aiutare.

If you want to help us with taking on different roles (technical/non-technical), you can also check out our Miraheze Vacancies‎ page for ways to help.

Usare i nostri servizi
Uno dei modi più semplici con cui ogni utente può aiutare Miraheze è richiedere un wiki e usarlo. Sii attivo, sviluppa la tua sotto-comunità. Porta le persone che conosci a Miraheze. Inoltre, sentiti libero di guardare WikiDiscover e Gazetteer of wikis per trovare wiki che potrebbero interessarti.

Don't want to create a wiki? Look for a wiki that already exists and which covers 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.

...helping out on Meta
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 question regarding wikis or Miraheze is asked on here, like help with ManageWiki, help with styling a wiki, help with a template, etc. This noticeboard also serves to help start community discussion about topics. 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 soliciting help in banning an vandalism-only account, marking pages as translatable, asking for local rights, among other local things. This noticeboard is not for global actions.
 * Stewards' noticeboard - Any question or issue that might need Steward intervention (like banning vandalism-only accounts, reporting an abusive user, starting a sockpuppet investigation, or a global rename) is asked on here. Sometimes, what users ask isn't necessarily something that needs a Stewards 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 and give them pointers! By doing so, you help our overworked Stewards focus better their attention to more serious issues instead of having to go through every single thread and reply to every single little request.

If you ever see a question that was asked on the wrong noticeboard (like a global lock asked in 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!

Traduzioni
Puoi tradurre pagine su Meta cliccando "Traduci" in alto oppure andando su tradurre estensioni.

You can also translate Miraheze extensions. For more info on this, see Translating Miraheze extensions.

...helping on Discord and IRC
Not all questions are asked on Meta, many prefer to ask on Discord and IRC. Don't be afraid to stop on by and answer any question someone might have. Most IRC channels relay to Discord meaning that you can talk with people on IRC in real time. For more info on connecting to Discord and IRC, check out their respective pages.

...helping fight global vandalism
While fighting global vandalism may seem hard, especially because Miraheze hosts wikis, it actually isn't! Miraheze employs AbuseFilter which stops most vandalism dead in its tracks. This, along with other suspicious activity, is reported on the IRC channel. You can monitor this feed for any possible vandalism or spam and report it on. Note that both channels are relayed on Discord. A Steward will review it and globally lock the user if needed. 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.

Not all wikis are enrolled in the global antivandalism program, some have purposefully opted-out. These are usually larger wikis that employ lots of administrators who keep an eye out for vandalism at all times. Private wikis are also not reported on the CVT feed. For more info on this, see Counter Vandalism Team.

Creatore di wiki
I creatori di wiki sono volontari che conoscono un po' meglio le due interfacce che permettono loro di creare wiki: Special:RequestWikiQueue and Special:CreateWiki.

Più creatori di wiki abbiamo, più velocemente possiamo gestire le richieste di nuove wiki, il che crea una migliore esperienza per l'utente finale dei nostri servizi.

Per diventare un creatore di wiki devi avere la fiducia della comunità, chiedi i diritti da wikicreator qui e gli Steward vi apriranno una discussione prima di decidere se approvare o declinare la richiesta.

Per maggiori informazioni sui creatori di wiki, vedi Meta:Creatori di wiki e Meta:Guida per creatori di wiki se ti piacerebbe diventare uno di essi.

...helping out on Phabricator
Phabricator is Miraheze's ticketing system. While the many tasks on there require a system administrator, some don't. A user might need help enabling an extension or might have not be 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's 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 wiki dump, you can still help on the task by sorting the tags correctly for the task. For more information on tags, see Phabricator.

...helping 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!

...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) is able to propose file changes.

Chiunque abbia un account GitHub (disponibile gratuitamente) può proporre cambiamenti ai file.

Iniziare con facilità
Uno dei modi può facili di iniziare è guardare le richieste di funzioni e poi modificare il file LocalSettings.php nella nostra repository Miraheze/mz-config. La maggior parte dei file (eccetto alcuni in fondo) dovrebbero essere alcune delle cose più facili da capire. Usa array nidificati per applicare impostazioni a tutte le wiki, di default, oppure solo ad alcune.

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.)

Una delle cose più facili sarà abilitare estensioni che sono già istallate (Vedi la sezione di wgConf chiamata estensioni, che segue il formato di cui sopra dove "Nome dell'impostazione" sarà qualcosa come wmgUse Estensione ' dove Estensione è il nome dell'estensione da abilitare.

Da notare che alcune estensioni come Flow e VisualEditor richiedono configurazioni addizionali.

Istallare una nuova estensione o skin
Chiunque può proporre cambiamenti al repository Miraheze/mediawiki. Per istallare una nuova estensione o skin non già istallata (non per abilitarne una su una wiki), vedi questa pagina.

Messa a punto dei server
Miraheze gira esclusivamente su 15 VPS Debian ospitati da RamNode e 1 VPS ospitato da Backupsy (per conservare i backup) - per lo più grazie a OpenVZ, o in rari casi KVM. La nostra configurazione di server è gestita da Puppet, e lavoriamo con vari tipi di tecnologia. Usiamo MediaWiki con Apache, GDNSD, MariaDB, nginx, e Varnish per supportare il nostro sito. Se hai familiarità con uno o più dei software menzionati qui sopra, ci piacerebbe molto che ci raccontassi della tua esperienza! Dell'aiuto supplementare è sempre il benvenuto, e anche i miglioramenti più piccoli (bug risolti, prestazioni migliorate ecc.) apportati da te possono essere un grande miglioramento per noi. Per favore contatta i System administrators se ti piacerebbe contribuire in quest'area o semplicemente crea un task Phabricator.

Traduzioni
Puoi tradurre le pagine su Meta cliccando "Traduci" in alto oppure o anche tradurre estensioni.