@conference {Ahmed:2014:IAC:2641580.2641585,
	title = {The Impact of Automatic Crash Reports on Bug Triaging and Development in Mozilla},
	booktitle = {Proceedings of The International Symposium on Open Collaboration},
	series = {OpenSym {\textquoteright}14},
	year = {2014},
	pages = {1:1{\textendash}1:8},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {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{\textquoteright}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.
},
	keywords = {Automatic Crash reporting, debugging, FOSS, Free/Open Source Software, Open Bug Reporting, testing},
	isbn = {978-1-4503-3016-9},
	doi = {10.1145/2641580.2641585},
	url = {http://doi.acm.org/10.1145/2641580.2641585},
	author = {Ahmed, Iftekhar and Mohan, Nitin and Jensen, Carlos}
}
@proceedings {1451,
	title = {Exploring the Role of Outside Organizations in Free / Open Source Software Projects},
	volume = {378},
	year = {2012},
	month = {09/2012},
	pages = {201-215},
	publisher = {IFIP AICT},
	abstract = {Free/Open Source Software (FOSS) projects have a reputation for being grass-roots efforts driven by individual contributors volunteering their time and effort. While this may be true for a majority of smaller projects, it is not always the case for large projects. As projects grow in size, importance and complexity, many come to depend on corporations, universities, NGO{\textquoteright}s and governments, for support and contributions, either financially or through seconded staff. As outside organizations get involved in projects, how does this affect their governance, transparency and direction? To study this question we gathered bug reports and commit logs for GCC and the Linux Kernel. We found that outside organizations contribute a majority of code but rarely participate in bug triaging. Therefore their code does not necessarily address the needs of others and may distort governance and direction. We conclude that projects should examine their dependence on outside organizations},
	keywords = {bug reports, commit, Community sustainability, Contributor affiliation, gcc, governance, linux kernel, Participation metrics},
	url = {http://research.engr.oregonstate.edu/hci/sites/research.engr.oregonstate.edu.hci/files/papers/forrest2012exploring.pdf},
	author = {Forrest, Darren and Jensen, Carlos and Mohan, Nitin and Davidson, Jennifer}
}
