一句话：研究 OSS 项目在采纳 DevOps 工具前团队如何讨论与决策，以及哪些团队特征影响采纳。
该文关注开源软件（OSS）项目中 DevOps 工具的采纳过程。现实中配置管理、云端持续集成与自动化部署工具众多，且同一任务常有多种选择，项目会定期采纳或放弃工具。已有工作表明，部分工具采纳之前存在讨论，且采纳可能给项目带来收益。但关键问题仍未解决：团队如何决定采纳某个工具？采纳前讨论了哪些内容、持续多久？哪些团队特征决定了采纳？论文围绕这些问题展开，旨在刻画团队讨论与动态在 DevOps 工具采纳中的作用。摘要未给出具体方法、数据与结果，需参见正文。
In Open Source Software (OSS) projects, pre-built tools dominate DevOps-oriented pipelines. In practice, a multitude of configuration management, cloud-based continuous integration, and automated deployment tools exist, and often more than one for each task. Tools are adopted (and given up) by OSS projects regularly. Prior work has shown that some tool adoptions are preceded by discussions, and that tool adoptions can result in benefits to the project. But important questions remain: how do teams decide to adopt a tool? What is discussed before the adoption and for how long? And, what team characteristics are determinant of the adoption?
DOI 原文 ·
@inproceedings{paperbot5930,
title = {Team discussions and dynamics during DevOps tool adoptions in OSS projects},
author = {Likang Yin and Vladimir Filkov},
booktitle = {ASE},
year = {2020},
doi = {10.1145/3324884.3416640}
}