Red Hat Files for Software Patents 323
Marsala writes "Apparently Red Hat has filed two patent applications for stuff related to the TUX webserver. The patents are for Embedded Protocol Objects and Method and apparatus for atomic file look-up. One has to wonder (if their patents are granted) what their licensing terms will be.... free for open source, or a tool to try and screw other Linux distros?" As reported by Linux Weekly News.
money or principle? (Score:4, Insightful)
Re:money or principle? (Score:2)
--
Benjamin Coates
Re:money or principle? (Score:2)
Re:money or principle? (Score:3, Insightful)
If software patents were commonplace, this couldn't be done--even if you reinvent something patented yourself, you still are in violation of the patent. Even if a few "free software patents" were held, the FS community would never be able to make another free software workalike version of a patented program.
Software patents don't benefit anyone but pattent lawyers, and Red Hat is not doing anyone any favors by trying to legitimize it.
--
Benjamin Coates
Ever heard of cross-licensing? (Score:2)
Re:Ever heard of cross-licensing? (Score:2)
Free software groups can fight that war if they want to, but they won't win. Do you seriously think RedHat or the FSF can out-litigate Microsoft, or IBM, or Sun, or any other big patentholder?
Besides, patent cross-licencing would be next to impossible to integrate with the GPL... The patentholder would have to not just allow Redhat or whatever to use the licenced patent, but everyone, which means that trading with a free software patent company means (effectively) surrendering your patents entirely. Not likely to get many offers on those terms...
--
Benjamin Coates
Re:money or principle? (Score:5, Insightful)
Re:money or principle? (Score:5, Interesting)
Expect a formal clarification from the Red Hat folks about this patent and usage (we didnt think it was news). Expect more patents too. In fact I've got two applications and I need to finish writing up - which I wouldn't be doing unless I was *convinced* this was the only way to do things in the short term, and that generic GPL use would be granted
Alan
Re:money or principle? (Score:2, Interesting)
mixing patent and copyright (Score:5, Interesting)
If you're opposed to (software) patents, I hope you won't limit free licensing to GPLed software. While it may be difficult to implement, mutual defense [mit.edu] is the appropriate patent analog to the GNU GPL.
The intersection of copyright and patent opponents is smaller than either on its own. If you are in both camps, support them separately with copyleft and mutual defense. The enemy of my enemy is my friend, or something like that.
Re:money or principle? (Score:2)
I've got some necessary evil pending as well (Score:2)
First off: I trust you, Alan, if for no other reason than you still have the bullocks to post here. Call me a lemming, but if you're down with the patent thing, then I'm fine too. I don't like patents, yet I have my name on 17 pending patent applications. I'm not sure they'll pass muster, and I'm not sure I'll care either way. They were filed a while ago, when I worked for a very pro-IP company.
Having said that, it *is* a little weird that Red Hat is patenting stuff. The suits want CYA, the lawyers want accountability, but the guys that wrote the stuff you distribute don't like patents. I didn't either, until amazon.com decided they could patent my finger acting upon a microswitch in the mouse on my desktop, then I realized that everyone had better patent whatever they can before the unscrupulous money weasels got their act together. We're well into the 3rd act.
IM(V)HO, patents aren't that great unless you're on the right end of the licensing agreement and I wish we didn't have to have them all. But we need to have them, if only to keep the bottom feeders of the world from reinventing the tux wheel and then patenting it out of existence. If I invent some novel "Method and Apparatus for the Extraction of Novel Nutrients from Common Playground Sand..." and then GPL/BSD/give-it-to-charity, can someone then patent a slightly reworked version and sue me for doing OSS work? Is that the precedence under which the license I pick wants to be tested? So, completely non-hypothetically, is Red Hat taking the so-called pre-emptive strike here?
I'm hoping -- as a very long time RHAT user, and a stockholder as long as there's been stock to hold -- that you guys will use some clout and cash to take out a patent or fourteen for the "good guys", as nasty as the conept sounds. If you have a claim to something novel, than have at it, I say, as long as you give back the key bits to the world. If you don't, then someone else will just patent it and hold onto/license it. So what sort of use to regular humans will be granted with the rights given RHAT by the USPTO? Does your company have a policy for this sort of thing?
I don't mean to grill you, but it *is* weird. Maybe I should think about patenting the process by which an OSS, for-profit company patents new ideas in order to give back to the world by protecting those ideas... :-)
-B
Re:money or principle? (Score:2)
I'm intrigued about this. I hope that they'll do the right thing. I'd like to see an immediate and permanent license to anyone writing code under the GPL, as done by Raph Levien [levien.com], plus a firm statement about free licensing to code under all other OSI approved licenses on request (there can't be a blanket statement as there can with the GPL). But in addition, I'd like to see Red Hat actively working towards reform of the patent system as it stands now.
Re:money or principle? (Score:4, Informative)
If you don't apply for a patent and you use 'your technology' then someone else could more easily take legal action upon you for using 'their technology'.
In this way having a patent means that you get to decide the rules under which the technology (kill me now for using that word) is used. A good patent owner will licence it under good rules, and a bad patent owner will licence under bad rules.
So it all comes down to how we think the owners of this patent will act upon uses of their 'technology'.
I certainly trust Redhat.
Re:money or principle? (Score:2)
The fact that RedHat holds a few patents will not stop them from being sued by someone else for patent violation.
--
Benjamin Coates
Re:money or principle? (Score:3)
No, you don't have to patent. But if someone else patents it, it will cost you a bundle to have the patent voided. A patent is thus cheap insurance.
Frankly, I think getting a patent and promising royalty-free license (except to those who won't do the same to you) makes a stronger statement of principle than refusing to play the game. But it remains to be seen if RH will do this...
Re:money or principle? (Score:2, Insightful)
There is no difference between offensive patents and defensive patents - they're just patents, and it depends on how are used.
If someone achieves a patent, but you have prior art, it's more difficult to prove that you were first because you didn't go via The System[TM]. Disproving a patent via prior art is significantly more difficult than disproving a patent via other patents.
Re:money or principle? (Score:4, Insightful)
You're missing the key feature of patents here. The one "proven" to invent first by virtue of a patent gets the privilege of setting arbitrary license terms for any use of the covered invention. Thus, a patent has everything to do with licensing, and it may be "closed" at the whim of the patent holder at any time.
If it was only about proving who invented first, a system like that used for acedemic publishing would fit the bill just fine. As a matter of fact, such a system would probably do more to "promote useful arts and sciences" for software than patents will. (Remember, promoting arts and sciences was the whole motivator for patents in the first place. Patents were *not* created just to institute a new form of "ownership" so that people can bask in additional property rights.)
Patents were originally intended to encourage people to not keep machines and manufacturing methods locked up as trade secrets, so everyone would benefit (initially from the shared knowledge, and using the invention directly after a few years). This does not match software development. Copyrights allow people to keep the actual implementation details secret for a century, so the patent disclosure doesn't do much good. Anything disclosed in the patent document can be trivially reverse engineered from the software product anyway, since all of the secrets are shipped with the product. The patent provides little if any additional knowledge to the general public. Therefore, due to the nature of software, a software patent provides essentially no value to the public in return for the monopoly granted to the patent holder.
Re:money or principle? (Score:2, Informative)
"having a patent means that you get to decide the rules under which the technology [...] is used"
I didn't say otherwise. I did say that it had nothing to do with specific types of licencing ("Patents have nothing to do with free, open or closedness licencing.") as the original post said "the only thing a patent is good for is to stop people from using an invention".
Ok, bye now!
Re:money or principle? (Score:2)
No. First-to-invent has no relevance to patents at all: if you invent something first but don't disclose it, it's irrelevant that you invented it first. Second, in order to establish that you invented something for the purpose of defending against other patents, a disclosure is sufficient.
Patents are about establishing a limited monopoly on technology. You are right that that can be used for good or for bad. But the responsibility is on RedHat to explain themselves to the community clearly, at least if they want to continue to receive support from the community.
Re:money or principle? (Score:2)
Depends on whether or not you consider being allowed to use somebody else's patent a payment or not.
Most big companies with patent portfolios don't necessarily license them out for money, they'll trade licensing rights with some other company that holds patents they want to use. I.e, if companies A and B each hold patents on some critical component of product Y, they might well mutally license them to each other to allow both to produce the product. (Or, more realistically, A needs B's patent to produce Y, and B needs A's patent to produce Z).
Furthermore, getting the patent yourself is (these days) often the only way to easily prove "prior art" to defend yourself against some other bozo patenting your invention and charging you for it. What's known as a "defensive patent".
Re:money or principle? (Score:2)
Not much use for open source, unless this other company RedHat's swapping patents with is willing to not just license it to RedHat, but to everybody else who gets a GPL copy...
--
Benjamin Coates
Re:money or principle? (Score:2)
Redhat is a public company. Public companies are owned by the shareholders. Shareholders are interested only in a profit. So what do you think?
What about MS in this deal (Score:5, Insightful)
-CPM
Re:What about MS in this deal (Score:3, Insightful)
(BTW - I don't mean to start a gun control thread, just for the sake of argument, okay? Please feel free to post a better metaphor if you can think of one.)
Re:What about MS in this deal (Score:3, Informative)
--
Benjamin Coates
Re:What about MS in this deal (Score:3, Insightful)
Re:What about MS in this deal (Score:2)
No they aren't.
Undefended trademarks are lost. Patents are often submarined (ie not defended for years until the patented idea is in widespread use, then you can sue more people for money), the canonical example is what Unisys did with the GIF patent.
I am not a lawyer. Consult a lawyer if you need legal advice.
Sumner
Re:What about MS in this deal (Score:2)
patents aren't abandoned like trademarks (Score:3, Insightful)
No. Trademarks can be abandoned (i.e., revert to the public domain) if they are not defended against dilution. Patents don't work that way. They can lie in wait for the technology to be more widely used, even if by independent invention. The most public instance of such a "submarine patent" is the GIF patent [mit.edu]. Slashdot has also reported on BT's hyperlink patent [slashdot.org]. Ditto Rambus's SDRAM patents [slashdot.org].
The only obstacles to late enforcement of a patent are public opinion and laws against unfair business practices. The latter is mentioned in the Rambus link above.
Re:What about MS in this deal (Score:2)
As we all know current IP laws are designed for the purpose of being able to apply constraints, that is to say "no. you cannot use".
Perhaps the greatest value of this is to preceive it as a test of weither or not a company can or will follow the FSF/GNU/GPL spirit.
Thee is always Debian.
Re:What about MS in this deal (Score:2)
You can still do that with the patent, and that guarantees (well, in theory) that nobody else will be granted a patent anyway. Given some of the PTO's decisions, merely PD'ing it without a patent gives no such guarantee.
This is what Bell Labs did with their software patent on the Unix SUID bit -- they formally released the patent into the public domain.
Software Patents = Bad (Score:2, Insightful)
Re:Software Patents = Bad (Score:2, Insightful)
No, regardless of what might come after this phrase.
-Chuck
typo? (Score:2)
--
Benjamin Coates
Is "atomic file look-up" something new? (Score:2)
What is there in Red Hat's patent application that is actually new?
What if this could defeat GNU license? (Score:3, Insightful)
Re:What if this could defeat GNU license? (Score:5, Insightful)
I don't think so, but maybe I don't understand what you're getting at. I think these clauses from the GPL [gnu.org] pretty much cover this potential problem (along with the GPL as a whole and the associated rights that everyone are granted who receives GPLd code):
ooohhhh... quoting the GPL on Slashdot... (-1:Karmawhore)
Re:What if this could defeat GNU license? (Score:2)
I suspect this is just a defensive move to protect Linux from somebody else patenting its algorythms, and maybe to get a MAD thing going with other software vendors where RH can retaliate if they start to enforce other patents against Linux.
Re:What if this could defeat GNU license? (Score:2)
However, nothing prevents them from charging proprietary software companies from using the invention described in the patent.
Summary (Score:3, Informative)
The first, "Embedded protocol objects", seems to be saying that if you have a webpage that consists of dynamic and static content then the static content can be cached for faster access. Hardly novel.
The first, "Method and apparatus for atomic file look-up", basically says that it is a good idea if you can see if something is in a cache before requesting the operation that would put it in the cache. Again, not particularly revolutionary.
Re:Summary (Score:2)
Re:Summary (Score:2, Insightful)
The 2nd one is probably the one most likely to have prior art. You'd need to find software which has a cache and which has a "if it isn't in the cache, don't do it at all" codepath.
Personally, I don't mind software patents too much. True, there are some well publicised stupidities; but I feel they do offer protection to smaller inventors.
Pushy companies. (Score:3, Insightful)
Re:Pushy companies. (Score:2)
Let's see...let's count the similarities between RH and MS. #1, RH is the biggest Linux company. #2...oops, no number 2.
What they heck are you talking about?
Re:Pushy companies. (Score:2)
Re:Pushy companies. (Score:2)
If you are not going to trust Microsoft's threat appraisal, what gives you the idea you're better qualified to gauge threats to them? Some vague notion that to beat them you have to act like them? They like that. It's their turf, and they'll bury anyone who tries to play that way.
Re:How so? (Score:2)
Unfortunately... (Score:2, Interesting)
If the US patent office allows you to patent knives and forks, RH is assuming that they will have to patent the spork to guarantee their future rights to use it without paying royalties.
This just shows how sick the patent process is at the moment. I only wonder why someone hasn't patented callable functions--prior art hasn't seemed to be much of an obstacle in the past.
G
Prior art. (Score:5, Insightful)
"Dynamic and static protocol objects are mixed together at a server and included in a dynamic reply to a communication request made by a client application."
Ahhhhm, so a client requests something and a reply is made that is partially dynamic and partially static? So, like php then? Like perl cgi pages? Like any reporting engine ever written?
And, check this out, step by step explainations of how the code works. This shit only exists to keep lawyers happy.
Don't get it.
Dave
claim1 && claim2 && ... (Score:3, Informative)
I'm not going to defend these patents, but keep in mind that the claims are ANDed together, not ORed. Don't read the first claim and exclaim that Red Hat patented reports. It patented a static HTTP server that uses an object cache in an O/S kernel and meets the characteristics of all twelve claims.
The question is, as with all patents: is this a novel, non-obvious (to one skilled in the art) leap from the existing prior art? I doubt it.
Re:Prior art. (Score:2)
Hard to say... (Score:3, Insightful)
But RedHat is a publicly-traded company now, so it has the same "duty to the shareholders" that every other large corporation in the U.S. has. Hence, I have a lot less faith in the company regarding the use of stuff like software patents only for Good. In short, I won't be surprised at all if they use these patents to smack down other commercial Linux distributions, all for Profit at Any Cost.
Only if a Good Guy retains a controlling share of the company would that not apply.
I'm far from being a Redhat apologist... (Score:5, Insightful)
But, as much as I dislike their product, I just get the strange feeling inside, that their company isn't run by the complete and utter assholes we see everywhere else.
To suspect them of pulling any dirty is just damn wrong. Maybe it's just me wanting at least one company out there to be ethical, some really corny wishful thinking on my part, but what have they ever done to you? They deserve an an apology.
Besides, they might be able to stick it to M$ somehow...
Re:I'm far from being a Redhat apologist... (Score:2)
Not to mention if they were, I'm sure some of the more vocal redhat employees would say something about it.
If Alan Cox doesn't even want to come to the USA because of ridiculous idealism (DMCA) - do we really think he wouldn't say anything about Red Hat doing unethical things?
One of Red Hats strengths is the brain trust of talented linux hackers - even if some PHB jerk were to start closing parts of Red Hat Linux tomorrow, methinks we'd see a huge exodus of talented people leaving Red Hat.
Re:I'm far from being a Redhat apologist... (Score:2)
I suspect that you are correct. However, it's largely irrelevant whether or not the people running the company are assholes or not - the company is still required to be competitve and make a profit. Especially since it's public.
When it comes down to it, a company will always choose profits over ethics -- else, it won't survive. This isn't to say that a company can't do good while still making a profit and doesn't mean that RedHat can't be a good member of the free-software/open source community; however, we must always be aware of where their priorities truly lie. If it comes down to it, RedHat will not hesitate to sacrifice the community in order to save itself.
(A good read in this regard is the history of Ben and Jerry's Ice Cream. This is a company that has always tried to do good. Whenever it came down to it, however, they always chose profits over doing good. And for a very understandable reason -- if they hadn't, they would have been bought out by Hagen-Daas or another competitor. Nevertheless, it shows you who they really are.)
Re:I'm far from being a Redhat apologist... (Score:2)
I think that you're misunderstanding what I said; I may have been unclear. I never intended to say that a company will always choose profit over ethics. Rather, when forced to choose between behaving ethically and being profitable, a company must choose profitability -- else, it won't survive.
Second- your term 'ethics' is utterly ridiculous. There are good ethics and bad ethics. Using the word the way you did is the equivalent of saying 'it is temperature outside today.'
From dictionary.com:
ethic:
1. A set of principles of right conduct.
2. A theory or a system of moral values.
Just felt like you could learn from my criticism.
Re:I'm far from being a Redhat apologist... (Score:2)
And I'm going to be watching how they handle this quite closely. I won't say that I disapprove of the move
Their stock prospectus indicated that they would devote much effort to maintaining a good relationship with the Open Source community (I forget the exact wording). So they don't need to abuse this. It could be a good thing. E.g.: "Software may use this patent freely, provided it is licensed under the GPL, and the code is made available to Red Hat. Otherwise special arrangements are available. Please contact our lawyers." If they used that I would have no problem at all. But I can also imagine other scenarios. When there is so much flux, perhaps the wisest choice is to defer decision.
Fear and Lothing in the IT Industry (Score:2)
At this point it might be worth touching on the subject of morality. When something is labeled as "evil" it is a moral judgment. Something is opposed to one's sense of morality. One moral code often expressed within tech circles is functionality. Interoperability and functionality is a goal - anything that intentionally interferes with that goal is "evil". Business morality is often centered around profit. Anything that makes profit can be approved. Tech and business moral codes clash when technology is used to create a (often profitable) dependence on a product by limiting functionality and interoperability through technical or legal means.
Vendors will screw over the average tech worker when the company's moral code moves from a technical one to an aggressive business one. Take a look at Silicon Valley's history. It is chock full of techies starting a business, the business growing, and then the techie is pushed out as the business-types move in. The only question is how aggressive the business types get. It is a part of how corporations work and how "business is done." A company that is "cool" now can change based on who runs it and who decides on company policy and direction.
The double-cross might not even come from the trusted company in question. A company's assets (products, patents, and other intellectual property) often survive the company. The patent that is held "just in case" by the "cool" company of today can be sold off at pennies-on-the-dollar in tomorrow's liquidation and become a tool for its new owner's questionable, aggressive business tactics.
Why the distrust of Redhat? Because we almost expect a double-cross. Its history, nothing personal.
It may not be fair. But then, its not the game that we created. But the rules are well known. And Redhat should be very familiar with them by now. Knee-jerk journalism aside, Redhat should be prepared to explain their situation, their tactics, and provide a system of assurance to their customers and community they work with.
Unless, of course, their moral code has shifted.
Re:I'm far from being a Redhat apologist... (Score:2)
Re:I'm far from being a Redhat apologist... (Score:2)
This has been proposed in the past as a defense. (Score:5, Insightful)
I have only seen one 'iffy' thing ever come out of Red Hat (the RHN server, which is an in-house secret...though they appear to be helpful with the Current developers), so I tend to believe they have no intention of using this offensively against Open Source companies or users.
Besides, I seem to recall the GPL protects us against anyone integrating incompatibly licensed code into GPL software. TUX is part of the Linux kernel, thus it cannot be restricted or fees enforced on its use. Red Hat would have a bear of a time rewriting TUX independently of the kernel (Ingo could do it, of course), but the damage is done. Those inventions (and inventions they are...Ingo does really cool stuff, this isn't a one-click patent folks) are already in the development kernels. We (the community) already own these developments.
So, what I'm trying to say is:
Thank you very much, Ingo and Red Hat. I am very appreciative of the interesting inventions you have given to us. I forward to learning about them, using them, and enjoying the benefits they give us. And boy, that sure was clever of you to patent it, so that Microsoft will have a bit of trouble stepping on your toes in the future. Way to play hardball!
Doesn't matter (Score:5, Informative)
From the GPL license:
Finally, any free program is threatened constantly by software
patents. We wish to avoid the danger that redistributors of a free
program will individually obtain patent licenses, in effect making the
program proprietary. To prevent this, we have made it clear that any
patent must be licensed for everyone's free use or not licensed at all.
The only thing this patent prevents is from others creating proprietary versions of the technology in question; which, IMO, is a Good Thing(tm). In fact, in the thread about this on the LKML someone brought up that the FSF even encourages doing this.
Re:Doesn't matter (Score:2)
From the GPL license:
Yes on that piece of software, but not on the methods or technology.
Re:Doesn't matter (Score:2, Informative)
Whoever brought that up is full of shit. RMS is against software patents, period, end of story.
Yeah RMS isn't the entire FSF, but he basically sets the policy. And you won't find any official documentation or website backing up that claim that the FSF encourages patents on Free software.
Please refrain from passing along bogus info like that in the future unless you can back it up....
Re:Doesn't matter (Score:2)
Does that "everyone" cover the entire world, or only those using GPL code that incorporates the patented stuff?
Re:Doesn't matter (Score:2)
License terms. (Score:2, Insightful)
What's the big deal? The GPL is pretty clear on this: So, Redhat can't use these patents in an abusive manner unless they're going to release this stuff in some kind of software that's released under a GPL-incompatible license.
Last i checked, Redhat had a policy of releasing software they write under Free Software licenses. So unless i'm badly mistaken, or Redhat is moving away from Free Software, which i haven't heard they were doing, then this is nothing at all to worry about.
Now, if redhat were going to announce they were going to start writing software and releasing it under non-free licenses, i would be worried indeed.
But for now.. Haven't you people ever heard of a defensive patent? Maybe a bit unecessary, maybe a bit worrying, but this isn't the end of the world.
- super ugly ultraman anonymous cowards filtered. if their comments aren't worth so much as a nom de plume why should i read them?
Damn right they should file patents (Score:5, Insightful)
So Redhat has done some significant work on the TUX webserver and it's patentable. They should DEFINTELY file those patents.
Now don't get me wrong. Software patents are generally bad news - they are too long (even 10 years in software is an eternity) and a lot aren't even worth the paper they are written on. But for the software industry today they are part and parcel of developing software and protecting the work that a software company has put in.
Patents aren't like trademarks - there is no 'patent dilution' to worry about. So RedHat can be extremely selective about who is allowed to benefit from the patent (even free of charge) and who is never going to get a license. This is particularly important - MS has a vested interest in watching over a lot of the developments in the TUX webserver as TUX is the main performance competitor to IIS. If RedHat patents its best ideas, it makes a public record of the 'invention'. If MS patents something that RedHat came up with, yes, prior art may be used to fight a legal battle to have the patent nulled but that is considerably more expensive than simply patenting the good stuff first.
Now I look forward to the day when software patents last 3 years from filing (because I dont see software patents ever going away totally). I look forward to the day when all software patents are published PRIOR to the patent being awarded so that many eyes may suggest prior art challenges. But until that day comes, Free and Open source companies had better use the weapons at hand to protect their assets. And if that means filing patents so be it.
Cheers,
Toby Haynes
Re:Damn right they should file patents (Score:3, Insightful)
Copyright is a protection of (intellectual) "work". If you really want to "protect" your work, don't open source it. Patents are a protection of inventions - new, original, non-obvious inventions - not just work. Just because you've done some "work", you shouldn't be able to charge people who want to do similar things.
RedHat can be extremely selective about who is allowed to benefit from the patent (even free of charge) and who is never going to get a license.
So now a single patent can be used to completely exclude any company, individual or group of individuals from doing something someone else did first? You really think this is a good thing?
So open source people should beat Microsoft through patents ? Yeah, forget all this technical work, making a better, more secure and reliable product than theirs. It's too hard. Let's just hire a couple of lawyers, and keep filing patents until we get one really good one we can really screw them with. That'll really make the world a better place for 100's of millions of people, won't it.
What if Red Hat gets sufficient patents to really hurt Microsoft financially? What happens then? If Microsoft are really hurting, they would just have to buy Red Hat. Remember that $40 billion in cash? Screw everything else in the company. Hell, it'll probably also hold up the development of Linux for a good few months. Not all the programmers will be able to find jobs elsewhere just like that, even if the Alan Cox's and similar are famous enough to do so. And then Microsoft get the patents. And then they can use them to screw over the rest of the world - especially the Linux community.
No, using patents in this way is not good. Look on it as a necessary evil at best.
I agree with your last paragraph, but I look forward to the day when big companies and small have all become so sick of being screwed over by patent leeches, and third-world countries with a more enlightened attitude to progress and fairness on this issue have begun overtaking the USA, that the whole concept of software patenting ideas (in the USA and everywhere else) has been thrown out.
You build a Project. (Score:2)
Sounds like what MS did. (Score:2)
It reminds me of how MS came along in the very early days with dirt cheap prices and was basically the savior of the microcomputer world. before then nothing existed beyond Unix. Unix was EXPENSIVE! DOS was comparatively cheap. Microsoft seemed like everyone's buddy back then, before they started to charge exorbitant fees and put an iron-tight contract in their software in the form of a EULA.
Since RedHat is in this world to turn a profit (and make no mistake about it, offering your products for free isn't very profitable), they are looking at an alternative way to produce. Will they be the next restrictive MS, or is this simply a neccessary "evil"?
A counter action to MS anti-GPL license. (Score:2)
An excellent strategy (Score:3, Interesting)
Given that they appear to be the way of the future (even in Europe, the organised eurolinux campaign seems to be struggling to hold off the "overly enthusiastic" patent office), the Free Software community should definitely use them when they discover nifty algorithms.
As someone above pointed out, the GPL guarantees that any GPL-dependent organisation (such as RedHat) will have to license software patents on a royalty-free basis for GPL software. It would be better to license them for all DFSG-free [debian.org] code. Note that such a license would not apply if, for example, Microsoft took some *BSD code an incorporated it in Win2k, because it's no longer DFSG-free.
The only question then is whether you charge royalties to proprietary software firms for use of the patented techniques, or whether you exclude them completely...
Gilmore Patent (Score:3, Interesting)
The only thing that concerns me about this idea is that it seems like it might be easily circumventable, you could do something like set up a subsidiary that doesn't have any patents, and then funnel the money back to the parent company. Any IP lawyers out there have a feasibility assessment of this idea?
Websurfing done right! StumbleUpon [stumbleupon.com]
Re:Gilmore Patent (Score:2, Interesting)
A Gilmore Patent can be Licensed (Score:2)
Re:Gilmore Patent (Score:2)
The only possible problem is that you will likely never see revenue from the patent, from other sources. Most licensees will insist on a "favored nation clause" that basically says that they won't be charged more than any other licensee. Clearly in this case, that would not be possible. So, I doubt you'd find many takers for the license. Remember that getting a patent is relatively expensive. If you hire a patent attorney, it'll run between $10-15K, just for the US. If you do it on your own, expect to spend 100 hours if you're inexperienced (about 40 with experience), and approximately $2000 for a patent. If you want international protection, multiply by 10 or 20. So, if you'll never see revenue from it, you're unlikely to get funding based on it, and you can't trade it for protection against other "evil" guys, what's the point of spending the money? You'd be better of using either Statutory Invention Registrations (cheaper, no examination, simply publishes the idea & documents your date), or publishing your ideas.
Thalia
What's wrong with software patents anyway? (Score:2, Interesting)
It is a separate matter that the vast majority of the software patents are absolute garbage (like the (in)famous one-click shopping), but so are the patents in other areas (like Rambus, and that guy who patented sideways swinging...)
Re:What's wrong with software patents anyway? (Score:2)
--
Benjamin Coates
Re:What's wrong with software patents anyway? (Score:3, Informative)
Software is too easy.
If you start dressing it up with fancy vocabulary you can make it seem difficult. For example method and protocol objects sounds really difficult but if you just want to build a webserver into the kernel it's under 200 lines of code. Sure that's khttp vs TUX but you could just add 100 lines of code at a time and very soon khttp would be as good as TUX. Which 100 lines of code is worth a patent?
Bio-engineering is different because each product is just one or two ideas. Software is built from combining ideas. Any large project is 1000's of little ideas. If 100 of those ideas are patented what are you going to do?
The truth is that part of the reason that software seems different is because I am involved in it. If I made medicine in my spare time then I'd probably think those type of patents were bad too.
Re:What's wrong with software patents anyway? (Score:2)
void ()
{
cout"Hello USA"
}
No prior art, the closest thing is Hello World program, but it's not the same thing. It's a new invention, so should I be able to patent it and collect royalties everytime the code is used? Software patents are just mushy things that don't really help much. You don't want people using your code, close the source.
Re:What's wrong with software patents anyway? (Score:2)
That's not true at all. Computers are patentable machines just like anything else, but software does not describe the operation of a computer, it is data which is input into the computer.
Patenting software is equivalent to patenting the words cut into a printing press roll.
Patent-wise, the situation has been quite unfair to programmers until recently [...]
It's not unfair to programmers because programmers aren't inventors, and they know it. Programmers create programs by taking a specification and translating it into machine-readable code. It's not a mechanical process, but there are well-known techniques and it's usually pretty straightforward. There is no invention going on here--any competent programmer could write any program given sufficient time.
otherwise patents would become enormous collections of huge diagrams showing the placement of charges in capacitors, or magnetic domains on a disk, or pits burned in a CD read by laser.
CD pit patterns aren't patentable, they aren't an invention, they're data and they have copyrights.
Do you believe that books should be patentable? How about literary "inventions"? There has been substantial change in the state of the art in writing over the years, isn't the denial of patents unfair to writers?
--
Benjamin Coates
The patents will never be granted (Score:2, Funny)
Legitimate Reason? (Score:4, Insightful)
Maybe someone at Red Hat thought they should get a patent on it before some asshole from another company did. If Red Hat patents the technology they can let anybody or nobody use it - at least they have control. Some outside group might have gotten a patent on the concept and held it hostage, forcing all users to pay.
I'm not a fan of silly IP actions, but Red Hat filing for a patent is NOT the same as Red Hat preventing others from using the technology. There are occasionally good reasons for this stuff and you should wait and see what the company does before you jump on them.
Re:Legitimate Reason? (Score:2, Insightful)
The idea of "patenting it before some other asshole does" is unreasonable. Once I invent something, the patent cannot be granted to someone else who patents it post that invention because it is not an original work. If I can prove prior art (ie that I made the invention before that time), the patent will not be granted/invalidated.
but.. isn't this what you wanted? (Score:2, Informative)
But now all are complaining about how it's patenting things.. Well, that may be, but going by the title of the patents, they look like they could be actual legitimate patents. Nothing like the whole wheel thing that went on.
So.. they might be on the way to proprietary code, closed source, and all that.. Well, GNU will keep it open. and we all like open because, unlike how Micro$oft does it, it allows people to fix bugs and work with the code they're given. So.. it's not bad there, either, imo. Or at least it can't be.
So.. give Redhat a break. They have to make money some way, and this may be what works on their end. Even doing what it's doing, it seems to be being nice.
Just my few pennies. But what do I know.
-DrkShadow
To Open Source a Patent? (Score:2)
Paranoia Runs Deep (Score:3, Insightful)
Of course, RedHat has to *compete* with other Linux distributions, but "screw" them? I seriously doubt it.
Red Hat is not my favorite distro (although it is one of several that I use), but It's a pisser to see all the irrational, unfounded RedHat bashing that goes on.
Red Hat is one of the biggest Linux distributors (probably *the* biggest here in the US), and many people seem to feel that just because they are big, they are also evil.
First of all, TUX (and most everything else that Red Hat has added to its Linux distro) is licensed under the GPL, and others have pointed out that the GPL provides that a free license effectively be granted for any patented part of the code. (The method and apparatus are still protected, which gives them the protections they are trying to get against MS and others using the technology in a proprietary product). On this point alone, any fears of Red Hat screwing other Linux distributions seems little more than paranoia.
Red Hat is by no means a perfect company (is there such a thing in the real world?), but they have gone out of their way many times to help and assist the goals of Linux and open source in general. Of course doing something for Linux as a whole also benefits Red Hat, but because of the nature of open source it also benefits everyone as well.
Many people don't seem to realize that because they are bigger than most Linux distributors, they have some extra reasources that others don't have to apply to general causes. For example, pushing Linux in education, lobbying to fight really bad laws like the DMCA and the Hollings Disney protection act, providing the credibility and support to get Linux into large corporations, and many other things that in the end will benefit everyone in the OSS world.
Moreover, Microsoft has shown the ability to steal ideas from others. Software patents may be bad in general, but Red Hat is actually acting responsibly to protect IP that they've licensed under the GPL. Assuming the patents are valid, which I'm admittedly not in a position to evaluate, this will give them the ability to further protect the ideas in the GPL'd code from abuses by MS and others while still making the technology transparently and freely available to the open source community. Because the code is GPL's, the patents are actually a benefit rather than a liability.
old hat (Score:2)
Patents, Red Hat, Free Software (Score:2, Informative)
The more patents that the Open Source community can secure, the more software that can be developed open source without fear of MS, Adobe, and other proprietary software vendors saying "Hey you can't do that without paying us royalties we have the patent".
All of you with your conspiracy theories about Red Hat trying to make linux proprietary are nuts. They know very well that if they did that, it would mean +90% of their customers would instantly abandon ship in the name of Free Software.
In talking with my father, the best thing Open Source software can do is apply for patents, while this causes the "inventions" to be owned by someone instead of "the community", there is no law that says if you have a patent you have to charge royalties. Therefore, the more "free patents" we can get, the more software/ideas/code is protected from proprietary companies who, if they had the patent would charge royalties.
Don't point at Red Hat (Score:3, Interesting)
Software patents are ridiculous - they are the work of ONE MAN who both pushed the idea as a practice and later became a judge and ruled on the legality of his own creation! . Can you say "conflict of interest"? Historically software was properly ruled out as being unpatenable.
This is not Microsoft ...yet (Score:2)
I really would wait and see what happens. If they start throwing cease and desists and legal suites around, that would be a better time to start an outcry.
RedHat, welcome to the business world (Score:2)
I can't blame RedHat, they are in this for the business, you can't give away everything if you are going to make a profit.
But I can't say that I like these kinds of patents, the are not good for a free market, for healthy competition, nor for non-profit software or the users.
Something needs to be done.
It's not about killing other open source projects (Score:2)
Software patents are evil, yes. But if you can't get rid of them, you unfortunately have to play the dirty game if you don't want to be sued for infringing on patents like "text in a window".
There are several things I totally dislike about Red Hat (such as their ultimately stupid choice of default desktops), but there are plenty of other things that keep me here, like the strong commitment to Open Source.
If that were to change, I'd be out of here the same day.
As long as you see my posting from a *@*redhat* address, don't worry about things like this.
Re:and from the looks of it (Score:2, Insightful)
Where have you been, man? This stuff has been opened up. It is in development kernels already. Heck it might even be in the shipping Red Hat kernel (TUX was offered in my most recent Red Hat installation, and these patents regard nifty stuff Ingo wrote for TUX).
These things are a part of the kernel. Red Hat can't help but open it up.
Re:Just like RedHat (Score:2)
Re:So what? (Score:2)
Can we limit the use of this software to paying customers (despite the inclusion of source), enforcable through such things as the DMCA.
Can we refuse to let people reverse engineer and redistribute the software?
Can we limit the source to only paying customers?
It's not a matter of closing software and making proprietary software to earn a buck (see Apple's Aqua for that). That tactic is fine with me, release something for an Open Source OS that's proprietary, as long as it's released under that licence. But what happens when you start patenting GPL software? That's what makes this interesting.
Re:What's the problem? (Score:2)
Re:The GPL trumps all. (Score:2)