@proceedings {1378,
	title = {When Cultures Clash: Participation in Open Source Communities and Its Implications For Organizational Commitment},
	number = {7},
	year = {2011},
	abstract = {Software applications developed within the OSS community have enjoyed tremendous success and for-profit organizations are keen to tap into this significant pool of software development talent (Chesbrough 2003; Feller et al. 2008). Examples companies include Netscape, IBM and Google (Maccormack et al. 2006). These companies seek to benefit from the talent of a global and sometimes voluntary workforce by paying some employees to contribute to OSS projects (Raymond 1999, Shah 2006). This merging of open and traditional software development may cause developer stress based on conflicting OSS community and traditional software development norms. Specifically, developers must balance company intellectual property concerns with the reciprocal and community-based norms that drive OSS development (Stewart and Gosain 2006). When these values are not in sync, contributors that aim to abide by conflicting values may exhibit dysfunctional attitudes. Employee stress with respect to their role can be destructive to organizational outcomes (Maas and Matejka 2009; Aranya and Ferris 1984). This study develops an OSS context specific model that describes the relationship between clashing software development cultures and employee organizational commitment. We leverage the rich OSS literature and the research that focuses on organizational-professional conflict (OPC) to develop hypotheses linking clashing cultures and organizational commitment. These hypotheses are tested using a combination of archival data and a survey of 127 GNOME developers. The findings presented in this paper contribute to OSS literature and offer findings that will enable organizations to more successfully engage OSS communities.},
	keywords = {gnome},
	url = { http://aisel.aisnet.org/icis2011/proceedings/projmanagement/7 },
	author = {Daniel, Sherae L. and Maruping, Likoebe M. and Cataldo, Marcelo and Herbsleb, James}
}
@conference {717,
	title = {A Social Network Approach To Free/Open Source Software Simulation},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	note = {"Second, we use mailing list archives for three different projects. This gives us a more stringent network measure, since links are generated only when one developer communicates directly with another."
 
"The mailing lists were the developers list from a well deployed database server, the general list for an text and file processing library, and the general list for a smaller F/OSS web browser."},
	pages = {16-23},
	abstract = {Free and Open Source Software (F/OSS) development is a complex process that is just beginning to be understood. The actual development process is frequently characterized as disparate volunteer developers collaborating to create a piece of software. The developers of F/OSS, like most software engineers, spend a significant portion of their time fostering collaboration through various channels social communication. We have analyzed several methods of communication; a social networking site, project mailing lists, and developer weblogs; to gain an understanding of the social network structure behind F/OSS projects. This social network data was used to create a model of F/OSS development that allows for multiple projects, users, and developers with varying goals and socialization methods. Using this model we have been able to replicate some of the known phenomena observed in F/OSS and provide a first step in the creation of a robust model of F/OSS. },
	keywords = {email, mailing list, social network analysis},
	doi = {10.1.1.178.4984},
	url = {http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.178.4984},
	author = {Wagstrom, Patrick Adam and Herbsleb, James and Carley, Kathleen}
}
@conference {1159,
	title = {Why Not Improve Coordination in Distributed Software Development by Stealing Good Ideas from Open Source?},
	booktitle = {Proceedings of the 2nd ICSE Workshop on Open Source},
	year = {2002},
	keywords = {apache, communication, coordination, distributed},
	attachments = {https://flosshub.org/sites/flosshub.org/files/MockusHerbsleb.pdf},
	author = {Audris Mockus and Herbsleb, James}
}
@article {flosswp26,
	title = {A Case Study of Open Source Software Development: The Apache Server},
	journal = {Proceedings of the International Conference on Software Engineering (ICSE 2000)},
	year = {2000},
	note = {We used the following archival sources of data:
Developer email list (EMAIL).
Concurrent Version Control archive (CVS).
Problem reporting database (BUGDB).},
	month = {June},
	abstract = {According to its proponents, open source style software development has the capacity to compete successfully, and perhaps in many cases displace, traditional commercial development methods. We examine the development process of a major open source application, the Apache web server. By using email archives of source code change history and problem reports we quantify aspects of developer participation, core team size, code ownership, productivity, defect density, and problem resolution interval for this OSS project. This analysis reveals a unique process, which performs well on important measures.},
	keywords = {apache, bug fix revisions, bugs, core, cvs, defect density, developers, email archives, participation, productivity, revision control, revision history, roles, scm, source code, team size},
	attachments = {https://flosshub.org/sites/flosshub.org/files/mockusapache.pdf},
	author = {Audris Mockus and Roy Fielding and Herbsleb, James}
}
