@article {9999,
	title = {Participation in Community-Based Free/Libre Open Source Software Development Tasks: The Impact of Task Characteristics},
	journal = {Internet Research},
	volume = {31},
	year = {2021},
	pages = {1177-1202},
	abstract = {<p>Prior research on participation in FLOSS development has focused mainly on factors at the individual and/or project levels. In this research, we focus on task characteristics and explore their impacts on participation in FLOSS development tasks. Analyzing tasks from five projects in two categories, we find differences in participation related to different task triggers and task topics. Further, our results suggest the mediating role of number of participants in the relationship between task characteristics and the number of messages and the moderating role of project type in the relationships between task characteristics and the number of participants.</p>},
	doi = {10.1108/INTR-03-2020-0112},
	attachments = {https://crowston.syr.edu./sites/crowston.syr.edu/files/IR\%20to\%20share.pdf},
	author = {Kangning Wei and Eseryel, U. Yeliz and Kevin Crowston}
}
@article {9999,
	title = {Decision-Making Processes in Community-based Free/Libre Open Source Software Development Teams with Internal Governance: An Extension to Decision-Making Theory},
	journal = {Communications of the Association for Information Systems},
	year = {2020},
	abstract = {<p>FLOSS teams are an extreme example of distributed teams, prominent in software development. At the core of distributed team success is team decision-making and execution. The lack formal organizational structures to guide practices and the reliance on asynchronous communication might be expected to make decision making problematic. While there is a paucity of research in how organizations make IS development decisions, the research in FLOSS decision making models is limited. Decision-making literature in FLOSS teams is limited to the investigation of the distribution of decision-making power. Therefore, it is not clear which decision-making theories fit FLOSS context best, or whether novel decision-making models are required. Despite these challenges many FLOSS teams are effective. We adopted a process-based perspective to analyze decision-making in five community-based FLOSS teams. We identified five different decision-making processes, indicating FLOSS teams use multiple processes when making decisions. Decision-making behaviors were stable across projects despite different type of knowledge required. We help fill in the literature gap due to the lack of investigations the extent to which FLOSS decision mechanisms can be explained using classical decision-making theories. Practically, community and company leaders should use these decision processes to infrastructure that fits best with the FLOSS decision-making processes.</p>},
	doi = {10.17705/1CAIS.04620},
	attachments = {https://crowston.syr.edu./sites/crowston.syr.edu/files/CAIS\%20Journal\%202nd\%20Round\%20Resubmission.pdf},
	author = {Eseryel, U. Yeliz and Kangning Wei and Kevin Crowston}
}
@article {9999,
	title = {Roles and politeness behavior in community-based Free/Libre Open Source Software development},
	journal = {Information and Management},
	volume = {54},
	year = {2017},
	pages = {573-582},
	abstract = {Community-based Free/Libre Open Source Software (FLOSS) development relies on contributions from both core and peripheral members. Prior research on core-periphery has focused on software coding-related behaviors. We study how core-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-periphery structure, Open source software development, Politeness behavior},
	doi = {10.1016/j.im.2016.11.006},
	attachments = {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 Heckman, Robert}
}
@article {9998,
	title = {Group maintenance in technology-supported distributed teams},
	journal = {Information \& Management},
	volume = {51},
	year = {2014},
	month = {4/2014},
	pages = {297-309},
	abstract = {In this paper we investigate group maintenance behavior in community-based Free/Libre Open Source Software (FLOSS) development teams. Adopting a sociolinguistic perspective, we conceptualize group maintenance behavior as interpersonal communication tactics{\textemdash}specifically, social presence and politeness tactics{\textemdash}that help maintain relationships among group members. Developer email messages were collected from two FLOSS projects with different development status and content-analyzed to identify frequently-used group maintenance tactics. We then compared the two projects on the group maintenance tactics used, finding differences that reflect changes in the project work practices. Our work contributes theoretically to FLOSS research and has practical implications for FLOSS practitioners. },
	doi = {10.1016/j.im.2014.02.001},
	attachments = {https://crowston.syr.edu./sites/crowston.syr.edu/files/Group_maintenance\%20paper_part\%20I_20140122_final.pdf},
	author = {Kangning Wei and Kevin Crowston and Li, Na and Heckman, Robert}
}
@article {Crowston:2009,
	title = {Free/Libre Open Source Software Development: What we know and what we do not know},
	journal = {ACM Computing Surveys},
	volume = {44},
	year = {2012},
	month = {02/2012},
	edition = {2},
	abstract = {We review the empirical research on Free/Libre and Open Source Software (FLOSS) development and assess the state of the literature. We develop a framework for organizing the literature based on the input-mediator-output- input (IMOI) model from the small groups literature. We present a quantitative summary of articles selected for the review and 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 topics for future research, as well as identifying methodological and theoretical issues for future inquiry in this area, including issues relating to sampling and the need for more longitudinal studies.},
	doi = {10.1145/2089125.2089127},
	attachments = {https://crowston.syr.edu./sites/crowston.syr.edu/files/CrowstonFLOSSReviewPaperPreprint.pdf , https://crowston.syr.edu./sites/crowston.syr.edu/files/Appendix\%201\%20Journal\%20and\%20Conference\%20Names.pdf , https://crowston.syr.edu./sites/crowston.syr.edu/files/Appendix\%202\%20Coding\%20Scheme.pdf , https://crowston.syr.edu./sites/crowston.syr.edu/files/Appendix\%203\%20Studies\%20included\%20in\%20the\%20review.pdf},
	author = {Kevin Crowston and Kangning Wei and James Howison and Wiggins, Andrea}
}
@conference {Wei:2010,
	title = {The impact of national culture on knowledge sharing in global virtual collaboration},
	booktitle = {Proceedings of International Conference on Information Systems (ICIS)},
	year = {2010},
	month = {12/2010},
	address = {St. Louis, MO, USA},
	keywords = {Knowledge Sharing, National Culture, Virtuality},
	author = {Kangning Wei and Kevin Crowston}
}
@article {2007,
	title = {Investigating the Dynamics of FLOSS Development Teams (Poster)},
	year = {2007},
	note = {SD 2007 poster - Full Adobe PDF
2007 HSD PI{\textquoteright}s conference poster reporting on the grant project work to date in a full Adobe PDF file.

HSD 2007 poster - Small PDF
HSD 2007 conference grant progress reporting poster in a smaller PDF file.
},
	attachments = {https://crowston.syr.edu./sites/crowston.syr.edu/files/HSDposter_8.ai_.pdf , https://crowston.syr.edu./sites/crowston.syr.edu/files/HSDposter_8.pdf},
	author = {Li, Na and Li, Qing and Kangning Wei and Heckman, Robert and Eseryel, U. Yeliz and Liddy, Elizabeth D. and James Howison and Kevin Crowston and Allen, Eileen E. and Scialdone, Michael J. and Inoue, Keisuke and Harwell, Sarah and Rowe, Steven and McCracken, Nancy and Wiggins, Andrea}
}
@article {Crowston:2007b,
	title = {Self-organization of teams in free/libre open source software development},
	journal = {Information and Software Technology Journal: Special issue on Understanding the Social Side of Software Engineering, Qualitative Software Engineering Research},
	volume = {49},
	year = {2007},
	pages = {564{\textendash}575},
	abstract = {This paper provides empirical evidence about how free/libre open source software development teams self-organize their work, specifically, how tasks are assigned to project team members. 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 {\textquoteleft}self-assignment{\textquoteright} 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.},
	doi = {10.1016/j.infsof.2007.02.004},
	attachments = {https://crowston.syr.edu./sites/crowston.syr.edu/files/060918.pdf},
	author = {Kevin Crowston and Kangning Wei and Li, Qing and Eseryel, U. Yeliz and James Howison}
}
@proceedings {Crowston:2006b,
	title = {Core and periphery in Free/Libre and Open Source software team communications},
	year = {2006},
	address = {Kaua{\textquoteright}i, Hawai{\textquoteright}i, January},
	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, {\textquotedblleft}how does one empirically distinguish the core?{\textquotedblright} 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 = {FLOSS},
	attachments = {https://crowston.syr.edu./sites/crowston.syr.edu/files/CoreAndPeripheryInFreeLibre.pdf},
	author = {Kevin Crowston and Kangning Wei and Li, Qing and James Howison}
}
@proceedings {Heckman:2006b,
	title = {Emergent decision-making practices in technology-supported self-organizing distributed teams},
	year = {2006},
	address = {Milwaukee, WI, 10{\textendash}13 Dec},
	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. Our analysis revealed differences in decision-making practices that seem to be related to differences in overall team effectiveness.},
	keywords = {Decision-Making, FLOSS},
	attachments = {https://crowston.syr.edu./sites/crowston.syr.edu/files/Emergent\%20Decision\%20Making\%20Practices\%20In\%20Technology\%20Supported\%20Self\%20O.pdf},
	author = {Heckman, Robert and Kevin Crowston and Li, Qing and Allen, Eileen E. and Eseryel, U. Yeliz and James Howison and Kangning Wei}
}
@article {2006,
	title = {Investigating the Dynamics of FLOSS Development Teams (Poster)},
	year = {2006},
	note = {Poster describing the current state of the project for the HSD Principal Investigators{\textquoteright} conference, 14-15 September 2006, Washington DC.},
	attachments = {https://crowston.syr.edu./sites/crowston.syr.edu/files/hsd2006poster.pdf},
	author = {Li, Qing and Kangning Wei and Heckman, Robert and Eseryel, U. Yeliz and Liddy, Elizabeth D. and James Howison and Kevin Crowston and Allen, Eileen E. and Inoue, Keisuke and Harwell, Sarah and Rowe, Steven and McCracken, Nancy}
}
@proceedings {Crowston:2005,
	title = {Coordination of Free/Libre Open Source Software development},
	year = {2005},
	address = {Las Vegas, NV, USA, December},
	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 = {Coordination, FLOSS},
	attachments = {https://crowston.syr.edu./sites/crowston.syr.edu/files/Coordination\%20of\%20Free\%20Libre\%20Open\%20Source\%20Software\%20Development.pdf , https://crowston.syr.edu./sites/crowston.syr.edu/files/CoordinationFreeLibreOSSDevSlides.pdf},
	author = {Kevin Crowston and Kangning Wei and Li, Qing and Eseryel, U. Yeliz and James Howison}
}
