take away

projects/gpp/gpp.md

@@ -13,7 +13,7 @@ title: Situated Docs
 
 ## What do you want to make?
 
-Compile a list of resources to explore the _documentation of coding related practices_ from a community-based perspective, as a process of sharing knowledge and making worlds together around _situated software_.
+Compile a list of resources to explore the _documentation of coding related practices_ from a community-oriented perspective, as a process of sharing knowledge and making worlds together around _situated software_.
 
 To work within the constraints of a structure such as the list will help to think through the complexity of dealing with a double _unknown_: the one of software and the one of situatedness. This complexity will hopefully be preserved and encoded in the relations between different items.
 

projects/take-away/take-away.md

@@ -15,12 +15,13 @@ cover_alt: tannuki tanuki tanuki tanuki
 -   the surface is A3 2 sides
 
 -   ideas:
-    -   blueprint for the thesis writing machine. use the a3 fanzine to plan and reflect on the features and needs for that
+    -   blueprint for the thesis writing machine. use the a3 fanzine to plan and reflect on the features and needs
     -   as a way to document it beforehand ( to worlding around )
     -   enchanting the software
         -   source things to insert in the code as lucky charm from ppl ahah !!
     -   provide starting points for the list
-    -   could be manga based ah ah or maybe not
+
+Some prompts:
 
 ![a spiral](spiral.jpg)
 the making of software in a spiral
@@ -29,10 +30,49 @@ the making of software in a spiral
 -   with all the other actors spiraling around
 -   one can get into the making of software from a distance
 -   size of the spiral is related to: the distance from the source code
--   documentation is following the spiral backward?
+-   documentation is following the spiral
 -   distance from the center is related to specificity
 -   more distant, less technical
 -   try to map the doc system on the spiral?
 
 ![LAMP](lamp.jpg)
-the making of software is a lamp
+Software is a lamp
+
+-   software is a lamp
+-   documentation is the light
+-   you can see the lamp if the light is lit
+-   if it's not lit the lamp is there but you cannot see
+-   can you use other lights to see the lamp?
+-
+
+What about these prompts? They are a way to think about documentation systems and the making of software.
+
+![river](river.jpg)
+Software is a river
+
+-   How to structure the thesis writing machine ?
+-   Which level of granularity ?
+-   I would like to work with small text files
+-   but then the parsing could be trublesome ?
+-   small frontmatter files ?
+-   every entry of the list is a different file ?
+-   that is crazy, it would be much better to work with a DB
+-   but the db is obscure and requires CRUD
+-   that is not a problem...
+-   but i would prefer to have the files with the text thereeee
+-   writing the thesis in git
+-   git writing workflow
+-   wait also true that the thesis and the project are two different things
+-   but still
+-   everything is a file?
+-
+
+## Topological thinking
+
+-   A3 double side: it means: 2 A3 or 4 A4
+-   2 A3 means 1 A3 to provide context 1 A3 to provide a starting point for this
+-   context:
+    -   situated doc -------> excerpts from the proj prop, framed in an accessible way (the outside of the spiral)
+    -
+
+context from the pro pro: