Software Licenses in Context: The Challenge of Heterogeneously-Licensed Systems

@article{Alspaugh2010SoftwareLI,
  title={Software Licenses in Context: The Challenge of Heterogeneously-Licensed Systems},
  author={Thomas A. Alspaugh and Walt Scacchi and Hazeline U. Asuncion},
  journal={J. Assoc. Inf. Syst.},
  year={2010},
  volume={11},
  pages={2}
}
The prevailing approach to free/open source software and licenses has been that each system is developed, distributed, and used under the terms of a single license. But it is increasingly common for information systems and other software to be composed with components from a variety of sources, and with a diversity of licenses. This may result in possible license conflicts and organizational liability for failure to fulfill license obligations. Research and practice to date have not kept up… 
The Challenge of Heterogeneously Licensed Systems in Open Architecture Software Ecosystems
TLDR
This work has developed an approach for understanding and modeling software licenses, as well as for analyzing conflicts among groups of licenses in realistic system contexts and for guiding the acquisition, integration, or development of systems with open-source components in such an environment.
Open Source Software: A Survey from 10, 000 Feet
TLDR
Through its widespread adoption, oss is affecting the software industry, science, engineering, research, teaching, the developing countries, and the society at large through its ability to democratize technology and innovation.
Understanding the role of licenses and evolution in open architecture software ecosystems
Software Licenses, Open Source Components, and Open Architectures
TLDR
This paper identifies key properties of OSS licenses, presents a license analysis scheme to identify license conflicts arising from composed software elements, and applies it to provide guidance for software architectural design choices whose goal is to enable specific licensed component configurations.
On licensing and other conditions for contributing to widely used open source projects: an exploratory analysis
TLDR
It is found that strong copyleft licenses are most common and are used in the majority of the projects, and use of no specific other conditions in addition to the license terms is more common for projects using strong copylesft licensing compared to projects using non-copyleft licensing.
Open Source License Violation Check for SPDX Files
TLDR
This work on license violation checking in the framework of Software Package Data Exchange (SPDX) examines potential violations in software package information formatted using the SPDX specification and proposes alternative solutions in the form of applicable licenses for the software package.
A market mechanism for software component reuse: opportunities and barriers
TLDR
It is argued that as software development is increasingly using modularized and component-based approaches software vendor strategies based on flexible licenses permitting the reuse of software offer a viable and sustainable alternative to the traditional software business model build on monolithic user licenses.
Achieving Better Buying Power through Acquisition of Open Architecture Software Systems: Volume 1
Abstract : This research focuses on continuing investigation and refinement of techniques for identifying and reducing the costs, streamlining the process, and improving the readiness of future
...
...

References

SHOWING 1-10 OF 92 REFERENCES
License integration patterns: Addressing license mismatches in component-based development
  • D. Germán, A. Hassan
  • Computer Science, Economics
    2009 IEEE 31st International Conference on Software Engineering
  • 2009
TLDR
A model is developed which describes the interconnection of components in these packages from a legal point of view and is used to document integration patterns that are commonly used to solve the license mismatch problem in practice when creating both proprietary and OSS applications.
Determinants of the Choice of Open Source Software License
TLDR
It is found that OSS managers who want to attract a limited number of highly skilled programmers to their open source project should choose a restrictive OSS license, and managers of software projects for social programs could attract more developers by choosing a restrictiveOSS license.
Rethinking Consideration in the Electronic Age
Our fast-paced age of electronic agreements that ostensibly govern transactions as diverse as downloading software, ordering goods, and engaging in collaborative development projects raises questions
An exploratory study of the evolution of software licensing
TLDR
This work proposes an approach to automatically track changes occurring in the licensing terms of a system and reports an empirical study of the licensing evolution of six different FOSS systems, showing that licensing underwent frequent and substantial changes.
Impacts of License Choice and Organizational Sponsorship on User Interest and Development Activity in Open Source Software Projects
TLDR
A model of the impacts of license restrictiveness and organizational sponsorship on two indicators of success: user interest in, and development activity on, open source software development projects concludes that users are most attracted to projects that are sponsored by nonmarket organizations and that employ nonrestrictive licenses.
Current developments in Open Source Software
The Role of Software Licenses in Open Architecture Ecosystems
TLDR
This work discusses software ecosystems of open architecture systems from the perspective of an architect or an acquisition organization, and outlines how the automated tool and environment help address their challenges, support reuse, and assist in managing coevolution and component interdependence.
Automated software license analysis
TLDR
The results validate the general feasibility of the ASLA approach in the context of analyzing non-trivial OSS packages and show that licenses for 89% of the source code files can be identified by using ASLA and that the efficiency of the automated analysis is 111 files per second.
Free software developers as an occupational community: resolving conflicts and fostering collaboration
TLDR
This paper characterize the GNUe developers as an occupational subculture within the occupational community of free/open source software (F/OSS) developers and show how the beliefs in free software and freedom of choice, and values in cooperative work and community assist GNUe contributors in mitigating and resolving conflict.
Dangerous Liaisons — Software Combinations as Derivative Works? Distribution, Installation, and Execution of Linked Programs Under Copyright Law, Commercial Licenses, and the GPL
TLDR
Fear, uncertainty and doubt (FUD) regarding the answers to these questions are prevalent in all quarters and have become a prominent topic in the computer lawyer community.
...
...