How to break an API: cost negotiation and community values in three software ecosystems
Open accessThe DOI matches its Crossref record; 4 of the 4 references it cites were found in a registry or an index.
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.
Overview
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
Integrity signals
Registry
Cites
Statistics
Verification
Claims the paper makes
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
Self-check
Percentages, sums and reported differences re-computed from the paper’s own numbers.
The self-check needs the paper’s full text.
Citations
Cites
Tiwana, A., Konsynski, B., & Bush, A. A. (2010) · Information Systems Research · doi:10.1287/isre.1100.0323 · Cited by 1,514
Programs, life cycles, and laws of software evolution
Lehman, M. M. (1980) · Proceedings of the IEEE · doi:10.1109/proc.1980.11805 · Cited by 1,181
Social coding in GitHub: transparency and collaboration in an open software repository
Dabbish, L., Stuart, C., Tsay, J., & Herbsleb, J. (2012) · Proceedings of the ACM 2012 conference on Computer Supported Cooperative Work · doi:10.1145/2145204.2145396 · Cited by 999
Self-citationThe Emergence of Governance in an Open Source Community
O'Mahony, S., & Ferraro, F. (2007) · Academy of Management Journal · doi:10.5465/amj.2007.27169153 · Cited by 909
Cited by
An empirical comparison of dependency network evolution in seven software packaging ecosystems
Decan, A., Mens, T., & Grosjean, P. (2019) · Empirical Software Engineering · doi:10.1007/s10664-017-9589-y · Cited by 259
(2018) · doi:10.1145/3180155.3180209 · Cited by 98
Self-citationRaman, N., Cao, M., Tsvetkov, Y., Kästner, C., & Vasilescu, B. (2020) · Proceedings of the ACM/IEEE 42nd International Conference on Software Engineering: New Ideas and Emerging Results · doi:10.1145/3377816.3381732 · Cited by 70
“Cultural differences between communities [2] may also affect the degree of toxic interactions.”
BackgroundSelf-citationHow has forking changed in the last 20 years?: a study of hard forks on GitHub
Zhou, S., Vasilescu, B., & Kästner, C. (2020) · Proceedings of the ACM/IEEE 42nd International Conference on Software Engineering · doi:10.1145/3377811.3380412 · Cited by 36
“In line with prior observations on monitoring change feeds [5, 10, 33, 52], interviewees report that systematically monitoring changes from other repositories is onerous and that current tools like GitHub’s network graph are difficult to use and does not scale (P11, P16).”
BackgroundSelf-citationEnabling Data-Driven API Design with Community Usage Data: A Need-Finding Study
Zhang, T., Hartmann, B., Kim, M., & Glassman, E. L. (2020) · Proceedings of the 2020 CHI Conference on Human Factors in Computing Systems · doi:10.1145/3313831.3376382 · Cited by 25
“[4] studied how community-specific values, policies, and tools may influence how developers respond to API changes that may break client code.”
Background
Metadata
- Authors
- Bogart, C., Kästner, C., Herbsleb, J., & Thung, F.
- Venue
- Proceedings of the 2016 24th ACM SIGSOFT International Symposium on Foundations of Software Engineering
- Publisher
- ACM
- Published
- 2016-11
- Pages
- 109-120
- OpenAlex
- W2548749170
- Cited by
- 207
- References
- 4
- FWCI
- 17.09
- Type
- conference paper
- Language
- en
- Open access
- bronze
About these checks
Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.
Statistics and arithmetic are recomputed, not judged.
Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.
What counts as a claim ›How we measure confidence ›How we check this ›
Are you an author, or do you see a problem with this page? Request a review
Data sources
Bibliographic data: Semantic Scholar, OpenAlex, Crossref.
Contains information from the Semantic Scholar Academic Graph Datasets, made available under the ODC Attribution License (ODC-BY 1.0).
Semantic Scholar’s data is described in: Kinney, R., et al. (2023). The Semantic Scholar Open Data Platform. arXiv:2301.10140.