Confirmed users
1,927
edits
BMO/ChangeNotificationSystem: Difference between revisions
Jump to navigation
Jump to search
BMO/ChangeNotificationSystem (view source)
Revision as of 17:47, 12 December 2014
, 12 December 2014status
No edit summary |
(status) |
||
| Line 1: | Line 1: | ||
For a more conversational introduction to the notification system, see this blog post: http://mrcote.info/blog/2014/04/04/bugzfeed-bugzilla-push-notifications/ | For a more conversational introduction to the notification system, see this blog post: http://mrcote.info/blog/2014/04/04/bugzfeed-bugzilla-push-notifications/ | ||
= Status = | |||
Bugzfeed is available via WebSockets at ws://bugzfeed.mozilla.org/. There is also an example app at http://people.mozilla.org/~mcote/bugzfeed_example/. | |||
Bugzfeed, being a relatively simple project, is currently serving its function well; there are no plans for further development at this time. | |||
= Team = | = Team = | ||
| Line 19: | Line 25: | ||
Re-implementing Bugzilla's permissions system is '''not''' an option. It is complex enough that changing the current model would be major surgery (and would further diverge BMO from upstream), and maintaining two parallel implementations would incur maintenance costs and be error prone. | Re-implementing Bugzilla's permissions system is '''not''' an option. It is complex enough that changing the current model would be major surgery (and would further diverge BMO from upstream), and maintaining two parallel implementations would incur maintenance costs and be error prone. | ||
Notifications should '''not''' include changes to dependent/related bugs. This is harder to track based on the current Bugzilla database schema, and a properly designed system should be able to track them | Notifications should '''not''' include changes to dependent/related bugs. This is harder to track based on the current Bugzilla database schema, and a properly designed system should be able to track them independently at the client's discretion. The exception here would be adding or removing dependencies, e.g. a notification will be sent for both bug X and Y if X is set to depend on Y. | ||
= Design and Approach = | = Design and Approach = | ||