Research Question: What mechanisms sustain long-term voluntary developer participation in OSS communities?
Abstract: Prior research into open source software (OSS) developer participation has emphasized individuals’ motivations for joining these volunteer communities, but it has failed to explain why people stay or leave in the long run. Building upon Lave and Wenger’s theory of legitimate peripheral participation (LPP), this paper offers a longitudinal investigation of one OSS community in which sustained participation is hypothesized to be associated with the coevolution of two major elements of LPP theory: “situated learning” (the process of acting knowledgeably and purposefully in the world) and “identity construction” (the process of being identified within the community). To test this hypothesis, data were collected from multiple sources, including online public project documents, electronic mail messages, tracker messages, and log files. Results from qualitative analyses revealed that initial conditions to participate did not effectively predict long-term participation, but that situated learning and identity construction behaviors were positively linked to sustained participation. Furthermore, this study reveals that sustained participants distinguished themselves by consistently engaging in situated learning that both made conceptual (advising others) and practical contributions (improving the code). Implications and future research are discussed.
Findings: Sustained participation was not associated with initial conditions (i.e., access and motivation), though these factors were a necessary condition. Rather, a three-way interaction occurred between (1) Situated Learning (“thinking”/advising others, “doing”/revising code); (2) Identity Construction (identity-regulation, and identity-work); and (3) Sustained Participation. Consistent with Lave & Wenger’s LPP cycle.
Implications: (1) A small number of committed, “core” developers is essential to project success. (2) A large pool of potential candidates can be helpful in accessing these core developers. The large pool was assembled through (a) open community access, and (b) keeping software objectives relevant & useful to a large audience. (3) Valued contributors should be recognized, e.g., with access privileges (to “prime” the LPP cycle). (4) Participants should be directly encouraged to make active code contributions, rather than engage in passive “lurking”.
Citation: Fang, Y. & Neufeld, D.J. (2009). Understanding sustained participation in open source software projects. Journal of Management Information Systems 25(4), pp. 9-50. [link]