On breakdowns, malfunctionings and failures



General comment on (mal)functioning of presentation script: 
    
Great. Groups are better between 5 and 7 people and need to be equal in size. The 30 minutes are good and keep things concentrated; sense of other groups working simultaneously on pad is beautiful and now further one-to-one connections need to develop in order to find out what really happened. Interesting miscommuncation: several interested people showed up around 16:00, routinely expecting that there would be plenary presentations, and found out that they literally had no entrance without an ip-address (also, discussions were of course on purpose not in presentation mode and therefore hard to grasp). We realised that creating README files per project was useful (method introduced last year), because it took over the function of the presentation, and we could simply link to them.

Group 0 == Group 4

Random group algorithm FAIL ! totally!
but totally fun

P: ... my software was not functioning ... so I captured my screen using sticky tape. made markings on which part of the screen to collect.


../images/Screenshot%20from%202015-08-25%2015:47:17.png

GH: I don't know ... not sure about the sentence ... "We love it when things fuck up" ... some people can deal with feeling lost. It is maybe too frustrating, to see people struggle with the network. Break down is interesting, but also difficult. Planning: starting at a certain time, but than it did not happen. It worries me.
DP: Do you think malfunctioning can be an excuse?
GH: Maybe it is ...
HL: It creates extra efforts.
DP: interpretations vs expectations
GH: Too chaotic?
DP: Things come from chaos.
Interesting that the sentence mentioned above was edited in the pad just before the discussion started. Somehow I wonder if there is a relation in wanting a process 'open' and it ending up being frustrating..
HL: Unplanned things at lunch is another thing than getting lost
DP: What does it mean to be lost. What do you mean? It might be inspiring.
Dennis : Two different types of lost. Getting lost in tools, and in procedures. Aspect of a school. Who is responsible? Are people also responsible for not getting lost in ideas? 
It's good to get lost in your tools, it forces you to learn it. You'll encounter problems you can not deal with, yet finding a way around within your means is inspiring.
HL: Some people come up with ideas they can't realize. Yet then finding an intermediate which fits is interesting.

Tiago: first days lost socially, if you are not from here ... getting a map. Exciting partially. Could be a source of breakdown. mapping who is who... no introduction... Not sure if people left for that reason.
My: People did leave. Why? Expectation to be more helped in a certain way.
HL: Are there people who left the whole school because of this reason?
FS: There are indeed people who left. For people living in Brussels it's easy to leave if the summerschool doesn't clearly enough state its urgency. It not neccessaraly a problem. Perhaps it's about stating it in advance

Tiago: it did not feel so different than projects I was part of.

DP: people might come from a distance from tools .. it is getting used to making space for this. Could we propose it differently?

HL: Maybe we shouldn't call it school but rather common exploration.

Group 1

(now we even have 5 groups ??)
we are 1 + 4 a few displayed while we are talking.

phil: something that happened last year as well as this year. being part of a not-popular track.
interesting dynamic of focus... makes it hard to diversify or push the projects along
technical outlook is not the same at every stage
if it starts small it stays small...
last year there were refugees
space is different : physical space last year created other circulation : small size room when too much people, the ones who arrived at 11am would join another track
our circulation is bad. blood not flowing or clogging
there were three divergent streams that then came together. {Trinary logic}

not much dialogue at the track table / discussion moments not organised?

catherine: not the while group joining every day, in general this was different last year.
people feeling like they can join or not... different kind of participation.  not a question of being on time, some were also fnishing late in the evening. Another kind of schedule from 11 till 8

"people were not hungry at 13.30"
"some people did! at 13 already!"

risotto @ poissonnerie

nice to have 1 day open - walks on Sunday - was a nice opportunity for exchange between tracks/ ideas etc...

meditation session was very nice

small presentations can work well - for example the presenation by hans between the text-generator and the training-common-sense tracks


GROUP 2

Frederick: time limit on the code on the entry door didn't work
issue used as example to expose the hidden elements of the organization of relearn...
the internet broke!or did it?
M:
     ssh tunneling aware it normally does not work perfectly, a lot of restarting, fixing-->making the effort, becoming aware of the structure
ethernet cables were available (especially for installing things)
found our own solutions--it is documented! ([[Tunneling_to_the_outside]]
"i didnt mind 'frustrating the connection'!"
proxychains as a workaround (see: proxychains) ..
no single solution to make a network and to connect to the internet
there should be a documented path of getting more complete access to the internet
- the time of the school: it could be longer! two weeks!?  > Agreed 
the didactic purpuse was to say "there is no singular internet, no singular network"
NO MORE TEA!
A: not efficient doesn't mean it's not working
There should be working group, talking about the projects on the 2d day to have time to achieve a group project at the end of the session
A: It was good not to have internet the first day round, people had to ask others for help. More sociability
F: 'Go there' not a solution?
Frederic: but it was problematic, I had to leave to reach the other network in order to work...
"try to find the one that can give the answer appropriate to you!"
RIS8 A la POISSONERIE and the failure of interacting with the people...

yes not able to diplomatically speak with them  (poissonnerie)
technical 
difficulty installing opencv, faulty OSX!!!,experience with the SDR Radios, very limited on OSX (Mac)
spending to much time on how to make the tools working then try it

more collective discussions!

What happened to exercices in the morning? ;)
F: What is the status of Mac OSX in relearn... it was presented that "we use Linux"... but then there was OSX ... so what's the status of it?
The first edition of relearn we used linux virtual machine but again the box in the box..
can be very useful to have different OS to compare, see differences, make different documentation
(Windows users were here too -- just not so many ... maybe 3 / 4) ... Seeing putty through a GUI interface was 
Frederic: an inconsistency between what was presented and what was done (not to use linux)
But its about FLOSS! An attempt to be inclusive to different systems
M: there's no pure solution (and it's a valid point that's hard to address ... dual boot IS ideal but not possible in a short time span... so how not to exclude people, or over-simplify to linux = good, all others = bad)
The linux virtual machine was not working good the past years
people that used it in the past came with a full install this year, it goes in steps




Group 3


(Mal)functioning of ... tools

A: Coffee on the machine!? why? No coffee? Too much coffee? Coffee spilling on a laptop! 

AC: channel 76: open failed: connect failed: Connection refused
channel 87: open failed: connect failed: Connection refused
channel 93: open failed: connect failed: Connection refused
channel 94: open failed: connect failed: Connection refused
channel 105: open failed: connect failed: Connection refused
channel 106: open failed: connect failed: Connection refused
channel 126: open failed: connect failed: Connection refused
channel 130: open failed: connect failed: Connection refused
channel 34: open failed: connect failed: Connection refused
channel 42: open failed: connect failed: Connection refused
channel 29: open failed: connect failed: Connection refused
channel 136: open failed: connect failed: Connection refused
channel 137: open failed: connect failed: Connection refused
channel 154: open failed: connect failed: Connection refused
channel 158: open failed: connect failed: Connection refused
channel 86: open failed: connect failed: Connection refused
channel 168: open failed: connect failed: Connection refused
channel 170: open failed: connect failed: Connection refused
channel 8: open failed: connect failed: Connection refused
channel 9: open failed: connect failed: Connection refused
channel 7: open failed: connect failed: Connection refused
channel 6: open failed: connect failed: Connection refused
channel 15: open failed: connect failed: Connection refused
channel 24: open failed: connect failed: Connection refused
channel 40: open failed: connect failed: Connection refused
channel 56: open failed: connect failed: Connection refused
channel 62: open failed: connect failed: Connection refused
channel 73: open failed: connect failed: Connection refused
channel 78: open failed: connect failed: Connection refused
channel 79: open failed: connect failed: Connection refused
channel 85: open failed: connect failed: Connection refused
channel 86: open failed: connect failed: Connection refused
channel 89: open failed: connect failed: Connection refused
channel 94: open failed: connect failed: Connection refused
channel 97: open failed: connect failed: Connection refused
channel 28: open failed: connect failed: Connection refused
channel 62: open failed: connect failed: Connection refused
channel 35: open failed: connect failed: Connection refused
channel 106: open failed: connect failed: Connection refused
channel 37: open failed: connect failed: Connection refused
channel 7: open failed: connect failed: Connection refused
channel 3: open failed: connect failed: Connection refused
channel 7: open failed: connect failed: Connection refused
channel 3: open failed: administratively prohibited: open failed
channel 3: open failed: administratively prohibited: open failed
--> what does it mean? ..something to do with the tunnel..?:)
shocking experience, a lot of failures and refusing moment
A waiting long time to join an etherpad

Server had moments that were frustrating, but it was also interesting
It was difficult to upload files, drag and drop worked well. This really created a distinction between server and local machine.
Some groups make their working files more explicitly accessible. Uploading is not enough for sharing, for some.. And therefor there is a hesitance felt sometimes to upload a project that has been worked on.
Need to document the work before sharing it. Documentation is very important for the future. Therefore there are a lot dead-end in the pad... but on the other hand, some links are just pasted for the moment.
Sharing was no so explicit, it was not so obvious that things should be shared.
Pad links become dead ends some weeks after relearn; no clear structure 

- is the network-setup of this Relearn for people who are less familiar with network-infrastructures too heavy?


meta-meta-note: how thinking of malfunctions makes you realize the things that actually worked!

 or a device, 

- the door, two codes. people locked out because of code wasn't communicated with the group



 but also social dynamics,

  food, -> not enough time!

  planning -> not enough time! -> Malfunctioning of the malfunciton discussion
---------------------------------------------------------------------------------^
|
------ malfunction of the comment of the malfunction of the malfunction discussion