@article {9998, title = {Examining Open Innovation in Science (OIS): What Open Innovation can and cannot offer the science of science}, journal = {Innovation: Organization \& Management}, year = {2021}, abstract = {

Scholars across disciplines increasingly hear calls for more open and collaborative approaches to scientific research. The concept of Open Innovation in Science (OIS) provides a framework that integrates dispersed research efforts aiming to understand the antecedents, contingencies, and consequences of applying open and collaborative research practices. While the OIS framework has already been taken up by science of science scholars, its conceptual underpinnings require further specification. In this essay, we critically examine the OIS concept and bring to light two key aspects: 1) how OIS builds upon Open Innovation (OI) research by adopting its attention to boundary-crossing knowledge flows and by adapting other concepts developed and researched in OI to the science context as exemplified by two OIS cases in the area of research funding; 2) how OIS conceptualises knowledge flows across boundaries. While OI typically focuses on well-defined organizational boundaries, we argue that blurry and even invisible boundaries between communities of practice may more strongly constrain flows of knowledge related to openness and collaboration in science. Given the uptake of this concept, this essay brings needed clarity to the meaning of OIS, which has no particular normative orientation toward a close coupling between science and industry. We end by outlining the essay{\textquoteright}s contributions to OI and the science of science, as well as to science practitioners.

}, doi = {10.1080/14479338.2021.1999248}, author = {Susanne Beck and Marcel LaFlamme and Carsten Bergenholtz and Marcel Bogers and Tiare-Maria Brasseur and Marie-Louise Conradsen and Kevin Crowston and Diletta Di Marco and Agnes Effert and Despoina Filiou and Lars Frederiksen and Thomas Gillier and Marc Gruber and Carolin Haeussler and Karin Hoisl and Olga Kokshagina and Maria-Theresa Norn and Marion Poetz and Gernot Pruschak and Laia Pujol Priego and Agnieszka Radziwon and Alexander Ruser and Henry Sauermann and Sonali Shah and Julia Suess-Reyes and Christopher L. Tucci and Philipp Tuertscher and Jane Bj{\o}rn Vedel and Roberto Verganti and Jonathan Wareham and Sunny Mosangzi Xu} } @article {2017, title = {Work~features to support stigmergic coordination in distributed teams}, year = {2017}, type = {Interactive paper}, abstract = {

When work products are shared via a computer system, members of distributed teams can see the work products produced by remote colleagues as easily as those from local colleagues. Drawing on coordination theory and work in computer-supported cooperative work (CSCW), we theorize that these work products can provide information to support team coordination, that is, that work can be coordinated through the outcome of the work itself, a mode of coordination analogous to the biological process of stigmergy. Based on studies of documents and work, we postulate three features of work products that enable them to support team coordination, namely having a clear genre, being visible and mobile, and being combinable. These claims are illustrated with examples drawn from free/libre open source software development teams. We conclude by discussing how the proposed theory might be empirically tested.

}, keywords = {Coordination, Stigmergy}, attachments = {https://floss.syr.edu/sites/crowston.syr.edu/files/Stigmergy\%20theory\%20paper\%20to\%20share.pdf}, author = {Kevin Crowston and James Howison and Bolici, Francesco and Carsten {\O}sterlund} } @article {2016, title = {Manifesto on Engineering Academic Software (Dagstuhl Perspectives Workshop 16252)}, volume = {6}, year = {2016}, month = {12/2106}, institution = {Schloss Dagstuhl {\textendash} Leibniz Center for Informatics}, address = {Wadern, Germany}, abstract = {

Software is often a critical component of scientific research. It can be a component of the academic research methods used to produce research results, or it may itself be an academic research result. Software, however, has rarely been considered to be a citable artifact in its own right. With the advent of open-source software, artifact evaluation committees of conferences, and journals that include source code and running systems as part of the published artifacts, we foresee that software will increasingly be recognized as part of the academic process. The quality and sustainability of this software must be accounted for, both a priori and a posteriori. The Dagstuhl Perspectives Workshop on {\textquotedblleft}Engineering Academic Software{\textquotedblright} has examined the strengths, weaknesses, risks, and opportunities of academic software engineering. A key outcome of the workshop is this Dagstuhl Manifesto, serving as a roadmap towards future professional software engineering for software-based research instruments and other software produced and used in an academic context. The manifesto is expressed in terms of a series of actionable {\textquotedblleft}pledges{\textquotedblright} that users and developers of academic research software can take as concrete steps towards improving the environment in which that software is produced.

}, doi = {10.4230/DagMan.6.1.1}, author = {Alice Allen and Cecilia Aragon and Christoph Becker and Jeffrey Carver and Andrei Chi{\c s} and Benoit Combemale and Mike Croucher and Kevin Crowston and Daniel Garijo and Ashish Gehani and Carole Goble and Robert Haines and Robert Hirschfeld and James Howison and Kathryn Huff and Caroline Jay and Daniel S. Katz and Claude Kirchner and Katie Kuksenok and Ralf L{\"a}mmel and Oscar Nierstrasz and Matt Turk and van Nieuwpoort, Rob and Matthew Vaughn and Jurgen Vinju} } @article {9998, title = {Stigmergic coordination in FLOSS development teams: Integrating explicit and implicit mechanisms}, journal = {Cognitive Systems Research}, volume = {38}, year = {2016}, pages = {14{\textendash}22}, keywords = {Coordination, Stigmergy}, doi = {10.1016/j.cogsys.2015.12.003}, attachments = {https://floss.syr.edu/sites/crowston.syr.edu/files/COGSYS-RS-\%28HHS\%29-\%282015\%29-\%283\%29.pdf}, author = {Bolici, Francesco and James Howison and Kevin Crowston} } @inbook {2015, title = {Open Source Technology Development}, booktitle = {Handbook of Science and Technology Convergence}, year = {2015}, publisher = {Springer International Publishing}, organization = {Springer International Publishing}, address = {Cham}, isbn = {978-3-319-04033-2}, doi = {10.1007/978-3-319-04033-2_29-1}, attachments = {https://floss.syr.edu/sites/crowston.syr.edu/files/chp\%253A10.1007\%252F978-3-319-04033-2_29-1.pdf}, author = {Kevin Crowston}, editor = {Bainbridge, William Sims and Roco, Mihail C.} } @proceedings {crowston2012, title = {Amazon Mechanical Turk: A research tool for organizations and information systems scholars}, volume = {389}, year = {2012}, month = {12/2012}, pages = {210-221}, publisher = {Springer}, address = {Tampa, FL}, isbn = {978-3-642-35141-9}, issn = {1868-4238}, doi = {10.1007/978-3-642-35141-9}, attachments = {https://floss.syr.edu/sites/crowston.syr.edu/files/3890210.pdf}, author = {Kevin Crowston}, editor = {Anol Bhattacherjee and Brian Fitzgerald} } @conference {2011, title = {Work as coordination and coordination as work: A process perspective on FLOSS development projects}, booktitle = {Third International Symposium on Process Organization Studies}, year = {2011}, month = {6/2011}, address = {Corfu, Greece}, url = {http://www.process-symposium.com/}, attachments = {https://floss.syr.edu/sites/crowston.syr.edu/files/PROS-134.pdf}, author = {Kevin Crowston and Carsten {\O}sterlund and James Howison and Bolici, Francesco} } @article {2010, title = {The under-appreciated role of stigmergic coordination in software development}, year = {2010}, abstract = {

Coordination in software development teams has been a topic of perennial interest in empirical software engineering research. The vast majority of this literature has drawn on a conceptual separation between work and coordination mechanisms, separate from the work itself, which enable groups to achieve coordination. Traditional recommendations and software methods focused on planning: using analysis to predict and manage dependencies. Empirical research has demonstrated the limits of this approach, showing that many important dependencies are emergent and pointing to the persistent importance of explicit discussion to managing these dependencies as they arise. Drawing on work in Computer-Supported Collaborative Work and building from an analogy to collaboration amongst insects (stigmergy), we argue that the work product itself plays an under-appreciated role in helping software developers manage dependencies as they arise. This short paper presents the conceptual argument with empirical illustrations and explains why this mechanism would have significant implications for Software Engineering coordination research. We discuss issues in marshaling clear positive evidence, arguing that these issues are responsible, in part, for the under-consideration of this mechanism in software engineering and outlining research strategies which may overcome these issues.

}, keywords = {Coordination, FLOSS, Stigmergy}, attachments = {https://floss.syr.edu/sites/crowston.syr.edu/files/stigmergy-short.pdf}, author = {Bolici, Francesco and James Howison and Kevin Crowston} } @proceedings {Scialdone:2009, title = {Group Maintenance Behaviours of Core and Peripheral Members of Free/Libre Open Source Software Teams}, year = {2009}, address = {Skövde, Sweden, 3-6 June}, abstract = {Group Maintenance is pro-social, discretionary, and relation-building behavior that occurs between members of groups in order to maintain reciprocal trust and cooperation. This paper considers how Free/libre Open Source Software (FLOSS) teams demonstrate such behaviors within the context of e-mail, as this is the primary medium through which such teams communicate. We compare group maintenance behaviors between both core and peripheral members of these groups, as well as behaviors between a group that remains producing software today and one which has since dissolved. Our findings indicate that negative politeness tactics (those which show respect for the autonomy of others) may be the most instrumental group maintenance behaviors that contribute to a FLOSS group{\textquoteleft}s ability to survive and continue software production. }, keywords = {FLOSS, Group Maintenance}, attachments = {https://floss.syr.edu/sites/crowston.syr.edu/files/34finalmjs.pdf}, author = {Scialdone, Michael J. and Heckman, Robert and Kevin Crowston}, editor = {Boldyreff, Cornelia and Kevin Crowston and Lundell, Bj{\"o}rn and Wasserman, Tony} } @proceedings {Wiggins:2009, title = {Heartbeat: Measuring Active User Base and Potential User Interest in FLOSS Projects}, volume = {299}, year = {2009}, pages = {94-104}, publisher = {Springer Boston}, address = {Skövde, Sweden, 3-6 June}, abstract = {This paper presents a novel method and algorithm to measure the size of an open source project{\textquoteright}s user base and the level of potential user interest that it generates. Previously unavailable download data at a daily resolution confirms hypothesized patterns related to release cycles. In short, regular users rapidly download the software after a new release giving a way to measure the active user base. In contrast, potential new users download the application independently of the release cycle, and the daily download figures tend to plateau at this rate when a release has not been made for some time. An algorithm for estimating these measures from download time series is demonstrated and the measures are examined over time in two open source projects.}, isbn = {978-3-642-02031-5}, issn = {978-3-642-02031-5}, doi = {10.1007/978-3-642-02032-2\%5f10}, attachments = {https://floss.syr.edu/sites/crowston.syr.edu/files/heartbeat.pdf}, author = {Wiggins, Andrea and James Howison and Kevin Crowston}, editor = {Boldyreff, Cornelia and Kevin Crowston and Lundell, Bj{\"o}rn and Wasserman, Tony} } @conference {2004, title = {Effective work practices for software engineering}, booktitle = {Proceedings of the 2004 ACM workshop on Interdisciplinary software engineering research (WISER {\textquoteright}04)}, year = {2004}, pages = {18}, publisher = {ACM Press}, organization = {ACM Press}, address = {Newport Beach, CA, USA}, abstract = {We review the literature on Free/Libre Open Source Software (FLOSS) development and on software development, distributed work and teams more generally to develop a theoretical model to explain the performance of FLOSS teams. The proposed model is based on Hackman{\textquoteright}s [34] model of effectiveness of work teams, with coordination theory [52] and collective mind [79] to extend Hackman{\textquoteright}s model by elaborating team practices relevant to effectiveness in software development. We propose a set of propositions to guide further research.}, keywords = {FLOSS}, isbn = {1581139888}, doi = {10.1145/1029997.1030003}, attachments = {https://floss.syr.edu/sites/crowston.syr.edu/files/p18-crowston.pdf}, author = {Kevin Crowston and Annabi, Hala and James Howison and Masango, Chengetai} }