Sprint/2022/Notes Andrew

How do we approach building memory and sharing knowledge in a complex, multiple perspective and open ended process?

what sort of participatory memory making tools can be used? facilitators tools? what is necessary to be remembered associations have a bureaucratic memory of events, activities, (what, where, who), statistics.. But what is not remembered. GIT/Wiki perspective which records changes, but GIT allows spin-offs/forks Each time there is an change, that is the best time to record the change. Visual conservation/layers and backtracing example

Collectively agreed central page, ToC with peripheral materials, notes, images in a collective pool submitted by many.

There is a need to have common competence in using the technical platform, and it needs to be easy to use.

There is a need to have this practice as part of the shared time schedule to record & document. Is it the hosts' responsibility to arrange thing or is it the participants who gain concensus?

Zine making is way to make a quick draft process.

Checking in at the beginning with each other, but also necessary to check in with the past. Does the description and materials still hold as valid?

Practices which encourage collective update obligation, not just individual update obligation before the gathering starts.

We are already fragmented, so choosing a platform and sticking with it.

Google Drive vs Wiki vs Etherpad

What to keep and what to let go? Maybe it is necessary to clean out each year. Copy and make as PDF, print and put into library.

We have not yet designed rituals for dealing with our memory and storing.