It's now safe to say that any typical piece of software now contains open source code.
You probably know, however, that while open source software delivers many benefits, it also presents certain license related risks, that have to be tamed.
To achieve this, specialized tools are required to analyze the product to determine which open source components are used, and, more importantly their licences and copyrights.
At Orange, we have been using a proprietary solution, Fossology, and are currently deploying OSS Review Toolkit.
How are you handling the open source compliance topic ? With what tools, what process?
What are your blocking points, how do you overcome them ?
Maybe your are also using Fossology, let's join forces to develop new features and fix bugs.
Let's meetup to discuss all this, share O/S compliance experiences, discuss features, bugs, processes.
All unfinished discussions can then naturally be continued during the Free Cocktail Party right afterwards :-)
