clandmeter/patchwork, branch notifications

notifications: implement opt-out

2011-04-14T11:37:55+00:00

Check for opt-out status before sending notification mail.

Signed-off-by: Jeremy Kerr

notifications: Add NOTIFICATION_FROM_EMAIL setting

2011-04-14T09:24:31+00:00

Allow a separate From: address for notificaton emails.

Signed-off-by: Jeremy Kerr

notifications: Add code to send notifications

2011-04-14T09:24:15+00:00

Add a function (patchwork.utils.send_notifications) to process the
PatchChangeNotification queue. We try to group mail to the same sender,
by waiting settings.NOTIFICATION_DELAY_MINUTES to allow other
notifications to arrive.

Signed-off-by: Jeremy Kerr

models: Add PatchChangeNotification and record patch state changes

2011-04-14T09:24:03+00:00

Add a PatchChangeNotification model to keep track of changes to a
patch's state. Hook this up to Patch's pre_save signal.

Requires a DB schema upgrade.

Signed-off-by: Jeremy Kerr

Add email opt-out system

2011-04-14T09:23:04+00:00

We're going to start generating emails on patchwork updates, so firstly
allow people to opt-out of all patchwork communications.

We do this with a 'mail settings' interface, allowing non-registered
users to set preferences on their email address. Logged-in users can do
this through the user profile view.

Signed-off-by: Jeremy Kerr

registration: use EmailConfimation rather than separate registration app

2011-04-14T09:21:04+00:00

Since we have infrastructure for email confirmations, we no longer need
the separate registration app.

Requires a migration script, which will delete all inactive users,
including those newly added and pending confirmation. Use carefully.

Signed-off-by: Jeremy Kerr

Use generic email confirmation object

2011-04-14T08:44:53+00:00

Rather than having a UserPerson-specific confirmation, add an
EmailConfirmation object to allow multiple types of confirmations (eg,
opt-out requests in future).

To do this, we use a view (patchwork.views.confirm) that will call the
type-specific view with the confirmation object.

Also, add tests to check that the User/Person linkage system works.

Signed-off-by: Jeremy Kerr

forms: Fix MultipleBooleanField.to_python when the field value is missing

2011-04-14T07:07:43+00:00

If you write a test for, say, the bundle form of a patch list, you'd
still have to specify the 'no change' value to other form (e.g. the
multiple update one) fields using MultipleBooleanField or else it'd
raise a ValueError when field.clean() is called as part of
form._get_errors().

Signed-off-by: Guilherme Salgado 
Signed-off-by: Jeremy Kerr

models: use implied line continuations

2011-04-14T07:04:14+00:00

Use the implied line continuations, and make the indentation more clear.

Signed-off-by: Jeremy Kerr

models: Project.is_editable to check whether a user has edit rights

2011-04-14T06:55:33+00:00

This is to replace the couple of places where we duplicate this same
check.

Signed-off-by: Jeremy Kerr