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

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

Linus Nyman, Tommi Mikkonen
Copyright: © 2011 |Volume: 3 |Issue: 3 |Pages: 9
ISSN: 1942-3926|EISSN: 1942-3934|EISBN13: 9781613508732|DOI: 10.4018/jossp.2011070101
Cite Article Cite Article

MLA

Nyman, Linus, and Tommi Mikkonen. "To Fork or Not to Fork: Fork Motivations in SourceForge Projects." IJOSSP vol.3, no.3 2011: pp.1-9. http://doi.org/10.4018/jossp.2011070101

APA

Nyman, L. & Mikkonen, T. (2011). To Fork or Not to Fork: Fork Motivations in SourceForge Projects. International Journal of Open Source Software and Processes (IJOSSP), 3(3), 1-9. http://doi.org/10.4018/jossp.2011070101

Chicago

Nyman, Linus, and Tommi Mikkonen. "To Fork or Not to Fork: Fork Motivations in SourceForge Projects," International Journal of Open Source Software and Processes (IJOSSP) 3, no.3: 1-9. http://doi.org/10.4018/jossp.2011070101

Export Reference

Mendeley
Favorite Full-Issue Download

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. Although forking in open source software does not require the permission of the original authors, the new version 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. The authors present the results of a study of forks performed in SourceForge (http://sourceforge.net/) and list the developers’ motivations for their actions.

Request Access

You do not own this content. Please login to recommend this title to your institution's librarian or purchase it from the IGI Global bookstore.