Slashdot Mirror
GPL Violators On The Prowl
ravenII writes "GPL Violations.org are looking after the GPL. Warning letters were personally handed over to companies at their CeBIT booths by Mr. Harald Welte, free software developer and founder of the gpl-violations.org project.
It seems big boys like Motorola, Acer, AOpen, Micronet, Buffalo and Trendware seem to violate GPL. Please visit the site for more information on GPL enforcements and violators."
Whats next, rude phone calls? Or how about ringing the door bell and then running away?
Sorry, but its not like Motorola is going to stop because a group they never heard of handed them a letter.
"Have you ever thought about just turning off the TV, sitting down with your kids, and hitting them?"
How do you get to prove it?
Who proves it?
Who sues at the end of the day?
Is there a legal fund set up to help out?
We don't know?
If someone is acting on "our" behalf, I think "we" should know fully what is going on before hand.
For all we know, this could be a scare tactic by MS to worry people back to their side of the fence.
Mod me down with all of your hatred and your journey towards the dark side will be complete!
It'll be good to see GPL violators being held responsible. We can start with CherryOS.
Paraphrasing:
Violators will be shot
Survivors will be shot again
how long until
If nobody is going to take these people to court then there is absolutely no reason to hand these people warning letters. They have no intention of changing their practices unless they are taken to court: they are no better than Apple or Microsoft.
I'm f#$king magic!
GPLviolations.org was served with a patent infringement suit from the BSA
If thou see a fair woman pay court to her, for thus thou wilt obtain love
end up being one big company later having all "legal department" to enforce GPL and IP issues as well as defending them?
I am harvesting funny/good quotes. Please help by putting them in your sigs
They could tell the Motorola people that their fathers were hamsters, and their mothers smelled of elderberries?
Then fart in their general direction?
Information wants to be free unless you're somebody we don't like.
Or unless you're somebody who takes code and doesn't follow the rules that the code was released under, or at least give credit where credit is due.
-Jesse
Nothing says "unprofessional job" like wrinkles in your duct tape.
Google has been doing this since they have been selling their packaged search. Kernel modifications and various other patches in their search boxes. It seems like the "OSS" community only wants to see what they want to see.
FTFA:
Since more than one year, the gpl-violations.org project tries to bring vendors who use GPL licensed software in their products into license compliance. To achieve this goal, it uses a number of measures, ranging from warning letters over public documentation of GPL violations, up to legal proceedings. In this year, the project managed to conclude more than 25 amicable agreements, two preliminary injunctions and one court order.
Sounds like some folks are paying attention to this guy.
Yes, information wants to be free, and this guy seems to be helping to keep it free, and prevent it (i.e. information-processing logic that is based on someone else's IP that released it under the GPL) from being locked away inside closed-source products. What's your problem?
Giving a legal letter to some booth lackey at a convention is NOT how you get a company's attention. Send it to the CEO, the resident agent, the law department, heck ANYONE who won't simply throw it away.
If someone says he and his monkey have nothing to hide, they almost certainly do.
They can't do anything but send letters.
They have no standing - only the copyright holders have this, and if they don't do anything then nothing will happen.
They might be able to whip slashdot into a frenzy though.. maybe that's all that it's all about?
Is all the feedback going to be negative? Everything has to start somewhere, and frankly I applaud the efforts of this guy to at least start enforcing a license that many companies do not take seriousley. If nothing else, it brings to light the face that many legit companies in fact do not care to honor the GPL, but benefit from the software that is covered by it.
sig: Playfully doing something difficult, whether useful or not
Since it looks like GPL violator's website is down, here's a mirror:f f3409b0475e/index.html
http://mirrordot.org/stories/c00f3d2fd6588c34ae25
Let me guess.
:)
1.2-300 pounds
2.black duster or trenchcoat
3.t-shirt with either Star Wars or some free 4.computer-related shirt acquired from a trade show
5.big beard. Mandatory
5.telltale fedora
6.2 cellphones on belt pocket. One might be a Treo.
7.Lifetime membership to RenFair
You don't want to mess with these guys.
Neither means one or the other. You can't include three things.
There is an umbrella organization who doesn't own the products in question but is sending letters to people it claims is infringing on the use of said products and is threatening to take legal action.
Why does this sound so familiar?
* To see some of the stories you've been missing, see my Journal *
We will bankrupt ourselves in the vain search for absolute security. -- Dwight D. Eisenhower
Before making nonsense, worthless comment, wait till the site gets unslashdotted and READ it. Most of you question might be answered there. Many other questions being asked are just stupid or have obvious answers. Like, how can you prove that the violaters are indeed using GPLed software. Many of the violaters are openly using GPLed software. Like using the Linux kernel. And then some question are very silly/small minded. Please.
Well, if you WERE a developer, you could get off your duff & do something about it, eh? There are these "little-known" BSD operating systems under your "less-restrictive" licenses. Check them out sometime when you're done with the C in 21 Days book.
Yup... every time we use something (we develop on Linux) we check the license out. If it's GPL, we either write our own or find something BSD licensed. In the past, libraries that I have had to write from scratch to achieve GPL code functionality, I've released under BSD.
All those who claim the GPL isn't viral have no idea and/or have never tried to use it on anything that isn't destined to be GPL.
Hense the BSD license.
... for him to serve one to SCO.
I'm not wrong. You haven't thought about it hard enough.
"OSS" already has one - see the BSD license.
Good thing you're not. We don't need any more ignorant developers.
Those like me who've read and understand the license, use it to make sure the programs we distribute are not redistributed without source. We *want* that restriction. If you don't like that restriction, feel free to not use the code and go the hell away.
But that's exactly my point, don't you see? That's the contradiction. You guys want everybody else to play by your rules when it comes to computer programs (those rules being fairly complex and confusing, from my point of view), but you have absolutely no desire to play by other people's rules when it comes to things like music and movies.
And those rules, by contrast, are incredibly simple: Pay for what you take, and don't give people copies. But any time somebody like the RIAA or the MPAA try to enforce those rules, you guys go positively batshit over it.
That's the contradiction. That's what I'm trying to point out. Hopefully somebody will read this and go, "Huh. I don't know if I agree, but he's got a fair point."
How can they tell that a binary has GPL code in it? I mean, do they use strings or something? If that's it, then it's pretty easy to defeat their GPL detection. Looking at the assembly isn't telling because some simple algorithms will be written the same and produce similar assembly, and optimizations will mangle all that anyway.
It'll take just one serious error/mallicious report/misidentification to be cause for libel and bring a suit that takes this site right out of commission.
This is good. I wrote in a previous comment that I thought the GPL had no teeth, if the FSF where the only people looking into GPL violations, because they don't really do a Hell of a lot about violators (sorry, it's a fact), and most FOSS developers don't have the resources to seek a legal solution against violators. None other than Bruce Perens took me to task for this opinion, but I still stand by it: The GPL might as well be a blank sheet of paper for most FOSS developers, what do they intend on doing when some Taiwanese hardware manufacturer embeds their code? Spit a lot? It takes a lot of money, money that few of us have.
"Who are in control, they are not in control of anything - they don't even control themselves!" - Glen Beck
benifits nobody
Guess what, most companies don't want to give back source code, and its apperant by how many companies are violating the GPL. Having the restrictions the GPL does, it causes the companies to give back, which helps the community. Take PearPC for example. CherryOS has (obviously) ripped the code from them, and claimed that they wrote it all (in a few months or something, by one man, with no programming experience, which is bullshit) Nowadays, PearPC doesn't get many updates, because everytime they do, CherryOS does too. It's dampened the whole thing for the developers. If CherryOS was forced to obey theGPL (which they will eventually, some organization like the EFF or something will take them to court) then this wouldn't happen. Now tell me how limiting restrictions would help this case.
i personally think the GPL is the best license currently available (except maybe the apache type licenses because of their patent clauses).
the spirit of the gpl is that the code stays open. if you want people to write code for you to sell, use bsd software.
I think we all remember the MPlayer and libmad case, where KISS stole GPL code, and used it in their DVD recoarders and DVD players.
Wouldn't this be a good place to start, as KISS doesn't give a f**k about the GPL?
If a company does not want to show their source code, they should use a BSD (or similar) licensed software or quite simply write their own. Some manufacturers of wireless access points would not have been on the recieving end of the GPL stick if they'd used something like OpenBSD with their own drivers.
Well, the parent will almost certainly be modded down as a troll, but I agree.
/.ers often complain about big corporations using, to try to force the entire industry to do things the FSF's way. This kind of machiavellian restrictive licensing is what we should be trying to get away from.
The GPL is far too insular. When you release your code under the GPL you do it only for the good of other GPL users. On the other hand, when you release your code under a BSD-like license, you're doing it for the good of the entire computing field.
The GPL uses the exact same predatory licensing practices, that
These people should be the next target. Maybe they'll be forced to GPL all that work the Pakistani company did for them.
I have seen violations at places like Iomega for there NAS drives. It was one of the issues that I brought up durring beta testing. And they said it wasn't an issue that they were using Linux with out releasing the source because their firmware developer for the embeded Linux told them it wasn't a problem and they weren't going to release the source. This little product only costed about 200.00 for network storage, and it has the potential to hit the market like the Linksys WRT54G did with custom firmware.
If anybody is interested in pursing Iomega about this let me know because I will sign a petition.
That's a blatant misrepresentation of his point - a straw man. Free-as-in-GPL doesn't mean "do not touch".
The GPL attempts to ensure that modifications to licensed, distributed, source code remain available to users. Whether that is a worthwhile cause is a matter of opinion; personally, I believe that for community OSS projects, the requirement for companies making modified versions to also make source available is generally good for the project.
Yeah, the freedom to use the code however you want, as long as you let others do the same.
The arbitrary restrictions are FAR from arbitrary.
It's designed to make sure that someone doesn't take your hard work and tweak it as such to lock you out. The restrictions are for your protection.
How many people run Darwin? All the BSD license did is let apple steal BSD and call it OSX. How much does apple contribute back? Not enough, considering their record profits this year. Would any of that been possible without OSX?
My company and I have looked at open source opportunities before, but it's precisely for this reason that we kept away from OS - even though we felt we could use it and contribute to it... Can somebody please explain this to me, or provide me with a clear link?
http://jcsnippets.atspace.com/ - a collection of Java & C# snippets
I wonder if some company may eventually say:
"We won't sue you for infringing on our patents if you don't sue us for infringing on the GPL"
Also, would that even be legal to accept an agreement like that? Nevermind that it would probably be a bad thing for OSS.
It is. And people who don't agree with the GPL are free to write their own code and license it however they like.
One CPU cycle wasted on digital restrictions management is ONE TOO MANY.
This opens up another front on the OSS battle so to speak. While some posters here question the value of informing companies that they may be in violation of the GPL and claim that they can simply ignore it, companies that ignore such warnings do so at their own peril. Why? Because from a legal standpoint they can't be sure who will hit them with a suit or when. There are all sorts of questions about who would have legal standing to bring a suit, and this itself would vary from state to state and country to country. If I'm a company bent on violating the GPL, defending that could be difficult especially if a GPL backing company like IBM or Novell decides it's in their best interests to get involved and bankrolls the lawsuit.
Given this, I think few companies will intentionally violate the GPL. So I think that most smart companies if informed of a problem, will probably rectify it one way or another rather than risk an uncertain threat of liability. Certainly any high profile organization with a smart legal counsel would. The not so smart ones are another story!
To the making of books there is no end, so let's get started
From my (albeit limited) understanding of the GPL, it just wants you to give credit to the original authors of the code. When someone downloads a song, they are not in any way claiming that they wrote the song. There's the difference betwen the two.
"It is better to risk sparing a guilty person than to condemn an innocent one." - Voltaire
without ever really stopping to think that that's not really what "free" means at all.
Then think about this: there at least two mainly known definitions of free: positive freedom and negative freedom.
The GPL follows the first one. Libertarians (i.e.e right wing people) follow the second. That's why you don't understand the mismatch, because there isn't one meaning for freedom.
And as positive > negative, *I* would say that GPL has more freedom than BSD.
Singularity: a belief in the "God" idea with the "demiurge" relation inverted.
I'll second the other poster who said, 'Good thing you aren't a developer.' See, development takes work; lots of it, in fact. Writing a program doat does anything more than put 'Hello, world!' on the screen takes a measure of effort that you, as a non-developer, can't really comprehend.
See, writing programs, especially *good* programs, isn't easy. It takes skill, patience, and experience, as well as a certain type of mind that isn't very common. And, before you tell me that even your seventy-two year old mother knows how to program, ask yourself this -- does she know what an eigenvector is? How about maxtrix transforms? Relational algebra? Multivariable calculus?
Why are these important? Because programming requires a high level of mathematical ability, at least if you want to have any understanding of why you are writing code a certain way.
So, all of this together makes a programmer, and people who do this sort of thing pour hours into their work. This is something they have created, and honestly, they should, and do, have the final word over what happens to their works. Some people are generous enough to release their works under a license like the GPL, which enables anyone else to use the program which the programmer has created, but with the caveat that the program can't be stolen and sold.
As a programmer, I'm happy the GPL exists, because there are a lot of ideas I've had for 'open-source' programs, and while I am happy to write them, I don't want to spend months coding, just so that some asshat can try to charge money for something I, as the creator of that thing, have released for free.
Finally, information doesn't 'want' anything -- it's an intangible concept, like 'santa claus' or 'income tax reform'. People want information to be free, and while that's all and good, there are far too many people demanding free information, and far too few people willing to work to provide it.
--
I Hit the Karma Cap, and All I Got Was This Lousy
"You guys?"
What, everyone who writes GPLed software is a music pirate?
Unlike all those Windows users who, undoubtedly, have never broken IP laws by, say, borrowing somebody's copy of Office or downloading a Dreamweaver zipfile?
Dear me.
Too bad Hyperion Entertainment didn't dare show up at CeBIT. Oh well, they'll get their C&D letters by registered mail instead, but it's not as entertaining when the humiliation doesn't take place in public right off the bat.
Bullshit. The GPL only prohibits taking open software, closing it and selling it as your own with no source available. You are free to use GPL libraries in your proprietary code without releasing your code, and to sell your closed code. Try again.
"Gold still represents the ultimate form of payment in the world." - Alan Greenspan, 1999
Good thing you're not. We don't need any more ignorant developers.
Its not about passing around source code. GPL forces me to make any code that's linked with it to be GPL as well. Even plugins written for a program, if GPL'ed require the entire program to be GPL'ed. That's a totally unnecessary condition. I'd rather choose BSD or CPL which ask that you pass around source code but aren't thoughtlessly viral.
Yes, but freedom is a two-way thing.
For example, if you were free to run all over anywhere you want on your dirt bike, including my back garden, then you would have removed my freedom to enjoy my back garden in peace.
In any society where resources are contested, granting one freedom to one person may remove a freedom from another.
The GPL trys to addresse this in a way which preserves the most freedom. You are granted the right to modify and redistribute anything I do, as long as you also redistribute the changes you made, so that I and others can benefit in turn. Your additional freedom comes at the price of not restricting the freedom of others.
Alternatively, here is another way of looking at it. Information wants to be free, but copyright laws are provided which allow it to be locked up. The GPL uses these laws against themselves, to create information which can never be locked up.
The RIAA and MPAA aren't authors and aren't doing anything to benefit authors. They're not really even doing anything to benefit themselves. However, it's their grave to dig.
The RIAA and MPAA shill for the companies that VICTIMIZE artists.
The notion that RIAA and MPAA help actual artists is just lame corporate propaganda.
A Pirate and a Puritan look the same on a balance sheet.
You're making an entirely unwarranted assumption: That GPL developers routinely infringe others' copyrights. Most developers I know are very respectful of any copyrights on a work.
I suspect the fraction of free software developers who infringe many copyrights is lower than the fraction of general internet users who infringe many copyrights, just because the former tend to be more familiar with the law and what it takes to produce a copyrightable work.
Don't confuse GPL developers with file traders just because they both read Slashdot.
Seems like the poster is a GPL violator himself. He found the easiest way of fighting back the threat: slashdotting the site.
No karma wore...
I know this *is* slashdot and all, but according to the article, the group last year reached 25 amicable conclusions, 2 preliminary injunctions, and 1 court order. That would lead most *readers* of the article to conclude that in fact they do take people to court. That is the usual way that you get injunctions and court orders.
Often companies start with warning letters too.
Avoid Missing Ball for High Score
does she know what an eigenvector is? How about maxtrix transforms? Relational algebra? Multivariable calculus?
Why are these important? Because programming requires a high level of mathematical ability, at least if you want to have any understanding of why you are writing code a certain way.
While I agree with your general tone, what non-scientific applications out there use an eigenvector? Multivariable calc? A large part of programming is just taking A, transforming it, and getting B. What you mention will help you solve math problems, but that's a small minority of programming.
I've seen allot of arguments for and against the GPL. I don't really take sides either way, but here are my general observations about it.
/any/ way, code that has a GPL license, that you must also release your code under the GPL. It's my understanding that this is not so. If you modify code covered under the GPL, then you have to release your modifications. If you use code covered under the GPL, then you have to release copies of that source. If you create /new/ code, but it depends on a GPL item, then you can release your code under whatever license you see fit - open or closed source.
Allot of people have the common mis-conception that just because software is released as being free, that they can do what ever they want with it. The truth is, if that were the case, then all we would have is mass chaos. This would lead to (more) code stealing and mis-use of IP.
Another mis-conception that I see, is that people believe if your code extends, in
Anyway, I've forgotten my original point here, so I'll just say this:
We can't have Free/Open Source without rules; That would just be Chaotic/Open Source. And if you violate the GPL, you deserve to be sued for. It's akin to breaking a Constitutional Amendment. I mean really....
http://www.accelerateglobalwarming.com
Great, the system works. When I release something under the GPL I never intended for you, nor any other non-GPL developer, to be able to use my work. I am being deliberatly selfish, if you wish. At the end of the day, I am only interested in sharing with others who will also share their work.
RTFLFAQ and then maybe you'll have enough sense that I'll want to argue with you.
Apple didn't bother with a scary letter.
Apple has threatened to invade Taiwan if the self-governed island moves toward formal independence from Apple's dominance in the mp3 player market. The threat has become more real to many in Taiwan as Apple prepares to enact an anti-secession law that some analysts fear may provide Apple with a license to attack the island.
That's what LGPL is for.
If Oracle and Electronic Arts can grok this than so can anyone else.
A Pirate and a Puritan look the same on a balance sheet.
Iomega stock tanking...rumor on the street is that nberardi might sign a petition against them.
Well, you're just a bit of a wanker then, really, aren't you.
Yes, it's about the Freedom of the code. The code is Free and the developer intends for it to remain Free. It isn't about your freedom as a developer.
If you don't want to redistribute your code under the GPL, find some non-GPL code to base your work on. No one is forcing you to use that GPL licensed library, it's your choice.
...outsourcing this to SCO?
(...) You are free to use GPL libraries in your proprietary code without releasing your code, and to sell your closed code. Try again.
LGPL libraries you mean.
If I were to sell copies of Star Trek DVDs that I made myself, Paramount would be all over me for violating their copyright. I have no contract with Paramount. That's the point - I have NO right to sell someone else's copyrighted material without permission. You must have permission to distribute ('publish') someone else's copyrighted material.
That permission could be given by a contract. Or it could be given by a license, such as the GPL. When the author places his work under the GPL, he grants permission to copy to those who adhere to the terms of the GPL. If someone doesn't follow the terms, then they DON'T have permission to distribute the copyrighted materials. It's a simple case of copyright infringement.
The GPL is far simpler than the usual EULA. The GPL makes no restriction on use, but most EULAs do. Most EULAs prohibit copying, but the GPL encourages it. The GPL is a license granting you permissions that you wouldn't otherwise have under copyright law. You don't have to accept the GPL, you just fall back on standard copyright law if you don't. No contract is needed.
Company A starts using some 'free' (they believe) source code in their product, mistakenly unaware of the subtleties of the GPL ... then they get a threatening letter. Yup, that's going to encourage the use of OSS in the commercial world!
I just read the LGPL and it still seems too restrictive. This is from the POV of a one-man part-time developer. I have steered away from any GPL stuff just because it's a can of worms if at any point you think your app might become the basis of something commercial.
I'm not wrong. You haven't thought about it hard enough.
Do we really want all these violators on the prowl? Seems like the article is about people on the prowl for GPL violators, not the other way around.
Critical reading is a lost skill in this country.
Those like me who've read and understand the license, use it to make sure the MUSIC we distribute are not redistributed without PERMISSIONe. We *want* that restriction. If you don't like that restriction, feel free to not use the MUSIC and go the hell away.
3 words,
1 hypocrite
haha says the man who has has a link to a hexeditor, thats real software innovation, perhaps you would like to make a text editor next ?
Before you call "bullshit", you might want to check your facts: the GPL in fact does not allow this (read par. 2). You're probably confused with the LGPL, which does.
Usually, if there's a demand, a supply manifests itself. it's automagic, really.
GPL Violations.org has successfully been slashdotted. Congratulations! We are a force to be reckoned with.
These aren't the sigs you're looking for.
Because programming requires a high level of mathematical ability, at least if you want to have any understanding of why you are writing code a certain way.
Programming requires logic, not math.
Eigen values, matrices... only applicable if you're doing an engineering software. The point of taking all that math in Comp Sci is to learn problem solving logic, how to approach a problem. There is no calculus/Eigen/matrices in presentation (UI), persistence (db, XML, flat file), or unless specific cases - business logic.
Some people are generous enough to release their works under a license like the GPL, which enables anyone else to use the program which the programmer has created, but with the caveat that the program can't be stolen and sold.
True generosity is using the BSD license - there's nothing generous about trapping future development by license.
"From my (albeit limited) understanding of the GPL, it just wants you to give credit to the original authors of the code. When someone downloads a song, they are not in any way claiming that they wrote the song. There's the difference betwen the two."
The forms of art are inherently different. The average pirate doesn't incorporate a downloaded song into their own work without credit, and the average GPL violator doesn't listen to the code. The implicit rationale here is "I follow this certain set of rules for one piece of media, and if another medium has different rules, then they're wrong and can be ignored." Different media have different uses, and thus, sets of rules.
In situations like this, the golden rule still applies: treat others as you would like to be treated. If a software developer -- big or small -- wants you to honor their wishes and respect their rights, do so. Likewise, if a musician -- or even a record company -- wants you to respect their wishes and respect their rights, you should as well. Because some day -- whether you're a musician or a programmer or a painter or an author -- it may be your own rights that somebody has taken the libery of ignoring.
Sitting in my day care, the art is decopainted.
Too subtle. (sad but true)
"Pay for what you take...."
"Take"? It's 'copy', not 'take', one source of the confusion.
Brilliant. I wish I had mod points to give.
I see that your point was a complete fly-by for some folks -- which, I think, served to prove your point even more strongly.
Sitting in my day care, the art is decopainted.
What, everyone who writes GPLed software is a music pirate?
Of course not. Everyone who posts on Slashdot is a music pirate.
Are you new around here?
Many programming applications *are* scientific, and eigenvectors are very useful when it comes to linear systems of differential equations, which are used extensively in engineering. (Note: I'm assuming you know this, of course, but that many other readers don't).
There is also a lot of programming which involves physics in some form or another, or at the very least differing rates of change -- multivariable calc is important for writing games, financial anaylsis tools, and more.
Yes, there are a lot of programs on the 'hello world' level, and equally many more that don't ever descend into the gritty world of math, but even so, the designers of these programs would do well to have a basic understanding of the math behind the tools they use. How, otherwise, can a coder know what 'going quadratic' means, and how to avoid it, in terms of a search algorithm? What about having an understanding of inductive logic, so that they can write routines iteratively, rather than recursively? Would you trust an encryption scheme designed by someone with no experience in number theory?
I will admit, I'm biased -- I'm a math-and-science guy, with an emphasis on math, but my original point stands. Namely, that without the requisite background knowledge in mathematics, writing good code on these big calculating machines we call 'computers' is nominally an accident. Ergo, a Good Programmer needs this skill, and is much more rare than Some Guy Who Took Visual Basic Once In Junior College.
--
I Hit the Karma Cap, and All I Got Was This Lousy
This is one of the instances in which geeks are naive to the weaselly, successful ways of lawyers and politicians. The geek instinct is to first survey the complete territory: "how many violations can we grep across the Net?" The lawyer or politician would first identify a few highly vulnerable violators, and take them out, before hinting that perhaps "everyone does it". They'd build momentum, gaining mindshare for the idea that "you better not do it". By the time they did their "complete survey", they'd have already shrunk that population through intimidation. Before creating more, by promoting the idea that it's widespread.
Geeks have to start thinking more about "social impedence" feedback problems. Maybe all the recent work by programmers in modelling social networks, filled with live normals, will create some conventional Usenet-style wisdom. We've got to learn through data what the accomplished weasels seem to know by instinct: defining the scale of the problem prematurely can increase its scale. Computers are sitting ducks - solving people problems requires a much more dynamic approach.
--
make install -not war
It's nice to know that someone is looking after the GPL.
/. knows, copyright violators are bad people who need to be punished. Right?
/dev/null.
After all, as everyone here on
Now, everyone go and enjoy your vast collection of pirated MP3's and DVD's you downloaded last month via Bittorrent. You can all nod your heads in a knowing, philosophical manner as you examine your hypocrisy and double standards.
Attempts to justify your copyright infringement activities in the name of "sticking it to the man" or other variations of socio-economic class warfare will be automatically redirected to
In the end they will lay their freedom at our feet and say to us, Make us your slaves, but feed us. - Fyodor Dostoyevsky
LOL! Funny AND Insightful.
Too bad we have retarded moderators here.
sveasoft (gpl-violations is slashdotted, so maybe they are listed)
Maybe if the law didn't mandate things like statutory damages in the order of thousands of dollars per infringement people wouldn't be quite so critical of RIAA's tactics? When I can potentially be sued for 20 counts of copyright infringement for sharing 20 songs with a combined retail value of maybe $20 and be potentially on the hook for a minimum of $15,000 and a maximum of $3,000,000 (!) in damages it doesn't take very long for us mere peons to cry, "FOUL!"
So, is this GPL-violator guy asking for/threatening thousands of dollars in damages each time he sends out a letter?
"You guys?"
What, everyone who writes GPLed software is a music pirate?
Don't be an ass. This is a pretty fair understanding of the prevailing attitude on Slashdot.
How many articles and posts are there decrying any action of the MPAA and/or RIAA to try and enforce their license terms (however hackneyed or backwards we may personally believe them to be)?
How many articles are there on "open source is good!" "GPL is good!" "More things should be released under the GPL!"?
See the point he was making?
The situation with the GPL is precisely analogous to the situation with downloaded music. (Most) music copyright owners expect a payment of some kind in exchange for their providing you with music. Creators of GPL code also expect payment. The only difference is that the music owners expect payment in the form of money, while GPL code owners expect payment in the form of more GPL code. In both cases, you legally have no right to distribute or use the music or code unless you make the appropriate payment - it's just that the terms of payment are different. In both cases, you have the choice not to accept the terms imposed by the owner of the work, by choosing not to use their work (and finding e.g. an independent artist who allows free downloads, or software that is distributed under a BSD or MIT license).
First, the math thing was more of a side-point, not a main point.
Second, you don't trap future development! The GPL mandates that source code must be made available. Licenses like the GPL specifically allow one to make modifications to the code as they wish, provided that any redistribution includes those changes. This encourages development!
What the GPL *does* do, is prevent other people, the freeloaders, from taking all that work, rebranding it, and selling it at a profit. It keeps the rights to the code squarely where they belong -- in the hands of the developers who funded the work and provided the labor, not in the hands of unscrupulous businessmen who are out to make a quick buck on the generousity of others.
--
I Hit the Karma Cap, and All I Got Was This Lousy
Then people should be bitching about the magnitude of penalty and not the fact that there are indeed penalties.
Totally agree. You hit the nail right on the head. -ron
You can use GPL libraries in your proprietary code and sell your closed code, provided your distributed binary is not a derivative work of those libraries.
The LGPL allows you to do so even if your distributed binary IS a derivative work.
Whether something is or is not a derivative work is a subject for the law and not something which the license can set out (because if it's not a derivative work, the license doesn't apply).
You are free to use GPL libraries in your proprietary code without releasing your code, and to sell your closed code. Try again.
Bzzzzt. Try again yourself.
You are free to use LGPL libraries in your proprietary code without releasing your code, and to sell your closed code.
Your argument only works partly. What I mean is that your argument only works the throw those arguments back in the faces of those who use them against corporations and organizations like the RIAA. You aren't really disagreeing with the idea that intellectual property needs protecting, but you are disagreeing with those who dislike big businesses protecting their intellectual property. You know as well as I do that nobody is going to enforce the GPL against college students or grandma, and you know that this action to protect GPL'd software isn't for simple "copy-and-paste theft" but rather huge portions making up the majority of the software these companies are using.
It will be interesting to see how this plays out. The GPL and BSD licenses will become equivalents if the GPL isn't protected sufficiently.
Yes, but that supply usually manifests itself because the people doing the supplying see some kind of benefit in meeting the demand. Usually because they get financially compensated. Sometimes for other reasons. But always because they get some beneift from it. Whether or not there will be an "automagic" supply of free information depends a lot on what the incentives are for suppliers of that information.
And YOU miss the point entirely by holding up your personal standard of what's "right" and saying that, clearly, that's what the courts should enforce, regardless of the law in question.
I'm sorry, but an MP3 of a Britney Spears song hardly qualifies as "information." It is (at least by the legal definition) a work of art. And it is therefore protected by copyright.
The author of a copyrighted work can choose to publish it or not. That's THEIR decision--not YOURS. IF they chose to share or publish it, they have the legal right to impose terms on that sharing. If you don't like the terms, you don't have to accept them. But then you don't get to see/hear/use that person's creation.
But to somehow claim that YOU PERSONALLY have some kind of "right" to take whatever you chose from whoever you chose whether they want you to or not under some "principle" of information freedom, frankly, offends me, and should offend anyone who has ever created something, be it art, music, or software. I made this--it's mine. It's not yours. If I'm so inclined, I am willing to let you share it if you agree to some rules. To say you can ignore any rules you don't agree with is arrogant beyond measure.
So, what, you want developers who AREN'T wary around GPL'd code, so that they just blatantly use it without paying attention to anything? Thereby, exponentially increasing the chance someone is going to use your code without respect to the license you set forth?
What are you, a fucking idiot?
The core of the problem is googlebot itself. Since it is distinguished from ordinary user by it's own identification and behavioral patterns, it disqualifies itself from Turing test in comparision with ordinary user. So it is easy to be spoofed at.
There may be usefull another layer for googlebot, which checks for authenticity of links/redirections by mimicking human behavior, disguised as some widely used browser. There is no need to check everything, that would create a detectable pattern again, but just a heuristicaly selected subset of the web site.
There you are, staring at me again.
I must have missed something. I remember reading somewhere in the GPL license that you need to distribute the source code along with the program... I do not recall, however, that the program and its source should be free (as in costless). Nor do I recall that the source code should be readily released to the community.
Correct me if I'm wrong, but I believe are all the following are valid:
- Under the GPL, I can take your code, modify it for my usage, and never release the end result to you or anybody else. Your code is released under the GPL, which sets limits to the way I distribute work based on yours. Not to the way I use it.
- Under the GPL, I can take your code and sell it to my customers, as long as I release your code to my customers. Moreover, I can sell them the upgrades and bug corrections that you release. Sure, some customers will become aware of this and will download your code for free, since it is there to grab. But most won't, because they won't be aware it exists or where to download it in the first place.
- Under the GPL, I can take your code, modify it, and sell it to my customers, as long as I release the resulting code to my customers. Arguably, they must release their source code if they build on top of it and decide to distribute the finished product, since mine and yours are released under the GPL. But they also have the right to never release the work I did to you or to anybody else. And most will, especially if the resulting code is specific to their business processes.
Actually, thats just what the GNU people think. Its not nessecarly the way it is.
:)
Honnestly, the GPL just giving you limited rights held by the copyright holder. However, the interface with that program is NOT copyrightable and so you are free to interface with it without needing to GPL your own code (thier flawed analysis be damned).
As long as you do not distribute the GPLed code with your own, there is nothing they can do.
.. assuming that there is willful infringement in every case, and that the companies involved will not comply with the letters. This is a pretty big assumption.
I guess you flunked out of charm school, and I guess you've never heard of the old adage "you can catch more flies with honey than with vinegar", so I'll spell it out for you here:
Making threats against a neutral party will usually make them a hostile party.
If they are neutral and you threaten them, you're damaging your own cause, because you'll be souring them on OSS and the GPL.
If they're hostile and you threaten them, then you don't gain anything.
If they're neutral and you ask them nicely, they just might comply.
If they're hostile and you ask them nicely, you haven't lost anything.
By sending the letters, the companies who are doing this understand that we're not all rabid loser anti-corporate zealots. Making threats will do nothing more than sour them on the GPL and open source in general.
I'm even pretty sure there are some GPL violators amongst the companies that fight against OSS (or at least trying to prove how bad and communist OSS is)...
"Honesty is such a lonely word..."
This one, that is - I wish I had mod points!
This diverges slightly from the file-trading theme here, but to extend your point: Many of us who use free software started to do so in part because we didn't have the means to legally obtain and use much of the software we used previously. Some people have moved to free software because they can't or don't want (for various reasons) to pay Microsoft, etc. to use their software, but also don't think that violating copyright is a moral thing to do either.
Online citizen journalism from the inner city: The View From The Ground
>You can use GPL libraries in your proprietary code and sell your closed code, provided your distributed binary is not a derivative work of those libraries.
What's the point of having gpl libraries in your code if you're not using them? AFAIK, linking to them does create a derivitave work, just as adding a few verses to a song would.
-- Give me ambiguity or give me something else!
As to playing by rules, by all means. When I write a piece of software, the rules say I have the copyright to it (or my workplace has). I kindly allow you to run and copy that program as much as you please. I do not immediately allow you to take the source code and put in your own program, but that should only be a concern to someone who writes programs. If you want to copy parts of my code into your own program, I allow you to do so under some conditions, which you may or may not find confusing, but which are actually quite simple: You have to release the combined work under the same license. As long as my program contains only my own code, I can sell it under alternative licenses, and make big money on it. As soon as I have borrowed someone else's GPL'd code in it, I will either have to make an explicit agreement with the owner of that code, or release the whole thing under GPL.
As to MPAA, RIAA, and their ilk, I do not disrespect them because they wish to stop illegal copying. I disrespect them for their clumsy and heavyhanded tactics, exaggerated claims, silly campaigns, and their inability to see how the times are changing. That is reason enough for me.
I've written GPLed code. I've protested what the RIAA and MPAA have done. I'll tell you why on both counts.
I write GPLed code as a step towards making someone else's life better. I like writing software, the code I GPL I would be writing anyway, and making it GPL doesn't harm me in the least. I make it GPL instead of BSD or public domain because I want to see the amount of freely available software increase as rapidly as possible, and I think the GPL promotes that.
Now, what's wrong with the RIAA and MPAA trying to enforce their copyright? If it were that simple, nothing. But I'll tell you what... these guys have successfully lobbied to take the vast majority of what would be in the public domain, a part of common culture expected to be commonly available, and made it their private property. Companies like Disney are founded on public domain material - Grimm's Fairy Tales, Pinnochio, Sleeping Beauty, you name it. They didn't pay a dime for those stories, stories that someone else wrote and the culture validated, because those stories had passed into the public domain.
Since then, Disney and other MPAA companies have successfully lobbied a 28 year copyright period into *120 years*. They go back and lobby for another 20 years every time their oldest works, the ones they built on public domain material, are about to fall out of copyright. This is no less than organized crime - bribes given to lawmakers to steal our culture from us. That's item 1.
The MPAA and RIAA are working very hard to make general computing illegal. A general computer is fantastically useful - it has transformed the lives of billions. Open systems based on simple principles can yield unbounded potential. The internet is a new testament to that fact, if the prior success of general computers weren't enough. But the MPAA and RIAA believe that general computing is a danger to their revenue, since it allows copying without flaw any information you have available to you. So the MPAA and RIAA, whose members' revenue is a fraction of that of the computing industry, but who control access to public attention and famous figures, lobby governments continually to make computers without DRM illegal. Have no doubts about it, mandatory DRM *will* cripple your computer. It *will* end up in a place where all of your personal information is available to "reputable" companies, where use of programs written by "unreputable" companies will be illegal to run, and where government sanctioned monopolies will charge exorbitant fees to vendors so they can release programs that actually run under DRM. You will see programs that cost money each time you use them, and more money to use them in more sophisticated ways. And using them in innovative ways that the creator never thought of? This will be simple impossible. This is the future if mandatory DRM is allowed to pass. That's item 2.
Finally, the penalties for copying the mass marketed tripe they produce are ludicrous. Charging 10 times the value of the illegally copied goods might be reasonable, both as a penalty and to account for the offenders that you can't catch. But the penalties are 100s or 1000s of times the cost to buy legal copies in stores. The penalties are totally disproportionate to the offense. That's item 3, minor as it may be in comparison to the other two.
That's why some of us get outraged when organized criminals call us communists for happily giving away our works, and name people who copy material that should have been part of the common culture after brigands of the sea who rape, murder and steal.
Yes, and the license terms are different. His point was that, in both cases, their are license terms being violated against the wishes of the licensor.
In the case of GPL'ed software, sharing is expressly permitted by the license. However, one term of the license agreement is that "if you take it, you muse share your derived works." So, downloading and using is fine, assuming you share what you make with it.
In the case of recoded music, sharing is expressly prohibited by the license. You do NOT have a license to copy the music, or share the music with others, so doing so is a violation.
The Supreme Court put some restrictions on how that license can be enforced with the "fair use" concept in the Betamax case. But they did NOT say that "copying, sharing, etc., in all it's forms is OK," and certainly sharing with strangers goes well beyond any "fair use" concept in the context of the Betamax case.
Harald Welte did a very interesting presentation about GPL Enforcement in Germany at FOSDEM two weeks ago.
He is one of the few, with Theo de Raadt, who really fight against proprietary software. See this Kerneltrap.org feature about OpenBSD fight against closed source drivers for wireless.
http://news.bbc.co.uk/2/hi/south_asia/4340497.stm
where did my sig go? where's my sig at?
...the math thing was more of a side-point, not a main point.
...you don't trap future development! The GPL mandates that source code must be made available. ...This encourages development!
That's nice, but the rest of the programmers/developers out there know you're just myopic.
Mandate: An authoritative command or instruction.
I am unable to make additions and release under the license of my choice - that is a confinement because I'm considered automatically guilty.
hiroMyopic++
That pretty much sums it up.
But it only takes one of your customers to download the code and make it freely available.
But that's exactly my point, don't you see? That's the contradiction. You guys want everybody else to play by your rules when it comes to computer programs (those rules being fairly complex and confusing, from my point of view), but you have absolutely no desire to play by other people's rules when it comes to things like music and movies.
And those rules, by contrast, are incredibly simple: Pay for what you take, and don't give people copies. But any time somebody like the RIAA or the MPAA try to enforce those rules, you guys go positively batshit over it.
That's the contradiction. That's what I'm trying to point out. Hopefully somebody will read this and go, "Huh. I don't know if I agree, but he's got a fair point."
When I take one of these songs I've downloaded, turn it into my own product, rerelease it and profit from it then we can talk...otherwise you are over simplifying the issue to make a flawed analogy...remember..just cause you CAN make some analogy, does not mean it's valid.
What are these "facts" you speak of? Don't cloud the issue with the idea that people should ACTUALLY read the GPL, and maybe make an attempt to ACTUALLY understand it. Who are you?
"Who are in control, they are not in control of anything - they don't even control themselves!" - Glen Beck
But enforced 'freedom' isn't freedom. Maybe it's a level playing field, and maybe it's a good thing, but it's not 'free' and it's not 'open.'
Vintage computer games and RPG books available. Email me if you're interested.
One thing threatening Open Source today--piracy.
As we have already seen, the GPL is under attack from evil forces known as "pirates." These shadowy folk silently steal source code and violate the GPL, infringing on the rights of GPL authors. They are nothing more than thieves getting a free ride off the work of others, and I for one am disgusted at the idea of it. As you can see in the previous article, clearly Slashdot is also sickened by the idea of copyright infringement and piracy.
Some have even called for a lawsuit against these pirate thieves. Suing individual infringers has always been a position that Slashdot and its readership has supported, so it's only fair that the original GPL authors protect their rights and safeguard their material from being stolen in the future. I think we should all support any lawsuits against these infringers to protect the rights of GPL authors everywhere.
I appluad Slashdot and its readers for always taking a proactive stance against piracy and copyright infringement in general, and I would like to join the cause against this "source code theft." Piracy is a major threat facing OSS today.
"You're making an entirely unwarranted assumption: That GPL developers routinely infringe others' copyrights. Most developers I know are very respectful of any copyrights on a work."
You are most likely right. I would imagine that serious developers who've put their heart and soul into brilliantly crafted code will often understand that musicians (and anybody else who chooses an art form other than software development) also tend to work hard and don't want their rights violated, either.
I think the bulk of the issue is Slashdotters who are aware of the rules regarding the GPL and other art forms, use the GPL as a convenient rationalization for music piracy, or piracy of non-GPL software. If not that, then they compare the GPL license with a typical license for, say, music or films, and believe one to be more equal than the other, while ignoring the fact that different media tend to have different uses, and thus different rules.
Sitting in my day care, the art is decopainted.
One thing threatening Open Source today--piracy.
As we have already seen, the GPL is under attack from evil forces known as "pirates." These shadowy folk silently steal source code and violate the GPL, infringing on the rights of GPL authors. They are nothing more than thieves getting a free ride off the work of others, and I for one am disgusted at the idea of it. As you can see in the previous article, clearly Slashdot is also sickened by the idea of copyright infringement and piracy.
Some have even called for a lawsuit against these pirate thieves. Suing individual infringers has always been a position that Slashdot and its readership has supported, so it's only fair that the original GPL authors protect their rights and safeguard their material from being stolen in the future. I think we should all support any lawsuits against these infringers to protect the rights of GPL authors everywhere.
I appluad Slashdot and its readers for always taking a proactive stance against piracy and copyright infringement in general, and I would like to join the cause against this "source code theft." Piracy is a major threat facing OSS today.
And many OSS companies aren't the authors of the software they sell and aren't doing anything to benefit the real authors.
All of this is irrelevant, however. The question is whether you believe in IP or you don't. If you don't you shouldn't embrace the GPL or the RIAA.
Mirror here.
Kim Jong Il: Hans Bwix? Oh no!... Oh hewwo Hans, gweat to see you again!
Hans Blix: Mr. Il, I was supposed to be allowed to inspect your palace, but your guards won't let me into certain areas.
Kim Jong Il: Hans Hans Hans, we've been thwew this a dozen times. I don't have any weapons mass destwuction, okay Hans?
Hans Blix: Then let me look around, so I can ease the UN's collective mind. I'm sorry, but the UN must be firm with you. Let me in, or else.
Kim Jong Il: O else what?
Hans Blix: Or else we will be very angry with you, and we will write you a letter, *telling* you how angry we are.
The LGPL doesn't really allow derivative works to be closed source. The problem is that the GPL incorrectly defines derivative work in a way that is so unreasonably broad that merely doing #include <gplheader.h> could potentially make your project a derivative work. That's why the LGPL was specifically created to remedy what a sizeable percentage of FOSS developers consider to be a fundamental flaw in the GPL.
In all likelihood, the implied linking restrictions in the GPL wouldn't hold up in court, so legally, the GPL and LGPL are probably equivalent. That said, most companies aren't willing to take that risk. And ditto for some BSD open source projects.
Despite what some of the moderators seem to think, the ACs are right on this one. Developing an app as GPL is fine. Developing a library as GPL is really a cheap shot, and in the end, only hurts your library's acceptance in the general computing world, as it makes it nearly impossible for a closed source app (or even some BSD-like apps, depending on license variant) to use your library.
If you're lucky and the library is useful enough, it may still be adopted in spite of being GPL-licensed, in which case, a BSD variant will inevitably be written. Suddenly you have two groups maintaining two versions of an essentially identical library (e.g. getopt_long). It's a total waste of time and resources, all for stupid political reasons that would have been obviated had the authors chosen a sane license for the library to begin with.
There are only two appropriate licenses for libraries: LGPL and BSD. For GPL-like protections (without fascist linking restrictions), use the LGPL. If you don't care if someone does a closed-source derivative work, use BSD.
Check out my sci-fi/humor trilogy at PatriotsBooks.
I hate to burst your bubble, but if you use GPL'd libraries in your proprietary code, the end result is *by definition* a derivative work of those libraries.
This includes something as simple as including a GPL'd header file. The only reason why code is allowed to include kernel headers (which are GPL'd) is because there is an *explicit* exception made by Linus to allow it.
If you are actually doing the above, you might want to talk to an IP lawyer.
Chris
Like when the RIAA sues individual infringers?
Or is Slashdot only for that when it's a GPL author? What a double standard.
If you're only using open source code for in-house applications you don't have to abide by the terms of the GPL or any other open source license. This primarily stems from the legal definition of a corporation as a single "person". As long as any violating code remains within the company you aren't engaging in distribution.
Do you have to run through legal whenever you want to install Tcl or Perl? What if you wan't to add proprietary extensions?
The heavy handed tactics of the entertainment industry is what gains them the public relations disaster.
This is just yet another way for the whole OSS/GPL community to shoot themselves in the foot. Something that RMS never understood.
You seem to think that just because someone's anti-GPL, they're anti all FOSS licenses. I prefer the MPL to the GPL, for instance because it doesn't try to extend its cover to other code - only its own code and modifications to it.
That is why the GPL really is a license and NOT a contract. You have license to do what you otherwise are not allowed to do. A contract is restricting your rights, so you must be compensated.
In fact, since the US ruled that "recieving copyrighted works" is equivalent to monetary comensation (as far as music sharing was concerned), then the code that was given is several million dollars' worth of consideration.
You can get a lot of restrictions for that sort of money...
Hey, Let's get off grandmothers and eigenvectors/eigenvalues. Mine taught me that Jacobian itteration is simple, but subspace itteration is more efficient for large matrices. What did yours teach you?
----- There are two kinds of people in this world, my friend; those with loaded guns, and those who dig.
If you customized each customer's code, they probably will keep it private and accomplish your goals, which are all legal under the GPL.
Note that if you for some reason start getting lazy in supporting them your customers can just take your code and give it to somebody else to maintain. They could also ship it to Elbonia for future maintenance.
Likewise, if you started raising prices and your customers became dissatisfied they could band together and create a replacement for you which would maintain all of their code while maintaining confidentiality. They could even hire a programmer to run diffs to tell apart the areas of code that you provided to all customers vs a single one. Common code could then be donated back to the parent project that you borrowed from for maintenance.
The GPL allows for many business models, like the one that you propose. What it does though is empower the customer - if the vendor gets out of control the customer can go to somebody else, or bring maintenance in-house.
seems like an honest question to me .. i don't get /.'s position on intellectual property at all. one minute they hate it, the next they love it and want to use it to prosecute gpl violations
I can't get to the article, but the summary lists Buffalo as a possible violator. If they are, I doubt it's intentional, since they released all their Kuro box code (which their linkstation is based off of) here .
"...today consumers have been conditioned to think of beer when they see a bullfrog..."
Nowadays, PearPC doesn't get many updates, because everytime they do, CherryOS does too. It's dampened the whole thing for the developers.
Is that really true, or just something you believe? Looking at the PearPC stats on SourceForge, I can see the downloads are declining, but only from a peak in September, corresponding to the latest release.
Besides which, I don't really sympathize. The developers are the copyright holders. They have the power to stop CherryOS if they want to. If they don't want to do it themselves, they have the option to go to the Software Freedom Law Center and try to get them to persue it, or sign their code over to the FSF and have them handle it.
If CherryOS was forced to obey theGPL (which they will eventually, some organization like the EFF or something will take them to court) then this wouldn't happen.
The evidence of infringement is overwhelming. CherryOS could have been taken down almost immedately through a preliminary injunction.
Obviously, I don't approve of what CherryOS has done, but I don't approve of people not standing up for themselves either.
"If you are actually doing the above, you might want to talk to an IP lawyer."
Yeah right. Just strip the GPL text out of the file
Problem solved!
Yes I'm serious.
On troll tuesdays we are for intellectual property rights.
It is good to see someone doing something about GPL violators, but what happens when the violators are other GPL developers?
I contribute (a little) to a project called AutoIt3 (http://www.autoitscript.com/). They make a really useful scripting language for Windows.
Until recently they were using the GPL license. However some people took big chunks of the code, ripped it and repackaged with a different name. They only mention "based on AutoIT" or something similar on the Readme.txt but not in the code and of course they do not mention the original authors of the original work nor on their web page.
Some of the AutoIt developpers were so pissed that now they have changed the license (for their newest releases only, of course) and do not distribute their code until some months later.
Perhaps what these guys did is legal, I don't know, but if GPL developpers dishonor the heart of the GPL, then why use it and how can we expect for commercial companies to abide to it?
OSS would be better off without ANY restrictions on use.
There are no restrictions on use, the restrictions are on redistribution. You can even modify GPLed code and never release the modifications, as long as you similarly never release any binaries.
It's official. Most of you are morons.
I'm sorry, but an MP3 of a Britney Spears song hardly qualifies as "information." It is (at least by the legal definition) a work of art. And it is therefore protected by copyright.
And source code is "information" and not copyrightable?
WTF?
Your reading comprehension skills are crap, no surprise for an AC.
But that Leo guy's are just as bad, he's a one-trick pony, he think's he's found some sort of internal contradiction in the idea that "information wants to be free" here on slashdot and no matter how many people explain it and spell it out to him, he just keeps going back to his one trick the next time an opportunity comes up.
I'm forced to conclude that the internal problem is not with information being free, it is with his own mental processes not being able to comprehend the full scope of that meme.
The GPL isn't an EULA - meaning, it doesn't apply to use. It applies to distribution.
Let's say you have that super-fancy application you just developed to take over the world. Of course, you want ease of use for that, so you rip some code from GPL'd programs. Now, as long as you don't give this application to someone else, it's perfectly legal to use it all you want.
"GPL Violators On The Prowl"
That should be... "On the prowl for GPL violators" or "GPL Violators on the hitlist" or similar!
Rip off Apple by using their code in your project without permission -> get sued by the copyright holder (Apple)
Rip off Microsoft by using their code in your project without permission -> get sued by the copyright holder (Microsoft)
Rip off a free software developer by using their code in your project without permission -> get used by the copyright holder (the developer)
Which part of this simple process don't you understand?
Thank you for consuming my HD with source code I will never open. Hosting it online would be an EVIL BAD THING TO DO.
Once again thank you... my Linux Boxs' 5 gig HD praises you every day.
But it's only legal because of the GPL, which licenses you to use the code in this way. The GPL only restricts distribution, but it applies to use as well. If it didn't, then use would not be permitted.
Let's see... I'm over 200 pounds, but I'm over six feet. We'll count that. I own a black duster. Hell, I own two. Half my t-shirts were free giveaways, but I never owned a Star Wars shirt. I grow a beard out of laziness. I own a big black cowboy hat, which is close enough to a fedora. I don't carry a cell phone when I can help it, because I loathe cell phones. And I've never been to a Ren Faire, and won't ever if I can help it.
Man, I made 4.5/7 and didn't even know. Thanks!
--grendel drago
Laws do not persuade just because they threaten. --Seneca
That's easy. We are for copyleft because it cancels out unreasonable copyright, which we are against. We also do not discuss "intellectual property" as a mater of policy. ...at least we would if we were the FSF.
Maybe you should read the license that the software is distributed under, instead of trolling Slashdot.
I want you to pay me for your use of "the"... and "?". They are both mine and "I want you to respect [my] wishes and respect [my] rights."
Or I'll sue you...
Bitch.
Feels good doesn't it!
Now If I was to tell you it would cost you $1000 each time you'd understand how people in third world countries feel about software patents and western media!(Cambodians I've talked to LOVE the idea of $40 DVD's it makes their WHOLE WEEK!
Of course you could go without "the" and "?" and still acheive a happy functional life, starting to understand?
I really hate you people.
Since open-source licenses (including the GPL depend on copyright law for their enforcement, most open source advocates seem to have no problem with existing copyright laws as it applies to software.
Patents are another issue altogether.
Mainframe/UNIX Bit Twiddler and long time Windows/Linux Hobbyist.
The Theorem Theorem: If If, Then Then.
Finally, information doesn't 'want' anything
You're right. He shouldn't say that. Information hates being anthropomorphised.
So I'll explain the idea more formally. The marginal cost of information approaches zero. In a free commodity market, the cost of a good approaches the marginal cost.
MOD PARENT UP, effing HYSTERICAL
These slashdotters don't like people pointing out their hypocrisy, and will get very defensive about it.
No matter what you say they will be convinced that it is ok for them to violate licenses/copy rights, but it is not ok for anyone when it applies to open source.
Plus with all the comments I am convinced of that prevailing attitude. In these articles we keep hearing at lengths from Joe Slashdot Pretend Business Major who has no clue about these businesses are run, telling others how their business should be ran. Most plans are essentially allowing people to amass all the companies stuff for free. Most of these "fair deals" usually end up with the business at a severe disadvantage and/or are too unrealistic(i.e. the albums should cost $0.01, they put it in every absurd format and encoding rate I can thing of, and they must give me the original CD).
Then again, most of that kind of stuff is justifying their greed of downloading a lots of copy righted works that they don't have the copy right owners permission to take, and not paying those who worked on the movies/music/games/etc they freeloaded.
I'm gonna disagree on this one. I hate math, but I have done pretty well programming on my own. The key wasn't math but data structures; once you grok how those work, you realize, "all we're doing is pushing around our data into some organized form." Sometimes an algorithm comes in very handy to do something optimally, or for a particularly complex situation - that's where math is useful. But you can usually get away with high school math abilities if what you're doing is code maintainance or porting or interfacing or many other numerous tasks which are not simulations.
To reiterate: programming is the applied organization of data, math(as it relates to programming) is the discovery of new organization techniques.
Isn't that inherent to the demand? A real demand has a method to manifest the supply. It's like a simple energy exchange (no loss or gain). That is, if you have a *real need, you will spend your money, hence manifestint a supply.
The GF bought a Sony HDTV which of course, the resident geek BF set up. I was amused to see a full printed GPL license in the included paperwork. I gather it uses a GPL-derived photo viewer program to display the content from media inserted into the Sony-proprietary (irony!) Memory Stick slot on the front.
I wonder if should I ask Sony for the source code for the TV.
I searched for some kind of adapter that would plug in the Memory Stick slot and take a Compact Flash card with no joy. There is an adapter that goes the other way, fitting the Memory Stick into CF slot, but the BF hesitates to recommend buying a memory stick just to make the TV happy. *sigh*
Ever dream you could fly? Get up from the Flight Sim. I Fly
I think that in general most people ignore rules they don't agree with (witness jaywalking, rampant filesharing, office supply theft, cell phones in theatres, etc etc). Looking just at filesharing - the majority of people believe this to be the greatest thing since email. So I wouldn't agree with saying that ignoring the rules is "arrogant beyond measure" but rather "typically self-centered".
You seem to be blinded to the idea that "to copy" is different than "to take". The cost of copying has dropped to virtually nothing in the digital age, making scarcity obsolete for IP. Copyright attempts to retain scarcity on IP artifically, and the view by many is that this is in vain - in a number of years, despite attempts by RIAA/MPAA or whomever, digital copying will be ubiquitous and free.
As a potential author, I would have to be aware that my works, even if I never released them digitally, will end up in the public and traded freely. Does that mean that I should not produce my work at all? Does that mean that I won't see a dime for my work ever? No. It may mean I get less income from a particular work than I otherwise might, but any work of value will still find paying customers. To wish that the gravy train of lifetime compensation per work and pay-per-view consumption continues is to wish the stagnation and death of thee internet and the Information Age.
To keep this on topic - the GPL is necessary to protect the ideas of Open Source in today's copyright landscape. Without it, unscrupulous companies will "take" open source code (not just "copy", but "take", as in claiming ownership and credit) without any compensation to the good samaritan coders. This is a thing to be fought, and rightly so. The RIAA/MPAA etc exist to do something similar for their works - however, they are not attempting to prevent unscrupulous people from "taking" works (claiming ownership or credit), but are trying to enforce a "pay-per-view" model.
I personally find obtaining digital things for free to be good, and arbitrary rules against it I ignore. I also personally feel that falsely claiming credit or ownership of a work is abhorrent, and should be fought against.
I think the way things are going, we'll end up going back to a "patronage" model, with quality being the revenue generator, and the actual 'works' freely available. For books, the real consumer value is in owning a physical copy (the 'work' being essentially an ad for the particular stack of bound paper). Publishers sell books not 'works'. For music, this will mean live performances rather than the 'works', which are essentially ads for the live performance. The **AAs will become the patrons of tommorrow. For software this means Open Source everywhere.
The true value lies in quality. That is what drives the economy and progress, and successful business models will always reflect this regardless of how copyright law plays out.
-ZOD-
the copyright for the code rests with the authors [unless assigned to another person/group/co/org]. these are the peple that need to bring the actions. the fsf are a good starting point for people intested in doing so.
the site mentions court wins, but provides no links [eg press releases, cort decisions, etc] and doesn't even directly say that the site owner was involved in the case. he makes tenous associations between himself and the fsf, but doesn't provide any real proof of association [and no, putting a link to another website does not count].
this looks a little sketchy to me...
sum.zero
And how does that apply to the "demand" for free information that we were discussing?
As long as you don't redistribute you have no problems. At my old job we used to use openh323 stack because it saved us 1/2 million in licensing fees for a commercial voip stack. Problem was it was pure shit, we had to put 3 developers on it for a year to get a workable version. I don't think we ever released what they did, for fear our competitors would pick up our changes and actually get a workable voip stack for free.
Have you ever been to a turkish prison?
if the other groups are using gpl code, they are required to keep the original copyright attributions in the code. failure to do so voids their rights under the gpl as far as i know. this is their only right to that code, so they now are violating the copyrights of the original coders.
your friends should have taken the violators to court, not turned anti-gpl...
sum.zero
Rip off a free software developer by using their code in your project without permission -> get used by the copyright holder (the developer)
Which part of this simple process don't you understand?
The part about how we are supposed to use them.
Use them for what?
there are very real differences between commercial indfringement and personal filesharing, not to mention that filesharing is legal in some places.
;P
your arguments, while often verbose, are simple misdirection and oversimplification.
can't we all just get along?
sum.zero
EXACTLY!! Who the hell is this guy, and why does he think he should take it upon himself to declare who is or is not in violation of the GPL?
This could be an effort to create court cases in which the GPL is declared to be unenforceable.
I'll feed the troll.
You know as well as I do you aren't forced to use GPL or even LGPL software in your commercial product. You are perfectly free to write everything yourself or choose something from the BSD license camp.
I love how different people define freedom these days. It means one thing to the Bush Administration and another thing to John Gilmore.
If you want my personal opinion, which you don't, BSD licenses view free in terms of free to do whatever you want with it. the GPL licenses view free as in the code must remain free in terms of it must be available for all people at all times. The GPL folks figure the way to do this is by drafting the terms under which you make use of the code.
"Fighting the underpants gnomes since 1998!" "Bruce Schneier knows the state of schroedinger's cat"
It is JUST as free as claimed.
If you wish to use it, no problem.
If you wish to improve it, no problem.
IF you wish to distribute it (with or without your improvements), no problem.
If you wish to steal it, Problem.
Now if you DON'T use GPL code in YOUR code, then there is no requirement for you to release YOUR code.
You are completely FREE to choose how YOUR code is done. It is NOT legal to violate the GPL.
Usage of a program is not restricted by copyright law. So use is permitted just fine without the GPL. The GPL even specifically says:
Activities other than copying, distribution and modification are not covered by this License; they are outside its scope. The act of running the Program is not restricted, and the output from the Program is covered only if its contents constitute a work based on the Program (independent of having been made by running the Program). Whether that is true depends on what the Program does.
So, no, running the program is not covered by the GPL, it doesn't apply to use at all. It goes so far as to explicitly exclude it from the terms.
sorry, having looked a little harder i now see he is the chairman of the netfilter team and that the actions seem to revolve around his own project's code. i would think this should be made clearer in the text of the site as it is, at least partially, a vehicle for his personal interests. having to go to another site for the info is not enough, imho.
it is likely more of a case of incompetent web design than malfeasance though...
sum.zero
US Mail Certified letters to those corporations US Legal Departments is the best place to start...
If you ignore the other uses of a tool, does that make the tool less useful, or you less useful?
Rip off a free software developer by using their code in your project without permission
Most free/open software licenses don't require anyone's permission to use the code, just adherence to the license.
How, otherwise, can a coder know what 'going quadratic' means, and how to avoid it, in terms of a search algorithm?
Maybe it is the fact that I work in an academic library, but I don't really write my own search algorithms. Mostly, the DBMS handles the searching, I just maximize my SQL query. It is only in instances of very small amounts of data that the data isn't dumped into a database, and I might have to write a Perl script or something to search it. And then, as long as I can manage a simple linear algorithm for the search, it does fine (small amounts of data, you know?).
And yes, I AM bitter about all those hours as an undergrad writing linked lists and search algorithms in C++.
This probably can't happen. Usually companies are only asked to stop the violation, meaning the penalty is only having to go back and redo the development the way it should have been done in the first place.
Damages are also a slight possibility, but the amount is hard to establish for GPL violations unless they are one of those few dual license cases, where the software is also offered for sale under a commercial license.
I suppose some court in the future COULD impose punitive damages that include loss of a company's copyright, but it seems unlikely, and would probably be reversed on appeal.
IANAL
a,e,i,o,u and sometimes w and y (at be if of up cwm by)
If you want to close-source your app, even if it is derived from GPL code, all you have to do is remove absolutely every single line of code that is covered by the GPL that you yourself did not actually author. If those lines include necessary portions of the program, then they must be rewritten from scratch (but not copied from the GPL'd work). If your changes to the GPL'd work are extensive enough that you expect a commercial distribution might actually succeed in the first place, this is probably not a problem.
Remember, copyright only protects _content_, not ideas. You cannot be sued for violating the GPL if you only copied an idea (or even a whole mess of ideas).
File under 'M' for 'Manic ranting'
The situation with the GPL is precisely analogous to the situation with downloaded music. (Most) music copyright owners expect a payment of some kind in exchange for their providing you with music. Creators of GPL code also expect payment. The only difference is that the music owners expect payment in the form of money, while GPL code owners expect payment in the form of more GPL code.
No, you don't get it (don't worry though, not many do). This is not about "payment" in any form, people don't use the GPL because they want to "earn" something, if that's the reason then they're confused. This is about Freedom.
There's a *distinct* difference between movie/music piracy and GPL piracy: FOSS was made to keep information *free*, and to promote sharing as a Good Thing. When someone is enforcing the GPL, that someone is preventing information being locked down and is thus protecting peoples freedom. The RIAA/MPAA wants to *prevent* sharing, and stop people from doing what they want with their music/movies.
Both kind of piracy is illegal, but it's waaaay different. The ethical background here is black and white, and can't be put in the same booth, ever.
Life is Reality
I've often wondered about that. If I keep the original copyright notice in there, and make modifications (perhaps significant) and release my changes under the GPL, how do I label it? I have to keep a copyright notice that attributes the code to someone else? What about my contributions? What if it's a complex mix where I can't nicely label just my parts? The GPL tells you what you're allowed to do and what your obligations are, it doesn't tell you how to do this in practice. Does the FSF have documentation on this? I haven't seen it.
This really could have a reverse affect. What I do not see here is "We try to work with companies to find a suitable path to bring them into GPL compliance". What I do see is the GPL version of scare tactics and lawsuits.
Most companies, especially the smaller companies, may be trying to be in compliance. They may not know how. This effort is most likely going to scare many companies off by showing how successful companies have tried to work with OSS and wound up being stuck in legal battles. The GPL is confusing for many and is mostly understood by word-of-mouth and/or other peoples confused interpretation. Not every company has a legal department to assist.
Let us take Sveasoft for example. Many people are outraged by the companies refusal to freely distribute (paid subscription required) their binaries and often scream "GPL VIOLATION". They do have their sources available for the public. According to Sveasoft, as well as my understanding, the GPL restricts the sources and not the binaries to be freely available.
A "strong arm" is not what Linux needs to assist with wide spread adoption. A community of people to assist with compliance is.
However, unless there is distribution actually occuring, any copying would fall under the category of personal use or fair use, which you have permission to do anyways, even without explicit permissison from the Copyright holder(s).
File under 'M' for 'Manic ranting'
So, I guess locking up (or killing) people and taking away someone else's money are all the same: either good or bad. It may not happen that locking up convicted felons in a prison is a good thing while locking up innnocents is bad. It HAS to be either good or bad, right?
Well, not.
It would be "double standard" if the OP stated the ultimate goal is to protect the copyright owner - however, if he thinks that benefitting the average citizen is the important thing, the standard against which everything is measured, then he may claim that different cases of copyright infringments can be judged differently without having to resort using double standards.
And the law is based on pretty subjective things (and at its very fundament is (or should be) the "greater good"): that's why we use humans to create the law and make judgements and not computers.
Real life is overrated.
Poster 2: That's really generous of you.
Anonymous Dumbass (sneering): True generosity would have been to give all of your money to the relief effort.
LRC, the best-read libertarian site on the web
You're only missing one thing. The GPL was created with the intended purpose to fight for the distribution of code, and the only way to do it was using the same laws that allow for the restriction of code. That's why it's ofter referred to as copyleft.
Really. You don't think RMS would give up the GPL in an INSTANT if it meant no other code could be copyrighted and it would all be in the public domain?
The law requires the permission of the copyright holder to use (as in, make a derivative work from) the code. The license grants the permission.
The ability to utter legalese tends not to be the same as legal protection or legal sanction. It's possible that GPL, by exposing source code to public view, exposes authors to de facto publication, placing their efforts squarely in the public domain. I realize GPL doesn't say this! My point is that GPL may be moot, void and irrelevant, depending on what happens before constructionist judges the first time GPL is challenged. My guess is, attempts to enforce GPL may be thrown out of court as meritless pious fiction.
``Tension, apprehension & dissension have begun!'' - Duffy Wyg&, in Alfred Bester's _The Demolished Man_
Transposition type. I hope you are just being obtuse!
Stripping copyright notices from a work when you copy with intent to redistribute _automatically_ negates any permission you may have previously had to copy the work unless such permission also explicitly included permission to strip existing copyright notices (which is highly unlikely, but possible).
While it must be conceded that finding such infractions may be technologically very difficult, it's still copyright infringement and infringers can, if discovered, be prosecuted to the full extent of the law.
File under 'M' for 'Manic ranting'
1) Statically link it, and provide the user the ability to relink with a bugfixed version of the LGPL code
2) Dynamically link it.
Plenty of commercial developers use LGPL code with no problems. See UT2004 et.al.'s use of SDL.
LRC, the best-read libertarian site on the web
"Stripping copyright notices"
What copyright notices? I don't see any...
Snip snip!
Hahaha! Buhbye GPL!
If your customers are consumers, why would they care or bother unless you suddenly changed your tune on support?
LRC, the best-read libertarian site on the web
Forget the term 'IP', it's only confusing ordinary people who aren't going to look up the details (yes, that means you parent poster).
IP is essentially both trademark, copyright and patents at the same time. *NONE* of those are related, they are simply not covered under the same law, their rules are completly different.
Copyright is what helps protect creative works. People write things in the GPL so that they can ensure it remains open and Free (as in freedom), and copyright is necessary to obtain that goal. (If they don't care if it becomes closed, they can just choose something like the BSD lisence instead.)
Patents (and trademark) are a whole different matter, they're not relevant to this discussion at all. Don't mix them, don't use the term IP unless you actually know what it means and your comment applies to all kinds of IP. Otherwise you're only adding further confusion. I'm not an expert, but atleast I'm humble enough to say so when I'm not sure.
"Believe in IP" is rather meaningless to say (you could be talking about anything), but you should embrace copyright (to a certain extent) unless you want everything created only to exist in public domain from the first second it sees the light of day.
Life is Reality
"[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz
As a very honest question, are there any open-source licenses that both a) allow the code to be used in a closed-source product (I understand the BSD licenses are like this) and also b)prohibit the code from being relicensed in such a way to prohibit (a) (I guess this would mean not allowing the code to be integrated GPL code)?
Thanks.
Man, I've been here years and I missed the 'offical complaints' pages. Where is that? Do we all vote on it or something?
If corporations are people, aren't stockholders guilty of slavery?
Programming an application isn't an easy task, but I think it's just a bit elitist to say that non-developers "can't really comprehend" it. There are many complex jobs in the world, and programming is just one of them. It really isn't special. I know this goes against some of our preconceived notions of programmers as gods, but it's the truth.
You said in another post that the math bit was a "side point"... Your wording makes it sound like you need to know those items to program, and you know as well as anyone else that is completely false. Yes, some applications require it. However, some applications also require knowledge of tax code. Does that mean you're not a programmer if you don't know tax code?
In short: Cool the ego.
You are refering to freedom as "anarchy". I don't want to live in an anarchy, stealing and murder should and must be illegal. Doing what ever YOU want to do with MY code should and must be illegal. You *can* however do what ever I give you permission to do, and that includes sharing it with others _as long_ as the freedom I gave to you is passed on to those you give my code/binary to.
We are protecting freedom here, what's so hard to understand? People aren't allowed to take away other peoples freedom in regards to MY code. If you must have that freedom, use a less restrictive license. There is however nothing wrong in protecting freedom, and it's still freedom.
Life is Reality
I demand someone smack you with a framed, nude picture of Ayn Rand.
Call me when they're done.
=Shreak
Ever put a GPLed binary on a USB stick and distribute it? Did you forget to include the source or offer it? No? Hope it's not netfilter/iptables because this guy will want $$$...
"Believe in IP" is rather meaningless to say (you could be talking about anything)"
Gee and just a few paragraphs ago you said "IP is essentially both trademark, copyright and patents at the same time." I only count 3 things. Are you confused?
Apparently you want to shift the discussion from consistency of position on authors rights to a technical discussion on what "IP" really means. Nobody (including you) has any confusion about what I meant by "IP" in the context of the discussion.
Remindes me to the Netgear situation. I'm waiting since August 2003 for the source code of the firmware to the WG602. They did release a source. But the orginal firmware (the one I bought in the package) had a telnet server and the route command didn't work completly. I couldn't find this bug in the released source. Thus they released the wrong one. One guy tried to help me last year, but I haven't heard from him since 3 months.
b4n
No, I don't think you get it. It's not so much that coders who release under the GPL expect to earn anything specifically for themselves, but that they require anyone who wishes to make use of their work (where use here means deriving a new piece of software) to provide some value in return (by releasing the derived code). The end result is about freedom, but the mechanism is identical to the situation with music. That's the whole reason that the GPL is referred to as "copyleft" - it uses the mechanism of copyright in a way that most people view as backwards. But the fact remains that the GPL uses copyright law. It could not exist without that copyright law. The same copyright law that music producers rely on. Unless you respect copyright law, the GPL is meaningless.
Ethically speaking, this is also about freedom in another sense: the freedom of a creator of some form of "content" to choose how their work will be used and distributed. GPL coders choose to release their code under the GPL. Others choose to use a BSD-style license. For whatever reason, most creators of music choose a very restrictive set of distribution terms. Not all of them do though. And frankly, I consider it far more ethical to respect the choices of "content creators" (else how can I ask anyone to respect my choice to use, e.g. the GPL) than to violate the terms which those creators freely chose. Better to persuade people that they're making the wrong choice about how to distribute their work, than to deliberately flout their choice (thereby encouraging them to flout my choices).
Woah. I have no problem with the GPL per se; more the encompassing RMS/Open Source movement, such as the parent's (or another in this article) comment of 'only GPL code can link to GPL code' and the like.
You're more than correct; you can license your code all you want. But there are licenses, such as BSD, artistic, or plain old PD, which are 'free.' The GPL, while a perfectly good license, however, is just as restrictive as anything commercial; the cost is simply in a different coin.
Vintage computer games and RPG books available. Email me if you're interested.
It's worth adding that the FSF actively discourages use of the LGPL (for their usual ideological reasons).
Also, many libraries are licensed under GPL and not LGPL. This may sometimes simply be ignorance on the part of the author who didn't carefully choose a license, but it may also be a deliberate choice by those that agree about the LGPL with the FSF. Either way, you have to respect the actual terms of the license that came with the code. You can't claim it's LGPL just "because it's a library" if your LICENSE file is the GPL. They are two distinct licenses.
Use of copyrighted things is automatically permitted. The only thing restricted by copyright is copying. (And public performances, which only applies to video, audio, and performing art copyrights, not software or image copyrights.)
Or have you been brainwashed by all the EULAs out there into thinking we need permission to run software?
If corporations are people, aren't stockholders guilty of slavery?
And why should a company even care ? It seems he's a no-one, a busy body who spends his time interferring in the affairs of others, worse yet he's a Trekkie!!!! http://gnumonks.org/users/laforge/ Though what he is doing is on the right track, he is trying to highlight the misuse of open source software by companies, but if GPL-Violations.org is to get any credibility they need some tougher sounding backers : Lawyer types, other big companies who DO play the game right ... and they need to drop the "I wish I was Lt LaForge" stuff ;-)
Depends on many factors. Deliberate infringement of copyrights or patents is always worse than innocent, inadvertant infringement, though. And for-profit infringement is always worse than free. So the company would already be negotiating at a huge disadvantage, and with much more to lose. There are other factors (how broad the patent is, how important the GPL'd program is to the community at large), but in general, other things being equal, that would be a very risky, and probably losing, move by the infringing company.
:)
The fact that there is so much redundancy in free software only strengthens the community's position in such a case, since dropping one project (at least until the patent can be worked around) will still probably leave several that do approximately the same thing. And you thought Gnome vs. KDE vs. Xfce vs. GNUStep was a bad thing!
Yeah, sometimes I'm funny. Sometimes I just fall flat.
You catch flies with shit.
As I work for a hardware vendor with an avid interest in operating systems for the embedded sphere, I would like to see more effort on the positive spin of GPL violations, and less on the policing spin.
What do I mean? Why hasn't someone thought to set up a "GPLCertification.org" site, where vendors could get their products certified as GPL compatible?
Police-state tactics, of repairing the damage 'after the fact', don't suit the F/OSS ideology, in my opinion. Far better to put in some up front creative energy into coordinating GPL usage, than to wait for someone to violate it and then butt-rape them in the courtrooms.
; -- the corruption of government starts with its secrets. a truly free people keep no secrets. --
You are the one missing the point. There is no difference between original poster who stated that the bitching about GPL vs RIAA are identical concepts, but that idea goes way over the heads of so many here trying to rationalize their hatred of RIAA/MPAA. If the GPL is about sharing, they should be happy that others are using their code and they should be more explicit what forms of renumeration are appropriate when a small portion of GPL'd code is incorporated into a much larger package. I know we've quit using ANY GPL code in our product because one attorney stated that even if we included one GPL module (about 200 lines), we'd have to release the source code for our entire package (about 2 millions lines). It was too difficult to get the absolute "correct" answer to the question as to how much we really needed to divulge. It was cheaper/quicker to re-invent the wheel. I suspect as more of these clashes go to court (and more proprietary source code becomes public record) the more companies will stay/run away from any GPL/BSD/OSS source.
The question is whether you believe in IP or you don't. If you don't you shouldn't embrace the GPL or the RIAA.
This was the text I was commenting on. You are saying that if you don't believe in IP then you shouldn't embrace the GPL.
Of course you need copyright to enforce the GPL, they coexist quite nicely and as expected. But patents are not good for software, especially open source software. This was the part I got hung up on, it doesn't make sence. However, someone might read it and think the GPL is inconsistent with copyright law, or that you either support both the GPL and the RIAA or neither. Your post was inaccurate and could easily lead to confusion.
Since it was inaccurate I thought you didn't know what it really meant.
Life is Reality
Actually, that is not true. FYI, GPL protects the idea and the specific implementation.
Rephrase the question, as it really has nothing to do with the GPL. How can they tell that a binary has someone else's code in it?
Looking for strings is one mechanism (and the most obvious). Looking for particular quirks in the behavior is another, disassembling the code is another. There are people who are experts in looking for this sort of thing. Yes, there's a chance for false positives, but the chance is slimmer than you might imagine. And, the false postive will turn up in discovery, before the case gets off the ground, so that's no biggie. (That's kind of the whole point of having discovery, SCO's abuse of it notwithstanding.)
Easy to defeat GPL detection? Perhaps, but it would take work, and the whole point of using someone else's code is to save work. If you've got to do a massive rewrite to hide your theft, you're probably going to end up doing nearly as much work as if you wrote the code yourself from scratch. So what's the point?
http://www.law.cornell.edu/uscode/17/usc_sec_17_00 000117----000-.html
TITLE 17, CHAPTER 1, 117 of the US Code begs to differ...
So the GPL isn't about sharing code, it's about maintaining control... I get it.
I'm only considered fat by people with frickin' eating disorders. And I've known a few.
And I'm still taller than you. Neener.
--grendel drago
Laws do not persuade just because they threaten. --Seneca
I wish you'd have posted with your name instead of AC, I would have given you an insight boost. I totally agree with your statements.
What about GPL developers who violate the BSD license? Why does the GPL using community tolerate members who violate other licenses? What makes it's okay to violate the copyright and license of non-GPL software? Why does the GPL community tolerate such behavior in its members?
http://www.feyrer.de/g4u/g4l.html
Don't blame me, I didn't vote for either of them!
The other posters' responses are more or less right on, but this may be an easier way to think about it: the GPL is a purely a defense against charges of copyright infringement. The legal part is: it will never come up in court except as a defense. (And it will probably never come up as a defense, because anyone who's actually complying with its terms is unlikely to be sued.) That is why it has never been tested in court. You don't sue someone for violating the GPL, you sue someone for violating your copyright, and they proffer the GPL in their defense, if they can. Which they presumably can't, or you wouldn't have brought the suit. Think of it as a limited-use get-out-of-lawsuit-free card that comes with the software.
I understand. You're saying the principle behind it is the same (specifically since it's ruled under the same law (copyright)) and thus they should be treated/responded to equally (music piracy & GPL violations).
You are completly right about this, I'm just pointing out that the differences in ideology underneath this is as big as it can get. On one hand you have users of Free software trying to keep things open and Free for everyone and trying to keep those freedoms alive, and on the other hand you have the RIAA/MPAA whose doing the opposite. Analog legal situation: yes. Fighting for the same cause: far from it.
Analog ethical situation: Well, the underlying motivations are opposite, but the ethical situation for those who brake the law (being it "stealing" music/movies or GPL code) is "perhaps" the same. I personally think copyright laws are too strict and simply wrong (the GPL doesn't enforce/use these wrong, restricting parts), and thus I have few moral problems "stealing" music/movies off the internet. I don't believe I'm doing something morally wrong as I wouldn't buy whatever I'm downloading before I downloaded it anyway (however there is a chance > 0 that I would buy it later). But that's just me.
When it comes to the artists: Yes, they should be respected. But again, I don't believe it's morally wrong downloading music I didn't pay for, so I don't feel disrespectful towards those artists. (Read my previous comment on this here.)
Life is Reality
The GPL, while a perfectly good license, however, is just as restrictive as anything commercial; the cost is simply in a different coin.
;) I guess you're right anyway.
Those were your words, not mine
Thank you for a thoughtful reply.
Life is Reality
"Of course you need copyright to enforce the GPL"
Thanks for making my point. The GPL will only succeed to the extent that people respect the "IP" behind it. Now, I don't want you to be confused or "hung up" by the term "IP" as it's used here. Since we are talking about the GPL, everybody understands that we're not talking about software patents. Likewise when we talk about "IP" with respect to music, we aren't talking about software patents either. Is that clear enough?
"However, someone might read it and think the GPL is inconsistent with copyright law, or that you either support both the GPL and the RIAA or neither."
Well, anyone who would conclude that my statement implied that the GPL was inconsistent with copyright law is not a very careful reader. As for the second intrepretation, that's fairly close to what I was saying. In other words, if you wish people to respect your rights under the GPL, you should respect their rights with respect to licensing other material. Obviously, if we only abide by licenses we personally agree with, then licenses in general would be worthless.
No problem.
The main thing I'm trying to get across here is that the GPL is neither 'free as in beer' nor 'free as in speech;' it's an interesting way of using copyright law, and of allowing other people to use your code, but the requirements of repayment (of changes) and the no linking/'viral' nature is, or appears to be, non-free.
And I can understand some company getting confused that the 'free software' comes with strings attached.
Vintage computer games and RPG books available. Email me if you're interested.
if you wish people to respect your rights under the GPL, you should respect their rights with respect to licensing other material. Obviously, if we only abide by licenses we personally agree with, then licenses in general would be worthless.
Yes, but being a lawful citizen doesn't equal to supporting all and every law (with "supporting" I mean "agree to"). Obviously we're talking about the same law here (copyright), but they're using it differently. The GPL uses copyright to keep information Free and open, the RIAA/MPAA uses copyright to impose strong restrictions upon the consumer. Thus, I personally don't support **AA's actions (trying to limit my freedom of using their products that I've paid for). Copyright law should be far less stricter, and promote much more fair use.
My point is that eventhough everyone should respect the law (licenses and so forth), that still doesn't make every law "right". The RIAA should not try to take away my freedom to do use their products as I please. So legally speaking you can say "respect the law, context being GPL or RIAA", but morally speaking I say they are completely different matters. One doesn't have support the RIAA to support the GPL (or vica versa for that matter).
Life is Reality
I prefer, "Unless you've got a really tight cunt.", not only because boobs can be faked, but because that's where the action is.
what do they intend on doing when some Taiwanese hardware manufacturer embeds their code?
Let China swoop down and close all of Taiwan's factories?
Get your Unix fortune now!
What's so bad about the open sound system?
If I wanted to discourage Open Source software, this is a great way to do it. One of the reasons for using Free software and Open Source software is the sanity of the licence. I want to AVOID the software police looking over my shoulder.
If large companies are going to be harrased, or possibly sued because of mistakes they might make with open source, they are not going to use it. And if they don't use it, then that has a huge effect on what other people do.
-1: Doesn't understand what copyright is
"This is something they have created, and honestly, they should, and do, have the final word over what happens to their works."
Hard work entitles you to exactly nothing.
The reason people generally get rewarded for work, is because the parties involved agreed so, and the reason people generally get rewarded for the fruits of their talent is because there is more demand for the products of a talented worker than for those of an untalented one.
"Finally, information doesn't 'want' anything -- it's an intangible concept, like 'santa claus' or 'income tax reform'."
Next time, try to understand English before you post. "Wants" also means "ought", "should".
"And how does that apply to the "demand" for free information that we were discussing?"
What do you get out of discussing things on Slashdot? There's your free information right there, obviously you are meeting a demand, and presumably you are getting something out of it.
For illustration on this point of human nature, when I was a kid, it was free to go to the various museums in the area. However, one new curator was dismayed to learn that buses were using the museum as a stop, solely to let their passengers use the washrooms. Shortly thereafter, the museum started charging admission, and is currently $27 to enter; there may be a free day once a week, but last time I was around there, this was not the case.
Moral of the story: whenever there is no cost to use something, eventually that resource will be abused. People will always equate costless with worthless.
Moreover, and more to the point, there is no 'money' behind open source code. Their threats have no teeth, since they are not backed up by lawyers and legal action. Sure, there are eventually victories, like against SCO, but it is costly to fight such things, and Im guessing that smaller targets will submit to getting 'screwed' by a large company rather than risk entering the courts. Sure, people are happy to pony up cash to help defend linux, but what about a small OSS app some college kid made in his spare time? If a large company blatently rips off his code, it is first unlikely he would even know, and second it is unlikely he would persue a legal recourse. And, any victories would be uncertain, come at great personal expense, and may not even be worth it in the end.
Heh, mine is in dec :P
(B) + (D) + (B) + (D) = (K) + (&)
"Those like me who've BANDAGED and KISSED the TREE"
Anonymous coward, you are an idiot! Of course, you must have known by now, your mommy told you so.
(BTW, feel free to hunt me down like the dog I am. I am not hard to find, and once you've found me I will pinch your pimple.)
More accurately, the combined work of the new code and the GPL item is required to be under the GPL when you distribute it.
However, if you can extract the new code by itself from the combination (for example this is easy if they're separate source files), then the new code by itself can be under whatever license its author wishes. This is permitted even if you receive a combined work: you are free to extract pieces of it and use the pieces according to their individual licenses. The GPL has a clause in it permitting this.
-- Jamie
The BSA hounds whoever it's masters PAY it to hound. Who would pay the huge fee's to the BSA?
Thanks for putting on the feedbag. Thanks for going all out. Thanks for showing me your Swiss Army knife.
The difference is the software guy isn't buying off congressmen to make 100+ year laws that stack the deck in their favor.Change the copyright laws back to the original standards and i'd be happy to play nice with the theiving corporate whores.
ACs don't waste your time replying, your posts are never seen by me.
Programming requires logic, not math.
Formal logic -- especially the boolean logic central to coding -- is a branch of discrete mathematics.
There is no calculus/Eigen/matrices in presentation (UI)
Well, if you use vector graphics (SVG, Flash etc) for your presentation, obviously you're using vectors there. If you use raster graphics (bitmaps, gifs etc), you're using matrices. And hopefully you can see that the presentation for something like Doom 3 involves quite a bit of mathematics.
Further, while talking to databases may not require calculus, it definitely uses set theory and boolean logic. And parsing XML requires some type of finite state machine. Again, discrete maths.
You can write programs without having studied mathematics formally, but even one ungraduate discrete maths subject will make you a better developer. Do yourself a favour.
Vino, gyno, and techno -Bruce Sterling
No, you don't get it. It's about not letting anyone else take control.
One CPU cycle wasted on digital restrictions management is ONE TOO MANY.
buying off congressmen
I wonder if you've got a tight grip on how the whole "representative government" thing is supposed to work.
Change the copyright laws back to the original standards
"Original?" As in the 18th century? Don't think so.
You forgot trade secrets.
Just because it CAN be done, doesn't mean it should!
Yep! And on Wednesdays, Thursdays, Fridays, Saturdays, Sundays, and even Mondays. Any more dumb questions???
Adult supervision
That used to be a lot funnier before the National Guard proved it at Abu Grabe
I have mod points and I am not afraid to use them
I was counting items in his list, not making one of my own.
Sorry about that. It's been hard to see past all the bullshit posted in this forum lately. :)
Synology (www.synology.com) sells the DS-101 Disk Station, a NAS appliance based on uCLinux, with no source offered and no GPL references anywhere on their site.
Jim Buzbee did a review on Tom's Networking recently thst mentions the detectable presence of BusyBox and thttpd in the firmware image. His review mentions that Synology are "working on" this issue, but they don't appear to actually be complying. I've written them as well, politely asking them to do so, and aside from a polite "We're on vacation, we'll look into it" response, there's been nothing for weeks.
I hope they do release the source, as the modding possibilities for the box are enticing; but to date, they're still in violation of the GPL.
"My strength is as the strength of ten men, for I am wired to the eyeballs on espresso."
Have anyone deal with microchip and there compiler C30? It's based on GCC 3.3 and all copyright belongs to FSF. It's possible to download the source for the compiler but that version is not the same. And earlier version of the compiler had compile error in the public code. Another funny this is the extra licence requirement. When downloading a binary version the is a 60-days license and the compiler will stop working after that time. For some resons the license check is not included in the public version :) /bin/make" (and extra space is added). This makes it impossible to run under Unix. All the files have been edit in windows as well.
There latest public code of the compiler are all the building files bean tempered with. For most (not all) the start of the file have been changed from "#!/bin/make" to "#!
Does it help if I cry out loud?
Check out this program
o mPs
http://www.s0nic.hostinguk.com/wiki/ow.asp?2PDFFr
The description says "This program will allow you to create PDFs from any source (doc,xls,ppt etc...). All you need is to create a printer which outputs to a file. From your preferred application print to this printer. This will generate a file. Select this file with 2PDF4ROMPS and generate your PDF.
Simple postscript to converter. Totally based on the superior GNU Ghostscript.
Note for the more technically inclinedIf you supply the postscript file from the command line, the PDF will be generated without any user intervention, allowing the use of 2PDF4ROMPS from the command line."
Apparently it incorporates ghostscript, but it is NOT free and source is NOT Available.
In the license on the website it says about the code (which includes the ghostscript source too!):
" * You may not distribute the Godwin Caruana source code, or any modification, enhancement, derivative work and/or extension thereto, in source code form.
* The source code contained herein and in related files is provided to the registered developer for the sole purposes of education and troubleshooting. Under no circumstances may any portion of the source code be distributed, disclosed or otherwise made available to any third party without the express, prior written consent of Godwin Caruana.
* Under no circumstances may the source code be used in whole or in part, as the basis for creating a product that provides the same, or substantially the same, functionality as any Godwin Caruana's product.
Should source code be distributed in original or modified form to a third party entity without prior writtent consent from Godwin Caruana, a minimum penalty of 10,000 UK Sterling applies."
Until recently they were using the GPL license. However some people took big chunks of the code, ripped it and repackaged with a different name. They only mention "based on AutoIT" or something similar on the Readme.txt but not in the code
If they have removed copyright notices, forget the GPL, forget licenses, forget civil suit. Move directly to Sec. 506, criminal offenses.
"(d) Fraudulent Removal of Copyright Notice. - Any person who, with fraudulent intent, removes or alters any notice of copyright appearing on a copy of a copyrighted work shall be fined not more than $2,500."
That is $2,500 per count, i.e. per file (same way RIAA reached a $97 billion lawsuit). After the first $100,000+ lawsuit (I assume 40+ files), I don't think they'll do that again...
Kjella
Live today, because you never know what tomorrow brings
Appearantly this guy's fallen to the same noob perception, and associated the word "free" with the word "cost" augh.
Which is precisely why the term "free" is a poor one. It is semantically confusing, and even contextual cues can be insufficient to determine which meaning is intended.
You are not respecting their choices about music distribution. And yes, I've read your previous comment. But the bottom line is that the only thing you can know about how an artist regards file-sharing is the terms they choose (choose!) to distribute under. Are some artists getting screwed? Possibly. But it's their battle, not yours - you can't know who's getting screwed, and who's happy with the status quo. There are plenty of artists that either (a) choose not to join in the RIAA clusterf**k and become independent, or (b) negotiate with their studio to allow online distribution. Your claim to be "fighting for the small artists" is specious at best.
They deserve to be questioned about their use of GPL code.
No, the bottom line is that the artists should benefit from any shakedowns by the RIAA or ASCAP done in their names. Alternatively, they should have the power to tell the labels and the lawsuit proxies to back off.
However, that's not actually the case. If a band wanted you to have some of their music for free on their website, the could/would/have been overruled by their label.
Infact, the cartel situation in popular music forces artists into a situation where they're basically forced to choose between indentured servitude or obscurity. If the labels could get away with it, they would have all music reclassified as works for hire.
They even tried to pull that but the congress wasn't quite that much on the take.
As far as what I believe: I believe the same thing that US Supreme Court Justice OConnor does.
A Pirate and a Puritan look the same on a balance sheet.
it's = it is
its is similar to yours, hers and his; no apostrophe here
fees = plural of fee
also I think whoever should be whomever, though I'm not absolutely sure and could have made a fool of myself
as an aside, English is crap, but it's my first language (British) and I don't know of any better; you'll notice I don't use full-stops much
GrimRC
as far as I understand it, the original (indivisable) work is copyrighted, and the derivative works of a copyrighted (indivisable) work are not copyrighted differently; small fixes might not be copyrightable (proof-reading a copyrighted book and making corrections doesn't grant copyright over the corrections); I think those contributing under the rules of the GPL, are meant to understand they don't have copyright on the moderate changes they make
.pl or whatever), then clearly that file has its own copyright; after all, copyright doesn't apply to ideas but to some concrete form; on the other hand, I could imagine the chapters in a book having individual copyrights, so where does the granuality end?
however, if a contributor adds significant functionality, and in so doing creates a separate code file (.c,
copyright and "authorship" are slightly different I think; nobody can pretend to have produced a work that you actually produced, regardless of copyright (even if you assign copyright to them!), because that'd be some kind of misrepresentation
why not refrain from adding your name to the copyright list at the headers of code files (that is where it is right?) unless you add a considerable amount to the file (like a chapter to a book)? you could review occassionally whether you consider you've done enough to warrant your name being added to the copyright list; you could create a second list of names of extra contributors and patches, with their names getting promoted to the copyright list as appropriate
I should say I'm not a lawyer and may be very wrong
GrimRC
I've not seen anyone mention it yet; can this be a good way to make money? can a legitimate copyright owner sue for damages? would this be a good way for some contributors to some of the big projects to earn some money? even a small contributor to the Linux kernel should be able to sue many of the license violators, though presumably the size of their contribution may affect their personal damage awards
I'm not sure about how one qualifies for damages; companies taking software like Linux and incorporating it without honouring the license are taking somebody's work and using it commercially; don't they deprive the copyright owner of recognition (which is hard to avoid with GPL)? shouldn't the copyright owner expect their work to garner them some recognition, when it is used in other projects and those projects must offer the source code?
GrimRC
Adding a few verses to a song doesn't make the new verses derivative. The modified song as a whole is, but you could sell the new verses separately without infringing on the original song's copyright.
Linking to a GPLed work -- dynamically or staticly -- does probably create a derivative work. But dynamic linking isn't done by the distributor of the code; it's done by the end user. And the GPL does not restrict the making of derivative works for private use, so there's no violation there (there can be no contributory infringement without direct infringement).
Including a header file doesn't necessarily make one's work derivative of the header file; the header file often doesn't actually cause any code to be generated. Rather, it sets out the APIs and layout of the data structures. This is unlikely to be copyrightable, and the FSF certainly doesn't want it to be copyrightable -- can you imagine the blow to interoperability if an API copyright was upheld?