What to share, when, and where: balancing the objectives and complexities of open source software contributions
- PDF / 978,199 Bytes
- 42 Pages / 439.642 x 666.49 pts Page_size
- 29 Downloads / 155 Views
What to share, when, and where: balancing the objectives and complexities of open source software contributions ¨ Regnell1 Johan Lin˚aker1 · Bjorn Published online: 12 August 2020 © The Author(s) 2020
Abstract Context: Software-intensive organizations’ rationale for sharing Open Source Software (OSS) may be driven by both idealistic, strategic and commercial objectives, and include both monetary as well as non-monetary benefits. To gain the potential benefits, an organization may need to consider what they share and how, while taking into account risks, costs and other complexities. Objective: This study aims to empirically investigate objectives and complexities organizations need to consider and balance between when deciding on what software to share as OSS, when to share it, and whether to create a new or contribute to an existing community. Method: A multiple-case study of three case organizations was conducted in two research cycles, with data gathered from interviews with 20 practitioners from these organizations. The data was analyzed qualitatively in an inductive and iterative coding process. Results: 12 contribution objectives and 15 contribution complexities were found. Objectives include opportunities for improving reputation, managing suppliers, managing partners and competitors, and exploiting externally available knowledge and resources. Complexities include risk of loosing control, risk of giving away competitive advantage, risk of creating negative exposure, costs of contributing, and the possibility and need to contribute to an existing or new community. Conclusions: Cross-case analysis and interview validation show that the identified objectives and complexities offer organizations a possibility to reflect on and adapt their contribution strategies based on their specific contexts and business goals. Keywords Open source software · Software product management · Requirements engineering · Contribution strategy · Community strategy Communicated by: Audris Mockus Johan Lin˚aker
[email protected]
Extended author information available on the last page of the article.
3800
Empirical Software Engineering (2020) 25:3799–3840
1 Introduction Sharing, or contributing, software artifacts (e.g., features, projects, and frameworks) as Open Source Software (OSS) is a common practice among software-intensive organizations today (Munir et al. 2016). By “opening up” (Chesbrough et al. 2014), an organization can exploit the external workforce residing in the OSS communities that develops and maintains the OSS. Improved product innovation, accelerated development, lower maintenance cost, as well as improved branding and reputation, are some of the potential benefits that may motivate (Munir et al. 2016, 2018a; Stuermer et al. 2009; Henkel 2006; Lindman et al. 2009). The motive may also be driven by pure idealism and being a good OSS citizen (Jansen et al. 2012). For some organizations, OSS may have a more direct connection to the business model or strategy, e.g., as a basis for complementary products and
Data Loading...
