Work Practices and Challenges in Pull-Based Development¶
Gousios, G., Zaidman, A., Storey, M., & Deursen, A. v. (2015). Work Practices and Challenges in Pull-Based Development: The Integrator's Perspective. Proceedings of the 37th International Conference on Software Engineering (ICSE), 1, 358-368.
Cited by¶
1 citation across 1 artifact.
Each citation links to the sentence it supports in the citing article.
Primes¶
- Helpful-Inflow Displacement
- Open-source maintenance: drive-by pull requests and low-quality bug reports consuming maintainer attention, where the bottleneck is review and triage bandwidth, not commit capacity.
This sourceSurvey of OSS integrators finding review-and-prioritization bandwidth — not commit capacity — is the binding constraint, with maintainers struggling to triage incoming pull requests.
Supported in partVerified against the publisher's abstract
Its abstract reports that integrators struggle to prioritize contributions to be merged, which supports a review/triage load, but says nothing of drive-by pull requests, low-quality bug reports, or commit capacity.
“Our key findings are that integrators struggle to maintain the quality of their projects and have difficulties with prioritizing contributions that are to be merged.”
- Open-source maintenance: drive-by pull requests and low-quality bug reports consuming maintainer attention, where the bottleneck is review and triage bandwidth, not commit capacity.
Verification¶
Does it exist? Confirmed. This work's DOI resolves to a registered record, which fixes its identity. That is all it fixes.
Does it back the claim? Read against the text for 1 of 1 citation: 1 supported in part. Each verdict is shown under its citation below, with what in the work backs the sentence.
Support is checked per citation rather than per work — the same source can be cited soundly in one article and wrongly in another. Per-citation recording began recently, so a citation with no recorded check is a gap in the record rather than evidence it went unchecked.
See how references were verified.
Registry ID ref:64fb9a8df662 · see in the full table