Change Details

New spec: https://docs.google.com/document/d/1wKtGxJn06bs6OGAFV7DKUfVw2salKdU_NAUn5SMGks0/edit# Definition of done for investigation: * take a look at the spec * Summarize approach and list rough tasks to be created on this phab (don't make them yet) * have a check in meeting with @DStrine and @CCogdill_WMF to review approach * Have a discussion with the team for an overall estimate Extremely old information: I met with the Mozilla team a couple of months ago and found out they built their own email subscription preference center. In the past, consultants had estimated building one of these would cost us upwards of $1m, but the Mozilla folks that was gross hyperbole. One of Mozilla's devs sent me these awesome notes with github links included. He said we are free to email or bug him on IRC if needed, but I'm leaving his contact info out of phab. Can we scope this and see if it's doable? This could be huge for both me and @CaitVirtue: **NOTES FROM MOZILLA** The email preference center is in the bedrock codebase[0] on github (links below), which is built using the Django[1] framework. As written it requires our basket[2] service for the newsletters and subscription data, as well as updating user prefs. Basket is basically a proxy to our email marketing provider (currently Exact Target, a.k.a. SalesForce Marketing Cloud I think). [0] https://github.com/mozilla/bedrock/ [1] https://www.djangoproject.com/ [2] https://github.com/mozilla/basket/ Email Pref Center Code: # View https://github.com/mozilla/bedrock/blob/master/bedrock/newsletter/views.py#L247-L459 # Forms https://github.com/mozilla/bedrock/blob/master/bedrock/newsletter/forms.py#L119-L216 Note: The view imports "basket", which is our python client library for interacting with the basket.mozilla.org service. The source for that is here: https://github.com/mozilla/basket-client

New spec: https://docs.google.com/document/d/1wKtGxJn06bs6OGAFV7DKUfVw2salKdU_NAUn5SMGks0/edit# Definition of done for investigation: * take a look at the spec * Summarize approach and list rough tasks to be created on this phab (don't make them yet) * Make sure we talk to ops about the possible need for another server so that we can display the donor's current email preferences without running into pci issues * Make sure we scope the 90 day suppression part needed for DS * Have a discussion with the team for an overall estimate Extremely old information: I met with the Mozilla team a couple of months ago and found out they built their own email subscription preference center. In the past, consultants had estimated building one of these would cost us upwards of $1m, but the Mozilla folks that was gross hyperbole. One of Mozilla's devs sent me these awesome notes with github links included. He said we are free to email or bug him on IRC if needed, but I'm leaving his contact info out of phab. Can we scope this and see if it's doable? This could be huge for both me and @CaitVirtue: **NOTES FROM MOZILLA** The email preference center is in the bedrock codebase[0] on github (links below), which is built using the Django[1] framework. As written it requires our basket[2] service for the newsletters and subscription data, as well as updating user prefs. Basket is basically a proxy to our email marketing provider (currently Exact Target, a.k.a. SalesForce Marketing Cloud I think). [0] https://github.com/mozilla/bedrock/ [1] https://www.djangoproject.com/ [2] https://github.com/mozilla/basket/ Email Pref Center Code: # View https://github.com/mozilla/bedrock/blob/master/bedrock/newsletter/views.py#L247-L459 # Forms https://github.com/mozilla/bedrock/blob/master/bedrock/newsletter/forms.py#L119-L216 Note: The view imports "basket", which is our python client library for interacting with the basket.mozilla.org service. The source for that is here: https://github.com/mozilla/basket-client Design

New spec: https://docs.google.com/document/d/1wKtGxJn06bs6OGAFV7DKUfVw2salKdU_NAUn5SMGks0/edit# Definition of done for investigation: * take a look at the spec * Summarize approach and list rough tasks to be created on this phab (don't make them yet) * have a check in meeting with @DStrine and @CCogdill_WMF to review approachMake sure we talk to ops about the possible need for another server so that we can display the donor's current email preferences without running into pci issues * Make sure we scope the 90 day suppression part needed for DS * Have a discussion with the team for an overall estimate Extremely old information: I met with the Mozilla team a couple of months ago and found out they built their own email subscription preference center. In the past, consultants had estimated building one of these would cost us upwards of $1m, but the Mozilla folks that was gross hyperbole. One of Mozilla's devs sent me these awesome notes with github links included. He said we are free to email or bug him on IRC if needed, but I'm leaving his contact info out of phab. Can we scope this and see if it's doable? This could be huge for both me and @CaitVirtue: **NOTES FROM MOZILLA** The email preference center is in the bedrock codebase[0] on github (links below), which is built using the Django[1] framework. As written it requires our basket[2] service for the newsletters and subscription data, as well as updating user prefs. Basket is basically a proxy to our email marketing provider (currently Exact Target, a.k.a. SalesForce Marketing Cloud I think). [0] https://github.com/mozilla/bedrock/ [1] https://www.djangoproject.com/ [2] https://github.com/mozilla/basket/ Email Pref Center Code: # View https://github.com/mozilla/bedrock/blob/master/bedrock/newsletter/views.py#L247-L459 # Forms https://github.com/mozilla/bedrock/blob/master/bedrock/newsletter/forms.py#L119-L216 Note: The view imports "basket", which is our python client library for interacting with the basket.mozilla.org service. The source for that is here: https://github.com/mozilla/basket-client Design