arXivDaily arXiv每日学术速递 周一至周五更新
arXiv 2204.00155cs.SEcs.HC
收藏

有多热?了解GitHub锁定问题

How heated is it? Understanding GitHub locked issues

Isabella Ferreira, Bram Adams, Jinghui Cheng

摘要:

尽管开源软件的问题是为了讨论和解决技术问题而创建的,但对话可能会变得激烈,讨论者会因为各种原因而变得愤怒和/或激动,例如糟糕的建议或违反社区惯例。为了防止和缓解讨论变得激烈,GitHub等工具引入了锁定违反行为准则或其他社区准则的问题讨论的功能。尽管有一些关于锁定问题的早期研究,但对社区如何使用此功能以及依赖锁定问题数据集作为激烈讨论的甲骨文的研究人员的有效性的潜在威胁缺乏了解。为了解决这一差距,我们(i)定量分析了79个GitHub项目,这些项目至少有一个问题被锁定为过热,(ii)定性分析了79个项目中所有被锁定为过热的问题,总共205个问题,包括5,511条评论。我们发现,项目在锁定问题时有不同的行为:54个项目锁定了不到10%的已关闭问题,14个项目锁定了90%以上的已关闭问题。此外,锁定的问题往往与非锁定的问题具有类似数量的评论,参与者和表情符号反应。在205个被锁定为“过于激烈”的问题中,我们发现三分之一的评论不包含任何不文明的话语,只有8.82%的评论是不文明的。最后,我们发现维护人员提供的锁定理由并不总是与用于锁定问题的标签相匹配。根据我们的研究结果,我们确定了在使用GitHub锁定的问题数据时需要避免的三个陷阱,并为研究人员和从业者提供了建议。

英文摘要:

Although issues of open source software are created to discuss and solve technical problems, conversations can become heated, with discussants getting angry and/or agitated for a variety of reasons, such as poor suggestions or violation of community conventions. To prevent and mitigate discussions from getting heated, tools like GitHub have introduced the ability to lock issue discussions that violate the code of conduct or other community guidelines. Despite some early research on locked issues, there is a lack of understanding of how communities use this feature and of potential threats to validity for researchers relying on a dataset of locked issues as an oracle for heated discussions. To address this gap, we (i) quantitatively analyzed 79 GitHub projects that have at least one issue locked as too heated, and (ii) qualitatively analyzed all issues locked as too heated of the 79 projects, a total of 205 issues comprising 5,511 comments. We found that projects have different behaviors when locking issues: while 54 locked less than 10% of their closed issues, 14 projects locked more than 90% of their closed issues. Additionally, locked issues tend to have a similar number of comments, participants, and emoji reactions to non-locked issues. For the 205 issues locked as too heated, we found that one-third do not contain any uncivil discourse, and only 8.82% of the analyzed comments are actually uncivil. Finally, we found that the locking justifications provided by maintainers do not always match the label used to lock the issue. Based on our results, we identified three pitfalls to avoid when using the GitHub locked issues data and we provide recommendations for researchers and practitioners.

机构、总结、中文摘要均由AI分析而来,可能存在错误,请以论文正文为准。

↑