Table of Contents
Programming AMRO
AMRO is 3 or 4 days long, depending on how one counts the days. It starts on a wednesday evening, with lectures, and runs till Saturday late night (or Sunday early morning). So 3 days and a starting evening, or 4 days, the first of which begins with participants arrival.
Program Structure
Here an approx program structure:
| day: | 0 - wednesday | 1 - thursday | 2 - friday | 3 - saturday |
| morning | setup finalization | talks & open mic | ||
| afternoon: | setup finalization | ws & sessions | ||
| participants arrival | dinner | |||
| evening: | opening lectures | evening program | ||
| night: | afo | open stage / DH5 | nightline | |
→ see production page for details about dates and logistics
Topics
Each AMRO edition has a title / series of subtitles that informs less a thematic intention for the edition, and rather a lens through which contemporary issues can be observed, and around which the community is invited to bring own contribution through the open call.
The topics for discussion of AMRO develop by:
- observing aspects of computing, networks and their intersection with wider socio-political conditions
- are developed from Research Labs happening in the year(s) before
- in exchange with local community group, loop list, individual exchanges
- from the practice of other art hosters
- from the exchange with AMRO participants of previous editions
Formats
- Talks, Lectures, Panels
- Workshops, Worklabs, Hands-on
- Performance and Sound
- Video
- Showcase
- other formats ?
Open Call
Usually out in February/March, but we want it to be out earlier and earlier.
Note for the future: ask why the applicant think their project fits to AMRO.
Does it have to be connected to an AMRO topic?
servus also takes note of some applications for other events.
