Slashdot Mirror
Sun Exec Backs GPLv3
Hyperbeth writes "Sun's chief open-source officer Simon Phipps said that existing work towards GPLv3 had been 'extraordinary and effective' and he said he is 'frankly amazed by the criticisms'. The article notes that Mr. Phipps' comments are somewhat surprising, given that the recent open-sourcing of Java went forward with GPLv2." From the article: "I am frankly amazed by the criticisms that have [been] levelled at the GPLv3 process. They seem to ignore the incredible and positive way it is evolving and just find fault with things that are already the subject of work... I would be very surprised if the final GPLv3 was not an effective tool for some of the communities Sun sustains or will initiate in the future."
The article notes that Mr. Phipps' comments are somewhat surprising, given that the recent open-sourcing of Java went forward with GPLv2
There is nothing surprising about this. GPL v3 in final, legally binding form doesn't exist yet, so of course any GPLed software released now will use GPL v2. It will only be surprising if future releases of Java don't use GPL v3 after it is finalized.
If future versions of java are released under GPLv3, does this mean that you won't be able to use those versions of java to implement DRM?
It will mean something when Solaris us placed under it.
Why does this have to be the case? Why does it have to be black and white, all or nothing? Why can't open source be the right answer for some of Sun's projects and not the right answer for others? This seems perfectly sensible to me.
It is no surprise that Sun put Java under the GPL2 for now. Sun didn't want to wait for the GPL3 license to become final. The Novell/Microsoft deal puts a dark cloud over Mono (The Linux implementation of .Net) which is in direct competition to Java. If ever there would be a better time to free the Java code, I don't know when.
I think the entire OSS community owes Sun a big thank you.
We should now embrace Java and incorporate it into Linux. We should push away from ASP.net and move toward making Java the defacto standard for web applications and Java script the standard for dynamic web pages.
The race isn't always to the swift... but that's the way to bet!
There is nothing anti-DRM about what the GPLv3 does, at least in that manner.
You can use GPLv3 software to impliment DRM all day and night if you feel like it. Play DRM'd music, use it on DRM'd operating systems, etc etc etc.
What is anti-DRM about the GPL is that you can't use DRM to remove the ability for people to modify software and then be able to run those modified versions.
the GPLv3 only cares about the program. It doesn't care about the hardware or any DMR'd media or anything like that.
Anyways DRM is a failed technology. I give it another 3-5 years then nobody is going to give a shit anymore, at least anybody that matters. (repeat after me children: failed business model = irrelevent)
Nobody has yet to come out with a effective DRM and it is only used to be abused by companies like Apple and Microsoft so that people have a harder time moving away from using Ipods or Windows, because your file formats that are DRM'd are locking you into a paticular hardware (ipod) or software (future versions of Office).
GPLv3 IS being examined.
Suns praticipating, IBM praticipating, HP is praticipating. Anybody that has any stake in Free and Open source software is praticipating. They have their lawyers all over it.
when it gets released it WILL the most well reviewed open source license in history. Maybe even the most well reviewed software license ever.
It will eliminate the need for a whole class of licenses. Licenses that desire to be 'more free' then the GPL, but want to stay GPL-compatable.
The GPLv3 + exceptions is beuatfull and it is flexible in what sort of additional restrictions it can take. It will make it more compatable with Apache licenses, Mozilla licenses, and dozens of others. It may even be CDDL compatable.
It will help standardize licenses and make them easier to deal with and have less legal questions cloading the Linux arena.
The Patent language has long been needed and it is much more liberal and easier for companies to deal with then what is already used in MPL, CDDL, or the modern Apache licenses. Much more well designed then those supposwdly 'more corporate friendly license'. The Novell-Microsoft deal highlights the need for reform in this area of the GPL, there needs to be a intellegent and standard way to deal with this stuff and GPLv3 should provide it.
So, Linus is stupid, now?
In questions of licensing and use of unfree software if it scratches his itch? That's at least debatable.
"When I first heard Daydream Nation it quite frankly scared the living shit out of me." -- Matthew Stearns
To see what I actually said, rather than relying on the ZDNet extracts, you'll find the original blog posting here. It's linked from the article but clearly from some of the comments above some people haven't spotted the link.
If Sun's goal is assumed to be freedom, sure, that's true. Probably their goal is the best interest of the company and to some degree its customers. A lot of times free software will serve that, but I don't think it necessarily best serves it in all cases.
I think there's great things to be found, even for businesses in free software -- I just wish people saw it as more an option and less a religion.
It's a hot topic and there are plenty of voices for and against. It was like this discussing the use of the GPL for the Java platform though, extensive and passionate debate right up to the last minute. In the end GPL v2 with the Classpath exception was clearly preferable, but every possible option was explored.
One key difference with Solaris though is that the base source code is already open source Free software and is in the care of the OpenSolaris community, so while Sun obviously gets a big say in what happens it's not just down to us, the community will also need to discuss it.