An Exploratory Study to Find Motives Behind Cross-platform Forks from Software Heritage Dataset

Abstract

The fork-based development mechanism provides the flexibility and the unified processes for software teams to collaborate easily in a distributed setting without too much coordination overhead. Currently, multiple social coding platforms support fork-based development, such as GitHub, GitLab, and Bitbucket. Although these different platforms virtually share the same features, they have different emphasis. As GitHub is the most popular platform and the corresponding data is publicly available, most of the current studies are focusing on GitHub hosted projects. However, we observed anecdote evidences that people are confused about choosing among these platforms, and some projects are migrating from one platform to another, and the reasons behind these activities remain unknown. With the advances of Software Heritage Graph Dataset (SWHGD), we have the opportunity to investigate the forking activities across platforms. In this paper, we conduct an exploratory study on 10 popular open-source projects to identify cross-platform forks and investigate the motivation behind. Preliminary result shows that cross-platform forks do exist. For the 10 subject systems in this study, we found 81,357 forks in total among which 179 forks are on GitLab. Based on our qualitative analysis, we found that most of the cross-platform forks that we identified are mirrors of the repositories on another platform, but we still find cases that were created due to preference of using certain functionalities (e.g. Continuous Integration (CI)) supported by different platforms. This study lays the foundation of future research directions, such as understanding the differences between platforms and supporting cross-platform collaboration.

Improving Collaboration Efficiency in Fork-Based Development

“…Therefore, it is interesting to look at different and the trade-offs between platforms. As a starting point, we have studied forks that were originated on GITHUB and then migrated to GITLAB [30] by mining the Software Heritage Graph Dataset [172], which contains the forking history of both GITHUB and GITLAB, although the dataset is not reliable and complete enough. Similarly, Pietri et al [173] has found large amount of forks that cannot be detected through GITHUB API.…”

Release conventions of open‐source software: An exploratory study

“…An origin is a location from where software development data and software itself are found while crawling the internet by the Software Heritage. A single software system can have multiple origins for different development repositories (e.g., the collaborative repositories, mirrors on forges, and forks by contributors) 11 . In this study, our first step is to collect the release information of each candidate software origin.…”

“…A single software system can have multiple origins for different development repositories (e.g., the collaborative repositories, mirrors on forges, and forks by contributors). 11 In this study, our first step is to collect the release information of each candidate software origin. Details of the candidate selection and data extraction process are discussed in Section 4.…”