[Maria-discuss] Backporting bug fixes to 1.0?
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/cb3213af6382c380df9fc47... 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 GPL code is being linked against code covered by an incompatible license (other code in MaxScale). Almost all of the files in MaxScale 2.0 derive from 1.0 so this problem is not just in one file of course. The FSF says that the owner of the software can't legally violate the GPL they can morally violate the GPL. Will MariaDB commit to backporting all bugs in 1.0 code into the 1.0 branch?
I have been fired for speaking out about the GPL and MariaDB actions that have caused great harm to our ecosystem. It has been pointed out that I have a non-compete agreement. None of my tools compete with MariaDB and I have no non-public knowledge of MariaDB technology. GPLScale remains free software under the GNU GPL license and it is my right to fork a github repo. I am not paid to work on GPLScale and I don't intend to get paid to maintain it by anyone. All my projects are labors of love. Who wants to hire me? I'm dedicated, honest, open, and I have integrity. I'm willing to risk everything for what I believe in. Email me at: greenlion at gmail dot com ---- I have been a proponent of GPL for a long time, and I don't need publicity. http://swanhart.livejournal.com/128586r.html https://libraries.io/github/greenlion https://blog.jcole.us/2008/07/23/on-mysql-forks-and-mysqls-non-open-source-d... Justin Swanhart on July 23, 2008 at 12:09 Brian, The “thing is” that we shouldn’t have to write it. MySQL may be ‘open source’, but it isn’t ‘open software’. With all the talk recently of proprietary extensions, the documentation licensing issues, the whole ‘enterprise’ vs ‘community’ debacle, well, MySQL has totally shown that they are not ‘Open Software’ company. WHEN I WAS SEVENTEEN I BROKE THE LAW AND DROVE FROM PITTSBURGH PA TO BOSTON MA FOR THE FIRST FREE SOFTWARE FOUNDATION CONFERENCE. I sat down and had breakfast with STALLMAN, TORVALDS, AND RAYMOND! My whole life is open source. I've made my living off it and I intend to make sure others have the same opportunities that I have. Sent from my iPhone
On Aug 18, 2016, at 9:51 AM, Justin Swanhart <greenlion@gmail.com> wrote:
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/cb3213af6382c380df9fc47...
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 GPL code is being linked against code covered by an incompatible license (other code in MaxScale).
Almost all of the files in MaxScale 2.0 derive from 1.0 so this problem is not just in one file of course.
The FSF says that the owner of the software can't legally violate the GPL they can morally violate the GPL.
Will MariaDB commit to backporting all bugs in 1.0 code into the 1.0 branch?
MariaDB. :) My former termination for speaking out in private and public about ColumnStore (loudly internally for sure) was rescinded because I'm currently (well I was) on unpaid sick leave. I'm bipolar and I am current using short term disability insurance. MariaDB has no ethics or morals. Sent from my iPhone
On Aug 24, 2016, at 7:06 AM, Sergei Golubchik <serg@mariadb.org> wrote:
Hi, Justin!
On Aug 24, Justin Swanhart wrote: I have been fired for speaking out about the GPL and MariaDB actions that have caused great harm to our ecosystem.
I'm sorry to hear that. Where were you fired from?
Regards, Sergei Chief Architect MariaDB and security@mariadb.org
What I find incredibly hilarious is that ColumnStore and MariaDB are forks. They love the GPL, and think it is great when they can make money from it. MySQL was bought for 1B dollars after all, and then forked to continue earning Monty money and hurting the community - solely because the GPL said he could. MariaDB is as bad as any FUD said Oracle would be - possibly worse. And that isn't FUD, I judge actual actions, not potential ones. Sent from my iPhone
On Aug 24, 2016, at 7:06 AM, Sergei Golubchik <serg@mariadb.org> wrote:
Hi, Justin!
On Aug 24, Justin Swanhart wrote: I have been fired for speaking out about the GPL and MariaDB actions that have caused great harm to our ecosystem.
I'm sorry to hear that. Where were you fired from?
Regards, Sergei Chief Architect MariaDB and security@mariadb.org
participants (2)
-
Justin Swanhart -
Sergei Golubchik