@inbook {Bibi2016,
	title = {A Bayesian Belief Network for Modeling Open Source Software Maintenance Productivity},
	booktitle = {Open Source Systems: Integrating Communities: 12th IFIP WG 2.13 International Conference, OSS 2016, Gothenburg, Sweden, May 30 - June 2, 2016, Proceedings},
	year = {2016},
	pages = {32{\textendash}44},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	chapter = {A Bayesian Belief Network for Modeling Open Source Software Maintenance Productivity},
	address = {Cham},
	abstract = {Maintenance is one of the most effort consuming activities in the software development lifecycle. Efficient maintenance within short release cycles depends highly on the underlying source code structure, in the sense that complex modules are more difficult to maintain. In this paper we attempt to unveil and discuss relationships between maintenance productivity, the structural quality of the source code and process metrics like the type of a release and the number of downloads. To achieve this goal, we developed a Bayesian Belief Network (BBN) involving several maintainability predictors and three managerial indices for maintenance (i.e., duration, production, and productivity) on 20 open source software projects. The results suggest that maintenance duration depends on inheritance, coupling, and process metrics. On the other hand maintenance production and productivity depend mostly on code quality metrics.
},
	isbn = {978-3-319-39225-7},
	doi = {10.1007/978-3-319-39225-7_3},
	url = {http://dx.doi.org/10.1007/978-3-319-39225-7_3},
	author = {Bibi, Stamatia and Apostolos Ampatzoglou and Ioannis Stamelos},
	editor = {Kevin Crowston and Hammouda, Imed and Lundell, Bj{\"o}rn and Gregorio Robles and Gamalielsson, Jonas and Juho Lindman}
}
@inbook {Rodr{\'\i}guez-P{\'e}rez2016,
	title = {BugTracking: A Tool to Assist in the Identification of Bug Reports},
	booktitle = {Open Source Systems: Integrating Communities: 12th IFIP WG 2.13 International Conference, OSS 2016, Gothenburg, Sweden, May 30 - June 2, 2016, Proceedings},
	year = {2016},
	pages = {192{\textendash}198},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	chapter = {BugTracking: A Tool to Assist in the Identification of Bug Reports},
	address = {Cham},
	abstract = {Issue tracking systems are used, in most software projects, but in particular in almost all free open source software, to record many different kinds of issues: bug reports, feature requests, maintenance tickets and even design discussions. Identifying which of those issues are bug reports is not a trivial task. When researchers want to conduct studies on the bug reports, managed by a software development project, first of all they need to perform this identification.
The job for researchers here is very different from the bug triaging that researchers do. In the latter case, people with a considerate experience in the project make a decision based on the information available at that time (maybe just a short comment by some user), asking, if needed, for more details. In the former case, researchers usually have not that experience in the project, but they have at their use all the information produced, until the moment the issue was closed. This may include not only all comments and actions on the issue tracking system, but for example, discussions about a fix in the code review system, or the final fixing patch in the source code management system. Having all that information conveyed to the researchers, in an easy, flexible and quick way, accelerates and makes their decision process much more reliable. It simplifies large scale manual analysis of issues (in hundreds or thousands), helping researchers to ensure that they are really working with what they intend to work: bug reports.
This paper presents a tool designed to solve exactly the problem of providing the researchers with all the relevant information needed to decide whether an issue corresponds to a bug report or not. The tool uses information extracted automatically from the projects repositories. It offers a web-based interface which allows collaboration, traceability and transparency of the identification of bug reports. All this makes the process easier, faster, and more reliable.},
	isbn = {978-3-319-39225-7},
	doi = {10.1007/978-3-319-39225-7_16},
	url = {http://dx.doi.org/10.1007/978-3-319-39225-7_16},
	author = {Rodr{\'\i}guez-P{\'e}rez, Gema and Gonzalez-Barahona, Jes{\'u}s M. and Gregorio Robles and Dalipaj, Dorealda and Sekitoleko, Nelson},
	editor = {Kevin Crowston and Hammouda, Imed and Lundell, Bj{\"o}rn and Gregorio Robles and Gamalielsson, Jonas and Juho Lindman}
}
@inbook {Kalliamvakou2016,
	title = {Certification of Open Source Software {\textendash} A Scoping Review},
	booktitle = {Open Source Systems: Integrating Communities: 12th IFIP WG 2.13 International Conference, OSS 2016, Gothenburg, Sweden, May 30 - June 2, 2016, Proceedings},
	year = {2016},
	pages = {111{\textendash}122},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	chapter = {Certification of Open Source Software {\textendash} A Scoping Review},
	address = {Cham},
	abstract = {Open source software (OSS) systems are being used for increasingly critical functions in modern societies, e.g., in health care, finance, government, defense, and other safety and security sensitive sectors. There is an increasing interest in software certification as a means to assure quality and dependability of such systems. However, the development processes and organizational structures of OSS projects can be substantially different from traditional closed-source projects. The distributed, {\textquotedblleft}bazaar-style{\textquotedblright} approach to software development in OSS systems is often perceived incompatible with certification. This paper presents the results of a scoping review on certification in OSS systems in order to identify and categorize key issues and provide a comprehensive overview of the current evidence on this topic.
},
	isbn = {978-3-319-39225-7},
	doi = {10.1007/978-3-319-39225-7_9},
	url = {http://dx.doi.org/10.1007/978-3-319-39225-7_9},
	author = {Kalliamvakou, Eirini and Weber, Jens and Knauss, Alessia},
	editor = {Kevin Crowston and Hammouda, Imed and Lundell, Bj{\"o}rn and Gregorio Robles and Gamalielsson, Jonas and Juho Lindman}
}
@inbook {Murphy2016,
	title = {Classifying Organizational Adoption of Open Source Software: A Proposal},
	booktitle = {Open Source Systems: Integrating Communities: 12th IFIP WG 2.13 International Conference, OSS 2016, Gothenburg, Sweden, May 30 - June 2, 2016, Proceedings},
	year = {2016},
	pages = {123{\textendash}133},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	chapter = {Classifying Organizational Adoption of Open Source Software: A Proposal},
	address = {Cham},
	abstract = {Staged adoption models are a common feature of information systems (IS) adoption literature, yet these are rarely used in open source software (OSS) adoption studies. In this paper, a staged model for classifying the organizational adoption of OSS is proposed, based upon a critical review of existing staged adoption models and factors identified from OSS adoption literature. Innovations in the proposed model include: defined transition pathways between stages, additional stages and a decomposition of cessation of use into four distinct pathways.
},
	isbn = {978-3-319-39225-7},
	doi = {10.1007/978-3-319-39225-7_10},
	url = {http://dx.doi.org/10.1007/978-3-319-39225-7_10},
	author = {Murphy, Stephen and Cox, Sharon},
	editor = {Kevin Crowston and Hammouda, Imed and Lundell, Bj{\"o}rn and Gregorio Robles and Gamalielsson, Jonas and Juho Lindman}
}
@inbook {Harzl2016,
	title = {Combining FOSS and Kanban: An Action Research},
	booktitle = {Open Source Systems: Integrating Communities: 12th IFIP WG 2.13 International Conference, OSS 2016, Gothenburg, Sweden, May 30 - June 2, 2016, Proceedings},
	year = {2016},
	pages = {71{\textendash}84},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	chapter = {Combining FOSS and Kanban: An Action Research},
	address = {Cham},
	abstract = {Even though Free and Open Source Software (FOSS) and Agile Software Development (ASD) have been recognized as important ways to develop software, share some similarities, and have many success stories, there is a lack of research regarding the comprehensive integration of both practices. This study attempts to consolidate these methods and to answer if FOSS and ASD can be combined successfully. Action Reseach (AR) is conducted with one sub-team of a large FOSS project. We performed two action research cycles based on the Kanban method. This paper has two main contributions; first, it describes a real world situation, where Kanban is applied to a FOSS project, and second, it suggests two new Kanban practices. These two methods are targeted specifically at FOSS projects and their characteristics.
},
	isbn = {978-3-319-39225-7},
	doi = {10.1007/978-3-319-39225-7_6},
	url = {http://dx.doi.org/10.1007/978-3-319-39225-7_6},
	author = {Harzl, Annemarie},
	editor = {Kevin Crowston and Hammouda, Imed and Lundell, Bj{\"o}rn and Gregorio Robles and Gamalielsson, Jonas and Juho Lindman}
}
@inbook {Crowston2016,
	title = {Core-Periphery Communication and the Success of Free/Libre Open Source Software Projects},
	booktitle = {Open Source Systems: Integrating Communities: 12th IFIP WG 2.13 International Conference, OSS 2016, Gothenburg, Sweden, May 30 - June 2, 2016, Proceedings},
	year = {2016},
	pages = {45{\textendash}56},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	address = {Cham},
	abstract = {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.
},
	isbn = {978-3-319-39225-7},
	doi = {10.1007/978-3-319-39225-7_4},
	url = {http://dx.doi.org/10.1007/978-3-319-39225-7_4},
	author = {Kevin Crowston and Shamshurin, Ivan},
	editor = {Kevin Crowston and Hammouda, Imed and Lundell, Bj{\"o}rn and Gregorio Robles and Gamalielsson, Jonas and Juho Lindman}
}
@inbook {Poo-Caama{\~n}o2016,
	title = {Herding Cats: A Case Study of Release Management in an Open Collaboration Ecosystem},
	booktitle = {Open Source Systems: Integrating Communities: 12th IFIP WG 2.13 International Conference, OSS 2016, Gothenburg, Sweden, May 30 - June 2, 2016, Proceedings},
	year = {2016},
	pages = {147{\textendash}162},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	chapter = {Herding Cats: A Case Study of Release Management in an Open Collaboration Ecosystem},
	address = {Cham},
	abstract = {Release management in large-scale software development projects requires significant communication and coordination. It is particularly challenging in Free and Open Source Software (FOSS) ecosystems, in which hundreds of loosely connected developers and their projects need to be coordinated to release software to a schedule. To better understand this process and its challenges, we analyzed over two and half years of communication in the GNOME ecosystem and studied developers{\textquoteright} interactions. We cataloged communication channels, categorized high level communication and coordination activities in one of them, and triangulated our results by interviewing developers. We found that a release schedule, influence instead of direct control, and diversity are factors that impact positively the release process in the GNOME ecosystem. Our results can help organizations build better large-scale teams and show that research focused on individual projects might miss important parts of the picture.
},
	isbn = {978-3-319-39225-7},
	doi = {10.1007/978-3-319-39225-7_12},
	url = {http://dx.doi.org/10.1007/978-3-319-39225-7_12},
	author = {Poo-Caama{\~n}o, Germ{\'a}n and Singer, Leif and Knauss, Eric and Daniel M. German},
	editor = {Kevin Crowston and Hammouda, Imed and Lundell, Bj{\"o}rn and Gregorio Robles and Gamalielsson, Jonas and Juho Lindman}
}
@inbook {Hirao2016,
	title = {The Impact of a Low Level of Agreement Among Reviewers in a Code Review Process},
	booktitle = {Open Source Systems: Integrating Communities: 12th IFIP WG 2.13 International Conference, OSS 2016, Gothenburg, Sweden, May 30 - June 2, 2016, Proceedings},
	year = {2016},
	pages = {97{\textendash}110},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	address = {Cham},
	abstract = {Software code review systems are commonly used in software development. In these systems, many patches are submitted to improve the quality. To verify the quality, voting is commonly used by contributors; however, there still exists a major problem, namely, that reviewers do not always simply reach a broad agreement. In our previous study, we found that consensus is not usually reached, implying that an individual reviewer{\textquoteright}s final decision usually differs from that of the majority of the other reviewers. In this study, we further investigate the reasons why such situations often occur, and provide suggestions for better handling of these problems. Our analysis of the Qt and OpenStack project datasets allow us to suggest that a patch owner should select more appropriate reviewers who often agree with others{\textquoteright} decisions.
},
	isbn = {978-3-319-39225-7},
	doi = {10.1007/978-3-319-39225-7_8},
	url = {http://dx.doi.org/10.1007/978-3-319-39225-7_8},
	author = {Hirao, Toshiki and Ihara, Akinori and Ueda, Yuki and Phannachitta, Passakorn and Matsumoto, Ken-ichi},
	editor = {Kevin Crowston and Hammouda, Imed and Lundell, Bj{\"o}rn and Gregorio Robles and Gamalielsson, Jonas and Juho Lindman}
}
@inbook {M{\"a}enp{\"a}{\"a}2016,
	title = {In-between Open and Closed - Drawing the Fine Line in Hybrid Communities},
	booktitle = {Open Source Systems: Integrating Communities: 12th IFIP WG 2.13 International Conference, OSS 2016, Gothenburg, Sweden, May 30 - June 2, 2016, Proceedings},
	year = {2016},
	pages = {134{\textendash}146},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	chapter = {In-between Open and Closed - Drawing the Fine Line in Hybrid Communities},
	address = {Cham},
	abstract = {Today, the community driven development model extends into a variety of new, often web based collaborations. Among these are hybrid open source development set ups in which various online tools are used to facilitate cooperation between virtual teams of commercial and voluntary stakeholders. As yet, how these relationships form and evolve is not understood extensively. This article presents a longitudinal case study of a smartphone startup that founded its early product development strategy on reliance on feedback from its customers through a web based question and answer forum. With this, the company managed to extend values typical for open source communities to support development of its proprietary software. Our main findings include that the challenge in similar settings lies in striking the right balance between the open and the proprietary {\textendash} while overt openness may risk the competitive advantage of a company, leaving too much behind closed boundaries can create unnecessary friction in the relationship.
},
	isbn = {978-3-319-39225-7},
	doi = {10.1007/978-3-319-39225-7_11},
	url = {http://dx.doi.org/10.1007/978-3-319-39225-7_11},
	author = {M{\"a}enp{\"a}{\"a}, Hanna and Kilamo, Terhi and M{\"a}nnist{\"o}, Tomi},
	editor = {Kevin Crowston and Hammouda, Imed and Lundell, Bj{\"o}rn and Gregorio Robles and Gamalielsson, Jonas and Juho Lindman}
}
@inbook {Gamalielsson2016,
	title = {On Involvement in Open Standards: How Do Organisations Contribute to W3C Standards Through Editorship?},
	booktitle = {Open Source Systems: Integrating Communities: 12th IFIP WG 2.13 International Conference, OSS 2016, Gothenburg, Sweden, May 30 - June 2, 2016, Proceedings},
	year = {2016},
	pages = {57{\textendash}70},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	chapter = {On Involvement in Open Standards: How Do Organisations Contribute to W3C Standards Through Editorship?},
	address = {Cham},
	abstract = {Over the years, a number of open standards have been developed and implemented in software for addressing a number of challenges, such as lock-in, interoperability and longevity of software systems and associated digital artefacts. Understanding organisational involvement and collaboration in standardisation is important for informing any future policy and organisational decisions concerning involvement in standardisation. The overarching goal of the study is to establish how organisations contribute to open standards development through editorship. Specifically, the focus is on open standards development in W3C. Through an analysis of editorship for all W3C recommendations we contribute novel findings concerning organisational involvement and collaboration, and highlight contributions from different types of organisations and countries for headquarter of each organisation. We make three principal contributions. First, we establish an overall characterisation of organisational involvement in W3C standardisation. Second, we report on organisational involvement in W3C standardisation over time. Third, we establish organisational collaboration in W3C standardisation through social network analysis.
},
	isbn = {978-3-319-39225-7},
	doi = {10.1007/978-3-319-39225-7_5},
	url = {http://dx.doi.org/10.1007/978-3-319-39225-7_5},
	author = {Gamalielsson, Jonas and Lundell, Bj{\"o}rn},
	editor = {Kevin Crowston and Hammouda, Imed and Lundell, Bj{\"o}rn and Gregorio Robles and Gamalielsson, Jonas and Juho Lindman}
}
@inbook {Berger2016,
	title = {An Open Continuous Deployment Infrastructure for a Self-driving Vehicle Ecosystem},
	booktitle = {Open Source Systems: Integrating Communities: 12th IFIP WG 2.13 International Conference, OSS 2016, Gothenburg, Sweden, May 30 - June 2, 2016, Proceedings},
	year = {2016},
	pages = {177{\textendash}183},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	chapter = {An Open Continuous Deployment Infrastructure for a Self-driving Vehicle Ecosystem},
	address = {Cham},
	abstract = {Self-driving vehicles are an ongoing research and engineering topic even though first automotive OEMs started to deploy such features to their premium vehicles. Chalmers University of Technology and University of Gothenburg are operating and maintaining a vehicle laboratory comprising 1/10 scaled cars, a Volvo XC90, and a Volvo FH truck to conduct studies with automated driving. This laboratory is used both from researchers from different disciplines and in education. The experimental software for all these platforms is powered by the same software environment for different hardware architectures. Therefore, maintaining and deploying new features and bugfixes to the users of this laboratory in a fast way needs to be organized in a reproducible yet easily maintainable manner. This paper outlines our open approach to encapsulate our build, test, and deployment process using VirtualBox, Docker, and Jenkins.
},
	isbn = {978-3-319-39225-7},
	doi = {10.1007/978-3-319-39225-7_14},
	url = {http://dx.doi.org/10.1007/978-3-319-39225-7_14},
	author = {Berger, Christian},
	editor = {Kevin Crowston and Hammouda, Imed and Lundell, Bj{\"o}rn and Gregorio Robles and Gamalielsson, Jonas and Juho Lindman}
}
@inbook {Abdulwahhab2016,
	title = {The Role of Local Open Source Communities in the Development of Open Source Projects},
	booktitle = {Open Source Systems: Integrating Communities: 12th IFIP WG 2.13 International Conference, OSS 2016, Gothenburg, Sweden, May 30 - June 2, 2016, Proceedings},
	year = {2016},
	pages = {3{\textendash}15},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	chapter = {The Role of Local Open Source Communities in the Development of Open Source Projects},
	address = {Cham},
	abstract = {This paper investigates the position of local open source communities (LOSCs) in the development of open source projects (OSPs). We have conducted an empirical study to examine the role of LOSCs, their way of working, and the benefits/challenges they experience compared to the overall global community. The qualitative investigation consisted of ten semi-structured interviews with members within different LOSCs. The results confirm the importance of LOSCs and the pivotal role they play in the development of OSPs. In many cases, they act as the middleman between individual members and the project{\textquoteright}s global community. However, LOSCs have their own kinds of challenges.
},
	isbn = {978-3-319-39225-7},
	doi = {10.1007/978-3-319-39225-7_1},
	url = {http://dx.doi.org/10.1007/978-3-319-39225-7_1},
	author = {Abdulwahhab, Sinan and Alabady, Yazen and Sattar, Yacoub and Hammouda, Imed},
	editor = {Kevin Crowston and Hammouda, Imed and Lundell, Bj{\"o}rn and Gregorio Robles and Gamalielsson, Jonas and Juho Lindman}
}
@article {1864,
	title = {Roles and politeness behavior in community-based free/libre open source software development},
	journal = {Information \& Management},
	year = {2016},
	month = {11/2016},
	abstract = {Community-based Free/Libre Open Source Software (FLOSS) development relies on contributions from both core and peripheral members. Prior research on core{\textendash}periphery has focused on software coding-related behaviors. We study how core{\textendash}periphery roles are related to social-relational behavior in terms of politeness behavior. Data from two FLOSS projects suggest that both core and peripheral members use more positive politeness strategies than negative strategies. Further, core and peripheral members use different strategies to protect positive face in positive politeness, which we term respect and intimacy, respectively. Our results contribute to FLOSS research and politeness theory.

},
	keywords = {Core{\textendash}periphery structure, open source software development, Politeness behavior},
	issn = {03787206},
	doi = {10.1016/j.im.2016.11.006},
	url = {https://crowston.syr.edu/sites/crowston.syr.edu/files/Group_maintenance\%20paper\%20to\%20share.pdf},
	author = {Kangning Wei and Kevin Crowston and Eseryel, U.Yeliz and Robert Heckman}
}
@inbook {AbbaspourAsadollah2016,
	title = {A Study of Concurrency Bugs in an Open Source Software},
	booktitle = {Open Source Systems: Integrating Communities: 12th IFIP WG 2.13 International Conference, OSS 2016, Gothenburg, Sweden, May 30 - June 2, 2016, Proceedings},
	year = {2016},
	pages = {16{\textendash}31},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	chapter = {A Study of Concurrency Bugs in an Open Source Software},
	address = {Cham},
	abstract = {Concurrent programming puts demands on software debugging and testing, as concurrent software may exhibit problems not present in sequential software, e.g., deadlocks and race conditions. In aiming to increase efficiency and effectiveness of debugging and bug-fixing for concurrent software, a deep understanding of concurrency bugs, their frequency and fixing-times would be helpful. Similarly, to design effective tools and techniques for testing and debugging concurrent software understanding the differences between non-concurrency and concurrency bugs in real-word software would be useful. This paper presents an empirical study focusing on understanding the differences and similarities between concurrency bugs and other bugs, as well as the differences among various concurrency bug types in terms of their severity and their fixing time. Our basis is a comprehensive analysis of bug reports covering several generations of an open source software system. The analysis involves a total of 4872 bug reports from the last decade, including 221 reports related to concurrency bugs. We found that concurrency bugs are different from other bugs in terms of their fixing time and their severity. Our findings shed light on concurrency bugs and could thereby influence future design and development of concurrent software, their debugging and testing, as well as related tools.
},
	isbn = {978-3-319-39225-7},
	doi = {10.1007/978-3-319-39225-7_2},
	url = {http://dx.doi.org/10.1007/978-3-319-39225-7_2},
	author = {Abbaspour Asadollah, Sara and Sundmark, Daniel and Eldh, Sigrid and Hansson, Hans~ and Enoiu, Eduard Paul},
	editor = {Kevin Crowston and Hammouda, Imed and Lundell, Bj{\"o}rn and Gregorio Robles and Gamalielsson, Jonas and Juho Lindman}
}
@inbook {Coman2016,
	title = {Towards Open Source/Data in the Context of Higher Education: Pragmatic Case Studies Deployed in Romania},
	booktitle = {Open Source Systems: Integrating Communities: 12th IFIP WG 2.13 International Conference, OSS 2016, Gothenburg, Sweden, May 30 - June 2, 2016, Proceedings},
	year = {2016},
	pages = {184{\textendash}191},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	chapter = {Towards Open Source/Data in the Context of Higher Education: Pragmatic Case Studies Deployed in Romania},
	address = {Cham},
	abstract = {The open source ideology is unfortunately not so popular in Romania. This subject represents, to this day, an untackled problem especially in various local educational areas. The paper describes an interesting initiative taken this year by the Faculty of Computer Science, University of Ia{\c s}i, Romania to change the collective opinion by progressively pushing the new generations of students through a binding process with the ideas involved in the open source philosophy. Three ongoing initiatives addressing this problem are detailed, including the results we have obtained so far through them, and also the steps that are planned to be taken soon on the matter.
},
	isbn = {978-3-319-39225-7},
	doi = {10.1007/978-3-319-39225-7_15},
	url = {http://dx.doi.org/10.1007/978-3-319-39225-7_15},
	author = {Coman, Alexandru and C{\^\i}tea, Alexandru and Buraga, Sabin C.},
	editor = {Kevin Crowston and Hammouda, Imed and Lundell, Bj{\"o}rn and Gregorio Robles and Gamalielsson, Jonas and Juho Lindman}
}
@inbook {Heppler2016,
	title = {Who Cares About My Feature Request?},
	booktitle = {Open Source Systems: Integrating Communities: 12th IFIP WG 2.13 International Conference, OSS 2016, Gothenburg, Sweden, May 30 - June 2, 2016, Proceedings},
	year = {2016},
	pages = {85{\textendash}96},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	address = {Cham},
	abstract = {Previous studies on issue tracking systems for open source software (OSS) focused mainly on requests for bug fixes. However, requests to add a new feature or an improvement to an OSS project are often also made in an issue tracking system. These inquiries are particularly important because they determine the further development of the software. This study examines if there is any difference between requests of the IBM developer community and other sources in terms of the likelihood of successful implementation. Our study consists of a case study of the issue tracking system BugZilla in the Eclipse integrated development environment (IDE). Our hypothesis, which was that feature requests from outsiders have less chances of being implemented, than feature requests from IBM developers, was confirmed.
},
	isbn = {978-3-319-39225-7},
	doi = {10.1007/978-3-319-39225-7_7},
	url = {http://dx.doi.org/10.1007/978-3-319-39225-7_7},
	author = {Heppler, Lukas and Eckert, Remo and Stuermer, Matthias},
	editor = {Kevin Crowston and Hammouda, Imed and Lundell, Bj{\"o}rn and Gregorio Robles and Gamalielsson, Jonas and Juho Lindman}
}
@inbook {Robles2016,
	title = {Women in Free/Libre/Open Source Software: The Situation in the 2010s},
	booktitle = {Open Source Systems: Integrating Communities: 12th IFIP WG 2.13 International Conference, OSS 2016, Gothenburg, Sweden, May 30 - June 2, 2016, Proceedings},
	year = {2016},
	pages = {163{\textendash}173},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	chapter = {Women in Free/Libre/Open Source Software: The Situation in the 2010s},
	address = {Cham},
	abstract = {Women are underrepresented in the IT sector. But the situation in FLOSS (free, libre, open source software) development is really extreme in this respect: past publications and studies show a female participation of around 2 \% to 5 \% and have shed some light into this problem. In this paper, we give an update the state of knowledge to the current situation of gender in FLOSS, by analyzing the results of surveying more than 2,000 contributors to FLOSS projects in 2013, of which more than 200 were women. Our findings confirm that women enter the FLOSS community later than men, do primarily other tasks than coding, participate less if they have children, and have slightly different reasons to enter (and to stay in) the development communities they join. However, we also find evidence that women are joining FLOSS projects in higher numbers in recent years, and that the share of women devoting few hours per week to FLOSS and full-time dedication is higher than for men. All in all, comparing our results with the ones from the 2000s, the context of participation of women in FLOSS has not changed much.
},
	isbn = {978-3-319-39225-7},
	doi = {10.1007/978-3-319-39225-7_13},
	url = {http://dx.doi.org/10.1007/978-3-319-39225-7_13},
	author = {Gregorio Robles and Reina, Laura Arjona and Gonz{\'a}lez-Barahona, Jes{\'u}s M. and Dom{\'\i}nguez, Santiago Due{\~n}as},
	editor = {Kevin Crowston and Hammouda, Imed and Lundell, Bj{\"o}rn and Gregorio Robles and Gamalielsson, Jonas and Juho Lindman}
}
@inbook {1782,
	title = {Open Source Technology Development},
	booktitle = {Handbook of Science and Technology Convergence},
	year = {2015},
	pages = {1-9},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	abstract = {In this chapter, we introduce the practices of free/libre open source software (FLOSS) development as an instance of the convergence of technological affordances with novel social practices to create a novel mode of work. We then consider how FLOSS software might be used for various scientific applications, perhaps leading to a convergence of current distinct disciplines. We conclude by considering how the technologies and practices of FLOSS development might be applied to other settings, thus leading to further convergence of those settings.
},
	keywords = {Free/Libre Open Source Software},
	doi = {10.1007/978-3-319-04033-2_29-1},
	url = {http://dx.doi.org/10.1007/978-3-319-04033-2_29-1},
	author = {Kevin Crowston},
	editor = {Bainbridge, William Sims and Roco, Mihail C.}
}
@article {1805,
	title = {Stigmergic coordination in FLOSS development teams: Integrating explicit and implicit mechanisms},
	journal = {Cognitive Systems Research},
	year = {2015},
	month = {12/2015},
	abstract = {The vast majority of literature on coordination in team-based projects has drawn on a conceptual separation between explicit (e.g. plans, feedbacks) and implicit coordination mechanisms (e.g. mental maps, shared knowledge). This analytical distinction presents some limitations in explaining how coordination is reached in organizations characterized by distributed teams, scarce face to face meetings and fuzzy and changing lines of authority, as in free/libre open source software (FLOSS) development.

Analyzing empirical illustrations from two FLOSS projects, we highlight the existence of a peculiar model, stigmergic coordination, which includes aspects of both implicit and explicit mechanisms. The work product itself (implicit) and the characteristics under which it is shared (explicit) play an under-appreciated role in helping software developers manage dependencies as they arise. We develop this argument beyond the existing literature by working with an existing coordination framework, considering the role that the codebase itself might play at each step. We also discuss the features and the practices to support stigmergic coordination in distributed teams, as well as recommendations for future research. {\textquotedblleft}Not everything that implicitly exists needs to be rendered explicit{\textquotedblright} (Sloterdijk, 2009, p. 3).},
	keywords = {Coordination mechanisms, distributed teams, FLOSS teams, Stigmergic coordination},
	issn = {13890417},
	doi = {10.1016/j.cogsys.2015.12.003},
	url = {http://www.sciencedirect.com/science/article/pii/S1389041715000339},
	attachments = {https://flosshub.org/sites/flosshub.org/files/COGSYS-RS-\%28HHS\%29-\%282015\%29-\%283\%29.pdf},
	author = {Bolici, Francesco and Howison, James and Kevin Crowston}
}
@article {9400325220140301,
	title = {COLLABORATION THROUGH OPEN SUPERPOSITION: A THEORY OF THE OPEN SOURCE WAY.},
	journal = {MIS Quarterly},
	volume = {38},
	number = {1},
	year = {2014},
	pages = {29 - A9},
	abstract = {This paper develops and illustrates the theory of collaboration through open superposition: the process of depositing motivationally independent layers of work on top of each other over time. The theory is developed in a study of community-based free and open source software (FLOSS) development, through a research arc of discovery (participant observation), replication (two archival case studies), and theorization. The theory explains two key findings: (1) the overwhelming majority of work is accomplished with only a single programmer working on any one task, and (2) tasks that appear too large for any one individual are more likely to be deferred until they are easier rather than being undertaken through structured team work. Moreover, the theory explains how working through open superposition can lead to the discovery of a work breakdown that results in complex, functionally interdependent, work being accomplished without crippling search costs. We identify a set of socio-technical},
	keywords = {COLLABORATION, COMPUTER programmers, COMPUTER programming, COMPUTER software, coordination, FREEWARE (Computer software), INFORMATION storage \& retrieval systems, open source software, research, socio-technical system},
	issn = {02767783},
	author = {Howison, James and Kevin Crowston}
}
@article {flosswp403,
	title = {Free/Libre Open Source Software: What We Know and What We Do Not Know},
	journal = {ACM Computing Surveys},
	volume = {44},
	year = {2012},
	publisher = {ACM},
	edition = {2},
	abstract = {We review the empirical research on Free/Libre Open Source Software (FLOSS) development and assess the state of the literature. Our review is organized around an input-mediator-output-input (IMOI) model. We start with a description of the articles selected for the review. We then discuss findings of this literature categorized into issues pertaining to inputs (e.g., member characteristics, technology use and project characteristics), processes (software development and social processes), emergent states (e.g., trust and task related states) and outputs (e.g. team performance, FLOSS implementation and project evolution). Based on this review, we suggest research questions, including methodological and theoretical issues, to guide future inquiry in this area.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/floss_review_paper.pdf},
	author = {Kevin Crowston and Kangning Wei and Howison, James and Andrea Wiggins}
}
@inbook {1586,
	title = {FLOSS Project Effectiveness Measures},
	booktitle = {Successful OSS Project Design and Implementation},
	year = {2011},
	pages = {149-168},
	publisher = {Gower},
	organization = {Gower},
	abstract = {In this chapter, we develop and illustrate measures of the effectiveness of FLOSS
projects. FLOSS is a broad term used to embrace software that is developed
and released under either a {\textquotedblleft}free software{\textquotedblright} or an {\textquotedblleft}open source{\textquotedblright} license. While
the free software and the open source movements are distinct, both kinds of
licenses allow users to obtain and distribute the software{\textquoteright}s original source
without charge (software is {\textquotedblleft}free as in beer{\textquotedblright}) and to inspect, modify, and
redistribute modifications to the source code. While the open source movement
views these freedoms pragmatically (as a development methodology), the
free software movement emphasizes the meaning of {\textquotedblleft}free as in speech,{\textquotedblright}
which is captured by the French/Spanish libre, and one of their methods of
supporting those freedoms is {\textquotedblleft}copyleft,{\textquotedblright} famously embodied in the General
Public License, meaning that derivative works must be made available under
the same license terms as the original. This chapter focuses on development
practices in distributed work, which are largely shared across the movements.
For example, many (though by no means all) FLOSS developers contribute to
projects as volunteers without working for a common organization or being
paid. We therefore use the acronym FLOSS to refer collectively to free/libre and
open source software. 

It is important to develop measures of effectiveness for FLOSS projects for
at least two reasons. First, having such measures should be useful for FLOSS
project managers in assessing their projects. In some cases, FLOSS projects are
sponsored by third parties, so measures are useful for sponsors to understand
the return on their investment. Second, FLOSS is an increasingly visible and
copied mode of systems development. Millions of users depend on FLOSS
systems such as Linux and on the Internet, which is itself heavily dependent
on FLOSS tools, but as Scacchi (2002a, p. 1) notes, {\textquotedblleft}little is known about how
people in these communities coordinate software development across different
settings, or about what software processes, work practices, and organizational
contexts are necessary to their success.{\textquotedblright} An EU/NSF workshop on priorities for
FLOSS research identified the need both for learning from open source modes
of organization and production that could perhaps be applied to other areas
and for a concerted effort on open source in itself, for itself (Ghosh 2002). But to
be able to learn from teams that are working well, we need to have a definition
of working well.

In the following sections of the chapter, we will first discuss several
measures of project effectiveness, and then the procedure we used to obtain
data with which to operationalize these measures, followed by the details of
the analysis approach. We then present the results of this analysis and discuss
the implications of these results. We then illustrate how these measures can be
used to compare projects as part of a research study. We conclude with some
suggestions for future research. },
	url = {http://library.trec.co.ir/pdfTemp/97805660879501.pdf$\#$page=164},
	author = {Kevin Crowston and Howison, James}
}
@article {howison2010validity-issues,
	title = {Validity Issues in the Use of Social Network Analysis with Digital Trace data},
	journal = {Journal of the Association for Information Systems},
	volume = {12},
	year = {2011},
	chapter = {Article 2},
	abstract = {There is an exciting natural match between social network analysis methods and the growth of data sources produced by social interactions via information technologies, from online communities to corporate information systems. Information Systems researchers have not been slow to embrace this combination of method and data. Such systems increasingly provide "digital trace data" that provide new research opportunities. Yet digital trace data are substantively different from the survey and interview data for which network analysis measures and interpretations were originally developed. This paper examines ten validity issues associated with the combination of data digital trace data and social network analysis methods, with examples from the IS literature, to provide recommendations for improving the validity of research using this combination.},
	keywords = {information system, Online Communities, social network analysis, Virtuality},
	attachments = {https://flosshub.org/sites/flosshub.org/files/HowisonSNADigitalTraceData-WorkingPaper.pdf},
	author = {Howison, James and Andrea Wiggins and Kevin Crowston}
}
@conference {1256,
	title = {Analyzing Leadership Dynamics in Distributed Group Communication},
	booktitle = {2010 43rd Hawaii International Conference on System Sciences (HICSS 2010)},
	year = {2010},
	note = {"Our analysis examines the communication patterns in two FLOSS development projects, Fire and Gaim"
"These data were imported into a database to allow automated analysis. The Fire data set includes about 1,800 events in the user email list, 7,800 messages in the developer venues, and 1,300 events in the combined trackers, spanning a period of 54 months. The significantly larger Gaim data set included over 41,000 events in the user forum, over 30,000 events in the developer venues, and about 20,000 events in the trackers, generated over 78 months."
"The dynamic network analysis was performed using a scientific workflow tool, Taverna Workbench"},
	pages = {1 - 10},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Honolulu, Hawaii, USA},
	abstract = {We apply social network analysis (SNA) to examine the dynamics of leadership in distributed groups, specifically Free/Libre Open Source Software development projects, and its relation to group performance. Based on prior work on leadership in distributed groups, we identify leaders with those who make the highest level of contribution to the group and assess the degree of leadership by measuring centralization of communications. We compare the dynamics of leadership in two FLOSS projects, one more and one less effective. We find that in both projects, centralization was higher in developer-oriented communications venues than in user-oriented venues, suggesting higher degrees of leadership in developer venues. However, we do not find a consistent relation between centralization and effectiveness. We suggest that SNA can instead be useful for identifying interesting periods in the history of the project, e.g., periods where the leadership of the project is in transition.},
	keywords = {core, DYNAMICS, email, email archives, fire, flossmole, gaim, leadership, mailing list, project success, social network analysis, srda},
	isbn = {978-1-4244-5509-6},
	doi = {10.1109/HICSS.2010.62},
	attachments = {https://flosshub.org/sites/flosshub.org/files/07-06-02.pdf},
	author = {Kevin Crowston and Andrea Wiggins and Howison, James}
}
@conference {Wiggins:2010,
	title = {Reclassifying Success and Tragedy in {FLOSS} Projects},
	booktitle = {Proceedings of the International Conference on Open Source Systems (OSS)},
	year = {2010},
	month = {31 May{\textendash}2 June},
	address = {Notre Dame, IN, USA},
	abstract = {This paper presents the results of a replication of English \& Schweik{\textquoteright}s 2007 paper classifying FLOSS projects according to their stage of growth and indicators of success. We recreated the analysis using a comparable data set from 2006, with one additional point in time. We also expanded upon the original results by applying different criteria for evaluating the rate of new software releases for sustainability of project activity. We discuss the points of convergence and divergence from the original work from these extensions of the classification, and their implications for studying FLOSS development using archival data. The paper contributes new analysis of operationalizing success in FLOSS projects, with discussion of implications of the findings.},
	keywords = {FLOSS},
	author = {Andrea Wiggins and Kevin Crowston}
}
@article {838,
	title = {Envisioning National and International Research on the Multidisciplinary Empirical Science of Free/Open Source Software},
	year = {2009},
	month = {Spring 2009},
	author = {Walt Scacchi and Kevin Crowston and Madey, Greg and Squire, Megan}
}
@conference {594,
	title = {Group Maintenance Behaviors of Core and Peripherial Members of Free/Libre Open Source Software Teams},
	booktitle = {OSS2009: Open Source Ecosystems: Diverse Communities Interacting (IFIP 2.13)},
	series = {IFIP Advances in Information and Communication Technology },
	volume = {299/2009},
	year = {2009},
	month = {2009///},
	pages = {298 - 309},
	publisher = {Springer},
	organization = {Springer},
	chapter = {26},
	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{\textquoteright}s ability to survive and continue software production.
},
	issn = {978-3-642-02031-5},
	doi = {http://dx.doi.org/10.1007/978-3-642-02032-2_26},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Group\%20Maintenance\%20Behavior.pdf},
	author = {Scialdone, Michael and Li, Na and Robert Heckman and Kevin Crowston}
}
@conference {578,
	title = {Heartbeat: Measuring Active User Base and Potential User Interest in FLOSS Projects},
	booktitle = {OSS2009: Open Source Ecosystems: Diverse Communities Interacting (IFIP 2.13)},
	series = {IFIP Advances in Information and Communication Technology },
	volume = {299/2009},
	year = {2009},
	month = {2009///},
	pages = {94 - 104},
	publisher = {Springer},
	organization = {Springer},
	chapter = {10},
	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.
},
	issn = {978-3-642-02031-5},
	doi = {http://dx.doi.org/10.1007/978-3-642-02032-2_10},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Heatbeat\%20Measuring\%20Active\%20Use.pdf},
	author = {Andrea Wiggins and Howison, James and Kevin Crowston}
}
@conference {flosswp408,
	title = {Asynchronous Decision-Making in Distributed Teams},
	booktitle = {Computer Supported Cooperative Work 2008},
	year = {2008},
	month = {July},
	pages = {1{\textendash}2},
	abstract = {Extensive use of CSCW applications can influence group decision-making practices. Unlike previous research focused on the influence of synchronous ICTs, our study examines how group decisions are made in asynchronous communication channels. Our inductive qualitative analysis of 360 decision episodes of six FLOSS projects revealed diversity in decision-making practices, which appears to be related to differences in project effectiveness and task type. We also find that standardization of procedures through CSCW tools transforms the nature of some software development work from non-routine to standard procedure.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/CSCW2008FLOSSposter_sub.pdf , https://flosshub.org/sites/flosshub.org/files/CSCW2008Poster11x17sub.pdf},
	author = {Li, Qing and Robert Heckman and Eileen Allen and Kevin Crowston and Eseryel, U. Yeliz and James Howison and Andrea Wiggins}
}
@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},
	note = {"Projects to be studied were selected from those hosted on SourceForge, (http://sourceforge.net/)"
"we chose projects for which data we need for our analysis are publicly available, meaning a large number of bug reports"
"we chose teams with more than 8 developers"
"Only 140 projects of SourceForge met the first two requirements in 2002 when we drew our sample"
kicq, gaim, phpmyadmin, dynapi
"First, we obtained data indica- tive of the effectiveness of each project, such as its level of activity, number of downloads and development status"
"we elected to use objective data about the bug- fixing process. Hence, the main source of data about the bug-fixing process was obtained from the archives of the bug tracking system, which is the tool used to support the bug-fixing process"},
	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.},
	keywords = {activity, bug tracker, bug tracking system, coordination, downloads, dynapi, effectiveness, FLOSS, gaim, kicq, phpmyadmin, project success, size, status},
	issn = {1063-8016},
	attachments = {https://flosshub.org/sites/flosshub.org/files/CrowstonScozziJDBM2008.pdf},
	author = {Kevin Crowston and Barbara Scozzi}
}
@conference {566,
	title = {eResearch Workflows for Studying Free and Open Source Software Development},
	booktitle = {OSS2008: Open Source Development, Communities and Quality (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing},
	volume = {275/2008},
	year = {2008},
	month = {2008///},
	pages = {405 - 411},
	publisher = {Springer},
	organization = {Springer},
	chapter = {39},
	abstract = {This paper introduces eResearch workflow tools as a model for the research community studying free and open source software and its development. The paper first introduces eResearch as increasingly practiced in fields such as astrophysics and biology,then contrasts the practice of research on free and open source software. After outlining suitable research data sets the paper introduces a class of tools known as scientific workflow frameworks, focusing on one{\textemdash}Taverna{\textemdash}and introducing its features.To further explain the tool a complete workflow used for original research on FLOSS is described. Finally the paper considers the trade-offs inherent in these tools.
},
	issn = {978-0-387-09683-4},
	doi = {http://dx.doi.org/10.1007/978-0-387-09684-1_39},
	attachments = {https://flosshub.org/sites/flosshub.org/files/eResearch\%20Workflows.pdf},
	author = {Howison, James and Andrea Wiggins and Kevin Crowston}
}
@conference {flosswp1938,
	title = {eResearch Workflows for Studying Free and Open Source Software Development},
	booktitle = {OSS2008: Open Source Development, Communities and Quality (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing},
	volume = {275},
	year = {2008},
	month = {July},
	pages = {405{\textendash}411},
	publisher = {Springer},
	organization = {Springer},
	abstract = {This paper introduces eResearch workflow tools as a model for the research community studying free and open source software and its development. The paper first introduces eResearch as increasingly practiced in fields such as astrophysics and biology, then contrasts the practice of research on free and open source software. After outlining suitable research data sets the paper introduces a class of tools known as scientific workflow frameworks, focusing on one?Taverna?and introducing its features. To further explain the tool a complete workflow used for original research on FLOSS is described. Finally the paper considers the trade-offs inherent in these tools.},
	author = {Howison, James and Andrea Wiggins and Kevin Crowston}
}
@unpublished {flosswp415,
	title = {eScience for Free/Libre Open Source Software Researchers},
	year = {2008},
	month = {August},
	publisher = {FLOSSpapers},
	type = {Working Paper},
	abstract = {This paper presents a case study of the application of eScience tools and practices for the social science research community studying Free/Libre Open Source Software (FLOSS) development practices. We first describe what we mean by eScience and introduce research on FLOSS to motivate the need for eScience tools and approaches. We then describe our initial efforts to introduce eScience tools for FLOSS research, potential obstacles, and how the use of such tools might affect the practice of research in this field.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/eResearch2008iCS-working.pdf},
	author = {Kevin Crowston and Andrea Wiggins and James Howison}
}
@conference {flosswp402,
	title = {The motivational arc of massive virtual collaboration},
	booktitle = {IFIP WG 9.5, International Working Conference on Virtuality and Society: Massive Virtual Communities},
	year = {2008},
	month = {February},
	pages = {1{\textendash}13},
	abstract = {Massive virtual collaborations (MVC) involve large numbers of mostly unpaid contributors collectively creating new content. Wikipedia is the most dramatic example of MVC; smaller-scale examples include contributors to blogs and discussion groups and teams of programmers and users developing free/libre open source software (FLOSS). In this paper, we propose a model of motivations for contribution to MVC that integrates various theoretical perspectives. The model extends prior work by distinguishing three different levels of contribution to projects (initial, sustained and meta) and by capturing the dynamic and recursive effects of contributions on emergent individual and project states.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/crowston_fagnot_ifip.pdf},
	author = {Kevin Crowston and Isabelle Fagnot}
}
@conference {flosswp392,
	title = {Replication of FLOSS Research as eResearch},
	booktitle = {Oxford e-Research Conference 2008},
	year = {2008},
	month = {May},
	abstract = {We are working to introduce the ideas of eResearch to a multi-disciplinary research domain: those researchers examining Free/Libre and Open Source Software (FLOSS) and its development (Howison, Wiggins, \& Crowston, 2008).The first phase of this work focused on building a repository for data on FLOSS teams, FLOSSmole (Howison, Conklin, \& Crowston, 2006), and collaborating with other nascent data repositories in the field. Recently we have begun a second phase, which is to introduce another established principle of eResearch, that of broader collaboration through shared workflows accessing these data repositories. To provide an example of the potential value of this principle, we are replicating seminal FLOSS papers using eResearch approaches. This paper describes research outcomes and lessons learned from translating published literature into eResearch workflows.},
	keywords = {eResearch eScience},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Wiggins-FLOSS-eResearch.pdf},
	author = {Andrea Wiggins and James Howison and Kevin Crowston}
}
@conference {538,
	title = {Social Dynamics of FLOSS Team Communication Across Channels},
	booktitle = {OSS2008: Open Source Development, Communities and Quality (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing},
	volume = {275/2008},
	year = {2008},
	month = {2008///},
	pages = {131 - 142},
	publisher = {Springer},
	organization = {Springer},
	chapter = {11},
	abstract = {This paper extends prior investigation into the social dynamics of free and open source (FLOSS) teams by examining the methodological questions arising from research using social network analysis on open source projects. We evaluate the validity of data sampling by examining dynamics of communication centralization, which vary across multiple communication channels. We also introduce a method for intensity-based smoothing in dynamic social network analysis.
},
	issn = {978-0-387-09683-4},
	doi = {http://dx.doi.org/10.1007/978-0-387-09684-1_11},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Social\%20Dynamics\%20of\%20Floss.pdf},
	author = {Andrea Wiggins and Howison, James and Kevin Crowston}
}
@conference {622,
	title = {Emergent Decision-Making Practices in Free/Libre Open Source Software (Floss) Development Teams},
	booktitle = {OSS2007: Open Source Development, Adoption and Innovation (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing },
	volume = {234/2007},
	year = {2007},
	month = {2007///},
	pages = {71 - 84},
	publisher = {Springer},
	organization = {Springer},
	chapter = {6},
	abstract = {We seek to identify work practices that make Free/Libre Open Source Software (FLOSS) development teams effective. Particularly important to team effectiveness is decision making. In this paper, we report on an inductive qualitative analysis of 360 decision episodes of six FLOSS development teams. Our analysis revealed diversity in decision-making practices that seem to be related to differences in overall team characteristics and effectiveness.
},
	issn = {978-0-387-72485-0},
	doi = {http://dx.doi.org/10.1007/978-0-387-72486-7_6},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Emergent\%20Decision-Making.pdf},
	author = {Robert Heckman and Kevin Crowston and Eseryel, U. and Howison, James and Eileen Allen and Li, Qing}
}
@article {86,
	title = {The role of face-to-face meetings in technology-supported self-organizing distributed teams},
	journal = {Ieee Transactions on Professional Communication},
	volume = {50},
	number = {3},
	year = {2007},
	note = {Times Cited: 0},
	pages = {185-203},
	abstract = {We examine the role of face-to-face meetings in the context of technology-supported self-organizing distributed (or virtual teams), specifically Free/Libre Open Source Software (FLOSS) development teams. Based on a qualitative inductive analysis of data from interviews and observations at FLOSS conferences, we identify a variety of settings in which developers meet face-to-face, and we point out the activities performed in these settings and the benefits obtained. Contrary to conventional wisdom about distributed teams, FLOSS developers generally do not meet face-to-face until the project is well under way. An additional benefit offace-to-face meetings is time away from a regular job and speed of interaction for certain kinds of tasks.},
	author = {Kevin Crowston and James Howison and Chengetai Masango and Eseryel, U. Yeliz}
}
@article {flosswp405,
	title = {Self-organization of teams for free/libre open source software development},
	journal = {Information and Software Technology Journal},
	volume = {49},
	number = {564-575},
	year = {2007},
	note = {"First, the data from these projects that we needed for analysis had to be publicly available (ruling out projects that limit access to their email lists or trackers). Second, we chose the projects that had more than 7 members"..."projects that have attracted numerous developers beyond the initial project founders, are continuing to release software, have numerous downloads and have an active user community that provides feedback"
"3 FLOSS projects were selected for analysis, namely Gaim, eGroupWare and Compiere ERP."

all had sourceforge hosting

Data: "The primary data used for our study were interactions on the main developer communication forum, either a developer mailing list or web-based discussion forum."

Analysis: "For this project, we inductively content-analyzed developer email interactions to identify the task assignment mechanisms used in the process. We coded each instance of task assignment identified on three dimensions: who assigned the task, to whom, and how"
},
	abstract = {This paper provides empirical evidence about how free/libre open source software development teams self-organize their work. Following a case study methodology, we examined developer interaction data from three active and successful FLOSS projects using qualitative research methods, specifically inductive content analysis, to identify the task-assignment mechanisms used by the participants. We found that "self-assignment" was the most common mechanism across three FLOSS projects. This 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.},
	keywords = {case study, compiere, coordination, DESIGN, distributed teams, egroupware, email, email archives, forum, free/libre open source software development, gaim, INTERNET, mailing list, metadata, qualitative research methods, self-organizing teams, sourceforge, SYSTEMS, task assignment, WORK},
	attachments = {https://flosshub.org/sites/flosshub.org/files/task_assignment_final.pdf},
	author = {Kevin Crowston and Li, Qing and Kangning Wei and Eseryel, U. Yeliz and Howison, James}
}
@article {85,
	title = {Assessing the health of open source communities},
	journal = {Computer},
	volume = {39},
	number = {5},
	year = {2006},
	note = {Times Cited: 0},
	pages = {89-91},
	author = {Kevin Crowston and James Howison}
}
@article {90,
	title = {Core and periphery in Free/Libre and Open Source software team communications},
	journal = {Proceedings of the 39th Annual Hawaii International Conference on System Sciences-Volume 06},
	year = {2006},
	abstract = {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{\textquoteright}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.},
	keywords = {bug fixing, contributions, contributors, core, developers, social network analysis, sourceforge, team},
	author = {Kevin Crowston and Kangning Wei and Li, Qing and Howison, James}
}
@conference {flosswp406,
	title = {Emergent Decision-making Practices in Technology-Supported Self-Organizing Distributed Teams},
	booktitle = {Twenty Seventh International Conference on Information Systems},
	year = {2006},
	pages = {1{\textendash}12},
	abstract = {We seek to identify work practices that make technology-supported self-organizing distributed (or virtual) teams (TSSODT for short) effective in producing outputs satisfactory to their sponsors, meeting the needs of their members and continuing to function. A particularly important practice for team effectiveness is decision making: are the right decisions made at the right time to get the work done in a way that satisfies team sponsors, keeps contributors happy and engaged, and enables continued team success? In this research-in-progress paper, we report on an inductive qualitative analysis of 120 decision episodes taken by 2 Free/libre Open Source Software development teams (the completed paper will include 360 episodes from 6 teams). Our analysis revealed differences in the performance of the two teams that seems to be related to differences in overall project effectiveness.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/decision_making_practices.pdf},
	author = {Robert Heckman and Kevin Crowston and Li, Qing and Eileen Allen and Eseryel, U. Yeliz and James Howison}
}
@proceedings {107,
	title = {Emergent decision-making practices in technology-supported self-organizing distributed teams},
	year = {2006},
	address = {Milwaukee, WI, 10{\textendash}13 Dec},
	author = {Robert Heckman and Kevin Crowston and Li, Qing and Eileen Allen and Eseryel, U. Yeliz and James Howison and Wei, Kangning}
}
@article {109,
	title = {FLOSSmole: A Collaborative Repository for FLOSS Research Data and Analyses},
	journal = {International Journal of Information Technology and Web Engineering},
	volume = {1},
	number = {3},
	year = {2006},
	pages = {17-26},
	author = {James Howison and Conklin, Megan and Kevin Crowston}
}
@conference {691,
	title = {From Individual Contribution to Group Learning},
	booktitle = {OSS2006: Open Source Systems (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing},
	year = {2006},
	pages = {77 - 90},
	publisher = {Springer},
	organization = {Springer},
	abstract = {Open Source Software (OSS) groups experience many benefits and challenges with respect to the core group{\textquoteright}s effectiveness. In order to capitalize on the benefits and minimize the challenges, OSS groups must learn not only on the individual level, but also on the group level. OSS groups learn by integrating individual contributions into the group{\textquoteright}s product and processes.
This paper reports on the characteristics of the learning process in OSS groups. The study utilized an embedded single case study design that observed and analyzed group learning processes in the Apache Web server OSS project. The study used learning opportunity episodes (LOE) as the embedded unit of analysis and developed and utilized three content analytic schemes to describe the characteristics of the learning process and the factors affecting this process.
},
	keywords = {apache, case study},
	doi = {http://dx.doi.org/10.1007/0-387-34226-5_8},
	attachments = {https://flosshub.org/sites/flosshub.org/files/From\%20Individual\%20Contribution\%20to\%20Group\%20Learning.pdf},
	author = {Hala Annabi and Kevin Crowston and Robert Heckman}
}
@article {Crowston:2006a,
	title = {Hierarchy and centralization in Free and Open Source Software team communications},
	journal = {Knowledge, Technology \& Policy},
	volume = {18},
	number = {4},
	year = {2006},
	pages = {65{\textendash}85},
	abstract = {Free/Libre Open Source Software (FLOSS) development teams provide an interesting and convenient setting for studying distributed work. We begin by answering perhaps the most basic question: what is the social structure of these teams? Based on a social network analysis of interactions represented in 62,110 bug reports from 122 large and active projects, we find that some OSS teams are highly centralized, but contrary to expectation, others are not. Projects are mostly quite hierarchical on four measures of hierarchy, consistent with past research but contrary to the popular image of these projects. Furthermore, we find that the level of centralization is negatively correlated with project size, suggesting that larger projects become more modular. The paper makes a further methodological contribution by identifying appropriate analysis approaches for interaction data. We conclude by sketching directions for future research.},
	keywords = {apache, bug fixing, bug tracking, FLOSS, project success, savannah, social network analysis, sourceforge, team size, teams},
	attachments = {https://flosshub.org/sites/flosshub.org/files/CrowstonHierarchyAndCentralization.pdf},
	author = {Kevin Crowston and Howison, James}
}
@article {Crowston:2006,
	title = {Information systems success in Free and Open Source Software development: Theory and measures},
	journal = {Software Process{\textendash}Improvement and Practice},
	volume = {11},
	number = {2},
	year = {2006},
	note = {"we continue our examination of success measures using data from Sourceforge..."
"e chose the number of developers (assessed from the records of the project and from bug fixing logs), bug-fixing time, and popularity (assessed from the number of downloads and viewings of project Web pages, and inclusion in distributions). These measures were chosen because they span the reconsidered FLOSS development process discussed above, including inputs (number of developers), process (speed of bug fixing) and output (popularity)."},
	pages = {123{\textendash}148},
	abstract = {Information systems success is one of the most widely used dependent variables in information systems (IS) research, but research on Free/Libre and Open Source software (FLOSS) often fails to appropriately conceptualize this important concept. In this paper, we reconsider what success means within a FLOSS context. We first review existing models of IS success and success variables used in FLOSS research and assess them for their usefulness, practicality and fit to the FLOSS context. Then, drawing on a theoretical model of group effectiveness in the FLOSS development process, as well as an online discussion group with developers, we present additional concepts that are central to an appropriate understanding of success for FLOSS. In order to examine the practicality and validity of this conceptual scheme, the second half of our paper presents an empirical study that demonstrates its operationalization of the chosen measures and assesses their internal validity. We use data from SourceForge to measure the project{\textquoteright}s effectiveness in team building, the speed of the project at responding to bug reports and the project{\textquoteright}s popularity. We conclude by discussing the implications of this study for our proposed extension of IS success in the context of FLOSS development and highlight future directions for research.},
	keywords = {bug fixing, developers, downloads, FLOSS, flossmole, page views, popularity, project success, size, sourceforge, success, team size},
	doi = {10.1002/spip.259},
	attachments = {https://flosshub.org/sites/flosshub.org/files/CrowstonHowisonAnnabi2006.pdf},
	author = {Kevin Crowston and Howison, James and Hala Annabi}
}
@conference {713,
	title = {The role of mental models in FLOSS development work practices},
	booktitle = {OSS2006: Open Source Systems (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing},
	year = {2006},
	pages = {91 - 97},
	publisher = {Springer},
	organization = {Springer},
	abstract = {Shared understandings are important for software development as they guide to effective individual contributions to, and coordination of, the software development process. In this paper, we present the theoretical background and research design for a proposed study on shared mental models within Free/Libre Open Source Software (FLOSS) development teams. In particular, we plan to perform case studies on several projects and to use cognitive maps analysis to represent and compare the mental models of the involved members so as to gauge the degree of common knowledge and the development of a collective mind as well as to better understand the reasons that underlie team members actions and the way common mental models, if any, arise.
},
	doi = {http://dx.doi.org/10.1007/0-387-34226-5_9},
	attachments = {https://flosshub.org/sites/flosshub.org/files/The\%20role\%20of\%20mental\%20medels.pdf},
	author = {Kevin Crowston and Barbara Scozzi}
}
@article {111,
	title = {Social dynamics of free and open source team communications},
	journal = {Proceedings of the IFIP 2nd International Conference on Open Source Software, Lake Como, Italy},
	year = {2006},
	author = {James Howison and Inoue, K. and Kevin Crowston}
}
@conference {708,
	title = {Social dynamics of free and open source team communications},
	booktitle = {OSS2006: Open Source Systems (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing },
	volume = {203/2006},
	year = {2006},
	month = {06/2006},
	pages = {319 - 330},
	publisher = {Springer},
	organization = {Springer},
	abstract = {This paper furthers inquiry into the social structure of free and open source software (FLOSS) teams by undertaking social network analysis across time. Contrary to expectations, we confirmed earlier findings of a wide distribution of centralizations even when examining the networks over time. The paper also provides empirical evidence that while change at the center of FLOSS projects is relatively uncommon, participation across the project communities is highly skewed, with many participants appearing for only one period. Surprisingly, large project teams are not more likely to undergo change at their centers.
},
	keywords = {bug fixing, bug reports, bug tracker, bug tracking, bugs, communications, Dynamic social networks, FLOSS teams, Human Factors, social network analysis, software development, sourceforge},
	issn = {978-0-387-34225-2},
	doi = {http://dx.doi.org/10.1007/0-387-34226-5_32},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Social\%20dynamics\%20of\%20free\%20and\%20open\%20source\%20team.pdf},
	author = {Howison, James and Inoue, Keisuke and Kevin Crowston}
}
@unpublished {flosswp404,
	title = {A structurational perspective on leadership in technology-supported self-organizing small groups},
	year = {2006},
	month = {October},
	publisher = {Syracuse University School of Information Studies},
	type = {Working Paper},
	abstract = {In this conceptual paper, we present a structuration-based theory of leadership behaviours in virtual teams, that is to say, in self-organizing technology-supported small groups such as Free/Libre Open Source Software development teams. Such teams are often composed of members of relatively equal status or who are so disparate in background that formal organizational status seems irrelevant, reducing the usual leadership cues provided by organizational status and title. Building on behavioural leadership theory and structuration theory, we present a two-order theory of leadership. It describes four classes of first-order leadership behaviours (task coordination, substantive task contribution, group maintenance, and boundary spanning) and defines second-order leadership as behaviour that influences changes in the structure that guides group action. Specifically, we suggest that second-order leadership behaviours are those that build structures of signification in the form of interpretive schema, structures of domination in the form of role structures and structures of legitimation in the form of rules and norms. We argue that second-order leadership is enabled by first-order leadership, is therefore action embedded, and is grounded in processes that define the social identity of the group. We propose that effective teams will exhibit a paradoxical combination of shared, distributed first-order leadership complemented by strong, concentrated, and centralized second-order leadership. We conclude by suggesting future research that might be conducted to test and further elaborate our theory.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/CrowstonHeckmanMisiolek.pdf},
	author = {Kevin Crowston and Robert Heckman and Nora Misiolek}
}
@conference {78,
	title = {Collaboration Using OSSmole: A repository of FLOSS data and analyses},
	booktitle = {Symposium on Mining Software Repositories},
	year = {2005},
	month = {17 May},
	address = {St. Louis},
	author = {Conklin, Megan and James Howison and Kevin Crowston}
}
@proceedings {89,
	title = {Coordination of Free/Libre Open Source Software development},
	year = {2005},
	note = {"The data used for the study were interactions on the main developer communication venue, either a developer mailing list or online forum"
sourceforge
},
	address = {Las Vegas, NV, USA},
	abstract = {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 {\textquotedblleft}self-assignment{\textquotedblright} 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.},
	keywords = {case study, compiere, coordination, egroupware, email, email archives, FLOSS, gaim, mailing list},
	attachments = {https://flosshub.org/sites/flosshub.org/files/CrowstonWeiLiEseryelHowison.pdf},
	author = {Kevin Crowston and Kangning Wei and Li, Qing and Eseryel, U. Yeliz and Howison, James}
}
@conference {723,
	title = {OSSmole: A collaborative repository for FLOSS research data and analyses},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {54-60},
	abstract = {This paper introduces a collaborative project, {\textquotedblleft}OSSmole{\textquotedblright}, designed to gather, share and store comparable data and analyses of free and open source software development for academic research. The project draws on the ongoing collection and analysis efforts of many research groups, reducing duplication, and promoting compatibility both across sources of FLOSS data and across research groups and analyses. The paper outlines current difficulties with the current typical quantitative FLOSS research process and uses these to develop requirements and presents the design of the system.},
	url = {http://pascal.case.unibz.it/handle/2038/1422},
	author = {Howison, James and Conklin, Megan and Kevin Crowston}
}
@article {84,
	title = {The social structure of Free and Open Source Software development},
	journal = {First Monday},
	volume = {10},
	number = {2},
	year = {2005},
	author = {Kevin Crowston and James Howison}
}
@conference {716,
	title = {A structurational perspective on leadership in Free/Libre Open Source Software teams},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {9-15},
	abstract = {In this conceptual paper, we present a structuration- based theory of leadership behaviours in self-organizing distributed teams such as Free/Libre Open Source Software development teams. Such teams are often composed of members of relatively equal status or who are so disparate in background that formal organizational status seems irrelevant, reducing the usual leadership cues provided by organizational status and title. Building on a functional view of leadership and structuration theory, we suggest that leaders are individuals who develop team structures that then guide the actions of team members. Specifically, we examine structures of signification in the form of shared mental models, structures of domination in the form of role structures and structures of legitimation in form of rules and norms. The main contribution of our paper is the integration of various social theories to describe emergent leadership behaviours in distributed teams. We develop a set of prop...},
	url = {http://pascal.case.unibz.it/handle/2038/623},
	author = {Kevin Crowston and Robert Heckman and Hala Annabi and Chengetai Masango}
}
@conference {Crowston:2004,
	title = {Coordination practices for bug fixing within FLOSS development teams},
	booktitle = {1st International Workshop on Computer Supported Activity Coordination, 6th International Conference on Enterprise Information Systems},
	year = {2004},
	note = {"First, we chose projects for which data we need for our analysis are publicly available (not all projects allow public access to the bug tracking system). Second, we chose teams with more than 8 members...we tried to select more and less suc- cessful development teams. To this aim we used the definitions of success proposed by [9], who suggest that a project is successful if it is active, the resulting software is downloaded and used and the code matures"

"Kicq, Gaim and PhPmyAdmin were chosen" - effective
DynAPI was chosen as an example of a less effective project" 

"We collected data indicative of the success of each project, such as its level of activity, number of downloads and development status. We then collected data from the archives of the bug tracking system, the tool used to support the bug fixing process"},
	address = {Porto, Portugal},
	abstract = {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.},
	keywords = {activity, bug fixing, bug reports, bug tracker, coordination, downloads, dynapi, FLOSS, gaim, kicq, phpmyadmin, status},
	attachments = {https://flosshub.org/sites/flosshub.org/files/CrowstonScozzi04coordination.pdf},
	author = {Kevin Crowston and Barbara Scozzi}
}
@proceedings {flosswp181,
	title = {The perils and pitfalls of mining SourceForge},
	year = {2004},
	month = {05/2004},
	pages = {7-11},
	abstract = {SourceForge provides abundant accessible data from Open Source Software development projects, making it an attractive data source for software engineering research. However it is not without theoretical peril and practical pitfalls. In this paper, we outline practical lessons gained from our spidering, parsing and analysis of SourceForge data. SourceForge can be practically difficult: projects are defunct, data from earlier systems has been dumped in and crucial data is hosted outside SourceForge, dirtying the retrieved data. These practical issues play directly into analysis: decisions made in screening projects can reduce the range of variables, skewing data and biasing correlations. SourceForge is theoretically perilous: because it provides easily accessible data items for each project, tempting researchers to fit their theories to these limited data. Worse, few are plausible dependent variables. Studies are thus likely to test the same hypotheses even if they start from different theoretical bases. To avoid these problems, analyses of SourceForge projects should go beyond project level variables and carefully consider which variables are used for screening projects and which for testing hypotheses.},
	keywords = {Data Collection, sourceforge},
	attachments = {https://flosshub.org/sites/flosshub.org/files/howison04msr.pdf},
	author = {Howison, James and Kevin Crowston}
}
@unpublished {flosswp198,
	title = {The social structure of Free and Open Source software development},
	year = {2004},
	month = {November},
	publisher = {Syracuse University School of Information Studies},
	type = {Working Paper},
	abstract = {Metaphors, such as the Cathedral and Bazaar, used to describe the organization of FLOSS projects typically place them in sharp contrast to proprietary development by emphasizing FLOSS{\textquoteright}s distinctive social and communications structures. But what do we really know about the communication patterns of FLOSS projects? How generalizable are the projects that have been studied? Is there consistency across FLOSS projects? Questioning the assumption of distinctiveness is important because practitioner-advocates from within the FLOSS community rely on features of social structure to describe and account for some of the advantages of FLOSS production. To address this question, we examined 120 project teams from SourceForge, representing a wide range of FLOSS project types, for their communications centralization as revealed in the interactions in the bug tracking system. We found that FLOSS development teams vary widely in their communications centralization, from projects completely centered on one developer to projects that are highly decentralized and exhibit a distributed pattern of conversation between developers and active users.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/crowstonhowison.pdf},
	author = {Kevin Crowston and James Howison}
}
@conference {flosswp180,
	title = {Towards a Portfolio of FLOSS project Success Measures},
	booktitle = {Workshop on Open Source Software Engineering, International Conference on Software Engineering},
	year = {2004},
	month = {May},
	abstract = {Project success is one of the most widely used dependent variables in information systems research. However, conventional measures of project success are difficult to apply to Free/Libre Open Source Software projects. In this paper, we present an analysis of four measures of success applied to SourceForge projects: number of members of the extended development community, project activity, bug fixing time and number of downloads. We argue that these four measures provide different insights into the collaboration and control mechanisms of the projects.},
	keywords = {bug fixing, developers, downloads, project success, sourceforge, team, team size},
	attachments = {https://flosshub.org/sites/flosshub.org/files/crowston04towards.pdf},
	author = {Kevin Crowston and Hala Annabi and Howison, James and Chengetai Masango}
}
@conference {flosswp137,
	title = {Defining Open Source Software Project Success},
	booktitle = {Twenty-Fourth International Conference on Information Systems},
	year = {2003},
	month = {December},
	abstract = {Information systems success is one of the most widely used dependent variables in information systems research. In this paper, we identify a range of measures that can be used to assess the success of open source software (OSS) projects. We identify measures based on a review of the literature, a consideration of the OSS development process and an analysis of the opinions of OSS developers. For each measure, we provide examples of how they might be used in a study of OSS development.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/crowstonannabihowison.pdf},
	author = {Kevin Crowston and Hala Annabi and James Howison}
}
@conference {1155,
	title = {Exploring the Strengths and Limits of Open Source Software Engineering Processes: A Research Agenda},
	booktitle = {Proceedings of the 2nd ICSE Workshop on Open Source},
	year = {2002},
	abstract = {Many researchers have investigated the nature and characteristics of open source software (OSS) projects and their developer communities. In this position paper, after examining some success factors, we discuss potential limits on the replicability and portability of OSS engineering processes. Based on this analysis, we propose a research agenda to better understand the current nature of the processes and thus the strengths and the limitations.},
	keywords = {replicability, requirements, research, research agenda},
	attachments = {https://flosshub.org/sites/flosshub.org/files/CrowstonScozzi.pdf},
	author = {Kevin Crowston and Barbara Scozzi}
}
@article {flosswp59,
	title = {Open Source Software Projects as Virtual Organizations: Competency Rallying for Software Development},
	journal = {IEE Proceedings Software},
	volume = {149},
	number = {1},
	year = {2002},
	pages = {3{\textendash}17},
	abstract = {The contribution of this paper is the identification and testing of factors important for the success of Open Source Software (OSS) projects. We present an analysis of OSS communities as virtual organizations and apply Katzy and Crowston{\textquoteright}s (2000) competency rallying (CR) theory to the case of OSS development projects. CR theory suggests that project participants must develop necessary competencies, identify and understand market opportunities, marshal competencies to meet the opportunity and manage a short-term cooperative process. Using data collected from 7477 OSS projects hosted by the SourceForge system (http://sourceforge.net/), we formulate and test a set of specific hypotheses derived from CR theory.},
	keywords = {competencies, competency rallying, coordination, project success, sourceforge, virtual organizations},
	attachments = {https://flosshub.org/sites/flosshub.org/files/crowston.pdf},
	author = {Kevin Crowston and Barbara Scozzi}
}
