1 files changed, 37 insertions, 22 deletions
diff --git a/extensions/ContributorEngagement/template/en/default/contributor/email.txt.tmpl b/extensions/ContributorEngagement/template/en/default/contributor/email.txt.tmpl
index 915ebd912..489cbd36b 100644
--- a/extensions/ContributorEngagement/template/en/default/contributor/email.txt.tmpl
+++ b/extensions/ContributorEngagement/template/en/default/contributor/email.txt.tmpl
@@ -12,38 +12,53 @@ Subject: Congratulations on having your first patch approved
 Date: [% date FILTER none %]
 X-Bugzilla-Type: contributor-engagement
 
-Congratulations on having your first patch approved, and thank you for your
-contribution to Mozilla.
+Congratulations on having your first patch approved, and thank you
+for your contribution to Mozilla.
 
 [%+ urlbase %]attachment.cgi?id=[% attachment.id FILTER uri %]&action=edit
 
-The next step is to get the patch actually checked in to our repository. For
-more information about how to make that happen, check out this post:
+Once the patch is correctly formatted and all the nits are addressed,
+you should ask the person who reviewed your patch to push it to the
+try server for testing.
 
-https://developer.mozilla.org/en-US/docs/Mercurial_FAQ#How_can_I_generate_a_patch_for_somebody_else_to_check-in_for_me.3F
+Once it comes back passing all our tests, your patch will be ready
+to check in!  To get your patch checked in you can add "checkin-needed"
+to the Keywords field on the bug summary page, and one of our helpful
+Code Sheriffs will come by to merge it into the Mozilla codebase.
 
-While you are going through those final steps, if you're looking for a new
-project to take on, have a look at our list of 'mentored' [% terms.bugs %] ([% terms.bugs %] where
-someone is specifically available to help you):
+Contributors with commit access can set up Mercurial to make their
+lives much easier. You can get learn how to get access to the Try
+Server here:
 
-https://bugzil.la/sw:mentor
+https://wiki.mozilla.org/Try#Getting_access_to_the_Try_Server
 
-Alternatively, you could join us on our IRC chat server in the #introduction
-channel and ask for suggestions about what would be a good [% terms.bugs %] to work on.
-There's more about using our chat server at:
+And you can learn more about how Mozilla uses Mercurial here:
 
-http://irc.mozilla.org/
+http://mozilla-version-control-tools.readthedocs.org/en/latest/hgmozilla/index.html
 
-If you haven't done so already, this is also a good time to sign up to the
-Mozilla Contributor Directory and create a profile for yourself. Doing this
-will give you access to community members' profiles so you can reach out and
-connect with other Mozillians. You will need someone to 'vouch for' your
-profile; if you don't know any other Mozillians well, why not contact the
-person who approved your patch?
+While that's underway, we'd be happy to work with you on something
+new; you can take a look at our list of Good First [% terms.bugs %],
+where someone who knows the code can help you get started:
 
-The directory is here:
+http://mzl.la/1QDR0MC
+
+... or ask someone who worked on this bug with you about something you might
+like to look at next. As well, you can join us on IRC (irc.mozilla.org)
+in the #introduction channel, to ask for suggestions for yourself
+or help new contributors find their feet.
+
+For first time contributors this is also a good time to sign up to
+the Mozilla Contributor Directory! This will give you access to
+other community members' profiles, so you can connect with other
+Mozillians in your city, region or country.
 
 https://mozillians.org/
 
-Thanks again for your help :-)
-Josh, Kyle, Dietrich and Brian; Coding Stewards
+You will need someone to 'vouch' for your profile; if you don't
+know any other Mozillians well, why not contact the person who
+approved your patch?
+
+Thanks again for your help. Mozilla's success depends on contributions
+like yours, and the Open Web is stronger for your help.
+
+- Josh, Kyle, Dietrich and Brian; Coding Stewards