Leaving Behind the Software History When Transitioning to Open Source: Reasons and Implications

Author(s)

Pinto, Gustavo ; Steinmacher, Igor ; Gerosa, Marco ; Stamelos, I ; GonzalezBarahona, JM ; Varlamis, I ; Anagnostopoulos, D

• Document type: Journal article
• Source: OPEN SOURCE SYSTEMS: ENTERPRISE SOFTWARE AND SOLUTIONS, OSS 2018; v. 525, p. 11-pg., 2018-01-01.

Abstract

Maintenance of software history is regarded to be one of the most relevant features of Version Control Systems (VCS) and is well-known to be indispensable for software developers. However, transitioning from proprietary to open source software poses a challenge: keeping the software history might make available years of historical records and internal matters from the company that built the software. On the other hand, removing the software history may disturb the development and may be harmful to new contributors. We conducted a survey with open source software projects that made this shift to investigate (1) the reasons why they removed the software history and (2) the challenges that developers face with the lack of availability of software history. Among the results, we found that the most common reason for removing the software history is because it is entangled with proprietary code (the fact that the history contains sensitive information appears next). Interestingly, most core developers believed that the lack of software history is, in the worst case, "a very minor inconvenience." (AU)

• FAPESP's process: 15/24527-3 - Fostering open source software communities on the internet by supporting newcomer software developers
• Grantee: Ivanilton Polato
• Support Opportunities: Regular Research Grants