[MDEV-10668] BSL - Clarify MariaDB Commitment to LGPL Connectors/Clients Created: 2016-08-25  Updated: 2018-07-31  Resolved: 2018-07-31

Status: Closed
Project: MariaDB Server
Component/s: Documentation
Affects Version/s: N/A
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Todd Farmer Assignee: Rasmus Johansson (Inactive)
Resolution: Fixed Votes: 0
Labels: None


 Description   

This is like MDEV-10666, but focuses explicitly on the LGPL-licensed client libraries and connectors produced by MariaDB.

Monty Widenius writes in his personal blog regarding the BSL:

"MariaDB Corporation will over time create more BSL products. Even with new products coming under BSL, MariaDB Server will continue to be licensed under GPL in perpetuity. Keep in mind that because MariaDB Server extends earlier MySQL GPL code it is forever legally bound by the original GPL license of MySQL."

http://monty-says.blogspot.com/2016/08/applying-business-source-licensing-bsl.html

This assertion notably covers only MariaDB Server, and not the LGPL-licensed client libraries and connectors. Quoting Wikipedia's definition of LGPL:

"The license allows developers and companies to use and integrate software released under the LGPL into their own (even proprietary) software without being required by the terms of a strong copyleft license to release the source code of their own components. The license only requires software under the LGPL be modifiable by end users via source code availability."\

https://en.wikipedia.org/wiki/GNU_Lesser_General_Public_License

I understand this to allow for the possibility of MariaDB client and connectors, which are currently licensed under LGPL, to be distributed in the future under BSL. Please clarify MariaDB's commitment to retain the LGPL licensing of all client libraries and connectors where the GPL does not currently apply.



 Comments   
Comment by Rasmus Johansson (Inactive) [ 2016-08-31 ]

There are no plans currently on changing licensing on the client and connectors.

Comment by Rasmus Johansson (Inactive) [ 2018-07-31 ]

Answered in previous comment.

Generated at Thu Feb 08 07:44:00 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.