Notifications/Sorting schemes/zh

总而言之，任务是决定不同类型的通知如何排序. 比如将新用户讨论页消息、编辑被回退以及有链接至用户创建页面的页面被创建进入两组. 目前的排序有一些问题.

之前曾有两个建议. 在获得部分反馈后，我们决定只保留一个备选方案作为当前方案（2016年4月）. 团队需要您对它的反馈（您的偏好或关注点）. 一种比较推荐的做法是我们从紧急程度进行分组（示例）.

请在Phabricator task或MediaWiki.org分享您的反馈.

需要解决的问题
目前有两种通知的浮动菜单，一种用于提醒，一种用于消息. 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. 批评主要有：
 * Ideas of "urgency" and "requiring follow up" are mixed together, making it difficult to explain or predict why different items are in each flyout.
 * 目前，在打开弹出菜单时，“提醒”项目会自动“标记为已读”. 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 flyout.

目標

 * 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.

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

选项
(This table has no annotations, and just shows the most common notification-types. See a more detailed version here at googledocs which also includes a 3rd and 4th (more complicated) alternative.)
 * 目前
 * 1) 紧急通知与非紧急通知相对
 * 2) （曾经提出但现已放弃）需要跟踪与不需要跟踪相对（是否需要回复或类似操作）