%0 Book Section %B Open Source Software: Mobile Open Source Technologies %D 2014 %T An Exploration of Code Quality in FOSS Projects %A Ahmed, Iftekhar %A Ghorashi, Soroush %A Jensen, Carlos %E Corral, Luis %E Sillitti, Alberto %E Succi, Giancarlo %E Vlasenko, Jelena %E Wasserman, AnthonyI. %K Code Quality %K FOSS %K open source software %K success metrics %X It is a widely held belief that Free/Open Source Software (FOSS) development leads to the creation of software with the same, if not higher quality compared to that created using proprietary software development models. However there is little research on evaluating the quality of FOSS code, and the impact of project characteristics such as age, number of core developers, code-base size, etc. In this exploratory study, we examined 110 FOSS projects, measuring the quality of the code and architectural design using code smells. We found that, contrary to our expectations, the overall quality of the code is not affected by the size of the code base, but that it was negatively impacted by the growth of the number of code contributors. Our results also show that projects with more core developers don’t necessarily have better code quality. %B Open Source Software: Mobile Open Source Technologies %S IFIP Advances in Information and Communication Technology %I Springer Berlin Heidelberg %V 427 %P 181-190 %@ 978-3-642-55127-7 %U http://dx.doi.org/10.1007/978-3-642-55128-4_26 %R 10.1007/978-3-642-55128-4_26 %0 Conference Paper %B Proceedings of The International Symposium on Open Collaboration %D 2014 %T The Impact of Automatic Crash Reports on Bug Triaging and Development in Mozilla %A Ahmed, Iftekhar %A Mohan, Nitin %A Jensen, Carlos %K Automatic Crash reporting %K debugging %K FOSS %K Free/Open Source Software %K Open Bug Reporting %K testing %X Free/Open Source Software projects often rely on users submitting bug reports. However, reports submitted by novice users may lack information critical to developers, and the process may be intimidating and difficult. To gather more and better data, projects deploy automatic crash reporting tools, which capture stack traces and memory dumps when a crash occurs. These systems potentially generate large volumes of data, which may overwhelm developers, and their presence may discourage users from submitting traditional bug reports. In this paper, we examine Mozilla's automatic crash reporting system and how it affects their bug triaging process. We find that fewer than 0.00009% of crash reports end up in a bug report, but as many as 2.33% of bug reports have data from crash reports added. Feedback from developers shows that despite some problems, these systems are valuable. We conclude with a discussion of the pros and cons of automatic crash reporting systems. %B Proceedings of The International Symposium on Open Collaboration %S OpenSym '14 %I ACM %C New York, NY, USA %P 1:1–1:8 %@ 978-1-4503-3016-9 %U http://doi.acm.org/10.1145/2641580.2641585 %R 10.1145/2641580.2641585