Tracing distributed collaborative development in apache software foundation projects

Gharehyazie, Mohammad; Filkov, Vladimir

doi:10.1007/s10664-016-9463-3

Cited by 7 publications

(4 citation statements)

References 61 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Still, we point out that this finding about the number of members involved in recurring collaborations is in line with previous work that also found pairwise collaborations to be extremely more prevalent in the FAWM music community [19,52]. Also, similar findings have been reported in [20] and [57] concerning the size of putative sub-teams of developers in the Apache OSS ecosystem. As for the second point, we speculate that the preference for working with fellow authors sharing the same level of expertise is because recurring collaborations are not a means for experienced musicians to teach newbies but rather a way to help each other and keep growing together.…”

Section: Recurring Collaborationssupporting

confidence: 92%

“…However, our focus here is not on investigating established teams but rather on groups of individuals who spontaneously get together and collaborate recurrently, acting de facto as a team. Xuan and Filkov [57] and Gharehyazie and Filkov [20] investigated synchronous group codevelopment within the Apache software ecosystem. They identified the presence of putative collaborative groups (CoG) of developers who act like teams since they tend to work together in code proximity (i.e., modify the same source files) and time proximity (i.e., around the same time).…”

Section: Recurring Collaborationsmentioning

confidence: 99%

“…Recurring 'collabs' in online communities for music co-creation are mentioned in the work on FAWM by Dow and Settles [15], where they report the case of three members who formed a virtual band to compose 42 songs about the U.S. presidents and adopted a "parallel, distributed-labor model of collaboration reminiscent of open-source software […] projects." Previous research on OSS development has proven the existence of co-development groups, i.e., latent socio-technical structures [4] formed by two or more developers (also referred to as implicit teams [38] and putative groups [20]) who tend to communicate often and work together on the same artifacts. There is also evidence that the members of these co-development groups are very productive and more likely to remain active within communities for longer [56].…”

Section: Introductionmentioning

confidence: 99%

See 2 more Smart Citations

An In-Depth Analysis of Occasional and Recurring Collaborations in Online Music Co-creation

Calefato

Iaffaldano

Trisolini

et al. 2021

Trans. Soc. Comput.

View full text Add to dashboard Cite

The success of online creative communities depends on the will of participants to create and derive content in a collaborative environment. Despite their growing popularity, the factors that lead to remixing existing content in online creative communities are not entirely understood. In this article, we focus on overdubbing , a dyadic collaboration in which one author mixes one new track with an audio recording previously uploaded by another. We study musicians who collaborate regularly, frequently overdubbing each other's songs. Building on frequent pattern–mining techniques, we develop an approach to seek instances of such recurring collaborations in the Songtree community. We identify 43 instances involving two or three members with a similar reputation in the community. Our findings highlight common and different remix factors in occasional and recurring collaborations. Specifically, fresh and less mature songs are generally overdubbed more. Exchanging messages and invitations to collaborate are significant factors only for songs generated through recurring collaborations, whereas author reputation (ranking) and applying metadata tags to songs have a positive effect only in occasional collaborations.

show abstract

Section: Recurring Collaborationssupporting

confidence: 92%

Section: Recurring Collaborationsmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

An In-Depth Analysis of Occasional and Recurring Collaborations in Online Music Co-creation

Calefato

Iaffaldano

Trisolini

et al. 2021

Trans. Soc. Comput.

View full text Add to dashboard Cite

show abstract

“…The authors of the original study enhanced their work by identifying patterns on the time series of working activity in terms of source-code commits and communication activity in terms of replying to e-mails on the mailing list for developer pairs, which indicate that collaboration on source-code artifacts and coordinating events on the mailing list are temporally related (Xuan et al 2016). Gharehyazie and Filkov (2017) extended the original study by not investigating pairs of developers but groups of developers working on the same source-code artifacts temporally close-by. In their work, they analyzed whether the size of such groups is purely random and how often developers work in groups rather than working alone.…”

Section: Related Workmentioning

confidence: 99%

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

et al. 2021

View full text Add to dashboard Cite

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.

show abstract

On the fulfillment of coordination requirements in open-source software projects: An exploratory study

2020

View full text Add to dashboard Cite

Tracing distributed collaborative development in apache software foundation projects

Cited by 7 publications

References 61 publications

An In-Depth Analysis of Occasional and Recurring Collaborations in Online Music Co-creation

An In-Depth Analysis of Occasional and Recurring Collaborations in Online Music Co-creation

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

On the fulfillment of coordination requirements in open-source software projects: An exploratory study

Contact Info

Product

Resources

About