BSL BS: How do you backport fixes from MaxScale 2.0 to MaxScale 1.0?

Datetime:2016-08-23 02:22:08          Topic:          Share

I have created a GitHub fork of MaxScale which does not include the 2.0 branch.  The repository is called GPLScale.

There is a big potential problem with this.  Take for example the file server/core/utils.c , which now has a new license:

https://github.com/mariadb-corporation/MaxScale/blob/2.0/server/core/utils.c

This file WAS covered under GPL:

https://github.com/mariadb-corporation/MaxScale/blob/cb3213af6382c380df9fc47347764f087ae7ecb4/server/core/utils.c

When there is a bugfix in 2.0 for server code that existed in 1.0, can that code be backported directly into GPLscale?

a) util.c in 2.0 is clearly derivative of 1.0, and is therefore a derivative work of 1.0 and therefore still covered by GPL and b) there is a violation of GPL, because 1.0 code is being linked against code covered by an incompatible license.

The FSF says that the owner of the software can't legally violate the GPL they can morally violate the GPL.  MariaDB Corporation has shown that they do not have very good ethics and morals.  The MariaDB executives knowingly released MariaDB Corporation ColumnStore alpha 1 with bundled included libraries which included 10+ year old vulnerabilities.  The bundled net-snmp library could have been updated before releasing (in fact, I removed it almost immediately after the release) but they would not hold up the alpha release deadline, which was a meaningless deadline.  It still doesn't even compile correctly in the master branch (the released alpha only compiles on a specially configured VM).  Releasing code that can't compile is also not against the letter of the GPL, but it is certainly against the spirit of it.

MariaDB has shown that they do not care about open source and free software.  This is not FUD.