NDLI: A method to detect license inconsistencies in large-scale open source projects

Please wait, while we are loading the content...

Confessions of a worldly software miner

Code ownership and software quality: a replication study

The uniqueness of changes: characteristics and applications

Using developer-interaction trails to triage change requests

Characteristics of useful code reviews: an empirical study at Microsoft

Ecosystems in GitHub and a method for ecosystem identification using reference coupling

Are these bugs really "normal"?

An empirical study of end-user programmers in the computer music community

A method to detect license inconsistencies in large-scale open source projects

Automatically prioritizing pull requests

The synergy between voting and acceptance of answers on stackoverflow, or the lack thereof

A repository with 44 years of Unix evolution

Extracting facts from performance tuning history of scientific applications for predicting effective optimization patterns

Co-evolution of infrastructure and source code: an empirical study

An empirical study of the copy and paste behavior during development

Will they like this?: evaluating code contributions with language models

A historical analysis of Debian package incompatibilities

Do bugs foreshadow vulnerabilities?: a study of the Chromium project

Are bullies more productive?: empirical study of affectiveness vs. issue fixing time

Toward deep learning software repositories

Matching GitHub developer profiles to job advertisements

Quality questions need quality code: classifying code fragments on stack overflow

The Debsources dataset: two decades of Debian source code metadata

Mining component repositories for installability issues

Mining energy-aware commits

Mining Android app usages for generating actionable GUI-based execution scenarios

Investigating code review practices in defective files: an empirical study of the Qt system

Recommending posts concerning API issues in developer q&a sites

Characterization and prediction of issue-related risks in software projects

What is the Gist?: understanding the use of public Gists on GitHub

Identifying software process management challenges: survey of practitioners in a large global IT company

Wait for it: determinants of pull request evaluation latency on GitHub

ETA: estimated time of answer predicting response time in stack overflow

A dataset of the activity of the git super-repository of Linux in 2012

Why power laws?: an explanation from fine-grained code changes

The app sampling problem for app store mining

Partitioning composite code changes to facilitate code review

An empirical study of architectural change in open-source software systems

Toward reusing code changes

Going green: an exploratory analysis of energy-related questions

StORMeD: stack overflow ready made data

Sameness: an experiment in code search

Unveiling exception handling bug hazards in Android based on GitHub and Google code issues

Lessons learned from building and deploying a code review analytics platform

A study on the role of software architecture in the evolution and quality of software

Modifications, tweaks, and bug fixes in architectural tactics

Mining StackOverflow to filter out off-topic IRC discussion

The MetricsGrimoire database collection

Do onboarding programs work?

An insight into the unresolved questions at stack overflow

Landfill: an open dataset of code smells with public evaluation

An enhanced graph-based infrastructure for software search engines

Mining successful answers in stack overflow

Fuse: a reproducible, extendable, internet-scale corpus of spreadsheets

Organizational volatility and post-release defects: a replication case study using data from Google Chrome

Quick trigger on stack overflow: a study of gamification-influenced member tendencies

Dataset of developer-labeled commit messages

Detecting and mitigating secret-key leaks in source code repositories

Intuition vs. truth: evaluation of common myths about stackoverflow posts

A novel industry grade dataset for fault prediction based on model-driven developed automotive embedded software

Summarizing complex development artifacts by mining heterogeneous data

Predicting answering times on stack overflow

The Firefox temporal defect dataset

An empirical study on stack overflow using topic analysis

An architectural evolution dataset

Stack overflow badges and user behavior: an econometric approach

A dataset for API usage

Employing source code information to improve question-answering in stack overflow

Generating the blueprints of the Java ecosystem

One-day flies on StackOverflow: why the vast majority of stackoverflow users only posts once

A data set for social diversity studies of GitHub teams

A dataset of high impact bugs: manually-classified issue reports

A dataset of open-source Android applications

A method to detect license inconsistencies in large-scale open source projects

Content Provider	ACM Digital Library
Author	Wu, Yuhao Kanda, Tetsuya German, Daniel M. Inoue, Katsuro Manabe, Yuki
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.
Starting Page	324
Ending Page	333
Page Count	10
File Format	PDF
ISBN	9780769555942
Language	English
Publisher	Association for Computing Machinery (ACM)
Publisher Date	2015-05-16
Access Restriction	Subscribed
Content Type	Text
Resource Type	Article

Central Library (ISO-9001:2015 Certified)
Indian Institute of Technology Kharagpur
Kharagpur, West Bengal, India | PIN - 721302

See location in the Map
03222 282435
Mail: support@ndl.gov.in

Sl.	Authority	Responsibilities	Communication Details
1	Ministry of Education (GoI), Department of Higher Education	Sanctioning Authority	https://www.education.gov.in/ict-initiatives
2	Indian Institute of Technology Kharagpur	Host Institute of the Project: The host institute of the project is responsible for providing infrastructure support and hosting the project	https://www.iitkgp.ac.in
3	National Digital Library of India Office, Indian Institute of Technology Kharagpur	The administrative and infrastructural headquarters of the project	Dr. B. Sutradhar bsutra@ndl.gov.in
4	Project PI / Joint PI	Principal Investigator and Joint Principal Investigators of the project	Dr. B. Sutradhar bsutra@ndl.gov.in Prof. Saswat Chakrabarti will be added soon
5	Website/Portal (Helpdesk)	Queries regarding NDLI and its services	support@ndl.gov.in
6	Contents and Copyright Issues	Queries related to content curation and copyright issues	content@ndl.gov.in
7	National Digital Library of India Club (NDLI Club)	Queries related to NDLI Club formation, support, user awareness program, seminar/symposium, collaboration, social media, promotion, and outreach	clubsupport@ndl.gov.in
8	Digital Preservation Centre (DPC)	Assistance with digitizing and archiving copyright-free printed books	dpc@ndl.gov.in
9	IDR Setup or Support	Queries related to establishment and support of Institutional Digital Repository (IDR) and IDR workshops	idr@ndl.gov.in