In a previous post, Make or buy? Home, sweet home — on the web, I argued that the most important decision facing a corporation considering starting a major open-source project is whether to build a community from scratch or buy into an existing community.
Sometimes there is no choice since there is no suitable existing community.
But if there is a suitable existing community then I think it is better to join that community than to build a new one from scratch.
That to me is the most surprising aspect of the SUN/FSF alliance and the recent announcement of the release of Java in open-source form under gplv2.
Why didn’t Sun leverage the existing Apache and Eclipse communities?
Now of course this was Sun’s decision to make, so I’m offering these thoughts here just to shed some insight on the various options that come into play when making this sort of choice.
But I expect the following announcement would have had a greater impact, and would have made a favorable outcome more likely.
In simple language, why didn’t Sun announce the following:
We’ve been working on Java for almost 15 years, and have been considering making Java more open for at least half of them. 
We have decided to make Java open-source. We seek to make it available to the widest possible audience, under a license compatible with existing open-source efforts around Java.
Accordingly, we are handing it over lock, stock and barrel to the Apache Software Foundation (ASF).
We look forward to working with the ASF to make Java a truly open platform.
1. Sun made some noises about offering Java for ECMA standardization in late 1999. I decided to no longer work on Java when this fell though, believing then that Sun would make no meaningful effort towards making Java more open for the forseeable future.