Notifications/Sorting schemes/en

The overall task is: Deciding how to sort the notification-types (e.g. "new usertalkpage message", "your edit was reverted", "a page you created has been linked to", "thanks", etc) into 2 groups. The current sorting has some problems. There are 2 more logical alternatives which the team is trying to decide between, and wants your feedback on (your preferences, or concerns). The recommendation is we start off with the "By urgency" grouping.

Please share your feedback at the Phabricator task or here on MediaWiki.org.

Problem to solve
There are currently two Notification fly-out menus, one for Alerts and one for Messages. Different notification types show up on different menus. There have been criticism over time that the scheme for dividing up the messages is unclear and/or inconsistent. These criticisms include the following:
 * Ideas of "urgency" and "requiring follow up" are mixed together, making it difficult to explain or predict why different items are in each fly-out.
 * Currently, "Alert" items are automatically "marked as read" on opening the fly-out. Yet some of these require follow-up or other action to be fully understood (e.g., Mention), so this feature's value is not always clear.
 * Because "Alerts" are perceived as "Urgent", the "Thanks" and other items seem out of place in that fly-out.

Goals

 * To create a scheme that is easy to understand, learn, and predict.
 * To give editors clearer information about their new notifications.
 * To reduce unnecessary distraction from non-urgent notifications.
 * Something that works well for editors who get large (and small) quantities of notifications.
 * Something that scales well, as new (requested) notification types are created.
 * Something that scales well, once cross-wiki notifications are available.

Types
See examples of the most common notification types at File:Notifications Catalog.png.

Options
(This version has minimal styling, and just shows the most common notification-types. See a more detailed version here at googledocs which includes a 4th (more complicated) alternative.)