Gareth Foote
Since 2010
Works in London United Kingdom of Great Britain and Northern Ireland

My background is in development, particularly web technologies. Before starting my Masters I was a fully indoctrinated member of the Adobe fan club. Studying FLOSS practices has inspired me to write about and practice software art. Within this practice I am attempting to refuse the passive role of the user and be part of relational practices involving Free Software and open collaborative practices.

Discussions (0) Opportunities (0) Events (2) Jobs (0)


Wed Jul 14, 2010 00:00 - Sun Jul 11, 2010

FLOSS inspired Software Art piece seeks willing contributors. GSOH.


There are three aspects to the Wabbitware software project: the software itself, a website for distribution and collation of versions and most importantly the contributors.


When the software executable (binary) is executed it will distribute a copy of the source code onto the host machine. You are then free to make any modifications to the source code. After this the original binary can be used to pre-compile those modifications ensuring that they are carried forward to the next generation of Wabbitware. The final stage is to compile the software, creating the next instantiation/generation/version of Wabbitware.

The process is then looped ad infinitum. The software is therefore never complete or whole but always in process.

The website whilst acting as a code repository for the first version of the code also aggregates any newly submitted versions of Wabbitware. There are instructions in the Versions section of the Wabbitware site (http:://, which state that once a new instance of software has been created there is an option to attach and email your binary to the email address: This collection process is a simplified concurrent version system which enables the rhizomatic growth of Wabbitware.

Contributions: /*Comments*/
Although it may seem that, despite the forceful access to the software source code, there is a knowledge barrier for open contributions. In normal circumstances you do need to understand some of the grammar and syntax involved in programming to able to make functional code. However on the website there are step by step instructions for creating your own instance of Wabbitware. There is not however a guide on how to program software in general. For anyone who would like to contribute but doesn't have the programming experience you can simple add comments to the source code. A comment is a section of the source code which is ignored by the compiler in the process of making software. They are there to enable programmers to write notes to themselves and to other programmers who they may be collaborating with.

In many cases these are purely functional:

/* count the occurances of each $keyword (supplied with categories) in the given $cmt */

/* assuming you're in /usr/src/linux/ (and linux .c and .h are present) */

in other cases create a collaborative narrative or psychological snapshot of a programmers state of mind:

/* It looks like I can't do a simple tweak with this structure because the IRIX
* version is just *too* stupid. Ok, here's a new version of it..

/* This is fucking braindead. There is NO WAY of doing this without
the CONFIG_SYSCTL unless you don't want to detect errors.
Grrr... --RR */

As you can see form these examples - which are all taken from the Linux kernel - a comment is started with a /* and closed with a */. Feel free to use this practice in Wabbitware.

One affordance of the Wabbitware project is that it has NO functional goals and NO beta release schedules. This is mainly due to its principle characteristic of being permanently incomplete or in a state of flux. The definition of the software does not end at its code, it continues into the social dynamics that are made up by the collaborative practice. The project is about the process as much as the code itself so any contributions are welcome and they do not need to be grand or well thought out.

//a favourite piece of code
//a malicious piece of code - see - (Feel free to right code that will break the software)
//pointless code - see

If you don't have a preferred piece of code then comments are just as welcome. You could add:
//prose, poetry, song lyrics, a quote, an insult, a link, a statement, a political message, a joke, etc, etc,etc

This is part of the We are All Transistors Graduate Exposition.


We are All Transistors

Thu Jul 15, 2010 00:00 - Sun Jul 11, 2010

EXPO 2010 - We are All Transistors

The Graduate Showcase for the MA Interactive Media: Critical Theory and Practice course at Goldsmiths, University of London.

Closing Party Thursday 15 July 6-9pm

Opening Hours:
Tue 13 July 3-8 pm
Wed 14 July 3-8 pm
Thu 15 July 12-9 pm

We are all transistors. We amplify. We resist. We always operate in a space, whether social, political or Hertzian. We navigate through these spaces, sometimes crashing into oblivion. We are switches that direct the current.

Through our ability to switch, we exercise our power to create turbulence in media systems. We collect and emit signals, messages and relays, make noise. We feel this matters because we live in a control society.

We are materialists. We are things that make possible the objects used everyday, such as electronic computers, radios and mobile phones. Stockhausen who famously coined the phrase ‘we are all transistors’ limited ‘all’ to human beings. We want to include the machines we interact with. We number in billions.

Our work intersects with various disciplines, from design to anthropology and from geography to science. We wish to bring such varied disciplines together by focusing on process.

For this exposition, we attempt to turn traditional research methodologies on their head. We investigate diverse areas like poetics of computing, event narratives in the real and virtual city, teleutopias, bodies in motion, enabling displaced groups with mobile technology, visuospatial impairments, cultural confusions and crashing bogus colleges into Goldsmiths.

And since we are all transistors, we contest the two terms, interactive and media by placing our energy, our potential, to the task.