Where does open source code come from?

From this article:
The European Commission has published its final report on the Economic Impact of FLOSS (Free/Libre Open Source Software) on innovation and competitiveness of the EU ICT sector.
Weighing in at 287 pages it will take some time to digest, and contains enough data and statistics to fill a blog for a whole year.

One interesting nugget in the report (which I've not had a chance to fully read yet) was a “top ten business contributors” list, based on number of Person-months. To be honest, I was a bit surprised by the list. Sun was number one, which was no surprise. Rounding out the top three were IBM and Red Hat, also very much expected. The rest of the list:
4 Silicon Graphics
5 SAP
6 MySQL
7 Netscape
8 Ximian
9 Realnetworks
10 AT&T

That's where the surprises came in. Many companies I'd have expected to be there are suspiciously absent. SAP was also a surprise up that high. I'll have to look into what else aside from MaxDB they've donated. Just goes to show that code isn't always coming from the places you think it is. I'd guess I'll be posting more about the report as I get a chance to read it.
(originally from Matt Asay)
–jeremy
,

Sun Releases First GPLed Java Source

A quick (belated) follow up to a story I previously covered. Sun has now officially released part of Java under the GPL. phoneME, which has previously been called J2ME, is now available for download with a GPLv2 license. The supported platforms are Linux/ARM, Linux/x86 and Windows/i386. Many seemed to guess that J2SE would be released first, but I'm sure that's coming soon. Once again kudos to Sun for making the decision they did.
–jeremy
, , , ,

Oracle questions GPL open sourced Java

It appears that Oracle is siding with IBM on the issue of the Open Source license for Java. From the article:
Steven Harris told Computer Business Review he believed the release of the Java code as open source would be beneficial, but questioned whether the Santa Clara, California-based company would have been better advised to have released it under an Apache license.
“It's a good thing that they're open sourcing it, and it opens up access to people who previously considered there were barriers to it,” he said, while noting that “those barriers were pretty low” in the first place.
However, he also repeated comments made by IBM Corp that the choice of the GNU GPL made the project incompatible with existing projects under the Apache and Eclipse initiatives.
“The most active Java communities are Apache and Eclipse. It is unfortunate that they did not provide a path that would allow these projects to grow,” said Harris. “The community is in Apache and Eclipse. Sun's choice creates a new community.”

Sun responded:
Speaking to Computer Business Review earlier this month Sun's chief open source officer, Simon Phipps, explained that using the GPL would overcome fears about license compatibility with Linux. “We've been working on the Java platform for a considerable time and we've got to the point where we're considering 'how do we grow the market',” he said.
“The most important thing is that that the Java platform is not included in many GNU Linux distributions.” Choosing the GPL, which is already used for Linux, avoids that issue, he explained. “Java now becomes the development platform of choice for enterprise GNU Linux users.”

I think this example is an indication of part of the problem some have with license proliferation (and note that these are two of the most popular Open Source licenses). Sun is basically in a position that it has to choose between Linux compatibility and Eclipse/Apache compatibility, or license Java under a myriad of licenses (which is really not an optimal situation). Someone is likely going to lose here, which is a shame since we're on the same team and have the same goals. Unfortunately I don't have an answer to the problem. Fortunately, people much smarter than me are working on it ;)
–jeremy
, , , , , , , , ,

IBM cool to Sun's open-source Java plan

In a bit of irony, it looks like IBM (who has been trying to get Sun to Open Source Java for years) isn't that happy with the GPL. From the article:
After years of internal debates and public calls from IBM to make Java open source, you would think that IBM would be overjoyed at the news.
Not so.
IBM on Monday issued a statement attributed to Rod Smith, vice president of emerging Internet technologies in the IBM Software Group, who penned the open letter in 2004 requesting Sun to make Java open source.
Smith said that IBM supports all open-source licenses approved by the Open Source Initiative (OSI). But he noted that there are already two projects around open-source Java.
There is Harmony, a project in the incubator phase at Apache to build an open-source edition of Java SE. IBM joined the Harmony project shortly after it was launched in 2005.
Meanwhile, Motorola two weeks ago said that it will contribute code to start a Java ME project at Apache .
“In light of the Apache projects, we have discussed with Sun our strong belief that Sun should contribute their Java technologies to Apache rather than starting another open-source Java project, or at least make their contributions available under an 'Apache friendly' license to ensure the open-source Java community isn't fragmented and disenfranchised, instead Sun would be bringing the same benefits of OS (open-source) Java to this significant and growing open-source community,” the statement said.

Just goes to show that you really can't make everyone happy. Overall the Open Source community seems quite happy with the GPL decision. I haven't yet had the time to look deep into the Java community reaction, but I do plan to. I'd guess that despite this initial reaction, IBM will likely become more involved as time goes on. What exactly will happen to projects like Harmony remains to be seen.
–jeremy
, , , , ,

Sun Open Sources Java under the GPL

Well, it's official and the rumors were true. Sun has released Java under the GPL. From the press release:
Santa Clara-based Sun said it is making nearly all of Java's source code – excluding small pockets of code that aren't owned by Sun – available under the GNU General Public License. The same type of license also covers the distribution of the core, or kernel, of the popular open-source operating system Linux, which competes against Microsoft Corp.'s Windows operating system.
All the Java source code is expected to be released by March 2007, Green said. The move covers all Java technology, which includes software that runs on handheld devices, personal computers and servers.

As I mentioned previously, I guessed that this would be released under the CDDL (as did many others). Sun is sending a huge message by using the GPL here. They have been supporters of Open Source for a while, but their occasional waffling really tarnished their rep in the Open Source community. I hope this move serves to get them the recognition they deserve. Of course, I hope it also helps them prosper, which will further serve to solidify Open Source in the enterprise and commercial worlds.
You may be interested in what this release actually covers. It's stock GPL2 for J2SE, J2ME, and J2EE code and then GPL2 + Classpath exception for the SE libraries. This basically means you are still 100% free to write closed source commercial applications that run in the Java VM. So what are the repercussions of this? First, being able to yum install java or apt-get install java will be really nice. That's just a small bit though. I'd guess Sun will dual license the code for those who are interested, so I'd not expect their direct bottom line to change immediately. That being said, I'd expect uptake of Java to increase substantially. It already powers a huge array of devices, but I'd expect that to increase dramatically. In the end, that's good for Sun. I'd also expect the number of Open Source projects that use Java to sky rocket. Sun will get the bits of innovation back for use, developer concerns over the license is gone and the JCP still controls the direction of Java. In the end, Sun still gets to decide what “Java” is (remember, you can fork without issue, but you can't call that fork “Java”). Moving out longer term is a little tougher, but I'm extremely interested in watching this one progress. For instance, what will the impact on the uptake of .NET be?
I find it intriguing to see that Jonathan Schwartz admitted that the recent Microsoft Novell deal did impact this decision. From that linked post:
And in closing, I want to put one nagging item to rest.
By admitting that one of the strongest motivations to select the GPL was the announcement made last week by Novell and Microsoft, suggesting that free and open source software wasn't safe unless a royalty was being paid. As an executive from one of those companies said, “free has to have a price.”
That's nonsense.
Free software can be free of royalties, and free of impediments to broadscale, global adoption and deployment. Witness what we've done with Solaris, and now, what we've done with Java. Developers are free to pick up the code, and create derivatives. Without royalty or obligation.
Those that say open source software can't be safe for customers – or that commercially indemnified software can't foster community – are merely advancing their own agenda. Without any basis in fact.
They're also fighting a rising tide.

To me, that means the CDDL may very well have been the leading candidate before the MSFT/NOVL deal. A bit of a silver lining there. To me though it also means that we may have a new Sun on our hands. One that has been forming for a while, but has finally got the conviction it needs to compete.
Here some additional reading material that I highly suggest if this topic interests you:
James Gosling
Tim Bray
Alan Hargreaves
–jeremy
, , , , ,

Sun Set To Move On GPL License For Open-Source Java

I looks like I may have been wrong when I said that the license for Java would probably be the CDDL. Much to my surprise, it looks like Sun will be releasing it under the GPL. From the article:
Sun Microsystems has talked a lot about putting Java into an open-source license. Now it's ready to move.
The company is very close to announcing that it will put the mobile (ME) and standard (SE) editions of the Java platform into the GNU General Public License (GPL), with the Java Enterprise Edition and GlassFish reference implementation (currently open-sourced under Sun's Common Development and Distribution License, or CDDL) to follow, several industry sources said.

So it would appear that both the J2ME and J2SE platforms will be released under the GPL. In a recent poll the most requested license by developers was the Apache license (a BSD derivative), but to be fair the comments show a fundamental lack of understanding about the GPL in a couple respects. In general, GPL misunderstandings seem to be fairly common and the cause of a lot of developer concern. When (if?) this announcement is made official, it will be interesting to see how the java developer community reacts. As for the actual license choice, I think it makes sense in a lot of regards. The GPL will prevent any closed source commercial forks and the trademark will give Sun full control of what is called “Java”. It will protect them from the embrace and extend tactic that has been tried before. Additionally, I'd guess they will dual license (a la MySQL AB) which could help add more revenue to the bottom line. If the license is indeed GPL I'd expect fairly quick uptake by the various Linux distributions. I'll post another update, including community response, after we get the official word from Sun.
–jeremy
, , ,

Google testing Sun's OpenSolaris

It looks like Google may be experimenting with OpenSolaris, according to a couple sources. From the article:
Google runs a stripped-down version of Red Hat Linux specially modified by its engineers. But another source, a Solaris systems administrator who recently interviewed for a job at Google, said he was told the company plans to create and test its own modified version of OpenSolaris.
“I am 100% certain that there are literally dozens of people horsing around with OpenSolaris inside Google,” said Stephen Arnold, a technology consultant and author of The Google Legacy. Moving to OpenSolaris, he said, would be a natural move for Google, with its large number of former Sun employees and its never-ending drive to push the performance of its data centers to the hilt. But Arnold said he doubts that Google, which finished rolling out its highly-secret data centers in 2004, is deploying OpenSolaris widely yet. “Will it quickly replace Linux anytime soon? No,” he said.

Now it's clear that Linux is fairly entrenched at Google and literally dozens of people at Google are always “horsing around” with all kinds of projects that will never come to fruition. That being said, what would the implications of Google dumping Linux for OpenSolaris be for the Linux community? I think the loss would be two fold. First, Google engineers put a lot of time and work into various aspects of Linux that end up moving upstream. Losing that would be bad, but in the end other companies would likely take up most of the slack. The other element is the hit to the reputation Linux has. “If it's good enough for Google..” is something you'll here quite a bit at Linux shops. While it wouldn't be a ding Linux couldn't recover from and it wouldn't actually impact the quality of Linux in any way, perception means a lot; especially in the corporate world. “Why did they make the migration” would be the subject of a massive amount of scrutiny, and rightfully so. Google is seen as a technically savvy company with talented engineers that really know their stuff. For them to move would be a huge seal of approval for OpenSolaris and something I think Sun would absolutely love to see happen. All in all, this is just another rumor at the moment, but it's definitely one the Linux world will be keeping a close eye on.
–jeremy
, , , ,