Votorola Changes ---------------- 0.1.9 2008-06 A viewer for the voter list was added to the Web interface. Users may browse the list at various scales, ranging from the whole electoral district, down to its component neighbourhoods. Minor bugs were corrected in the Web interface. The script "list.js" was added for configuring the compilation and indexing of the voter list. A default is provided under votorola/a/register/, please copy it to your register's configuration directory. List compatibility with previous releases is broken. Any voter list compiled by "volist" under a previous release will be unmountable under this one. 0.1.8 6 Election results were added to the Web interface. Voter pre-registration of new candidates was added, similar to the same feature in the mail interface. User's guides were drafted for both Web and mail. Count compatibility with previous releases is broken. Any election count tallied by "vocount" under a previous release will be unmountable under this one. 0.1.7 6 Tabbed navigation was added to the Web interface. Electoral districts were formalized, and are now separately configurable for each election. Support for relative file paths was added to the modular inclusion facility (_voIncluder) for use in configuration scripts. Reply localization and bounce handling bugs were corrected in the mail interface. 0.1.6 5 User authentication was added to the Web interface. Users have the choice of either OpenID or email authentication. Rate limits were imposed on messages sent from the mail interface, in order to prevent mail loops or deliberate abuse. Item "userDatabase" was added to the subserver configuration (subserver.js). It configures the database in which users' preferences and other settings are stored. Item "mailTransferService" was added to the Web interface configuration (web.js). It configures the transmission of email authentication messages. By default, messages are transmitted via the localhost mail server. 0.1.5 5 Voter registration pages were added to the Web interface. Summary descriptions of the electoral subserver and its services were added to both the Web and mail interfaces. Items "setJurisdictionName" and "setShortJurisdictionName" were renamed in the subserver configuration to "setDistrictName" and "setShortDistrictName". Please modify your subserver.js. The fallback cache directory for the Web interface was relocated to a subdirectory named after the subserver. Persistance of the Web interface's activity window will be lost (at least under Tomcat), unless you shut down the interface; manually move the serial file (web-activity-list.serial) to the new location; and restart. 0.1.4 5 An activity window was added to the Web interface, providing voters with a view of recent electoral activity. Instructions for the initial setup of an electoral office were completed in the administrator's manual. The default location of the snapshot output store (files for mounted election counts and voter lists) was moved from /var/cache to /tmp. The general location of cache files is now configured per subserver, set by "setCacheDirectoryPath" in your subserver.js. 0.1.3 5 An "altin" facility was added to the voter interface. It enables the user to login under the identities of other users (with limited privileges), in order to see who they are voting for, how they are registered, and so on. The naming of electoral services was simplified on the administrative side. 0.1.2 4 The visualization of vote traces in the user interface was improved. Configuration was overhauled. Electoral services are now configured by scripts (JavaScript), instead of by XML. A test interpreter "voscript" was added to the command line interface, for off-line smoke testing of the configuration. 0.1.1 4 A Web interface was added for voters. A relaying loophole was closed in the mail interface. 0.1.0 3 The electoral register is now backed by a neighbourhood trust network. Commands "trust" and "untrust" were added to the front end, allowing voters to submit trust signals for the purpose of cross-authentication. A channel to Google's geocoding service was added to the back end, enabling signal ranges to be restricted by configuration scripts. A complete trace of the trust network is now merged with the voter list, enabling administrators to restrict voting to trusted registrants. This completes the functional core of Votorola, bringing it to alpha. 0.0.11 pre-alpha 3 Voter eligibility tests were added. Administrators may now specify eligibility criteria, such as residential address, by attaching a test script to the election. Support for meta-services was added to the "voter" command shell. Administrators may now issue meta-commands directly from the command line on behalf of voters, bypassing the usual voter interface. 0.0.10 3 The utility "volist" was added to the command line administrative interface. Snapshots of the electoral register may now be captured in archival format. Use cases were documented. 0.0.9 1 A snapshot facility for electoral registers was added to "vosnap". The design of the voting mechanism (delegate cascade) was documented. 0.0.8 1 The electoral register was coded. Register "set" and "unset" commands were added to the voter interface. 0.0.7 2007-12 The utilities "vosnap" and "vocount" were added to the command line administrative interface. Snapshots of elections may now be captured in archival format, and results tallied. 0.0.6 12 A meta-service was added to the voter interface to provide bootstrap instructions on accessing the electoral services. 0.0.5 12 Basic "vote" and "unvote" commands were added to the voter interface, allowing votes to be cast or withdrawn. 0.0.4 11 Manual pages were written for the command line administrative interface. Help options were added to administrator and voter commands. A "voter" shell was coded, allowing an administrator to issue a voter command directly to an electoral service. 0.0.3 11 The command/response layer of the voter interface was coded. The code was internationalized. 0.0.2 10 The authentication layer of the mail-based voter interface was coded. A demonstration subserver was set up. 0.0.1 9 The project was created. Initial designs were drafted, and posted for public review.