TL;DR: This chapter discusses the open source definition, which doesn't just mean access to the source code, but also allows modifications and derived works to be distributed under the same terms, as the license of the original software.
Abstract: This chapter discusses the open source definition Open source doesn't just mean access to the source code The distribution terms of open-source software must comply with the following criteria: free redistribution, source code, derived works, integrity of the author's source code, no discrimination against a person or a group, no discrimination against fields of endeavor, distribution of license, license must Nnt be specific to a product, license must not restrict other software, and the license must be technology-neutral According to free distribution, the license does not restrict any party from selling, or giving away the software as a component of an aggregate software distribution containing programs from several different sources The program must include source code, and must allow distribution in source code in a compiled form The license must allow modifications and derived works, and must allow them to be distributed under the same terms, as the license of the original software The license may restrict the source-code from being distributed in modified form The rights attached to the program must apply to all those, to whom the program is redistributed without the need for execution of an additional license by those parties
TL;DR: In this article, a software protection comprising software license management and online software license enforcement is presented, where individual licenses are provided for regulating the use of a software product, and the software product is individualized while being downloaded from a license server.
Abstract: A software protection is presented comprising software license management and online software license enforcement, wherein individual licenses are provided for regulating the use of a software product, and the software product is individualized while being downloaded from a license server, and the execution of each individualized software product is monitored in agreement with the individual license terms corresponding to the individual software download.
TL;DR: The SQALE (software quality assessment based on life-cycle expectations) method provides guidance for managing technical debt present in an application's source code.
Abstract: To date, several methods are available for estimating the technical debt present in an application's source code. The SQALE (software quality assessment based on life-cycle expectations) method provides guidance for managing this debt. This article provides some implementation recommendations the authors learned from coaching and assisting large organizations in setting up and using SQALE.
TL;DR: An evaluation that shows that Ninka outperforms other methods of license identification in precision and speed and an empirical study on 0.8 million source code files of Debian that highlight interesting facts about the manner in which licenses are used by FOSS.
Abstract: The reuse of free and open source software (FOSS) components is becoming more prevalent. One of the major challenges in finding the right component is finding one that has a license that is e for its intended use. The license of a FOSS component is determined by the licenses of its source code files. In this paper, we describe the challenges of identifying the license under which source code is made available, and propose a sentence-based matching algorithm to automatically do it. We demonstrate the feasibility of our approach by implementing a tool named Ninka. We performed an evaluation that shows that Ninka outperforms other methods of license identification in precision and speed. We also performed an empirical study on 0.8 million source code files of Debian that highlight interesting facts about the manner in which licenses are used by FOSS
TL;DR: In this paper, the authors present a software license engine that allows an enterprise to model software license contracts and evaluate deployment of software for compliance with the license contracts, which is modeled in a configuration management database.
Abstract: A software license engine allows an enterprise to model software license contracts and evaluate deployment of software for compliance with the software license contracts. Deployment of software products in the enterprise is modeled in a configuration management database. The software license engine maintains a license database for connecting software license contracts with software deployment modeled by the configuration management database. Users of the software license engine may use license types that are predefined in the software license engine or may define custom license types. The software license engine may indicate compliance or non-compliance with the software license contracts.