Re: [spoon-discuss] obsolete wiki pages

[Jeremy Cook <athena@xxxxxxxxxxxxxxx>]

On Sun, Aug 01, 2004 at 09:23:51PM -0400, Daniel Lepage wrote:
> 
> On Aug 1, 2004, at 7.56 PM, Jeremy Cook wrote:
> >True. We could make another minister to do the recognition you've been
> >doing, you know, and then we'd have an adminless game (though we'd
> >probably want to split it up, or set up a rotating system).
> 
> The whole point of recognition is to ensure that everything gets put 
> into public displays. At the moment, I'm the only one who can edit the 
> database directly, so for now I'm the only one qualified to recognize 
> rule changes, card changes, etc.
> 
> What I'd really like to do is become sort of a Minister of History. 
> Other people could write code to display current proposals, count 
> votes, etc., and then at the end of each nweek they'd send me big 
> chunks of XML containing all that nweek's props, some sort of 
> description of all the rulechanges, etc., and I'd just put the XML 
> stuff into the database so Historical Docs, etc. can search it all.
> 
> Then I'd also be in charge of keeping the website there, adding new 
> functionality to the wiki if needed, etc.; I could also be what my 
> reset-ruleset called the "Minster of Etc.", the guy responsible for 
> kludging together quick and dirty ways of tracking new game concepts 
> until we appoint somebody to track them properly.
> 
> That's my dream job, anyway.
> 
> As it stands, I'll probably end up doing the latter anyway as soon as 
> new game concepts start cropping up again, but I also have to go edit 
> the database whenever the rules are changed, or funny things happen 
> with cards, or somebody makes a CFI, and I have to enter proposals into 
> the wiki, etc. I also currently seem to be in charge of writing most of 
> the automation code - so far the only player to donate code has been 
> Phil, who wrote python modules for scanning XML proposals into python 
> objects, and then for turning those objects into nice HTML. I am very 
> thankful for this code.

I'd like to (formally) prop a system where you write out the specs of
the Python scripts you want, and Players get points for writing them.
I'd like to help with this, but I'm not sure exactly what you need.

The Minister of History could be automated easily if it's just putting
something in a database. Set permissions so that the wiki can send it 
to the database.

> Also, we talked at one point about making a very simple language to 
> describe rule change. It would save me a lot of time if we had such a 
> thing in effect - as it stands, I have to go through and edit each rule 
> one by one, so even repealing rules gets tedious.
> 
> I propose (informally, not as a Game Object) that we use something like 
> this:

This should be done formally as well. Keywords no longer exist as of
today, BTW. Also, #create is easier to type than CREATE or <propcode>
CREATE </propcode>.
_______________________________________________
spoon-discuss mailing list
spoon-discuss@xxxxxxxxx
http://lists.ellipsis.cx/mailman/listinfo/spoon-discuss