Slashdot Mirror


Sun Looks To GPL3 For Java, Solaris

daria42 writes "Sun is leaning toward changing the license for Java and Solaris to the GNU GPL version 3. The article has some insightful comments from Sun boss Jonathan Schwartz. '"Will we GPL Solaris? We want to ensure we can interact with the GPL community and the Mozilla community and the BSD community," he says.'"

24 of 164 comments (clear)

  1. Huh? by Anonymous Coward · · Score: 3, Insightful

    GPL'ing stuff will make it difficult to "interact" with the BSD and Moz communities, unless by interact they mean "take stuff and put it in Solaris/Java"...

    1. Re:Huh? by pato101 · · Score: 5, Insightful

      This stupid license wars is slowing Linux and FOSS community and serves NO FUCKING PURPOSE!
      You are completely wrong. License is a key feature of FOSS, and provides the developer which is the freedom of her work
      roughly, IMHO,
      BSD: the world has the freedom to do whatever: companies like it- not only to use the code but to provide FOSS modules as well!
      GPL: the user won't loose the freedom to keep using the work made by the programmer.
      Which is better? depends strongly on the programmers intention about the software she is releasing. She has put a lot of effort on that, so she may have an opinion of which is the allowed use of her code.
      Saying it is stupid, is selfish as you seem to be thinking only in the present day with the present apps, which seem you have not developed, have you?

    2. Re:Huh? by Vihai · · Score: 3, Insightful

      You may think it is the fscking truth, but what you say denotes a complete lack of understanding of the reasons for which FOSS people code. Choosing the license which better represents the programmer will is IMPORTANT. Otherwise we would all put our code in the public domain, which most of us do NOT want.

      License WARS serve no purpose, I agree, but you will likely not see "one license to bind them all".

    3. Re:Huh? by Aladrin · · Score: 2, Interesting

      "GPL: the user won't loose the freedom to keep using the work made by the programmer."

      Um, no. The work made by the programmer will be available to the user no matter whether the license is BSD or GPL, or many others. Once a version of some code is released open source, it will be there forever.

      The difference between the GPL and BSD is that the GPL ensures that any improvements to the code will be given back to the community. This makes it more restrictive and businesses cannot add code to a GPL'd app that might give away their business secrets. (Unless they keep it in-house, blah blah blah.)

      --
      "If you make people think they're thinking, they'll love you; But if you really make them think, they'll hate you." - DM
    4. Re:Huh? by Aladrin · · Score: 4, Insightful

      You lose karma because people believe you are wrong. FOSS is about choice and freedom, and license is one of those choices. You are essentially saying that they are stupid for believing in what they do.

      I'm a huge fan of the BSD license. Nothing says freedom like lack of restrictions.

      But lately, I've begun to see the draw of the GPL license. I've never had an issue with the LGPL, as it does what I think the GPL should: It makes certain that code improvements are returned to the community. The GPL tries to make additional code belong to the community, too, though.

      So you cannot kill this 'license war' without killing the FOSS community, too. They're the same thing.

      If it makes you feel better, you can think of them as GPL and BSD communities instead of a single FOSS community.

      --
      "If you make people think they're thinking, they'll love you; But if you really make them think, they'll hate you." - DM
    5. Re:Huh? by Calinous · · Score: 2, Interesting

      "The difference between the GPL and BSD is that the GPL ensures that any improvements to the code will be given back to the community."
      GPL and BSD code are totally free to use.
            BSD is free to redistribute, no problems (well, you should have a copyright notice) - Microsoft used in Windows 2000 a network stack (TCP/IP) derived from the BSD stack.
            GPL is not free to redistribute - unlike BSD, anything containing even a small part of GPL code MUST be redistributed with its full source code, both the GPL part and the modified code.

            Assuming Google uses the Linux kernel - Google can change anything in the kernel, and keep the code secret AS LONG AS it doesn't give the updated kernel to anyone. If it would, it would need to ship full source code (or at least the place to get the standard code, and all its modifications to it)

  2. That's a reasonable choice by velco · · Score: 5, Interesting

    Seems pretty normal for Sun to not be willing to give away years of hard work, without getting anything back.

  3. Should OpenSolaris be dual licensed via CDD by anandpur · · Score: 4, Interesting

    CAB/OGB Position Paper # 20070207 version 0.6
    Topic: Should OpenSolaris be dual licensed via CDDL and GPLv3

    http://www.opensolaris.org/jive/thread.jspa?thread ID=23699&tstart=0
    http://lwn.net/Articles/221543/

  4. Not too long ago.... by Anonymous Coward · · Score: 5, Interesting

    Somebody asked linus if he would be willing to put the license for the next kernel up to a vote. His reply was: "Sure, write your own kernel, license it how you want it, and see how many people use it."

    Be careful what you wish for...

  5. Re:What a load of FUD by blowdart · · Score: 2, Interesting

    How is GPL3 "the same license as the majority"? Utter tosh; you see far more people rejected the drafts because of the political DRM restrictions than are accepting it.

  6. Interesting point by babbling · · Score: 5, Interesting

    I used to think that GPL is the only way to go. I share my code, so why shouldn't others using my code (assuming they distribute software) have to share their modifications to it, as well?

    Well, I've since found one good use for BSD-like licenses. They're good for situations where what you care about the most is that people are using your code. For example, I think some of the Vorbis code was released under BSD so that companies producing proprietary software would add Vorbis support, hopefully leading to widespread adoption of Vorbis.

    1. Re:Interesting point by cheater512 · · Score: 2, Interesting

      The vorbis example is a good use of the BSD licence.

      Two bad examples are the BSD network stack and giflib (MIT Licence).
      Both are now in Microsoft Windows with nothing more than a credit line to the original developers buried somewhere.

      Personally all my code will be GPLed.

    2. Re:Interesting point by jrumney · · Score: 3, Informative

      The LGPL covers situations like file formats or codecs that you want become standard even in proprietary software. Using BSD for such a case allows unscrupulous companies to create their own incompatible Vorbis+ codec to lock users into using their own software. LGPL at least ensures that if they use your code to do this, they have to provide the source so that other implementations can provide compatibility.

    3. Re:Interesting point by Tim+C · · Score: 5, Insightful

      Both are now in Microsoft Windows with nothing more than a credit line to the original developers buried somewhere.

      So what? Given that a network stack is a fundamental part of a modern operating system, and that poorly written, incompatible and vulnerable network stacks would degrade the entire network for everyone on it, surely it's better that MS used a tried and tested stack rather than going it alone and producing a buggy, not quite compatible version of their own?

      Besides which, it was clearly the intention of the authors in using the licence that it could be used in closed-source products, and MS are complying with the letter and the spirit of the licence; "use it as you see fit, just credit us".

    4. Re:Interesting point by jackharrer · · Score: 3, Interesting

      Best option, IMHO, would be to use GPL with pay-for-business-use clause. All proceedings from this should go to Electronic Frontier Foundation or similar, so they can be nicely used for patents, lawsuits, and so on.

      If business pays for code they buy it from community for their own use, thus code will be released from GPL and free for their use. That would mean licensed for their use. And cash can be used, for example, to pay developers for creating things dull and boring like Exchange connectors (damn important for businesses) and such.

      Just an idea, what do you think?

      --

      "an experienced, industrious, ambitious, and often, quite often, picturesque liar" - Mark Twain
  7. Has this any implications for the Linux kernel? by jimicus · · Score: 4, Interesting

    I'd be interested to see if this might result in things like zfs being ported natively to the Linux kernel (rather than the current FUSE-based solution).

    But then... if Sun go for GPLv3, I'm not certain that can coexist within the same kernel as a bunch of GPLv2 code.

    1. Re:Has this any implications for the Linux kernel? by kripkenstein · · Score: 2, Informative
      I'd be interested to see if this might result in things like zfs being ported natively to the Linux kernel (rather than the current FUSE-based solution).

      Well, based on TFA, that won't happen: :

      Using GPLv3 for Solaris likely would preclude Linux programmers from using Solaris software, and vice-versa. That would make it difficult for Solaris to benefit from hardware support built into Linux, or for Linux to benefit from performance tools built into Solaris.
      And indeed, since Linux will stay GPL2, it can't utilize code from OpenSolaris, which will be (perhaps) GPL3. However, TFA is wrong about the other direction. Some 40% or so of Linux source code is licensed under "GPL2 or above", which means that OpenSolaris could use it, as I understand the issue.
  8. Java as a first class citzen on FOSS Desktops by vhogemann · · Score: 4, Insightful

    I wonder,

    Now that Java is OpenSource, and that it has bindings to both GTK (as in SWT) and QT (as in Jambi), will we see it on more desktop applications? I'm asking because I feel that Java is a better choice than C#, because of its extensive libraries and frameworks.

    Also, Java is already a major player on the server side, if KDE and Gnome had a better integration with it than Windows... it would be a major push for the adoption of a FOSS Desktop...

    --
    ---- You know how some doctors have the Messiah complex - they need to save the world? You've got the "Rubik's" complex
    1. Re:Java as a first class citzen on FOSS Desktops by Sax+Maniac · · Score: 3, Funny

      Now that Java is OpenSource ... will we see it on more desktop applications?
      I was going to respond to your post with my Java(TM) capable browser. I waited a minute or so for it to start, but the web page was too big and it ran out of memory. So I went and dug out the shortcut and restarted the VM with -Xmx256m of memory. While it was starting up, I fired up Notepad and composed the text into it. Sure enough, this time the page loaded up after a minute or two, so I went to cut and paste it out of Notepad. But that got completely swapped out by Java, so I had to wait for it swap Java out and Notepad back in. Good, I press ^C, and go back to Java, and... well, then I rotated some laundry while it was coming back.

      I'd email you but my Java(TM) email client requires Java 1.4.2.1 which is different than the 1.3.2.7 that the web browser requires so I can't run them at the same time, or, at least, I haven't figure out how to get the two installations to coexist just yet. Let me reboot and get back to you.

      (Posted from a friend's laptop)

      --
      I can explanate how to administrate your network. You must configurate and segmentate it, so it can computate.
  9. My user concerns by erroneus · · Score: 2, Insightful

    As an end-user, I'm rather interested to see the first Java packages included in Linux distros... well maybe there already is, but not in the distro I use. I want to see an RPM added to the respositories and the horrible GNU/Java implementation removed forever.

  10. One of the things to do... by starseeker · · Score: 2, Interesting

    when considering GPLv3 for Solaris is to contact the actual authors of key parts of the Linux kernel that they would be interested in incorporating and sound out their willingness to license those parts under v3.

    The Linux kernel as a whole is indeed copyright by many people, some of whom are not keen on GPLv3, but what is critical for Solaris is not the WHOLE kernel but the parts which are in fact better than Solaris. The obvious ones are drivers and file system support, but I imagine there are others as well. The point, however, is that Solaris doesn't NEED all of the Linux kernel code. They could only benefit from a few key parts, and the authors of those parts might be convinced to see things differently than Linus and company.

    If I were Sun, what I would be doing is a) waiting for the final GPLv3 while being very active in the process of developing the license b) quietly contacting key individual authors of parts of the Linux kernel that would benefit Solaris, sounding out their attitude to see how much code would be available if they did make the switch, and c) putting an in-house team on a Linux vs. Solaris evaluation to determine the major lacks of Solaris and how they might be addressed internally, assuming no Linux code will be usable.

    The Free Software Foundation's support is not necessarily a guarantee of OS kernel success (*cough*HURD*cough*) but if all FSF code goes GPLv3 and Solaris follows suit being the new favorite development platform of the GNU toolchain will have to have some benefits.

    I'd say the biggest key for Solaris is "what can GPLv3 do for me?" And the biggest immediate factor there is how many of the current Linux kernel authors with desirable code would be willing to consider accommodating Sun by releasing under GPLv3. If they won't, then the question becomes how many new developers could they attract, and that's a much harder question to answer.

    --
    "I object to doing things that computers can do." -- Olin Shivers, lispers.org
  11. Re:What a load of FUD by squiggleslash · · Score: 3, Insightful

    The GPL3 is not the same license as the majority because it hasn't been released yet. There is no other reason. Nobody has rejected it because there is nothing to reject.

    The entire process is being driven by consensus. The DRM stuff is in there because regardless of the views of a vocal minority, most people interested in Free Software are well aware that software is not free if someone can simply define it as an "Access Control Mechanism" and then use the DMCA to tear apart anyone who changes that code in a way they don't like. The "signatures" thing is in there because regardless of the views of a vocal minority, most people interested in Free Software are well aware that software you cannot use in any modified form except those signed-off by a hardware manufacturer is not free.

    And I might hazard a guess that the primary reason why Torvalds is being to vocal in winging about both of the above has to do with the amount of work he'd need to do to change the license in the first place, given his lack of forethought in neither adopting the "or later version" clause, or any alternative that would make it easy to upgrade the license to one similar in spirit without the active support of every single person who has ever made a "contribution", no matter how small, to the Linux kernel.

    Either way, I'm not seeing much evidence that, outside of the Linux kernel, there's much rejection of GPL3 at all. And I am seeing much of the Free Software community who rejected GPL2 seeing GPL3 as a much better alternative. That's the aim, after all, to try to get a license that suits almost everyone who believes in Copyleft, and to end the current, insane, license forking that causes so much damage.

    --
    You are not alone. This is not normal. None of this is normal.
  12. Re:Solaris, we hardly knew thee by dwarfking · · Score: 2, Interesting

    Actually, I see the potential differently. Consider ---

    For years the GNU folks have tried to point out that Linux is just a kernel and the system should be referred to as GNU/Linux. They've been largely unsuccessful because there is no alternative (GNU/Hurd isn't really there).

    Now along comes Sun offering the Solaris kernel which would allow for GNU/Solaris.

    Add to this that the SCO lawsuit was based on IBM contributing code to the Linux kernel (though they probably tried to include samples from GNU tools), Microsoft working with Novell to patent protect users of the the Linux kernel (haven't heard MS say anything about the GNU tools), and we have business concerned again about Linux legalities.

    Sun, however, will claim original or approved authorship of all of Solaris (as early Unix licensees), thus making GNU/Solaris potentially less risky in the eyes of the business community. I would think Sun would prefer the separation of Solaris (on Sun hardware) from Solaris (on Intel hardware) and probably wouldn't have an issue with it being referred to as GNU/Solaris, IMHO.

    And, if Sun does it right and continues improvements in Project Looking Glass, then GNU/Solaris with a 3D desktop built on GPL3-Java could have an impact not only on Windows but also potentially OSX. I wonder how many video card manufacturers would be willing to work with Sun for drivers for GNU/Solaris?

    All in all, this could push Linux (GNU/Linux) off the front burner. Could be interesting.

  13. Re:What a load of FUD by squiggleslash · · Score: 4, Insightful

    I said he was whining, not that he merely had an opinion and that any opinion constitutes whining. There is nothing in my comment that constitutes calling "having an opinion" whining, and if you read that, then you need glasses.

    As for whining, that's what he's doing. He's making up excuse after excuse, complaining that GPLv3 is somehow overbearing compared to its predecessor when, in reality, it is cut from exactly the same cloth and merely closes a few loopholes. His complaint that, in some way, TiVo using signatures to close its hardware and its code is in some way what he wanted all along is a completely ridiculous position - if you want that, you don't make your code copyleft. His complaints about DRM have no basis in anything the draft license says.

    Torvald's inability to posit a position consistant with the aims and effects of the license he chose, claiming GPL2 is somehow not the copyleft license it is intended to be, shows me that his positions are completely insincere, and this realistically is more excuse making, presumably because of his shortsighted decision not to ensure there was a process for upgrading the license in the future.

    Yes, it's whining. If he had a strong legitimate point, I'd say it was merely having an opinion. But he doesn't. He's saying his choice of a strict copyleft was right, yet complaining that the loopholes within it that completely undermine the entire point of making it copyleft are, in some way, desirable. He's full of shit, and not for the first time.

    --
    You are not alone. This is not normal. None of this is normal.