Change Details

Proposed in #community-wishlist-survey-2016. Received 43 support votes, and ranked #29 out of 265 proposals. [[ https://meta.wikimedia.org/wiki/2016_Community_Wishlist_Survey/Categories/Bots_and_gadgets#Identify_high-use_gadgets_and_ensure_that_they_have_proper_long-term_maintenance|View full proposal with discussion and votes here.]] === Problem === 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 [[ https://commons.wikimedia.org/wiki/Category:Commons_protected_edit_requests | protected edit requests ]] on gadget's Javascript talk pages seems quite dangerous. For example on Commons, I suspect we should look more closely at [[ https://commons.wikimedia.org/wiki/Help:Gadget-HotCat | HotCat ]], [[ https://commons.wikimedia.org/wiki/Help:Gadget-Cat-a-lot | Cat-a-lot ]], [[ https://commons.wikimedia.org/wiki/Help:VisualFileChange.js | VisualFileChange ]] and [[ https://commons.wikimedia.org/wiki/Help:Gadget-ImageAnnotator | 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. === Proposer === [[ https://meta.wikimedia.org/wiki/User:Jarekt | Jarekt ]] === Related links === - https://phabricator.wikimedia.org/T108630 - https://phabricator.wikimedia.org/T121470 - https://phabricator.wikimedia.org/T87730 - https://phabricator.wikimedia.org/T151056

Proposed in #community-wishlist-survey-2016. Received 43 support votes, and ranked #29 out of 265 proposals. [[ https://meta.wikimedia.org/wiki/2016_Community_Wishlist_Survey/Categories/Bots_and_gadgets#Identify_high-use_gadgets_and_ensure_that_they_have_proper_long-term_maintenance|View full proposal with discussion and votes here.]] === Problem === 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 [[ https://commons.wikimedia.org/wiki/Category:Commons_protected_edit_requests | protected edit requests ]] on gadget's Javascript talk pages seems quite dangerous. For example on Commons, I suspect we should look more closely at [[ https://commons.wikimedia.org/wiki/Help:Gadget-HotCat | HotCat ]], [[ https://commons.wikimedia.org/wiki/Help:Gadget-Cat-a-lot | Cat-a-lot ]], [[ https://commons.wikimedia.org/wiki/Help:VisualFileChange.js | VisualFileChange ]] and [[ https://commons.wikimedia.org/wiki/Help:Gadget-ImageAnnotator | 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. === Proposer === [[ https://meta.wikimedia.org/wiki/User:Jarekt | Jarekt ]] === Related links === - {T108630} - {T121470} - {T87730} - {T151056}

Proposed in #community-wishlist-survey-2016. Received 43 support votes, and ranked #29 out of 265 proposals. [[ https://meta.wikimedia.org/wiki/2016_Community_Wishlist_Survey/Categories/Bots_and_gadgets#Identify_high-use_gadgets_and_ensure_that_they_have_proper_long-term_maintenance|View full proposal with discussion and votes here.]] === Problem === 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 [[ https://commons.wikimedia.org/wiki/Category:Commons_protected_edit_requests | protected edit requests ]] on gadget's Javascript talk pages seems quite dangerous. For example on Commons, I suspect we should look more closely at [[ https://commons.wikimedia.org/wiki/Help:Gadget-HotCat | HotCat ]], [[ https://commons.wikimedia.org/wiki/Help:Gadget-Cat-a-lot | Cat-a-lot ]], [[ https://commons.wikimedia.org/wiki/Help:VisualFileChange.js | VisualFileChange ]] and [[ https://commons.wikimedia.org/wiki/Help:Gadget-ImageAnnotator | 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. === Proposer === [[ https://meta.wikimedia.org/wiki/User:Jarekt | Jarekt ]] === Related links === - https://phabricator.wikimedia.org/- {T108630} - https://phabricator.wikimedia.org/- {T121470} - https://phabricator.wikimedia.org/- {T87730} - https://phabricator.wikimedia.org/- {T151056}