Reply to post: Re: @AC - I understand where the dev is coming from but ....

FUSE for macOS: Why a popular open source library became closed source and commercially licensed

Venerable and Fragrant Wind of Change

Re: @AC - I understand where the dev is coming from but ....

Two answers to that.

One, it's nowhere near your claim of GPL code being derivative of BSD code and causing problems for the latter. Unless you're going to claim something about MySQL's heritage?

Two, the issue I mentioned was one of ASF policy never to distribute code whose licence is in any way more restrictive than Apache's own. So we arrived at a point where Apache could bundle a generic SQL interface with drivers for open source (eg PostgreSQL), closed source (e.g. Oracle) and for third-party standards (e.g. ODBC), but a MySQL driver could only be distributed by a third-party. The effect of the FOSS exception was to permit the MySQL driver to be distributed under the Apache Licence, and thus by Apache itself, so lowering the barriers to adoption.

See here for the Debian angle on it (a few months later, the ASF accepted it under the FOSS exception too). And further down the thread, a more serious problem (also here - it didn't go away from non-Debian user-land just because Debian dealt with it) having nothing to do with licencing.

POST COMMENT House rules

Not a member of The Register? Create a new account here.

  • Enter your comment

  • Add an icon

Anonymous cowards cannot choose their icon

SUBSCRIBE TO OUR WEEKLY TECH NEWSLETTER

Biting the hand that feeds IT © 1998–2020