Most issue tracking systems for open source software (OSS) development include features for community members to embed visual contents, such as images and videos, to enhance the discussion. Although playing an important role, there is little knowledge on the characteristics of the visual contents to support their use. To address this gap, we conducted an empirical study on the Jupyter Notebook project. We found that more than a quarter of the issues in the Jupyter Notebook project included visual contents. Additionally, issues that had visual contents in the comments but not in the issue posts tended to have a longer discussion and to involve a larger number of discussants. In our qualitative analysis, we identified eight types of visual contents in our sample, with about 60% including screenshots or mockups of the main product. We also found that visual contents served diverse purposes, touching both problem and solution spaces of the issues. Our effort serves as an important step towards a comprehensive understanding of the characteristics of visual contents in OSS issue discussions. Our results provided several design implications for issue tracking systems to better facilitate the use of visual contents.
翻译:开放源码软件(OSS)开发的大多数问题跟踪系统都包括社区成员将图像和视频等视觉内容嵌入图像和视频等视觉内容的特征,以加强讨论。虽然我们发挥了重要作用,但我们对视觉内容的特点知之甚少,难以支持其使用。为解决这一差距,我们对Jupyter Notesbook项目进行了一项经验性研究。我们发现,Jupyter Notesbook项目中四分之一以上的问题包括视觉内容。此外,在评论中含有视觉内容但不包含在议题文章中的问题往往有较长的讨论时间,而且涉及更多的讨论者。在我们的质量分析中,我们确定了我们抽样的八类视觉内容,其中约60%包括屏幕截图或主要产品的模拟。我们还发现视觉内容具有不同的目的,既触及问题又触及问题的解决空间。我们的努力是全面了解开放源码软件问题讨论中视觉内容特点的一个重要步骤。我们的成果为问题跟踪系统提供了若干设计影响,以便更好地利用视觉内容。