Ready to be published? LXer is read by around 350,000 individuals each month, and is an excellent place for you to publish your ideas, thoughts, reviews, complaints, etc. Do you have something to say to the Linux community?
What would you do if you found someone who was violating the GNU GPL? Would you report them? I should probably tell the story first.
[This guy wants to bring about a peacful resolution to a violation of the GPL. Click the Read More Link to see what LXer says. - DC Parris]
After personal efforts have failed to bring about a resolution, I would not hesitate to contact the Free Software Foundation or GPL-Violations.org for assistance. Here's why. The Free Software Foundation and GPL-Violations.org both attempt to resolve such conflicts on amicable terms. That is, they do not immediately resort to legal threats. They discuss the problem in friendly terms first. Only as a last resort do they pull out the legal threats and action. If I recall, the FSF has only brought one case to trial. Additionally, both of these organizations may be able to help the author of the code resolve the problem himself.
The approach of most in the community is not to beat someone over the head with lawsuits, but to convince people to simply open their code. The FSF have convinced nearly all violators to open their code. GPL-Violations.org also attempts to avoid court fights, but has gotten publicity for having gone to court. The resolution process can take a fair amount of time, so developers seeking to enforce their license need to be patient. Here's hoping our reader gets the problem solved amicably.
I'm not sure I'd be all that tender with "just a kid." Quite a few "just a kids" knowingly take advantage of such mercies. For example, several of my webmaster chums are quite fed up with MySpace.com because it's a hotbed of "just a kid" pestilence. The little vermin love to hotlink images. It's futile to politely explain why that is bad and please stop it, the only thing that works is cunning scripts that detect MySpace hotlinks and replace the hotlinked images with gigantic image files that take forever to load and crash browsers. The kewl part is the images are cunning magical 1k .jpgs that load in browsers as 10k x 10k images, so the bandwidth penalty is all on the user.
I'm not sure that I even get the conversation occuring there. Does the poster think that the GNU GPL horde is going to descend on this kid with automatic weapons and grab his computer? Visions of "Hackers" dancing in their heads maybe?
I mean, c'mon, the orginazation 'll be the FSF at worst, not the BSA. They'll take pains to explain to the software author what they're doing, why it's wrong, and what their options are. Those guys love to spread their dogma.
Post a comment
A free account is needed to post. Write your comment here first: your text is kept in this browser while you sign up or log in, and is waiting for you when you come back.
Your message:
|||||
10
Markdown: **bold**, *italic*, [text](https://link), - lists, > quotes, $x^2$ for math. Formatting help
I'm not sure I'd be all that tender with "just a kid." Quite a few "just a kids" knowingly take advantage of such mercies. For example, several of my webmaster chums are quite fed up with MySpace.com because it's a hotbed of "just a kid" pestilence. The little vermin love to hotlink images. It's futile to politely explain why that is bad and please stop it, the only thing that works is cunning scripts that detect MySpace hotlinks and replace the hotlinked images with gigantic image files that take forever to load and crash browsers. The kewl part is the images are cunning magical 1k .jpgs that load in browsers as 10k x 10k images, so the bandwidth penalty is all on the user.
mwahahaaaaa