This page is a translated version of the page Steward handbook and the translation is 52% complete.
Raccourci :
SH
Cette page donne des informations sur les outils des steward , et fournit des recommandations sur leur utilisation. Voir aussi les politiques concernant les vérificateurs d'adresse , les masqueurs de modifications , et les stewards . Pour les discussions à propos de l'activité des stewards, voir le Bulletin des stewards.
Stewards
Pour les stewards
Tableaux d’affichage

Groupes d'utilisateurs et adjustement des droits

Wikis uniques

 
Capture d'écran de Special:UserRights.

Les stewards peuvent utiliser Special:UserRights sur Meta pour configurer les droits d'accès des utilisateurs sur n'importe quel projet Wikimedia , en cochant et en décochant des groupes spécifiques. Chaque groupe est associé à un ensemble de droits techniques dans la configuration de MediaWiki, présentés sur la page Special:ListGroupRights de chaque wiki.

  1. Saisir le nom de l'utilisateur.
    • Le format doit être “nom_d'utilisateur@préfixe_de_base_de_données” (pour les utilisateurs sur d'autres wikis) ou “nom_d'utilisateur” (pour les utilisateurs de Meta-Wiki).
    • La première lettre du nom doit être en majuscule (sauf si le wiki autorise l'utilisation de minuscules pour la première lettre des noms).
    • Le préfixe de base de données est constitué du code de la langue du wiki pour ceux disposant d'un sous-domaine (en remplaçant les traits-d'union par des blancs soulignés), suivi du préfixe du projet tel qu'indiqué ci-dessous.
  2. Cliquez sur “Modifier les groupes de l’utilisateur”. Une nouvelle boîte apparaît, vous présentant les groupes auxquels l'utilisateur appartient déjà, et où d'autres groupes sont disponibles.
  3. Sélectionnez les groupes.
    • Pour ajouter l'utilisateur à un nouveau groupe, cochez ce groupe.
    • Pour retirer l'utilisateur d'un groupe, décochez ce groupe.
    • Si l'appartenance à un groupe doit être définie pour une durée déterminée, sélectionnez la durée appropriée dans le menu déroulant.
  4. Cliquez sur “Enregistrer les groupes de l’utilisateur”.

Préfixes des bases de données

Les préfixes des principaux projets sont indiqués ci-dessous. Pour les autres projets, voir la liste complète. Notez que les traits-d'union (-) devraient être remplacés par des blancs soulignés (_), ainsi par exemple, cbk_zamwiki est le nom de la base de données de cbk-zam.wikipedia.org.

projet préfixe
Wikis multilingues
Wikimedia Commons commonswiki
Gouvernance de la Fondation Wikimedia foundationwiki
Wikifonctions wikifunctionswiki
Incubateur de Wikimedia incubatorwiki
MediaWiki mediawikiwiki
Wikisource multilingue sourceswiki
Wikipédia de test testwiki
Wikipédia de test 2 test2wiki
Test de Wikidata testwikidatawiki
Wikidata wikidatawiki
Wikispecies specieswiki
Wikis avec sous-domaines
Wikilivres codewikibooks
Wikinews codewikinews
Wikipédia codewiki
Wikiquote codewikiquote
Wikisource codewikisource
Wikiversité codewikiversity
Wikivoyage codewikivoyage
Wiktionnaire codewiktionary

Exemples :

Wikipédia en anglais Billy@enwiki
Wikiversité en français Billy@frwikiversity
Wikipédia en chinois classique Billy@zh_classicalwiki
Wikisource multilingue Billy@sourceswiki

Permissions

Les groupes suivants peuvent être manipulés (parmi d'autres sur certains wikis) :

Problèmes d'encodage

Many browsers have difficulty manipulating user names in non-Latin characters. There are two ways to get around this problem:

  • Enter the URL-encoded name through the URL.
    1. First, get the URL-encoded name:
      • Copy it from the address bar of your browser while viewing their user page;
      • or, type "{{urlencode:{{PAGENAME}}}}" on the user's page, preview, and copy the text.
    2. Go to Special:Userrights, and in the address bar add "?user=" followed by the URL-encoded name. For example, http://meta.wikimedia.org/wiki/Special:Userrights?user=Foo+Bar.
  • Enter the user id (for example, "#55@frwiki" for user #55 on the French Wikipedia). There are a few ways to determine the user ID:
    • Ask a system administrator in #wikimedia-techconnecter.
    • Use the API with a query like this.
    • If the user has edited on that wiki, you can find the ID by exporting that revision (if it is the latest) or exporting the whole history and locating that revision. Once located, look for the number inside "<id></id>" under "<contributor>" (make sure you're not getting the revision ID under "<revision>").

Actions globales et ensembles de wikis

 
Capture d'écran de Special:GlobalGroupPermissions (sélection de groupe).
 
Capture d'écran de Special:GlobalGroupPermissions (liste des droits).

Les comptes globaux ont les mêmes nom d'utilisateur et mot de passe réservé sur tous les wikis publics de Wikimédia (sauf les comptes locaux créés avant la mise en place du SUL). Des groupes globaux peuvent être assignés aux comptes globaux, qui donnent certains droits à l'utilisateur sur tous les wikis (dans un wikiset spécifique) où son copmte global peut se connecter.

Notez qu'un "droit" (ou une "permission") est un accès spécifique (comme "edit-interface"), et ne pas être donné directement à un utilisateur ; un "groupe" est un groupement abstrait de droits (comme "steward").

Gestion des groupes

Stewards can create, edit, or delete a global group using Special:GlobalGroupPermissions. The scope of each group can be global (all public wikis), or defined for a specific set of wikis.

  • Edit:
    1. In the "Existing groups" box, click "View and edit permissions" for the group you want to edit.
    2. A list of possible rights will appear (see also mw:Help:User rights). Check the rights the group are to have and uncheck those they are not to have.
    3. If the group needs access on specific wikis (instead of globally), select the set of wikis in the drop down menu above the list of rights (see Managing sets of wikis).
    4. Enter the reason for the change in the textbox below.
    5. Click "Save changes to group permissions". The changes will be applied immediately.
  • Create:
    1. Enter the group name in the "Create a new group" textbox.
    2. Click "Assign permissions".
    3. Check at least one right, and if applicable select the scope (see step 2 onward how to edit above).
    4. Create necessary MediaWiki pages (see :mw:Manual:User rights).
  • Delete:
    1. Uncheck all its rights (see how to edit above).
    2. The group can be recreated later, and all former members will regain the same rights.

Gestion de l'appartenance à un groupe

 
Screenshot of Special:GlobalGroupMembership with example content.

Stewards can edit global accounts' membership using Special:GlobalGroupMembership. Placing a global account in global groups will give them all the rights assigned to that group on all public wikis.

  1. Enter the global account's user name in the textbox.
  2. Select a wiki where they have a local account from the drop-down menu.
  3. Click "Edit user groups". A "Edit user groups" box will appear below.
  4. Check the global groups to assign. (Even if they are similarly named, global and local groups are not necessarily identical!)
  5. Enter the reason for the change in the textbox.
  6. Click "Save User Groups".

Gestion d'ensembles de wikis (pour les groupes globaux)

Stewards can define "wiki sets" using Special:WikiSets, lists of wikis where global groups can be given access (instead of globally). It's not necessary to create a set of all wikis: that is the default for global groups if no set is selected.

  1. If you're creating a new set, click "Create a new set". Otherwise, click "view/edit" beside the name of the existing set to edit.
  2. Enter the set's name in the "name" box. This is for the convenience of stewards, and can be changed any time.
  3. Select the appropriate type in the "type" box (opt-in or opt-out).
  4. Enter the database prefixes, one per line, in the "wiki" box.
  5. Enter the summary or reason for your change, which will appear in the global rights log.

Gestion des comptes globaux

 
Screenshot of the CentralAuth interface for managing global accounts
 
Error message when trying to log in with a locked account

Stewards can access unification information about a particular global account, unattach local accounts from the global account, delete the global account (restoring all local accounts), and lock out access to the account using Special:CentralAuth (see logs).

Bug: Special:CentralAuth can only hide the global account (see bug 14476). An option to hide local accounts when using the CentralAuth can be enabled with the gadget in Special:Preferences#mw-prefsection-gadgets.

Renommage de compte global

Global accounts can be renamed (see the help page). If a user would like a new username, they should use the following process:

  1. Check availability of the new name with a tool such as CentralAuth. If there are existing accounts with that name that have contributions, especially across multiple projects, the user is encouraged to select a different name, as usurping users with significant contributions is not likely.
  2. Request a username change on SRUC.

Note that global renames should be done in accordance with the global rename policy.

Suppression de compte global

Stewards can, via Special:CentralAuth, delete global accounts. This should only be done when there is a compelling reason. Requests such as "I don't want it" are not sufficient to warrant a deletion.

  • Requests to delete the global accounts of vandals should not be performed at all, as this would interfere with the ability to lock the account in case of a spread of the abuse.
  • Users should be warned that preferences (including passwords and email addresses) will be reset to their pre-merge values and that they will lose any global group membership which they previously had. Local accounts will not be otherwise affected and cannot be deleted.
  • Some bot owners may request a deletion of the global account if it interferes with proper functioning of the bot. Of course, non-unified bots are not eligible for the "global bot" flag, and if the bot login password has changed during the time it was unified, that password will be reset to the pre-unification password.
  • Warning: Once a global account is deleted, it cannot be reversed by stewards (see also bug T25243).

Séparation de comptes locaux d'un compte global

If a local project wishes to rename a vandal account, unmerge only that project from the vandal's global account, even if it's the only project in the global account. If there is a valid reason to not want the global account to be visible after the rename, the global account should be hidden instead of deleted, as deleting it would simply open that account name to recreation.

Restrictions d'accès globales

Blocages d'adresses IP

 
Error shown to globally blocked users when they try to edit.

Stewards can block IP addresses and CIDR ranges (up to /16 in size for IPv4, up to /32 for IPv6) on all public Wikimedia wikis using Special:GlobalBlock, and remove a global block using Special:GlobalUnblock (see guidelines at Global blocking). Current global blocks are listed on Special:GlobalBlockList and logged on Special:Log/gblblock.

Globally blocked IPs cannot edit any page on any wiki except MetaWiki (which allows users to appeal on Meta). When a global block conflicts with a local block, the strongest block will apply; for example, a global anonymous-only block will be overridden by a local full block.

Local administrators can unblock a globally-blocked address on single wikis using Special:GlobalBlockWhitelist on those wikis, and customize the error message using MediaWiki:Globalblocking-blocked.

Global account lock (& hide)

Filtre anti-abus global

Since July 2013, stewards can create abuse filters on MetaWiki (Special:AbuseFilter) and then mark them as global; however, these global filters only apply to some wikis. See "Global AbuseFilter" for the current status of this tool. See here for some proposed guidelines during this phase of Global AbuseFilter deployment.

Recommandations pour le traitement des demandes

Droits d'accès utilisateur

  1. Check the Steward requests/Permissions page regularly
  2. Check that the procedure on that page has been followed and that the request does not violate any policies or guidelines (see the following sections for details).
  3. If the request is valid, fulfill it using Special:Userrights (see above for instructions).
  4. Mark the request as fulfilled (this is most often done with {{done}}) or rejected ({{not done}}) as appropriate.
  5. You can optionally tell the user, preferably on his own wiki, that he is now an admin and/or bureaucrat and invite him to join the admin channel by using Template:Invite.
  6. Leave the request on Steward requests/Permissions to allow follow-up comments and questions. It will be moved into the archive by a bot.

Recommandations générales

  • Checking facts: If a user claims they already have a certain right, you can verify this by checking Special:Listusers on the local project. If the steward has any doubts about the request, they should discuss with one or more regular users of the local project.
  • Promoting very new users: There is no approved policy regarding the promotion of very new users for projects with no local community. New users should generally not be given rights until they have spent more time editing projects. However, stewards might grant new users temporary rights until a community has time to build up, at which point it can hold a vote to confirm the user's status.

Droits d'administrateur et de bureaucrate

  • If the wiki has a community, the community should have approved the user's request, generally on a local request page. The user should wait at least a week—perhaps two if the community is very small—before placing their request on Meta.
  • If the wiki has no community, or if it has too few active users to hold a meaningful discussion of the issue, it is probably advisable to grant temporary rather than permanent rights. Three months is a common period for temporary rights.
  • Be sure the community does not already have a local bureaucrat. Stewards should only grant administrator and bureaucrat requests on wikis with no local bureaucrats. The only exception to this is if all local bureaucrats have been inactive for a period of time.

Vérificateurs d'adresses IP

  • Read the CheckUser policy carefully. Pay particular attention to the Access section, which specifies several important rules regarding the bestowal of this status. The use of this tool can have legal implications, so knowing and following the policy is of the utmost importance. Breach of the rules in this policy may result in removal of steward rights.
  • Send this e-mail to the user to request that they sign the Confidentiality agreement for nonpublic information with the Wikimedia Foundation, record on the request page that the mail has been sent.
  • If the user claims to have already signed the confidentiality agreement with the Foundation, check the Access to nonpublic personal data policy noticeboard or ask for confirmation of this fact from the Trust and Safety team.
  • Grant rights only after receiving confirmation from the Wikimedia Foundation that the confidentiality agreement has been signed.
  • After granting access, list the user in the appropriate section on CheckUser.
  • Ask the user to subscribe to checkuser-l, and notify the listadmins that the user has been approved.

Droits des masqueurs de versions

  • Read the policy at Oversight policy carefully. Pay particular attention to the Access section, which specifies several important rules regarding the bestowal of this status. The use of this tool can have legal implications, so knowing and following the policy is of the utmost importance. Breach of the rules in this policy may result in removal of steward rights.
  • On the English Wikipedia, only the Arbitration Committee can approve a request for this status.
  • Send this e-mail to the user to request that they sign the Confidentiality agreement for nonpublic information with the Wikimedia Foundation, record on the request page that the mail has been sent.
  • If the user claims to have already signed the confidentiality agreement with the Foundation, check the Access to nonpublic personal data policy noticeboard or ask for confirmation of this fact from the Trust and Safety team
  • Grant rights only after receiving confirmation from the Wikimedia Foundation that the confidentiality agreement has been signed.
  • After granting access, list the user at Oversight policy/User list.

Retrait des accès

  • If a user requests that his or her own rights be removed, it is generally put on hold for some time (usually 24 hours) to allow the user to change their mind if they wish to do so.
  • If a user requests that another user's rights be removed, be sure that the action complies with the local wiki's policy on removal of rights. This will often involve sifting through a lengthy debate on a local request page to confirm the validity of the procedure.
  • After removing a user's checkuser or oversight rights, do not forget to remove them from the corresponding lists.

Droits temporaires

CheckUser information

  • See Steward requests/Checkuser.
  • If local checkusers exist in a project, checks should generally be handled by those. In emergencies or for multi-project checkuser checks as in the case of cross-wiki vandalism stewards may perform local checks. Stewards should remove checkuser access on the projects upon completion of the checks and notify the local checkusers or checkuser email list. (from the official CheckUser policy page).
  • Stewards may checkuser on loginwiki as a form of long-requested "cross-wiki checkusering" (link).
  • Note: The German Wikipedia requests that absolutely all CheckUser queries must be announced on de:Wikipedia:Checkuser/Anfragen (please ask the local users with access if you need help with formulation, or with precisely what should be published).

Autres tâches des stewards

  • Ideally, one or several stewards should be 'on duty' in the #wikimedia-stewardsconnecter IRC channel at any given time. Users of small wikis are encouraged to use this channel to report emergencies, but it has also been used for conversation about and among stewards, and for discussion of routine matters.
  • We have a VRT queue, ideally at least one steward should review and sort the incoming queue at least once a day.

Modèles de courriels

To be sent to users with access to private data:

Communication avec les autres stewards

Mailing list: There is a private stewards mailing list, for discussions of policy and private requests. Please be advised that some mail services might mark some mail as "Spam". For instance, when using Gmail, it may be useful to setup a filter, instructing the service to avoid marking mails that are addressed "To: stewards-l@lists.wikimedia.org", checking the box "Never send it to Spam".

IRC: The public #wikimedia-stewardsconnecter channel is a place to ask for help, announce emergencies, or discuss ongoing events with stewards and others. stewardbot will flag stewards' attention in the channel if you say @steward for routine requests and !steward for urgent requests.

Meta: High-level discussion about policy and other wikis takes place on the Stewards’ noticeboard and Babel.

Outils et signalement de bogues

Outils

user or wiki activity
other
  • CrossBlock: block status of given IP, CIDR range, or user on all wikis with links to prefilled block/unblock forms.
  • gUserSearch: search and filter global accounts by exact, partial, or regex match.
  • SULutil and Stalktoy: information about a given global account, and information and unification status for each local account with that name.
  • SULWatcher - Reports: reports and logs of SULWatcher's monitoring of account unifications.
  • Steward requests: overview of open steward requests.
JavaScript
  • StewardScript: adds shortcuts to the Meta interface for quicker stewarding.
  • hideuser: allows quickly crosswiki local-hiding of globally locked & hidden accounts; available on the gadgets tab of Special:Preferences
IRC
  • StewardBot: a Python script which accepts commands from authorized stewards on IRC and performs utility operations related to steward activities.