The fourth thread of the evolution project is to develop learning and leave a legacy from three years’ operation of meet. coop. This thread below contains the brief, job list, actions log and discussion.
meet. coop is a radical experiment in provisioning, mobilising and stewarding digital means for organisers, in the commons. This is one reason why members join meet. coop, and one reason why organisers in our communities more broadly pay attention to the meet.coop project. Thus part of the work of evolution at this point should be harvesting the learning of what will amount to more than three years of practice - what was well framed and executed, and what wasn’t - so that other initiatives in digital infrastructuring in the commons might build a stronger and clearer frame for themselves.
Thus we need to:
Convene a ‘learning’ pod as part of the migration plan.
Design a method and outline a programme of activity that might harvest insights and present them in a usable form - for example, as design patterns for commoning and as stakeholder stories.
Make a durable home for media generated in this ‘legacy’ project
As part of this programme we need to:
Archive the media spaces of meet. coop: the Discourse forum, the interim handbook, the cloud database of internal documentation.
Interview multistakeholders in the project, and
Solicit and curate their accounts and reviews of the project and their expectations of the project, in any other form they would like to offer.