Stack Overflow: A Code Laundering Platform?

Developers use Question and Answer (Q&A) websites to exchange knowledge and expertise. Stack Overflow is a popular Q&A website where developers discuss coding problems and share code examples. Although all Stack Overflow posts are free to access, code examples on Stack Overflow are governed by the Creative Commons Attribute-ShareAlike 3.0 Unported license that developers should obey when reusing code from Stack Overflow or posting code to Stack Overflow. In this paper, we conduct a case study with 399 Android apps, to investigate whether developers respect license terms when reusing code from Stack Overflow posts (and the other way around). We found 232 code snippets in 62 Android apps from our dataset that were potentially reused from Stack Overflow, and 1,226 Stack Overflow posts containing code examples that are clones of code released in 68 Android apps, suggesting that developers may have copied the code of these apps to answer Stack Overflow questions. We investigated the licenses of these pieces of code and observed 1,279 cases of potential license violations (related to code posting to Stack overflow or code reuse from Stack overflow). This paper aims to raise the awareness of the software engineering community about potential unethical code reuse activities taking place on Q&A websites like Stack Overflow.Comment: In proceedings of the 24th IEEE International Conference on Software Analysis, Evolution, and Reengineering (SANER

Open Source Licensing in Mixed Markets, or Why Open Source Software Does Not Succeed

The rivalry between developers of open source and proprietary software encourages open source developers to court users and respond to their needs. If the open source developer wants to promote her own open source standard and solutions, she may choose liberal license terms such as those of the Berkeley Software Distribution as proprietary developers will then find it easier to adopt her standard in their products. If she wants to promote the use of open source software per se, she may use more restrictive license terms such as the General Public License to discourage proprietary appropriation of her effort. I show that open source software that comes late into a market will be less likely than more innovative open source software to be compatible with proprietary software, but is also more likely to be made more accessible to inexperienced users.Open Source; Software; Standards; Compatibility; Network Effects; Duopoly; Mixed Markets; Intellectual Property; Copyright; Licensing

Copyright vs. Copyleft Licencing and Software Development

This article aims at clarifying the role played by licenses within the increasingly relevant Open Source Software (OSS) phenomenon. In particular, the article explores from a theoretical point of view the comparative properties of the two main categories of OSS license--copyleft and non-copyleft licenses--in terms of their ability to stimulate innovation and coordination of development efforts. In order to do so, the paper relies on an incomplete contracting model. The model shows that, in spite of the fact that copyleft licenses entail the enjoyment of a narrower set of rights by both licensors and licensees, they may be preferred to non-copyleft licenses when coordination of complementary investments in development is important. It thus provides a non-ideologically-based explanation for the puzzling evidence showing the dominance, in terms of diffusion, of copyleft licenses.intellectual property rights, open source, copyright, copyleft, GPL license, incentives to innovation.

Open Source Software: The New Intellectual Property Paradigm

Open source methods for creating software rely on developers who voluntarily reveal code in the expectation that other developers will reciprocate. Open source incentives are distinct from earlier uses of intellectual property, leading to different types of inefficiencies and different biases in R&D investment. Open source style of software development remedies a defect of intellectual property protection, namely, that it does not generally require or encourage disclosure of source code. We review a considerable body of survey evidence and theory that seeks to explain why developers participate in open source collaborations instead of keeping their code proprietary, and evaluates the extent to which open source may improve welfare compared to proprietary development.

Open Source Software: From Open Science to New Marketing Models

-Open source Software; Intellectual Property; Licensing; Business Model.

Concurrentie, innovatie en intellectuele eigendomsrechten in software markten

This study analyzes under which circumstances it may be desirable for the government to stimulate open source software as a response to market failures in software markets. To consider whether policy intervention can increase dynamic efficiency, we discuss the differences between proprietary software and open source software with respect to the incentives to innovate and market failures that may occur. The document proposes guidelines to determine which types of policy intervention may be suitable. Our most important finding is that directly stimulating open source software, e.g. by acting as a lead customer, can improve dynamic efficiency if (i) there is a serious customer lock-in problem, while (ii) to develop the software, there is no need to purchase specific, complementary inputs at a substantial cost, and (iii) follow-on innovations are socially valuable but there are impediments to contractual agreements between developers that aim at realizing such innovations. This publication is in Dutch.

The Case for CAPSL: Architectural Solutions to Licensing and Distribution in Emerging Music Markets

Compulsory licensing in music has paved the way for a limited class of new noninteractive services. However, innovation and competition are stifled in the field of interactive or otherwise novel services due to high transaction costs inherent in direct licensing. While the creation of a new compulsory license available to a wider array of services may facilitate growth and diversity in new markets, it is unlikely that the legislative process can deliver a new compulsory regime in time to serve relevant interests. Furthermore, the risk exists that legislation written in response to contemporary technology will likely fail to recognize the diversity within the music industry, and therefore will underserve both artists and potential licensees. As such, this brief argues for the creation and adoption of a new standardized protocol for artists and labels to announce the availability of new content with attached standardized licensing terms for automated integration into the catalogs of new or existing digital music services. Such a protocol would allow for automated systems of pricing, distribution, and tracking to reduce transaction costs, increase market transparency, and commodify user participation

How open is open enough?: Melding proprietary and open source platform strategies

Computer platforms provide an integrated architecture of hardware and software standards as a basis for developing complementary assets. The most successful platforms were owned by proprietary sponsors that controlled platform evolution and appropriated associated rewards. Responding to the Internet and open source systems, three traditional vendors of proprietary platforms experimented with hybrid strategies which attempted to combine the advantages of open source software while retaining control and differentiation. Such hybrid standards strategies reflect the competing imperatives for adoption and appropriability, and suggest the conditions under which such strategies may be preferable to either the purely open or purely proprietary alternatives

Motivation and Sorting in Open Source Software Innovation

This paper studies the role of intrinsic motivation, reputation, and reciprocity in driving open source software innovation. Unlike previous literature based on survey data, we exploit the observed pattern of contributions - the .revealed preference. of developers - to infer the underlying incentives driving the decision to contribute source code. Using detailed information on code contributions and project membership, we classify software developers into distinct types and study how contributions from each developer type vary according to the open source license type and other project characteristics. We find that developers strongly sort by license type, project size, and corporate sponsorship, and that reciprocity is important only for a small subset of projects. We also show that contributions have a substantial impact on the performance of open source projects.open source software, innovation, incentives, intrinsic motivation, motivated agents, reputation, reciprocity