Contemporary development projects benefit from code review as it improves the quality of a project. Large ecosystems of inter-dependent projects like OpenStack generate a large number of reviews, which poses new challenges for collaboration (improving patches, fixing defects). Review tools allow developers to link between patches, to indicate patch dependency, competing solutions, or provide broader context. We hypothesize that such patch linkage may also simulate cross-collaboration. With a case study of OpenStack, we take a first step to explore collaborations that occur after a patch linkage was posted between two patches (i.e., cross-patch collaboration). Our empirical results show that although patch linkage that requests collaboration is relatively less prevalent, the probability of collaboration is relatively higher. Interestingly, the results also show that collaborative contributions via patch linkage are non-trivial, i.e, contributions can affect the review outcome (such as voting) or even improve the patch (i.e., revising). This work opens up future directions to understand barriers and opportunities related to this new kind of collaboration, that assists with code review and development tasks in large ecosystems.
翻译:现代发展项目从代码审查中获益,因为它提高了项目的质量。像OpenStack这样的大型独立项目生态系统产生了大量审查,对合作提出了新的挑战(改进补丁、修补缺陷);审查工具允许开发者在补丁之间建立联系,表明补丁依赖性、相互竞争的解决办法或提供更广泛的背景;我们假设这种补丁联系还可能模拟交叉协作;通过对OpenStack的案例研究,我们迈出第一步,探讨在两个补丁(即交叉协作)之间打上补丁联系之后发生的协作。我们的经验结果表明,尽管要求协作的补丁联系相对不那么普遍,但协作的可能性相对较高。有趣的是,审查的结果还表明,通过补丁联系的协作贡献是非三角的,也就是说,捐款可以影响审查结果(例如投票),甚至改善补丁(即修订),这项工作开辟了未来方向,以了解与这种新型协作有关的障碍和机会,有助于大型生态系统的代码审查和开发任务。