Confirmed users
753
edits
No edit summary |
(→Email) |
||
Line 6: | Line 6: | ||
== 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. | ||
=== Structure of the email === | |||
Email will have a list of Good first bugs and potentially Good first projects that people can help with. | |||
=== Frequency of emails === | |||
Currently we are thinking that this will be best sent as 2 emails with differing content. | |||
==== Weekly/Fortnightly Email ==== | |||
This will have a list of Good First Bugs that people can work on that will be pulled from Bugzilla. We may decide to seen a separate email for mentored bugs based on how many bugs the person has fixed. | |||
==== Monthly/Quarterly Email ==== | |||
This email will show a list of the top contributors. The idea is to create a little competition between contributors to get onto that list and show that we value their contribution. | |||
== 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. |