New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GPL violation? XYZware #4103
Comments
I can't say I'm surprised in the least, @alexrj needs to weigh in. That the comments are the same too is pretty telling. |
They are also using several other open source projects, with a range from simple libraries, some gpl, lgpl, mit, to repetier where they just removed nearly all the functionality + donate button and any mention.. which is legal according to the license, but still, dick move. This is a fair bit plaincut and not so much edgecase :). Need a dump? |
This user license agreement (this "Agreement") governs your use of XYZWare software ("XYZWare") and defines the relationship between you, or in the case that you represent and are using XYZWare on behalf of a company or other entity, that company or other entity ("you") and XYZprinting, Inc., a Taiwanese company ("XYZprinting"). PLEASE READ THIS AGREEMENT BEFORE PRESSING THE "AGREE" BUTTON AND CHECKING THE BOX WHERE THE OPTION IS MADE AVAILABLE TO YOU. BY PRESSING "AGREE," YOU REPRESENT AND WARRANT THAT YOU HAVE THE AUTHORITY TO ACCEPT THIS AGREEMENT AND YOU ARE AGREEING TO BE BOUND BY THE TERMS OF THIS AGREEMENT. IF YOU DO NOT AGREE TO THE TERMS OF THIS AGREEMENT, PRESS "CANCEL" AND STOP USING AND/OR DOWNLOADING XYZWare.
QUESTIONS OR ADDITIONAL INFORMATION. |
Well anything that is MIT/BSD is legit to do what they want. But GPLv3 (which is what Slic3r is under) requires that source modifications (which hey, they made) are available. |
Interestingly enough, the new Simplify3D produces a "new" gap fill with the
familiar "trimmed skeleton" pattern. From how it works, it looks like they
used the Slic3r gap fill code verbatim.
…On Thu, Aug 31, 2017 at 5:35 PM, Joseph Lenox ***@***.***> wrote:
Well anything that is MIT/BSD is legit to do what they want. But GPLv3
(which is what Slic3r is under) requires that source modifications (which
hey, they made) are available.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#4103 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AFj5IxYpQ7nsfAILY9jl61Pidlj2hYABks5sdtLHgaJpZM4PI70G>
.
|
@magnusjjj is that the old open-licensed repetier they jacked or the newer closed source repetier? |
@lordofhyphens : What licenses has the project had? I linked the revison for that one file that is the closest I could find energy for that day. Wouldn't know any closer to that. |
The revision itself is something like 4 years old. |
As far as I know Slic3r has always been GPL.
I was wondering about RepetierHost (which you has mentioned that they had
used it whole with the branding ripped out).
…On Sep 3, 2017 5:16 AM, "magnusjjj" ***@***.***> wrote:
The revision itself is something like 4 years old.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#4103 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAB8CkWwhIa0xcffgJVQ826mSBxdAV62ks5senyAgaJpZM4PI70G>
.
|
For that, I have zero clue. The folks over at RepetierHost seemed to think it was fine (I opened a ticket there, but they have the apache license). I have just been decompiling it half arsedly, trying to decipher things like how the firmware is uploaded and some drm checks. That, however, does not translate well to comparing with a git repo :). |
I have reported the GPL violation of Slic3r by XYZprinting to the free software foundation and I have asked them to take a legal action. |
Hi. After poking around XYZWare, i found its slicer, and extracted it. They statically linked with perl, which is its own issue, but in it was some code that looked... rather like slic3r.
You can see it at:
https://www.diffchecker.com/Cxcyu4Tm
which is the xyzware version vs https://github.com/alexrj/Slic3r/blame/37105e8237272565b60550c41945b3c41b11a9d9/lib/Slic3r/Print/Object.pm
Its a four year old version they are using, only lightly hacked.
The text was updated successfully, but these errors were encountered: