Finally have some code written. After some brief inspection of how Parliament actually works I decided it doesn't do what we need. We can use some of its features in the future if we like, but it's just not going to fit with what I want to do.
So, after playing with pyjamas a bit and realizing that CouchDB isn't quite mature yet, I figured just use Django, like originally planned. I have a tentative branch up on Launchpad, lp:~cellofellow/gavel/gavel_django. So far all it has is one app called "rules" with a lot of different kinds of motions in it. I got the basic information on what to put in there from an official NAP cheat sheet. I'll link to it if I can find it. Basically, the rules are hard-coded within each objects fields. These rule fields are not stored in the database. We may be able to find a way to get them to be stored in the database in the future. Only the bare necessities, like who made the motion, which motion a subsidiary motion modifies, and the like are stored in the database. One thing on the todo list is determine a standard API for amending. There are lots of different motions that allow amending, and almost every one of them behaves differently when amended. For now this rules app should remain abstract. It should be models-only, in theory, no views or templates. -Josh -- Society loses the value of things which are uselessly destroyed. --Frederick Bastiat GCS/B/M d+ s+ a--- C++ UL++ Py+++ L+++ E- W++ w-- M- PS+++ PE+++ Y+>++ PGP+ t+ R tv- b+ DI++ G e h! r! y- _______________________________________________ Mailing list: https://launchpad.net/~gavel-team Post to : gavel-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~gavel-team More help : https://help.launchpad.net/ListHelp
