HP Calls For Sun and IBM to Remove OS Licenses 424
Rob writes "Computer Business Review is reporting that in order to help nudge Linux and open source
software further into the enterprise, a vice president at Hewlett-Packard Co yesterday
called on rivals IBM Corp and Sun Microsystems Inc to invalidate their open-source
software licenses in favor of a free licensing model. During his keynote at the LinuxWorld
Conference in San Francisco yesterday, HP's vice president of open source and NonStop
Enterprise Martin Fink commended the Open
Source Initiative on setting up new rules to limit the growth of open-source licenses." From the article: "He asked IBM to deprecate its open-source license and instead put it under the General Public License, the most popular license for free software that gives users the freedom run the program for any purpose, to study how it works, to modify and improve it and distribute copies. In contrast, an open-source license, like IBM's, is copyrighted. Fink also called on Sun Microsystems to deprecate its Common Development and Distribution License (CDDL), which applies to OpenSolaris, GlassFish and JWSDP, and to re-license Solaris 10 under the General Public License, which drew the crowd's applause."
A lot of hot air (Score:4, Interesting)
(first post?)
Re:A far more interesting story (Score:4, Funny)
Wow, these kind of sentiments, and your User ID is 707389? What time frame do you believe constitutes the "Good Old Days" of Slashdot, last week?
s/GPL/BSD/ (Score:4, Insightful)
And the fact that Compuware wraps PMD and calls it OptimalAdvisor [compuware.com]? More power to them! Maybe they'll contribute a bug fix or two, and maybe I'll sell a couple more copies of the book [pmdapplied.com]. A rising tide, as it were...
Re:s/GPL/BSD/ (Score:5, Insightful)
The BSD is a great license, but that is actually a -weakness-, IMO - that anyone can take BSD code, make a new product out of it, and not have to release those changes back to the community.
It's called leeching.
Re:s/GPL/BSD/ (Score:4, Insightful)
Re:s/GPL/BSD/ (Score:2)
Yes, for people who want to make easy money on work done by community people. GPL can mean protection. Protection that your work won't be stolen by sensless FOSS-opposing jerks and sold for money without giving credit.
Re:s/GPL/BSD/ (Score:4, Insightful)
Re:s/GPL/BSD/ (Score:2, Insightful)
Or perhaps Free From Hidden Agendas.
Free From Politics.
Free From Misinterpretation.
Re:s/GPL/BSD/ (Score:2)
Re:s/GPL/BSD/ (Score:2)
Re:s/GPL/BSD/ (Score:4, Informative)
There is no way whatsoever that licensing under the BSD is worse than the GPL, unless of course the real reason you want to give away code is not to help others, but rather to benifit yourself.
How do you benifit yourself? You force others to put changed under YOUR license of choice. This means you get access to their changes whether they want to be nice or not, and it may also push your political agenda by forcing people to use your particular philosophy bound license.
Then, there is always the spitefullness aspect of the GPL. "If *I* can't make money off the code, you sure as hell won't either!"
So what is your motive? Greed, Power, or Spitefullness?
Re:s/GPL/BSD/ (Score:2, Insightful)
Am I trying to help everyone, regardless of their motive, or am I trying to promote the common good.
I've got an GPL licensed axe. I'll lend it to you if you want to build a log cabin, or cut firewood for yourself, or if you want to make a better axe that we can all share, you may borrow it.
If you want to use it for something I consider morally wrong (say, murder) then you can get your own fucking axe.
Similarly, I've got a GPL house. If you need shelter, you can come in. B
Re:s/GPL/BSD/ (Score:4, Insightful)
The secondary purpose is to create a culture of sharing. You could view it sort of as the difference between a potluck and a soup kitchen.
Re:s/GPL/BSD/ (Score:3, Informative)
Re:s/GPL/BSD/ (Score:5, Insightful)
No, it's not a weekness any more than the GPL's requirement to provide source code is. Choose the right license for what you want to do, and you'll have no problems. For example, the Apache project works on the idea that providing a common code base instead of reinventing the wheel at 500 different companies is a good thing. Thus they provide code (donated by many of those same companies!) under the BSD license specifically so the software *can* be commercialized.
In the case of Linux, control over the source code is a more important feature than not reinventing the wheel. Thus it's under the GPL license.
You people need to wake up and remember the programmer's addage, "Use the right tool for the right job!"
Re:s/GPL/BSD/ (Score:2)
Companies CAN licence GPL'd software, they have to go to the software's copyright owner, and if that owner is willing, negotiate a different licence that suits the company in question.
Re:s/GPL/BSD/ (Score:3, Informative)
The problem lies in... (Score:2)
So many proponents of the BSD license seem to think that it's a magic bullet for everything and insist in BSDing all the code. For example, in the case of the discussion here, someone suggested that they BSD the stuff from IBM and Sun- because it was a better license for everything so that people wouldn't have their hands tied with use.
This is so dead wrong it's tragic.
In this case, you'd want
Re:s/GPL/BSD/ (Score:2)
Re:s/GPL/BSD/ (Score:2)
True! There's a tradeoff there though - how many folks will _not_ contribute since they want to stand clear of the GPL? I'd rather give those folks a safe way to contribute, and I've got zero interest in tracking down GPL violators.
And it seems to be working out well - check the contributors [sourceforge.net] page. Most of the real interesting stuff in PMD has come from other folks... like the data flow analysis stuff, for example. I want to avoid any chance of scaring away those folks
Re:s/GPL/BSD/ (Score:2)
Not many I would think, they can contribute their code with a BSD or even public domain licence and you can still use it in a GPL codebase. Or didn't I understand the problem?
Re:s/GPL/BSD/ (Score:2)
> BSD or even public domain licence
Right, but I think their concern is that they may "contaminate" themselves by looking at the GPL'd code. You know, it's like looking at CDDL'd code; if those ideas show up in your own code later and someone traces it back, bad times. Better to just stand clear, you know?
Re:s/GPL/BSD/ (Score:2)
We may wish that the authors had chosen a different license, but we respect their wishes.
Note that we *use* GPL software (cygwin, gcc, etc...), but do not incoroporate it into anything that we redistribute. I, for one, would love to contribute code back for the part
Re:s/GPL/BSD/ (Score:2)
Re:s/GPL/BSD/ (Score:2)
Although the BSD license has its place, I think the GPL is superior in the arena of source changes.
I'm all for being able to change the code, and if you distrubute the modified code, everyone should be able to see what you modified. That is what the GPL license gives us.
Re:s/GPL/BSD/ (Score:4, Insightful)
As opposed to the GPL's form of forced reverse leeching?
Using the GPL is like saying, "If you don't follow my rules, you can't use my tools."
That's fine. I have no problem with authors choosing whatever license they want.
I would argue that *more* freedom comes to the user with software licensed under the BSD license. I have fewer restrictions when I choose BSD licensed software.
When I choose to license software under BSD, I am choosing to allow my users greater freedom than the GPL provides.
My community contributed software is a gift of my time and resources. I feel that gifts should come without strings and without expectations.
-Adam
Re:s/GPL/BSD/ (Score:2)
Therefore, GPL'd software is NOT a gift. It is simply a resource that one may choose to use or not use. If one uses this community resource are bound by the restrictions outlined in the license.
-Adam
Re:s/GPL/BSD/ (Score:2)
If your tool is complete and you don't want any help with it, and people should use it freely, use the BSD license.
If you want to see it improved and become something greater than one man's labour, use the GPL, because that's the only way you'll ever see the improvements.
By using the GPL, it says "look, I put some effort in here - you can use it for free, but all I expect is that if you do something cool with it, you do the same thing I did". This seems
Re:s/GPL/BSD/ (Score:2)
GPL: The cynic's license.
-Adam
Re:s/GPL/BSD/ (Score:2)
I don't believe the OSS community would have gotten half as far without the GPL. People are selfish - that's how the economy works. GPL means that free-software is compatible with the selfishness of the human race. Anything else is idealism.
Re:s/GPL/BSD/ (Score:2)
Well hell... somebody better let these [netbsd.org] guys [freebsd.com] know [openbsd.com] then.
Re:s/GPL/BSD/ (Score:2)
Re:s/LGPL/BSD/ (Score:5, Insightful)
Re:s/LGPL/BSD/ (Score:4, Insightful)
I mean how many Linux users really contribute back to the Kernel?
People used to be afraid of companies running off and locking people buying HW to a given OS.
Now because most OSS is written by kids [e.g. 25] they're just afraid of being left behind and not noticed.
The actual motives for a GPL or BSD or whatever license rarely has to do with the original goals.
Becase, really, if you want code to be just out there for folk to use you could make it public domain [like I do
Tom
Re:s/LGPL/BSD/ (Score:2)
Yes, to use, not to sell, without having been no contribution initially. Now that's what leeching is IMO.
Re:s/LGPL/BSD/ (Score:3, Interesting)
When I write code, I want as many people as possible to be able to use it, so I choose the BSD license[1]. If someone makes a closed-source product out of it then their customers will ben
Re:s/GPL/BSD/ (Score:2)
The important point of GPL is that it lowers entry barriers into the market - as distributors of GPL software must release all their changes back a newcomer with a neat idea can easily release a product that is just like the competition plus one improvement.
If you change all licenses to BSD than the first company that will not be a good corporate citizen
Re:s/GPL/BSD/ (Score:2)
The Original BSD software is still out there. Did the TCP/IP stack for FreeBSD stop working when Microsoft copied it? Did Microsoft then have a monopoly on TCP/IP stacks? NO! THINK!
Re:s/GPL/BSD/ (Score:2, Insightful)
Self interest (Score:2)
Well there's a healthy attitude.
Do you think companies are contributing to the GPL because they are forced to? Naw. They are contributing to open source software because it's in their best interest to do so.
For example, many large companies (eg, IBM) would like to develop their products for a popular operating system that is not under the control of a competing company. They don't want to be held hostage to MS.
As well, many comp
BSD's okay... (Score:3, Insightful)
Sadly so many BSD advocates just don't get this concept. It's not tha
no one-size fits all (Score:2)
However, BSD alone is not enough to cover all the needs of open source software. I have made available code under all three licenses, depending on what objectives I had in mind. Just because you think that BSD works for your project doesn't mean that it works for all projects. People who pick the GPL generally do so deliberately and after a lot of thought, and the success of G
Re:s/GPL/BSD/ (Score:2)
You've just described EXACTLY what the GPL is, BSD license with a requirement to feed changes/enhancements back into the program. That is what the license does, period.
With the BSD license a company is much more likely to take the BSD'd code, and then that's it. For example, microsoft's TCP stack.
Re:s/GPL/BSD/ (Score:2)
They wouldn't be stealing anything, as the license allows that kind of use.
If you try to see BSD-like licenses from the perspective that "close sourcing" == "stealing", then you might as well just avoid it.
Re:s/GPL/BSD/ (Score:2)
If it's published under BSD license, it can't be stolen, stupid.
And if MS uses it (in) Windows Linux (Microsoft Linux, it's going to compatible with Linux (or BSD). What's wrong with that. If they want to invest resources in further code development and fork it, it's their money...
And if you dont' want to use their stuff, just use the original/free BSD code.
And then... (Score:5, Funny)
Re:And then... (Score:3, Funny)
Shit!
Why (Score:3, Insightful)
On another note, did anyone else find it ironic that he is trying to push the ideals of software freedom of creativty and expression...by locking everyone under the same license?
Re:Why (Score:5, Insightful)
Nor why HP doesn't think its good for themselves either. From http://h18000.www1.hp.com/products/quickspecs/120
Yes, I did. I also agree with another poster that suggested maybe the BSD license vs. GPL. The GPL license is not very attractive to many commercial software companies, and may also conflict with other contracts that they are already bound to. In general, the BSD license is much more appealing to commercial endeavors. The BSD TCI/IP stack should be a sufficient example.
Re:Why (Score:3, Insightful)
If you're talking about commerce that wants something for free, yeah. If you're talking about firms that have something and are considering giving it away, they I'd say 'bullshit'.
Any example of contracts that prevent release under GPL while permitting it under BSD licence would be greatly appreciated, cos I don't think any exist.
Justin.
The GPL is great for a commodity OS. (Score:2)
It may, but it should not if it is only the OS.
I can see that for apps running on the OS, but not for the OS itself or components of it (as with your TCP/IP stack example).
For a commodity OS, developed by many, used by many and
Re:The GPL is great for a commodity OS. (Score:3, Funny)
Yeah, under the GPL we only see something called GNU/forking, which is just great.
Re:Why (Score:2)
How about IBM and Sun just not list their licenses (Score:2)
Re:How about IBM and Sun just not list their licen (Score:2)
-russ
*rolls eyes* (Score:4, Insightful)
This seems like meaningless posturing for positive HP market spin. I don't see why two other companies would listen to the head of HP, when they haven't really been listening to the community itself for years.
oh noes (Score:5, Funny)
at the risk of sounding like an idiot (Score:2)
Re:at the risk of sounding like an idiot (Score:2)
Re:at the risk of sounding like an idiot (Score:2)
The details of HP's contributions can be found on http://opensource.hp.com/ [hp.com].
It is true that the older systems like HP-UX, Tru64 and VMS aren't GPL'ed, but as I said in another post, it's probably very difficult to do so without either heavy recoding or relicensing of other codebases.
--Ng
GPL is Copyrighted too (Score:5, Informative)
In contrast? The GPL and works released undef GPL are Copyrighted too. GPL doesn't work without Copyright.
Re:GPL is Copyrighted too (Score:2)
Tom
Re:GPL is Copyrighted too (Score:2)
Re:GPL is Copyrighted too (Score:5, Informative)
Every item asserted by the above paragraph is untrue. Just an FYI for the casual reader.
Re:GPL is Copyrighted too (Score:2)
Um, that's not true. The GPL has been copied probably millions of times, and the FSF has never objected to it, nor asked for a fee, etc.
They do disallow derived works, and it's perfectly obvious why they should.
HPUX Open Source! (Score:2, Insightful)
(NOT!)
-Matt
Anything licensed with the GPL is copyrighted (Score:4, Informative)
There is a lot of confusion... (Score:2, Informative)
There is a lot of confusion around there about what exactly is open source, free, copyrighted and/or proprietary software.
I suggest to everyone to read the Free Software Definition [gnu.org] and the FAQs about the GNU GPL [gnu.org].
Yeah, even if you don't like RMS read them: they are very informative!
Re:There is a lot of confusion... (Score:2)
There is a lot of confusion around there about what exactly is open source, free, copyrighted and/or proprietary software. I suggest to everyone to read the Free Software Definition and the FAQs about the GNU GPL.
That's not "free" it's "Free" - it only applies to the FSF use of the word. To paraphrase Nietszche, "there are freedoms but no freedom".
laptops (Score:2)
Pot calling Kettle... (Score:5, Interesting)
My company that just purchased 3 computers from HP. There was a total of 5 dual core CPUs. We had to purchase 10 licences for HP-UX 11.11. Utilities that were an extra charge had to be purchased on a per CPU basis as well. A utility that cost $300 ended up costing $3000 even if it was only used on one machine. And they have the nerve to tell other companies to make their licences free???
HP, if you want others to change their licences, lead by example.
Re:Pot calling Kettle... (Score:5, Informative)
Be fair. Martin was simply saying that if IBM/Sun/HP/whoever is going to release software under a free license, then it would be preferable to release under a single, well known license - the GPL. HP's techies and lawyers tend to agree (in as much as techies ever agree about anything) that the GPL is the best way to give stuff to the free software community while protecting HP's intellectual investments. In other words, it will only give away stuff in the knowledge that some leech won't just take it and make the code non-free. And HP has released a lot of code under the GPL.
So he wasn't saying that Sun should open up everything including Java, or that IBM should free up AIX/Tivoli/etc or such things: just that the proliferation of licenses adds to market confusion.
Lastly, HP can't just open up HP-UX without a huge amount of work; there is code in there which is licensed under arrangements incompatible with the GPL. Case in point: HP licenses the SVR4 codebase, and I believe there is some ongoing litigation involving the contract conditions around that. Can't quite remember the company's name...
Scoff? Scold? Squelch?
--Ng
Re:Pot calling Kettle... (Score:4, Interesting)
Re:Pot calling Kettle... (Score:3, Interesting)
Yes, I did. But what I don't know is what Sun's contract language with AT&T/Novell/SCO states they can and can't do with it. SCO specifically stated that Sun was in the clear, which implies that they have a different contract term from the other SVR4 licensees. NB: I am not speaking from knowledge here - just pure speculation.
--Ng
Re:Pot calling Kettle... (Score:2)
I believe HP was asking Sun and IBM to make their free software free in a more
standard way. I don't think HP was suggesting that Sun and IBM make free things
that currently aren't free.
OSS, not OS (Score:5, Insightful)
Can we please refer to Open Source either using the phrase "Open Source" or with the abbreviation "OSS"?? The "OS" usually stands for "Operating System".
So the headline of this article read to me like "HP calls for Sun and IBM to remove Operating System licenses" which is completely different from what the article was about.
</soapbox>
GPLed Software Not Copyrighted? (Score:3, Insightful)
I guess the hardest part of journalism school is learning to talk out of ones ass.
For those who, like this reporter, don't know: Any material must be under copyright for the GPL to apply.
J.T.F.C.
-Peter
Copyrighted? (Score:2)
Whoever wrote that doesn't appear to know what "copyrighted" means.
The GPL is "copyrighted", too. Software published under the GPL or IBM's license or Creative Commons or Microsoft's EULA* is copyrighted. Almost everything is copyrighted, except things which have been put or have at last fallen into the public domain.
The li
Just to be clear... (Score:2)
Unless I'm mistaken, and I don't think that's the case this time around, copyright remains in effect under the GPL. All it is is a license that says you have more
Re:Just to be clear... (Score:2)
Wasted effort (Score:2)
By the way, the executive would have taken this chance to announce that HP has placed all its software under the GPL that he seems to worship. Of course he didn't. Why? Because
Fink confused on licenses (Score:2)
However, the devil is in the details. I agree that Sun's CDDL is a mess, and replacing it with GPL would be great. Or with BSD. Or with MPL or IBM's PL. But IBM's license is quite good--in fact, probably better than GPL at this point, since it deals with patents, requiring non-discriminatory treatment by patent holders. IBM's PL is most certainly a Free Software license, as we
Re:Fink confused on licenses (Score:4, Interesting)
I have no idea how Sun ended up hated by Slashdot. They sell Linux, they open-sourced the Solaris kernel, they have cooperated with OSS operating systems to get them running on their hardware. Lets not forget a huge donation in the form of buying StarOffice and immediately open-sourcing it. The completely open and royalty-free SPARC architecture (as opposed to the far-from-open PPC). Few companies have done more.
There have been some back and forth on how they perceive Linux, but considering that Linux has been eating Sun's marketshare quickly the last decade they sure seem to have a very good relationship with Linux and related technologies.
This just pisses me off! (Score:5, Insightful)
Yes, HP
Before HP opens its yap, I want to see the source for HPUX, and CDE.
You know, that OS where you can't use local variables named "u" in kernel code (just like 30 year old Unix).
But NOOO - HP feels they must shoot at IBM and SUN for the (Open Source approved) LICENSE -- AND PEOPLE ACTUALLY CLAPPED?!?!?
Ratboy
Competitors? (Score:2)
If MS declared that Apple should open-source more of their offerings would it make news? Maybe only so we can lau
Sun won't GPL Solaris (Score:3, Insightful)
Misleading article title. (Score:2)
When Martin Fink talks... (Score:2)
To GPL or not to GPL ... (Score:3)
A much more reasonable request of IBM and Sun might be to ask them (note: not DEMAND!) to consider dual licensing. Obviously they see some advantage to their licences, and presumably they thnk their users do too, so lets see which license people adopt. Its not unreasonable to require that users of their code state at the time of aquiring the code which license they are aquiring under -- no picking the license to match the circumstances -- make people think about what they are doing.
As to the question of which is the world's most wonderful OSS license, well, I have some personal reservations about GPL -- which doen't mean that I don't think that the GPL does not have its place, and that it couldn't be improved.
That said, I also have a lot of sympathy for the point of view expressed by Pamela Jones when she says that it is the GPL and only the GPL that has destroyed the pirate raids of SCO and put them into a defensive mode, trying to defend the indefensible. She is right. The GPL did the world a huge favor here.
Does that mean the GPL could not be made somewhat more flexible? Well, we will see when GPL 3.0 sees the light of day.
Stupidity (Score:3, Insightful)
It's one thing to want to limit the number of approved Open Source licenses. I may disagree with it, but I understand the motive. I can also understand his urging his competitors to use the more popular Open Source licenses instead of their own (even though HP still insists on proprietary for most of its software).
But when he says that the GPL is not copyrighted, he is being stupid. EVERY Free Software and Open Source license is copyrighted! Even the sacred and immaculately conceived GPL! For a LWCE keynote speaker to make such a fundamental blunder on the nature of Free Software is scandalous.
Too many companies make up their own OSS licenses. (Score:3, Insightful)
Who is HP in the OSS world? (Score:3, Insightful)
I'm sure the Eclipse people and the OpenSolaris project, among many others, have been waiting with great anxiety for HP's opinion of what they are doing. "Hey guys, stop everything! Martin Fink says we're using the wrong license!"
Even if the guy has a point, it takes some gall for HP to tell these other companies much of anything about how to conduct their OSS business.
And what do they offer in the form of GPL stuff? (Score:3)
To me, at rough glance, this is typical HP tactics. Instead of touting what they're doing, they point the finger at everyone else and go 'see, they suck so we're OK' but don't tell you why they're OK.
The hard part about the GPL (from the way I understand it, which could be flawed) is you in effect give up any IP claims you have on something when it's submitted if you should choose to change the way you do things later. I think what you're seeing by a lot of companies that are opening the kimono a bit but in case this turns out to be a wild fad or something they can close it back up should they want too.
Personally I think the genie is out of the bottle and it is only a matter of time. But monster companies by nature are conservative, and won't jump whole heartedly into something right away.
Re:Somebody please explain OSI (Score:4, Informative)
I do agree with you though that their statement that there should be fewer OS licenses is outside of the scope of what they should be doing. Approve them or don't, realizing that they're talking about other peoples' copyrighted material that they can license however they want, but leave philosophical discussions to some other group. I agree with that stance, they just shouldn't be the ones pushing it.
Re:Somebody please explain OSI (Score:2)
As it stands know the big ones are GPL, LGPL and the BSD family of licences. I think most OSS programmers can grasp these licences and can use source from projects knowing they don't commit a crime.
Re:Somebody please explain OSI (Score:2)
I
Re:hypocrites (Score:2)
Dunno, my PC is built from parts all-over. None of which are HP, SUN or IBM. Yet I can crunch numbers with the best of them.
Sure if you're making a 1000 processor cluster you need something like IBM but for the average home user... no way.
And that's w
Hosre Crap-ola de Jur (Score:4, Insightful)
Re:Sure, right after HP GPL's... (Score:2)
Re:Don't Forget Apple's APSL! (Score:4, Interesting)