On Tue, Aug 25, 2015 at 6:29 PM, Platonides
<platonides(a)gmail.com> wrote:
Welcome, CT!
Romaine Wiki wrote:
Another subject that recently came up is the
subject of continuity. One
of the largest announces I notice is that users see that software is no
longer maintained, but still like to use it, are getting very annoyed.
This is not an issue that is incidental, it is a structural problem.
+1 I think orphaned gadgets maintenance will/should be an important task
for this team. There many gadgets created a long time ago, that were
maintained and improved for years but now are orphaned with lots of
editors
still using them. Editors that are unhappy each time they break (api
changes, document.write bans, sajax being gone, and most recently that
they
must use ResourceLoader to continue working…).
We're actually collecting reports of broken gadgets on Phabricator
currently and trying to fix them as we have time:
https://phabricator.wikimedia.org/T108282. Normally we will only be working
on tasks that are submitted through some sort of formal process (see
https://www.mediawiki.org/wiki/Community_Tech_team#Work_input_and_prioritiz…),
as we don't have the capacity to field random requests from all the
communities. The huge number of gadgets that have broken recently (due to
various core MediaWiki changes) is something of a crisis though and we want
to help get them back up and running. TheDJ (who is not on our team) has
also been helping with gadget fixes. There are a lot of gadgets out there,
so any additional help (or bug reports) are welcome.
This seems kind of backwards. A bunch of changes were made, things
exploded, and now Community tech is going to try to desperately fix
them.
Maybe this is a sign we need to re-evaluate how we do client-side deprecations.
--
-bawolff