This is worth exploring but as of now, I'm thinking of just improving
1.x.x in 2.0. There are still many things left to do so I'm not yet
ready for radical changes. Maybe as a sideline or in Halalan 3.0, we
can start creating from a different concept.
--
Waldemar Amado Bautista
We need this to support transaction and it is also the default engine
of MySQL 5.5 so I think this is a safe choice going forward.
> Also, I have an idea on how to solve the "voter anonymity issue" using voter
> groups, if you haven't already thought of it. :D
> Instead of storing the voter_id in the votes table, we can replace it with
> the group_id of the voter group that a voter is part of, right? I figured
> this would work since we don't actually look at the individual voters
> themselves when generating the statistics.
Actually, I'm thinking of a 3-level "privacy".
Level 0:
- no association of votes and voters
- cannot generate statistics
- voters cannot login again and view/print their votes
Level 1:
- association of groups and votes (as you stated)
- can generate results breakdown by group
- voters cannot login again and view/print their votes
Level 2:
- association of voters and votes
- can generate results breakdown by group
- voters can login again and view/print their votes
We can offer this as an option during installation.
--
Waldemar Amado Bautista