Code Siblings: Technical and Legal Implications of Copying Code between Systems. German, D. M., Di Penta, M., Gu�h�neuc, Y., & Antoniol, G. In Godfrey, M. W. & Whitehead, J., editors, Proceedings of the 6<sup>th</sup> Working Conference on Mining Software Repositories (MSR), pages 81–90, May, 2009. IEEE CS Press. 10 pages.
Code Siblings: Technical and Legal Implications of Copying Code between Systems [pdf]Paper  abstract   bibtex   
Source code cloning does not happen within a single system only. It can also occur between one system and another. We use the term code sibling to refer to a code clone that evolves in a different system than the code from which it originates. Code siblings can only occur when the source code copyright owner allows it and when the conditions imposed by such license are not incompatible with the license of the destination system. In some situations copying of source code fragments are allowed—legally—in one direction, but not in the other. In this paper, we use clone detection, license mining and classification, and change history techniques to understand how code siblings—under different licenses—flow in one direction or the other between Linux and two BSD Unixes, FreeBSD and OpenBSD. Our results show that, in most cases, this migration appears to happen according to the terms of the license of the original code being copied, favoring always copying from less restrictive licenses towards more restrictive ones. We also discovered that sometimes code is inserted to the kernels from an outside source.

Downloads: 0