paperbot · PL 论文追踪

全部论文 待读 收藏

P2 Improving Collaboration Efficiency in Fork-Based Development

提升基于 Fork 的开发中的协作效率
ASE 2019 34th IEEE/ACM International Conference on Automated Software Engineering (ASE)2019匹配度 1/10 · 该论文研究 Fork 式开发中的协作效率与开发者工具,属于软件工程/开发者协作方向,与用户关注的 PL 与 AI 交叉、静态分析、浮点程序分析、贝叶斯程序分析及 LLM/Agent 改进分析等核心方向基本无关。引用 6 inbox
Shurui Zhou
crossref: 2026-09-12

AI 速览

一句话:针对 Fork 式开发中贡献可见性差与重复开发等问题,提出识别最佳实践与设计新干预两类互补策略。

Fork 式开发是一种轻量级协作机制,允许开发者在不显式协调的情况下参与项目。它易用且流行,但当开发者各自创建 fork 并独立开发时,其贡献往往难以被他人看到;随着 fork 数量增长,维护对各 fork 现状的整体认识变得非常困难,进而导致贡献丢失、重复开发、社区碎片化以及低效实践等问题。为应对这些问题,论文提出两类互补策略:一是识别已有的最佳实践,并为效率低下的项目提出基于证据的干预建议;二是设计新的干预措施,以提高使用 fork 式开发的社区意识,并帮助开发者检测重复开发,从而减少不必要的工作量。摘要未报告具体评估结果。

问题
Fork 式开发中,独立 fork 使贡献难以可见,fork 数量增长后难以形成整体认识,导致贡献丢失、重复开发和社区碎片化等协作低效问题。
方法
提出两类互补策略:识别最佳实践并面向低效项目提出基于证据的干预;设计新干预以提升社区意识并帮助检测重复开发。
评估
摘要未提供具体实验、数据集或量化结果,评估方式未在摘要中说明。
原文摘要(Abstract)

Fork-based development is a lightweight mechanism that allows developers to collaborate with or without explicit coordination. Although it is easy to use and popular, when developers each create their own fork and develop independently, their contributions are usually not easily visible to others. When the number of forks grows, it becomes very difficult to maintain an overview of what happens in individual forks, which would lead to additional problems and inefficient practices: lost contributions, redundant development, fragmented communities, and so on. Facing the problems mentioned above, we developed two complementary strategies: (1) Identifying existing best practices and suggesting evidence-based interventions for projects that are inefficient; (2) designing new interventions that could improve the awareness of a community using fork-based development, and help developers to detect redundant development to reduce unnecessary effort.

链接与引用

DOI 原文 ·

BibTeX
@inproceedings{paperbot5285,
  title = {Improving Collaboration Efficiency in Fork-Based Development},
  author = {Shurui Zhou},
  booktitle = {ASE},
  year = {2019},
  doi = {10.1109/ase.2019.00144}
}