Confirmed users
753
edits
User:Automatedtester/Community Email: Difference between revisions
User:Automatedtester/Community Email (view source)
Revision as of 12:38, 25 April 2014
, 25 April 2014→Community Email Initiative
(→Email) |
|||
| (3 intermediate revisions by the same user not shown) | |||
| Line 2: | Line 2: | ||
Community at Mozilla is one of the pillars of how we get things done. In the latest release of Firefox we saw roughly 1/3 of people supplying patches being a volunteer. See [http://areweeveryoneyet.org/ Are We Everyone Yet] for data. | Community at Mozilla is one of the pillars of how we get things done. In the latest release of Firefox we saw roughly 1/3 of people supplying patches being a volunteer. See [http://areweeveryoneyet.org/ Are We Everyone Yet] for data. | ||
A lot of people come in through initiatives like [http://whatcanidoformozilla.org What Can I do for Mozilla] and from [http://www.joshmatthews.net/bugsahoy/ Bugsahoy]. A lot of people work on their first bug and hopefully the mentor can keep them engaged. | A lot of people come in through initiatives like [http://whatcanidoformozilla.org What Can I do for Mozilla] and from [http://www.joshmatthews.net/bugsahoy/ Bugsahoy]. A lot of people work on their first bug and hopefully the mentor can keep them engaged. | ||
Unfortunately due to projects that paid contributors need to do, especially with in specific timeframes, keeping community members engaged can be difficult. | |||
Unfortunately due to projects that paid contributors need to do, especially with in specific timeframes, keeping community members engaged can be difficult. When people have high priority issues community tends to be the first item that is dropped. | |||
With this in mind I would like to propose that we try a different tact to keep community members engaged using tried and tested digital marketing methods. By using these techniques we can hopefully gather metrics on how we are doing with community. | With this in mind I would like to propose that we try a different tact to keep community members engaged using tried and tested digital marketing methods. By using these techniques we can hopefully gather metrics on how we are doing with community. | ||
== Email == | == Email == | ||
| Line 9: | Line 11: | ||
=== Structure of the email === | === Structure of the email === | ||
Email will have a list of Good first bugs and potentially Good first projects that people can help with. | Email will have a list of Good first bugs and potentially Good first projects that people can help with. We will also have a look at including a list of active contributors (if they opt-in) to do this. | ||
=== Frequency of emails === | === Frequency of emails === | ||
| Line 30: | Line 32: | ||
* Team(s) they are engaging | * Team(s) they are engaging | ||
* Bugmail address (This is more to help with joining metrics between bugzilla and ESP) | * Bugmail address (This is more to help with joining metrics between bugzilla and ESP) | ||
* Opt-in for being added to emails if they do the top fixes in a specific time period | |||
=== Data collected from email === | === Data collected from email === | ||
* Opens | * Opens | ||
| Line 36: | Line 40: | ||
=== How will people sign up === | === How will people sign up === | ||
Hopefully we can patch Bugsahoy asking people if they want to sign up for the mailing list. If not we can have a snippet that we add (maybe part of the bug closure when landing) asking them to sign up for other bugs that they can work on. | Hopefully we can patch Bugsahoy asking people if they want to sign up for the mailing list. If not we can have a snippet that we add (maybe part of the bug closure when landing) asking them to sign up for other bugs that they can work on. | ||
Mentors are also crucial in getting people to sign up for the email to receive a regular update of bugs they can be working on. | |||