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.
Background and overall project notes are here Evolution of meet.coop - Background and framework. This thread has parallel threads:
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:
As part of this programme we need to:
We also probably ought to:
commons.hour Series #2, Welcome to the dance of infrastructure project so that as much work as possible from that commitment can be performed within the meet. coop evolution framecommons.hour gatherings to process the learning from three years of meet.coop practiceWrite a brief - above
Open job list (logbook) - here!
Open public forum thread - here!
Publish & discuss @ forum - started 06feb2023, here.
Convene a learning pod
Design a method, outline a programme
Archive the media spaces of meet. coop: the Discourse forum, the interim handbook, the cloud database of internal documentation.
Make a durable home for media
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.
I put out a crowdsourcing call for some gift work in this aspect of the evolution project . See A learning project - Some gift work?