Intrinsic vs. extrinsic incentives in profit–oriented firms supplying Open Source products and services
Open accessAbstract
This paper contributes to the literature on Open Source (OS) software by providing empirical evidence on the incentives of firms that engage in OS activities. Data collected by a survey conducted on 146 Italian companies supplying OS solutions (Open Source firms) show that (surprisingly) intrinsic, community–based incentives do play a role but are not, in general, put into practise. We investigate this discrepancy between attitudes and behaviours and single out groups of firms adopting more consistent behaviours. Our results are in line with the literature on business models of the firms that enter the Open Source field.
Integrity signals
Registry
Cites
Statistics
Claims the paper makes
Claims other papers make about this one
Each is checked against this paper’s own text: does it say what the citing paper says it does?
Small companies frequently rely on open source communities to fix bugs and improve software.
“Small companies frequently rely on open source communities to fix bugs and improve software (Rossi and Bonaccorsi, 2005).”
From Open Source Software: The New Intellectual Property Paradigm (2006) · cites this paper as Rossi and Bonaccorsi, 2005
Companies share code to test software, fix bugs, and to get improvements, feedback, and extensions, all of which they would otherwise have to do independently with substantial duplicated costs.
“In particular, companies share code to test software, fix bugs, and to get improvements, feedback, and extensions (Rossi and Bonaccorsi, 2003, 2005), all of which they would otherwise have to do independently with substantial duplicated costs.”
From Open Source Software: The New Intellectual Property Paradigm (2006) · cites this paper as Rossi and Bonaccorsi, 2005
Adopting a single, industry-wide open source standard avoids transactions costs associated with intellectual property such as 'patent thickets' and 'anticommons.'
“Adopting a single, industry-wide open source standard for software fosters a common pool of skilled workers, reduces costs associated with unnecessary versioning, increases the total number of programmers submitting bug reports and extensions, and avoids transactions costs associated with intellectual property such as 'patent thickets' and 'anticommons' (Rossi and Bonaccorsi, 2005, Lerner and Tiro”
From Open Source Software: The New Intellectual Property Paradigm (2006) · cites this paper as Rossi and Bonaccorsi, 2005
Adopting a single, industry-wide open source standard reduces costs associated with unnecessary versioning.
“Adopting a single, industry-wide open source standard for software fosters a common pool of skilled workers, reduces costs associated with unnecessary versioning, increases the total number of programmers submitting bug reports and extensions, and avoids transactions costs associated with intellectual property such as 'patent thickets' and 'anticommons' (Rossi and Bonaccorsi, 2005, Lerner and Tiro”
From Open Source Software: The New Intellectual Property Paradigm (2006) · cites this paper as Rossi and Bonaccorsi, 2005
Adopting a single, industry-wide open source standard increases the total number of programmers submitting bug reports and extensions.
“Adopting a single, industry-wide open source standard for software fosters a common pool of skilled workers, reduces costs associated with unnecessary versioning, increases the total number of programmers submitting bug reports and extensions, and avoids transactions costs associated with intellectual property such as 'patent thickets' and 'anticommons' (Rossi and Bonaccorsi, 2005, Lerner and Tiro”
From Open Source Software: The New Intellectual Property Paradigm (2006) · cites this paper as Rossi and Bonaccorsi, 2005
Adopting a single, industry-wide open source standard fosters a common pool of skilled workers.
“Adopting a single, industry-wide open source standard for software fosters a common pool of skilled workers, reduces costs associated with unnecessary versioning, increases the total number of programmers submitting bug reports and extensions, and avoids transactions costs associated with intellectual property such as 'patent thickets' and 'anticommons' (Rossi and Bonaccorsi, 2005, Lerner and Tiro”
From Open Source Software: The New Intellectual Property Paradigm (2006) · cites this paper as Rossi and Bonaccorsi, 2005
Cited by
Sorted by citations
Open Source Software: The New Intellectual Property Paradigm
Maurer, S., & Scotchmer, S. (2006) · NBER Working Paper No. 12148 · doi:10.3386/w12148 · Cited by 81 · see citing works
Acceptance of Monetary Rewards in Open Source Software Development
Krishnamurthy, S., Ou, S., & Tripathi, A. K. (2014) · Research Policy · doi:10.1016/j.respol.2013.10.007 · Cited by 65 · see citing works
- Authors
- Rossi, C., & Bonaccorsi, A.
- Venue
- First Monday
- Publisher
- University of Illinois Libraries
- Published
- 2005-05-02
- ISSN
- 1396-0458 (ISSN-L)
- 1396-0466
- OpenAlex
- W2028446887
- Cited by
- 25
- References
- 0
- Citations by year
- 2024: 1 · 2019: 1 · 2018: 1 · 2015: 1 · 2014: 1 · 2012: 2
- FWCI
- 10.17
- Type
- journal article
- Language
- en
- Open access
- diamond
- doi.org
- Locations
- First Monday (publishedVersion)
- First Monday (acceptedVersion)
- Virtual Community of Pathological Anatomy (University of Castilla La Mancha) (submittedVersion)
- Topics
- Physical Sciences › Computer Science › Computer Science Applications › Open Source Software Innovations
- Social Sciences › Business, Management and Accounting › Strategy and Management › Digital Platforms and Economics
- Physical Sciences › Computer Science › Information Systems › Software Engineering Techniques and Practices
- Keywords
- open source software, intrinsic rewards, extrinsic rewards, business models, firm incentives
About these checks
Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.
Statistics and arithmetic are recomputed, not judged.
Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.
What counts as a claim ›How we measure confidence ›How we check this ›
Are you an author, or do you see a problem with this page? Request a review
