Last modified: 2014-11-20 09:22:49 UTC
This is intended as a Master Bug. MediaWiki's notification system is pretty prehistoric. It's time to enter the current decade.
Starting to put more details together on an RFC page: <https://www.mediawiki.org/wiki/Requests_for_comment/Notification_framework>
I'd love to do this for the next major deployment.
Untagging this as a 1.19 release blocker. No work has gone into this feature, and it cannot go in anymore.
https://bugzilla.wikimedia.org/show_bug.cgi?id=9838 The fix for this bug is very much related to this.
(In reply to comment #1) > Starting to put more details together on an RFC page: > <https://www.mediawiki.org/wiki/Requests_for_comment/Notification_framework> https://www.mediawiki.org/wiki/Echo_%28Notifications%29
Now that Echo exists, would anyone object to me closing this bug and reassigning the dependencies to Echo? Otherwise, they are unlikely to be incorporated into current Echo development.
(In reply to comment #6) > Now that Echo exists, would anyone object to me closing this bug and > reassigning the dependencies to Echo? Otherwise, they are unlikely to be > incorporated into current Echo development. Sounds good to me. Tracking bugs are only as useful as the people working on the project say they are. If tracking bugs aren't the Echo team's style, feel free to close. :-)
(In reply to Ryan Kaldari from comment #6) > Now that Echo exists, would anyone object to me closing this bug and > reassigning the dependencies to Echo? Otherwise, they are unlikely to be > incorporated into current Echo development. Ryan: Willing to go ahead?
AFAIK Echo is in maintenance mode (it was already when it started being enabled on wikis other than en.wiki), in other words no big development is going to happen there. Considering that most blockers of this bug appear to be related to stuff that is not en.wiki/desktop (like apps, mobile and LQT) and that we don't even see work on talk page bar for unregistered users... I think core is the only place where we're likely to see some work, withing 5-10 years.
Most of these bugs are clearly Echo related, but are unlikely to ever be noticed by Echo developers unless they are targeted to the extension. If we want to keep a tracking bug for non-Echo notification bugs (as there are a small number), we should change the title of this bug. While I agree that the WMF isn't going to do any major development to Echo any time soon, if most of these bugs are ever going to be addressed, they will be addressed in Echo.
(In reply to Ryan Kaldari from comment #10) > if most of these bugs are ever going to be addressed, they will be > addressed in Echo. It would be good to know also the opinion of the Echo developers in terms of their priority over those reports (and all the Echo related reports, actually). Normal, Low, Lowest? Collateral comment: I was discussing with Andre the idea of organizing a Bug Day again. Maybe we could focus on triaging Echo-related reports, and perhaps the developers could even get 1-2 days of "liberated time"? An Echo sprint.
(In reply to Quim Gil from comment #11) > (In reply to Ryan Kaldari from comment #10) > > if most of these bugs are ever going to be addressed, they will be > > addressed in Echo. > > It would be good to know also the opinion of the Echo developers in terms of > their priority over those reports (and all the Echo related reports, > actually). Normal, Low, Lowest? Reply by Echo team welcome.
Echo team: Could you answer comment 11 please?
