Copilot, an artificial intelligence-based system for automatically generating source code, has just been sued for $9 billion in damages for “software piracy.” This amount is based on a calculation from 3.5 million copyright infringements allegedly committed by the system, at the compensation of $2,500 damages per case. What is the background? Artificial intelligence (AI) is now appearing in all areas

Open Source (OSS) is everywhere. Nowadays, hardly any project can be carried out economically if existing software packages are not reused. This is advantageous for software development: The usage of Open Source increases the speed of development, reduces costs, and very often is of higher quality then similar code written in-house due to extensive collaboration of many people. Open Source

Open Source is everywhere. Experienced developers do not write code from scratch, they know where to get code. Improving productivity, shortening time to market, and reducing development costs are all good reasons to use Open Source code. However, by using open source components, organizations ultimately take responsibility for the code they did not write. One interesting aspect of Software Composition

Over the past decade I have observed how the sentiment around Open Source Disclosure has changed from why should I tell what open source I use to how should I do it and even how do I do it better than my competitors? During my recent vacation (before the world had collapsed into the pandemic paralysis) I have rented a

Identifying all copyright holders, licenses and license obligations within a Linux distribution is one of the most complex and tedious audit activities. In earlier Linux versions, before version 4.19, many source files in the tree are missing licensing information. This makes it hard for compliance tools to determine the correct license, and a manual audit is very time consuming. By