devshawn / ulysses Goto Github PK

it's happening before prettifyOutput, and doesn't seem to be related to my handling of slots. I suspect the number of volunteers is somehow relevant.

I probably need to change my while loops to for loops because of behavior... It's at where it's at because I was focusing on getting the output to look proper, and not error.

Volunteers should be able to have e-mails sent to them with their assignments. This should be sent to them from organizers.

Things to consider:

• Initial e-mail boolean (have they been emailed already)
• E-mail all volunteers (that have an assignment) their assignment, ignore non-assigned volunteers
• E-mail a particular volunteer their assignment
• E-mail all updated volunteers their new, or updated, assignment

Add tests for the various subroutines used by the scheduler.

We need to have end-to-end unit testing for volunteer functions, organizer functions, pretty much everything. It would be good to get this automated and tested before we have tons of generated schedules and lots of use of the software product.

We want to be able to view a master schedule of all of our time slots, preferably in nice columns dependent on the job. We should be able to color code the slots. The slots should say the start and end time, and probably, the volunteers that are currently assigned. We should talk to the customer to get more details once we get a base system implemented.

This will probably fix the rest of the errors...