Sharing and software (in timebanking)

In this talk to the Global Exchange Gathering last week, I show how the competition between timebanking platforms is a result of the software structures, and how even if different platforms can't share code, the can still service their users by becoming more interoperable.

The talk was very well received perhaps because I spent the previous five days in reconnaissance, and thus was able to say what this audience needed to hear.

Sarah, have a look at

Sarah, have a look at,, and There are heaps of good community-building website initiatives popping up online all the time. One problem I've noticed, after more than a decade watching and working on them, is that too many of them are created by novice web developers, who reinvent the wheel instead of using well-supported free code, or create something genuinely new, but don't build an open source community around it to ensure ongoing maintenance and development is sustainable. Both Matt's Drupal module and Community Weaver (also based on a set of Drupal modules) solve this problem by releasing their code, and encouraging others to work on it with them, and I'd like to see community ICT support embrace this model, for the reasons Matt describes in this talk.

What I would find especially

What I would find especially interesting are gift- and sharingplattforms

Post new comment

The content of this field is kept private and will not be shown publicly.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Allowed HTML tags: <a> <em> <strong> <cite> <code> <ul> <ol> <li> <dl> <dt> <dd> <img> <blockquote> <div>
  • Lines and paragraphs break automatically.

More information about formatting options