Confirmed users, Bureaucrats and Sysops emeriti
1,057
edits
MDN/Projects/Development/On-Site Messaging: Difference between revisions
MDN/Projects/Development/On-Site Messaging (view source)
Revision as of 03:55, 16 August 2014
, 16 August 2014→Implementation Thoughts
| (4 intermediate revisions by one other user not shown) | |||
| Line 1: | Line 1: | ||
=Goal= | =Goal= | ||
* Increase participation and collaboration | * 1,000 contributors on MDN per month | ||
* | * Project goal: Increase participation and collaboration between contributors, leading to better retention of volunteers on MDN | ||
* | * Metric: # of contributors per month, % growth increases after messaging is launched | ||
* Metric: # of messages sent per month, messaging growth over time as correlates to contribution | |||
* Metric: % of contributors who continue editing after their first edit (over 3,6,12 months) | |||
On-site messaging (direct, private communication among MDN users) will increase contribution and retention of contributors in several ways: | |||
*Increased engagement with newer users, encouraging them to continue to participate without having to install IRC clients or subscribe to mailing lists, as well as make sure they can find things to work on and are not facing obstacles to contributing | |||
*Contributors can form teams to collaborate on projects or articles | |||
*Leads of various areas can message others working on their topics or localization areas to help organize work, ask for help, etc. | |||
* l10n drivers can't contact editors who have left partially translated articles and work with them to get the articles completed. | |||
*Connect volunteer with others in their community (be that local, language-based, or topic) | |||
*Contributors can ask for reviews and feedback from peers, or volunteer to review or edit | |||
*Provides a secure way to interact on MDN without needing to expose your personal email address on the web. | |||
*Additional incentive to register, gaining access to other MDN services (profile, badges, etc.) | |||
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. | ||
| Line 9: | Line 21: | ||
=User stories= | =User stories= | ||
* Bold use cases are important to l10n and topic driver roles. | |||
==MDN User== | ==MDN User== | ||
* I want to send a message to another user who has given permission to receive messages. | * I want to send a message to another user who has given permission to receive messages. | ||
| Line 49: | Line 61: | ||
* On-site replying to and deletion 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). | * Support for "email gateway", where messages can be read and replied to using standard emails (like a mailing list). | ||
=References= | |||
* [https://etherpad.mozilla.org/mdnmessaging Discussion etherpad] from writing staff discussions about this topic. | |||