Support/Notifications

< Support

Contents

Goals

  • Ref integ of email addresses
  • More customizable scoping

Use cases

Trigger a notification

  1. Notify anytime any Document changes.
  2. Notify anytime a Document in a certain locale changes.
  3. Notify when a particular Document changes.
  4. Delete an object and make its watches go away.
  5. New articles or changes to Documents that are untranslated into de and that are localizable and that are approved.
  6. Notify when an approval happens in German.
  7. Major edits to Documents in English
  8. Major edits to Documents
  9. Any activity tagged with "blue"
  10. Anything Fred does
  11. Tell what the user is subscribed to
  12. Notify any new thread in a given discussion forum
  13. Notify any post (new thread or reply) in a given discussion forum
  14. Notify any post in a discussion thread
  15. Notify any new thread in any KB forum in a given locale
  16. Notify any post in any KB forum in a given locale
  17. Notify any new thread in a given KB forum
  18. Notify any post in a given KB forum
  19. Notify any post in a given KB forum thread
  20. Notify on new question (confirmed)
  21. Notify on new answer to a given question
  22. Notify on answer marked as solution to a given question
  23. Notify on new flagged item for review

Deliver notification

Logged in user

(non-exclusive)

  • To email
  • To private message
  • (Future, other options?)

Anonymous user

  • To email

If a user registers, we should look for any anonymous watches with that email address and add them to the user, when the user is confirmed.

Schedule

A strawman schedule—when to target having things up for review:

  • 1/24: fire() offthreading (up for review)
  • 1/26: object_id moving; de-duplication
  • 1/28: templating; confirmation views
  • 2/1: claiming; porting old client code & deleting old subsystem code (which go together)
  • 2/4: migrating old watches

That should be possible with 2 people on it; we have between 3 and 4. Have fun!