Now that bloc STAR SC elections have been approved (quite a while ago actually) and the changes to PEP 13 have been merged, we need to figure out how to actually run an election this way.
I know that it’s awfully early to start thinking about this (the election result was posted earlier today), but I’d rather be early than having to scramble because everyone forgot until a month before next year’s election.
I checked with Ee and they are willing to run the election using whatever tool we pick. But I think it would be nice if we didn’t also saddle them with picking the tool.
Here’s what I found out so far (also a while back).
-
@larry has a complete STAR voting library with Bloc STAR support but I believe he’s reluctant to offer using it for running the SC election (probably out of modesty, or because he doesn’t want the hassle of having to babysit a production service). (Actually, I didn’t find any evidence on Discourse about his reluctance, so maybe he will be willing to host the election for us. Larry?)
-
There’s an open source site bettervoting.com that will host simple elections for free (but you have to do all the work yourself) and (for a fee?) they will do most of the work for you (not sure how much – their email said “we’re also happy to help officiate the election on your behalf”).
That’s all I found so far. (STAR voting is pretty new.)
IIUC, unlike Helios, bettervoting.com does not guarantee that nobody can see your ballot – but if they host it, only their database admin can see it. (What about people with root on their server?) I would personally fine with this – I don’t see why their admins would care about our election (it’s a TypeScript code base), but it’s worth thinking about. PEP 13 doesn’t specify how secure the ballot system needs to be (and never did). Not sure what the situation with Larry’s library would be.
Thoughts? Opinions? Too soon? I’m sure the new SC has better things to do with their time (congrats all!).