Loomio

Tagging of members for vote counting purposes

Miles Thompson PublicSeen by 70

This is a feature request, arising out of needs of timebanking nz, who are moving rapidly to use Loomio. Also looking at a couple of discussions on the Enspiral loomio I can see how it would be good there too.

I'll put more details in comments

Miles Thompson

OK, so.

CONTEXT:
Timebanks NZ came to a group consensus to "use loom.io for decisions" at our recent national hui. (Timebanking in NZ basically consists of a bunch of seperate mostly local groups, but we come together as a national body on loomio/skype/coactivate).

PROBLEM:
Right now we are wrestling with :
- On the one hand we'd like to make loom.io memberships available on a fairly ad-hoc way to people 'sufficiently interested' in national timebanking issues.
- On the other hand, if we are going to use it 'for decisions' at least some people are concerned about having some basic rules around who gets the right to vote.

For example, one idea floated is that we have one vote 'per timebank' or maybe some timebanks, being bigger get more votes. etc etc. This represents the fact that each timebank is actually a lot of people is represented at the national grouping (and therefore on loom.io) by only one or two people for each timebank.

FEATURE REQUEST:
Suggested this to @richardd.bartlett and he suggested "have user-tags, and filter the votes based on them. i.e., everyone can state their position, but when it comes to a binding decision you could say, "we need consensus of the users tagged as 'member' for this decision to go ahead."

I love that idea. Even more so if we can have certain rules for some, more binding decisions and more relaxed rules otherwise.

This would also ideally apply to the "19% of members have stated their position (24/123)" stuff you see along the bottom of proposals. It could instead be "82% of 'contributor' tagged members have stated their position" which might be a lot more meaningful in certain contexts.

RELATED:
I can see that this is coming up with the Enspiral loomio as well. I feel grateful to be involved in some of the Enspiral discussions and debates on loom.io but there are certainly other places where they are really just discussing things of relevance to core 'contributors' and 'members' and not (in that case) 'friends'. Or at least as far as the voting goes.

Alanna Irving

User tags is something we've talked about for a long time. Maybe it's time to implement them.

Richard D. Bartlett

Sounds easy but it could open up a can of worms if we're not careful to come up with the leanest possible implementation.

Question: who defines and who assigns the tags?

One option: admin defines, users assign, e.g., admin could set up their group so that users can self-select as 'members', 'contributors', and 'friends'.

Paul Smith

I wonder if what we're talking about is solvable by looking at the subgroups of a group, as really if we're looking at a subsection of the users in a group it is a subgroup.

Could we get to the same point just by adding an option for a subgroup's parent members to vote on a subgroup proposal? Then just look at the subgroup's votes as "binding".

Eg/
In the example for TBANZ we could create a subgroup of users called "Representatives" and come to some agreement having a rep from each timebank (or more than one).
Then when a proposal is created that looks like this: http://www.loomio.org/discussions/1361 there's an option to include parent group members in the decision.
All the representatives are agreeing but someone who's just interested in timebanking might come in and block saying "timebanking isn't work! it's play!"
Which while not "binding" might cause us all to go back to our individual timebanks and change our representative vote?

I'd prefer to see it this way because:

  • It doesn't add another layer of complexity for new members, they're already aware of subgroups.
  • It should be easier to implement as we've already got privacy settings for subgroups.
  • Seems cleaner from a UX standpoint as it's just adding one more option to the flow of Loomio proposals/discussions.

Miles Thompson

@paulsmith you wrote "they're already aware of subgroups.".

And I thought.. Subgroups? What are they?

Danyl Strype

We are struggling with this issue in a closed group I'm part of, and it seems to me to be a social issue, not a technical issue. Specifically, it's a culture clash between those who are used to consensus and those who are used to majority-rules. Loomio is not fundamentally designed as a polling tool (although it can be used that way). It works best when proposals emerge organically from the discussion, and the discussion is used to tweak proposals or come up with new ones, until all concerns and objections are addressed.

It seems to me that if you are going to use Loomio as a formal decision-making tool, rather than a forum for open-ended discussion (for which a web forum or an email list is sufficient), you do need to have admins who set and enforce rules about who gets to participate. Once that is in place, you need to set some rules about what constitutes a binding decision for your group. Only proposals with unanimous agreement (or abstentions)? Any proposal that doesn't get blocked? Ideally, you would have hashed this stuff out at the face-to-face hui, and created a sort of charter including principles of unity, and decision-making rules. Perhaps at the next hui?