During the active archives code sprint in June 2010 Deptford.TV got the active archives system installed, see pictures. Soon we will be running an active archives workshop in London.

Manifesto for an Active Archive

From ActiveArchives

This Manifesto is a work in progress. The text introduces the ideas and motivations behind the Active Archive project lead by Constant in collaboration with Arteleku, and was initiated in 2006. This project aims at creating a free software platform to connect practices of library, media library, publications on paper (as magazines, books, catalogues), productions of audio-visual objects, events, workshops, discursive productions, etc. Practices which can take place on line or in various geographical places, and which can be at various stages of visibility for reasons of rights of access or for reasons of research and privacy conditions. The development will take place during 2008-2009 and regular workshops will be organised to stimulate dialog between future users, developers and cultural workers and researchers.

Creating web pages and displaying information on-line has become easier and easier for non-expert users. The Active Archives project starts from the observation that most of the interesting cultural archives that have been developed over the last few years have taken advantage of those new facilities for instant publishing, but mostly in the form of websites that mirror regular information brochures, announcements and text-publishing. Often, they are conceived as “We” give information to “You”. Within Active Archives, we aim to set up multi-directional communication channels, and are interested in making information circulate back and forth. We would like to give material away and receive it transformed: enriched by different connections, contexts and contradictions.

Decentralizing the archive

When we want to share with other cultural associations and groups/institutions, the challenge is as follows: how do “We” share information “Together”, how do we channel information through each others’ network, under which conditions? How do we produce digital content together? To develop common infrastructures, we will need to discuss what kind of licensing we prefer, and work on norms and a common agreement on formats. We also need to find a shared understanding of classifications or maybe first question existing ones.

Digital cultural archives today fall into two categories: fragmented archives and over-centralized archives. Fragmented archives look like isolated islands. Every institution sits on top of its treasure and tries to regulate and control the way it is used with at most offering a timid RSS feed. Centralized archives gather collections and resources from different origins but disconnect the material from its original context. Accessibility and searchability come at the cost of legitimisation.

An active archive is a decentralized archive which is not only open for reading but also for re-appropriation, comment, divergences, transformations. This manifesto is a plea for such a decentralized archive: an archive constituted from many sites and voices that keep their own contexts without fear of sharing, mirroring, connecting and using common protocols.

Owning our infrastructure

If public television channels decide to publish their archives on YouTube, libraries work in partnership with Google etc., why does the Active Archive not make use of the existing web 2.0 infrastructure? Flickr + MySpace + FaceBook with a bit of Delicious to glue it all together… who needs more? But to upload digital culture on the servers of dotcom billionaires might not be such a good idea after all.

However much influence the functionalities of Web 2.0 had in popularising the digital archive, we need to be aware of their terms of use. We would like to prevent that cultural archives serve as footage for ad-placement or as honey pot for market profilers and for this reason we need to make the effort to build our own infrastructure.

An active archive should provide to its contributors a clean and clear contract where the terms of the participation are fair and legible for everyone. The goal of an active archive is to produce more interesting content in the first place. Not to make profit in monitoring the users and selling their behavioural patterns. Only when the different parties involved own their own infrastructure and accept to share it, they can ensure the conditions for access without strings attached. This means open content licenses for all material stored, so that the conditions for use are clear for everyone. An infrastructure built with free software so that everybody can co-own the source code.

Distributing more than text

An active archive needs to go beyond mere text-publishing. Artists, cultural groups and institutions regularly produce video and audio images for various communication or creative purposes. It is necessary to take into account that media content requires different material configurations: they need more disk space and more bandwidth, therefore they require clever strategies of distribution. Peer-to-peer networks have pioneered large scale experiments with the distribution of audiovisual media, and it is time to learn from them.

Integrating audiovisual media is not just adding another type of file. It requires a new approach to navigation, searching, linking, subtitling and translation so that audio and video content can connect to text-based content because otherwise those files remain black holes in the archives.

Promoting re-use

The material that is made available through the Active Archive is thought of as source material for other works. This means, systems need to be put in to place to make referencing and re-use of the material easy, but also make sure that versions of the material can filter back to the place it original came from. These systems are partially technical, and partially cultural: a series of commissions, workshops, exhibitions and publications will inspire creative use.

Between tags and ontologies

To improve the search facilities, to group elements, to link them and to create new meaning and new experiences, an archive needs a system of classification. Librarians and archivists are used to work with fixed standards but the work produced and discussed within contemporary culture tends to escape these classification schemes.

An Active Archive requires the creation and discussion of vocabularies and taxonomies that can evolve, diverge or merge. These vocabularies and taxonomies should neither be brutally top-down or completely flat. The system should stimulate the sharing of common classifications, allow for divergence and promote the convergence of knowledge trees. Active Archive needs a classification system with a difference.

Moving through new gestures

Sharing is the principal motivation to create an Active Archive. This means that we need to update our assumptions about the users of such an archive, the sources that are used and the circulation of its content. An Active Archive is not a black box with a Download button, it is information reconfigured. And it has to start now.

The plan is to integrate the Cinelerra Server project into the Cinelerra FLOSSMANUAL, see http://en.flossmanuals.net/bin/view/Cinelerra/WebHome

What is FLOSS Manuals?

FLOSS Manuals is a collection of manuals about free and open source software together with the tools used to create them and the community that uses those tools. They include authors, editors, artists, software developers, activists, and many others. There are manuals that explain how to install and use a range of free and open source softwares, about how to do things (like design) with open source software, and manuals about free culture services that use or support free software and formats. Anyone can contribute to a manual – to fix a spelling mistake, to add a more detailed explanation, to write a new chapter, or to start a whole new manual on a topic. You can read and use the manuals in a number of different ways. They are available online in separately indexed chapters, and you can use the website as a reference base in this way. You can also view, download, or print each manual as a PDF file. It is also possible to ‘remix’ manuals to create a version that only includes specific aspects of a particular manual, or that combines chapters from two or more manuals in a single document. These can be downloaded and printed, added to websites, and used for any purpose. You can also print a manual, or an individually ‘remixed’ manual, as a book via the print-to-order service of Lulu.com.

What does FLOSS stand for?

F. L. O. S. S. stands for Free Libre Open Source Software. Basically, this means software that makes its code available for anyone to use, change, and redistribute under the same terms. If you’re still confused, you can read more below.

What is Open Source? What is the difference between Free and Open?

Open Source emphasizes availability of source code to software users. This means not only that the source code is available at no cost and with little difficulty, but that users can modify the source code and distribute the results under the same conditions. Bruce Perens wrote the original Open Source definition for Debian. Free Software emphasizes the freedom to modify and reuse software, which of course also requires that source code be readily available. Richard M. Stallman initiated the definition of Free Software as part of the creation of the Free Software Foundation and its GNU project (GNU’s Not Unix) to create a completely Free Unix-compatible operating system and set of software tools. GNU software together with the Linux kernel, plus contributions from many other sources, constitute the GNU/Linux Operating System, commonly known as Linux. So in practice the differences in meaning between the two phrases are not great, but they lead to some differences in attitude, terminology, and use of specific license terms. One reason for the difference in terminology is that “Free” is ambiguous in English. FSF has to explain that it means, “Free as in Free Speech, not as in Free Beer.” To counter this, the unambiguous French term “Libre” can be added in, resulting in FLOSS, or Free (Libre) Open Source Software. FSF maintains a page explaining the various Free and Non-FREE licenses. The BSD (Berkeley Software Distribution) license, for example, allows users to modify source code and put the changes under a restrictive commercial copyright, as Apple has done in Mac OS/X. Since most BSD users put their changes under BSD, it can be considered somewhat, but not entirely, Free. In addition to these software licenses, there are several licenses for documentation and other content, most notably the GFDL (GNU Free Documentation License) and the various Creative Commons licenses. FLOSS Manuals uses the Free Software GPL for all of its work. For details of definitions and available licenses, see

• http://www.fsf.org/ Free Software Foundation
• http://www.gnu.org/ The GNU Foundation
• http://www.opensource.org/docs/definition.php Open Source Initiative
• http://www.opensource.org/licenses Open Source Licenses
• http://www.fsf.org/licensing/licenses/ Free and Non-Free Licenses
• http://www.creativecommons.org/ Non-software licenses

A Little About the History..

Adam Hyde started FLOSS Manuals while a digital artist. Adam had made a living running workshops on free software all over the world and had accumulated a lot of support material in the form of workshop manuals. In 2005 this material was put into a wiki with the help of Aleksandar Erkalovic and Lotte Meijer did the design. In 2006 Lotte Meijer and Adam Hyde applied for and recieved funding from Digital Pioneers to extend FLOSS Manuals. Thus the development and design of FLOSS Manuals as it is now started in 2006. This is the same year the Foundation was registered. Several digital artists were commissioned to write manuals on Audacity, Gimp, Blender, and PureData. The actual site wasn’t ready until May 2007. The first unsolicited edit on the site was in July 2007. FLOSS Manuals was officially launched at a party at Montevideo Time Based Arts (Amsterdam) in October 2007. In 2008 we created the Farsi version of FLOSS Manuals (http://fa.flossmanuals.net) and started our first Book Sprints. Now there are over 40 manuals on free software, and 1200 registered contributors and a healthy and active mailing list. Burmese, French, Finnish and Spanish language communities are currently being established.

What’s the benefit to me of using FLOSS and FLOSS Manuals?

By using free/libre/open-source software, you have the right to use, change  and share the software freely. FLOSS is also usually no-cost. You are not dependent on a big company to add features or fix problems; for FLOSS, these issues are handled by a community of software developers, which often responds more quickly. If the FLOSS community doesn’t address a problem that have with the software, you can hire a programmer to do it for you; this is almost never possible with proprietary software. Similarly, when you use free/libre/open-source manuals, you have the right to use, modify and share the documentation freely. Manuals on the FLOSS Manuals site are no-cost to use online. For paper copies, we charge just for the paper and printing, and a little extra to support making more books. You can also take the online version as a PDF file and print it yourself. You can also edit the documents on the site, for example, if you find things are incorrect, out of date, or incomplete. (You can also change your own copy, but we appreciate if you help us make the manuals on the site better.)