Halalan 2.0 Direction (was: Halalan 2.0 UI Design Contest)

7 views
Skip to first unread message

Waldemar Bautista

unread,
Feb 21, 2011, 7:32:35 PM2/21/11
to halal...@googlegroups.com
On Mon, Feb 21, 2011 at 11:01 PM, Darwin Bautista <dar...@gmail.com> wrote:
> I read the paper about the Helios voting system recently. It made me
> ponder if we should make Halalan 2.0 a single-page web application.
> With this approach, we'll have more control on what's shown and what
> shouldn't be (e.g. votes of previous voter).

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

Darwin Bautista

unread,
Feb 21, 2011, 9:26:48 PM2/21/11
to halal...@googlegroups.com, Waldemar Bautista
You're right. I'm guessing the priority for Halalan 2.0 would be:
* voter groups
* multiple admins
* modern interface
* InnoDB?

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.

Waldemar Bautista

unread,
Feb 21, 2011, 9:38:22 PM2/21/11
to halal...@googlegroups.com
On Tue, Feb 22, 2011 at 10:26 AM, Darwin Bautista <dar...@gmail.com> wrote:
> * InnoDB?

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

Reply all
Reply to author
Forward
0 new messages