The problem right now with the voting system is that the sever it's run on (and the databases it pulls from) are not automated or easily accessible, requiring and admin for the machine to intervene on Council's behalf. That game of admin-tag tends to take some time.

I've been working on the voting machine to allow several "new" features. You can see my recent check-ins to see the changes, mainly minor ones so far. One of those features was fixing a script to allow using one voting token for multiple elections, as was the case for the recent CC elections and will be the case for this dual Board/Council election. Another change was the ability to get your token re-mailed to you in case your spam filter ate the first one, or you accidentally deleted it.

I'm hoping to later update the system to create new elections, automate the pulls needed to form the electorate table, generate tokens, and possibly even automate the outgoing e-mail. That would allow Council or the Board to setup and run elections without the need of an administrator doing anything. It would also limit the exposure of the user database, since it would all be handled locally on the server, purely by php scripts.

For now, the setup steps one can replicate elsewhere (tables, candidates, etc) have been done and sent off to be injected. If we're lucky, we may have vote tokens mailing out later today or tomorrow. But that's highly dependent on Niels, as he's the only admin on those servers right now.