he only thing needed is a shared medium or workspace in which clear traces of the work areregistered (Heylighen, 2011a; Parunak, 2006). The aggregated trace functions as a collectivememory that keeps track of the different contributions and indicates where further work may beneeded. This function is typically performed by the community website, such as the Wikipedia site.A more advanced example of this functionality can be found in the issue queue used byDrupal developers (Kiemen, 2011; Zilouchian Moghaddam, Twidale, & Bongen, 2011). This is acommunity-maintained, ordered list of feature requests or problems that need to be addressed,together with the status of the work being done on each. The issue queue makes it easy forcontributors to see where their contribution would be most helpful, and to keep track of theadvances made by others. It can be seen as a more spontaneous, self-organizing version of the jobticketing systems that are commonly used in technical support centers, where each incomingproblem is assigned a “job ticket”, after which the ticket is assigned to one or more employees, andmonitored so as to make sure it is adequately dealt with (Heylighen & Vidal, 2008; Orrick, Bauer,& McDuffie, 2000).