TY - Generic T1 - Coordination in OSS 2.0: ANT Approach T2 - Proceedings of the 52nd Hawai'i International Conference on System Sciences (HICSS-52) Y1 - 2019 A1 - Sangseok You A1 - Kevin Crowston A1 - Jeffery Saltz A1 - Yatish Hegde KW - actor-network theory KW - free/libre open source KW - Stigmergy AB -

Open source software projects are increasingly driven by a combination of independent and professional developers, the former volunteers and the later hired by a company to contribute to the project to support commercial product development. This mix of developers has been referred to as OSS 2.0. However, we do not fully understand the multi-layered coordination spanning individuals, teams, and organizations. Using Actor-Network Theory (ANT), we describe how coordination and power dynamics unfold among developers and how different tools and artifacts both display activities and mediate coordination efforts. Internal communication within an organization was reported to cause broken links in the community, duplication of work, and political tensions. ANT shows how tools and code can exercise agency and alter a software development process as an equivalently active actor of the scene. We discuss the theoretical and practical implications of the changing nature of open source software development.

JF - Proceedings of the 52nd Hawai'i International Conference on System Sciences (HICSS-52) UR - http://hdl.handle.net/10125/59538 ER - TY - JOUR T1 - Core-periphery communication and the success of free/libre open source software projects JF - Journal of Internet Services and Applications Y1 - 2017 A1 - Kevin Crowston A1 - Shamshurin, Ivan KW - Apache Software Foundation KW - communication KW - core and periphery KW - free/libre open source software (FLOSS) KW - inclusive pronouns KW - natural language processing KW - project success AB - We examine the relationship between communications by core and peripheral members and Free/Libre Open Source Software project success. The study uses data from 74 projects in the Apache Software Foundation Incubator. We conceptualize project success in terms of success building a community, as assessed by graduation from the Incubator. We compare successful and unsuccessful projects on volume of communication and on use of inclusive pronouns as an indication of efforts to create intimacy among team members. An innovation of the paper is that use of inclusive pronouns is measured using natural language processing techniques. We also compare the volume and content of communication produced by core (committer) and peripheral members and by those peripheral members who are later elected to be core members. We find that volume of communication is related to project success but use of inclusive pronouns does not distinguish successful projects. Core members exhibit more contribution and use of inclusive pronouns than peripheral members. VL - 8 UR - http://rdcu.be/uguP IS - 10 ER - TY - CONF T1 - Core-Periphery Communication and the Success of Free/Libre Open Source Software Projects T2 - IFIP International Conference on Open Source Systems Y1 - 2016 A1 - Kevin Crowston A1 - Shamshurin, Ivan AB - We examine the relationship between communications by core and peripheral members and Free/Libre Open Source Software project success. The study uses data from 74 projects in the Apache Software Foundation Incubator. We conceptualize project success in terms of success building a community, as assessed by graduation from the Incubator. We compare successful and unsuccessful projects on volume of communication by core (committer) and peripheral community members and on use of inclusive pronouns as an indication of efforts to create intimacy among team members. An innovation of the paper is that use of inclusive pronouns is measured using natural language processing techniques. We find that core and peripheral members differ in their volume of contribution and in their use of inclusive pronouns, and that volume of communication is related to project success. JF - IFIP International Conference on Open Source Systems PB - Springer ER - TY - JOUR T1 - Collaboration through superposition: How the IT artifact as an object of collaboration affords technical interdependence without organizational interdependence JF - MIS Quarterly Y1 - 2014 A1 - James Howison A1 - Kevin Crowston AB - This paper develops a theory of collaboration through superposition: the process of depositing separate layers on top of each other over time. The theory is developed in a study of development of community-based Free and Open Source Software (FLOSS), through a research arc of discovery (participant observation), replication (two archival case studies) and formalization (a model of developer choices). The theory explains two key findings: 1) the overwhelming majority of work is accomplished with only a single programmer working on a task and 2) when tasks appear too large for an individual they are more likely to be deferred until they are easier, rather than being undertaken through structured teamwork. It is theorized that this way of organizing is key to successful open collaboration where the IT artifact is the object of collaboration, because it allows the co-production of technically interdependent artifacts through motivationally interdependent work. The affordances of software as an object of collaboration are used as a framework to analyze efforts to learn from FLOSS in other domains of work and in the IS function of for-profit organizations. VL - 38 UR - http://misq.org/collaboration-through-open-superposition.html IS - 1 U1 - R&R at MISQ ER - TY - CONF T1 - Cross-repository data linking with RDF and OWL: Towards common ontologies for representing FLOSS data T2 - WoPDaSD (Workshop on Public Data at International Conference on Open Source Software) Y1 - 2008 A1 - James Howison KW - FLOSS KW - FLOSSmole AB - This paper provides an approach to the problem of integrating data from multiple research repositories for FLOSS data. It introduces semantic web technologies (RDF, OWL, OWL-DL reasoners and SPARQL) to argue that these are useful for building shared research infrastructure. The paper illustrates its point by describing parts of an ontology developed for the integration and analysis of project communications drawn from FLOSSmole, the Notre Dame archive and direct collection of data. RDF vocabularies provide a way to agree on things we agree about as well as a way to be clearer about ways in which we disagree. JF - WoPDaSD (Workshop on Public Data at International Conference on Open Source Software) ER - TY - Generic T1 - Coordinating and motivating open source contributors Y1 - 2006 A1 - James Howison N1 - LinuxWorld Asia Presentation Slides from James Howison's LinuxWorld Asia Workshop A Black and White version of the slides from the workshop. ER - TY - Generic T1 - Core and periphery in Free/Libre and Open Source software team communications T2 - Proceedings of the 39th Hawai'i International Conference on System Sciences (HICSS-39) Y1 - 2006 A1 - Kevin Crowston A1 - Kangning Wei A1 - Li, Qing A1 - James Howison KW - FLOSS AB - The concept of the core group of developers is important and often discussed in empirical studies of FLOSS projects. This paper examines the question, “how does one empirically distinguish the core?” Being able to identify the core members of a FLOSS development project is important because many of the processes necessary for successful projects likely involve core members differently than peripheral members, so analyses that mix the two groups will likely yield invalid results. We compare 3 analysis approaches to identify the core: the named list of developers, a Bradford’s law analysis that takes as the core the most frequent contributors and a social network analysis of the interaction pattern that identifies the core in a core-and-periphery structure. We apply these measures to the interactions around bug fixing for 116 SourceForge projects. The 3 techniques identify different individuals as core members; examination of which individuals are identified leads to suggestions for refining the measures. All 3 measures though suggest that the core of FLOSS projects is a small fraction of the total number of contributors. JF - Proceedings of the 39th Hawai'i International Conference on System Sciences (HICSS-39) CY - Kaua'i, Hawai'i, January ER - TY - CONF T1 - Collaboration Using OSSmole: A repository of FLOSS data and analyses T2 - Symposium on Mining Software Repositories Y1 - 2005 A1 - Conklin, Megan S. A1 - James Howison A1 - Kevin Crowston AB - This paper introduces a collaborative project OSSmole designed to collect, share, and store comparable data and analyses of free, libre and open source software (FLOSS) development for research purposes. The project is designed to be a clearinghouse for data from the ongoing collection and analysis efforts of many disparate research groups. A collaborative data repository will reduce duplication and promote compatibility both across sources of FLOSS data and across research groups and analyses. The primary objective of OSSmole is to mine FLOSS source code repositories and provide the resulting data and summary analyses as open source products. However, the OSSmole data model additionally supports donated raw and summary data from a variety of open source researchers and other software repositories. The paper first outlines current difficulties with the typical quantitative FLOSS research process and uses these to develop requirements for such a collaborative data repository. Finally, the design of the OSSmole system is presented, as well as examples of current research and analyses using OSSmole. JF - Symposium on Mining Software Repositories CY - St. Louis ER - TY - Generic T1 - Coordination of Free/Libre Open Source Software development T2 - Proceedings of the International Conference on Information Systems (ICIS) Y1 - 2005 A1 - Kevin Crowston A1 - Kangning Wei A1 - Li, Qing A1 - Eseryel, U. Yeliz A1 - James Howison KW - Coordination KW - FLOSS AB - The apparent success of free/libre open source software (FLOSS) development projects such as Linux, Apache, and many others has raised the question, what lessons from FLOSS development can be transferred to mainstream software development? In this paper, we use coordination theory to analyze coordination mechanisms in FLOSS development and compare our analysis with existing literature on coordination in proprietary software development. We examined developer interaction data from three active and successful FLOSS projects and used content analysis to identify the coordination mechanisms used by the participants. We found that there were similarities between the FLOSS groups and the reported practices of the proprietary project in the coordination mechanisms used to manage task-task dependencies. However, we found clear differences in the coordination mechanisms used to manage task-actor dependencies. While published descriptions of proprietary software development involved an elaborate system to locate the developer who owned the relevant piece of code, we found that “self-assignment” was the most common mechanism across three FLOSS projects. This coordination mechanism is consistent with expectations for distributed and largely volunteer teams. We conclude by discussing whether these emergent practices can be usefully transferred to mainstream practice and indicating directions for future research. JF - Proceedings of the International Conference on Information Systems (ICIS) CY - Las Vegas, NV, USA, December ER - TY - CONF T1 - Coordination practices for bug fixing within FLOSS development teams T2 - 1st International Workshop on Computer Supported Activity Coordination, 6th International Conference on Enterprise Information Systems Y1 - 2004 A1 - Kevin Crowston A1 - Scozzi, Barbara AB - Free/Libre Open Source Software (FLOSS) 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. FLOSS development teams some how profit from the advantages and evade the challenges of distributed software development. Despite the relevance of the FLOSS both for research and practice, few studies have investigated the work practices adopted by these development teams. In this paper 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. JF - 1st International Workshop on Computer Supported Activity Coordination, 6th International Conference on Enterprise Information Systems CY - Porto, Portugal ER - TY - ABST T1 - Collective Learning in Distributed Groups (Research in progress) Y1 - 2003 A1 - Annabi, Hala A1 - Kevin Crowston KW - FLOSS PB - Syracuse University School of Information Studies ER -