An empirical study of the reliability of UNIX utilities
Communications of the ACM
Communications of the ACM
Software runaways: monumental software disasters
Software runaways: monumental software disasters
Extreme programming explained: embrace change
Extreme programming explained: embrace change
Adaptive software development: a collaborative approach to managing complex systems
Adaptive software development: a collaborative approach to managing complex systems
Rapid Development: Taming Wild Software Schedules
Rapid Development: Taming Wild Software Schedules
The Cathedral and the Bazaar
Culture Clash and the Road to World Domination
IEEE Software
Open Source Software Adoption: A Status Report
IEEE Software
Software development: processes and performance
IBM Systems Journal
An empirical study of the robustness of MacOS applications using random testing
Proceedings of the 1st international workshop on Random testing
Securing web application code by static analysis and runtime protection
Proceedings of the 13th international conference on World Wide Web
CONFER: towards groupware for building consensus in collaborative software engineering
AUIC '07 Proceedings of the eight Australasian conference on User interface - Volume 64
Students working for students on programming courses
Computers & Education
SEAFOOD'07 Proceedings of the 1st international conference on Software engineering approaches for offshore and outsourced development
Defining task oriented components
TAMODIA'07 Proceedings of the 6th international conference on Task models and diagrams for user interface design
Information and Software Technology
Collaboration in software development: a spotlight
Proceedings of the CUBE International Information Technology Conference
Key factors for adopting inner source
ACM Transactions on Software Engineering and Methodology (TOSEM)
| Hi-index | 0.00 |
In early 1999, VA Software launched a project to understand how the Internet development community had been able to produce software such as Linux, Apache and Samba that was generally developed faster and with higher quality than comparable commercially available alternatives [1,2,3,20]. Our goal was simple: determine how to make more software development projects successful.We discovered that successful Internet community projects employed a number of practices that were not well characterized by traditional software engineering methodologies. We now refer to those practices as Collaborative Software Development or CSD. Late in 1999 we developed the SourceForge platform to make it easy for even small software development projects to employ those practices, and in November of 1999 launched the SourceForge.net web site based on the SourceForge platform.The site was an overwhelming success, and in less than two years, grew to support more than 27,000 software development projects and over a quarter million software developers worldwide. SourceForge.net affords us an unequaled test bed for understanding CSD. In response to demand from companies seeking to enable CSD within their organizations, we announced a commercial version of the SourceForge platform, SourceForge Enterprise Edition, in August 2001.This paper describes the principles of CSD, the software development pain points those principles address, and our experience enabling CSD with the SourceForge platform.