From f1d0d6068580b9fd75bea3decb0a63550f377543 Mon Sep 17 00:00:00 2001
From: "kam (from the studio)" <luzzanafrancesco@gmail.com>
Date: Wed, 23 Nov 2022 18:57:52 +0100
Subject: [PATCH] list

---
 list.md | 49 ++++++++++++++++++++++++++-----------------------
 1 file changed, 26 insertions(+), 23 deletions(-)

diff --git a/list.md b/list.md
index 807ec3a..f0e5574 100644
--- a/list.md
+++ b/list.md
@@ -11,23 +11,22 @@
 -   how to be a developer™
 -   or how to do things with code without being a developer™
 -   that is actually the case for most of the people that enjoy coding
--   or a way to enjoy coding more
--   **situated** refer to the context of this research
--   fine tuning about
--   kind
--   size
--   of software to look into
+-   or a way to enjoy it more
+-   **situated** refers to the context of this research
+-   which kind of software to look into
 -   _situated software_
 -   software built around the needs of a community
--   _example_ xpub has a small server
--   `server = a machine connected to internet`
--   the soupboat
+-   that can be specific instead of generic
+-   that does not need to scale
+-   _example:_ xpub has a small server
+-   `server = machine connected to internet`
+-   we call it Soupboat
 -   _url_ `hub.xpub.nl/soupboat/`
 -   it is a shared space online
--   where we can prototype websites, hosting applications, etc
+-   where to prototype websites, hosting applications, etc
 -   a place to call home in the internet
 -   very public yet very intimate
--   _??_
+-   and now a series of _??_
 -   how to share knowledge about
 -   how to run
 -   how to manage
@@ -35,39 +34,42 @@
 -   our server
 -   could this knowledge be useful for others than us
 -   could this small system support others similar ones
--   how _situated knowledges_ inform the knowledge surrounding our tools
+-   how _situated knowledges_ inform the knowledge around our tools
 -   how different situations generate different documentations
 -   and how different contexts resonate together
+-   _??_
+-   **the plan** to think through these thing is to compile a list of resources
 
 <br>
 
 -   ![list](img/list.png)
 -   **a list**
 -   to explore the process of sharing knowledge and making worlds together around situated software
--   the plan
 -   compile a list of
 -   _devices_
 -   _thoughts_
 -   _tools_
 -   _references_
+-   _excercises_
 -   _hints_
 -   _fieldwork_
--   _excercise_
 -   to articulate software documentation as a form of care
--   a list
 -   without claim to catch everything
 -   where order
 -   matters
--   but the relations between items
+-   but relations between items
 -   matter more
 -   a space to sketch contours
--   and then draw through
+-   and then draw out the borders
 -   a soft structure
--   respect the heritage of each item
+-   to respect the consistency of every items
 -   without worries of tangling them together
--   experiment with the list
--   as a writing machine
--   that seems already fun
+-   a texture where to weave
+-   different voices
+-   different registers
+-   different genres
+-   list as writing machine
+-   seems already fun
 -   **here some prompts:**
 
 <br>
@@ -76,14 +78,15 @@
 -   **documentation as a form of care**
 -   _care for who?_
 -   the actors involved
+-   (human and more-than-human)
 -   developer
 -   user
--   mantainer
--   the community
+-   community
 -   everyone in the range of 1km from the source code
 -   aha it's a nice image
 -   because the source code is not just in 1 place
 -   but cloned in different machines
+-   care for the future life of the software
 -   _care for what?_
 -   infrastructure
 -   accessibility