When to make proprietary software open source

B-Tier
Journal: Journal of Economic Dynamics and Control
Year: 2013
Volume: 37
Issue: 6
Pages: 1182-1194

Authors (6)

Caulkins, Jonathan P. (not in RePEc) Feichtinger, Gustav (Technische Universität Wien) Grass, Dieter (not in RePEc) Hartl, Richard F. (not in RePEc) Kort, Peter M. (Universiteit van Tilburg) Seidl, Andrea (not in RePEc)

Score contribution per author:

0.335 = (α=2.01 / 6 authors) × 1.0x B-tier

α: calibrated so average coauthorship-adjusted count equals average raw count

Abstract

Software can be distributed closed source (proprietary) or open source (developed collaboratively). While a firm cannot sell open source software, and so loses potential sales revenue, the open source software development process can have a substantial positive impact on the quality of a software, its diffusion, and, consequently, the demand for a complementary product from which the firm does profit. Previous papers have considered the firm's option to release software under a closed or open source license as a simple once and for all binary choice. We extend this research by allowing for the possibility of keeping software proprietary for some optimally determined finite time period before making it open source. Furthermore, we study the impact of switching costs.

Technical Details

RePEc Handle
repec:eee:dyncon:v:37:y:2013:i:6:p:1182-1194
Journal Field
Macro
Author Count
6
Added to Database
2026-01-25