diff --git a/projects/gpp/documentation.md b/projects/gpp/documentation.md index 46208ce..8530019 100644 --- a/projects/gpp/documentation.md +++ b/projects/gpp/documentation.md @@ -39,6 +39,8 @@ Write the documentation together. Could there be multiple voices or is necessary Expand the research to tap into ongoing projects outside XPUB, such as freelance works and parallel research such as [OOC](../ooc-summer-session/). + + Are there ways to make the documentation process more sustainable (socially, economically)? Are there strategies to overcome a low-resources environment? Search for escamotages to create space and energies to document. Work with collaborators, clients, and end-users to approach code from multiple point of view. What are the relations between documentation and the community around a software? @@ -131,19 +133,6 @@ Documenting software is a complex practice. Documenting software is a process of As a piece of code would write: I am documented, therefore I am. - - - - - - ### Who can help you and how? It would be interesting to get in touch with someone mantaining open source projects such as Paged.js, P5Js, vvvv. diff --git a/projects/graduation-divination/documentation.md b/projects/graduation-divination/documentation.md index 559d86e..f0a511d 100644 --- a/projects/graduation-divination/documentation.md +++ b/projects/graduation-divination/documentation.md @@ -133,3 +133,5 @@ Developing togheter with others it's a way to renegotiate priorities when develo [... staying low] --- + +And viceversa. Undocumented software is invisible, but for the eyes of their own developers. And eventually, it begins to fade as soon as the developer looks away.