@conference {942,
	title = {On mining data across software repositories},
	booktitle = {2009 6th IEEE International Working Conference on Mining Software Repositories (MSR)2009 6th IEEE International Working Conference on Mining Software Repositories},
	year = {2009},
	pages = {171 - 174},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Vancouver, BC, Canada},
	abstract = {Software repositories provide abundance of valuable information about open source projects. With the increase in the size of the data maintained by the repositories, automated extraction of such data from individual repositories, as well as of linked information across repositories, has become a necessity. In this paper we describe a framework that uses web scraping to automatically mine repositories and link information across repositories. We discuss two implementations of the framework. In the first implementation, we automatically identify and collect security problem reports from project repositories that deploy the Bugzilla bug tracker using related vulnerability information from the National Vulnerability Database. In the second, we collect security problem reports for projects that deploy the Launchpad bug tracker along with related vulnerability information from the National Vulnerability Database. We have evaluated our tool on various releases of Fedora, Ubuntu, Suse, RedHat, and Firefox projects. The percentage of security bugs identified using our tool is consistent with that reported by other researchers.},
	keywords = {bug reports, bugzilla, Fedora, Firefox, htmlscraper, integration, launchpad, national vulnerability database, RedHat, Suse, tracker, Ubuntu},
	isbn = {978-1-4244-3493-0},
	doi = {10.1109/MSR.2009.5069498},
	attachments = {https://flosshub.org/sites/flosshub.org/files/171MiningAcrossmsr09.pdf},
	author = {Anbalagan, Prasanth and Vouk, Mladen}
}
@conference {Yatani:2009:UWO:1518701.1518853,
	title = {Understanding how and why open source contributors use diagrams in the development of Ubuntu},
	booktitle = {Proceedings of the 27th international conference on Human factors in computing systems},
	series = {CHI {\textquoteright}09},
	year = {2009},
	note = {"To examine how and why diagrams are used in any and all aspects of the software development process of an OSS project, we performed a series of semi-structured interviews with contributors to one particular effort{\textemdash}Ubuntu."
"Our study was divided into two phases. First, we asked participants to complete a questionnaire and provide us with information and materials for discussion. The questionnaire featured questions about participants{\textquoteright} OSS experience, project participation, their roles in each project, and basic demographics. We also asked participants to share diagrams they had created, modified or used as part of their work on Ubuntu. In the second phase of the study, we conducted semi-structured interviews with participants."},
	pages = {995{\textendash}1004},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Some of the most interesting differences between Open Source Software (OSS) development and commercial co-located software development lie in the communication and collaboration practices of these two groups of developers. One interesting practice is that of diagramming. Though well studied and important in many aspects of co-located software development (including communication and collaboration among developers), its role in OSS development has not been thoroughly studied. In this paper, we report our investigation on how and why Ubuntu contributors use diagrams in their work. Our study shows that diagrams are not actively used in many scenarios where they commonly would in co-located software development efforts. We describe differences in the use and practices of diagramming, their possible reasons, and present design considerations for potential systems aimed at better supporting diagram use in OSS development.},
	keywords = {developers, diagramming, interviews, open source software (oss), software development, Ubuntu, visual representation},
	isbn = {978-1-60558-246-7},
	doi = {http://doi.acm.org/10.1145/1518701.1518853},
	url = {http://doi.acm.org/10.1145/1518701.1518853},
	author = {Yatani, Koji and Chung, Eunyoung and Jensen, Carlos and Truong, Khai N.}
}
@article {Wang:2007:MEO:1317471.1317479,
	title = {Measuring the evolution of open source software systems with their communities},
	journal = {SIGSOFT Softw. Eng. Notes},
	volume = {32},
	year = {2007},
	note = {"1. M1: The number of modules in software system at a series of specific moment.
2. CD: The number of developers (code contributors) at a series of specific moment.
3. MC: The correlation of M1 and CD."
"We get the information of Modules from the Launchpad[1] which is a distributed collaborative infrastructure for Ubuntu and other open source software development. Ubuntu mainly grows though a manner of adding new packages. So, we treat packages as the modules we mention before. In Ubuntu community, some members are in charge of auditing the packages and add them to Ubuntu, here developers are refers them."},
	month = {November},
	publisher = {ACM},
	address = {New York, NY, USA},
	abstract = {Open Source Software (OSS) has become the subject of much commercial and academic interest in last few years. As traditional software, OSS also evolves to fulfill the need of stakeholders. Therefore, providing quantitative metrics for OSS evolution has also become an urgent issue. However, most existing studies of software evolution have been performed on systems developed within a single company using traditional management techniques. These metrics models are inadequate to measure OSS evolution. In this paper, we describe a preliminary evolution metrics set for evaluating OSS. The most significant novelty of this model is that it takes specific properties of Open Source Community (OSC) into consideration. In another word, we measure the evolution of OSS and OSC together. We also provide a lightweight case study on Ubuntu project using this metrics set. We find out that the Open Source Community and its members also play essential role in OSS evolution. We expect this metrics model can bring better understandings and explanations of phenomena in open source development and evolution.},
	keywords = {evolution, launchpad, metrics, open source community, open source software, Ubuntu},
	issn = {0163-5948},
	doi = {http://doi.acm.org/10.1145/1317471.1317479},
	url = {http://doi.acm.org/10.1145/1317471.1317479},
	author = {Yi Wang and Defeng Guo and Shi, Huihui}
}
