<?xml version="1.0" encoding="UTF-8"?><xml><records><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>17</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Audris Mockus</style></author><author><style face="normal" font="default" size="100%">Roy Fielding</style></author><author><style face="normal" font="default" size="100%">Herbsleb, J. D.</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Two case studies of open source software development: Apache and Mozilla</style></title><secondary-title><style face="normal" font="default" size="100%">ACM Transactions on Software Engineering and Methodology</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">apache</style></keyword><keyword><style  face="normal" font="default" size="100%">bug fixing</style></keyword><keyword><style  face="normal" font="default" size="100%">bug reports</style></keyword><keyword><style  face="normal" font="default" size="100%">bugzilla</style></keyword><keyword><style  face="normal" font="default" size="100%">change history</style></keyword><keyword><style  face="normal" font="default" size="100%">core</style></keyword><keyword><style  face="normal" font="default" size="100%">defect density</style></keyword><keyword><style  face="normal" font="default" size="100%">email</style></keyword><keyword><style  face="normal" font="default" size="100%">email archives</style></keyword><keyword><style  face="normal" font="default" size="100%">mailing list</style></keyword><keyword><style  face="normal" font="default" size="100%">mozilla</style></keyword><keyword><style  face="normal" font="default" size="100%">ownership</style></keyword><keyword><style  face="normal" font="default" size="100%">participation</style></keyword><keyword><style  face="normal" font="default" size="100%">productivity</style></keyword><keyword><style  face="normal" font="default" size="100%">scm</style></keyword><keyword><style  face="normal" font="default" size="100%">source code</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2002</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">http://flosshub.org/sites/flosshub.org/files/mockusFieldingHerbsleb2002.pdf</style></url></related-urls></urls><number><style face="normal" font="default" size="100%">3</style></number><volume><style face="normal" font="default" size="100%">11</style></volume><pages><style face="normal" font="default" size="100%">309-346</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">According to its proponents, open source style software development has the capacity to compete successfully, and perhaps in many cases displace, traditional commercial development methods. In order to begin investigating such claims, we examine data from two major open source projects, the Apache web server and the Mozilla browser. By using email archives of source code change history and problem reports we quantify aspects of developer participation, core team size, code ownership, productivity, defect density, and problem resolution intervals for these OSS projects. We develop several hypotheses by comparing the Apache project with several commercial projects. We then test and refine several of these hypotheses, based on an analysis of Mozilla data. We conclude with thoughts about the prospects for high- performance commercial/ open source process hybrids.</style></abstract><accession-num><style face="normal" font="default" size="100%">WOS:000177759000002</style></accession-num><notes><style face="normal" font="default" size="100%">apache data sources:
email, cvs, bug database 
regarding email: &quot;We wrote Perl scripts to extract date, sender identity, message subject, and the message body that was further processed to obtain details on code changes and problem reports (see below). Manual inspection was used to resolve such things as multiple email addresses in cases where all automated techniques failed.&quot;
(but the rest of the paper does not address this data source at all)

mozilla data sources
bugzilla, cvs

</style></notes><custom1><style face="normal" font="default" size="100%">software engineering</style></custom1><custom2><style face="normal" font="default" size="100%">case study</style></custom2></record></records></xml>
