Uma abordagem para atualização de forks frente ao projeto original

• Ano de defesa: 2021
• Autor(a) principal: Marcondes, Arthur Roberto
• Tipo de documento: Dissertação
• Tipo de acesso: Acesso aberto
• Idioma: por
• Instituição de defesa: Universidade Federal de Lavras; Programa de Pós-Graduação em Ciência da Computação; UFLA; brasil; Departamento de Ciência da Computação
• Palavras-chave em Português: Evolução de software; Atualização de fork; Conflitos de mesclagem; Software evolution; Fork update; Merge conflicts; Ciência da Computação
• Link de acesso: http://repositorio.ufla.br/jspui/handle/1/46129

Several software projects start from an existing project. This practice, in the VCS ecosystem, is called fork. For instance, the Bootstrap project, initially developed on Twitter, has in December 2020 more than 68,000 forks, which indicates that several projects started from the Bootstrap source code at a certain moment and are being customized. The problem occurs when customized projects want to obtain updates from the original project, i.e., new features, bug fixes, etc. The merge of the source code between the original and the customized projects usually generates conflicts that need human resolution. More important, the resolution of those conflicts might not be trivial and poses an arduous task for developers. This dissertation, therefore, proposes an approach for updating forks against the original project where features are modularized, documented, traceable, and can be reused. We claim that the such task can no longer be carried out on an ad hoc basis. The approach updates those systems in a non-invasive way, which preserves the independence of the customized project does not requires direct interventions in the original project. For this purpose, it specifies features on a high level using a DSL (Domain Specific Language). In a nutshell, instead of modify the method foo from the original project, the developer implements it locally and specifies, using one of the eleven instructions of the proposed DSL, something like “replace the foo method with local implementation”. We developed a tool that automates the approach and conduced an evaluation on a real-world project that is regularly updated against your original project. Through this evaluation we found that the approach applies to real scenarios and avoids merging conflicts. We also evaluated the perspective of the developers of this project regarding the proposed approach, which proved to be positive and contributed to the planning of future work.