@proceedings {1713,
	title = {Gender and Tenure Diversity in GitHub Teams},
	year = {2015},
	abstract = {Software development is usually a collaborative venture.
Open Source Software (OSS) projects are no exception; indeed,
by design, the OSS approach can accommodate teams
that are more open, geographically distributed, and dynamic
than commercial teams. This, we find, leads to OSS teams
that are quite diverse. Team diversity, predominantly in of-
fline groups, is known to correlate with team output, mostly
with positive effects. How about in OSS?
Using GITHUB, the largest publicly available collection of
OSS projects, we studied how gender and tenure diversity
relate to team productivity and turnover. Using regression
modeling of GITHUB data and the results of a survey, we
show that both gender and tenure diversity are positive and
significant predictors of productivity, together explaining a
sizable fraction of the data variability. These results can
inform decision making on all levels, leading to better outcomes
in recruiting and performance.},
	keywords = {gender, github, team},
	url = {http://bvasiles.github.io/papers/chi15.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/chi15.pdf},
	author = {Vasilescu, Bogdan and Posnett, Daryl and Ray, Baishakhi and van den Brand, Mark G.J. and Serebrenik, Alexander and Devanbu, Premkumar and Filkov, Vladimir}
}
@proceedings {export:232407,
	title = {The Uniqueness of Changes: Characteristics and Applications},
	year = {2015},
	month = {05/2015},
	abstract = {Changes in software development come in many forms. Some changes are frequent, idiomatic, or repetitive (e.g. adding checks for nulls or logging important values) while others are unique. We hypothesize that unique changes are different from the more common similar (or non-unique) changes in important ways; they may require more expertise or represent code that is more complex or prone to mistakes. As such, these changes are worthy of study. In this paper, we present a definition of unique changes and provide a method for identifying them in software project history. Based on the results of applying our technique on the Linux kernel and two large projects at Microsoft, we present an empirical study of unique changes. We explore how prevalent unique changes are and characterize where they occur along the architecture of the project. We further investigate developers{\textquoteright} contribution towards uniqueness of changes. We also describe potential applications of leveraging the uniqueness of change and implement two such applications, evaluating the risk of changes based on uniqueness and providing change recommendations for non-unique changes.},
	keywords = {linux kernel},
	url = {http://research.microsoft.com/apps/pubs/default.aspx?id=232407},
	attachments = {https://flosshub.org/sites/flosshub.org/files/MSR-TR-2014-149.pdf},
	author = {Ray, Baishakhi and Meiyappan Nagappan and Christian Bird and Nachiappan Nagappan and Zimmermann, Thomas}
}
