Last modified: 2011-01-25 01:15:58 UTC
Having good native support would help with various issues such as cleaning up image redirects (see fight on bug 15842 about this :)
Support for foreign APIs would be hot.
Tougher, though. We'd need to implement some sort of 'subscription' API that foreign sites could use to request updates -- that's a totally separate issue and should be broken out to its own bug.
From what I recall there is a certain brokenness in the population script. Don't remember exactly, but I don't think it will work out of box.
Not ready for shell, AFAICT.
The recent toolserver outages have really underscored how overdependent on the toolserver Commons has become: with the toolserver down, Commons admins are all but reduced to twiddling their thumbs. This extension would help a lot. Bryan: What's the current status of this extension? Is it ready to deploy, and if not, what's missing?
Requires: * Testing whether actually still works on the current trunk * Code review * Architecture review. I haven't looked in it recently, but I think there are some things that I would have done differently now. * UI design I will see if I can poke around a bit soon.
I think it is ready for review.
This has been enabled on WMF wikis. Still has some unresolved issues, though.
GlobalUsage has been disabled due to "major scaling issues."[1] [1] http://wikitech.wikimedia.org/index.php?title=Server_admin_log&diff=23608&oldid=23607&diffonly=1
GlobalUsage seems to be running more or less stably now. I think this bug can be closed, right?