On Tue, Sep 26, 2006 at 03:23:35AM -0000, Serge wrote:
We also would need to have a proposal at hand for what the system should be able of doing (Emmanuel do you have such a definition document?). Then again it’s not like it needs to be all slick and pretty since these documents are openstanding, it is more to provide a reasonable amount of information and direction for people to catch up on the idea and decide if they are interested and want to participate. Once the starting elements are there, it’s all about publicity. Talk on message boards forum, talk with political bloggers, email your address book about it, whatever you can think of to spread the word….
I don’t have much documents besides our discussions and parlement itself. Somehow, there is also rubyforge.
Basically, here are the already implemented features:There are no roles, ranks, agendas, private settings, or obscured data. Everything is transparent, but for passwords (which are recorded as salted hashes and not replicated).
Poll results will be calculated according to a given electoral list. Which would thus act as a caucus of sorts. Anybody will be able to setup any number of electoral lists.
Anyone who has already posted to top-politics already has a parlement’s pseudo. It is the same as your mail’s name. Me for example, it’s “echarp”. Don’t hesitate to try it. You can, among other things, set up your avatar ;)
Come and have a talk on irc (you need to have java on your machine).
echarp – http://leparlement.org/irc
+2
+1
This reminds me about compilating our recent intentions in order of getting back to them when the time comes.
ATB,
Gale
+1
+1
+1
+1
I am copying your implemented features and planned additions on the wiki so we may try to find a synthetic vision of the features a system would need.
Cool, definitely very cool!
Chiefly I’d like to add that this needs to be as easy as possible to install and implement so as to raise the chance of organizations adopting it.
There are currently two dependencies: ruby on rails and PostgreSQL. The only one bothering me is the DB. Anybody knows of a good ruby DB to remove that dependency? (this would do the same trick as derby in a J2EE project)
best regards,
Thanks, take care
echarp
+1