Closed Bug 814187 Opened 13 years ago Closed 7 years ago

Add "size of change" filter to revision dashboard

Categories

(developer.mozilla.org Graveyard :: Dashboards, enhancement, P2)

enhancement

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: openjck, Unassigned)

Details

(Whiteboard: [triaged][type:feature])

A user should be able to filter the revision dashboard by the size of a change. Quoting Janet from bug 814186. > The size filter would let you set a top or bottom threshhold for > number of "words" changed, so you could look at just "big" or > "small" revisions.
What should be considered big, what should be small? Do we need character counts here?
Priority: -- → P2
Janet - how many words delineate "big" from "small" revisions?
Flags: needinfo?(jswisher)
I think we don't really know yet what "big" and "small" is. We should try with some values and see if it works. I would consider as big any change affecting more than 10 words. I think we should be conservative here: 10 new words is quite big, but 10 typo-edit throughout the document surely not. Not sure that such a simple heuristic can define big and small changes. (But better than nothing of course).
In that case, we should make it a constance config setting so we can change it live. https://github.com/mozilla/kuma/blob/master/settings.py#L941
I'm imagining a UI like: Show only revisions with [less than|greater than] [10] changes. Where the first [] is a select list, and the second [] is an edit or combo box.
Flags: needinfo?(jswisher)
Whiteboard: p=
David is looking at the revision dashboard now. Maybe he could take a look at this.
Severity: normal → enhancement
Whiteboard: [triaged][type:feature]
This would help me to see quickly where we have large contributions as I am compiling a weekly report on MDN content activities now. https://wiki.mozilla.org/MDN/Content/Weekly How complex is this to fix? Can anyone give me a hint on how to approach this one?
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
Product: developer.mozilla.org → developer.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.