@booklet {493,
	title = {Champions of Revealing - The Role of Open Source Developers in Commercial Firms},
	year = {2008},
	month = {Jan},
	abstract = {The link between firms engaging in open source software (OSS) development and the OSS community is established by individual developers. This linkage might entail a principal-agent issue due to the developer{\textquoteright}s double allegiance to firm and OSS community, and expose the firm to the risk of losing intellectual property. Using both interviews and a large-scale survey, I substantiate the importance of the developer{\textquoteright}s role. However, neither interview data nor regression analysis show indications of commercially harmful revealing behavior induced by ""Free Software ideology."" Management, on the other hand, sometimes seems to be overly concerned about openness. I conclude that a more positive stance towards openness will allow firms to better share in the benefits of open innovation processes.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Henkel_Champions_of_revealing_2008-01.pdf},
	author = {Joachim Henkel}
}
@unpublished {flosswp387,
	title = {Promoting the Penguin: Who is Advocating Open Source Software in Commercial Settings?},
	year = {2008},
	month = {March},
	abstract = {Most firms that use or develop software today face the questions of whether and how to engage in open source software (OSS). Yet, little is known about the process of OSS adoption and diffusion within corporations. Guided by the models of Rogers (innovation diffusion) and Davis (Technology Acceptance Model), we develop a theoretical framework of how job function influences individuals? proclivity to support their employers? adoption of OSS and OSS practices. We argue that job function determines an individual?s tasks, and that different tasks are differentially affected by OSS. Our study is based on interviews and a large-scale survey in a multinational corporation. Distinguishing between developers, testers, software architects, project managers, and managers, we find greater engagement in OSS to be favored most strongly by testers. Excepting project managers, developers, despite having the most experience with OSS, are the least favorably disposed to greater corporate OSS engagement. A corporation interested in adopting OSS should thus take into account the job function-related incentives of each individual. More generally, we propose that models predicting IT adoption behavior be extended to account for the ways in which individual adopters interact with the innovation at hand, which will be determined largely by their job functions.},
	author = {Oliver Alexy and Joachim Henkel}
}
@article {flosswp367,
	title = {Promoting the Penguin: Who is Advocating Open Source Software in Commercial Settings?},
	year = {2007},
	month = {August},
	abstract = {Most firms that use or develop software today face the questions of whether and how to engage in open source software. Yet, little is known about the process of OSS adoption and diffusion within corporations. Guided by the theoretical frameworks of Rogers (innovation diffusion) and Davis (Technology Acceptance Model), we develop a model of how job function influences individuals??? proclivity to support their employers??? adoption of OSS and OSS practices. We argue that job function determines which tasks in the software development process are part of an individual???s daily routine, and that different tasks are differentially affected by OSS. Our study is based on interviews with 25 individuals and a large-scale survey distributed to 249 participants in the telecommunications department of a multinational company. The results, although consistent with theoretical considerations, are nevertheless surprising. Distinguishing between developers, software testers, software architects, project managers, and managers, we find greater involvement in OSS activities to be favored most strongly by software testers, followed by software architects and managers. Excepting project managers, developers, despite having the most experience with OSS, are the least favorably disposed to greater corporate engagement in OSS. A corporation interested in adopting OSS and open innovation processes should thus take into account the job function-related incentives of each individual as well as various organizational factors. More generally, we propose that models developed to predict IT adoption behavior be extended to account for the ways in which individual adopters interact with the innovation at hand, which we maintain will be determined largely by their job functions.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Alexy_Henkel_-_Promoting_the_Penguin.pdf},
	author = {Oliver Alexy and Joachim Henkel}
}
@article {flosswp369,
	title = {Putting a Value on Openness: The Effect of Product Source Code Releases on the Market Value of Firms},
	year = {2007},
	month = {October},
	abstract = {This study examines the effect of releasing the source code of commercial software products as open source software on the market value of firms. Using a sample of 30 software companies in the time span from 1 January 1999 to 30 April 2007, I find that market valuation is influenced by investor sentiment???abnormal returns take a curvilinear shape over time???and the business model firms choose for their OSS efforts???non-existence of an explicit revenue model is punished by the capital market. From my findings, I deduce several implications for IT-related event studies and research on open innovation processes.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Alexy_-_Putting_a_Value_on_Openness.pdf},
	author = {Oliver Alexy and Joachim Henkel}
}
@article {flosswp158,
	title = {The Jukebox Mode of Innovation: a Model of Commercial Open Source Development},
	year = {2004},
	month = {May},
	abstract = {In this paper, I explore the circumstances under which innovation processes without secrecy or intellectual property protection are viable, and where free revealing of innovations is a profit-maximizing strategy. Motivated by an empirical study of embedded Linux, I develop a duopoly model of quality competition. Firms require two complementary technologies as inputs, but differ with respect to the relative importance of these technologies. I find that a regime with compulsory revealing can lead to higher product qualities and higher profits than a proprietary regime. When the decision to reveal is endogenized, equilibria with voluntary revealing arise, again superior to the proprietary outcome.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/henkel.pdf},
	author = {Joachim Henkel}
}
@article {flosswp167,
	title = {Munich/MIT Suvey: Development of Embedded Linux},
	year = {2004},
	month = {May},
	abstract = {The use of Linux in embedded devices has increased enormously in recent years. Most of the publicly available code for embedded Linux is developed and contributed by commercial firms, not by hobbyists. This raises the question if and how the development process differs from that of other OSS. This issue was addressed in a survey of embedded Linux developers yielding 268 valid responses. This paper is a collection of descriptive results from the survey.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/henkeltins.pdf},
	author = {Joachim Henkel}
}
@article {flosswp190,
	title = {Patterns of Free Revealing ? Balancing Code Sharing and Protection in Commercial Open Source Development},
	year = {2004},
	month = {September},
	abstract = {Commercial firms increasingly contribute to the development of open source software (OSS). However, a conflict often arises between the requirements of the General Public License to make "derived work" available, and firms? interest to protect their intellectual property embodied in the code. If there are ways to mitigate or solve this conflict, the conditions under which OSS will be an appealing solution to firms become much more general. This paper is the first to provide a quantitative empirical study of this conflict and the ways firms deal with it. I present a study of embedded Linux, based on an online-survey that yielded 268 valid responses. It turns out that firms routinely use various means to protect their developments, while keeping the GPL. Still, they do reveal a considerable share of their code? on average, 49\%. Heterogeneity between firms is analyzed using multivariate analysis. I show how the relative importance of various benefits and downsides of revealing determines a firm?s pattern of revealing. An analysis of reported reasons for revealing and of the type of code that is revealed provides further insights into these patterns. Putting the different dimensions of revealing behavior together, I find that consistent patterns of revealing can be identified for different types of firms.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/henkel2.pdf},
	author = {Joachim Henkel}
}
@article {flosswp3,
	title = {Profiting From Voluntary Information Spillovers: How Users Benefit By Freely Revealing Their Innovations},
	year = {2000},
	month = {July},
	abstract = {Software users reveal the code they have written to other users for free. This behavior is contrary to conventional wisdom in economics - but is essential to the functioning of an effective user innovation community. This paper explores conditions under which the free revealing of innovations (code, in the case of OS) pays for innovating users.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/evhippel-voluntaryinfospillover.pdf},
	author = {Dietmar Harhoff and Joachim Henkel and von Hippel, Eric}
}
