The cathedral and the bazaar: musings on Linux and open source by an accidental revolutionary
The cathedral and the bazaar: musings on Linux and open source by an accidental revolutionary
Toward an understanding of the motivation Open Source Software developers
Proceedings of the 25th International Conference on Software Engineering
MSR '05 Proceedings of the 2005 international workshop on Mining software repositories
How developer communication frequency relates to bug introducing changes
Proceedings of the joint international and annual ERCIM workshops on Principles of software evolution (IWPSE) and software evolution (Evol) workshops
An analysis of developer metrics for fault prediction
Proceedings of the 6th International Conference on Predictive Models in Software Engineering
The Swarm Model in Open Source Software Developer Communities
SOCIALCOM '10 Proceedings of the 2010 IEEE Second International Conference on Social Computing
The impact of bug management patterns on bug fixing: A case study of Eclipse projects
ICSM '12 Proceedings of the 2012 IEEE International Conference on Software Maintenance (ICSM)
| Hi-index | 0.00 |
In open source software development, the collaboration among developers is the key to improve software quality. In particular, to fix a bug related to various parts of a system, developers need collaboration because each developer usually has very limited knowledge about a large software system. This paper aims to clarify how narrow (or how wide) is each developer's knowledge area in the Eclipse project, and how often do developers need to collaborate with each other. As a result of analysis, we found that 50 % of committers take care of just one or two modules, which indicates the necessity of collaboration when a bug-fix affects multiple modules. In addition, we also found the significant relationship between committers' collaborations and the re-opened bugs. We conclude that a committer should be aware the risk of re-opened bugs caused by the collaboration.