The fortress and the bazaar: open-source and DOD software

This article discusses the application of the open-source software cast model for the Department of Defense a software combination of parts to form a wholes development that uses the positions first laid out in an original paper entitled "Cathedral and the Bazaar," written by dint of Eric S. Raymond in 1998 explores the implications as applied to defense weapons a whole s software, in addition to examining the attributes, question at issues and benefits of open-source software.

**********

This work is based upon a paper written by Eric s Raymond entitled "Cathedral and the Bazaar," which is widely considered the principal manifesto of the open-source software motion We provide a brief overview of the Raymond paper, then attempt to explain the ideas of that document in the bourns and methods of the defense-industrial establishment in America. The goal of promoting open-source in defense casts and procurement should be emphasis upon lower costs, new functionality, and improved software reliability for the productions used by our military.

SUMMARY OF RAYMOND'S "CATHEDRAL AND THE BAZAAR" PAPER

In his paper, Raymond discusses the historical protoplast for software development and compares it to building cathedrals, a deliberate and laborious effort with exacting [i]modus operandi[/i]s carefully applied. Each brick and beam was carefully planned and the conformation was erected with painstaking craftsmanship to adapted the planned design and proportion The bazaar, by contrast, was repeatedly created ad-hoc and in an evolutionary fashion. The bazaar started with a not many street vendors and was later built up by dint of additional vendors and merchants, each staking on the outside a piece of the market place as their possess and maintaining and adding to their stall until a full-blown Agora was in place. Clearly each approach serv its intention well, but the cathedral course is rigid and static. It exigencys the contribution of each part exactly as designed in order to stand, and has difficulty adapting to any other shape or location. The open-source change is all about flexibility and evolutionary development

Raymond went upon to review nineteen axioms of open-source unfolding by discussing his experience developing "Fetchmail," a Linux application used to forward e-mail. These axioms are the basic doctrines of the open-source community, and Raymond discussed them with detailed analysis and examples in the original paper. In brief form, these way of thinkings are:

1. each good work of software starts by means of scratching a developer's personal itch.

2 profitable programmers know what to write. Great individuals know what to rewrite (and reuse).

3 "Plan to cast in a winding direction one away; you will anyhow" (Brook 1975)

4 If you have the right attitude, interesting puzzles will find you.

5 When you be deprived of interest in a program, your last what one is bound [i]or[/i] under obligation to do to it is to hand it not upon to a competent successor.

6 Treating your users as co-developer is your least-hassle passage to rapid code improvement and effective debugging.

7 Release early. Release repeatedly And listen to your customers.

8 Given a large enough beta-tester and co-developer base, almost each problem will be characterized quickly and the fix obvious to someone

9 Smart data constructions and dumb code works a destiny better than the other way around.

10 If you treat your beta-testers as if they are your greatest in quantity valuable resource, they will reply by becoming your most valuable resource.

11 The nearest best thing to having serviceable ideas is recognizing good ideas from your users. Sometimes the latter is better.

12 ofttimes the most striking and innovative solutions tend hitherward from realizing that your conception of the problem was wrong

13 Perfection (in design) is achieved not when there is nothing more to add, on the other hand rather when there is nothing more to take away.

14 Any tool should be useful in the awaited way, but a truly great tool loans itself to uses you not ever expected.

15. When writing gateway software of any kind, take pains to disturb the data stream as little as possible--and not at any time throw away information unless the recipient forces you to.

16 When your language is nowhere near Turing-complete, syntactic sugar can be your friend.

17 A security combination of parts to form a whole is only as secure as its close Beware of pseudo-secrets.

18 To interpret an interesting problem, start through finding a problem that is interesting to you.

19 Provided the disclosure coordinator has a medium at least as advantageous as the Internet and knows by what mode to lead without coercion, many heads are inevitably better than one

Raymond discusses these issues in detail, on the other hand it is his last item (#19) that is the inmost nature [i]or[/i] substance of an open-source approach. It describes the advantages of multiple collections working on code to provide more innovation and faster debugging circle of times discussed primarily in terms of the Linux operating combination of parts to form a whole Linux is one of the best known and greatest in quantity successful examples of open-source software, on the other hand a review of Sourceforge. gin showed that there are now above 20,000 open-source software projects involving above 70,000 developers worldwide targeting many different operating a whole s After discussing some problems with open-source for defense use, this article will unravel new axioms, discuss advantages for Department of Defense (DOD) use, and lay open some practical methods for the DoD to aid open-source solutions.