All software exhibits operational problems as well as opportunities for redesign. How software projects handle problems and ongoing redesign efforts – Software Problem Management or "SWPM" – is not well understood, especially in open distributed communities such as Free/Open Source Software (F/OSS) projects. Little is known about the factors that influence performance or outcomes (e.g. time, cost, quality, sustainability) of software development communities involved in SWPM. Publicly accessible repositories of SWPM data, such as bug report repositories maintained by F/OSS development communities, provide vast stores of data about distributed SWPM practices and knowledge. Individual bug reports (BRs) within these repositories are texts that provide detailed records of community activities including responses to, and analyses of, problems. By examining these records we can develop detailed pictures of how many collaborative, distributed, computermediated SWPM processes unfold, creating finer-grained accounts of how coordination actually works, and extending current theories of computer-supported collaboration. This paper reports on several ways in which activity and information interact in SWPM. We have identified a number of "basic social processes" (BSPs) that shape how participants organize and use information, build and maintain community knowledge, and coordinate community activities at a very large scale (e.g., several gigabytes of online information, tens of thousands of reporters, over 50,000 simultaneously open problems). We focus on how one BSP, negotiation, shapes coordination activities in SWPM. Using detailed qualitative methods, we report on the varieties and frequencies of negotiation practices, and analyze how different types of negotiation in different situations influence what knowledge is available to participants, how collective activity gets focused in specific directions, and how the organization of information shapes activity. Overall, this provides a more detailed understanding of key collaborative distributed coordination mechanisms than has been available in the CSCW literature to date.
[1]
Roberto Venosa,et al.
Negotiations: varieties, contexts, processes and social order
,
1992
.
[2]
Ronald R. Powell,et al.
Basic Research Methods for Librarians
,
1985
.
[3]
L. Gasser,et al.
Distributed Collective Practices and Free / Open-Source Software Problem Management : Perspectives and Methods
,
2003
.
[4]
K. Weick.
FROM SENSEMAKING IN ORGANIZATIONS
,
2021,
The New Economic Sociology.
[5]
R. Weber.
Basic Content Analysis
,
1986
.
[6]
Kevin Crowston,et al.
A Coordination Theory Approach to Organizational Process Design
,
1997
.
[7]
Peter H. Carstensen,et al.
Let's Talk About Bugs!
,
1995,
Scand. J. Inf. Syst..
[8]
Elihu M. Gerson,et al.
Analyzing due process in the workplace
,
1986,
COCS '86.
[9]
Nancy G. Leveson,et al.
An investigation of the Therac-25 accidents
,
1993,
Computer.
[10]
Les Gasser,et al.
Scalable Automatic Extraction of Process Models for Understanding F/OSS Bug Repair
,
2003
.
[11]
Andreas Larsson,et al.
Making sense of collaboration: the challenge of thinking together in global design teams
,
2003,
GROUP.
[12]
Ina Wagner,et al.
Time-management: a case for CSCW
,
1992,
CSCW '92.
[13]
Pamela Jordan.
Basics of qualitative research: Grounded theory procedures and techniques
,
1994
.
[14]
Eric S. Raymond,et al.
The cathedral and the bazaar - musings on Linux and Open Source by an accidental revolutionary
,
2001
.
[15]
A. Strauss,et al.
Negotiations: Varieties, Contexts, Processes, and Social Order.
,
1979
.
[16]
Les Gasser,et al.
Bug Report Networks: Varieties, Strategies, and Impacts in a F/OSS Development Community
,
2004,
MSR.
[17]
Carla Simone,et al.
Coordination mechanisms: Towards a conceptual foundation of CSCW systems design
,
1996,
Computer Supported Cooperative Work (CSCW).
[18]
Susan Leigh Star,et al.
Institutional Ecology, `Translations' and Boundary Objects: Amateurs and Professionals in Berkeley's Museum of Vertebrate Zoology, 1907-39
,
1989
.