Last modified: 2014-11-20 09:22:49 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 32281 - MediaWiki needs a sane notification system (tracking)
MediaWiki needs a sane notification system (tracking)
Status: NEW
Product: MediaWiki
Classification: Unclassified
Interface (Other open bugs)
unspecified
All All
: Normal enhancement with 3 votes (vote)
: ---
Assigned To: Nobody - You can work on this!
https://www.mediawiki.org/wiki/Reques...
: tracking
Depends on: 32283 32284 32285 32287 32288 39513
Blocks: tracking 3234 9838 19248 20541 29856 29857 30750 11636 27829
  Show dependency treegraph
 
Reported: 2011-11-08 20:58 UTC by Brandon Harris
Modified: 2014-11-20 09:22 UTC (History)
13 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Brandon Harris 2011-11-08 20:58:31 UTC
This is intended as a Master Bug.

MediaWiki's notification system is pretty prehistoric.  It's time to enter the current decade.
Comment 1 Brion Vibber 2011-11-08 22:06:02 UTC
Starting to put more details together on an RFC page: <https://www.mediawiki.org/wiki/Requests_for_comment/Notification_framework>
Comment 2 Mark A. Hershberger 2011-11-10 17:53:02 UTC
I'd love to do this for the next major deployment.
Comment 3 Siebrand Mazeland 2012-01-23 13:40:21 UTC
Untagging this as a 1.19 release blocker. No work has gone into this feature, and it cannot go in anymore.
Comment 4 Tyler Romeo 2012-06-18 16:54:21 UTC
https://bugzilla.wikimedia.org/show_bug.cgi?id=9838

The fix for this bug is very much related to this.
Comment 5 MZMcBride 2012-06-19 20:24:41 UTC
(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
Comment 6 Ryan Kaldari 2013-01-11 00:47:14 UTC
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.
Comment 7 MZMcBride 2013-01-11 04:22:17 UTC
(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. :-)
Comment 8 Andre Klapper 2014-03-11 14:26:53 UTC
(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?
Comment 9 Nemo 2014-03-11 14:42:03 UTC
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.
Comment 10 Ryan Kaldari 2014-03-11 17:42:22 UTC
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.
Comment 11 Quim Gil 2014-03-12 14:20:44 UTC
(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.
Comment 12 Andre Klapper 2014-08-17 10:16:18 UTC
(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.
Comment 13 Andre Klapper 2014-11-07 14:05:42 UTC
Echo team: Could you answer comment 11 please?

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links