Networked journalism takes obvious cues from the open source software movement, but because the two seem so distant it helps to spell out these parallels. Below are 10 examples of how the software revolution is organized, with its emphasis on open-ended work on computer code, to show how it can be flushed out into open source journalism.

1. Bug fixing in code equates to fact checking in journalism

To make a direct comparison; Mozilla’s Bug-catching efforts are equivalent to fact checking. There are many similarities between the two. More eyeballs on the code (or articles) make bugs (or mistakes) shallow, to use Linus Torvalds’ famous statement.

To address this issue, network journalism will benefit from a director of verification.

2. Reuse and reproducibility of code–-and the exploration of public databases

The power of open source concepts lay in its emphasis on sharing information. This makes it possible for coders to build on the work of others. It’s particularly inherent in open source projects with scientific motives ( e.g. standing on the shoulders of giants to see further, to use Newton’s analogy). In this way one can “massage” content or code to better suit different purposes. In journalism this means creating and using public databases of information for citizen muckrakers to pour over and find relevant facts for their own investigations.

3. Recognition as motivator — money as a secondary factor

It is no secret that many reporters are overworked and underpaid. The reason for persistence, however, is often genuine interest, true personal involvement, and impact. The same can sometimes be said about software developers who seek to fulfill a goal, overcome perils, and address personal pet peeves. Satisfaction comes from a self-tailored product, be it an article or software.

Eric Raymond calls this phenomenon “scratch-itching” software, where each member of the development group addresses his/her own needs and desires. Similarly, every investigation needs to be approached from different angles to create a broad overview of the subject. Ultimately, the entire team provides a more robust software package or an investigation that takes everyone’s concerns into account.

4. Quantity does not lead to a higher cost of production

The cost of manufacturing an electronic code or text is almost inexistent. They involve no physical raw material. Unlike the production of shoes, for example, replicating code (programs) is a money-independent process. It is only research and development that counts. Likewise, in new media, it is the effort of the group ( e.g. time spent) that counts. Bandwidth limits aside, a successful story can reach a wide audience and receive a lot of feedback (including corrections) without elevating any production/delivery costs.

5. Authorship/credit

It’s well known that a coder’s product becomes their “baby” (see #3). With open source models, there remains an electronic trail to show who contributed to different parts of an article or program (e.g. SVN, CVS for version control). Thus, credit can be given to the rightful person and mistakes can be traced back to the culprit.

6. Versioning, editions, fixes, patches, and corrections as separate
press releases

Open source projects rely on versioning of content (revisions, changes, and rollbacks). In journalism this means passing content among different groups and attracting more eyes to verify reporting. Consequently, material can be corrected before outrageous, inflammatory or erroneous information gets published. Once again, the argument revolves around peer moderation and review. Open Source is renowned for being a quick and reliable method for assessing work and providing an almost-immediate quality assurance.

7. Monetized model — donate on investigations that appeal to you

In open source the crowd determines what projects reach completion by participating in those that appeal to their needs the most. Independence for the writer is analogous to the freedom of a freelance software developer. In journalism there is potential to create alternative methods of funding investigations through reader micro-payments, with investigations that have the widest mass appeal rising to the top.

8. Expansion; a story is never finished”

Open content is available for extension since ownership becomes ‘fluid,’ so to speak, territory. Creative Commons licenses, for example, permit and accommodate derivative work with various defensive exceptions. It becomes a case where the “one-size-fits-all” myth is broken. Different authors and audiences seek accurate information with a different angle.

9. Code similarity, duplicability and linking

Sharing information and links gets rid of the need to repeat. The ability to follow links and merge information is forged to create more cohesive and centralized knowledge. With the vast size of the Web, however, concern also emerges about the reliability of information (see #1 above).

Excess from duplications is the motivator for gathering information in a single place which—-in turn—-enables more eyes to view and correct mistakes. It is hardly surprising that collaboration and unification (much like standardization) benefit all by improving the eventual outcome. This prevents waste, as well as reinventions and incarnations of the same wheel.

10. Editorial control, personal writing style/unification

Consistency is an important aspect of paper-based publications and code alike. It is important not to duplicate effort (e.g. similar/identical reporting or multiple functions that achieve the same goal). There needs to be supervision that relies on knowledge that is applied in a top-down direction.

For more lessons that the open source community has for network journalism, see Jay Rosen’s conversation with Mozilla’s community guy Asa Dotzler.

Roy Schestowitz is a Ph.D. Candidate in Medical Biophysics at
Manchester University. While on the verge of completion he finds himself fascinated by the endless possibilities that the World Wide Web offers; consequently he often gets distracted. He advocates the use of Open Source technology in the public and private sector and uses his background in computing to make personal contribution to the Free Software movement. In his spare time he engages in activities ranging from weights-related sports to easy-listening music.