Open Source Summit + Embedded Linux Conference Europe 2020

Different organizations do open source compliance differently. The approach, the level of automation and the compliance practices vary. In addition different open source communities have created a selection of tools for the compliance verification. Some tools fit some approaches better than other. But how does my organization’s approach compare to another organization’s? What tools could be useful for me? Are the tools any good? In order to compare approaches, tools and see what fits and what doesn't, the industry needs a common way to name and address the different steps in the open source compliance process. This presentation dissects the open source compliance checking steps, names and describes them (Sir Bedevere, wood, and a duck. Or was it lead?). It also describes the different approaches different companies take to executing these steps, particularly describing the Nokia approach. As a practical step, the presentation shows the results of our study to investigate how the current open source compliance tools perform the different steps of open source compliance. We might also relieve if the tools weigh the same as a duck…