diff --git a/projects/grs/documentation.md b/projects/grs/documentation.md index 0464295..91cc29a 100644 --- a/projects/grs/documentation.md +++ b/projects/grs/documentation.md @@ -116,62 +116,77 @@ Probably not so directly connected but there is this book (which one and where w ### What do you want to make? -A methodology for software development as a form of care. Research how software development changes depending on the context and actors involved. +A methodology for software development as a form of care. +Research how writing software changes depending on the context and actors involved. +Bring the specificity of three different case studies: coding for oneself, coding for others, coding with others. +How different nuances of these three settings can inform and resonate one with the other? ### How do you plan to make it? -Focusing on three parallel projects of different nature. One in which I develop for myself, one in which I develop for someone else, and one in which I develop together with some others. Im not sure if this projects need to be start from scratch, actually this graduation could be the chance to inject some awareness and forms of care in already going project. +The plan is to focus on three parallel projects of different nature. -Developing for myself could happen in the context of [OOC](../ooc-summer-session/), my long-term contemporary dance project with VR. What would it mean to bring XPUB forms of care into that work? +One in which I develop for myself, one in which I develop for someone else, and one in which I develop together with some others. +Not all these projects need to start from scratch. This year could be the chance to inject some awareness and forms of care in already ongoing projects. -Developing for someone else could refer to commercial practice and freelance work. Could it be a way to bring not only the advantages but also the perspective and cultural dynamics of FLOSS into the real world. This freelance work often comes in the form of web or interaction design and development. +Developing for myself could happen in the context of [Object Oriented Choreography](../ooc-summer-session/), my long-term contemporary dance project with VR. What would it mean to bring XPUB forms of care into that work? What does it mean to develop for oneself in the context of coding as discourse? -Developing togheter with others it's a way to rinegotiate priorities when developing software. How do we value and balance between accessibility, flexibility and sustenaibility? This could happen either collaborating with someone from xpub (think for example to the [workbook](../workbook/) with supi, the laser with ) or intercepting some third party reality +Developing for someone else refers to commisioned works and freelance work. Could it be a way to bring not only the advantages but also the perspective and cultural dynamics of FLOSS into commercial practices. Freelance work often comes to me in the form of web or interaction design and development. It could be a way to orientate specific commision to the development of tools of general use. + +Developing togheter with others it's a way to rinegotiate priorities when developing software. How do we value and balance between accessibility, flexibility and sustenaibility? This could happen either collaborating with someone from XPUB (think for example to the [workbook](../workbook/) with supi, the ilizarov projects with gr, etc ) or intercepting some external realities' need to craft together some piece of site-specific software. ### What is your timetable? -october +**october** define practically a method for the methodology: think about format and protocols define the premises in which to ground the three projects by revisiting first year projects get in touch with different communities for proj 2 and 3 -november +**november** work on OOC preparing for december performance develop context and prep-works for point 2 and 3: ideally setup temporality try to reach key figure to ask -december +**december** ooc performance and follow up about findings for the methodology -january +**january** start working on proj 2 start working on proj 3 -february +**february** working on one proj update format and protocols -march +**march** workin on the other proj update format and protocols -april +**april** follow up about findings for the methodology production for methodology outcome -may +**may** production for methodology outcome production for grad exhibition -june +**june** graduation exhibition party -july +**july** siesta ### Why do you want to make it? + + +Software comes from a really specific and situated cultural tradition. Software tends to privilege occidental, masculine, binary, and extractive practices. Software comes with technical obscurity. Software comes invisible, transparent, neutral. Software models the world in order to better control it. I don't like these trends. + ### Who can help you and how? ### Relation to previous practice