Extension:FlaggedRevs/fr

L'extension Flagged Revisions permet aux contributeurs et aux relecteurs d'évaluer les révisions des articles et de définir ces révisions comme les révisions par défaut affichées lors de la vue normale d'une page. Ces révisions resteront les mêmes, même si les modèles inclus ou les images viennent à être modifiées. Ceci per met à MediaWiki d'agir plus comme un système de gestion de contenu (Content Management System - CMS).

Configuration
Suivre ces étapes pour installer FlaggedRevs :

Reviewers will see the reviewer's widget on the bottom of an editable page.
 * 1) Assurez-vous d'exécuter MediaWiki version 1.17 ou supérieur. Sinon, vous devez faire une mise à jour avant de pouvoir installer FlaggedRevs.
 * 2) Téléchargez FlaggedRevs. Choisissez une version de FlaggedRevs compatible avec votre version de MediaWiki. Par exemple : si vous utilisez MediaWiki 1.17, téléchargez FlaggedRevs 1.17.
 * 3) Décompressez le fichier téléchargé dans le dossier   de votre installation MediaWiki. Par exemple :
 * 4) Assurez-vous que les codes de hachage des images sont à jour en exécutant le script de maintenance . Par exemple :
 * 5) Assurez-vous que le répertoire   est accessible en lecture par le serveur web (afin que ce dernier puisse fournir le CSS de FlaggedRevs, les images et le JavaScript). Par exemple : en supposant que la personne qui a démarré le serveur web n'est pas le propriétaire du répertoire  , exécutez :
 * 6) Active la collecte des statistiques concernant la relecture des articles.
 * 7) Désactive la génération des statistiques à la demande. Initialiser   dans . This will prevent statistics from being generated when articles are accessed (which can lead to poor performance when many articles without current statistics are accessed concurrently).
 * 8) Active la génération des statistiques au calendrier. Crée une tâche de cron pour exécuter   à intervalles réguliers. Exécuter   pour voir combien temps prend le scénario pour courir et mettre son cron avec des intervalles de travaux approchés. For example, to create a cron job that runs   as user   every hour:
 * 9) Activer FlaggedRevs en ajoutant la ligne suivante à  :
 * 10) Mettre à jour les schémas de la base de données MediaWiki en exécutant  . This must be done after the above step is saved or you will receive a database error when accessing any page.
 * 11) Promouvoir les utilisateurs en tant que relecteurs. After FlaggedRevs is first installed, no user can see the reviewer's widget. To fix this, login as a wiki bureaucrat and go to Special:UserRights, then grant review rights to one or more users.
 * 1) Activer FlaggedRevs en ajoutant la ligne suivante à  :
 * 2) Mettre à jour les schémas de la base de données MediaWiki en exécutant  . This must be done after the above step is saved or you will receive a database error when accessing any page.
 * 3) Promouvoir les utilisateurs en tant que relecteurs. After FlaggedRevs is first installed, no user can see the reviewer's widget. To fix this, login as a wiki bureaucrat and go to Special:UserRights, then grant review rights to one or more users.
 * 1) Mettre à jour les schémas de la base de données MediaWiki en exécutant  . This must be done after the above step is saved or you will receive a database error when accessing any page.
 * 2) Promouvoir les utilisateurs en tant que relecteurs. After FlaggedRevs is first installed, no user can see the reviewer's widget. To fix this, login as a wiki bureaucrat and go to Special:UserRights, then grant review rights to one or more users.
 * 1) Promouvoir les utilisateurs en tant que relecteurs. After FlaggedRevs is first installed, no user can see the reviewer's widget. To fix this, login as a wiki bureaucrat and go to Special:UserRights, then grant review rights to one or more users.

Droits utilisateurs et groupes d'utilisateurs
Par défaut, aucune personne ne peut relire quoi que ce soit, donc la première étape est de définir les droits utilisateur.

Droits utilisateurs
FlaggedRevs crée les nouveaux droits utilisateur suivant :
 * – utilisateur pouvant relire les révisions
 * – utilisateur pouvant relire les révisions et pouvant placer toutes les balises à tous les niveaux
 * – toutes les nouvelles révisions faites par l'utilisateur sont automatiquement marquées comme ayant été revues
 * – relecture automatique pour les annulations faites par l'utilisateur.
 * – utilisateur pouvant afficher Special:UnreviewedPages
 * – utilisateur pouvant modifier les paramètres des révisions stables de n'importe quelle page
 * – utilisateur pouvant renommer (déplacer) des pages ayant des révisions stables

Groupes d'utilisateurs
FlaggedRevs creates the following new user groups:


 * – receive, plus the standard MediaWiki user rights
 * – receive, plus the standard MediaWiki user rights
 * – receive

Comment assigner des droits utilisateurs
Les droits utilisateur peuvent être assignés de deux manières :

Assign these user rights to existing user groups in :
 * En assignant les droits aux groupes d'utilisateurs

Manually add user accounts to the appropriate groups via Special:UserRights.
 * En assignant les droits à des utilisteurs spécifiques
 * By default:
 * Bureaucrats can add/remove Reviewers
 * Administrators can add/remove both Autoreviewers and Editors.

Configuration de base
FlaggedRevs.php comes with a number of configurable variables. These should be configured in LocalSettings.php.


 * – Sets what namespaces may be subject to the review process. C'est un tableau d'entiers. Look at the beginning of includes/Defines.php to see what integer the default namespaces map to and use the defined constants for readability.
 * – Sets the tags and their three settings: 'levels', 'quality', and 'pristine'
 * Définition
 * is an associative array with keys corresponding to each tag name and values that are arrays of the three settings 'levels', 'quality', and 'pristine':
 * 'levels' controls the number of review levels,
 * 'quality' decides what level the tag must be for a revision to be 'quality'
 * 'pristine' decides what level the tag must be for a revision to be 'pristine'
 *  Labeling 
 * Each tag can be labeled editing the page MediaWiki:revreview-.
 * Each tag level can be labeled editing the page MediaWiki:revreview--.
 * Exemple
 * Suppose one wants to have "accuracy", "depth", and "tone" tags, with 3 levels each.
 * The admins also want revisions with at least "accuracy" and "depth" of the 2nd levels to count as "quality". The following settings will do that:
 * By default, the tags are labeled as they are set in the $wgFlaggedRevsTags array. In this example this means the tags appear exactly as 'accuracy', 'depth' and 'tone'.
 * To show tags for example as their capitalized name, the admins have to edit these pages with the shown content:
 * {|class="wikitable"
 * {|class="wikitable"

!balise ! labeling page ! content
 * accuracy
 * MediaWiki:revreview-accuracy
 * depth
 * MediaWiki:revreview-depth
 * tone
 * MediaWiki:revreview-tone
 * Tone
 * }
 * tone
 * MediaWiki:revreview-tone
 * Tone
 * }
 * }


 * To label the tag levels, the admins have to create these pages with the shown content:


 * {|class="wikitable"

!balise ! level ! labeling page ! content
 * rowspan=3|accuracy
 * 0
 * MediaWiki:revreview-accuracy-0
 * 1
 * MediaWiki:revreview-accuracy-1
 * 2
 * MediaWiki:revreview-accuracy-2
 * rowspan=3|depth
 * 0
 * MediaWiki:revreview-depth-0
 * 1
 * MediaWiki:revreview-depth-1
 * 2
 * MediaWiki:revreview-depth-2
 * rowspan=3|tone
 * 0
 * MediaWiki:revreview-tone-0
 * Mauvais
 * 1
 * MediaWiki:revreview-tone-1
 * Bon
 * 2
 * MediaWiki:revreview-tone-2
 * Excellent
 * }
 * rowspan=3|tone
 * 0
 * MediaWiki:revreview-tone-0
 * Mauvais
 * 1
 * MediaWiki:revreview-tone-1
 * Bon
 * 2
 * MediaWiki:revreview-tone-2
 * Excellent
 * }
 * 2
 * MediaWiki:revreview-tone-2
 * Excellent
 * }


 * The resulting setup will be:


 * {|class="wikitable"

! tag names !colspan=3| level names
 * Tone
 * Mauvais
 * Bon
 * Excellent
 * }
 * Tone
 * Mauvais
 * Bon
 * Excellent
 * }
 * Tone
 * Mauvais
 * Bon
 * Excellent
 * }
 * }


 * – Whether the stable version is the default content for pages.
 * – An array with keys corresponding to each flag type, and values that are arrays of rights and how high users with it can rate the flags (integral tag level).
 * Exemple
 * – Array of string titles. These titles are pages that are exempt from FlaggedRevs. They are unreviewable and have no flagging UI. Replace ' ' with '_' in titles (e.g. "Main page" -> "Main_page").
 * – Array of string titles. These titles are pages that are exempt from FlaggedRevs. They are unreviewable and have no flagging UI. Replace ' ' with '_' in titles (e.g. "Main page" -> "Main_page").
 * – Array of string titles. These titles are pages that are exempt from FlaggedRevs. They are unreviewable and have no flagging UI. Replace ' ' with '_' in titles (e.g. "Main page" -> "Main_page").

Interface utilisateur

 * – When enabled, a simpler, icon based UI is used. Does not affect the tags shown in edit mode.
 * – This setting hides the review status box/bar for pages that are reviewed in their latest version. Explanatory text is also removed from some places.

Flux du travail

 * – Makes users in these groups see the current/draft revision by default.
 * – If enabled, every edit by a user with 'autoreview' rights is automatically reviewed upon save. There is no need to hit the "submit review" button. This feature requires that the previous revision was also reviewed; otherwise, auto-review will not occur.
 * – If  is enabled, this settings controls how high each tag can be auto-reviewed. If allowed, tags will be auto-reviewed to the same level the previous revision tags were. This is an associative array; each key is a tag and each value is a tag level.
 * Exemple

Promotion automatique de l'utilisateur

 * – An array with keys for days, edits, time spacing, benchmarks, emailconfirmed, recent content page edits, total content edits, content pages edited, edit summaries used, IP uniqueness, and userpage existence as keys. The values correspond to how many days/edits are needed for a user account to be autopromoted to Editor status and whether they must be emailconfirmed and have a user page do so. The user must have at least X edits that are Y or more days apart, where X is the number of benchmarks and Y is the time spacing. Set this variable to false to disable this entirely.
 * Exemple
 * For $wgFlaggedRevsAutopromote, one might have:
 * Exemple
 * For $wgFlaggedRevsAutopromote, one might have:

Utilisation avancée
See FlaggedRevs.php for a complete list of configuration options (with some explanatory comments). Be sure to change only localsettings.php to set configuration options rather than editing this file.

To have a wiki where non-users can only see the stable version of articles, see.

Utilisation

 * Voir aussi : 

Approving pages
Users with some level of review status will have a small rating form on page view (at the bottom of the page) and diffs (at the top of the page) that lets them review revisions. Each tag must at least meet the minimal level of approval. Users should look at the whole page, included templates and images, before reviewing. The (diff to stable) link is very useful for speeding up this process.

Users cannot review a page which they cannot edit. They cannot lower the level of a revision from a level they cannot set. Blocked users cannot do anything.



At Special:StableVersions, you can list out all of the reviewed revisions for a certain page or view reviewed revisions.



Upkeep
At Special:UnreviewedPages, there is a list of pages that have not yet been reviewed, for Editors only. A namespace must be selected and an optional category filter is also present.



At Special:OldReviewedPages, there is a list of pages that have been reviewed, but have edits pending. This is for Editors only. An optional category filter is also present.



Pages that cannot be reviewed can still be patrolled for anti-vandalism purposes by Editors to see what has been checked already.

A list of reviewed pages at the main review levels can be found at Special:ReviewedPages.



Journalisation
All relevant actions are permanently logged, so everything can be tracked and overseen properly.


 * A log of promotion/demotion of editors and the reasons is kept at Special:Log/userrights.
 * A log of the approval/unapproval of revisions is kept at Special:Log/review.
 * A log of changes to the stable versioning configuration to pages is logged at Special:Log/stable.

Also, a new page, Special:QualityOversight shows only flaggings log entries related to quality revisions. This is useful if the main log is too flooded with page "sightings".

API
FlaggedRevs adds API modules for reviewing revisions and configuring "stabilization" of pages, a module for retrieving flag configuration, and three list modules corresponding to the special pages for reviewed pages, unreviewed pages and "old" reviewed pages.

Some more API documentation is at.

action = review
Reviews a page.


 * Parameters
 * : The revision ID for which to set the flags
 * : A csrf token retrieved through
 * : Comment for the review (optional)
 * : Set the flag named "accuracy" to the specified value; (replace "accuracy" with the flag name to set another flag)


 * Example

action = stabilize
Changes page stabilization settings.


 * Parameters
 * : Title of page to be stabilized
 * : Reason for stabilization
 * : (Deprecated?) Stabilization expiry. Default: infinite
 * : Whether to auto-review the page
 * : Whether to watch the page
 * : An edit token retrieved through
 * For protection-like configurations :
 * : The right users must have in order for their edits to not require review.
 * Otherwise :
 * : Default revision to show (latest | stable)
 * : Which stable revision should be shown (pristine | quality | latest). Default: quality
 * : Restriction level for the 'autoreview' right (sysop | none). Default: none


 * Exemple

action = flagconfig
Shows information about review flag configuration.

The following parameters are returned for each tag:


 * : the name of the flag
 * : the number of possible levels the flag has (not counting the "unreviewed" level)
 * : level the flag must be for the revision to be considered "quality"
 * : level the flag must be for the revision to be considered "pristine"

The displayed name for each flag and the different level names for each flag are MediaWiki messages, so can be set and retrieved through the appropriate page; for example the name for the first level of the "accuracy" flag is located at MediaWiki:revreview-accuracy-1.


 * Exemple

list = reviewedpages
Lists pages that have been reviewed.


 * Parameters
 * : Start listing at this page id.
 * : Stop listing at this page id.
 * : In which direction to list.
 * : The namespaces to enumerate.
 * : How to filter for redirects
 * : How to filter by quality (0=sighted,1=quality)
 * : How many total pages to return.


 * Exemple

list = unreviewedpages
Lists pages which have never been reviewed.


 * Parameters
 * : Start listing at this page title.
 * : Stop listing at this page title.
 * : The namespaces to enumerate.
 * : How to filter for redirects
 * : How to filter by quality (0=sighted,1=quality)
 * : How many total pages to return.


 * Exemple

list = oldreviewedpages
Lists pages that have at some point been reviewed, but for which the most recent revision is not reviewed.


 * Paramètres
 * : Start listing from this timestamp
 * : Stop listing at this timestamp.
 * : In which direction to list.
 * : Espaces de noms à énumérer.
 * : Comment filtrer les redirections
 * : How many total pages to return.


 * Exemple

prop=flagged
Use action=query&prop=flagged to get information about the flagging status of the given pages.

Limitations
Therefore, there would be no pointers to the revision id for this different template to load from, making it blue linked. You will be notified if this happens during review.
 * Transclusions across wikis are not stabilized
 * External images (aside from Commons) are not stabilized
 * Metatemplates that conditionally include other templates may have the condition change between the time a reviewer loaded a page and when they reviewed it.

Uninstalling

 * 1) Remove the include line from
 * 1) Drop the tables in.
 * 1) Drop the columns ,  , and  , and the index   from the   table (if they exist; only older versions of FlaggedRevs used these)
 * 1) Run   from the command line to flush out the stable version links
 * 1) Run   from the command line if you use

Plate-formes de test

 * 
 * 
 * 

Voir aussi

 * – edits remain private until they're approved
 * Flagged Revisions
 * – documentation about the user groups and rights created by this extension, while it was at use on mediawiki.org
 * – edits remain private until they're approved
 * Flagged Revisions
 * – documentation about the user groups and rights created by this extension, while it was at use on mediawiki.org

Liens externes

 *  Quality Assurance in an Open Project  – 2008 Wikimedia blog post
 * Images of Flagged Revisions – Wikimedia Commons
 * About Flagged Revisions – Meta-Wiki

Licensing
© GPL, Aaron Schulz, Joerg Baach, 2007