Year: 2016
Type: conference-paper
Abstract: Change introduces conflict into software ecosystems: breaking changes may ripple through the ecosystem and trigger rework for users of a package, but often developers can invest additional effort or accept opportunity costs to alleviate or delay downstream costs. We performed a multiple case study of three software ecosystems with different tooling and philosophies toward change, Eclipse, R/CRAN, and Node.js/npm, to understand how developers make decisions about change and change-related costs and what practices, tooling, and policies are used. We found that all three ecosystems differ substantially in their practices and expectations toward change and that those differences can be explained largely by different community values in each ecosystem. Our results illustrate that there is a large design space in how to build an ecosystem, its policies and its supporting infrastructure; and there is value in making community values and accepted tradeoffs explicit and transparent in order to resolve conflicts and negotiate change-related costs.
Institutions: Carnegie Mellon University, Singapore Management University
Language: English
Subfield: Information Systems
Field: Computer Science
Domain: Physical Sciences
Open Access status: bronze
Awards: HCC: Large: Collaborative Research: Large-Scale Human-Centered Coordination Systems to Support Interdependent Tasks in Context, VOSS: Designing Transparent Work Environments, BIGDATA: Collaborative Research: F: Study of a Cyber-Enabled Social Computing Framework for Improving Practice in Online Computing Communities, CAREER:VARIATIONAL EXECUTION, SHF: Small: Reverse Engineering Variability Implementations, HCC: Medium: Personalized information access for online deliberation systems, Socio-technical ecosystems for scientific software development
OpenAlex ID: W2548749170
