Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Renewal email #128

Open
jamesgeddes opened this issue Dec 3, 2020 · 8 comments
Open

Renewal email #128

jamesgeddes opened this issue Dec 3, 2020 · 8 comments
Assignees
Labels
P1 Issues that are both high impact and urgent

Comments

@jamesgeddes
Copy link
Contributor

jamesgeddes commented Dec 3, 2020

Send member email two weeks before their renewal date

Send member email one day before their renewal date.

Relates to #122

Requires #147

Impact

High

Urgency

Now

@jamesgeddes jamesgeddes added the pre-go-live Required for MVP label Dec 3, 2020
This was referenced Dec 3, 2020
@jamesgeddes
Copy link
Contributor Author

Here is the copy to use for this email.


Hi {{preferred_name}},

I just wanted to let you know that it's almost time to renew your Geek.Zone Sand membership. In the next few days, we will debit your bank account with the amount that you have specified in your GZ account.

Remember, GZ membership costs just £1 plus a suggested donation of £30 per year - that's less than 9p per day! Your support allows us to do all of our great events and activities, as well as to find other awesome geeks like you! As always, if you have any questions, comments or ideas, please do not hesitate to let me know.

Thanks for being awesome and continuing to be a part of our great, geeky community!

Thanks again, {{preferred_name}}

James & everyone at Geek.Zone

@jamesgeddes
Copy link
Contributor Author

This will need updating once #254 is available.

@Freshrojek
Copy link
Contributor

Thinking of using crontab schedules.
Deciding whether to check every member every month or so or to put an email in a queue once they join for when the renewal date is. Problem with the latter is there will be a constant massive queue of pending emails for every member.

@jamesgeddes
Copy link
Contributor Author

@Freshrojek ask @SamWinterhalder about celery beat.

@SamWinterhalder
Copy link
Contributor

@jamesgeddes @Freshrojek As far as I am aware, you do not need celery-beat to schedule tasks, using celery, but you do need it if the task is going to be repeated.

@jamesgeddes
Copy link
Contributor Author

I think setting a future date on the celery task would be better than cron

@SamWinterhalder
Copy link
Contributor

I think that post MVP we should be using specific workers to handle specific kinds of tasks to help organise what is being done and where/

@jamesgeddes
Copy link
Contributor Author

I believe that one can label your tasks so that would probably be the best way around it rather than creating several clone functions.

@jamesgeddes jamesgeddes added P1 Issues that are both high impact and urgent and removed pre-go-live Required for MVP labels May 30, 2021
@jamesgeddes jamesgeddes added P2 Issues that are high impact but not urgent and removed P1 Issues that are both high impact and urgent labels Oct 18, 2021
@jamesgeddes jamesgeddes added P? Awaiting priority assignment and removed P? Awaiting priority assignment P2 Issues that are high impact but not urgent labels Apr 13, 2022
@geekzonebotold geekzonebotold added P1 Issues that are both high impact and urgent and removed P? Awaiting priority assignment labels Oct 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P1 Issues that are both high impact and urgent
Projects
None yet
Development

No branches or pull requests

4 participants