Closed
Bug 1169673
Opened 10 years ago
Closed 10 years ago
Add RSS feed for article revisions
Categories
(developer.mozilla.org Graveyard :: General, enhancement)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: sheppy, Unassigned)
Details
(Keywords: in-triage, Whiteboard: [specification][type:feature][LOE:5])
What problem would this feature solve?
======================================
We used to have a badly broken "revisions" RSS feed, which listed all articles which have changed recently, including in the body of each entry details about what changed (tags, review flags, content diff, etc).
The old feed was removed because the code behind it was running amok and obliterating site performance.
We need to build this feature again, from the ground up, so that it works and is regularly available for use. We have users whose preferred workflow is to see as much as possible in their feed reader so they can do all their work in one place (I admit to being one of these people).
Who has this problem?
=====================
All contributors to MDN
How do you know that the users identified above have this problem?
==================================================================
Not having this feed is a problem because without it, I'm using hacked up methods for tracking work that needs to be done. We have gotten occasional complaints about the broken RSS feeds, so I'm pretty sure this would be used if it existed and worked well.
How are the users identified above solving this problem now?
============================================================
Revision dashboard, although this is an active rather than passive mechanism for watching for changes.
Do you have any suggestions for solving the problem? Please explain in detail.
==============================================================================
Nope. It seems straightforward from my end, but I'm sure it's not. :)
Is there anything else we should know?
======================================
Comment 2•10 years ago
|
||
I'd say LOE:5 days because we could probably fix the existing feed code. E.g., the RevisionsFeed.item_description includes a call to Revision.get_previous() which makes a SELECT query for all 50 items in the feed. We could fix the Revision QuerySet to pre-fetch corresponding previous revisions.
Flags: needinfo?(lcrouch)
Whiteboard: [specification][type:feature] → [specification][type:feature][LOE:5]
| Reporter | ||
Comment 3•10 years ago
|
||
If we think we can fix the existing code, then that's probably a smart move. We had known problems with the existing code where some changes were getting reported repeatedly, sometimes for weeks, though. I don't know if we know what would solve that.
Comment 4•10 years ago
|
||
Commits pushed to master at https://github.com/mozilla/kuma
https://github.com/mozilla/kuma/commit/6f00e233bfd32277a8674d4c019e68be36381eee
Bug 1169673 - Lower complexity of db queries in RevisionFeed.
https://github.com/mozilla/kuma/commit/4a6312ae950d75d28deeb4ad7231d332c1617d8a
Merge pull request #3245 from mozilla/bug1169673
Bug 1169673 - Lower complexity of db queries in RevisionFeed.
Comment 5•10 years ago
|
||
Commit pushed to master at https://github.com/mozilla/kuma
https://github.com/mozilla/kuma/commit/b5726a1edefbc4266ae4d9b089ea3eb1abd19022
Merge pull request #3263 from jezdez/bug1169673-regression
Fix bug 1174820 - Revert the get_previous changes made in bug #1169673.
Comment 6•10 years ago
|
||
See bug 1167231 for the reason why this has fixed this ticket.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Comment 7•10 years ago
|
||
Commits pushed to master at https://github.com/mozilla/kuma
https://github.com/mozilla/kuma/commit/059b3d5800ab0bcf89236f96068c2a43bb209aa5
Bug 1169673 - Lower complexity for DocumentsFeed feeds.
https://github.com/mozilla/kuma/commit/d38df567b05ed93ff93279150c37db6ead8456f3
Merge pull request #3296 from mozilla/bug1169673-2
Bug 1169673 - Lower complexity for DocumentsFeed feeds.
Updated•5 years ago
|
Product: developer.mozilla.org → developer.mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•