@proceedings {1895,
	title = {How are Developers Treating License Inconsistency Issues? A Case Study on License Inconsistency Evolution in FOSS Projects},
	volume = {496},
	year = {2017},
	month = {05/2017},
	pages = {69-79},
	publisher = {Springer},
	abstract = {A license inconsistency is the presence of two or more source files that evolved from the same original file containing different licenses. In our previous study, we have shown that license inconsistencies do exist in open source projects and may lead to potential license violation problems. In this study, we try to find out whether the issues of license inconsistencies are properly solved by analyzing two versions of a FOSS distribution{\textemdash}Debian{\textemdash}and investigate the evolution patterns of license inconsistencies. Findings are: license inconsistencies occur mostly because the original copyright owner updated the license while the reusers were still using the old version of the source files with the old license; most license inconsistencies would disappear when the reusers synchronize their project from the upstream, while some would exist permanently if reusers decide not to synchronize anymore. Legally suspicious cases have not been found yet in those Debian distributions.},
	keywords = {Code clone, debian, License inconsistency, licenses, Software license},
	doi = {10.1007/978-3-319-57735-7_8},
	url = {https://link.springer.com/chapter/10.1007/978-3-319-57735-7_8},
	author = {Y. Wu and Manabe, Yuki and Daniel M. Germ{\'a}n and Inoue, K.}
}
@proceedings {1776,
	title = {A Method to Detect License Inconsistencies in Large-Scale Open Source Projects},
	year = {2015},
	month = {05/2015},
	publisher = {IEEE},
	abstract = {The reuse of free and open source software (FOSS)
components is becoming more and more popular. They usually
contain one or more software licenses describing the requirements
and conditions which should be followed when been reused.
Licenses are usually written in the header of source code files as
program comments. Removing or modifying the license header
by re-distributors will result in the inconsistency of license with
its ancestor, and may potentially cause license infringement. But
to the best of our knowledge, no research has been devoted
to investigate such kind of license infringements nor license
inconsistencies. In this paper, we describe and categorize different
types of license inconsistencies and propose a feasible method to
detect them. Then we apply this method to Debian 7.5 and present
the license inconsistencies found in it. With a manual analysis, we
summarized various reasons behind these license inconsistencies,
some of which imply license infringement and require the attention
from the developers. This analysis also exposes the difficulty
to discover license infringements, highlighting the usefulness of
finding and maintaining source code provenance.},
	url = {http://sel.ist.osaka-u.ac.jp/lab-db/betuzuri/archive/992/992.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/992.pdf},
	author = {Yuhao Wu and Manabe, Yuki and Tetsuya Kanda and Daniel M. German and Inoue, Katsuro}
}
@inbook {1595,
	title = {Analyzing the Relationship between the License of Packages and Their Files in Free and Open Source Software},
	booktitle = {Open Source Software: Mobile Open Source Technologies},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {427},
	year = {2014},
	pages = {51-60},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	abstract = {Free and Open Source Software (FOSS) is widely reused today. To reuse FOSS one must accept the conditions imposed by the software license under which the component is made available. This is complicated by the fact that often FOSS packages contain files from many licenses. In this paper we analyze the source code of packages in the Fedora Core Linux distribution with the goal of discovering the relationship between the license of a source package, and the license of the files it contains. For this purpose we create license inclusion graphs. Our results show that more modern reciprocal licenses such as the General Public License v3 tend to include files of less licenses than its previous versions, and that packages under an Apache License tend to contain only files under the same license.},
	isbn = {978-3-642-55127-7},
	doi = {10.1007/978-3-642-55128-4_6},
	url = {http://dx.doi.org/10.1007/978-3-642-55128-4_6},
	author = {Manabe, Yuki and German, DanielM. and Inoue, Katsuro},
	editor = {Corral, Luis and Sillitti, Alberto and Succi, Giancarlo and Vlasenko, Jelena and Wasserman, AnthonyI.}
}
