Page MenuHomePhabricator

Identify high-use gadgets and ensure that they have proper long-term maintenance
Open, Needs TriagePublic


Proposed in Community-Wishlist-Survey-2016. Received 43 support votes, and ranked #29 out of 265 proposals. View full proposal with discussion and votes here.


Many gadgets start small, often as a proof of concept, but when they reach some level of popularity and high use than they need to be revisited and possibly rewritten with long-term maintenance and stability in mind. Some popular gadgets are written by people who are no longer active, or more focused on other things than maintenance of old gadgets, and if no one steps up to maintain them problems and incompatibilities accumulate. Some gadgets are copied to other projects and multiple versions diverge. Many users rely heavily on tools and gadgets to do more efficiently their tasks on Wikimedia projects and keeping the tools running is important to keep them happy and busy.

Who would benefit

Users of gadgets

Proposed solution

Identify high-use gadgets on different projects and ensure that there is a long-term plan to maintain them. That might require code rewrite to more maintainable version or conversion to extension format. Would require a link to phabricator pages where one can report errors and issues. Current approach on Commons of protected edit requests on gadget's Javascript talk pages seems quite dangerous. For example on Commons, I suspect we should look more closely at HotCat, Cat-a-lot, VisualFileChange and ImageAnnotator. I am sure Wikipedia might have other popular gadgets.

Proposed implementation: I envision a site on Tool Labs that hosts a mostly-JS AWB that does editing. The backend would only authenticate users (OAuth), store settings and editing lists, and collect statistics. Most of JS code can be made reusable in Node.js for use by fully-automated bot developers.

Technical details

Time, expertise and skills required

  • e.g. 2-3 weeks, advanced contributor, javascript, css, etc

Suitable for

  • e.g. Hackathon, GSOC, Outreachy, etc.



Related links

Event Timeline

This task was proposed in the Community-Wishlist-Survey-2016 and in its current state needs owner. Wikimedia is participating in Google Summer of Code 2017 and Outreachy Round 14. To the subscribers -- would this task or a portion of it be a good fit for either of these programs? If so, would you be willing to help mentor this project? Remember, each outreach project requires a minimum of one primary mentor, and co-mentor.