Slashdot Mirror


Sun Considering GPL For OpenSolaris

narramissic writes, "At an event today to formally open-source Java, Jonathan Schwartz, Sun's president and CEO, and Rich Green, the company's senior VP of software had an exchange in which Schwartz put Green on the spot about using GPL for OpenSolaris: 'Are you averse to changing the license, Rich Green?' Schwartz asked. 'Certainly not,' Green responded, prompting the Sun CEO to fire back in a half-joking manner: 'Will you GPL Solaris, Mr. Green?' 'We will take a close look at it,' Green said, adding that it was possible that the familiarity and comfort level many developers have with the GPL may result in Sun adopting it for OpenSolaris." Another note about Sun's decision to use the GPL for Java comes from reader squiggleslash, who writes: "According to Jonathan Schwartz, the decision of Novell and Microsoft to '(suggest) that free and open source software wasn't safe unless a royalty was being paid' is what prompted Sun to finally come down on using the GPL for Java. So I guess every cloud has a silver lining."

2 of 215 comments (clear)

  1. Re:Another dumb move by xzvf · · Score: 4, Informative

    Sun does two things well. Rock solid hardware and excellent service. GPLing Solaris and Java allows them to limit resources spend on software development. In addition, GPL compatible Solaris and Linux will blur the lines between the OS as they adopt each other's best features. Linux and Solaris might become binary compatible. Sun can focus on selling hardware and services.

  2. Which *version* of the GPL by YA_Python_dev · · Score: 4, Informative

    More interesting than this, IMHO, is to note that for Java they choose to use the "GNU GPL v2 only" (plus Classpath exception) license, not the more common "GPL v2 or any later version".

    This is what the Java FAQ says about it:

    Q: What about GPL v3? Have you considered using that license?
    A: While Sun has been working with the Free Software Foundation as an active participant in the development and review of the GPL v3 license, this license is not yet complete. It is Sun's strong desire to complete the open sourcing of its Java technology implementations in a timely manner, so we made the decision to use an existing, established license paradigm rather than wait for GPL v3 to be completed. Using GPL v2 does not indicate anything negative about GPL v3. Sun continues to be very actively and positively involved in this new license's development.

    And, from this InfoQ article about the GPLed Java:

    GPLv3 was not chosen since it is not finished yet, but when asked if Sun will move to GPLv3 an official said "at this point we don't know what the final license will be."
    --
    There's a hidden treasure in Python 3.x: __prepare__()