Last modified: 2014-09-09 04:03:12 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T22541, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 20541 - Watchlist, LiquidThreads and Echo notifications need to be unified
Watchlist, LiquidThreads and Echo notifications need to be unified
Status: NEW
Product: MediaWiki extensions
Classification: Unclassified
LiquidThreads (Other open bugs)
unspecified
All All
: Normal enhancement with 5 votes (vote)
: ---
Assigned To: Nobody - You can work on this!
:
: 41972 (view as bug list)
Depends on: 21732 32281 41808
Blocks:
  Show dependency treegraph
 
Reported: 2009-09-08 10:08 UTC by Andrew Garrett
Modified: 2014-09-09 04:03 UTC (History)
10 users (show)

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


Attachments

Description Andrew Garrett 2009-09-08 10:08:38 UTC
Need to stick them in the same place so as not to confuse people.

Watchlist in general needs a rethink, but that's for another bug.
Comment 1 Brandon Harris 2010-09-10 01:51:19 UTC
Design. Taking. (I'm typing that a lot today.)
Comment 2 Helder 2012-08-05 20:56:48 UTC
Now, mediawiki.org shows
---------------------------------------------------------------
... [My watchlist] [My notifications] [My new messages (N)] ...
---------------------------------------------------------------
on top of all pages when I am logged in.
Comment 3 Ryan Kaldari 2012-11-06 23:50:08 UTC
We (me, Benny, Fabrice, Howie, Vibha, and Oliver) discussed this issue a lot over the past few weeks (while Brandon was in Hawaii). After much debate, we haven't solved the fundamental problems, but we did reach one important decision:
For now, we are not going to have any watchlist-type notifications in Echo (notifications about simple edits), with the exception of User talk page edits. Echo will only be used for high-importance/low-velocity type notifications, while low-importance/high-velocity information will still be handled in the watchlist. We may, however, turn on more of the watchlist preferences for new users so that they are more likely to be informed of edits related to their work. At some point, we will need to revisit this, and figure out how to better integrate Echo and the Watchlist. Echo + LQT is still an unsolved issues though (as are some aspects of Echo + Talk).
Comment 4 Andre Klapper 2013-01-09 13:24:55 UTC
Brandon:
This report has been in ASSIGNED status for more than one year and you are set as its assignee. In case that you are not actively working on a fix, please reset the bug status to NEW/UNCONFIRMED.
In case you do not plan to work on a fix in the near future: Please also edit the "Assigned To" field by clicking "Reset Assignee to default", in order to not prevent potential contributors from working on a fix. Thanks for your help!
[assigned>=1y]
Comment 5 Ryan Kaldari 2013-01-09 18:13:13 UTC
Andre: Well, the fix for this bug is replacing LQT with Flow, which Brandon is designing. That fix won't happen for a year or so though. This is one case where I would actually argue that 'LATER' is the correct resolution, although we don't have that option any more.
Comment 6 Quim Gil 2013-03-21 05:37:27 UTC
*** Bug 41972 has been marked as a duplicate of this bug. ***
Comment 7 Quim Gil 2014-01-13 05:31:24 UTC
(In reply to comment #5)
> Andre: Well, the fix for this bug is replacing LQT with Flow, which Brandon
> is
> designing. That fix won't happen for a year or so though. This is one case
> where I would actually argue that 'LATER' is the correct resolution, although
> we don't have that option any more.

Pong! Now Flow starts to exist, and its notifications are indeed integrated to Echo.

As Kaldari explained in comment 3, Watchlist has still its own channel of notifications (by design), while LiquidThreads is on a clear way of deprecation at least in the Wikimedia context.

I wonder whether anything else is expected to happen in order to resolve this report in a way or another.

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


Navigation
Links