• mayfirst tool -en

last modified January 10, 2009 by mallory

Summary

May First / People Link has developed a Free and Open Source Software to foster collaboration during self-organized activities. The software's final product is a document that has been generated by a decentralized group during a fixed time interval (2 hours, for example). The document, as it is currently coded, allows for 10 "Rights", each of which are generated, edited, and endorsed by smaller groups via a restricted-access website or a local server. As the software has no predetermined agenda or topic, "Rights" can also be Actions, Resolutions, agenda Topics, Paragraphs in a larger document, etc. Currently, the software and interface are bilingual and translatable (English and Spanish). Currently there is no capability for live chat or video conferencing, although increasing language and communication capabilities are ongoing. A link to an example of final document is here. An interactive link to an example of the scribe interface: http://ir.dev.mayfirst.org/ with room access code "b".
Link to our OpenFSM space Join our Mailing List for active discussion.

Specification for collaborative workshop software

This is a specification for the Collaborative Democracy Workshop, an exercise in collaborative democracy originally developed by May First/People Link. Our Open FSM space is here.

Vocabulary

These specifications make use of short-hand terms that can be ambiguous. This is an attempt to settle on fixed meanings for the purposes of discussion.

Workshop
A concrete instance of running this exercise, happening at a specific time, in a specific set of Rooms, with a specified set of human languages. The number of specific languages in any particular workshop is called L. L < 2.
Room
An environment in which a number of Groups are physically present. Each room should have a projector showing the current state of the workshop (the "board"), a link to the central workshop server, and a (wireless?) network to connect the scribes. When there is only one room for the workshop, it makes sense for the server to be physically located in that room.
Group
A small breakout cluster of people, identifiable during the workshop. There is exactly one Scribe per Group. Groups have been identified by color names in the past, but should probably be identified by number, icon, or the colors themselves in a multi-lingual environment. Since there aren't that many distinguishable colors (and projectors have a notoriously unreliable colorspace), icons or numbers should be used to allow for a larger set of participating groups)
Scribe
A person with a laptop or other terminal connected to the network, with the technical ability to add, edit, and endorse Rights.
A Right is one of the items under discussion/debate in the workshop. There is a maximum of R possible Rights in the workshop (R == 10, currently). Each Right is versioned; when an edit is made, a new version of the Right is created. A particular version of a Right is endorsable by any Group. Editing a Right clears all existing endorsements, and adds an endorsement by the editing Group to the new version. A right is identified in shorthand by
Translation
A Right exists as an idea, but the idea must be expressed in human language. An expression of a right in language X is a "Translation" of that right. Each Right should have exactly one Translation per language supported by the workshop.
Endorsement
A specific version of a Right can be Endorsed by any Group. The endorsement means that the group believes that Right is worth promoting. The projector in each Room displays the current list of Rights, ordered by the number of endorsing Groups.

Workflow

The introduction to this workshop has been scripted in English, Spanish, French, and Portuguese. Below is a proposed workflow that has never been executed quite this way at an actual Workshop (as of 2008-09, anyway).

  • There is a presenter in each Room capable of speaking the languages of the participants in that Room.
  • The presenters in a room get a rough count the number of participants in that room, let's call it N. The exercise seems to work well when groups are composed of roughly 5 people. This means that there should be ~N/5 Groups in the Room.
  • The presenters give a basic outline of the exercise to the participants, and solicit N/5 Scribes. Scribes should be comfortable working with a simple web application interface.
  • All scribes are set up with terminals (laptops?), connected to the network, and ensure that they can see the central server. They are asked to distribute themselves evenly around the physical space in the room, and given signs to display associated with their group's identity (number? color? icon?).
  • Non-scribes count off, and physically re-locate to form small clusters around each scribe.
  • The presenter manually injects an initial Right, and points out how it shows up on the board, asking if there are any questions. It's probably a good idea to make this "starter Right" absurd, so that it doesn't shape what people think they "should" be including. For instance, "Only peopl who eat cheese should be allowed on the Internet."
  • Usually, someone in the audience will complain about the mistake (the missing "e" in peopl), or about the absurdity of the proposition. (if this doesn't happen, it should be easy to solicit such a remark from the audience by asking if anyone sees a misspelling). The presenter asks the complainer what it should say instead (pointing out that they can change not just spelling, but content), and asks them to ask their group to ask their scribe to make the change.
  • Once the whole room sees the resulting revision (and the new endorsement), the game is on!
  • The presenters in each room should make it clear how much time is left with verbal announcements. Announcing 10 minutes, 5 minutes, 1 minute, and 30 seconds seems to work OK. (perhaps the board should display this as well?)
  • During the time that the Rights are under development, the rooms can get pretty hectic. Presenters should stay alert, and occasionally do a circuit of the room, listening to the discussions, and observing if any Scribe is having technical difficulty. Presenters should help troubleshoot if problems do come up.
  • When the time is up, the presenter should read out the resulting Rights, along with the number of endorsers.
  • There should be a significant amount of time remaining in the Workshop after the clock has run out to have discussion among the participants.

Discussion Questions

Presenters in each room should encourage discussion afterwards, first by simply asking:

  • Does anyone have any comments about what just happened?

If people are shy, some leading questions can be useful:

  • Were there any Rights you were surprised to see come up? Which ones? Why were they surprising?
  • Did you change your mind about anything during the workshop? What about?
  • How did your group make decisions about what to do? Did the scribe do what you expected?
  • What frustrated you about the experience? Why?
  • Did you wish the process worked differently? How would you prefer it to work? Why?
  • What is the relationship between the process you just participated in and the Internet as a whole? What about larger society, beyond the Internet?
  • We decided the rules for this exercise when we planned the workshop. Who decides the rules in the larger Internet? Why?

History

The workshop has been organized 6 times over the last year and half, including:

 * US Social Forum, June 2007, Atlanta, GA
 * Grassroots Media Conference, March 2008, New York, NY
 *  Allied Media Conference, June 2008, Detroit, MI
 * Grassroots Use Of Technology Conference, June 2008, Boston, MA
 * Critical Resistance 10, September 2008, Oakland, CA
 *  Americas Social Forum, October 2008, Guatemala City, Guatemala

 Prior to the ASF, we were limited to one language and one room. At the ASF we significantly expanded the workshop to include two languages (spanish and english) and two rooms in two different cities.

  • The number of participants in each Group has ranged in size from 3 to 8
  • The total number of participants in each Workshop has ranged from 12 to 60

Steps for Using this Software in Your Own Activity

  1. Answer the following questions:
    1. What is the title and description of your workshop?
    2. What is the intended topic of your workshop's Rights?
    3. Which languages will you require for your workshop?
    4. What is your location?
    5. What are the locations of your workshop?
  2. Email these questions and your answers to mallory@mayfirst.org
  3. We will respond to your request with further steps towards fostering your fluency with the software, depending on your specific needs.