Loomio

Invite Jon's friend to this group to facilitate discussion around Loomio's "techno-utopic" undertones

Jon Lemmon PublicSeen by 37

Invite Jon's friend to this group to facilitate discussion around Loomio's "techno-utopic" undertones

proposal by Jon Lemmon Closed Sun 22 Apr 2012 11:21PM

One of my good friends had a look at our pledgeme campaign and mentioned his hesitance about the techno-utopian vibes we've been frontin pretty hard. Anyway, we went back and forth on facebook, and then he asked if he could address my points within Loomio itself, haha.

Anyway, it's making me think about how we can start opening the dialog about the development of Loomio to a wider group. I'm guessing most people feel like we're probably not ready for that yet (and I would agree for the most part), although I think in this particular case... what do we have to lose?

I propose we invite my friend Kim to our group here on Loomio, and then he can create a motion like "I propose you guys use less techno-utopic rhetoric in your external comms" and then we can all just have a conversation about it in there and see what happens. Personally, I'm interested in dirtying the waters a bit... and I think if we're truly about openness, let's put our money where out mouth is and give it a go. Again, I'm just thinking about what we have to lose... and I can't really think of anything

Results

Jon Lemmon
Agree

I can't see how it would hurt

Deleted account
Agree

Agree with the less techno utopic point so yep

Richard D. Bartlett
Abstain

not worried about Kim per se, just feel we should clarify strategy instead of bringing people in at random

Aaron Thornton
Disagree

This is a no for bringing new voices into our development environment. But I am definitely keen to hear this in a test or sub group.

Joshua Vial
Disagree

I think we can do better than just dropping them into our main group

Andrew Cobb
Agree

Having someone help us communicate the ideas and values of Loomio is a more accessible way sounds like a good thing to me.

Alanna Irving
Disagree

I would love to have Kim involved in the team if he wants to work on the project. But just inviting him in for feedback is not the way to go IMHO. Why not give him a demo and get his feedback in person?

Richard D. Bartlett

Basically my answer is the same as for your other question about opening up the public demo: I advocate restraint. I feel like we already have way more input than developer time.

I'm not worried either way about this specific proposal, just a more general concern about this sort of scatter-shot approach to getting more public input.

My guts say we should be bringing groups and individuals on in a very targeted fashion so we can be confident that the overhead of their presence is justified by the value they bring to the development of the project. I.e. I'm sure a discussion with Kim about the techno-utopic undertones would be valuable, but then what? Does he get to have a say on every other motion coming down the lines, or do we kick him out after the motion closes? That could conceivably be valuable, but I would prefer to keep going down the current track: meet people in person, introduce them to the Loomio ecosystem, then get them engaging with the software.

Aaron Thornton

Have to agree with rich on this one those are very good points. Just have to soak her up manually at this stage.

Jon Lemmon

Rich, I take your point, but there's a few things.

  1. Input vs. developer time - I don't think this is related to developer time (i.e. new features), it's related to the way we communicate our ideas to the outside world. This is something we are going to want to think about carefully over the next few weeks before we introduce ourselves to the rest of the world via Kickstarter.

  2. We've been talking about getting expert input/consultation regarding Loomio. Kim is in the process of finishing up his Master's Degree at Victoria in Media Studies and he has a lot of knowledge about techno-utopia's specifically.

  3. Inviting someone external from the team (even just one or two people) to participate in our Loomio group will inform development decisions. For instance, I'm already starting to think about our decision about tags vs. sub-groups again (i.e. it seems that it would be harder to slot kim into a sub-group than it would be to tag him as an "advisor" and to tag us as "core-members")

  4. In terms of future motions, I don't think it will be an issue in this case. If Kim wants to bring up points, he can. I'm guessing he'll remain relatively silent though. And if he does start bringing up a few issues that some of us might not need to be involved in (say, issues related to external comms), then we just need to start thinking about how we can create sub-groups that divide up items so that there is a smaller signal-to-noise ratio. And to be honest, if he does start contributing more, then that's great! It means we get another extremely intelligent person with an expert opinion giving us his take on things.

In conclusion, you say that "we should be bringing groups and individuals on in a very targeted fashion", and I would say... I think this is a very targeted fashion and that we really don't have much to lose in this case. In the future if we want to add someone else external to the group, we can create another motion about it at that point and make a decision. I don't think this is a case of "opening up the flood-gates".

Richard D. Bartlett

Good points Jon. I'm going to stick to my Abstain on the grounds that I don't know Kim but trust your judgement on this one :)

I'm just sticking to the same answer I give to every question ever: "It's funny you should ask, because..."

Damian Sligo-Green

I think you both raise several valid points. My thoughts probably align most closely with Rich in terms of the greater scope of development. My feeling is that it there may be better ways of establishing an 'outsiders' view of the application. Perhaps creating a open-source development/alpha group? It could be made invite only or anything really but could also be a good way of using Loomio to tell Loomio how to improve Loomio.

Just throwing it out there...

Joshua Vial

Happy to open the dialogue and am ambivalent about the techno-utopian vibes point. Right now I would suggest that we limit the main loomio group to people working on the project or early stage beta testers.

Other ways of engaging might be
- voting and commenting on trello tickets
- using the soon to be released general public can create motions feature
- creating a sub group for wider public engagement

guillaume

Ok. I got an error 500 (I think) trying to vote. Bad.
So, I wanted to vote no, because I think the risk is too high to decrease signal vs. noise.
But I really don't feel good about this as I joigned the project only 2 weeks ago and I don't like the idea to have that much weight. Too much power for me now. So I'll abstain.
Same for Josh's suggestion : letting someone else vote and comment on the trello board is (I think) really risky for this same signal vs. noise ratio. We first need :
- to be efficient with the trello board,
- to choose features and make them happen, not to rethink them every other day,
- to deploy them with backups, rollbacks, non-regression (does it make sense in english ?) tests.

Then, we should take more external output.

Jon Lemmon

K, sounds like the general vibe is that people are open to a dialogue, but feel that having it in the "Loomio Dev" group might add too much noise and be the wrong place for it.

I'll go and create another motion about creating a separate group for this sort of thing...