August 9th, 2024

The Complexity of Business Source License (BUSL) Transformation

The Business Source License allows software to shift from proprietary to open-source after four years, creating challenges for Linux distributions regarding licensing, packaging, and security updates for transformed software.

Read original articleLink Icon
The Complexity of Business Source License (BUSL) Transformation

The Business Source License (BUSL) is a source-available license that transitions to an open-source license after a specified period, typically four years. This concept allows software to be proprietary initially and then become open-source, which has been adopted by several companies, including MariaDB for its MaxScale product. However, the transition raises complexities for Linux distributions, particularly regarding how to handle software that has changed from BUSL to a free license. Recent discussions within the Fedora Project highlighted concerns about categorizing such software and the potential risks involved in packaging it. Legal experts noted that it could be challenging to determine whether a version of the software still contains BUSL elements, complicating its acceptance in Fedora. Additionally, there are unresolved questions about how to manage security updates for these transformed licenses, as packagers may need to implement their own fixes, effectively creating a fork of the software. The conversation underscored the need for clearer guidelines on handling software that transitions from BUSL to open-source licenses, as well as the importance of companies considering open-source licenses from the outset to avoid these complications.

- BUSL allows software to transition from proprietary to open-source after a set period.

- The transition creates challenges for Linux distributions in terms of licensing and packaging.

- Legal uncertainties exist regarding the categorization of software that has changed licenses.

- Packagers may need to implement their own security fixes for ex-BUSL software.

- Clearer guidelines are needed for handling software transitioning from BUSL to open-source licenses.

Related

Link Icon 1 comments
By @whitten - 8 months
Could anyone please point to the story behind GhostScript and its licensing ?