The FSF, Linux's Hit Men 1230
PrimeNumber writes "Forbes has this story about the Free Software Foundation and its quest for Cisco and Broadcom to release the source of GPL'ed linux source used in routers. Forewarning: The open source community is not portrayed in positive light so you might want to skip reading this. However it did help me gain insight into software from a PHB and suit perspective."
Of course! (Score:2, Insightful)
Re:Of course! (Score:3, Funny)
</sarcasm>
Quite. (Score:5, Insightful)
Re:Quite. (Score:4, Insightful)
You're right, but you missed one of the most disturbing parts IMO.
From the article:
This basically means that "It's alright to do whatever you want, and infringe on anybody's stuff, as long as you pay them off at the end. Asking them to stop, or comply with the way the code was released is bad, because nothing should be free." This is disturbing in and of itself.
Erioll
Re:Pls Mod Parent Up (Score:3, Insightful)
You can add the word "just" after the "isn't" in the first sentence, if you wish.
-aiabx
Re:Quite. (Score:3, Interesting)
His story should really have been, "Company develops hardware product driven by code they didn't write, and dosen't read the source code licence."
Re:Jealous? (Score:3, Interesting)
You are exhibiting what is commonly refered to by fundies as a "faith in science". You blindly accept the conclusions of the day as if they are not subject to change.
Substances like asbestos and ddt are a clear demonstration of the folly in this sort of thinking.
Earth is
Re:anti-GM = junk science (Score:3, Insightful)
There is plenty of real science employed by both sides in the GM debate. The problem is that *none* of it is conclusive. Depending on your point of view, this is "evidence of absence of harm" of "absence of evidence of safety".
Neither side can legitimately claim that current scientific knowledge provides solid support for their position. I, personally, ta
Re:Of course! (Score:5, Insightful)
What I've never understood is how people can object to the "viral" GPL, yet have no objection to propriatary licenses, which are equally viral. Linksys needed an OS for their router. They could have paid SCO huge bux for the rights to the Unix source. Presumably MS has its source available for embedded apps, also at high prices. Had they chosen to use SCO's Unix they not only could have kept their changes secret, the license would have required that they do so. So the secrecy license scheme is also "viral".
Modifying GPLed code is an exchange, just as much as using non-GPLed code is. With non-GPL stuff, you exchange money for code. With the GPL you exchange access to your changes for code. What is with this pathetic whining: "But we wanted to keep our changes secret." If you want to keep your changes secret either build your own damn OS, or license one of the propriatary ones by paying lots of money. The FSF is about exchanging access to code for access to code, not about giving away code
More to the point, of course the FSF sues people who violate their license, just as MS and SCO sue those who violate their license. Likewise, the FSF thinks that its system is superior and would like to see it supplant the propriatary system. Why is this bad? MS and SCO certainly would like to see their system prevail. Apparently, Forbes can't stand to see actual competition...
Revolting 'Article'! (Score:5, Insightful)
Why not focus on the fact that these criminal corporations are STEALING from thousands of individual contributors of GPL code worldwide? Linksys didn't code what they're using and they're not even being asked to PAY for it! The bargain is - they need to share what they've modified - end of story. The FSF has an obligation to stand up for the 'little guy' because... Well... Who else would? You can bet that if I took a piece of Cisco router code and put it in a "Chordsoft Router" they'd sue me for everything I had - and rightly so. I deserve to be sued for using proprietary software under their license agreement. Can't hack the terms of the agreement? Simple. DON'T USE IT!
The FSF was doing things 'in secret' - not for some dark motive, but because they didn't want to make a specticle out of corporations they are in negotiations with. Contrast this behavior with the BSA who routinely lines up companies and individuals for public inspection. Ask Ernie Ball (music manufacturer) about it sometime.
But everyone in the industry knows that GPL'd code - particularly network kernel stuff is the best there is. With so many eyes viewing, fixing, modifying, and tweaking it, it's as perfect as perfect gets. It's also very tempting for companies like Lineo and Linksys to appropriate it because it's so easy to do. But when you do the crime, shouldn't you do the time?
And pardon me, but I don't see $65,000 as a big settlement - these are reasonable costs associated with having to do this research in the first place. It's certainly not like when you have organizations like the BSA demanding MILLIONS for violations of their copyright holders.
How about a little more balance Forbes? Truly horrible 'reporting'.
Re:Of course! (Score:3, Funny)
I love being called a commie before breakfast!
GPL benefits companies like Cisco (Score:4, Insightful)
Re:GPL benefits companies like Cisco (Score:4, Informative)
As a company, "we" once toyed with the idea of loading our own code on Linksys hardware (it's simple really, even before the whole GPL BS.) But that didn't make it past the lawyer(s)
PS: Cisco is terrified of all the old, "obsolete", "used" hardware floating around. And with all the failed dot-coms, there's tones of it available. Some of it never came out of the box/off the pallet. It might be several years old, but it works perfectly (2500's, 5000's, etc.)
Re:Of course! (Score:4, Interesting)
No, they just hate copyleft. If one goes along with the assumption that "intellectual property" is just like private property in general, copyleft might indeed seem like a communist plot to promote a concept of The United Soviet States of America (or something like that).
It's one reason why "intellectual property" isn't such a good word. Where I live, there is a rather widely understood word for copyright, patents, trademarks, trade secrets and other similar things. It's immaterial rights and it would be great if it caught on to wider use. Speaking of immaterial rights is rather neutral and doesn't carry any positive or negative payload that I could see.
Re:Of course! (Score:3, Insightful)
Speaking of immaterial rights is rather neutral and doesn't carry any positive or negative payload that I could see.
It would quickly acquire such a payload. Meanings in language only remain constant for 'dead' languages like Latin, and you can contrive arguments that Latin's mutable, as well.
Re:Of course! (Score:5, Interesting)
FSF ombudsmen, not "hit men"
Dear Editor,
In response to Daniel Lyons' piece, "Linux's Hit Men" dated October 14, 2003, I respectfully disagree with the author's conclusions.
Lyons seems to take offense that Cisco should be required to release the source code for the router software used in their Linksys wireless router, which was derived from GPL-covered code. When the Linksys engineers sat down to design their product, they had three options for the software. They could either a) license router software from another vendor, like Microsoft, which developed the Windows CE embedded operating system, b) write their own software from scratch, or, c) take advantage of code developed by the open-source community. Since option a) would require them to purchase a license for each router they sold, and thereby eat into their profits, and option b) would surely cost millions of dollars and months if not years of development time, they chose option c), with full knowledge of the requirements of the GPL, which are completely up-front, and in no way "onerous," as Mr. Lyons describes them. Where licensing Windows CE from Microsoft requires you to pay Microsoft money, licensing GPL software requires you to contribute back to the pool of open source software from which you benefited.
Lyons mentions that: "the $129 device has been a smash hit, selling 400,000 units in the first quarter of this year alone," and then goes on to say that the "the Free Software Foundation doesn't want royalties--it wants you to burn down your house..." The problem with that conclusion is that Cisco didn't build the house. Their $129 device, of which they have sold 400,000 units of, would have cost much more, and taken much longer to develop and get to market if they hadn't leveraged the free software provided by thousands of volunteers over the past ten years. Is it too much to ask that they make a small contribution of software back to the community, which provided them with software that allowed them to make millions of dollars?
Finally, I question the author's motives and biases. I wonder how Mr. Lyons would have reported this story if Cisco were distributing Windows CE on their devices, without paying royalties to Microsoft, or failing to abide by the far more restrictive policies in their license? The author states that "For months, in secret, the Free Software Foundation...has been making threats..." when, in fact, it has been widely reported in the technical media that the FSF has made requests for the source code from Cisco. The language of the article makes Linux sound like some of shadow-communist conspiracy. "Linux's Hit Men?" "The dark side of the free software movement?" "Comrade?"
Some objectivity and a modicum of research, please, Mr. Lyons.
Re:Tunnel vision (Score:3, Insightful)
If you want to base your competitive edge on trade secrets, don't use GPLed software. It's as simple as that.
I didn't build my house either, but I wouldn't be happy if RMS & crew tried to strongarm me into burning it down.
What a useless comment. RMS & crew are protecting the copyrights of the original programmers of the code used by Linksys for their router. Are you against the protection o
Re:Of course! (Score:4, Insightful)
As the story mentions, the BSD licensed products provide an easy alternative without the licensing issues. It just takes an awareness of the options to realize that using Linux in the first place is a silly idea for commercial products.
Re:Of course! (Score:4, Interesting)
I hope someone reads it.
Forbes is a Microsoft shill anyway (Score:5, Insightful)
Now, maybe I'll RTFA.
Re:Forbes is a Microsoft shill anyway (Score:5, Insightful)
A summary, if you like: beware of using this software (which thousands of people have developed and give away for free) because you might have to actually honor the license that comes with the software! Imagine that.
Re:Forbes is a Microsoft shill anyway (Score:3, Insightful)
Correct, as per 17 USC 117 [cornell.edu]. This raises the question as to why virtually every EULA in existence isn't invalid due to lack of consideration. You already have the right to run the software; the publisher is attempting to remove other rights in exchange for nothing.
Re:Forbes is a Microsoft shill anyway (Score:3, Insightful)
"For months, in secret, the Free Software Foundation,
Uncertainty:
"The dispute... offers a rare peek into the dark side of the free software movement--a view that contrasts with the movement's usual public image of happy software proles linking arms and singing the "Internationale" while freely sharing the fruits of their code-writing lab
Re:Forbes is a Microsoft shill anyway (Score:3, Informative)
> keep saying (including this article) that if you adopt GPL code into your
> project, then you have to open source and make available your entire project.
>
> isn't this not true?
Correct, that statement is not true.
The 'entire project' is usually everything you do.
If you modify the kernel, your kernel modifications MUST be released.
Now, if that kernel mod was literally the only thing you did, and the kernel alre
Re:Forbes is doing thier readers a service (Score:3, Insightful)
So I think the article sends the right message to business people:
Correction: It could have sent the right message to people. Unfortunately, Mr. Lyons sees no value in understanding what "free" in "free software" really means. His consistently uninformed, slanted, and frequently infammatory jabs indicate this to be true.
In addition, Forbes is intentionally spreading this misinformation because it jives with what a large number of techless managers (a large part of its following) already think and feel
Re:Reading Source Files (Score:3, Insightful)
For most EULAs, it is clear that the copyright owner does not want you to make copies of their binary software available for others to use.
Heh. If that is what EULA's were actualy about then they wouldn't exists at all. Ordinary copyright law already prohibits that. EULA's try to add on additional restrictions not granted by copyright law. They almost always try to revoke rights specificly granted by copyright law.
Books, magazines, and newspapers don't come
Re:Forbes is a Microsoft shill anyway (Score:4, Informative)
OK, I did RTFA, and it is mostly bashing.
For months, in secret,
If LKML, KernelTrap, Slashdot, and Newsforge stories all qualify as secret, that is.
I don't know about "controlling" the licensing. They wrote the license, Linus and various other project maintainers chose to use the license. There is not much "control" to be wielded here. Open is open.
The first actual statement of fact in the article, even though "threats" might be a bit of a stretch. Moglen was quoted farther down that all of his conversations had been ammicable and that a resolution would probably be reached without going to court. That doesn't sound very threatening.
Re:Controlling the license (Score:3, Informative)
Hardly. Before you drop $500 million on a company, you're going to perform due diligence. Which means one or more of the following happened:
* Cisco did a poor job of due diligence
* Cisco knew of the brewing problem, but considered the potential liability to be worth the risk
* Linksys intentionally misled Cisco when it came to their software. This is the only scenario in which Cisco might be considered a victim, but also goes back to Cisco doing a poor job.
Still worth a read (Score:5, Insightful)
I'd suggest it is very important to read this. I think it's a bit simplistic to say that Forbes is a "Microsoft shill." Rather, Forbes is heavily invested in the status quo of business circa the early 21st century, and is naturally threatened (and apparently not a little confused) by open source and what it represents.
Anyone who bothers to give it a little thought realizes that in the modern economic system, the wealth of the 5% that own 85% of everything is protected by a business environment where the barriers of entry are too high to permit the appearance of significant competition from below. Every once in a while, emerging technologies can be harnessed to create an Apple or a Microsoft to challenge the more traditional, say, IBM.
Now, it's plain enough that we among the 95% are largely responsible for all of this wealth getting shuffled around. We do the work, we buy the products. Our retirement plans sit around for 40 years, a nice capital base in the market while the fat cats try to speculate their way to another billion. In general, we aren't able to muster sufficient organization or marshall enough of our resources together to have a conscious, guided effect on these things.
It's little surprise, then, that Forbes falls back on the rhetoric of Communism and revolution to characterize the Open Source movement, because it represents a similar kind of threat to that system. Labor unions, for example, represent an attempt to collectivize the theoretical power of a group (workers are required for business to be done, workers can choose to see themselves in a collective bargaining position opposite those that own the business) to shift the balance of power between labor and management. Communism represents the attempt to acheive this reordering on the national scale through conventional political means (democratic processes and conquest). Open source has succeeded up to this point by a similar route - harnessing the distributed power of a group of individuals to achieve results normally available only to major players.
Unlike these things, though, while the Open Source "movement" may be informed by an ideology, the integrity of its product is maintained by an adherence to the strictly capitalist, legal definition of intellectual property. What is truly offensive to the Forbes set is that the grubby horde would have the audacity to coopt one of THEIR legal power tools to create a product that nakedly opposes the dynamics of the status quo.
The basic argument of this article, if you strip away the snide asides about the irony of those open source commies suing people for violating their I.P. just like regular businessmen, fercryin'outloud, is that by legally defending it's licenses, the Open Source community will discourage people who don't wish to abide by those licenses from adopting software released under them. Uh, yes, that is correct, sir. Businesses which wish to develop proprietary technologies with closed source software should not use GPL code.
Is Forbes genuinely incapable of understanding that the whole point of Open Source is that it represents a parallel software development strategy that is opposed to the conventional business paradigm of proprietary I.P., or are they engaged in conscious propaganda in defense of the status quo? In the end it doesn't matter, the result is the same. The principle of open source licensed software is a genuine economic threat to the conventional I.P. business paradigm, but it is completely impotent if the licenses are not enforced. So I'd say, don't skip this article - study it carefully and learn the strategy of your oponents.
Linux isn't a threat to the IP paradigm at all! (Score:3, Informative)
Actually, business that wish to develop proprietary technologies without releasing the source can still use GPL code. Take my company, Kiyon, for example. We're making a kernel module that, once installed into Linux, turns an embedded Linux device into an autonomic router that can do some really nifty things.
Now the only actual GPL-derived code we have is a modification to a driver to add funct
Re:Forbes is a Microsoft shill anyway (Score:4, Insightful)
Yeah, real good attitude. Keep ignoring Forbes: it's that mentality that keeps Forbes readers ignoring Linux and free software.
The free software community really needs to understand that when you're the underdog, you want to ALWAYS be portraying yourself in the best light possible and holding your head up high, even when people take really cheap shots at you. If the free software movement keeps miring itself in the mud and digging in its heels, it's going to continue to have a very difficult time growing.
At least get it right (Score:2, Insightful)
Re:At least get it right (Score:2, Insightful)
I'm quite stunned at this statement. It's like, you've just gotten a software's source code, someone elses work, to use in your product for free. free. no payment. just you have to hand back what you take.
Now the bit about
Re:At least get it right (Score:2)
Under the license, if you distribute GPL software in a product, you must also distribute the software's source code. And not just the GPL code, but also the code for any "derivative works" you've created--even if publishing that code means anyone can now make a knockoff of your product.
The first part of that looks fair enough. The second is a combination of oversimplification and hyperbole, but it is no worse
Re:At least get it right (Score:3, Insightful)
Great quote: (Score:5, Insightful)
1) Hah! Let's try:
There has been more than one story about Microsoft and IBM using licensing or patent disputes in order to screw competitors. SCO's entire existence seems to depend on wanting you "to burn down your own house". Oracle's in there for completeness. I'm sure there's other examples.2) And holy FSOF, since when did complying with the license the software is released under become such an onerous act? When it forbids you to release benchmarks of .NET software (MS)? When it
includes clauses saying "If you're in Europe, and you have the right to
reverse engineer this software, you explicitly give up that right even
though you don't have to" (Synplicity or Matlab, I forget which --
installed recently at work)? Evidently these crack-induced clauses are
perfectly acceptable; why, then, does Forbes' writer swallow a camel and
strain at a gnat?
Grr, this is going to bug me all day...
Re:Great quote: (Score:3, Insightful)
CISCO knew this requirement, yet they still used Linux for their routers.
Re:Great quote: (Score:3, Informative)
Re:Great quote: (Score:5, Insightful)
Exactly. The reason that Linksys was able to sell 400,000 units is that they stole a jump on their competitors by using Free Software as the base of their product. They didn't write that software and the license that Linux is distributed under is very explicit. Linksys sold nearly a half million units of a product that someone else did the bulk of the work developing and now they want to complain about the terms?
That's just ridiculous.
The reason that Cisco is going to settle is that they know that if they didn't settle they would lose,be forced to cough up the source code, and pay damages to boot. They are fortunate that they stole from the FSF and not someone else.
But the copy wasn't as good that way (Score:3, Insightful)
I mean, it's hard to get an anti-GPL spin if you make the fundamental correction to the story:
the story so far... (Score:3, Informative)
broadcom made the chips..
linksys used the chipset in their product. they also used linux as the OS in the product. they wrote drivers for the broadcom chips and patched them into the linux kernel. actually linksys didn't necessarily write the code themselves, they could have contracted it out to consultants, india, broadcom, mars, atlantis.
for months people have been hounding linksys to release the source code for using the broadcom chips (which would greatly enhance open source sup
Re:Great quote: (Score:3, Insightful)
Re:Great quote: (Score:3, Insightful)
Well, no. You said that the First Sale doctrine "makes no mention of a limit as to how many copies you can resell". This is simply not correct: it is mentioned quite explicitly that the legal owner of a particular copy is allowed to resell that particular copy.
How do you know Broadcom did not comply with the GPL? Maybe Broadcom gave Linksys the source code to its changes.
Hence the word "If" that began my sentence. Anyway, "if" that were
Re:Great quote: (Score:3, Informative)
Re:Great quote: (Score:3, Funny)
That line is rather funny. He seems to have missed the point that, in fact, it's NOT Linksys's house. Linksys only built the outhouse, and the FSF wants Linksys to share the outhouse in exchange for Linksys being allowed to use the mansion. Not to mention that Linksys remains entirely free to take their outhouse and remove it from the FSF property, as long as they qu
Re:Great quote: (Score:5, Insightful)
And does Forbes believe in EULA that says you must have a license for each machine or each processor? I guess not. After all, the consequences to businesses for violating these agreements are extreme. A company with several PCs and lacking a single license for the MS software could be a great deal of trouble. And the gestapo tactics of the BSA audits and spy software certainly cannot be good a corporation.
Many of these adults remind me so much of adolescents who want to pick and choose the rules. The GPL is disclosed up front and a person chooses to use the GPL code or not. If they choose to used it and violate the license, there are consequences, just like any other violation. It is childish to say after the fact that the rules are unfair. The rules were agreed to when the software was used. And unlike some other software or music licenses, there is no element of constraint or duress, and the GPL has no element of unreasonable restrictions of rights.
The fact is that corporations want others to pay for their worthless products, but refuse the same in return. We have seen this with the RIAA and expensive industry reports. I have seen this with guys make 100K a year but only go to movies when they are free. And we see this know with companies that steal code but complain when others do the same.
Re:Great quote: (Score:3, Insightful)
And I like how he talks about the GPL "enforcement" squad as hit men, "snooping" into companies to try to find hidden violations. What about the Business Software Alliance? Don't Oracle and Microsoft do the same thing, looking for illegal copies of their software?
No one made Linksys or Broadcom use Linux; they were perfectly free to buy someone else's kernel, or to write their own. If the
WTF? (Score:3, Insightful)
The author obviously has no idea what the GPL involves, and demonizes an organization who's concern is to enforce a simple set of rules. Does he think Linksys would get such leniency from the BSA, Microsoft's hitmen?
Re:WTF? (Score:2)
Re:WTF? (Score:3, Interesting)
He does not make clear that these companies would have been completely aware that they were taking an existing software product which, like all others, would have a license attached. Basic due diligence would then mean that the license should be read and complied with.
The GPL did not come a
Re:WTF? (Score:5, Insightful)
Re:WTF? (Score:4, Interesting)
Yes, he does:
He thinks that releasing the code is a far worse penalty than having to pay money. And, here's the scary thing: he's right. Most companies would much rather spend a couple million to make the license problem go away then have to release any intellectual property.Granted, they should have known what they were getting into before they used the license. Because they are using a product that has a license for use, and they implicitly demonstrate agreement with that license (by distributing the work), then they should follow the terms of that license. It just happens that in this case the terms of the license may require them to do more than they really want to do.
My Feedback (Score:5, Insightful)
The GPL license is very clear and up-front in its terms and conditions, and is far more permissive than traditional copyright licenses. However it does state clearly that if you do not abide by the limited restrictions it does enforce, you cannot distribute the covered work.
This article, in the face of all reason, appears to suggest that readers should feel sympathy for companies who break copyright law by distributing copyrighted works without ahering to the terms of the copyright license.
Furthermore, the article goes on to lambast the Free Software Foundation, a non-profit watchdog group, for attempting to enforce its own copyrights.
The author ludicrously justifies his hostility towards the FSF by stating that the FSF is more "dangerous" than other businesses holding copyrights, because it is insists that violators of its copyright stop distributing its covered works.
The FSF is also derided for apparantly having a limited budget, as if its limited funds are somehow justification for others to violate its copyrights.
The FSF are referred to using terms associated with communist propaganda, which add nothing to the intellectual quality of the article.
The language the article uses appears to make the FSF appear suspicious and nefarious for attempting to come to an amicable resolution with other companies before seeking legal protection.
Finally, the article ends with the authors opinion that it is a "pity" that companies will settle with the FSF when they are caught distributing covered works without a license, instead of going to court.
If this is the kind of article one can expect to find in Forbes these days, I don't know how much longer I will be a reader.
Re:WTF? (Score:2)
Blindly believing any single source is just setting yourself up for disappointment...
Questionable Article (Score:2)
What's 'PersonId'? They're keeping track of you
I think RMS is a kook, with some fairly questionable ideas, but this sort of imagery does not contribute to the idea of objective journalism.
Re:Questionable Article (Score:2)
Ahem... (Score:3, Funny)
(-1, Troll)
use of GPL code (Score:2)
If you don't want to get caught using GPL code and breaking the GPL license, then spend the money to hire the programmers to write new code from scratch.
I'm a zealot (Score:5, Insightful)
I only read what I want to hear and ignore others perspectives, right or wrong.
Re:I'm a zealot (Score:2)
So, I'm not a zealot
Re:I'm a zealot (Score:3, Interesting)
Got that? I WANT to be told things aren't as bad as they seem. But I won't believe it unless it's credible.
I think PrimeNumber was foolish to suggest one shouldn't read the article. I agree with your implication that one should read the article. However, I'm concerned that peopel don't know the difference between advo
You just know (Score:2)
The Dark Side? (Score:2)
Furthermore, the FSF isn't demanding damages or money, they're only asking their licence to be obeyed. How is this "worse than commercial" like those clowns at SCO asking for big $$$ for supposed harm?
They should get a clue. Nobody strapped anybody down and forced them to use free software. And nobody is now trying to enforce some obscure clause in some new way. They are simply asking for the #1 tenet of the GPL to be
Re:The Dark Side? (Score:2)
Furthermore, the FSF isn't demanding damages or money, they're only asking their licence to be obeyed. How is this "worse than commercial" like those clowns at SCO asking for big $$$ for supposed harm?
Indeed. On one side, we have the FSF saying, "everybody play fair and play by the rules." On the other side, we have proprietary companies saying, "Aha! You were caught! Cough up the protection money!"
And, yet, somehow, the author of the article seems to think that the FSF's approach is the more onero
Daniel Lyons (Score:5, Informative)
Re:Daniel Lyons (Score:5, Insightful)
Either a license is legal and a company has the right to enforce the terms that were entered into, or it's not. Either it's okay to rip off someones IP or it's not. The idea that it's okay to rip off someone elses IP if you're going to make a buck is hollow.
Then again, these guys thought Enron was wonderful. Forbes isn't targeting the type of person that is furthering the world, just themselves. What I find really sad is that the author completely skips over the fact that companies can develop internal applications based on GPLcode then deploy and use them enterprise wide without paying the onerous licensing fees that would normally be required by proprietary software. That would save a lot of businesses a lot of money, improving their margins and boosting profits and bonuses. I don't think that it would really be against Forbes targetted readership to have an article that shows both sides of the issue. If you use it to sell a product based on GPL you have obligations that you don't normally take into account and that you might well decide are too steep for you. That's an informed business decision for you to make. And, that same software deployed internally you can keep to yourself and still save a bundle on licensing costs. Again, another informed business decision.
It's not outside of Forbe's scope to present a balanced article to help its readership make informed decisions. They miss the point that the GPL is about allowing businesses to have more options in the tools that they use to conduct business. It's all about lowering costs, being more efficient and freeing you to spend less money while keeping more of what you make. And that truly is what business is about.
Just go ahead and censor things... (Score:2)
So are you saying we can't deal with negative criticism (even if it's structured like a falling card castle - haven't read the article yet, I don't know).
Daniel
Re:Just go ahead and censor things... (Score:2)
Re:Just go ahead and censor things... (Score:2)
Of course not. All ready, all of the posts about this article have been screaming "TROLL!!" without even reading the fucking article. OSS zealots tend to be a bunch of immature kids.
Meanwhile, we've got NineNine here making a blanket statement about all the posts, clearly without having read them.
You can find immature kids everywhere.
-Rob
Boo hoo. (Score:2)
The FSF's attempts to enforce their licensing is fair, not knee-breaking or Communism, as the writer implies. You used the code, you're bound by the license--which is not kind to closed-source business models. Cry me a fuckin' river.
-Carolyn
How is this Useful? (Score:2)
How in the world is this useful? The idea that reading something that you might not agree with is "bad" is bad for you is incredible on a site that most people might think is open-minded.
Please! Read this! If you ask me (which of course noone did, hehe) I'd think everyone here
There is always two sides to a story... (Score:2)
Frankly, what did you expect from Forbes magazine? These people looooove closed-source companies making lots of $$$.
They also do not understand the business benefits of GPL: strong, stable, mature code that is freely modifiable and that will actuall ensure that your competitors will have to share whatever modifications and improvements they make to the code with you.
This is the basis for much "coopetition" between firms, which has produced some fairly advanced open standards. This is also why IBM is inves
Hired enforcer? (Score:2, Insightful)
So to the PHBs at Forbes it's presumably OK for the BSA to act as an enforcer for one type of license but not for the FSF to act as an enforcer for another?
Balanced Views (Score:2, Interesting)
What a stupid thing to say. How can anyone claim to have a balanced view of an issue if they refuse to read any articles that oppose them?
What did they expect? (Score:3, Interesting)
Forbes may be making the FSF look like the bad guys here, but really, what are the alternatives? If this were Windows or some proprietary software, you'd have the BSA breathing down their neck.
What a slant! (Score:2)
This is a fine example of journalism with a 'slant'.
I don't see the Big Deal, Forbes magazine. If these companies didn't want to make their source code open and public, they shouldn't have used GPL'd code.
Maybe Linksys & company should have used SCO instead of Linux for their devices? ;)
Killer penguins (Score:3, Funny)
Arrgh! (Score:2)
Because ya know, we don't ever wanna hear nuthin' bad 'bout our boys, no sir, no sir.
Whatever happened to "know thy enemy"? Instead of telling people to not read this piece because it has bad things to say about the open source community, why not advocate reading it carefully to pick out the other side's arguments, analyze them, and learn how to counter them when your own boss starts quoting
Libre Society (Score:2)
This might be found interesting in lieu of the comments about free/libre/open-source ness... The Libre Society [libresociety.org]
Poor, dumb bastards (Score:2)
The bottom line, however, is that companies that use GPL'ed software are saving millions in development costs they'd otherwise have to swallow. Developing
Bias (Score:2)
*cough*BULLSHIT*cough* (Score:2)
Well, it's certain Forbes has been led astray. At SOME point that code had to be external and compiled into the kernel before it's loaded into firmware; this article makes it seem like any program run with Linux has to be made open source and freely available.
The fact is: Linksys saved themselves a whole lot of money by using Linux instead of some commercial OS product to drive their router.
Author is a jerk (Score:2)
Worried About Big Brother? (Score:3, Interesting)
Are you worried about Big Brother? Worry about Forbes:
Apparently they give everyone a PersonID. Guess they slipped up revealing it this time. I actually subscribe to the magazine; I wonder what my PersonID is.Re:Worried About Big Brother? (Score:4, Funny)
Or maybe it just has something to do with it being easier to cross-reference records stored in a database with a unique key, huh? ;)
Didn't look too bad to me. (Score:2)
I think a similar strategy can work in the P2P mess. People who get their networks scanned by vigilante enforcement agencies need to stand up and resist instead of just playing dumb and ignoring it or pretending to hide. You can just wr
Daniel Lyons, the author (Score:5, Informative)
It's my personal opinion not to read too much into the article, and take it just as it is, an opinion -- someone else's view on what is happening.
What does Daniel Lyons have against Linux? (Score:3, Informative)
My Letter to the Forbes Editors (Score:5, Interesting)
I am a technology expert with development and management experience, who has used and overseen the use of GPL software in a variety of very large, very recognizable organizations.
If you choose to use GPL software, the rule is simple and straightforward. You are choosing to take some work for free. The authors gave it away. All they ask is that you, too, give it away.
The GPL is the legal manifestation of the idea that it is wrong to take free work and sell it.
If you read some GPL'd work, and then threw it away and wrote something of your own, having taken nothing, you would owe nothing. But if you take this particular work, you must respect the wishes of those who gave it, and add to their collective efforts in the same way.
The popularity of the GPL is such now that many organizations begin to feel threatend by it. In some few cases, a response to this perceived threat has been a remarkably crafted item of disinformation: that the GPL is "viral."
This is a beautiful piece of propaganda, because it conveys, with gorgeous sleight of hand, that, like a virus, the GPL infects without your permission, or perhaps even without your knowledge.
This is a stunning act of deception. From the front lines, with the benefit of over a decade of experience, I can tell that it is unlikely anyone "accidentally" or "unknowingly" takes from this particular pool of free work. One _chooses_ to take it because it's there, it's free, it's been crafted by a community of people without regard for deadlines or profit margins, and because you can fix it yourself if there are problems. You do this only if you find the compromise of giving away any of your changes or improvements on it to be acceptable. Many places do not take this bargain - as well they should not! And many more places find this kind of cooperation is exactly what the doctor ordered.
If, as a manager, you discovered that GPL code has "appeared" in your program against your wishes, you will never find, in the history of the "Free Software Foundation" any situation where, like SCO, all redress is deemed impossible, and blackmail is demanded. (Indeed, metaphorically speaking, SCO demands it not just from you, but all your customers!) Rather, you will find a patient, polite group of academics and engineers, who are eager to avoid conflict, and happy to let you simply correct your mistake, if that's what it is, by removing the free work from your own.
And you will find that this is so even when, though the obstinacy, momentum and ignorance of a large organization, some people dabble with the idea of stealing this free work from and then not giving their changes back - breaking the rule.
There are, as the author points out, many "open source" organizations and licensees that are less restrictive than the GPL, from which an individual or company may choose from in the event that they still wish to get software for free, yet find the GPL rules unsuitable.
But there is nothing more normal and harmless than the GPL, or the people who enforce it. And I must say, none of their actions do damage to the GPL or its continuing, widespread adoption - in fact, they enhance it, since by making people follow the rules, everyone feels more comfortable in sharing their work. Everyone knows that their contribution won't be simply appropriated by SCO or another unscrupulous party and charged for. Only articles like this, which through what I'm sure are a series of honest misunderstandings, can convey a mistaken impression of how the process works, that might give pause to the concept of sharing labor.
Thank you for your time.
Re:My Letter to the Forbes Editors (Score:3, Informative)
Fighting misunderstanding with misunderstanding only perpetuates problems rather than solve them.
The FSF, and most people who use the GPL, are not against making money (see Tivo), but rather are against the violation of the social contract that the GPL put
The Biggest Hypocricy (Score:3, Funny)
Who pays for this? The 12-employee Free Software Foundation has limited resources. So it seeks donations. And sometimes it collects money from companies it has busted. "
Gee, sounds just like the BSA, doesn't it? Except that the BSA extorts -- uh -- I mean collects -- hundreds of millions of dollars from companies that are guilty of various software licensing violations. Funny that the FSF is portrayed as evil and communistic for doing the same exact thing as the BSA.
BSA = Good
FSF = Bad
What a moron.
Skip reading this? (Score:5, Insightful)
Does this statement strike anyone else as idiotic? If someone doesn't agree with "the community" we just ignore them? Talk about sticking your head in the sand.
Rubbish (Score:3, Insightful)
Rubbish. Absolute rubbish. Whoever wrote this article doesn't understand the first thing about the FSF. Why wouldn't they protect the GPL? You won't have free software if everyone can just use it without contributing back to the source. I don't feel the least bit sorry for these executives. It's clear to everyone that if you use GPL and release a product then you must release derivative works. Come 'on.
Here's mine (Score:5, Interesting)
Choice tidbits (Score:3, Insightful)
From the article...
What a horrible analogy, but it does point out the flaw at the root of the article. The article presumes a double-standard: An entity that develops a product using GPL software has a right to reap the benefits of the foregoing development of that software, but has no responsibilities to the users of that software. Clearly this is contrary to the very core of the GPL.
To try and hammer this idea into the (inflammatory, incorrect, inaccurate) language of the excerpt, someone else laid the foundation, built the walls, and put the roof on. The "house" was never "yours" in the first place.
The author of the article, Daniel Lyons, concludes:
Whoa! Ad hominem and straw man all in one passage. Way to go, Dan!
The expense of the legal action is irrelevant if the GPL-abusing entity intends to win, so this is an admission that the GPL is legally sound and has teeth. Win the lawsuit and take the FSF's $750k in damages and legal expenses. I suspect the targets of the FSF settle because they don't have a leg to stand on.
Here's a message for Forbes: If you think the GPL is bad, tell us why you think it's bad. I'm sure there are plenty of people here prepared to debate you. Don't report that it's bad because companies violate it and get caught. The Chewbacca defense will not save you. (I hope.)
I've no sympathy at all for the companies mentioned in the article. FSF enforcement of the GPL should not come as a surprise to anyone. If you're basing a company on a project using third-party code, due diligence requires you to understand the terms of the license under which you are using the code. Maybe instead of moaning and groaning (via Forbes) when they get caught with their corporate mitts in the cookie jar, they should either abide by the GPL, find a package with a license the imposes fewer responsibilities, or *gasp* do their own development work and pay for it.
Re:Forbes should shut it (Score:2)
Then judge for yourself.
It's always a bad idea to say something that could be taken out of context as slander, so why not just let their own words speak for themselves.
Re:Generate dollars? (Score:2)
Re:Sounds like a Microsoft ... (Score:2)
What you mention is more the LGPL, or 'Light' (or 'Library', i never know) GPL, which allows you to link proprietary a software to for instance a LGPL library.
Thus, glibc is released under LGPL to allow proprietary software to be distributed under Linux and still use glibc
Re:shouldn't read it? (Score:2)
Reading this stuff, while distasteful to some people, is very important; I'm reading it right now. Learning about ourselves from a different perspective will allow us to remove the myths and misconceptions and tell people the truth about ourselves. Avoiding this type of stuff only guarantees that we'll continue acting in a way that the corporate wor
Re:Good Article, Bad Publicity (Score:2)