Slashdot Mirror
Maui X-Stream: GPL Violations, Lies, and Damn Lies
Jeremy writes "Drunkenbatman is at it again. This time he takes apart Maui X-Stream and all the who and whats that go along with it. Deconstructing Maui X-Stream has GPL Violations with reproducable proof (not done this myself), chat logs, and double talk from the CEO's and supposed authors of the software."
That's why this keeps happening.
If I do this, and get caught...so what? What's the penalty? Exactly who is going to prosecute?
What if this CEO came right out and said "Yup, copied the whole damn thing from Sourceforge. What are you going to do about it?" What happens next?
PS: Not trolling, genuinely curious. All the focus seems to be on "Is the GPL enforcable", not "Who shall enforce it". And IMHO, both are important.
Weaselmancer
rediculous.
GPL violations seem to be getting more and more common. Take for instance eMule, where an eMule+ developer is knowingly breaking the GPL while working for a proprietary company called MetaCafe:c =72668 (login probably required)
http://forum.emule-project.net/index.php?showtopi
http://forums.metacafe.com/viewtopic.php?t=139
The worst part is probably that the eMule+ folks, who forked the eMule codebase and should be well aware of how the GPL works, are directly contributing to this violation.
GPL violations are a lot more common than most people think.
Just because it doesn't hit the mainstream media doesn't mean that thousands (yes, thousands of OSS projects out there are being actively violated by commercial enterprises). A few years ago I caught Sony doing this and reported about it (picked up by Slashdot here based on my account).
But that was relatively small potatoes to another GPL violation we've had to deal with. The CEO of a mobile company (who shall remain nameless, thousands know who he is) took our code, stripped our names and attribution out, removed the COPYING file (our copy of the GPL license), put his name all over it, and claimed he wrote it. He also waffled and lied over the years about which parts of our project he was and was not using. His stories changed back and forth (and I have all of the emails confirming these wishy-washy statements).
When we started seeing companies giving away binary versions of an application that looked suspisciously like ours (and I mean pixel-for-pixel identical) without any source, attribution or links back to the GPL, we started calling those companies and requesting the source for compliance. Since these companies had no idea who we were, they referred us back to the company they bought it from.. the original one who took our code from us outside of compliance with the GPL.
Then the threats started coming in... from the CEO of the company that originally took our source. My favorite quote from him:
We were appointed an amazing attorney by the FSF, and she represented us well. I even went to NYC to meet with this CEO with Wendy to discuss how they could bring themselves into compliance. The CEO insisted that "..the GPL is not a license, its subject to interpretation... it was never reviewed by real attorneys or tested in court", and then proceeded to tell me to fire my attorney, right in front of her, because he said she wasn't giving me correct information about the law. Yeah ok, except she TEACHES law, and this CEO does what again? Oh yeah, steals other people's products for his own profitous gain.
He continued to threaten us for contacting his "partners" (who were also not transferred the GPL when he sold them "his" product [using our code]). Of course his threats fell on deaf ears, since it is our duty to require compliance with our code no matter who uses it.
The case goes on now, 4+ years later, but some interesting facts have come to light and we may have some official corporate backing from someone he believes is a partner of his... this is FAR from over, and he has absolutely no idea what mountain of legal stress is heading his way.
Wendy has moved on to the EFF now, and we have some new legal contacts at the FSF to try persue this further, but they're busy with lots of other cases.
If anyone is interested in hearing more details, feel free to contact me. If you want to support our case against companies like this, please visit our donation page and contribute to help us fund more legal support (or just because your appreciate our work: Don't forget to check out our Plucker eye-candy page).
True, but it takes a judge to administer the paddle once your pants are down.
The people in charge of the groups that own the code should get together and give permission for something like FSF to pursue this case in court (FSF has a few lawyers, I believe), and FSF gets to keep any money won in the suit. This appears to be an open-and-shut case. X-Stream gets shut down, FSF can try to get a lot of money from them, and the general public gets the source code to this nice (if stolen) software. Sounds like a win-win proposition to me.
"-1 Troll" is the apparently the same as "-1 I disagree with you."