Realtime Collaboration

Yes, this is quite high on the roadmap: https://trello.com/c/qeGivEzn

Expect a big update in this space later this year.

Since this is important to you, can you expand a bit on how you'd see it working? What would your ideal user experience be?

I'm really happy to do that. I'm going to need about a week or so to get to know loomio to make some recommendations. I'd like to let you know about my use-case.

I'm starting the 21C Dawn Foundation, a guiding body for a resilient mesh of project-oriented corporations that exchange equity with one another to enhance member individuals and corporations ability to take risk. Once I saw Loomio, I knew I'd found something really special. TOday, we use quip for nearly everything, and likely will until Loomio supports the level of interactivity that we desire. Today, we use quip for everything-- from to-do lists to decision-making, and of course, for collaboration, too.

If anyone else out there has experience with Loomio in a business setting, I'd really like to hear it :)

Sounds really great @jacobgadikian ! My main experience with Loomio has been in business settings. Check out this blog for a bit more on that:
http://blog.loomio.org/2014/06/17/management-hacker-gary-hamel-interviews-loomio/

I am very interested in how you scaled up in size. What tools supported the scaling? Obviously there was a ton of sheer human networking, but I am guessing that you had some sort of a plan as you moved up in terms of members?

150 is about the cap for us. We are not opposed to going above that, but at that number we would hope to form several 75-150 person "cores" so that each "core" or "cluster" could have genuine knowledge of the other members.

@jacobgadikian - I'm curious, if your foundation is so happy with Quip, why you want to switch to Loomio? (I'm not questioning your decision, just interested in the reasons. I like Loomio quite a lot myself.)

Because if loomio had Real time collaboration it would be more like the UR-quip. I don't have too much use (but I am uncertain I only learned about Loomio today so I may get it installed on our servers tomorrow and discover that I have a billion uses for Loomio. )for the present iteration of Loomio.

I love quip but here's what it is missing:

-self-hosted

-open source code

-smart documents instead of just collaboration

-calendaring

-task management

-spreadsheets (ethersheets can give this to Loomio)

-better web publishing

-should be able to function as a cms for rapid web dev

-the ability for anyone to leave comments on anything on the published web page

-mind mapping with computer analysis and assistance in modeling, coloring, and relative element sizes(my partner Dan has this on lockdown)

-mind map mode should be able to visually represent the flows between nodes in a network business

-presentations

-ide

-P2P desktop client with built in VPN utilities based on XUL

-voting

-team web browsing with collaborative bookmark and highlight arrangements like pearltrees

-automated lexical analysis

So basically I will stick with quip for now simply because I positively love real time collaboration and think it helps our team be more effective. I know that is a ton of work, but hey, if we get all that done, we can have truly clear consciences because we have truly done a service to humanity.

Best,

-Jake

Sent using CloudMagic ( https://cloudmagic.com/k/d/mailapp?ct=ta&cv=5.1.3&pv=4.4.4 )

I like that mealtime collaboration!

I'm skeptical of adding all of that to this platform for decision making. If we need realtime collaboration, we should be able to do it in meatspace.(non virtual) Or over wise there's googledocs and our programs to use. Not knowing what quip is like, or whether loomio needs such business heavy functionality, at least that is what it sounds like. I will abstain.

What % of votes have a higher turnout? Lower? Just curious......

Meatspace is really impractical for a multinational networked organization, even though I agree 100%.... It is ideal. To get an idea of what quip is like head out to quip.com ( http://quip.com ).

:)

To

The problem with having teams use several applications to get their work done is that some team members will get confused along the way, information needed here will be stored there, etc.

Hence the desirability to be able to access the functionality all from one place. Ideally, you wouldn't have to replicate the functionality, just link to it.

So I support this initiative for real-time interaction, but in a way where you leverage existing (and evolving) technologies and platforms by linking to them, instead of diluting your focus.

I think it's important to frame every feature request with decision making being the goal of the feature. How does realtime collaboration help us make a decision? Collaboration is critical, but does realtime collaboration scale beyond a small, close knit team?

I want to say that I agree with Jean-Daniel, and need to comment to Ben Burton that small, close-knit teams exist on a global basis now. They,too need to make decisions and do work. Work flows out of decisions very often and so it would be quite handy for a Loomio installations to include some of the RTC enabled open source apps out there.

Recently I have gotten a taste of what software development really involves, and must comment on just how well your team is doing. Thank you for your dedication to an idea that brings massive value, even if it may not bring much financial reward.

I published an outcome on this. Please do let me know if that is the sort of style you'd like to see used and how well you feel it reflected the voting and comments.

In the hierarchy of small team collaboration, making decisions together is right up there, at the top. Decision making engages the future, and is a complex task.

At the bottom of the collab. hierarchy, we'll find random chats, posting updates, etc. Not complex.

It is probably fair to say that all serious team work implies making decisions AND that no other online "collaboration" space effectively supports that level of activity.

So, it's not about collaboration versus decision making. Decision making is collaboration at a senior/higher level.

Enabling decision making requires a cadre that has sufficient bandwidth to capture the full complexity of the decision making process and the content that travels through that process, in a way that is timely enough that complexity is not lost (forgotten) by the passage of time.

This is a strong argument in favor of leveraging existing and evolving real-time collaboration technologies to improve the bandwidth offered by Loomio in support of Loomio's mission of enabling decision making in teams.

As an (just an) example, it could be an API that opens a Google Hangout session from within Loomio for a conversation, associated with a recording of the conversation, and a comment space where a participant note taker can summarize decision proposals the group converged on, and any actions decided upon.

Several such APIs could be created over time to bring in real time collaboration technologies as they become available. In the years to come, we'll have probably have avatars meeting in virtual worlds, designing 3D structures, in sessions made accessible thru an API in Loomio. Loomio then closes the loop, formalizing the decision making. This gives Loomio the role of documenting, officially, that a decision was made, and how it was made.

" we’ll have probably have avatars meeting in virtual worlds, designing 3D structures, in sessions made accessible thru an API in Loomio. Loomio then closes the loop, formalizing the decision making. This gives Loomio the role of documenting, officially, that a decision was made, and how it was made." (I know that we will be chasing this goal, and open sourcing the product during a 6-18 month timeline)