Last modified: 2013-05-02 20:01:34 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T31831, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 29831 - Enable Extension:Usage Statistics on Hindi Wikipedia
Enable Extension:Usage Statistics on Hindi Wikipedia
Status: RESOLVED WONTFIX
Product: Wikimedia
Classification: Unclassified
Extension setup (Other open bugs)
unspecified
All All
: Unprioritized enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
: patch-need-review
Depends on:
Blocks: 29823
  Show dependency treegraph
 
Reported: 2011-07-12 11:49 UTC by Vaibhav Jain
Modified: 2013-05-02 20:01 UTC (History)
6 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Vaibhav Jain 2011-07-12 11:49:59 UTC
Please enable Extension:Usage Statistics on Hindi Wikipedia. The local consensus is here:
http://hi.wikipedia.org/wiki/विकिपीडिया:New_Extension
Comment 1 Chad H. 2011-07-12 19:20:32 UTC
Just from a quick glance, this extension would need some *major* cleanup to be considered for deployment to WMF sites. It's not in good shape at all.
Comment 2 Brion Vibber 2011-07-13 01:02:27 UTC
'Local consensus' link leads to a nonexistent page.

Assuming the extension is this: http://www.mediawiki.org/wiki/Extension:UsageStatistics

While it looks like it might be able to make some neat graphs, performance is obviously a concern; it's unlikely that we'd deploy something like this without a way to make sure it can always run very efficiently even on the largest/most active sites/pages/users.

It's unlikely we'd turn something like this on on a wiki-by-wiki basis either; it should either go in or not.

* extension needs overall cleanup & overhaul
* the actual DB queries look fairly likely to explode on large data sets -- it may read a row for *every edit you've ever made* and doesn't even try to limit to a sane number; very slow queries or running out of memory are possible
* needs to use rev_user instead of rev_user_text when possible (renaming inconsistencies)
* gnuplot usage would need a security audit etc probably -- or replace with something else (not google charts, we'd want to avoid using an external service)
* split JavaScript libraries out of the PHP files!

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links