comex wrote:
For the CotC election I intend to vote for and only for a candidate who will maintain a database with a web interface (preferably *the* database) emself. Currently we have, in effect, two redundant databases (one of which is a set of text files), one maintained by Murphy, one Zefram. The CotC database has a very nice interface, but it is not always in sync with the actual gamestate, which I dislike.
This would change if I were CotC again, as the database would drive the carrying-out-of-duties rather than the other way round.
If made CotC, I intend to: - attempt to find a way to manage the CotC database (see above) or, failing that, make my own
It was relocated once before (from Eris's server to mine), but it took a good bit of head-scratching. I could give you a shell account, but then you'd be cut off whenever my server's net connection decided to flake out for a while. (The cfj.qoid.us mirror is a good workaround for that problem.)
- send messages to official in the same verbose format as Zefram
The DB was designed to generate copy+paste'able messages in a similar format (follow the "Format for e-mail" link on any case page). I'd have to see how much updating it would require (some things are just terminology; others are somewhat conceptually different, e.g. the mechanism for calling appeals, but could be dealt with by one who knows how; others are completely outside the DB's knowledge, e.g. pre-trial phases, and would likely require manual maintenance of an external file - not that I haven't been doing that in spades anyway with the Assessor and Accountor records).
- support automated CFJ submission to the extent that is feasible and that is acceptable to Agora
Should require username+password to block spambots.
