Actually , I meant source open to view not to change.
People can always request changes. JSRs?
No Sun Is An Island
As if driven by the cycles of the moon, it seems like the Java community gets a monthly visit from that special topic that divides and angers us more than any other: the question of whether Sun should "open source" Java? Most recently a top open source advocate named Eric Raymond (author of " The Cathedral And The Bazaar ") published an open letter to Sun urging them to "Let Java Go." I have huge respect for the achievements of the open source community, but I tend to stay away from the pissing contests that these discussions about open sourcing Java often devolve into.
I think the issue is something of a bugaboo, anyway. The source code for Java is readily available to anyone who accepts the Sun Community Source License (SCSL.) You can fix problems and submit patches to your heart's content. You can freely use the source code to better understand where problems in your own code are occurring, and you can also look to the Java source for useful examples and implementation patterns which you can emulate in your own code. Most of the technical benefits of source code availability are present to developers under the SCSL, and they are a very significant set of benefits. Furthermore, the Java Community Process (JCP) does a fine job of driving Java technology innovation in a balanced way that meets the needs and serves the interests of many vested participants. The problem definitely isn't that the source code to Java is unavailable or that the community has no voice in the platform's ongoing evolution.
Let Java Go !