#40: Allow to revise one's submission
---------------------+---------------------
Reporter: pingou | Owner: nigelj
Type: defect | Status: new
Priority: major | Milestone: 2.4
Component: General | Version:
Keywords: | Blocked By:
Blocking: |
---------------------+---------------------
We have all what's needed to allow someone to change his/her mind and
revise his/her vote even after having voted once.
This shouldn't be hard to do.
--
Ticket URL: <https://fedorahosted.org/elections/ticket/40>
Fedora Elections <https://fedorahosted.org/elections/>
Fedora Elections
#21: Anonymize datasets
-------------------------+--------------------------------------------------
Reporter: nigelj | Owner: nigelj
Type: enhancement | Status: new
Priority: major | Milestone: Release 0.2.0
Component: General | Version: 0.1.5
Keywords: |
-------------------------+--------------------------------------------------
Apologies if this is how the system currently works.
I'm posting this on behalf of the Fedora Board. We would like for our
election voting tool to work like this:
FAS2 user goes to vote, they authenticate. The voting system assigns the
user a unique ID number. The user then votes, and confirms their vote. The
"ballot" is stored but is tied only to this unique ID number (not to the
FAS2 user/account). The FAS2 system records that the FAS2 user has voted,
but does not store a correlation between the FAS2 account and the unique
ID number attached to the ballot.
Thus, we have a dataset showing the results, but it is anonymized
automatically, and we still know who has (and has not) voted, just not who
(or what) they voted for.
Thanks in advance.
---
2008-07-29 19:26:00 changed by mmcgrath
Just so we're clear. The idea is to ensure that the results of a ballot
cannot in any way be tied to a user. We would also not want this data in
logs on the elections app servers correct?
This might make fraud more likely but then I'm not entirely sure how its
any better or worse from that perspective with what we have now.
G, can you think of any technical hurdles in implementing this?
Spot/Board: Do you want us to anonymize the data that's already in the
database?
2008-07-29 19:35:42 changed by spot
Yes, that is the idea. We would not want a correlation between a ballot
and a user anywhere, not even logs. If we're careful with ensuring that
once a ballot is submitted, the FAS2 user is marked as having voted in an
election, I don't think we open the door to any additional fraud
possibilities.
As to anonymizing the existing data, I'm not sure it is worth the effort.
2008-07-29 21:39:01 changed by jspaleta
If we are going to be making changes to address the voting system... are
we gonna make any effort to contact someone doing active research into
electronic voting methods to get an idea as to existing workable
implementation concepts that accomplish the desired anonymizing of the
voting but also protect against fraud?
-jef
--
Ticket URL: <https://fedorahosted.org/elections/ticket/21>
Fedora Elections <https://fedorahosted.org/elections/>
Fedora Elections
#25: Allow other voting methods
---------------------+------------------------------------------------------
Reporter: nigelj | Owner: nigelj
Type: defect | Status: new
Priority: major | Milestone: Release 0.3.0
Component: General | Version: trunk
Keywords: |
---------------------+------------------------------------------------------
In addition to #24, it'd be nice to allow a simpler voting method,
something like:
for - abstain - against
For would be +1, abstain 0, against -1
This makes it nice and easy to count etc.
Is this something like you want as well Kevin?
--
Ticket URL: <https://fedorahosted.org/elections/ticket/25>
Fedora Elections <https://fedorahosted.org/elections/>
Fedora Elections