looking east

Technical objects define in their configuration a certain partition of the physical and social world, they attribute roles to certain types of actors - humans and non-humans - and exclude others, they authorise certain modes of relations between these different actors […] in such a way that they participate as a whole to the construction of a culture in the anthropological sense of the term, and, at the same time, they become enforced mediators in all relations that we are maintaining with the “real”.

Madelaine Akrich, Comment décrire les objets techniques?

Later in her paper, Madelaine Akrich introduces the term “script” to refer to the behaviour of a technical object. The “script” is the program which the original developers write in order to define how the object can be used by its users.

For the purpose of studying FOSS in Asia, the technical object would be a piece of FOS software, its behaviour is defined by the source code, and the users are people who are using this software from within the borders of what is defined as Asia.

However, the scope of my master thesis as described above is not complete. FOS software has a specific characteristic which is related to it’s licensing terms. I don’t want to enter into FOSS licensing in detail, but I would like to emphasise one interesting aspect of open source software: modifiability. This means, we can take a piece of existing FOS software and tailor it to our needs. Going back to Madelaine Akrich’s definition of the “script”, this means that the “script” can be modified by its users. We are thus moving away from the traditional developer-user model to a more distributed open source community development model. In FOSS, users are not stuck with a pre-defined script, rather they are encouraged to change the script according to their needs. This in turn, forces users to think about the software in terms of its utility to an individual.

To be honest, the source code or “script” cannot be changed by any random user. Instead, this freedom is restricted to people who are familiar with computer programming. However, FOSS has made it easy for users to give feedback, propose new features, and report bugs. You don’t need to be a programmer to do this, though you still need to be able to use a computer and run the program.

Implementing modifiability into objects is not new, although the open source movement and its derivatives have been strongly promoted lately. In his book Two Bits, Kelty investigates the impact of modifiability on culture, he writes:

But what is the cultural significance of modifiability? What does it mean to plan in modifiability to culture, to music, to education and science? At a clerical level, such a question is obvious whenever a scholar cannot recover a document written in WordPerfect 2.0 or on a disk for which there are no longer disk drives, or when a library archive considers saving both the media and the machines that read that media. Modifiability is an imperative for building infrastructures that can last longer. However, it is not only a solution to a clerical problem: it creates new possibilities and new problems for long-settled practices like publication, or the goals and structure of intellectual-property systems, or the definition of the finality, lifetime, monumentality, and especially, the identity of a work. Long-settled, seemingly unassailable practices — like the authority of published books or the power of governments to control information—are suddenly confounded and denaturalized by the techniques of modifiability. (page 12)

Modifiability is at the core of FOSS. It’s one of the main reasons why FOSS communities have emerged. It’s at the base of almost all discussions on mailinglists, forums, IRC channels and FOSS events. The users and developers can decide the future of the software by participating in these discussions. The fact that a FOSS culture has emerged around open source software, proves Madelaine Akrich’s point that technical objetcts are important elements in the construction of cultures. And, of course, despite it’s modifiability, FOS software has a “script” which clearly defines how it’s supposed to be used