-
Notifications
You must be signed in to change notification settings - Fork 1
/
collective-processes.html
37 lines (30 loc) · 1.54 KB
/
collective-processes.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
in which we document our processes
<p>
Part of our planned deliverables for the class, other than the games themselves, are new collective processes for making games. To that end, we plan to try out a few different processes. The idea is to try out a process in micro every week.
</p>
<h2>week 1: free salad</h2>
<img src="images/documentation/miro/week1-sticky.png">
<p>
For our first attempt, we are going to:
<ol>
<li>
Pick a single image/object/idea.
</li>
<li>
Each one of us works on our own, making something in response to the chosen image.
</li>
</ol>
We can share our works-in-progress with each other during the week, but we don't have to. We should have something to show by next Wednesday (2/10).
</p>
<img src="images/documentation/miro/week1-mirodoc.png">
<p>
We also have this idea of "haunting" someone else's work-in-progress, which we left pretty vague and I will intentionally not describe further :)
</p>
<h3>How we picked the image: digital Ouiji</h3>
<p>
Miro has this functionality that lets you see where each other's cursors are in real-time. We grouped our cursors together in more or less the center of the image cloud, and tried to keep our cursors on top of each other.
</p>
<p>
The cursors naturally drifted in one direction. Nudged southeasterly by the spirits, we collectively crawled until we reached the edge of the word cloud. We picked the last image that we passed over (before we all fell off the edge of the world of images) which was:
</p>
<img src="images/documentation/free-salad.png">