Last modified: 2014-11-17 10:36:26 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 T43329, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 41329 - Add edit history graph(s) to MediaWiki's info action
Add edit history graph(s) to MediaWiki's info action
Status: NEW
Product: MediaWiki extensions
Classification: Unclassified
Extensions requests (Other open bugs)
master
All All
: Lowest enhancement with 1 vote (vote)
: ---
Assigned To: Nobody - You can work on this!
: analytics
Depends on: 43666
Blocks: 38450 41326
  Show dependency treegraph
 
Reported: 2012-10-23 21:29 UTC by MZMcBride
Modified: 2014-11-17 10:36 UTC (History)
5 users (show)

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


Attachments

Description MZMcBride 2012-10-23 21:29:26 UTC
It would be nice to have a graph/graphs of edits over time in MediaWiki's info action.
Comment 1 Antoine "hashar" Musso (WMF) 2012-10-23 21:33:18 UTC
Zak Greant wrote a Greasemonkey script "MediaWiki history Sparklines" which we might want to integrate:

http://userscripts.org/scripts/show/79234

That would be a nice experiment, can most probably be implemented as a Gadget too.
Comment 2 MZMcBride 2012-10-23 21:54:22 UTC
(In reply to comment #1)
> Zak Greant wrote a Greasemonkey script "MediaWiki history Sparklines" which we
> might want to integrate:
> 
> http://userscripts.org/scripts/show/79234

Neat!

> That would be a nice experiment, can most probably be implemented as a Gadget
> too.

Hmm, maybe. The nice thing here is that we have all of the data already (edit timestamp, page title) and it's indexed. The not-so-nice thing here is that the edge cases are a bit rough. Some pages have over 600,000 revisions.

Zak's user script is hitting the API. For small pages, this is fine. For large pages, this is probably impractical. If this feature were implemented as an extension, it could do direct queries on the database to get the underlying data and/or use a cache store/database table for larger pages.
Comment 3 Tyler Romeo 2012-11-03 04:23:26 UTC
https://gerrit.wikimedia.org/r/31603

Just a draft. If anybody can come up with a better way to draw graphs other than a jQuery extension, please do. I figured a JavaScript dependency would be easier to manage than a PHP dependency.

Also, it should be noted this is a bit of a draft. There is some polishing that can be done to make the graph look better.
Comment 4 Nemo 2013-01-11 19:17:09 UTC
-easy: given the discussion on commit doesn't seem so at all.
Comment 5 Andre Klapper 2013-03-07 16:11:36 UTC
Wondering whether to move this to Extension requests too, as per dependency on bug 43666?
Comment 6 Quiddity 2014-09-26 00:20:05 UTC
Patch abandoned in April 2013, resetting to New.

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


Navigation
Links