@article {9999,
	title = {Building an apparatus: Refractive, reflective and diffractive readings of trace data},
	journal = {Journal of the Association for Information Systems},
	volume = {21},
	year = {2020},
	pages = {Article 10},
	abstract = {<p>We propose a set of methodological principles and strategies for the use of trace data, i.e., data capturing performances carried out on or via information systems, often at a fine level of detail. Trace data comes with a number of methodological and theoretical challenges associated with the inseparable nature of the social and material. Drawing on Haraway and Barad{\textquoteright}s distinctions among refraction, reflection and diffraction, we compare three approaches to trace data analysis. We argue that a diffractive methodology allows us to explore how trace data are not given but created though construction of a research apparatus to study trace data. By focusing on the diffractive ways in which traces ripple through an apparatus, it is possible to explore some of the taken-for-granted, invisible dynamics of sociomateriality. Equally, important this approach allows us to describe what and when distinctions within entwined phenomena emerge in the research process. Empirically, we illustrate the guiding principles and strategies by analyzing trace data from Gravity Spy, a crowdsourced citizen science project on Zooniverse. We conclude by suggesting that a diffractive methodology may help us draw together quantitative and qualitative research practices in new and productive ways that also raises interesting design questions.</p>},
	doi = {10.17705/1jais.00590 },
	attachments = {https://floss.syr.edu/sites/crowston.syr.edu/files/RA-JAIS-17-0130.R3.1_FIN\%20to\%20share.pdf},
	author = {Carsten {\O}sterlund and Kevin Crowston and Corey Brian Jackson}
}
@proceedings {568,
	title = {Boundary-Spanning Documents in Online FLOSS Communities: Does One Size Fit All?},
	year = {2013},
	month = {1/2013},
	address = {Wailea, HI},
	attachments = {https://floss.syr.edu/sites/crowston.syr.edu/files/floss\%20documents\%20to\%20distribute.pdf},
	author = {Carsten {\O}sterlund and Kevin Crowston}
}
@article {Crowston:2008,
	title = {Bug Fixing Practices within Free/Libre Open Source Software Development Teams},
	journal = {Journal of Database Management},
	volume = {19},
	number = {2},
	year = {2008},
	pages = {1{\textendash}30},
	abstract = {Free/libre open source software (FLOSS, e.g., Linux or Apache) is primarily developed by distributed teams. Developers contribute from around the world and coordinate their activity almost exclusively by means of email and bulletin boards, yet some how profit from the advantages and evade the challenges of distributed software development. In this article we investigate the structure and the coordination practices adopted by development teams during the bug-fixing process, which is considered one of main areas of FLOSS project success. In particular, based on a codification of the messages recorded in the bug tracking system of four projects, we identify the accomplished tasks, the adopted coordination mechanisms, and the role undertaken by both the FLOSS development team and the FLOSS community. We conclude with suggestions for further research.},
	issn = {1063-8016 },
	attachments = {https://floss.syr.edu/sites/crowston.syr.edu/files/jdbm2008.pdf},
	author = {Kevin Crowston and Scozzi, Barbara}
}
@inbook {Crowston:2008b,
	title = {The bug fixing process in proprietary and free/libre open source software: A coordination theory analysis},
	booktitle = {Business Process Transformation},
	year = {2008},
	pages = {69-99},
	publisher = {M. E. Sharpe},
	organization = {M. E. Sharpe},
	address = {Armonk, NY},
	abstract = {To support business process transformation, we must first be able to represent business processes in a way that allows us to compare and contrast them or to design new ones. In this paper, I use coordination theory to analyze the bug fixing processes in the proprietary operating system development group of a large mini-computer manufacturer and for the Free/Libre Open Source Software Linux operating system kernel. Three approaches to identifying dependencies and coordination mechanisms are presented. Mechanisms analyzed include those for task assignment, resource sharing and managing dependencies between modules of source code. The proprietary development organization assigned problem reports to engineers based on the module that appeared to be in error, since engineers only worked on particular modules. Alternative task assignment mechanisms include assignment to engineers based on workload or voluntary assignment, as in Linux. In the proprietary process, modules of source code were not shared, but rather {\textquotedblleft}owned{\textquotedblright} by one engineer, thus reducing the need for coordination. In Linux, where multiple developers can work on the same modules, alternative resource sharing mechanisms have been developed to manage source code. Finally, the proprietary developers managed dependencies between modules informally, relying on their personal knowledge of which other engineers used their code. The Linux process allows developers to change code in multiple modules, but emphasizes modularity to reduce the need to do so.},
	keywords = {Coordination, FLOSS},
	isbn = {9780765611918},
	attachments = {https://floss.syr.edu/sites/crowston.syr.edu/files/The\%20bug\%20fixing\%20process\%20in\%20proprietary\%20.pdf},
	author = {Kevin Crowston},
	editor = {Grover, Varun and Markus, M. Lynne}
}
@article {Howison:2007,
	title = {Building a collaboratory for research on open source software development (Poster)},
	year = {2007},
	address = {Ann Arbor, MI},
	keywords = {eScience, FLOSS},
	attachments = {https://floss.syr.edu/sites/crowston.syr.edu/files/Howison_eSocSciPoster-small.pdf},
	author = {James Howison and Squire, Megan and Kevin Crowston}
}
@article {2006,
	title = {Business Partnering with Open Source Communities:Opportunities, Perils and Pitfalls},
	year = {2006},
	note = {In July 2006 James Howison presented a tutorial at OSCON in Portland Oregon},
	keywords = {FLOSS},
	attachments = {https://floss.syr.edu/sites/crowston.syr.edu/files/Howison_OSCON_tutorial.pdf},
	author = {James Howison}
}
