search

dmurphy1 / Warmshowers.org

The code for warmshowers.org. If you'd like to help develop code for Warmshowers.org or if you would like to handle some of the website configuration/sitebuilding tasks in the issue queue, please let me know.
http://www.warmshowers.org
0 stars 0 forks source link

Fix update of pester queue #1

Open dmurphy1 opened 10 years ago

dmurphy1 commented 10 years ago

My notes and thoughts regarding local development prior to making a pull request.

dmurphy1 commented 10 years ago

Criteria for pestering: (1) If unavailable and become available is NULL (note: set_unavailable_timestamp will also be NULL if become available is NULL, and vice versa): If they've been unavailable for more than 6 months, and they have not been pestered in 2 months, then pester. (2) If unavailable and become available is set (note: set_unavailable_timestamp will also be set if become available is set, and vice versa): If they become available in more than 7 months from now, and they've been unavailable for more than 6 months, and they have not been pestered in 2 months, then pester. So, for example, a user that sets their availability 13 months in the future will receive one pester email before they automatically become available.

User's whose become available date passes will automatically become available, and they will be notified via email.

dmurphy1 commented 10 years ago

Also, need to include a way to test.

dmurphy1 commented 10 years ago

Per Randy: "Also, in the default text, make sure the username is included in the subject, which causes the various support requests to sort separately in gmail"

dmurphy1 commented 10 years ago

For testing - the problem is that wsuser save will automatically set/update the timestamps for set_available_timestamp, set_unavailable_timestamp, and last_unavailability_pester, making it difficult to test.

dmurphy1 commented 10 years ago

Also, become available SHOULD NOT be allowed to be set in the past, so that SHOULD be difficult to test too.