Loomio

Make a Plugin Version of Loomio

Danyl Strype PublicSeen by 56

The Meshed Coop is now using RedMine as our collaboration platform, as it offers more features than CoActivate (tickets, forums, charts etc)
http://www.redmine.org/

RedMine is written in Ruby on Rails, and is designed to allow new features to be added in the form of plug-ins. It's been proposed to implement a Loomio plug-in we can use in RedMine. With some planning this "containerization" of Loomio could be used with other RoR platforms, and potentially even CMS in other language and frameworks (Drupal, Joomla etc).

Danyl Strype

Before we allocate any resources to this, we'd like feedback and questions from the Loomio team. Is there a better way to achieve the same result? Can use an API instead? Could a combination of single-sign-on and importation of page style into Loomio from our site achieve the same objectives of seamless and integrated user experience?

Jon Lemmon

@strypey can you expand upon exactly what it is that your group wants and why? As you probably know, "plug-in" can mean many different things.

Danyl Strype

@jonlemmon the main issues are:
* security: as our co-operative business gets up and running, and we start taking on serious clients, we need to think seriously about what online platforms we use for making business decisions.
* dogfooding: as a tech support co-operative, it makes sense to self-host our own collaboration tools
* platform proliferation: to reduce this, we are already in the process of deprecating CoActivate, and shifting it's contents into our RedMine platform.

For all these reasons, one member talked about adding a "voting engine" to the web forums to replace Loomio. My counter-proposal was to somehow implement a private instance of the Loomio interface inside RedMine.

I figure this could be done one of two ways:
1) "containerize" the Loomio engine so we can run an instance of it inside RedMine
2) "containerize" the Loomio UI as a section of our RedMine UI, and use an API to connect to back-end hosted by Loomio.

The advantages of option 1) is that the Loomio server would not have to host us, and any code we develop would be contributed back to the Loomio project. However, if you already intend to develop an API, it might be a better for us to use that, and give you guys some cold hard cash for hosting.

Jon Lemmon

@strypey we intend both to enginify Loomio and to create an API. However, both of these items not on the immediate agenda. Usability improvements, building basic missing features, and performance improvements are all top of the list at the moment. So the stuff you're asking for is probably going to have to wait for a few months on our end.

Danyl Strype

OK, so let's say Meshed decide to invest some time (or cash for someone else's) to make this happen. Does the Loomio crew have a preference on whether we invest in the API approach or the "enginify" approach? If you don't mind either way, that's all I need to know, and I'll leave it to the coders to decide which is easier/ better for them.

Jon Lemmon

@strypey at this point i'd say enginify. Although for it to be useful to us it'd need to be done in a way so that we could use the Loomio engine as a way to split up our content which shouldn't be in the open-source app (e.g. our front page and our donate page). The open source app would be the engine, and we would include it in our parent rails app which would contain the front-page and the donate page.

At least this is how I've imagined it thus far...

@robertguthrie might have some thoughts

Robert Guthrie

I think both approaches would be nice to have - they serve pretty different use cases. However both represent a lot of work.

Megan Salole

Being a non-tech dude, this might sound silly - but I am just going to say what I would value from a user perspective.

I currently use the Commenting feature on Google docs to help ratify/discuss/agree each paragraph in a document shared with a group of stakeholders.

I essentially put "Agree? Disagree? Discuss." at the end of each para, highlight it, and > Insert Comment. Then each paragraph can be reviewed on the page.

I would love it if I could insert a loomio decisionmaker widget at each paragraph level instead so that we can both use the traffic light decision making tool within the page, as well as being able to track the outstanding decisions within my loomio dashboard. BTW - "notifications" somewhat trivialises the items contained within (because I connect the concept of notifications with Facebook - and reading them is optional). "Decisions in progress" or something like that might be a better term, because actually the decisions are all really important, not optional as are FB notifications... (does that make sense?)

Benjamin Knight

I like this thinking a lot @megansalole!