MDN/Projects/Development/On-Site Messaging: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
Line 2: Line 2:
* Increase participation and collaboration by enabling direct, private communication among MDN users.
* Increase participation and collaboration by enabling direct, private communication among MDN users.
* '''This is essential if we are going to meet our goal of 1,000 contributors per month before the end of Q4. Without having this feature in place with enough time for it to gain traction before the end of the year, this goal will be missed.'''
* '''This is essential if we are going to meet our goal of 1,000 contributors per month before the end of Q4. Without having this feature in place with enough time for it to gain traction before the end of the year, this goal will be missed.'''
* I put in <strong> the use cases that are important of l10n and topic driver roles.
* I put in bold use cases that are important of l10n and topic driver roles.


See SUMO's private messaging feature for an example of how this functionality might be implemented.
See SUMO's private messaging feature for an example of how this functionality might be implemented.

Revision as of 11:44, 30 June 2014

Goal

  • Increase participation and collaboration by enabling direct, private communication among MDN users.
  • This is essential if we are going to meet our goal of 1,000 contributors per month before the end of Q4. Without having this feature in place with enough time for it to gain traction before the end of the year, this goal will be missed.
  • I put in bold use cases that are important of l10n and topic driver roles.

See SUMO's private messaging feature for an example of how this functionality might be implemented.

Also see the Social features page for related features that may affect design decisions, etc.

User stories

MDN User

  • I want to send a message to another user who has given permission to receive messages.
  • I want other MDN users to be able to send me messages without exposing my email address on the Web.
  • I want to control whether other users can send me messages.
  • I want to control how I am notified about messages I receive (desktop notifications, email, on-MDN-boxes, twitter, etc).
  • I want to report and block a sender.
  • I want to reply to messages.
  • I want to archive, retrieve, and delete messages.
  • I want to send a review request to people who have expressed willingness to review articles about the topic my article is about, or (for editorial reviews) to people who have expressed willingness to do that.
  • I want to be able to report users who message me inappropriately.
  • I want to be able to send a message to all users working in the same topic.
  • I want to be able to send a message to all topic/l10n drivers for a given topic/locale.
  • I want to be able to send a message to all MDN admins.

MDN Localization or Topic Drivers

  • I want to send messages to all members of my topic or locale "team".
  • I want to send messages to all other l10n/topic drivers.
  • I want members of my team to be able to message one another (or all team members) easily, to encourage my team to work together.
  • I want to subscribe to automatic summary messages about the l10n/topic I drive, so I don't have to click dozens of things all over the site to find this mission-critical information
    • Digests of changes made
    • Lists of pages with errors
    • Lists of pages flagged for reviews or for translation work
    • Etc.

MDN Admin

  • I want to receive reports of abusive messaging behavior by users.
  • I want to appropriately handle reports about abusive messaging behavior by users. (Need to create a policy on how abuse will be handled. E.g., banning for obvious spam; otherwise, 3 strikes and you're out.)
  • I want to view messages that have been reported as abusive, so that I can take appropriate action on the sender.
  • I want to view messages sent to all topic members/l10n members/topic drivers/l10n drivers: we act as default l10n/topic drivers, inheriting all their capabilities.
  • I want to be able to create messages that are sent to all users (to announce downtime, major feature updates, surveys, etc).
  • (Maybe) I want to view any message as needed to maintain site performance and integrity (i.e., investigate suspicious activity).

Implementation Thoughts

  • On-site notification of new messages
  • On-site reading of messages
  • On-site replying to and deletion of messages.
  • Support for "email gateway", where messages can be read and replied to using standard emails (like a mailing list).