Closed Bug 859875 Opened 11 years ago Closed 11 years ago

Email page watching notifications

Categories

(developer.mozilla.org Graveyard :: General, defect, P2)

All
Other
defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: openjck, Unassigned)

References

Details

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

What problems would this solve?
===============================
We currently have no page watching features. This makes certain work, like catching and correcting vandalism, very difficult.

This feature would be a temporary solution -- not the robust notification system we all want, but something simple to address the vandalism problem right now.

Who would use this?
===================
For now, I imagine the primary users will be users are concerned about vandalism.

What would users see?
=====================
On the MDN itself:
The user would see a menu item labeled something like "Receive email notifications" in the "This page" menu.

The user would then receive an email whenever that page is updated. The email must include:
* A content diff
* A metadata diff (tags, page title, page name, needs_review, etc.)
* A link to the page that was changed
* A link to the page history
* A link to the user profile of the person who made the change

What would users do? What would happen as a result?
===================================================
Users would interact with the email to determine if a change is spam, and use the links provided to correct the issue if needed.

Is there anything else we should know?
======================================
This is our number one priority at the moment. Does a launch date of Friday sound reasonable?

FWIW, we have talked about using django-tidings for this:
https://github.com/erikrose/django-tidings
Priority: -- → P1
We have some traction on a rabbitmq backend for celery tasks thanks to bug 766627. django-tidings seems a bit intense, but we can probably get a SUMO dev to pair with us to implement it quickly.
By intense, do you mean too heavyweight or difficult to implement? If it's the former, I can get us set up with one of the SUMO devs.
(In reply to John Karahalis [:openjck] from comment #3)
> By intense, do you mean too heavyweight or difficult to implement? If it's
> the former, I can get us set up with one of the SUMO devs.

As can I :)

It's a full-featured library, it has some work to it.

Celery should be a blocker for this no matter what. Sending an arbitrary number of emails during the request cycle for editing is a Bad Idea™.
Commits pushed to master at https://github.com/mozilla/kuma

https://github.com/mozilla/kuma/commit/f31022bc7cf7ff08129b3eb33d4877a45e06e342
bug 859875 - watch page for email notification

add django-tidings

update/copy/refactor wiki events code from SUMO

remove notifications from apps in use

restore and move watch view tests

https://github.com/mozilla/kuma/commit/99140b70f55cfb51f475dcbeefbfec896a28bab2
Merge pull request #1036 from groovecoder/page-watch-email-859875

bug 859875 - watch page for email notification
Is there any work left on this aside from bug 766627?
Depends on: 766627
Priority: P1 → P2
Commits pushed to master at https://github.com/mozilla/kuma

https://github.com/mozilla/kuma/commit/c51ea2c5405c97411b2c9fcfaeed7c7438e87ef1
fix bug 859875 - email change notifications UI

page_watch waffle flag

https://github.com/mozilla/kuma/commit/86782e814bc348690649f359833046ef0485a240
Merge pull request #1050 from groovecoder/page-watch-email-859875

fix bug 859875 - email change notifications UI
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Product: developer.mozilla.org → developer.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.