launchpad development|
Size: 1222
Comment:
|
← Revision 4 as of 2010-11-08 19:46:42 ⇥
Size: 1483
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 2: | Line 2: |
''('''note:''' still a work in progress draft here...)'' |
|
| Line 8: | Line 6: |
| * ''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. | * ''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 12: | Line 10: |
| * Ideally, we will eventually build a standard way to do this in Launchpad. | |
| Line 15: | Line 14: |
| * Not projects, packages, etc. Make sure you send one email ''per person''. | * Not projects, packages, etc. Make sure you send one email '''''per person'''''. |
| Line 17: | Line 16: |
| * Make sure you know the difference between bug supervisors, drivers, and other celebrities and who can do what on Launchpad. This can be deceptive. Ask around and also look at the code path email recipients will hit. |
Sending Mass Emails
If you need to send mass email on behalf of Launchpad, here are some things to consider.
- 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.
- Build email script on other people's work
See spam.py in lp:~launchpad/lp-dev-utils/trunk as an example
A flawed script that deryck used is at lp:~deryck/+junk/lpjunk
- Ideally, we will eventually build a standard way to do this in Launchpad.
- Make data changes first
- If your email is based on changes being made on Launchpad, then make those changes before sending email.
- Remember: you're sending email to people
Not projects, packages, etc. Make sure you send one email per person.
- Ensure the people have permissions for required action
- Make sure you know the difference between bug supervisors, drivers, and other celebrities and who can do what on Launchpad. This can be deceptive. Ask around and also look at the code path email recipients will hit.
