User:Automatedtester/Community Email: Difference between revisions
No edit summary |
|||
| Line 1: | Line 1: | ||
= Community Email Initiative = | = Community Email Initiative = | ||
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. | ||
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 == | ||
Email is a medium that a lot of people use regularly and know how to triage quite quickly if they are not interested in it. This means that we can put ourselves in front of them on a regular basis and, with a bit of wordsmithing, get them re-engaged with the team and/or mentor they had previously. | Email is a medium that a lot of people use regularly and know how to triage quite quickly if they are not interested in it. This means that we can put ourselves in front of them on a regular basis and, with a bit of wordsmithing, get them re-engaged with the team and/or mentor they had previously. | ||
== Data needed == | == Data needed == | ||
Unfortunately to make this personalised we will need to collect some data. Below is a sample of the data we need at least at the beginning and will probably be expanded depending on how initial sends go. | Unfortunately to make this personalised we will need to collect some data. Below is a sample of the data we need at least at the beginning and will probably be expanded depending on how initial sends go. | ||
=== Data for segmentation === | === Data for segmentation === | ||
* Name (this might just be a IRC nick or we might need to collect that separately.) | * Name (this might just be a IRC nick or we might need to collect that separately.) | ||
| Line 21: | Line 13: | ||
* 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) | ||
=== Data collected from email === | === Data collected from email === | ||
* Opens | * Opens | ||
* Clicks (this is done on each link) | * Clicks (this is done on each link) | ||
* Forwards | * Forwards | ||
=== 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. | |||
Revision as of 21:24, 24 April 2014
Community Email Initiative
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 Are We Everyone Yet for data. A lot of people come in through initiatives like What Can I do for Mozilla and from 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. 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 is a medium that a lot of people use regularly and know how to triage quite quickly if they are not interested in it. This means that we can put ourselves in front of them on a regular basis and, with a bit of wordsmithing, get them re-engaged with the team and/or mentor they had previously.
Data needed
Unfortunately to make this personalised we will need to collect some data. Below is a sample of the data we need at least at the beginning and will probably be expanded depending on how initial sends go.
Data for segmentation
- Name (this might just be a IRC nick or we might need to collect that separately.)
- Programming language(s)
- Team(s) they are engaging
- Bugmail address (This is more to help with joining metrics between bugzilla and ESP)
Data collected from email
- Opens
- Clicks (this is done on each link)
- Forwards
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.