Share Java - Sure, Open Java - Maybe

Interesting moves in the Java hemisphere recently. Red Hat’s acquisition of JBoss and then at Sun’s Java Developer Conference, JavaOne in San Francisco - a flurry of announcements including Apache Harmony’s full support for SWING/AWT, IBM’s successes with Eclipse, and Sun’s revised Distro License for Java (DLJ). DLJ was endorsed by Ubuntu’s Mark Shuttleworth prominently on stage with Sun CEO Jonathan Schwartz. Schwartz hinted broadly at continuing to open up Java. Even Marc Fleury of JBoss announced Red Hat participation in Sun’s NetBeans project. A lot of positive dance moves but what’s next?

“Sun’s Distro License for Java (DLJ) makes Java more distribution friendly.”

The 3 C’s: Control, Compatibility, Community

Open source software and collaboration are here to stay. Commoditization of information technology components, whether software or hardware, is a reality. Every company is grappling with how to balance using open source collaboration and community while retaining control of their own technologies, innovation and developers. For Sun, whether it is Java, Solaris or Sparc technologies - every project is affected by the disruptive wave of open source. What’s more, everyone wants to turn the money wheel for their own benefit, open source or no open source. The trick, however, is to balance control with innovation, community and expansion of markets.

Maintaining compatibility and control while open sourcing Java is achievable according to Sun’s open source chief, Simon Phipps. Phipps, an expert on open source and key advisor to Schwartz, believes that after open sourcing Solaris, the same process for Java should be a lot easier for Sun. Just released, DLJ demonstrates Sun’s intent to make Java more distribution friendly. In the words of Simon Phipps, Sun is taking positive steps of “goodwill and intent to deliver in a new context.” And more presumably will follow.

Other open source experts, such as Danese Cooper of OSI, who earlier had been part of Sun’s internal licensing efforts for NetBeans, OpenOffice.org, OpenSolaris and CDDL, believes that Sun already understands the issues of control and compatibility in open sourcing Java. Sun’s spin on freeing Java during the past several years has been motivated by an interest in ensuring control of technologies and markets, and avoiding brand dilution. Today Sun understands that open source collaboration ultimately can amplify rather than diminish a successful project’s brand. It has clearly worked for Linux, Apache, and Mozilla. So why not open the gates?

Growing Java markets together

Further open sourcing Java with a flexible license could increase its developer base and contribution of new ideas as well as grow its market rapidly. An Eclipse-like Java foundation where all industry and community contributors can participate freely would be ideal. Obviously there are complex steps required in setting up an open source project structure and managing community contributions extending the Java Community Process (JCP). A full management structure with Java experts from various organizations is needed. Benefiting from community driven innovation and riding on a strong services organization can help Sun grow its market share and expand the global market for Java. Backed up by Sun’s top-notch engineering and services teams, and those of all of its collaborators, open Java will be a win-win for all.