call with estragon and e.zn

chapters/02_backdoors.md

@@ -1,14 +1,23 @@
 ## 2. Documentation as a backdoor
 
-```placeholder
-- when the entry points are blocked one has to search for backdoors
-- little context for backdoors
-```
 
-Code documentation is a technical object used to create entry point for people to participate to programming practices.  But could it also be a way to inject context around code. ?
+Exploring and stretching coding contingencies using code documentation practices as a backdoor to inject context in software.
+
+Coding contingencies are conditions we found ourselves in. Not entirelly by chance, but on entirelly by choice as well. Sometimes these contingencies are economical: in order to work in this studio, you need to program with this framework. Sometimes affective: a friend shares the excitement over a new visual programming language. Sometimes
+
+
+Politics of participation & representation
+    from transfeminist servers to queer motto api to 360 degrees of proximity
+    from alt-text poetry to p5js inclusivity guidelines to soupboat
+Aesthetic practices
+    uxn ecosystem: introspective programming
+    the screenless office and chimeric worlding
+    aesthetic programming and software studies
 
 
 ```placeholder
+- when the entry points are blocked one has to search for backdoors
+- little context for backdoors
 - not only to participate in the making of software
 - but also to inject values,
 ```
@@ -36,7 +45,7 @@ It's an approach that helps us to think about software as a cultural object. Som
 
 An object that, in turn, can be used to probe its surroundings. Who is developing? Who is going to use it? Who is paying for it and why? How is it structured? It is a big and centralized system or a loose collection of small and interchangeable tools? How long is it supposed to last? How can be fixed if it breaks?
 
-The main focus of this research is to explore software documentation as a surface where these kind of questions can be addressed. A place where the complexity of code doesn't blackbox ideas, and choices behind development can really be open source.
+The main focus of this chapter is to explore software documentation as a surface where these kind of questions can be addressed. A place where the complexity of code doesn't blackbox ideas, and choices behind development can really be open source.
 
 A way to situate programming in specific contexts.
 
@@ -69,7 +78,7 @@ from reaching a public to creating a public
 rethink participation in coding practice through femminist perspectives is not just swapping who can participate and who can not. doing so would just replicate current forms of exclusion.
 
 the trans\*femminist servers wishlist engages with a more messy entangled complex way of understanding participation and technology
-a way that open up for plurality, for questioning, for instability, for safety, for situatedness
+a way to open up for plurality, for questioning, for instability, for safety, for situatedness
 
 1
 
@@ -99,12 +108,34 @@ fluid processes - not purely technical architecture, but affective infrastructur
 process of collective learning and knowledge transmission 360 degrees of proximities
 
 ```placeholder
-questions for artemis and mika regarding sister server and 360 degrees of proximity
+call with artemis and mika
-- is this a feminist approach to documentation? what do you see different from other kinds of documentation?
+
-- how does it work? which methods and procedures are involved? who is the public and how does it influences the process? what's left after the install party? written docs? printed materials, recordings, other?
+- ask to record for note taking (not published)
+
+- overview  code documentation
+- entry point / backdoor
+- surface: language formats and approaches
+- practice: participation, representation, aesthetic
+
+- documentation practices and politics of participation
+- from wishlist for transfeminist servers to queer motto api to 360 degrees
+- relation between wishlist and code documentation
+
+- about 360
+- where does it come from?
+- how does it work? already started?
+- does it involve also writing code documentation?
+
+- situated code documentation? iterative? always the same? always different? depends on the context?
+
+pls use our nicknames
+estragon
+e.zn
+
 ```
 
 
+
 #### from alt-text as poetry to the discussion about accessibility in p5js to the soupboat
 
 alt-text as poetry is a project by Bojana Coklyat and Shannon Finnegan

notes.md

@@ -2,6 +2,7 @@
 
 
 
+
 ## first chap structure
 
 consider to readjust a bit the structure of first chapter, swapping things in order to have issues at the beginning and approaches and methods at the end