Synchronous development in open-source projects: A higher-level perspective

Abstract

Mailing lists are a major communication channel for supporting developer coordination in open-source software projects. In a recent study, researchers explored temporal relationships (e.g., synchronization) between developer activities on source code and on the mailing list, relying on simple heuristics of developer collaboration (e.g., co-editing files) and developer communication (e.g., sending e-mails to the mailing list). We propose two methods for studying synchronization between collaboration and communication activities from a higher-level perspective, which captures the complex activities and views of developers more precisely than the rather technical perspective of previous work. On the one hand, we explore developer collaboration at the level of features (not files), which are higher-level concepts of the domain and not mere technical artifacts. On the other hand, we lift the view of developer communication from a message-based model, which treats each e-mail individually, to a conversation-based model, which is semantically richer due to grouping e-mails that represent conceptually related discussions. By means of an empirical study, we investigate whether the different abstraction levels affect the observed relationship between commit activity and e-mail communication using state-of-the-art time-series analysis. For this purpose, we analyze a combined history of 40 years of data for three highly active and widely deployed open-source projects: QEMU, BusyBox, and OpenSSL. Overall, we found evidence that a higher-level view on the coordination of developers leads to identifying a stronger statistical dependence between the technical activities of developers than a less abstract and rather technical view.

OSCMS: A Decentralized Open-Source Coordination Management System Using a Novel Triple-Blockchain Architecture

“…Liao et al [32] explored OSS management from problems' feedback, but the perspective was single and did not consider the historical tracing of problems and related modifications. The authors of [33] studied the collaboration and communication of OS developers from a higher-level perspective, which can improve efficiency, but did not consider trust. Zhang et al [34] summarized the common structure and evolutionary characteristics of OS community developer collaboration models and provided relevant management suggestions based on sociology.…”

Social-technical network effects in open source software communities: understanding the impacts of dependency networks on project success

“…Therefore, this method is often used in analysis such as case studies (Lindberg et al, 2016). The second method is an alternative way to represent technical dependencies using code MR, which has been used in some empirical studies (Bock et al, 2022;Costa et al, 2021). That is, if two modules are modified by the same modification request, there will be technical dependencies between these two modules.…”

“…, 2016). The second method is an alternative way to represent technical dependencies using code MR, which has been used in some empirical studies (Bock et al. , 2022; Costa et al.…”