Community Tech team/All Our Ideas

The All Our Ideas Tool Survey was a survey conducted of the English and Spanish Wikipedia communities in 2014 to collect and prioritize ideas for improving the tools used by those communities. The results of the survey can be seen at the following URLs:
 * http://www.allourideas.org/wikimediagadgets/results (English)
 * http://www.allourideas.org/wikimediaaccesorios/results?locale=es (Spanish)

While preparations are being made for a cross-project technical request survey, the Community Tech team has begun working on the requests identified by the community as high priority in the All Our Ideas survey. The Top 10 requests from both the English and Spanish surveys are combined below. (There are less than 20 listed because some appeared in both languages.)

For details about the process used for organizing work on this page, see /Process.

Reflinks
Scores: 75 (English), 54 (Spanish)
 * Documentation
 * Interface

Discussion
Discussing with Dispenser (maintainer). Ryan Kaldari (WMF) (talk) 02:06, 12 August 2015 (UTC)

Checklinks
Scores: 65 (English)

Discussion
Discussing with Dispenser (maintainer). Ryan Kaldari (WMF) (talk) 02:32, 12 August 2015 (UTC)

Dab Solver
Scores: 63 (English)
 * Interface

Discussion
Discussing with Dispenser (maintainer). Ryan Kaldari (WMF) (talk) 02:44, 12 August 2015 (UTC)

Add i18n support to Magnus' tools
Scores: 60 (Spanish)

Discussion
Need to answer the following questions: See Phabricator ticket for more info. Ryan Kaldari (WMF) (talk) 23:53, 25 August 2015 (UTC)
 * What would be the best UI for allowing the user to select their language from Magnus' tools?
 * How would translations for the tools be acquired? Would it be possible to use TranslateWiki?
 * How much work would be involved in refactoring the existing tools to use this system?

Promote the LanguageTool WikiCheck on relevant wikis
Per, we should advertise the LanguageTool WikiCheck on the Wikipedias for the 20 languages it supports. It is a very useful tool, but probably not well known since it isn't hosted on Tool Labs.

Acceptance criteria:
 * Create a blurb on meta or mediawiki.org about the LanguageTool WikiCheck (http://community.languagetool.org/wikiCheck/pageCheck/index)
 * Set it up for translation using the content translation system (https://www.mediawiki.org/wiki/Help:Extension:Translate/Page_translation_example)
 * Send an email to the translate mailing list asking for translations in the 20 languages supported by LanguageTool
 * Post the translated notices on the Village Pump/Community Chat pages of the 20 Wikipedias corresponding to those languages (or get a Community Liaison to do it)

This is currently blocked by .

Analysis

 * Support: ?
 * Feasibility: ?
 * Impact: ?
 * Risk: ?

Priority: ?

Fix HotCat on wikis where it is broken
Per, HotCat is currently broken on many wikis that have local copies of the old gadget code (rather than importing the code from Commons). We should identify the wikis that have local copies, and fix them.

To identify the wikis where it is broken, we could run a bot to check MediaWiki:Gadget-HotCat.js on each wiki and see if it is more than a few lines long, which generally means there is a local version of the Gadget (which is probably broken).

They can either be fixed by applying the same fix that was used on English Wikipedia and Commons or by switching them to import the Gadget code directly from Commons or English Wikipedia.


 * English Wikipedia documentation
 * Commons documentation

Analysis

 * Support: Medium/High
 * Feasibility: Good/Medium (not sure how many instances are broken)
 * Impact: High
 * Risk: Low

Priority: High

Make Twinkle localizable to any wiki
Per, it would be awesome if Twinkle could be localized for wikis other than English Wikipedia. Since Twinkle is very tied to wiki-specific templates and processes, this is going to mostly involve creating an on-wiki configuration system (perhaps using JsonConfig) rather than a traditional i18n architecture. See and https://github.com/azatoth/twinkle/issues/129 for more discussion on this.


 * Documentation
 * Code repo

Analysis

 * Support: High
 * Feasibility: Medium/Difficult (See Phabricator ticket and )
 * Impact: High
 * Risk: High

Priority: High

Integrate Turnitin into Copyvio Detector
Plagiabot provides an API for testing articles with the Turnitin engine (see https://en.wikipedia.org/wiki/Wikipedia:Turnitin). Here is an example of the API output for a specific article: http://tools.wmflabs.org/eranbot/plagiabot/api.py?action=suspected_diffs&page_title=Rajesh_Khanna&report=1. (It returns an array of 1 or more potential violations.)

It would be great if the Copyvio Detector tool had the option of using Turnitin as well as Yahoo BOSS for detecting possible copyright violations.

Acceptance criteria:
 * In the "Copyvio search" options, add a new option for "Use Turnitin"
 * If "Use Turnitin" is checked, include source URLs from the Plagiabot API output in the "Checked Sources" list (and have them actually be checked by Copyvio Detector)
 * Source URLs that are detected by both Turnitin and Yahoo should only be shown in the list once
 * If the source URL isn't publicly accessible, show an error and link to the Turnitin report

For now, we should only use the Plagiabot API as a source for more source URLs to compare using the Copyvio Detector engine. For the sake of consistent output (that isn't mixing apples and oranges), we should not use Plagiabot's score or reports (at least for now), but should use the score and diffs generated by the Copyvio Detector engine.

Analysis

 * Support: Medium
 * Feasibility: Good
 * Impact: Medium
 * Risk: Medium/Low (unclear if all Turnitin sources are publicly accessible)

Priority: Normal

Fix RevisionJumper Firefox bug
Per, we should fix the bug in RevisionJumper that breaks certain links in Firefox. It looks like this is due to Firefox never completing the page load for some reason.


 * Original bug report

Analysis

 * Support: Medium
 * Feasibility: Good
 * Impact: Low
 * Risk: Low

Priority: Normal

Add i18n support to Copyvio Detector
Per, we would like to add basic i18n support to the Copyvio Detector tool on Tool Labs.

Acceptance criteria:
 * You can set UI language via query string, e.g. ?uselang=es (so that links from particular projects can pre-set the language)
 * uselang query string parameter is preserved while navigating to tool settings page and back
 * Language can be set explicitly from the settings page and stored in a cookie
 * Language cookie can be deleted via the settings page (same as other Copyvio Detector cookies)
 * i18n architecture must be easily extendable for adding new languages (this probably means that you want to create separate i18n files for each language and have some sort of key for each i18n string that gets mapped to a translated string in the i18n files)
 * Should support at least 1 language besides English (pick a language you know or can easily get translations for)

Analysis

 * Support: Medium
 * Feasibility: Good
 * Impact: Low
 * Risk: Low

Priority: Normal

Add spell-checking option to LanguageTool WikiCheck

 * LanguageTool WikiCheck interface

Analysis

 * Support: Medium (spell-checking was identified as high priority in Spanish survey, but this tool was not specifically mentioned)
 * Feasibility: Good
 * Impact: Medium
 * Risk: Low

Priority: Normal

Turn RevisionJumper into an extension
Create an extension that adds the functionality of the RevisionJumper gadget to any wiki.

Acceptance criteria:
 * Build an extension that has the same functionality as RevisionJumper
 * The extension should be localizable to any language
 * Improve the text of the select list options (use NaN undefineds switch instead of "revision(s)", make "prompt revision(s)" more clear, etc.)

This task does not include deploying the extension to any wikis. That should be filed as separate tasks afterwards based on the local consensus of specific wikis (talk to Community Liaisons to handle this part).


 * Documentation
 * Gadget code

Analysis

 * Support: Medium
 * Feasibility: Good
 * Impact: Medium/High (will make the feature available on any wiki)
 * Risk: Medium (will communities want to enable this by default? via a preference? not at all?)

Priority: Normal

Fix HotCat/VE bug
Steps to reproduce:

1. Enable HotCat. 2. Edit the page (any page containing categories) in VisualEditor. 3. Save the page. 4. Scroll to the bottom and notice that HotCat's buttons are missing.

Workaround: Re-load the page.


 * HotCat documentation

Analysis

 * Support: Medium/Low
 * Feasibility: Medium
 * Impact: Low (users can always reload the page to work around the bug)
 * Risk: Medium (anything involving VisualEditor has some risk involved)

Priority: Low

Create documentation for Quick Intersection tool
Per T108637, we should create some on-wiki documentation for the Quick Intersection tool.

Specifically, it would be good to explain the differences between Quick Intersection and CatScan on pages that already talk about CatScan.

Analysis

 * Support: Medium/Low
 * Feasibility: Good
 * Impact: Low
 * Risk: Low

Priority: Low

Fix or replace Citation Bot
It looks like Citation bot is currently blocked because it started blanking articles about a month ago. Let's see if we can help fix or replace it.


 * Documentation
 * Bug reports and discussion about replacing it
 * Usage instructions
 * Source code (PHP)
 * Interface

Analysis

 * Support: Very High (This was the highest ranking request on the English survey. There is also discussion on-wiki about this needing to be fixed.)
 * Feasibility: Good
 * Impact: Medium
 * Risk: Low

Priority: High

Improve FlickrFree search results
During the FlickrFree investigation, Magnus went ahead and rewrote the search code so that now it consistently returns the last 500 free-license uploads, rather than all the free-license images within the last 1000 uploads (which could be zero).

Fix thumbnail display in FlickrFree
Fixed the thumbnail display so that they are no longer squished in Chrome and Safari.

Syntax highlighter
This has been referred to the WMF Editing team, per their request.

Get Hovercards to feature parity with Navigation Pop-ups
We will be collaborating with the WMF Reading team on this one.

Add page view statistics to page information pages (action=info)
Referred to Analytics Engineering team.

Cite4Wiki
This is a Firefox add-on. Unfortunately, no one on our team is familiar with Firefox add-on development so we feel that our efforts would be better directed towards other tools.