<?xml version="1.0" encoding="UTF-8"?><xml><records><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Cook, J.</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Open Source Development: An Arthurian Legend</style></title><secondary-title><style face="normal" font="default" size="100%">1st Workshop on Open Source Software Engineering at ICSE 2001</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">commercial software</style></keyword><keyword><style  face="normal" font="default" size="100%">developers</style></keyword><keyword><style  face="normal" font="default" size="100%">MOTIVATION</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2001</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://ifipwg213.org/sites/flosshub.org/files/cook.pdf</style></url></related-urls></urls><abstract><style face="normal" font="default" size="100%">OSSD (Open Source Software Development) achieves remarkable success in delivering complex software systems – systems which are incredibly reliable and robust – in a short amount of time and without even paying anyone! Naturally, in the face of this success, organizations are interested in seeing if the mechanisms behind OSSD success can be migrated into their own practices, hopefully improving their systems and their productivity.
In this paper, we look (lighthearted at first) at the motivations behind those involved in OSSD and describe the problems that need to be overcome if OSSD-type practices can be migrated into traditional organizations.</style></abstract></record></records></xml>
