Attribution Required: Stack Overflow Code Snippets in GitHub Projects

July 03, 2017 ยท Declared Dead ยท ๐Ÿ› 2017 IEEE/ACM 39th International Conference on Software Engineering Companion (ICSE-C)

๐Ÿ‘ป CAUSE OF DEATH: Ghosted
No code link whatsoever

"No code URL or promise found in abstract"

Evidence collected by the PWNC Scanner

Authors Sebastian Baltes, Richard Kiefer, Stephan Diehl arXiv ID 1707.00452 Category cs.SE: Software Engineering Citations 42 Venue 2017 IEEE/ACM 39th International Conference on Software Engineering Companion (ICSE-C) Last Checked 3 months ago
Abstract
Stack Overflow (SO) is the largest Q&A website for developers, providing a huge amount of copyable code snippets. Using these snippets raises various maintenance and legal issues. The SO license requires attribution, i.e., referencing the original question or answer, and requires derived work to adopt a compatible license. While there is a heated debate on SO's license model for code snippets and the required attribution, little is known about the extent to which snippets are copied from SO without proper attribution. In this paper, we present the research design and summarized results of an empirical study analyzing attributed and unattributed usages of SO code snippets in GitHub projects. On average, 3.22% of all analyzed repositories and 7.33% of the popular ones contained a reference to SO. Further, we found that developers rather refer to the whole thread on SO than to a specific answer. For Java, at least two thirds of the copied snippets were not attributed.
Community shame:
Not yet rated
Community Contributions

Found the code? Know the venue? Think something is wrong? Let us know!

๐Ÿ“œ Similar Papers

In the same crypt โ€” Software Engineering

Died the same way โ€” ๐Ÿ‘ป Ghosted