Changeset 26fd6cf for asadb/template


Ignore:
Timestamp:
Aug 28, 2012, 1:54:00 AM (14 years ago)
Author:
ASA Group Database <asa-db@…>
Branches:
master, space-access, stable, stage
Children:
8068f6d, 3af5d74
Parents:
0851637
git-author:
Alex Dehnert <adehnert@…> (08/28/12 01:54:00)
git-committer:
ASA Group Database <asa-db@…> (08/28/12 01:54:00)
Message:

August 28 derecognition reminder

File:
1 edited

Legend:

Unmodified
Added
Removed
  • asadb/template/groups/letters/missing-transition.txt

    r0851637 r26fd6cf  
    11{% autoescape off %}
     2Hello {{group.name}},
     3
     4    We're following up on our email from July 31st (see below). You still
     5appear to be suspended, and are consequently currently scheduled for
     6derecognition *this Friday*.
     7
     8The following problems (at least) exist with your database entry:
     9{% for prob in problems %}* {{prob}}
     10{% endfor %}
     11
     12Please contact us (asa-exec@mit.edu) by this Friday (August 31st) if you wish
     13to remain active.  We prefer that you fix the listed problems first, but can
     14give you some extra time if needed.
     15
     16You can view your ASA Database entry at
     17https://asa.mit.edu/groups/{{group.pk}}, and the listed president, treasurer,
     18and group admin can update it. If they are not available, please contact
     19asa-exec@mit.edu promptly, copying your president and officers' list.
     20
     21If you have any questions or concerns, please contact us at asa-exec@mit.edu.
     22Make sure to include your group and database URL (just replying to this email
     23is fine).
     24
     25Thanks,
     26Alex Dehnert
     27ASA Executive Board
     28
     29===
     30
    231Hello again {{group.name}},
    332    We contacted you several months ago (see below) informing you that we
     
    736
    837In particular, the following problems apply:
    9 {% for prob in problems %}* {{prob}}
    10 {% endfor %}
     38[...]
    1139
    1240In order to get your group unsuspended, you should first update your database
Note: See TracChangeset for help on using the changeset viewer.