NOTE: The #Security-Team will strive to set an Estimated Start date after submission
**Project Information **
* Name of tool/project: ChessBrowser
* Project home page: [[https://www.mediawiki.org/wiki/Extension:ChessBrowser]]
* Name of team requesting review: ChessBrowser
* Primary contact: Wugapodes
* Target date for deployment:
* Link to code repository / patchset: [[https://gerrit.wikimedia.org/r/plugins/gitiles/mediawiki/extensions/ChessBrowser/]]
**Description of the tool/project: ** ChessBrowser is an extension which takes [[ https://en.wikipedia.org/wiki/Portable_Game_Notation | Portable Game Notation ]] and produces an interactive user interface for viewing and navigating the chess game.
**Description of how the tool will be used at WMF:** The extension would primarily be used on Wikipedias to enhance encyclopedic coverage of chess games such as the Opera Game and the Evergreen Game. The Hebrew and Russian Wikipedias have a javascript gadget for this purpose, but the English Wikipedia has not done so for performance reasons. Despite this, multiple discussions on the English Wikipedia have shown a desire for a way to interactively view chess games ([[https://en.wikipedia.org/wiki/Wikipedia:Village_pump_(technical)/Archive_175#Enable_chess_PGN_viewer_for_chess_articles | most recent discussion]], [[https://en.wikipedia.org/wiki/Wikipedia:Village_pump_(proposals)/Archive_132#Interactive_chess_boards|2016 discussion]], [[https://en.wikipedia.org/w/index.php?sort=relevance&search=Chess&prefix=Wikipedia%3AVillage+pump&title=Special:Search&profile=advanced&fulltext=1&advancedSearch-current=%7B%7D&ns0=1|village pump archive search]]).
**Dependencies**
None
**Has this project been reviewed before?**
No
**Working test environment**
I have a test environment set up using mediawiki vagrant. Taking any PGN and placing it between <pgn></pgn> tags will invoke the extension and allow testing. A good test example would be copying https://www.mediawiki.org/wiki/Extension:ChessBrowser/Test_games, which includes multiple games with different special behaviours.
**Post-deployment**
Wugapodes and DannyS712 will be primarily responsible for the code. Kipod has also contributed to the code base and may be interested in post deployment support.