Tom Barrett

There is probably some third-party library which would handle "internal cron" for us. So that the system cron calls some script every hour/whatever, and the library works out which tasks...

Yes interesting feature idea. It would be worth discussing it further here (including implementation details) to ensure a smooth path into the main branch :)

More context: In the members area currently, you can manage your unavailabilities, and you can view any roster view which has its visibility set to "members area" or "public".

Some initial questions that arise for me: - Why limit the date range, instead of having it open-ended? - If Joe Bloggs adds himself to the roster on a certain...

Ah I see, it's like a draft roster for a particular period. A 'working document'.

"Member roster view" probably isn't the best name, because "roster view" already refers to a collection of roster roles, without the time-restricted draft concept. Maybe "Roster draft" is a better...

So I can see it working like this: * Administrator creates a "roster draft" object, which references roster view and has a start and end date. * In the members...

Yes I guess that's fair enough. A roster_draft record signifies "assignments for roster view X between dates Y and Z are open for self-editing". I wonder if there would be...

The tricky part is that the mailchimp sync includes merge tags (custom fields in Mailchimp) for gender, congregation, age bracket and status. These could all be different for the two...

The thing is: Once you've recorded "Sally's friend Deb" in the notes field, you *have* "added Deb to the database"! People currently tend to handle this kind of scenario by...