#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
#44: Rework FAS integration
-------------------------+-----------------------------
Reporter: pingou | Owner: nigelj
Type: enhancement | Status: new
Priority: major | Milestone: Future Release
Component: General | Version:
Keywords: | Blocked By:
Blocking: |
-------------------------+-----------------------------
At the moment we keep the user's FAS name in memcached but this is not
working so well and quite ofte we're stuck or very slow.
What we could do is add a new table or a new field in the candidate table,
to store locally the FAS name.
This way, when we add/edit candidates, we would query FAS for their name,
store it locally and forget about memcached.
--
Ticket URL: <https://fedorahosted.org/elections/ticket/44>
Fedora Elections <https://fedorahosted.org/elections/>
Fedora Elections
#46: Migrate to Pagure
----------------------------+-----------------------------
Reporter: jflory7 | Owner: nigelj
Type: task | Status: new
Priority: blocker | Milestone: Future Release
Component: Administration | Version: 0.2.1
Keywords: | Blocked By:
Blocking: |
----------------------------+-----------------------------
= Problem =
All FedoraHosted instances are closing
[https://communityblog.fedoraproject.org/fedorahosted-sunset-2017-02-28/
on February 28, 2017. This Trac instance should be [https://pagure.io
/pagure-importer migrated to Pagure].
= Analysis =
I remember ryanlerch saying he had attempted this one, but there had been
a bug at the time that prevented him from moving it. It was since resolved
(the same one I faced moving the Marketing Trac). But since it's fixed, it
should be possible for moving now.
--
Ticket URL: <https://fedorahosted.org/elections/ticket/46>
Fedora Elections <https://fedorahosted.org/elections/>
Fedora Elections
#45: Add support for claiming badge from voting
-------------------------+-----------------------------
Reporter: jflory7 | Owner: nigelj
Type: enhancement | Status: new
Priority: critical | Milestone: Future Release
Component: Voting | Version: 0.2.1
Keywords: badges | Blocked By:
Blocking: |
-------------------------+-----------------------------
= Enhancement =
After voting, a user can click a link to receive a badge for participating
in the elections (similar to Nuancier).
= Analysis =
Ideally, there should be a way to determine if a badge is available for an
individual election or for all elections globally. I think the current
idea is to make it so that there is just one badge for the entire election
cycle, but it may make more sense to design it so that each individual
link is set up with a badge claim code, should there ever be a need or
desire to create a badge for a specific election.
It would be claimed like in Nuancier, where the user is presented with the
link to the badge immediately after submitting their vote to any given
election.
= Implementation =
1. Choose an election, vote.
2. Submit votes.
3. On post-vote / confirmation page, "Thanks for voting! etc." and
clickable link with the badge claim URL
--
Ticket URL: <https://fedorahosted.org/elections/ticket/45>
Fedora Elections <https://fedorahosted.org/elections/>
Fedora Elections