Understanding Sustained Participation in Open Source Software Projects
Journal of Management Information Systems
A sentence-matching method for automatic license identification of source code files
Proceedings of the IEEE/ACM international conference on Automated software engineering
Proceedings of the ACM 2011 conference on Computer supported cooperative work
Train and retain: the impact of mentoring on the retention of FLOSS developers
Proceedings of the 50th annual conference on Computers and People Research
Links to the source - a multidimensional view of social ties for the retention of FLOSS developers
Proceedings of the 50th annual conference on Computers and People Research
Meanings and boundaries of scientific software sharing
Proceedings of the 2013 conference on Computer supported cooperative work
Theory and Analysis of Company-Sponsored Value Co-Creation
Journal of Management Information Systems
The attraction of contributors in free and open source software projects
The Journal of Strategic Information Systems
Proceedings of the 2013 annual conference on Computers and people research
Network ties and the success of open source software development
The Journal of Strategic Information Systems
Hi-index | 0.00 |
The Open Source Software (OSS) development model has emerged as an important competing paradigm to proprietary alternatives; however, insufficient research exists to understand the influence of some OSS project characteristics on the level of activity of the development process. A basic such characteristic is the selection of the project's software license. Drawing upon social movement theory, our study examined the relationship between OSS licenses and project activity. Some OSS licenses include a “copyleft” clause, which requires that if derivative products are to be released, it must be done under the license the original product had. We hypothesize that copylefted licenses, as opposed to noncopylefted licenses, are associated with higher developer membership and coding activity, faster development speed, and longer developer permanence in the project. To test the hypotheses, we used archival data sources of working OSS projects spanning several years of development time. We discuss practical and theoretical implications of the results as well as future research ideas. © 2009 Wiley Periodicals, Inc.