The schema file should now be correct

[selectricity-live] / TODO

diff --git a/TODO b/TODO
index bba3e79df8450e97ba1ba02de5de248d60a9a138..0575d629afa9bde8c0e0993dd6f09a92dff5a28c 100644 (file)
--- a/TODO
+++ b/TODO
@@ -5,8 +5,6 @@ General Issues
 
 Known bugs or issues:
 
 
 Known bugs or issues:
 

-- randomize each voting list
-

 - it'd be nice if the ordering were persistent, so I could drag
   the candidates around, then come back later (loading the page anew),
   make tweaks, and submit.
 - it'd be nice if the ordering were persistent, so I could drag
   the candidates around, then come back later (loading the page anew),
   make tweaks, and submit.


@@ -15,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.
 
   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.
 - 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.


@@ -30,11 +24,6 @@ Known bugs or issues:
   helpful for auditing, too, as one could separately match names to the
   correct list and match addresses to names.)
 
   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
 ==============
 
 QuickVotes
 ==============