Blog Tag

Free and Open Source Software (FOSS) is "free", right? Free as in speech, and sometimes free as in beer. But the intellectual property expressed in FOSS code does not inhabit the public domain. Nearly all FOSS code is distributed under one or more licenses -- all binding agreements subject to copyright law. Compliance with FOSS licenses should not be left until a redistribution event or the launch of a service implemented with open source. This blog lays out what those compliance activities entail.

This blog seeks to inform test code creators and test automation practitioners about real-world best practices for using and integrating open source software. Many of the missteps described also apply to code published under proprietary / closed-source licenses, albeit with different terms and particulars. It is not intended to scare readers away from open source but rather, to inform test automation practitioners how to avoid the most common missteps, to realize the greatest value from open source software with the least risk.

A source-available license grants users access to source code, allowing them to view, modify, and sometimes distribute the code. However, there may be restrictions or limitations imposed. These restrictions most often include limitations on commercial use, restrictions on redistributing modified versions, or requirements to share modifications with the original developer without necessarily making them public.

Dual Licensing (or multi-licensing) is the practice of releasing source code under multiple licenses.  Most open source software is published and distributed under the rubric of a single license: Apache, GPL, Mozilla or about one hundred other licenses recognized by the Open Source Initiative.

Dual licensing, while adding complexity to use and management of open source software, serves several needs and application use cases: