To Fork or Not to Fork: Fork Motivations in SourceForge Projects - Open Source Systems: Grounding Research Access content directly
Conference Papers Year : 2011

To Fork or Not to Fork: Fork Motivations in SourceForge Projects

Linus Nyman
  • Function : Author
  • PersonId : 1007647
Tommi Mikkonen
  • Function : Author
  • PersonId : 1007648

Abstract

A project fork occurs when software developers take a copy of source code from one software package and use it to begin an independent development work that is maintained separately from its origin. Although forking in open source software does not require the permission of the original authors, the new version, nevertheless, competes for the attention of the same developers that have worked on the original version. The motivations developers have for performing forks are many, but in general they have received little attention. In this paper, we present the results of a study of forks performed in SourceForge (http://sourceforge.net/) and list the developers’ motivations for their actions. The main motivation, seen in close to half of the cases of forking, was content modification; either adding content to the original program or focusing the content to the needs of a specific segment of users. In a quarter of the cases the motivation was technical modification; either porting the program to new hardware or software, or improving the original.
Fichier principal
Vignette du fichier
978-3-642-24418-6_18_Chapter.pdf (110.52 Ko) Télécharger le fichier
Origin : Files produced by the author(s)
Loading...

Dates and versions

hal-01570771 , version 1 (31-07-2017)

Licence

Attribution

Identifiers

Cite

Linus Nyman, Tommi Mikkonen. To Fork or Not to Fork: Fork Motivations in SourceForge Projects. 9th Open Source Software (OSS), Oct 2011, Salvador, Brazil. pp.259-268, ⟨10.1007/978-3-642-24418-6_18⟩. ⟨hal-01570771⟩
69 View
59 Download

Altmetric

Share

Gmail Facebook X LinkedIn More