Diff for "PolicyAndProcess/MassEmail"

Not logged in - Log In / Register

Differences between revisions 2 and 3
Revision 2 as of 2010-11-08 19:12:34
Size: 762
Editor: deryck
Comment:
Revision 3 as of 2010-11-08 19:19:25
Size: 1222
Editor: deryck
Comment:
Deletions are marked like this. Additions are marked like this.
Line 7: Line 7:
 1. So you really have to send the email?
    * Seriously, think about it. Is the email absolutely necessary?  Be cautious and try to find other means of notification -- blog, identi.ca, twitter, etc. If you do have to send email, then make sure you blog first. Emails should be supplementary notifications where the importance of the notification warrants contacting people directly.
 1. Do you really have to send the email?
    * ''Seriously'', think about it. Is the email absolutely necessary?<<BR>><<BR>>Be cautious and try to find other means of notification -- blog, identi.ca, twitter, etc. If you do have to send email, then make sure you blog first. Emails should be supplementary notifications where the importance of the notification warrants contacting people directly.
Line 10: Line 10:
    * See spam.py in [[https://code.launchpad.net/~launchpad/lp-dev-utils/trunk|lp:~launchpad/lp-dev-utils/trunk]] as an example
    * A flawed script that deryck used is at [[https://code.launchpad.net/~deryck/+junk/lpjunk|lp:~deryck/+junk/lpjunk]]
Line 11: Line 13:
    * If your email is based on changes being made on Launchpad, then make those changes before sending email.
Line 12: Line 15:
    * Not projects, packages, etc. Make sure you send one email ''per person''.

Sending Mass Emails

(note: still a work in progress draft here...)

If you need to send mass email on behalf of Launchpad, here are some things to consider.

  1. Do you really have to send the email?
    • Seriously, think about it. Is the email absolutely necessary?

      Be cautious and try to find other means of notification -- blog, identi.ca, twitter, etc. If you do have to send email, then make sure you blog first. Emails should be supplementary notifications where the importance of the notification warrants contacting people directly.

  2. Build email script on other people's work
  3. Make data changes first
    • If your email is based on changes being made on Launchpad, then make those changes before sending email.
  4. Remember: you're sending email to people
    • Not projects, packages, etc. Make sure you send one email per person.

  5. Ensure the people have permissions for required action

PolicyAndProcess/MassEmail (last edited 2010-11-08 19:46:42 by deryck)