|
|
|
|
@ -59,42 +59,44 @@ Documentation is a way to produce narrations around software. To create a world
|
|
|
|
|
|
|
|
|
|
## What is your timetable?
|
|
|
|
|
|
|
|
|
|
- October
|
|
|
|
|
- 🎃 October
|
|
|
|
|
|
|
|
|
|
- Define a domain of research.
|
|
|
|
|
- Understand where to ground the project by revisiting first year prototypes.
|
|
|
|
|
- Think about a glossary and possible formats to test some concept in a small scale
|
|
|
|
|
- Experiment writing documentation for XPUB prototypes
|
|
|
|
|
- November
|
|
|
|
|
|
|
|
|
|
- 🍂 November
|
|
|
|
|
|
|
|
|
|
- Experiment writing documentation for projects outside XPUB
|
|
|
|
|
- Artistic and commercial ones.
|
|
|
|
|
- Tap into networks related to situated software
|
|
|
|
|
- Participate to events! Software is a public discourse don't be too shy
|
|
|
|
|
|
|
|
|
|
- December
|
|
|
|
|
- ⭐ December
|
|
|
|
|
|
|
|
|
|
- Archeology of software documentation.
|
|
|
|
|
- Field research of the current trends in software documentation.
|
|
|
|
|
- Explore different contexts and different coding languages.
|
|
|
|
|
|
|
|
|
|
- January
|
|
|
|
|
- ☃️ January
|
|
|
|
|
|
|
|
|
|
- Follow up on the outcomes of the different hackpacts. Focus on
|
|
|
|
|
1. materiality (style, contents, forms)
|
|
|
|
|
2. context (actors, timeframe, hosting)
|
|
|
|
|
- Research possible formats for the list outcome.
|
|
|
|
|
|
|
|
|
|
- February
|
|
|
|
|
- 💘 February
|
|
|
|
|
|
|
|
|
|
- What surface could host this different factes together?
|
|
|
|
|
- Fast daily prototypes or field research
|
|
|
|
|
|
|
|
|
|
- March
|
|
|
|
|
- ☔ March
|
|
|
|
|
|
|
|
|
|
- Follow up on February daily prototypes
|
|
|
|
|
- Plan for production
|
|
|
|
|
|
|
|
|
|
- April
|
|
|
|
|
- 👃 April
|
|
|
|
|
- Production in the form of fast and iterative prototyping
|
|
|
|
|
- Fine tuning and polishing.
|
|
|
|
|
- Think about graduation exhibition and collective pubblication.
|
|
|
|
|
|
