TY - GEN
T1 - Leaving behind the software history when transitioning to open source
T2 - 14th IFIP WG 2.13 International Conference on Open Source Systems, OSS 2018
AU - Pinto, Gustavo
AU - Steinmacher, Igor
AU - Gerosa, Marco
N1 - Publisher Copyright:
© 2018, IFIP International Federation for Information Processing.
PY - 2018
Y1 - 2018
N2 - 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.”
AB - 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.”
UR - http://www.scopus.com/inward/record.url?scp=85048997915&partnerID=8YFLogxK
UR - http://www.scopus.com/inward/citedby.url?scp=85048997915&partnerID=8YFLogxK
U2 - 10.1007/978-3-319-92375-8_5
DO - 10.1007/978-3-319-92375-8_5
M3 - Conference contribution
AN - SCOPUS:85048997915
SN - 9783319923741
T3 - IFIP Advances in Information and Communication Technology
SP - 50
EP - 60
BT - Open Source Systems
A2 - Stamelos, Ioannis
A2 - Gonzalez-Barahoña, Jesus M.
A2 - Varlamis, Iraklis
A2 - Anagnostopoulos, Dimosthenis
PB - Springer New York LLC
Y2 - 8 June 2018 through 10 June 2018
ER -