This post is a response to a number of high level discussions about using a single Drupal instance to serve many communities, each using their own currency. Running many Drupal instances can be done with reasonable efficiency, though they take time to set up, and there is a trade off between their independence and the amount of time and expertise taken to train, administer and maintain them. CES is already running in one instance of custom built software and its success is testimony that few of these kinds of communities value independence over convenience.
Last month's meeting at Tiocan, near Geneva was pivotal for Community Forge, as it was the first time we had really engaged with a broad spectrum of users, potential users, and other actors in the movement. We made tangible progress on many fronts, but the headline issue, how we should coalesce into a Community of Practice wasn't properly addressed. Nor was it addressed at all in Lyon.
Initially, Tim and I decided that we wouldn't go to Lyon, as it was purely academic, and as practitioners, we neither had time to write an academic-style paper, or listen to theories that had no bearing on our work. However as time went on, and the practitioners day was announced, and we later timed our 2011 Community Forge General Assembly to follow it directly, more and more of our colleagues appeared to be coming, so in the end Community Forge showed up in force.