Ordered pref tables so that the smallest margin of vicotry appears first and the...

[selectricity-live] / TODO

diff --git a/TODO b/TODO
index f2e186e5ee61a36d8cd5a4168fa6687d18ee450c..0a4f465d05340399db6c38908d91a37bd4426d83 100644 (file)
--- a/TODO
+++ b/TODO
@@ -1,6 +1,9 @@
-Known bugs or issues:
+General Issues
+==================
+
+- check out about css for headers on documentation/Selectricity anywher\12
 
-- randomize each voting list
+Known bugs or issues:
 
 - it'd be nice if the ordering were persistent, so I could drag
   the candidates around, then come back later (loading the page anew),
@@ -10,10 +13,6 @@ Known bugs or issues:
   if it were aware that it's a five-seat election and could say
   explicitly who the whole board is.
 
-- it's probably a good thing that users can't check out what alternate
-  voting systems would have done at the click of a button. =)
-  (though of course they could work it out themselves.)
-
 - is there rhyme or reason to the ordering within each row of the
   second table in pref_tables?  it could be, eg, sorted by magnitude
   of victory, narrowest first.
@@ -25,9 +24,11 @@ Known bugs or issues:
   helpful for auditing, too, as one could separately match names to the
   correct list and match addresses to names.)
 
-- just a tiny suggestion - possibly it could be a good idea to add a
-  counter/line-count to the table with keys and vote results so in one
-  glance someone can see that the number of votes matches the number of
-  voters.
+QuickVotes
+==============
+
+- support for emailing users when quickvotes conclude (see create.rhtml)
 
+- support for invisible results until over quickvotes (see create.rhtml)
 
+- quickvotes should have automatically created urls