Closed Bug 842620 Opened 11 years ago Closed 11 years ago

Add KB revisions feature

Categories

(support.mozilla.org :: Knowledge Base Software, task, P3)

Tracking

(Not tracked)

RESOLVED FIXED
2013Q1

People

(Reporter: atopal, Assigned: mythmon)

Details

(Whiteboard: u=contributor c=wiki p=3 s=2013.6)

We researched adding an MDN like KB revisions feature in bug 823891

Since the effort seems reasonable and demand is there, we should go ahead and build it.
Priority: -- → P3
Whiteboard: u=contributor c=wiki p= s=2013.4 → u=contributor c=wiki p=3 s=2013.4
Carrying over the comment from bug #823891:

"""
I skimmed their code and I think this is pretty straight-forward. The page consists of a view that loads the html/javascript which then does an AJAX call to the same view for the data. Then it periodically updates the data.

The data is retrieved via Django ORM queryset stuff--there's absolutely nothing fancy going on caching-wise or otherwise. The filters are straight-forward.

Our Revision class has the fields we'd need to filter against.

Setting up the view code should be pretty easy. I think the bulk of the work here is going to be doing the html/javascript side of things. I think this is at least a 2 pointer. It's possible I'm underestimating the html/javascript work required which would make this a 3 pointer.
"""

Hedging towards a 3 pointer because there are differences between the MDN Revision model and the SUMO Revision model that we probably need to account for and I don't know enough about the html/js side to estimate that with more accuracy.
Failing to next sprint since 2013.4 is full.
Whiteboard: u=contributor c=wiki p=3 s=2013.4 → u=contributor c=wiki p=3 s=2013.5
Failing to next sprint since 2013.5 is full.
Whiteboard: u=contributor c=wiki p=3 s=2013.5 → u=contributor c=wiki p=3 s=2013.6
I'm going to work on this one.
Assignee: nobody → mcooper
Landed: https://github.com/mozilla/kitsune/cfd1c3b788d3f902be2415c5c8109d7c348efd86

Deployed to prod just now.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.