Tag Archives for resources

Teaching Ourselves & Each Other: Blogging & Sharing

Theory: Making space for folks to engage in self-teaching is empowering others to teach themselves

An opportunity to honor agreements about process and collaboration:

  • With the Femme Conference, when we agreed on using google-docs as part of our process, that meant we would use the file-sharing and form-making capacities
  • Some people kept sending docs as links not “sharing” –> sent gentle reminders twice over a few months to “Share” so we can all access
  • Some people sent me g-docs with their forms in them –> sent a gentle reminder to make forms in gmail and “share” it with me and the Collective gmail account.
  • Are these details kind of trivial? NO! They determine whether the entire technology setup is going to be collaborative or a shitstorm of emails and confusion.

An opportunity to give people access to resources and to support accessibility by providing resources:

Blogging was happening a lot by four committees and not at all from the other five committes. In the interest of accessibility, I created a google doc how-to and shared it. [download it here] It contains both direct links to WP’s documentation on blog posting and a step-by-step Best Practice Guide that uses screenshots from the actual femme2012.com blog to help folks see exactly what/where they are doing:

 

Collaborative Technology Reasoning: Beg, Borrow, Buy

Why collaborate with a specific technology? Why not just get our work done some other way and all hand it in? For starts, in a collective–or any horizontal project–there’s no manager to hand it in to, no boss, no one to organize the work for you but you. Getting organized is a systems-level problem that best be addressed as soon as possible.

And for projects that have principles that base around justice, equality, accessibility, and collective or direct-democratic decision making, the choice of platforms is a political decision.

For the 2012 Femme Conference, we needed to set up a system where 14 core organizers and 30 subcommittee members can work together — both in terms of accessibility and capacity. Systems we chose thus had to be not overly hard to learn or use, but still must allow for organization and effectiveness.

We looked at possibly using:

I tried to get people to use Crabgrass [open source!] or Basecamp [more useful!], but the request from the majority of the other organizers was that most people had existing Gmail accounts and were familiar with the interface, so we went with G-docs

  • Theory: Choosing the achievability of agility and accessibility over principles, choosing to fight battles later with other technologies. For example, I decided to force WP participation rather than “force” the use of a platform that no one would use.

In an ideal build we’d have Crabgrass or Open Atrium sitting on a Drupal site, but in an ideal world we’d be paying someone to build this. Better to pick that which will actually happen and — most importantly, that which people are willing to interact with.

  •  Theory: I like to occassionally remind people that Gmail is a “begged” resource that datamines our every word typed in, just to raise awareness of the issues in using “free” software that’s not Free/Libre software.