Loomio -> liquid feedback
So I notice Loomio have released their source code:
https://github.com/loomio/loomio
This could be a good opportunity to create a liquid democracy platform.
Andrew Reitemeyer Mon 3 Feb 2014 6:47PM
LF is being developed and improved by a lot of different groups. IMO we should not spend too much effort in duplicating what others are already doing. That said if it is fun then go for it.
Craig Magee Mon 3 Feb 2014 9:50PM
Implementing and maintaining our own fork would require a lot of dedicated effort for very little in return.
The platform is here and we are using it. If another platform is seen to suit us better we can switch to that. Developing and long-term maintenance of our own platform is unlikely to be stable and secure given our size and resources.
Learning they use Ruby on Rails makes me really pleased we didn't go with the hassle of hosting our own Loomio instance!
Danyl Strype Wed 5 Feb 2014 2:11AM
Loomio has been free code/ open source from the start. It was one of the main reasons I supported Pirates trialling it. If people want to contribute code to Loomio, that’s great, and I’m sure the code team would welcome any patches or plug-ins you might want to write.
However, I’m not sure there’s anything you can achieve with delegative voting which can’t be achieved by efficient use of subgroups. I think once more members actually spend some time doing serious decision-making work in Loomio, as the Board did last year, you will get a better sense of what a powerfully simple platform it is.
How about we trial that by setting up a Candidates subgroup to formalize candidates for electorates in the coming election? Any decisions made would have to be approved by the Board and/or an MMORPG/ SGM, but it would give us a set of serious decisions to test Loomio with.
Poll Created Wed 5 Feb 2014 2:17AM
Set up a Candidates subgroup to formalize electorate candidates for the General Election Closed Wed 12 Feb 2014 10:08AM
The responses to this proposal reveals some very different understandings of how Loomio will be used to make Party decisions. This clearly needs more discussion.
I propose that we set up a Candidates subgroup to formalize electorate candidates for the General Election. These candidates would still have to be signed off by the Board or a general meeting. Local chapters should be given some ability to endorse or reject potential candidates based on local knowledge, but the best way to do this would be for their members to participate in the thread on their electorate in the Candidates subgroup.
Results
Results | Option | % of points | Voters | |
---|---|---|---|---|
|
Agree | 20.0% | 2 | |
Abstain | 30.0% | 3 | ||
Disagree | 50.0% | 5 | ||
Block | 0.0% | 0 | ||
Undecided | 0% | 33 |
10 of 43 people have participated (23%)
Danyl Strype
Wed 5 Feb 2014 2:20AM
I see this as a group of serious decisions which need to be made ASAP, but with plenty of rigour (we don't have want any David Hay debacles). Making these decisions via Loomio will encourage more member participation here, and test its usefulness.
Craig Magee
Wed 5 Feb 2014 2:31AM
We have an open-platform, we have an election. Let's see Loomio in action.
David Peterson
Wed 5 Feb 2014 7:11AM
Extra work for no extra benefit. It can be simpler.
Andrew Reitemeyer
Wed 5 Feb 2014 11:19PM
The local chapter should have the say in candidate selection. After all they are the ones who will be campaigning for that candidate. It is nothing to do with the board. Objections should go to the full party.
Does not apply to list candidates.
Tommy Fergusson
Thu 6 Feb 2014 8:33AM
Would need to see someone reliable volunteer to run this right up to the election. If there's no credible plan ready to implement it then it's a dream, not a decision.
Hubat McJuhes · Mon 3 Feb 2014 9:52AM
I took the liberty to change the description slightly to express more clearly what you seem to want to say. Unfortunately I don't seem to be able to do the same to the title.
I understand you would like to encourage people to join in the development of loomeo towards implementing core aspects of the concept of liquid democracy. It surely will not become liquid feedback, though, as this is the name of a particular other implementation of those concepts.
But the title as it stands now suggests you would actually want to dump loomeo and switch to liquid feedback instead (which I would passionately support once we reach a certain number of members).
Nevertheless, loomeo is written in Ruby on Rails which is a language I always wanted to play with.
Thank you, folks of loomeo, for opening up your code. This is very, very cool.