Release status: beta
|Implementation||API, ContentHandler, User interface|
|Description||Robust false-positive and feedback gathering system, to allow human refutation and review of ORES scoring.|
|Author(s)||The Scoring Platform team|
|License||GNU General Public License 3.0 or later|
|Translate the Jade extension if it is available at translatewiki.net|
|Check usage and version matrix.|
|Issues||Open tasks · Report a bug|
The Jade (Judgment And Dialog Engine) extension provides two new namespaces,
Jade_talk, used for collecting and discussing proposals. Proposals are an opinion about a wiki revision, diff, or page.
For background information, see the Jade project page.
- Download and place the file(s) in a directory called
- Only when installing from git run Composer to install PHP dependencies, by issuing
composer install --no-devin the extension directory. (See T173141 for potential complications.)
- Add the following code at the bottom of your LocalSettings.php:
wfLoadExtension( 'Jade' );
- Done – Navigate to Special:Version on your wiki to verify that the extension is successfully installed.
// Provide proposal title translations for your wiki. $wgJadeEntityTypeNames = [ 'diff' => 'Разница', 'revision' => 'Версия', 'page' => 'Страница', ]; // For Wikidata: replace the wp10 article quality scale with something wacky. $wgJadeAllowedScoringSchemas['revision'] = [ 'itemquality' ];
To add interface support for your language, please help translate at https://translatewiki.net/wiki/Special:MessageGroupStats?group=ext-jade
Pages in the
Jade namespace are difficult to edit by hand, and are intended to be edited through a third-party tool. Currently, no such integrations exist, so please check in again later.
To endorse a proposal, you can post a signed comment to its endorsement section or create another proposal with supporting data and your own comments.
To challenge a proposal, create and endorse an alternative proposal.
We encourage users and integrators to offer free-text justifications or other explanations in the proposal
notes field. These notes are stored publicly as part of the Jade entity page and can be edited later.
Bots, abuse, and quality standards
Please do not create proposals for "autopatrolled" predictions, nor any automatically or semi-automatically generated data. This includes scores from ORES unless you have verified, using your own judgment, that the correct score is the same score given by ORES.
We ask that developers don't integrate without including the collaboration features. For example, don't send a "damaging: true" proposal as a side-effect of a patrolling workflow, unless the interface also shows existing proposals, the proposal notes, links to the entity page and so on.
Beyond these requirements, nothing is non-notable in Jade. Enjoy!