+ Robert's Rules have come up several times in conversations on occupy-dev lists and other related lists.
+ the decision process the Occupy General Assembly uses is heavily informed by Robert's
+ several different occupy dev teams are working on an online version of the GA process
+ I don't know who those teams are exactly, and none of them are in Austin, but they likely can be contacted through the Occupy-dev list
+ the local dev teams (occupyapps) are working on Mobile apps rather than websites, but I am quite sure they would love to make an ATEN or consensus app.
In fact, Austin is planning a 48-hour mass Code-a-thons for March & April. If we can get the resources, then Robert's could easily be the/a goal/target of the Code-a-thon (
code-a-thon.org)
Seems to me that the resource that either apps or code-a-thon peeps or anyone would need is a high-level analysis of what the steps in the process are and what UI screens would be needed to lead people through them.
The major roadblock that I have heard discussed is authentication. There are lots of ways to ensure people do not "game" the system, but each have their disadvantages. For instance, any system that knows for sure that the people are people could also be used to monitor those people in ways we wouldn't want to support. Most ways of anonymizing users or shielding their identities from negative use of the software, also open up ways for people to make fake users and manipulate the results in that way. I'm sure that problem is solvable, but it's more complicated than "Login in with Facebook" ;-)
The point that I am trying to make, is that there are so many overlapping projects happening here, that the Django Robert's is likely to pop-out very soon, the authentication problem will likely be solved, and what will be left will be the implementation details of:
+ how are people lead through the process? first time user vs. repeat customer
+ what options should they be presented with at each step? (a few as possible ;-)
+ when there is a list of things, like items to vote on or potential time exchange opportunities or whatever, how should they be ordered? Should we place time limits and order by time, or try for huge groups and order by popularity?
+ any brainstorming on how to tie this into alt currency like permabank or aten would be super-helpful. I feel like everyone wants that to happen, but no one has really started that conversation.
in any event, hope some of that helps!
I'll ping this list again when apps or code-a-thon peeps have a meeting. Maybe some of yall could attend, I know we have been repeatedly asking for people to come to the meeting to talk about their needs and wants. The meetings are not just for developers.
much love & chat soon, Bz
On Tue, Jan 3, 2012 at 2:19 PM, ...
<offonoff...@gmail.com> wrote:
Hi there,
I saw your link to the decision making platforms. What I have really wanted for a while is a a web-app implementation of Robert's rules of order (preferably in django) for democratically based decision making through a web interface. I am looing into the links but do you know if any of them are based on Rober't rules?