Slashdot Mirror


Is UnitedLinux Violating The GPL?

mmayberry writes "NewsForge has posted an article, UnitedLinux might not be very GPL-friendly. With a closed beta that includes an NDA, UL may be on the verge of angering a large part of their target market. You'd think that the likes of Suse, Turbo, SCO, and Conectiva would get the point by now..."

373 comments

  1. This is comical... by meis31337 · · Score: 2, Insightful

    What is the best way to NOT gain ground and support in the open source community??

    How bout violating the GPL. Duh.

    1. Re:This is comical... by Elbereth · · Score: 2, Insightful

      So, it's okay for you to ignore the copyright on movies and music, but they can't ignore the copyright on some software?

      I would die laughing if I saw modified, binary-only releases of GNU utilities on a P2P network.

    2. Re:This is comical... by Anonymous Coward · · Score: 0

      Sorry, its very simple: They are not in violation of GPL.

      NDA is fully legal and the source should be considered for "interal usage". Its not for the "public" and therfor no violation of GPL.

    3. Re:This is comical... by cyborch · · Score: 1

      your post screams O/T and flamebait, but i'll bite...

      of cause it's not ok for meis31337 to ignore copyright on music and movies, but neither of us can say he did do so. On the other hand, I i did see modified binary only releases of GNU software on a p2p network I wouldn't touch it with... well anything. The same applies to United Linux which if they did indeed break the GPL I won't come near. Hence your parent post.

    4. Re:This is comical... by mmol_6453 · · Score: 2

      Anyone stop to think they might be re-writing from the ground up?

      In that case, they'd own the copyrights. By not releasing the source until they're ready for a full release of an OS(Linux is the kernel, not the OS), they have the ability to, like Microsoft, unveil beatiful rainbows of extraordinary functionality, getting an edge over their competition. (It's hard to write a competitor to a project behind closed doors.)

      It's a perfect example of the way companies will be able to produce excellent Open Source products at a profit. Businesses will grab the products while they're hot, and the simultaneous source code release will be supported by the OSS community.

      At least, I think that's what they're trying to do.

      From the community point of view, that's pretty damn sad...

      --
      What's this Submit thingy do?
    5. Re:This is comical... by debrain · · Score: 2

      There is a subtle philosophical difference between protecting the copyright of GNU and that of music and movies:

      The spirit of GNU is to provide freedom to the copyrighted material. As such, protecting software under GNU copyright is protecting freedom, and intrinsicly in the interest of the common person such as you and I.

      The spirit of the copyright of music and movies is protecting ownership for profit. Protecting those copyrights is all too often protecting the interests of transnational conglomerates, and typically the common person has no direct vested interest in that transnational's profits.

      Not to say that violating copyright is right or wrong for any reason. But certainly the interests that we have as free individuals are different depending upon that particular copyright, and as such our perception of "right and wrong" is not founded in a uniform copyright. The spirit of the copyright status is very different, from a moral point of view.

      Not all copyright is created equal in the eyes of the consumer. :)

    6. Re:This is comical... by Misch · · Score: 3, Informative

      They would have to be rewriting from the ground up. And they'd have to rewrite everything.

      *******

      GPL FAQ

      Q: Does the GPL allow me to distribute a modified or beta version under a nondisclosure agreement?

      A: No. The GPL says that anyone who receives a copy of your version from you has the right to redistribute copies (modified or not) of that version. It does not give you permission to distribute the work on any more restrictive basis.

      ********

      Or, they're distributing their version of Linux without any GPL'ed code in it. That would be kinda like giving someone a goldfish in a tank with a shiny plastic castle in it, except that there is no tank, no water, no goldfish, and no shiny castle inside of it.

      --

      --You will rephrase your request for me to go to hell. Goto statements are not acceptable programming constructs
    7. Re:This is comical... by Anonymous Coward · · Score: 0

      Yup, that's the american way. Innocent until proven guilty.

      Why didn't newsforge wait until they had real proof. Most of you have already convicted United Linux of violating the GPL without even seeing what the NDA says. Maybe the NDA specifically says that any GPLed software can be redistributed. Who knows.

      Can't you see when you're being manipulated? Newsforge is totally trying to get you to hate United Linux, without any proof of wrong doings.

      Sheep.

    8. Re:This is comical... by Chris+Burke · · Score: 2

      So, it's okay for you to ignore the copyright on movies and music, but they can't ignore the copyright on some software?

      No.

      Next stupid question?

      --

      The enemies of Democracy are
    9. Re:This is comical... by Anonymous Coward · · Score: 0

      Too bad the GPL has nothing to do with Open Source.

      GPL = theft.

    10. Re:This is comical... by numark · · Score: 2, Insightful

      There's quite a bit that they'd have to rewrite. Here's just a few of the programs that any Linux user can recognize that are GPLd:

      bash, gcc, glibc, both KDE and GNOME, plus quite a few other window managers, virtually all drivers in existence, etc.

      It's highly doubtful in the short year or so that UnitedLinux has been around for that all of those programs could either be replaced or rewritten. It's therefore logical to conclude that the UnitedLinux group is violating the GPL. There's virtually no way around it.

      --
      Want Slashdot headlines on your site? Try SlashHead
    11. Re:This is comical... by BlowCat · · Score: 2
      Modified binary-only GNU Midnight Commander for BeOS

      The unmodified source doesn't compile because it heavily uses select(). The modifications have never been made public. All attempts to reach the author of the port have been unsuccessful so far. The binary-only version has been downloaded 5007 times.

      Now please put it on a P2P network and die (laughing or otherwise).

    12. Re:This is comical... by Anonymous Coward · · Score: 0

      The way I see it, they are not actually violating GPL, but we'll see that in the future.

    13. Re:This is comical... by Anonymous Coward · · Score: 0

      Heh, the kernel itself is under the GPL.. no kernel, no Linux..

    14. Re:This is comical... by mmol_6453 · · Score: 3, Interesting

      I understand what you're saying, but I think the GPL has a gray area:

      The GPL allows you to distribute a closed-source modification of a GPL, as long as the distribution is within the organization making the modification. One could argue that by placing beta testers under an NDA, they're making those testers part of their organization. Who knows? Maybe they're giving them membership cards.

      Of course, UL can't make the entire world a member of its organization, so they'll have to release the source when the product goes public.

      This gray area hasn't been a secret. In fact, the Affero GPL was created for the purpose of closing this loophole. Problem is, nobody's using it because it limits the people who will use the software to corporations with no need to adapt it to their needs(a rare case where a custom-built system would normally be used), and people of the general OSS community.

      --
      What's this Submit thingy do?
    15. Re:This is comical... by Anonymous Coward · · Score: 0

      theft = kittens.

      Thus GPL = kittens.

      And who doesn't like kittens?

    16. Re:This is comical... by mmol_6453 · · Score: 2

      gcc and glibc I can see as being very difficult to rewrite.

      (I'm no expert, but I'll take a stab at it. I'm playing devil's advocate, unpopular as that is, on /.)

      While it's still slightly unstable, GNOME has gone a long way catching up with KDE, and that was without much corporate sponsership. With all of UL, I don't see that it would be impossibe for such a large organization. GNOME manages to retain certain compatibilities with KDE, so UL could probably accomplish simaler feats.

      Windowmanagers? They'd only need one, and they could probably put together themes for it.

      Drivers aren't an issue as long they run on the Linux kernel.

      The only thing I don't see them rewriting "overnight" is the X server. Even if they build it for a framebuffer target, it's still a massive, complex piece of software. I don't know how much the X Consortium's code would help.

      Remember, Microsoft has tens (hundreds?) of thousands of programmers dedicated to their suite of games, tools, and OS. UL consists of a lot of experienced Linux programmers, who I'm sure wouldn't refuse to code, so long as their source was released in the end. Professional Linux programmers are, IMO, a lot more dedicated, creative and productive than your run-of-the-mill I-hate-my-boss engineers. (Sorry Gene)

      --
      What's this Submit thingy do?
    17. Re:This is comical... by Anonymous Coward · · Score: 0

      They can certainly sell to those places in the world where the GPL isn't tested or testable, though. All those places where Microsoft can't sell more than a single licence per region, binary only GPL'd software doesn't stand a CHANCE of getting their license enforced.

    18. Re:This is comical... by Anonymous Coward · · Score: 0

      I wonder if the binary of Midnight Commander I run on this Windows 2000 machine has released source?

      No, on second thought, I really don't give a shit if it does. It works well enough.

      And that, my friend, is what will lead to the downfall of the GPL. People don't care, so long as it works pretty good.

      They'll actively stop caring, if anybody comes in and interferes with them using software because of a source code technicality they don't care about.

    19. Re:This is comical... by TheLostOne · · Score: 1

      Maybe I can help the devil out a bit here :)

      If the big problem is the X server I don't think it's a problem, FAIK it isn't GPLed.

      I was bored and reading some rms propaganda and it looks like it is one of the reasons he started thinking copyleft in the first place (check the 2nd link, header Copyleft and the GNU GPL)

      I'd go check out the license right now but my pizza's burning :P

      --


      '..that kernel panicked like a nun in a crack house!'
    20. Re:This is comical... by hayden · · Score: 3, Insightful
      The GPL allows you to distribute a closed-source modification of a GPL, as long as the distribution is within the organization making the modification. One could argue that by placing beta testers under an NDA, they're making those testers part of their organization. Who knows? Maybe they're giving them membership cards.
      Ummm, no. The reason you can distribute GPL code internally in a corporation is (as far as I understand it) because in the eyes of the law the corporation is a person. Giving binary only GPL'd stuff to yourself isn't a violation so distributing around a corporation isn't either.

      As for this being a loophole, I think closing it would be a bad thing. Getting Free software on the inside of a company is a Good Thing.

      --
      Nerd: Derogatory term typically directed at anybody with a lower Slashdot ID than you.
    21. Re:This is comical... by BlowCat · · Score: 2
      I believe that the binary of Midnight Commander you run on your Windows 2000 machine (if you do) has released source. The patches for Windows were posted, they just weren't applied. But if somebody decides to continue this work, the patches can be found in the mailing list archives.

      As for the "downfall of the GPL", I have to disagree. Somebody still needs to encourage developers to write new software or to make improvements. You cannot ask somebody to improve the software if you don't have the sources. Well, you can, but it will cost more. Now think about security holes.

      Only if most software is 100% secure, costs $0 and fully satisfies users the "downfall of the GPL" as you describe it would be a possibility. Unfortunately, it's not going to happen any time soon.

    22. Re:This is comical... by mmol_6453 · · Score: 2

      What makes someone a member of a corporation? A contract? NDAs fall under that description. (IANAL)

      As for closing the loophole being a Bad Thing, I agree completely. It just doesn't make sense to create a contract that can't be enforced. It's just lawyer food.

      (How can you prove they're using Affero-licensed software? You can't...Any more than I know what brand printer my teacher uses to produce his assignments.)

      --
      What's this Submit thingy do?
    23. Re:This is comical... by -*rootetclog*- · · Score: 1

      really? Kittens? Well it's okay then! init...

    24. Re:This is comical... by -*rootetclog*- · · Score: 1

      Now see, Newsforge isn't alone in coralling people into baseless hatred of someone/thing. How ever most of the people in the world have the mindset of the average sheep or cow easily lead and coearced into doing what ever you wish them to do or beliveing what you want them to belive. I for one am saddened to see such creatures laying wast to one of the few bastions of logic, intelligence and free speech on the subject of technology and related issues. The problem with people is stupidity. I'm not saying there should be a capital punishment for stupidity, but why don't we just take the safety labels off of everything and let the problem solve itself?

    25. Re:This is comical... by -*rootetclog*- · · Score: 1

      But it dosn't. It would if it prevented people from distributing non-proprietary software and code. But, Guess what! it doesn't. It only limits the distribution of PROPRIETARY information

  2. Considering the companies in UnitedLinux... by leviramsey · · Score: 4, Insightful

    ...It's not that surprising.

    SuSE are not exactly huge supporters of the GPL, what with a non-Free installer and configuration tools.

    Wasn't Ransom Love bashing the GPL a few years ago, while at Caldera and saying that the BSD license is better?

    1. Re:Considering the companies in UnitedLinux... by npietraniec · · Score: 2

      Yea, I don't know too much about the other 2 companies, but Caldera (er.. SCO) never was a big GPL fan, and Suse... Well, I never bothered to try them out because they don't provide ISOs. Mandrake has made probably 150 bucks off of me over the years because I was able to download and try out their distro. Now I buy official CDs because they're cheap, and I'm familiar with it... But I digress.

    2. Re:Considering the companies in UnitedLinux... by lemkebeth · · Score: 1

      ISOs are big aren't they?

      SuSe does provide an FTP installer on their FTP server.

      Hell, all the code is there.

      The only thing they don't provide you is ISOs. Big deal, want a CD? order one.

    3. Re:Considering the companies in UnitedLinux... by bockman · · Score: 1
      SuSE are not exactly huge supporters of the GPL, what with a non-Free installer and configuration tools.


      SuSE also contributes greatly to several free software projects, XFree86 being one of them ( they persuaded Neomagic to release [first binary, then source] the driver for they card - so I enjoyed X on my laptop ).

      --
      Ciao

      ----

      FB

    4. Re:Considering the companies in UnitedLinux... by fault0 · · Score: 4, Informative

      > SuSE are not exactly huge supporters of the GPL, what with a non-Free installer and configuration tools.

      But they are heavy contributors in two of the largest free software projects in XFree86 (through Keith Packard, etc) and KDE (Waldo Bastian, Kurt Granroth, etc..) Of course, XFree86 is X11-licensed, and only parts of KDE are GPL, but the point is that SuSE makes many contributions to free software (The GPL doesn't matter here because SuSE doesn't release their installer under a X11 or BSD license either)

      > Wasn't Ransom Love bashing the GPL a few years ago, while at Caldera and saying that the BSD license is better?

      He said that the GPL was bad for buisness, but good for development. I wouldn't doubt that most other CEO's or CFO's would agree with him.

    5. Re:Considering the companies in UnitedLinux... by Anonymous Coward · · Score: 0

      I am still trying to find out whose great idea at the XFree86 project it was to start deprecating old graphics cards. They've pitched out support for numerous older cards, like my S3 Trio64 card, which was made by STB who at the time were actually one of the few graphics hardware vendors who were members of the X Consortium.

      It's very Microsoft-like to abandon older graphics cards.

    6. Re:Considering the companies in UnitedLinux... by kuiken · · Score: 1

      you forgot tomention reiserfs, kde, 4GB and 64GB kernel patches, sound drivers ....

      --

      42
    7. Re:Considering the companies in UnitedLinux... by phaze3000 · · Score: 2

      and only parts of KDE are GPL
      Actually as far as I was aware all of KDE itself was free. TheKompany certainly produce some non-free software, but everything that comes with KDE is GPL'd AFAIK.
      --
      Blaming GW Bush for the Iraq war is like blaming Ronald McDonald for the poor quality of food.
    8. Re:Considering the companies in UnitedLinux... by Isle · · Score: 1

      KDE is completely free. But parts of it are LGPL, especially kdelibs has to be.

    9. Re:Considering the companies in UnitedLinux... by fault0 · · Score: 2

      I was talking about the fact that KDE comes in various FREE licenses that are not always the GPL, like BSD, X11, Artistic, etc..

  3. Violating the GPL by Anonymous Coward · · Score: 0

    Violating the GPL is like using antibiotics on a open wound. It helps to keep the virus at bay, but doesn't kill it.

    1. Re:Violating the GPL by Anonymous Coward · · Score: 0

      >using antibiotics on a open wound. It helps to
      >keep the virus at bay

      Antibiotics don't affect viruses.

  4. Just chill, people by geekd · · Score: 5, Informative

    Leave your knee-jerk reactions at home for now, people. The FSF is on the case. Don't get all up in arms unless the FSF determines there is an actual problem.

    On the other hand, this Register story paints the upper brass at UL as clueless retards. But the Register always does that. :-)

    1. Re:Just chill, people by Anonymous Coward · · Score: 0

      On the other hand, this [theregister.co.uk] Register story paints the upper brass at UL as clueless retards. But the Register always does that.

      If you actually read the article you linked to, you would notice that it was a Newsforge article. Not an artilce by El Reg.

    2. Re:Just chill, people by geekd · · Score: 1

      Oops, register story and newsforge story are the same story.

      My bad.

    3. Re:Just chill, people by garcia · · Score: 2

      the article on newsforge did not put the brass in any better light. In fact they made her sound like an absolute moron.

      She didn't have answers to this question or that, she was shielded from answering any technical question about Linux (Line-Ux).

    4. Re:Just chill, people by Anonymous Coward · · Score: 0

      The GPL gestapo is on the case! The vigilantes are honing their root kits as we speak!

      Anyone that touches the GPL is just plain foolish.

    5. Re:Just chill, people by lunenburg · · Score: 5, Funny

      Leave your knee-jerk reactions at home for now, people. The FSF is on the case. Don't get all up in arms unless the FSF determines there is an actual problem.

      That's right - save the knee-jerk reactions for when Red Hat changes a desktop theme.

    6. Re:Just chill, people by Anonymous Coward · · Score: 0

      It's actually a newsforge article, which is not surprising since it get's the facts straight unlike most Register articles.

    7. Re:Just chill, people by geekd · · Score: 1


      That's right - save the knee-jerk reactions for when Red Hat changes a desktop theme.


      Now *that's* funny.

      Seriously, that's the funniest thing I read all day so far (we'll it's only 11:45 am. early still for me)

      I'd mod you up, but I can't since I posted in this thread already.

    8. Re:Just chill, people by killmenow · · Score: 2
      clueless retards
      Please refrain from referring to the mentally retarded as REE-tards. Especially as clueless ones. It's demeaning. Besides, many of them have more common sense than "normal" folk.

      Also, if El Reg paints upper management types as mentally retarded, I know some mentally retarded people who would be offended. They're much smarter and more sensible than Management.
    9. Re:Just chill, people by Anonymous Coward · · Score: 0
      She didn't have answers to this question or that, she was shielded from answering any technical question about Linux (Line-Ux).


      Oh my God! A business person in a position of power at a Linux company? What are they trying to do, succeed?
    10. Re:Just chill, people by fatboy · · Score: 1

      Please refrain from referring to the mentally retarded as REE-tards. Especially as clueless ones. It's demeaning. Besides, many of them have more common sense than "normal" folk.

      Yea! The ones that have more common sense than "normal" people are to be called "GoTards".

      --
      --fatboy
  5. Stupid Question by cosmosis · · Score: 4, Interesting

    Many of these companies are obviously violating the GPL, but exactly who is going to prosecute them? And if no one can effectively prosecute them, then what strength does the GPL really have? This is something I have never really understood. Anyone care to elaborate?

    1. Re:Stupid Question by leviramsey · · Score: 4, Informative

      The GPL is enforced through private enforcement. Basically, someone who holds the copyright on GPL software sues for violation of the license. So Linus could sue in this case. The FSF could sue because, presumably, UL will be shipping gcc, glibc, and/or bash.

    2. Re:Stupid Question by phorm · · Score: 1

      The best power would be if everyone were smart, and supported the GPL. Then, simple, nobody buys/uses their product, and it ends up ebay for $0.01

      Waiting for nuclear missiles to be available on ebay - phorm

    3. Re:Stupid Question by geekd · · Score: 5, Informative

      who is going to prosecute them?

      The FSF asks that authors of GPL software tranfer the copyright to the FSF, so that the FSF can take action against violators.

      From http://www.gnu.org/philosophy/enforcing-gpl.html

      So what happens when the GPL is violated? With software for which the Free Software Foundation holds the copyright (either because we wrote the programs in the first place, or because free software authors have assigned us the copyright, in order to take advantage of our expertise in protecting their software's freedom), the first step is a report, usually received by email to . We ask the reporters of violations to help us establish necessary facts, and then we conduct whatever further investigation is required.

    4. Re:Stupid Question by turnstyle · · Score: 1
      Amen. Furthermore, one big benefit of GPL is supposed to be props for the programmers, but credit only needs to appear in the source code, and not in the interface itself, so it's easy enough to hijack GPL code, without even needing to resort to violating the terms of the license.

      I really wanted the GPL to make sense for Andromeda but the more I thought about it, the less sense it made for me.

      --
      Here's what I do: Bitty Browser & Andromeda
    5. Re:Stupid Question by enjo13 · · Score: 2, Insightful

      I beleive that the only person with authority to prosecute them is whomever licensed whatever programs that they are violating the GPL with.

      So if I made "Nicks uber cool GPL spreadsheet" and United Linux decided to take it, make a couple of tweaks and not release the changes I would be the one who was harmed and thus have legal standing to go after them.

      I can also appoint a representative authority (with legal restrictions) like the FSF to go after them as well.

      The point being, that whoever is at the top of the GPL pyramid (AKA the original creator) has to be the one to actually take action.

      --
      Turn s60 photos into awesome videos with mScrapbook for all S60 3rd edition phones!
    6. Re:Stupid Question by turnstyle · · Score: 1
      "The FSF asks that authors of GPL software tranfer the copyright to the FSF, so that the FSF can take action against violators."

      The FSF also asks that you tranfer the copyright on music by The Experiments over to the FSF.

      Tempted? ;)

      --
      Here's what I do: Bitty Browser & Andromeda
    7. Re:Stupid Question by aero6dof · · Score: 2, Insightful

      The NDA's might be incompatible with the GPL, but I'm not sure that the GPL is being violated unless one of the receiving companies tries to excercise their GPL rights with the UL distro and is denied. Now if UL was making it difficult for end customers to redistribute or receive source there might be a story here. Until then, it's just an undefined, untested legal situation. (And I doubt any of the NDA companies would will bother trying to redistribute the UL distro because of business reasons - not because they feel limited by an NDA.)

    8. Re:Stupid Question by Durindana · · Score: 1

      You wouldn't get prosecution - this is a copyright infringement case, open and shut. Any copyright holder of GPL'd software within UL's beta could (pretty easily, I'd imagine) obtain an immediate, binding preliminary injunction against use of that software. Perhaps even summary judgment, so you wouldn't even need to go to court.

      That's not just the FSF's prerogative (though they certainly hold many GPL copyrights), but that of any copyright-maintaining contributor to GPL'd code. BSK doesn't need to get huffy-puffy; copyright violation (if that's what this is) on such a large scale would be quite fragile legally.

      IANAL (of course)

    9. Re:Stupid Question by fault0 · · Score: 2

      Offtopic, but I wanna give you props for making Andromeda. I've been using it for about 6 months and it's great :)

    10. Re:Stupid Question by Misch · · Score: 2

      So if I made "Nicks uber cool GPL spreadsheet" and United Linux decided to take it, make a couple of tweaks and not release the changes I would be the one who was harmed and thus have legal standing to go after them.

      Actually, under the GPL, I don't have to release any changes I make to a program unless I then distribute the program again. I'm perfectly welcome to download a program, change it, and use it for my personal use.

      Distribution is the point at which I have the responsibility to deliver the source code.

      --

      --You will rephrase your request for me to go to hell. Goto statements are not acceptable programming constructs
    11. Re:Stupid Question by turnstyle · · Score: 1
      "Offtopic, but I wanna give you props for making Andromeda. I've been using it for about 6 months and it's great :)"

      First, thanks. It's remarkable how nice a 'props' can feel. Props to you!

      However, you're not as offtopic as you might think. A big part why you can send your good will my way is that my name is visibly displayed in the running software.

      One of the things that concerns me about the GPL is that somebody can take GPL'd code, rework it to take credit prominently in the interface, but leave the formal credit in the source, and redistribute.

      As far as I can tell, that's not a violation, but it totally subverts the author's ability to get credit. And when it comes to GPL, credit is often all that the programmer hopes to get.

      --
      Here's what I do: Bitty Browser & Andromeda
    12. Re:Stupid Question by ortholattice · · Score: 2
      Many of these companies are obviously violating the GPL, but exactly who is going to prosecute them?

      Well, the copyright holder I suppose. Heck, it actually would be kinda fun to have some multi-billion corp (I'll mention no names...) steal my GPL'ed stuff. Then I'd gleefully find a greedy lawyer to sue them for megabucks and hopefully (after the contingency fee) get rich also.

    13. Re:Stupid Question by sw155kn1f3 · · Score: 1

      Hello, I'm writing from the past - we have now backslash-dot site (\.) http://backslashdot.microsoft.com and defending the freedom of speech/software b\c in our branch of the world FSF has finally taken out all the copyrights from original holders and swapped the roles with MSFT! They ship Lindux XP with "echo 'Start here'" button!

      --
      - Arwen, I'm your father, Agent Smith.
      - Well, you're just Smith, but my father is Aerosmith!
    14. Re:Stupid Question by rgmoore · · Score: 2

      Adding an NDA is directly incompatible with the GPL. Just read it:

      6. Each time you redistribute the Program (or any work based on the Program), the recipient automatically receives a license from the original licensor to copy, distribute or modify the Program subject to these terms and conditions. You may not impose any further restrictions on the recipients' exercise of the rights granted herein. You are not responsible for enforcing compliance by third parties to this License.

      Tacking an NDA onto the program would clearly classify as adding a "further restriction on the recipients' excercise of the rights granted herein." That makes requiring one a violation of the GPL. I'm not sure whether that's a violation that would actually void the NDA requirer's rights under the GPL, or if the NDA would just be considered to be void and unenforcable.

      --

      There's no point in questioning authority if you aren't going to listen to the answers.

    15. Re:Stupid Question by armyofone · · Score: 1


      Distribution is the point at which I have the responsibility to deliver the source code.

      Ummm... isn't it fairly common knowledge that distributing their brand of Linux is what UL intends to do? That's why they're called 'distributions', after all.
      --
      "A revolution without dancing is... a revolution not worth having"
    16. Re:Stupid Question by aero6dof · · Score: 1

      I agree that there's a license conflict. I just think that it is legally undefined unless one of the receiving companies actually tries to excercise their GPL rights. If it one of them actually tested the conflict between the NDA and GPL, I would guess that only the specific infringing clauses of the NDA would be voided while the rest of the NDA would remain in force - but I am neither a lawyer nor a judge.

      If anything, the NDA just provides a pragmatic "cost-of-litigation" deterrent to breaking it - not an actual legal deterrent.

    17. Re:Stupid Question by moogla · · Score: 2

      Nothing prevents you from adding an auxiliary clause to the license that stipulates what you just said. A "don't rebrand without my approval" clause would be in order. Perhaps you might call the license the "Andromeda" license. :-)

      --
      Black holes are where the Matrix raised SIGFPE
    18. Re:Stupid Question by fault0 · · Score: 2

      Actually, the GPL does prevent you from adding auxiliary clauses or changing the GPL itself.

      However, going back to the grandparent post, the GPL does disallow removal of copyright notices. A (small) part of the recent stinkup between Redhat and KDE indirectly dealt with this (removal of about kde menu items)..

    19. Re:Stupid Question by turnstyle · · Score: 1
      "the GPL does disallow removal of copyright notices"

      Removal of copyright notices from the source code, certainly, but as I understand it, no so from the interface of a running application.

      And it doesn't need to be replaced by a copyright notice - it could just as easily be replaced by a new product name claiming a new authorship. Consider, for instance, a simple fork -- the forked code would have to credit contributing authors, but (as far as I understand) it wouldn't need to give them any prominent credit that end users would necessarily be exposed to...

      --
      Here's what I do: Bitty Browser & Andromeda
    20. Re:Stupid Question by Anonymous Coward · · Score: 0

      GPLites refer to that as an 'obnoxious advertising clause' and they fragged the BSD license for it for years and years.

      Remember, where GNU software is concerned, the individual means NOTHING. IT is ALL for the collective.

    21. Re:Stupid Question by Anonymous Coward · · Score: 0

      Maybe they'll hand the binaries off to members of their organization in, say, Shanghai. Said members in Shanghai become the distribution hub for United Linux. The United Linux folk here in the West wring their hands and make a big show of opposing what the evile Shanghai branch has done.

      And, of course, the evile Shanghai branch buys a support contract from the Main Office equal to aprox. how much they're making selling the illegal binaries.

      Here in the West the only people who'd refuse use said distro would be people who, ummm, only run squeaky clean licensed software.

      Guess who that leaves out?

    22. Re:Stupid Question by mpe · · Score: 2

      I beleive that the only person with authority to prosecute them is whomever licensed whatever programs that they are violating the GPL with.

      It the law worked even handedly it should probably work something like the Adobe/Elcomsoft case. Once the authorities have been tipped off the actual prosecution being handled by the state...

  6. Yes, but... by redragon · · Score: 2, Insightful

    The Linux community is pretty fickle. Seriously, with the number of licenses, distrobutions, holy-wars, does it surprise anyone that people are getting grumpy? There are just a lot of grumpy people, and seems a lot of them have a passion for Linux. :)

    I figured at some point someone's toes would get stepped on.

    --
    - Sighuh?
    1. Re:Yes, but... by fire-eyes · · Score: 1

      This is a serious issue. Possible violation of GPL is striking at the core of the Linux, and other, communities. It should be taken seriously, and if found true, focused on.

      --
      -- Note: If you don't agree with me, don't bother replying. I won't read it.
    2. Re:Yes, but... by Anonymous Coward · · Score: 0

      People don't start out that way. But dealing with Linux makes people grumpy. It's always breaking, everything takes forever to figure out. It's almost impossible to code for and have work on every distro. And it's terminally behind the hardware/software curve. It's just plain frustrating. Makes even the stoutest supporters grumpy.

    3. Re:Yes, but... by cscx · · Score: 2

      Yeah, according to Slashdot logic, EULAs don't apply when made for Microsft and Apple OSes, but when it's the GPL it's suddenly a super-duper legally binding "let's sic' em' cowboy!" situation.

    4. Re:Yes, but... by ichimunki · · Score: 2

      Dear Troll: That's because EULAs reduce rights, the GPL offers more of them. Thanks for playing.

      --
      I do not have a signature
    5. Re:Yes, but... by karmawarrior · · Score: 1
      The GPL is not an EULA.

      Nor are Microsoft's or Apple's EULA's comparable. With the former, if you don't agree to them, you have more rights than if you do. For that reason, both Microsoft and Apple force you to agree to them before allowing you access to the software to begin with.

      With the GPL, you have more rights after you agree to it than before. If you choose not to agree to the GPL, not only will most vendors continue to allow you access to the code, but you are restricted entirely by the default provisions of copyright law, usually meaning you can "use" the product, and pass it on - with all copies - to someone else, but you cannot redistribute it, or modify it, etc. If, however, you agree to it, you gain the right to redistribute and to redistribute modified versions, albiet under certain conditions.

      EULAs are, arguably, invalid under many circumstances, sometimes because the rights they choose to remove are often illegal, and sometimes because the user is not able to, legitimately, "disagree" with an EULA and expect a refund. Agreeing to the GPL is optional, and it never, ever, removes rights that you'd otherwise have had.

      So, yeah, "Slashdot logic" (whatever that is) holds. Your implied charge of hypocracy doesn't. Go boil your head.

      --
      KMSMA (WWBD?)
    6. Re:Yes, but... by tc · · Score: 1
      No, no it doesn't. The GPL restrists rights too. In particular, it prevents me from distributing software to another party under a license of my own choosing. This is most certainly a restriction. It might be one which you are happier with, but it's still a restriction.

      The previous poster might be a troll, but he does have a point: the enforcability of the GPL relies on copyright law and is in the same boat in enforcability terms as EULAs for proprietary software. Indeed, the GPL is a EULA, it just has different terms to proprietary ones.

    7. Re:Yes, but... by Ed+Avis · · Score: 2

      Well part of the difference is that the GPL isn't an EULA. You don't have to 'agree' to it and you are not bound by it. However, under copyright law you need the permission of the copyright holder to distribute a work, and that permission is available only under the terms of the GPL (in most cases). An EULA purports to bind you just because you try to run the software, even though running a program is (in most countries) not restricted by copyright.

      --
      -- Ed Avis ed@membled.com
    8. Re:Yes, but... by cscx · · Score: 2

      You don't have to 'agree' to it and you are not bound by it.

      So if these people didn't 'agree' to the GPL, they are not bound to it, and can do whatever they want with the Linux source? Right.

    9. Re:Yes, but... by Ed+Avis · · Score: 2

      They can't do whatever they want, because they would then be in breach of copyright. It is copyright law, and not any kind of 'agreement' or contract, that gives the GPL its force.

      As long as UnitedLinux is based in a country that applies copyright to software, they cannot distribute any code without the permission of its copyright holder (either the author or the FSF, in the case of most Linux stuff). So the copyright holder could sue them if they distributed code without permission - in other words, outside what is specifically permitted by the GPL licence they received.

      --
      -- Ed Avis ed@membled.com
    10. Re:Yes, but... by Wdomburg · · Score: 2

      >So if these people didn't 'agree' to the GPL, they
      >are not bound to it, and can do whatever they want
      >with the Linux source? Right.

      You seem impervious to the point. If you don't agree to the GPL, that does not mean you can do whatever you want with copyrighted material.

      Matt

    11. Re:Yes, but... by msaavedra · · Score: 2

      You have several misconceptions that need to be corrected. The parent poster was stating that the GPL offers more rights to distributors than copyright law does, while the MS EULA adds additional restrictions. He was not comparing the GPL to, for instance, the BSD license, which has even fewer restrictions than the GPL.

      I think the parent was stating a belief that software licenses in general are of questionable legality. If one were challenged in court, there is a good chance it would be found to be not legally binding. However, the creator's copyrights would still apply to the software. If the GPL is overturned, the software is still protected by copyright law, which is more restrictive than the GPL. It is in no licensee's interest to have it overturned, since they would actually lose privileges if the GPL were overturned. A court challenge is therefore unlikely. If the EULA were overturned, it would grant end users more freedoms. For instance, the ability to buy one copy of Windows and install it on all four of my PCs at home, which is permissible under copyright law but not under the EULA. Thus, challenging the EULA is much more likely.

      Finally, the GPL is not an end user license agreement (EULA) as you state. Users are under no obligation to accept the GPL when they install or use the software. The GPL only needs to be accepted if you mean to redistribute the software. Thus it is legally more like MS's OEM License agreements, which are even more restrictive than the EULA.

      And, of course, I should include the obligatory IANAL

      --
      "Any fool can make a rule, and any fool will mind it."
      --Henry David Thoreau
    12. Re:Yes, but... by Anonymous Coward · · Score: 0
      For instance, the ability to buy one copy of Windows and install it on all four of my PCs at home, which is permissible under copyright law but not under the EULA.
      I'm not so sure about this. To me this would be the same as you buying a book and making 3 copies, 1 each for a wife and 2 kids (or any 3 other people in your household). IANAL, but this would seem to be a copyright violation and not covered under fair-use. You might be able to argue that 1 extra installation serves as your backup, but not 3 extra installations.
  7. violating GPL by gh0ul · · Score: 1

    That doesnt sound too good if they have violated it.. I believe Lindows made the same mistake, as did Corel..

    1. Re:violating GPL by jasonditz · · Score: 1

      I don't believe Corel ever actually violated the GPL did they? I mean, they sold commercial apps that weren't open source for Linux, but there's nothing in the GPL about that.

    2. Re:violating GPL by gh0ul · · Score: 1

      When they did their closed source beta trials of Corel Linux, in which you had to sign an NDA they were hit with claims of violating the GPL

      Also this blurb i found on google

      Since discrimination is prohibited by the General Public License (GPL) which covers most of the base Linux code and support programs, it is quite likely that Corel is blatantly violating the Linux license.

      http://list.asfar.org/1999/11/0090.html

      some more here:
      http://old.lwn.net/1999/0930/backpage.php3

    3. Re:violating GPL by bfree · · Score: 2

      Corel did violate the GPL! Check this out to see the /. story that covers the resolution or this to see the original /. story on the violation. They also had another problem which was not a GPL issue (I think) regarding limiting downloads to over 18s. Anyway Corel were far from perfect, but they rectified the Beta test issue in 4 days (according to Bruce P at one of the above links) so perhaps UL will fix this as quickly.

      --

      Never underestimate the dark side of the Source

  8. GPL Death Penalty by bwt · · Score: 4, Insightful

    I'm amazed that they would pull this. Their competitors have undoubtably contributed to some of the GPL software that is covered by the NDA.

    What incentive does a company like say Red Hat have to not enforce the GPL death penalty, which says if you violate the GPL, your licence is revoked (GPL, section 4 sentance 2).

    1. Re:GPL Death Penalty by fire-eyes · · Score: 1

      Hm, is GDP an actual term used? Not that I know of. That sounds cool, rather like UDP for Usenet Death Penalty.

      GDP -- GPL Death Penalty

      I wonder what the actual penalties would be? I wouldn't be so interested in moneytary damages, so much as getting whoever got it imposed on them ignored by the community, especially developers, at large.

      --
      -- Note: If you don't agree with me, don't bother replying. I won't read it.
    2. Re:GPL Death Penalty by jas79 · · Score: 1

      That would hurt Red Hat just as much. They are already called the Microsoft of Linux. what would happen if they would use legal tricks to crush their competitors.

    3. Re:GPL Death Penalty by bwt · · Score: 2

      GDP -- GPL Death Penalty
      I like that.

      I wonder what the actual penalties would be?
      They would be commiting commercial copyright infringement. The law can be extremely brutal in such a case.

      I would think it would go like this:
      A) Some GPL contributor would send them a cease and desist letter: "Action X by you violates the GPL. Accordingly, I am enforcing the GDP, see section 4"
      B) The other company says "Nah."
      C) The contributor sues for willful commercial copyright infrigement
      D) The court should determine whether the GPL was violated or not. If they can determine that the contributor is likely to win on the merits, they issue a temporary restraining order and/or a preliminary injunction. At that point the company can no longer ship product. Ouch.
      E) If the contributor persues and wins at trial the Court should reward the larger of statutory damanages (up to $100,000) or actuals. Actuals would include revenue directly attributable to infringement, with the burden of proof on the defendent to show what is or isn't included.

      I really wish that somebody would persue this route sometime. If it goes the way I think it would go, I seriously doubt that anybody would EVER violate the GPL again.

    4. Re:GPL Death Penalty by bwt · · Score: 2

      I disagree. Protecting their copyright from unambiguous infringement is not a "legal trick". The GPL is pretty damn generous. For somebody to turn around and violate it is contemptible and I, for one, would cheer if they got what they deserved. The NDA UL is using serves no other purpose than to allow them to do what the GPL forbids: hoard advancements. When those infringing acts are done to give them a business advantage, I can think of no better situation to kick them in the nuts.

      I guarantee you that if RedHat did this successfully, no one would **EVER** violate the GPL again.

    5. Re:GPL Death Penalty by Anonymous Coward · · Score: 0

      Except that any REAL copyright lawyer (non-FSF) or judge, would see that the GPL doesn't disallow the violator to download another copy of the software, thereby receiving distribution rights.

      In order to block this, RedHat/and or any GPL'd software would need an EULA that says that you may not distribute this package if previous distribution rights have been revoked.

      This is just the one of many loopholes in the GPL. I suspect that a NDA would not be illegal under certain conditions either (external/public versus internal distribution.

      Oh yeah, I'm only in law school, not a lawyer yet.

    6. Re:GPL Death Penalty by bwt · · Score: 2

      Except that any REAL copyright lawyer (non-FSF) or judge, would see that the GPL doesn't disallow the violator to download another copy of the software, thereby receiving distribution rights.

      Assuming that they actually threw away all of their previous infringing code and started over and complied with the GPL with respect to reproducing what they had done before again, yes.

      But if their behavior didn't change, they would again be in violation of the GPL and I think any judge would think: "You were already on notice action X violated the GPL, but you repeated a separate instance of action X" and find two separate counts of infringement, with statutory damages up to $100,000 per occurance.

    7. Re:GPL Death Penalty by be-fan · · Score: 2

      GDP already stands for Gross Domestic Product. Can we call it GnuDP instead?

      --
      A deep unwavering belief is a sure sign you're missing something...
    8. Re:GPL Death Penalty by SN74S181 · · Score: 1

      The stench from such a legal proceeding would completely and irrevocably kill Linux as a viable product in the marketplace.

      So it's a game of chicken.

      I don't think Red Hat wants Linux getting that kind of press at this point.

    9. Re:GPL Death Penalty by gorilla · · Score: 2

      Every TLA has multiple meanings. GDP has at least 12 meanings. Adding 1 more won't make much difference.

  9. Goofy Would Be Proud by kenp2002 · · Score: 1

    Well... so much for trying to set standards... Grrr...

    --
    -=[ Who Is John Galt? ]=-
  10. NDA probably == violation by fire-eyes · · Score: 1

    I'm no GPL expert, or anything..

    But from what I understand, you release the source code WITH the product, period. Maybe you can release it but make it simply available elsewhere but I dunno..

    Wouldn't an NDA be a VERY clear violation?

    I know the GPL question with UL has come up before, and I don't remember what the answer(s) was(were).

    What's going on here?

    P.S. - The "Line-ux" REALLY makes me wonder...

    --
    -- Note: If you don't agree with me, don't bother replying. I won't read it.
    1. Re:NDA probably == violation by Anonymous Coward · · Score: 0

      If you download GPL sourcecode and then modify it for your needs. You have used the rights of GPL.

      Now to the obligations, if you then distribute the binaries for that modification, you need to release the source code as well. But if you do not release the binaries you dont need to release the sourcecode.

      What NDA makes is the latter. It makes the sourcecode to be considered private and not distributed to the masses, and not be public. So the only obligation they have is to release the source code to the NDA users who are allowed to see the product at all.

    2. Re:NDA probably == violation by Anonymous Coward · · Score: 0

      It's NOT pronounced Line-ux!

      It's actually, (and this is a very little known fact), correctly pronounced LINIX, just like MINIX with an L.

    3. Re:NDA probably == violation by fault0 · · Score: 2

      > But from what I understand, you release the source code WITH the product, period. Maybe you can release it but make it simply available elsewhere but I dunno..

      The second is correct. You can charge a reasonable amount of money for shipping and the cost of a cd, too. You don't have to put it on the net.

    4. Re:NDA probably == violation by Lugae · · Score: 1

      But from what I understand, you release the source code WITH the product, period.

      But the GPL gives users the right to redistribute that source code in any way that they deem useful. Signing a non-disclosure agreement is the violation of the GPL, because these beta testers can't redistribute the source.

    5. Re:NDA probably == violation by Anonymous Coward · · Score: 0

      Blah, Leenoox.

    6. Re:NDA probably == violation by Anonymous Coward · · Score: 0

      Consulting my handy ancient GNU Emacs manual (for version 18) I go to the back and notice there's a June 1988 price list from the Free Software Foundation.

      A 1600 bpi tape containing the GNU Emacs source code and other software (it excludes GCC) sells for $150.

      A 1600 bpi tape containing GCC source code (and the compiler toolchain) sells for $150.

      It's also available on DC300XL cartridges, for Suns, for $175 each, and a VMS format version as well.

      GNU Emacs manuals for $15 apiece (they're $50 now).

      I don't think if you fill out the order form and order the GCC source but omit to include money that they would have processed your order.

    7. Re:NDA probably == violation by whereiswaldo · · Score: 1

      It's pronounced "Lih-nucks", but some people say "Line-ucks" instead. Assuming people who use the latter pronunciation are idiots is pretty shallow.
      Personally, I think it's English class time, unless you want to call Linus "Lih-nuss". Man, the English language is going down the shitter. _Everybody_ wants an exception to the rule.

  11. On a side note... by chill · · Score: 3, Flamebait

    Ransom Love, the once head of Caldera, claimed he was stepping down from Caldera to head up UL.

    However, he has since disappeared from the scene. UL claims he never worked for them and has hired someone from "outside" for the position he was after.

    While heading Caldera, now the SCO Group, he had a great deal of input on the direction of UL.

    Maybe, with his non-involvement, this can get sorted out properly.

    UL also stated they will be using SuSE as a base distro and YAST2 as the installer, with contributions from the others adding on.

    Also, both RedHat and Mandrake are set to release new versions any day now. And RedHat's Advanced Server is selling better than expected, with a reported 8,000 units sold so far.

    --
    Learning HOW to think is more important than learning WHAT to think.
    1. Re:On a side note... by pyat · · Score: 1

      To add what little info I have:

      I was at a Caldera partner meeting and it seems that United Linux will ship on one CD, which will be included in SuSE, SCO Linux, Turbo, Connectiva.

      Each will then add in another cd (or more) with their own extensions to the basic version.

      Maybe the GPL stuff will go on the basic CD. (They did say that anybody could base a distro on it, but they would not be certified "united linux", so oracle support would not be there, etc.,)

      I have to say I found the whole business model a bit disconcerting. Yes it is entirely legal to sell GPL code; but no credit was given to the guys who created it. You could be forgiven for thinking that Caldera/SCO had authored Samba! (they gave a 2 hour tutorial on it without once mentioning the guys behind it, although they did mention the ways Caldera supplied it, and how to buy it).

      Now I understand that this is business, and they have to make money, but I still find it all a little off-putting. I suspect that United Linux will be more of this (Caldera business model, SuSE technology is how I see it, but then what do I know!?).

    2. Re:On a side note... by ivan256 · · Score: 1

      RedHat's Advanced Server is selling better than expected, with a reported 8,000 units sold so far.

      It's amazing how marketing can get people to throw their money away.

    3. Re:On a side note... by GigsVT · · Score: 1

      Advanced Server is not just software, it's the guarantee that everything will work, and if it doesn't, that they will fix it, for you, quickly. Think of it as keeping the Red Hat programmers on retainer, and it sure seems like a lot sweeter deal, doesn't it?

      --
      I've had enough abrasive sigs. Kittens are cute and fuzzy.
    4. Re:On a side note... by ivan256 · · Score: 1

      I don't know if it's intentional or not, but they're doing a great job providing vendor lockin. With their versioning, it's practically impossible to make things work with both advanced server and other distros automatically. For example, they say that the kernel is version 2.4.9, but it's got practically everything from 2.4.17 in it, and alot of stuff from the 2.5 tree. It you want to ship a 3rd party device driver, you need to have a special build process for advanced server. That's a pain in the ass.

    5. Re:On a side note... by GigsVT · · Score: 1

      It you want to ship a 3rd party device driver, you need to have a special build process for advanced server.

      I'm not sure I understand what you mean. Nvidia is an example of a driver that is pretty much independant of kernel version, 3ware is another. One is open source, one is not... Please expand on what you mean.

      --
      I've had enough abrasive sigs. Kittens are cute and fuzzy.
    6. Re:On a side note... by ivan256 · · Score: 1

      You cannot key off the kernel version to build a device driver for advanced server. This may not affect video, but it definitaly affects I/O drivers. Instead of putting in your code:

      #ifdef kernel_version 2.4.10

      You have to do something special in your build system to determine if it's advanced server. It can be transparent to the end user, but it's a pain for the developer. I bet both of those drivers you mentioned needed a new release to work on advanced server dispite 2.4.9 having been supported for over a year.

    7. Re:On a side note... by GigsVT · · Score: 1

      #ifdef kernel_version 2.4.10

      This is dangerous in any case. The user may have patched their kernel in a way that makes it incompatible with your driver. There are smarter ways to do things that to do a uname and make assumptions, other than the kernel at least supports what that kernel supported, as a minimum only.

      --
      I've had enough abrasive sigs. Kittens are cute and fuzzy.
    8. Re:On a side note... by ivan256 · · Score: 1

      The user may have patched their kernel in a way that makes it incompatible with your driver.

      Then that's the user's responsibility. An systems vendor should be more well behaved then that.

    9. Re:On a side note... by GigsVT · · Score: 1

      But all major distros are running kernels that are heavily patched from vanilla... I don't see how AS is different in this regard, it's just another heavily patched kernel you have to deal with. I don't see how you could complain about AS but not about the normal Red Hat kernels, or Mandrake, or any other big distro that uses their own kernels.

      --
      I've had enough abrasive sigs. Kittens are cute and fuzzy.
    10. Re:On a side note... by ivan256 · · Score: 1

      RedHat's regular kernels are bad, but they don't change driver interfaces (which is my gripe), and they don't take code from 2.5. Neither does SuSe.

    11. Re:On a side note... by jericho4.0 · · Score: 1

      How the hell did this get modded flamebait? It may be a bit offtopic, but not really. Jees people.

      --
      "A language that doesn't affect the way you think about programming, is not worth knowing" - Alan Perlis
  12. Ironic... by Anonymous Coward · · Score: 0

    ...that this very type of behaviour might drive lotsa folks to use Red Hat Linux, the very distro that UL is supposed to be countering.

    1. Re:Ironic... by meis31337 · · Score: 0, Redundant

      absolutely... I mean. Why would the people behind UL even THINK to do what they did? How many lawyers does it take to figure out that an NDA and GPL don't mix together (you can't even lump the acronyms together and descramble them into a word!!) :) At least I can't. :)

    2. Re:Ironic... by Anonymous Coward · · Score: 0

      Maybe their laywers have looked at the GPL and found that it is uninforceable.

      It still has to be proven in court. Until then it's anyone's guess as to it's validity as a liscense or as toilet paper.

    3. Re:Ironic... by Anonymous Coward · · Score: 0

      an NDA and GPL don't mix together (you can't even lump the acronyms together and descramble them into a word!!)

      GP-land. The place where all the doctors/racing drivers live.

    4. Re:Ironic... by Anonymous Coward · · Score: 1, Informative

      If they beleive the GPL is invalid, then they beleive they have NO right to distribute the software at all since they are not the copyright holders. The GPL gives them the right to distribute so they have to beleive in its vallidity.

    5. Re:Ironic... by fault0 · · Score: 2

      Pray tell, why couldn't the GPL and a NDA mix together?

      The GPL gives special stipulations to non-public software.

    6. Re:Ironic... by Anonymous Coward · · Score: 0

      Bummer, the closest I could come was PiG-LAND, where all the cops live. :-)

    7. Re:Ironic... by HughsOnFirst · · Score: 2

      P-GLAND ?

  13. Re:Blah by fire-eyes · · Score: 1

    Yet you took the time to reply :D

    --
    -- Note: If you don't agree with me, don't bother replying. I won't read it.
  14. Well then by sulli · · Score: 2, Insightful

    Don't use it.

    --

    sulli
    RTFJ.
    1. Re:Well then by Anonymous Coward · · Score: 0

      If only you and everyone else said that and nothing but that about any windows "news"...

      Don't like what MS did today? Use Linux and S.T.H.U.

    2. Re:Well then by spd_rcr · · Score: 1

      haha, no doubt, mod this up, the United Losers (against redhat & mandrake) are no different than M$ wannabes if they close their source. who cares what they do.
      try gentoo.org, tricky, but well documented istall process, with wonderful results =)

      --
      - tensions in our lives that are attacking our minds, unite themselves together to make our consciousness blind - op'ivy
  15. Re:Blah by Anonymous Coward · · Score: 0

    and yet you took the time to reply to one of the articles you "immediately skip over". interesting.

  16. Ehm......about that closed beta... by The+J+Kid · · Score: 4, Insightful

    Not meaning too troll or anything, but...

    The GPL states that you must make the Source Code freely avilible to your customers...

    So if it's a closed beta only the people who recieve that beta have right to that source... and anyway, all the programmes are available on the internet (freshmeat) and as part of other distro's...!

    Speellling is mi graetest good ting!

    --
    Moderation: +4. Modded 70% Funny and 30% Overrated. 100% Saturated.
    1. Re:Ehm......about that closed beta... by SirSlud · · Score: 2

      The GPL also states that if you distribute the source, you must give the same rights to that person as you had.

      So you can't attach an NDA wtih GPL'd software/source saying, "BTW, you know the part in the GPL where it says now that you have the source, you can distribute it too, so long as you adhere to these conditions? Well forget it. You can't distribute it. We're ignoring that point of the GPL and you'd better not exercise that right."

      At least, thats my understanding. Please correct me if I'm off base.

      --
      "Old man yells at systemd"
    2. Re:Ehm......about that closed beta... by Anonymous Coward · · Score: 0

      The problem is that those people who received the closed beta HAD to sign a NDA first. FSF doesn't knoe what's in the NDA. If the NDA forbids the beta testers from releasing/redistributing GPL licensed softwares (even for a limited time during the beta testing period) --- then that's a GPL violation.

    3. Re:Ehm......about that closed beta... by Scooby+Snacks · · Score: 2
      The GPL states that you must make the Source Code freely avilible [sic] to your customers...

      It also says you musn't interfere with their rights granted by the GPL:

      6. Each time you redistribute the Program (or any work based on the Program), the recipient automatically receives a license from the original licensor to copy, distribute or modify the Program subject to these terms and conditions. You may not impose any further restrictions on the recipients' exercise of the rights granted herein. You are not responsible for enforcing compliance by third parties to this License.

      Seems pretty clear to me: "You may make copies and give them away provided you give the recipients all the rights which I gave you."

      So if it's a closed beta only the people who recieve [sic] that beta have right to that source... and anyway, all the programmes are available on the internet (freshmeat) and as part of other distro's [sic]...!

      Yes, this is true. However, you miss a couple of important points:

      1. While it's correct that "only the people who recieve [sic] that beta have right to that source," the people who receive the source have certain rights which are granted by the license. To restrict those rights means that the license has been violated and any prior rights granted to the distributor have been revoked.
      2. Although "all the programmes are available on the internet (freshmeat) and as part of other distro's [sic]," that doesn't mean that they're the ones doing the distributing in this case. All that means is that when someone distributes an app through Freshmeat, that person must offer the source code and full GPL rights to it. When UnitedLinux distributes GPL-covered programs, they must do the same thing. It doesn't matter that other people already do it; "other people" cannot fulfill your obligations under this particular distribution license.
      In case you haven't read it, I strongly urge a reading of the GPL itself; it is certainly one of the most lay-accessible legal documents out there.
      --

      --
      Runnin' around, robbin' banks all whacked on the Scooby Snacks...
    4. Re:Ehm......about that closed beta... by Waffle+Iron · · Score: 2
      So you can't attach an NDA wtih GPL'd software/source saying, "BTW, you know the part in the GPL where it says now that you have the source, you can distribute it too, so long as you adhere to these conditions?

      Just to speculate, I suppose one could make the argument that the NDA is a separate contract not associated with the GPL. IOW, it's not that they've modified the GPL so that you can't distribute the work. Instead, you've entered into a separate agreement that says you won't distribute the work.

      Unlike the GPL, which is a license concerning copyright laws, the NDA could be an ordinary contract covering an exchange of commitments between two parties. Unlike a shrinkwrapped EULA, it would be actually signed by both parties.

      I have no idea if that argument would fly, but it might be what they are thinking.

    5. Re:Ehm......about that closed beta... by henben · · Score: 1
      Insightful? For fuck's sake.

      The GPL seems to be the most misunderstood simple idea since natural selection.

      As has been pointed out already, the people who receive code have to have the right to redistribute it.

    6. Re:Ehm......about that closed beta... by Sabalon · · Score: 2

      But if they are not the original copyright holders on the code (ie te Linux kernel) then they can not modify the license that code is under.

      Sure...they can say that they are giving the testers the code under the NDA, but that does not change the license that the kernel, gcc, etc... comes under in anyway. Since UL is using the GPL'd code, they MUST pass those rights on to whoever they distribute it to - with not further restrictions - or not use the code.

      So if they sign the NDA, that can't invalidate the GPL clauses.

    7. Re:Ehm......about that closed beta... by Anonymous Coward · · Score: 0

      At least, thats my understanding. Please correct me if I'm off base.

      well of cause you are off base, all your base are belong to us!

    8. Re:Ehm......about that closed beta... by nuggz · · Score: 2

      the NDA is a separate contract not associated with the GPL.

      Yes, you could, however the net effect would be you are distributing the software and denying others the right to further distribute it .
      This clearly conflicts with the GPL requireing no further restriction.
      Since UL can't distribute under the GPL they cannot distribute at all.

      I hope the FSF gets them.

  17. GPL is Free Source not Free Binaries by Anonymous Coward · · Score: 0

    If my reading of the GPL is correct. GPL and LGPL require the Source code to be free not the Binaries or the Distributions. Therefore UnitedLinux can provide the Source code for their product but they are not required to have a freely downloadable Binary.

    Remember GPL is about Freedom and I think a company should be able to add to the source and share the source without having to give their software binaries away to anybody. IMHO.

    1. Re:GPL is Free Source not Free Binaries by SirSlud · · Score: 2

      You cannot pass along GPL'd software with conditions attached that *reduce* the terms of the GPL for that receiving party. (This would be like me distributing Vendor X software and having people sign NDAs that _force_ them to break the terms of the licence attached to the Vendor X software .. what was the point of the Vendor X licence then?)

      If you give me GPL'd software, I can redistribute it if I adhere to the conditions set forth in the GPL. You cannot tell me that I must ignore certain rights given to me by virtue of you distributing GPL'd source/software.

      This is the 'viral'ness that MS hates, but its so wonderful if you think about it; you can't go out and grab value, and redistribute that value, while improving your positioning in the marketplace by reducing the rights of the people you are distributing the software to. It creates an even playing field for all; and lets us try and restore our economy to a meritocracy where people create value through collarberative work rather than information hoarding and reinventing wheels ...

      If anything, the GPL simply ensures that people can benifit from authors' work without those same people abusing the terms and conditions you'd like to attach to your software. If you dont like the GPL, create your own licence, but the whole point is that the GPL's "restrictive terms" ensure to the original author that his hard work will never be used so that somebody else can gain a competative advantage through information hoarding.

      I don't get it .. don't you think its more efficient for everybody to run as hard as they can to the finish line, even helping each other along the way, instead of spending so much time trying to trip each other up and prevent others' progress such that *everybody* runs the race slower? It seems obvious to me that the more open you make the scientific community, the more progress it can make with less work. One company might not become a true victor in a market, but who the hell cares because the whole point of this system was to encourage technological development and collarberative work in the first place ..

      --
      "Old man yells at systemd"
  18. GPL no way by Anonymous Coward · · Score: 0
    i think that all these opensource related licenses such as GPL LGPL etc. are not more than a blind hype. i understand that having the sourcecodes and beeing able to tweak inside them is nice but generally the author itself is in no way protected for his own work. personally i like linux as alternative to windows i like the tools on linux which gives me full control over my system but these licenses are protecting no one. during all the years i have seen a lot of GPL'ed software that got violated by other people, companies etc. maybe i am more a follower of rastaman (his interview some months ago) i think he is right people should be able to protect their software. they should be able to give it away so others can compile the code and install the software but it should clearly protect the persons work from others ripping the code and derivating other software out of it.

    this 'there should be no owner of the software' hype is stupid. how often has one tried to e.g. take the code of an active maintained project and making a derivate out of it and then the maintainer or programmer came up and pissed the person off who derivated his code. i think GPL is nothing else than a hype. people should be able to better protect their software.

    my expirience from all the years is that no one really cared for GPL or ever have read it or understood it. people start to care as soon as someone is comming and ripping their stuff up. look at the REDHAT KDE conversation. regarding to the GPL redhat had the right but the KDE people came along and were really pissed off.

    helping make software better and contributing to sourcecode is a good idea. but people should keep the full right of the source. they should be able to declare that others should not derivate or ripp parts of the code. (i know the sideeffects of that from code beeing duplicated) but please also think about all these companies that see all these opensource programmers as a god given present. all these FREE workers. thats sad.

    1. Re:GPL no way by JonKatzIsAnIdiot · · Score: 1

      Bill! Get on the phone and call security.
      Looks like Steve has escaped from his cel^H^H^H^H office again.

  19. Hardly unusual by leastsquares · · Score: 4, Informative

    Many Linux distributions first see light of day as closed betas. For example, the Xandros betas have been available to only a small number of people, all of whom have signed NDAs.

    As I see it, a closed beta is not a public release, and therefore not violating the GPL in any way.

    In these situations, making the full source available would not help anybody (1. slower development due to extra hassle, 2. most code is available from original sources anyway, 3. modified code will be in a state of unstable flux). At the point of full release, well, that's a different matter.

    1. Re:Hardly unusual by Anonymous Coward · · Score: 0

      It doesn't matter whether they are giving a beta to their selected volunteers --- a distribution is a distribution.

      That's why IBM doesn't do distributions --- their IP lawyers won't let them. Read this interview with IBM engineer who ported linux to the S/390.

      http://www.sslug.dk/patent/strassemeyer/transr-d el .shtml

      QUOTE

      Now let me give you an interesting story to start off with. When we had done the so called patch for 390, as I already told this morning, I had a talk with Linus Torvalds about it. I think it was early November 1999, I had an appointment with Linus Torvalds and my key engineer Boas Betzler and Boas wanted to show Linus what this patch was all about, so that he could read into it a little bit and give us advices, on how to do it differently or whatever, right?

      I had made this appointment. When our lawyers got hold of the fact that I wanted to show running Linux kernel, including our patch to Linus Torvalds they all of sudden got this idea: "What the hell are you doing? You are doing a distribution". I had no idea what a distribution is and I had not the feeling that I was distributing anything when I showed it to Linus Torvalds but I learned about those legal effects later.

      Nevertheless, they said "You can not do this". So I said: "You have a problem. I have an appointment with Linus Torvalds in three days and I will hold this appointment so you'd better make sure what I can do."

      So we found out that, I could show this nice running code to Linus Torvalds in an executive office, in an IBM lab, which was on IBM premises. And make sure that nobody took anything out so it wasn't a distribution.

      So this was what I learned: Basically after that I understood what was critical about a distribution.

      END QUOTE

      There had been no court cases on GPL since 1999 --- so IBM's legal stance regarding distribution still stands.

    2. Re:Hardly unusual by Angry+White+Guy · · Score: 2

      I wholehartedly agree. If they are trying to keep some form of order and control over their development cycle, then I say go for it! But if they don't make these sources available at the very instant that UL goes public, then nail their collective asses to the wall!

      I think that the FSF should just hold off for a bit, but be ready to do a full code audit on everything that is released. It's a big job, but hey, they're our big lawyer buddies, aren't they?

      --
      You think that I'm crazy, you should see this guy!
    3. Re:Hardly unusual by Anonymous Coward · · Score: 0

      only the crappy or lowlife ones do that...

      redhat betas are cast into the public eye for everyone to download and share with 75,000 others freely... in fact you are expected to give away a couple billion copies to friedns relatives or to force on people in the street.

      only someone with something to hide, or pure scumbags do the closed/NDA thing.....

      It's GPL, I dont care what stage you are in you HAVE TO ABIDE BY the GPL! or stop using it.

      hey they are very welcome to change to the United BSD system... if they love the BSD license so much please feel fre to leave and go there...

      Xandros is shady at best... I never did trust them. if your distro doesnt have open public betas with their guts all spread out for everyone to see... then they are losers and promoting crap.

    4. Re:Hardly unusual by rjw57 · · Score: 4, Insightful
      The problem is that any NDA which restricts the right of the beta testers to distribute the distribution is in violation of the GPL. If the NDA mentioned doesn't remove the rights of the GPL and the beta-testers just don't re-distribute voluntarily, then the GPL isn't violated.

      The GPL only protects distribution rights for the people you distribute to, it doesn't require that you personally release it publically, only that you can't stop the people you do give it to from doing so.

      --
      Rich
    5. Re:Hardly unusual by Anonymous Coward · · Score: 0

      Yes, but IBM is notoriously paranoid about copyright/patent stuff, mostly because a) their lawyers don't know what they're doing b) they twist so many other people's arms with their patents that they don't want their own arm twisted in turn.

    6. Re:Hardly unusual by Anonymous Coward · · Score: 0

      >>>Yes, but IBM is notoriously paranoid about copyright/patent stuff, mostly because a) their lawyers don't know what they're doing b) they twist so many other people's arms with their patents that they don't want their own arm twisted in turn.

      If IBM lawyers don't know what they are doing then how can they collect the most patent licensing fees amoung all corporations. Also that's IBM we are talking about --- the company who spent 1 billion dollars on linux.

      Lawyers think in legal terms. GPL license hasn't change since 1999. There has not been a court case deciding what's a distribution since 1999. Therefore, IBM's legal stance still stands.

      Whether you listen to the lawyers --- that's a business matter. But do you want to be Progress who had to permanently terminate their MySQL business.

    7. Re:Hardly unusual by Anonymous Coward · · Score: 0

      That's a practical matter --- whether they want the chaos of the public poking around unfinished codes. But you can't force this practical decision on the other people by way of a NDA.

    8. Re:Hardly unusual by leastsquares · · Score: 2



      The problem derived from how you define "distribution". You are allowed to use and modify the code for your own use and don't need to provide source to anybody else. This is still true if you are a company instead of a single person. Is a closed beta distribution outside of your company? This is the tricky, legally dubious, question. With an NDA, the testers are part of the company and therefore public distribution hasn't occurred, I think. Of course, IANAL.

      Another question is whether they are acting in accordance of the spirit of the GPL. Since they have already announced the release plans (i.e. all source available for free download) then I don't think they are. They would be within their rights to charge for access to the code, afterall.

      Don't agree? Then please write your own code. The question is not whether you will think it will help or not, the question is: Are you violating GPL?


      I do write my own code, most of which is released under the GPL, whilst the remainder is released under a BSD-like license. I know for a fact (I saw it whilst doing consultancy work) that at least one company uses a modified version of my GPL'd code without releasing the changes to the community. This is fine by me because it is for their internal use only. I'd argue that the closed beta tests are also for internal use only -- there was an NDA.

    9. Re:Hardly unusual by leastsquares · · Score: 2

      But "you" can be a company/cooperative/whatever rather than a single person. This is actually quite important.

      In most cases, software used as part of a job has to be licensed to company not to the individual (obvious example: MS office at work is licensed to the company. The linux kernel is no different in this regard). While used within the company it is not being distributed so long as only employees/partners/interns/whatever have access to it. (So once again the dubious point is whether a closed beta is to be considered public distribution, or not).

    10. Re:Hardly unusual by leastsquares · · Score: 2

      Yes.

      Except, I would have written "probably can" instead. ;) Where are the laywers when you need them?

    11. Re:Hardly unusual by Fastolfe · · Score: 2

      I would completely agree with you, if users were just being told to sign NDA's. But the concept of a "closed beta" is such that you are volunteering your time to test software for a company, in return for getting a nifty preview. In other words, you've become an agent acting on behalf of the company. You are no longer an independent user receiving software released from a company, you are acting in a limited capacity *as* the company. As a result, there is no redistribution going on.

    12. Re:Hardly unusual by Fastolfe · · Score: 2

      If this were true, GPL'd code would almost NEVER find use in a corporate environment. The biggest seller for GPL'd code is that people can modify it to suit their own needs. If a company wishes to use GPL'd code with their proprietary environment, it's quite likely some modification of that GPL'd code would be desirable to make it more compatible with that environment. If you were to force that company to release its changes, they'd have to release proprietary (and potentially trade secret) data.

      No company is going to want to open themselves up to that kind of thing.

      The fact is (as others have indicated), employees or agents of a company can *not* act as individuals when they're on the clock (and occasionally off-the-clock). If you're downloading GPL'd software on behalf of the company, YOU did not receive the software. The COMPANY did. The "recipient" of that software is the company, not you. Any changes you or other employees or agents make on behalf of the company are copyrighted by the company, and you have no rights to redistribute that until the company says you can. If the company decides to release a finished product to entities outside of that company, they're obligated under the GPL to release their modifications with it, but so long as you're acting as an agent or employee of that company, you cannot interpret the license as applying to you individually.

    13. Re:Hardly unusual by Fastolfe · · Score: 2

      Contract law recognizes corporations as individuals. When you're acting as an agent or employee of a company, YOU downloaded nothing. The COMPANY did. The company is the recipient in the context of the license, and until the company releases a piece of software, they have no obligations under the GPL to release code with it.

      If you are acting as an agent or employee of a company, and you receive software from a fellow employee, the company received software from itself. In other words, no redistribution has occurred. I can transfer a copy of software from my right hand to my left hand without ever being accused of giving it to someon else.

      The concept of a closed beta generally means you have volunteered your time for the company. You are now an agent of the company authorized to perform work (testing) in exchange for the preview. As an agent of the company, software you receive from the company has never changed hands.

      This isn't a matter of someone's "opinion" on what redistribution means. These are very standard concepts in the world of contract law. Please consult a lawyer if you are uncertain.

      If anything, the true question here is whether their NDA/other contracts do indeed qualify the participant as an agent of the company. I can see a fairly solid case indicating that they are, but not a water-tight one.

      But does it REALLY matter? When they end up releasing their finished product complete with code, is everyone still going to be so pissed with these guys for not releasing the code earlier? Come on..

    14. Re:Hardly unusual by Fastolfe · · Score: 2

      only someone with something to hide, or pure scumbags do the closed/NDA thing....

      I don't really understand this attitude. Lots of corporations make use of GPL'd software internally for their own purposes. This is the beauty of the GPL: people can modify it to suit their own needs.

      If companies were required to redistribute modifications whenever this application was deployed internally, GPL'd software would never be used in this capacity. No company wants to be forced to give out source code to the general public just for wanting to use that software internally. That's neither the intent of the GPL nor is it in the spirit of it.

    15. Re:Hardly unusual by Gleef · · Score: 3, Interesting

      leastsquares writes:

      Many Linux distributions first see light of day as closed betas.

      The fact that it's a "closed beta" is not the issue here.

      For example, the Xandros betas have been available to only a small number of people,

      What Xandros has or hasn't done also isn't the issue here. I don't know any details about what Xandros did, but I remember hearing that they talked to key Debian and FSF people. I would be surprised if they released GPL software under additional restrictions (particularly since an earlier version of their distribution got slammed for doing the exact same thing back when it was first beta tested by Corel).

      all of whom have signed NDAs.

      That is the issue. It is perfectly legal to release your own code under an NDA, or your distribution of BSD-licensed code. However, the GPL does not permit you to redistribute the software with additional restrictions, so wrapping a distribution of GPL software in an NDA is solidly illegal.

      It should be fairly simple for them to write the NDA containing appropriate holes for the GPL to peek through, something along the lines of "This NDA does not cover the software in this distribution licensed under the GPL, LGPL or any other license that explicitly precludes additional restrictions". This way, you still get a "closed beta", since nobody can redistribute the whole thing, but if people feel the need to redistribute a GPL'ed bit from inside the distribution, they retain the legal right to, as required by the GPL.

      As I understand it, the FSF is merely asking to see the text of the NDA, to ensure that it is worded so as not to violate the GPL.

      As I see it, a closed beta is not a public release, and therefore not violating the GPL in any way.

      The GPL does not say anything about "public release", it is a license for distribution, and a beta distribution, even a "closed" beta distribution, is still a distribution.

      In these situations, making the full source available would not help anybody

      I disagree, I have found source code helpful in many unexpected situations.

      Your comment here makes me wonder if you understand the situation, the question isn't "is source code helpful", the question is "is UnitedLinux violating the GPL". I'll do a simplified rundown: take Alice, Bob, Carol and Doug. Alice writes a piece of software, and releases it under the GPL. Bob creates a software distribution containing precompiled binaries of many different programs under many different licenses, and sells a copy to Carol. Neither Bob, Carol nor Doug have any interaction with Alice or her legal representatives.

      In order to legally distribute his package to Carol, Bob has accepted the GPL, and must abide by its terms (this is called a contract of adhesion). One of the terms is that he is legally obligated to make the source available to Carol (Section 3). Another is that along with the distribution, he must pass on a copy of the license to Carol, with no additional restrictions (Section 6). This ensures that, if Carol wishes, she can also accept the GPL and give a copy of Alice's software to her friend, Doug.

      If Bob distributes his collection under an NDA, that doesn't change his legal obligations to Alice. It doesn't matter that Carol can get the source from SourceForge, Bob is obligated to make it available to her himself. It doesn't matter that Bob wants to keep the details of his collection under wraps, he is required to give Carol a GPL, unencumbered by the NDA or any other additional restrictions. He can legally use the NDA to cover other parts of his collection, but not Alice's GPLed software.

      If Bob violates these terms, Alice has the legal right to sue, seek injunctions against Bob's distribution of her software, and so forth.

      The current Bob (UnitedLinux) is not necessarily violating the GPL, the FSF is trying to determine if they are or aren't. I assume, given past history, if the FSF determines that UnitedLinux is in violation, they will offer advice on how to do what they want to do without violating the GPL, and not go farther unless UL makes no attempt to fix the situation.

      (1. slower development due to extra hassle,

      Cost of doing business.

      2. most code is available from original sources anyway,

      As described above, it doesn't matter. UnitedLinux has the legal obligation to make all the source code used to produce the GPL software they distribute available to the people they distribute to.

      3. modified code will be in a state of unstable flux

      That's an easy one, the source code to make available is the source used to create the binaries being distributed. If your code is in such "unstable flux" that you don't know what you compiled in order to make the binaries, then you certainly shouldn't be doing a commercial beta distribution.

      At the point of full release, well, that's a different matter.

      No, it isn't. The GPL makes no distinction between distribution to one person, and distribution to the general public.

      Disclaimer: I am not a lawyer, the above should not be construed as legal advice. If you have an NDA to write, I strongly recommend you consult a real lawyer for advice on how to appropriately word it.

      --

      ----
      Open mind, insert foot.
    16. Re:Hardly unusual by leastsquares · · Score: 2

      This ground has already been covered, but you clearly put a lot of effort into your reply, so I think that providing a reponse is the polite thing to do.

      The initial question is whether the GPL has been violated by the UL guys as a result of their closed beta with an NDA. Such closed betas are not uncommon, even of GPL'd code. It is apparent that some of us believe this to be legal, others don't. I think everyone agrees up to the point where we ask whether a closed beta is distribution, or not. There is a fine line to be drawn.

      I am in the camp that believes that as a result of the NDA, the beta-testers should be considered as part of the organisation preparing the software for release. Therefore, the GPL is not violated since the software is only being distributed internally, which I think everyone agrees is allowed.

      Other people (probably the majority) believe that the beta-testers are not part of the organisation and therefore the GPL is clearly violated.

      It would be nice to know which side of the argument is correct.

      In UL's case the spirit of the GPL isn't broken anyway because they have already announced that all source will be freely available for download once they are ready to make a proper release.

    17. Re:Hardly unusual by Anonymous Coward · · Score: 0

      The word "beta" doesn't appear in the GPL. If UL has carte blanche to label some people as "organization members" instead of human beings with rights, what's to keep them from doing the same thing to all their customers?

    18. Re:Hardly unusual by Kashif+Shaikh · · Score: 1

      If you think NDA is allowed, then what if another company tries to sell you GPL software but you must agree to its NDA that:

      You are not allowed to disclose the source code.

      To me, NDAs are another form of licenses, and not all licenses are compatible with GPL.

    19. Re:Hardly unusual by Alien+Being · · Score: 2

      I agree. No, wait a second, I disagree.

      "Beta" testing means "outside" which does imply distribution. The line needs to be drawn somewhere. IMO, the reasonable place is in-between the Jargon File definitions of Alpha-test and Beta-test.

    20. Re:Hardly unusual by DHam · · Score: 1

      No, absolutely not. The issue that has been raised about whether distribution within a company is distribution stems from the fact that a company is a single legal entity and is therefore distributing only to itself.

      If two companies develop software together then already it is distribution every time they send each other a copy (although in this case the companies would presumably not choose to invoke their GPL right to redistribute). The relationship of a beta tester to the company is at most a contract. The beta tester is a completely separate entity. Hence giving the beta tester a copy of the software is definitely distribution and can only be done under the terms of the GPL.

    21. Re:Hardly unusual by kuiken · · Score: 1

      Since we dont know hat is in the NDa, we cant be certain
      The NDA could only cover the inhouse build stuff, in which case they can slap any restiction on they want.

      Then there is the whole since this is a closed beta, did any ditribution actualy took place question

      And the final question is, has any harm been caused to the spirit of GPL.

      It makes sense to me to not have UL in the open until it reaches a certain lvl of stability.
      This as a comercial ditribution and you would not want a buggy beta to get in the hands of some FUD spitting reviewer, hence the need for an NDA

      in my view : 100% in acordance with GPL ? No probly not
      Evil Intentions : doesnt smell like it

      --

      42
    22. Re:Hardly unusual by mpe · · Score: 2

      If this were true, GPL'd code would almost NEVER find use in a corporate environment. The biggest seller for GPL'd code is that people can modify it to suit their own needs. If a company wishes to use GPL'd code with their proprietary environment, it's quite likely some modification of that GPL'd code would be desirable to make it more compatible with that environment. If you were to force that company to release its changes, they'd have to release proprietary (and potentially trade secret) data.

      The GPL does not oblige you to distribute the code also it applies only to program code not to data handled by that code. If you alter a GPL wordprocessor the GPL does not affect any documents you have written with it, altering a GPL database does not apply the GPL to your data. In contrast there are proprietary systems which do "infect" your data.
      The vast majority of companies arn't in the business of supplying software to anyone else in the first place...

    23. Re:Hardly unusual by Gleef · · Score: 2

      leastsquares wrote:

      The initial question is whether the GPL has been violated by the UL guys as a result of their closed beta with an NDA.

      Yes.

      Such closed betas are not uncommon, even of GPL'd code.

      Which is why the FSF, whenever they find out that such a distribution has occurred, goes out of their way to make sure that the company has made it clear to their beta testers that the NDA does not cover GPL/LGPL code.

      It is apparent that some of us believe this to be legal, others don't. I think everyone agrees up to the point where we ask whether a closed beta is distribution, or not. There is a fine line to be drawn.

      I see the situation differently, it looks to me that some people here feel it ought to be legal to NDA GPL code in a "closed beta", and are coming up with spurious arguments with little to basis in fact, in an attempt to convince themselves that it is legal. I have yet to see a credible argument that it is legal.

      I am in the camp that believes that as a result of the NDA, the beta-testers should be considered as part of the organisation preparing the software for release.

      Part of the organization how? You have a contract with the company, that doesn't make you an employee of the company. Even a contractor doing a work-for-hire for a company, invokes the GPL when releasing that work to the company. How does being someone who managed to get on the beta test program make you more a part of the company than someone doing work for the company?

      Therefore, the GPL is not violated since the software is only being distributed internally, which I think everyone agrees is allowed.

      I agree that internal use is allowed, but I don't agree that you can declare use outside the company to be "internal use" so trivially.

      Other people (probably the majority) believe that the beta-testers are not part of the organisation and therefore the GPL is clearly violated.

      I would like to point out that among the people who feel that a beta test is not internal use is the FSF, the authors of the GPL, and the single largest copyright holder of GPL software.

      It would be nice to know which side of the argument is correct.

      I would like to hear the argument. You've asserted that you think it's internal use, but you haven't offered any argument that would make it internal use.

      In UL's case the spirit of the GPL isn't broken anyway because they have already announced that all source will be freely available for download once they are ready to make a proper release.

      In UL's case the contract of the GPL probably isn't broken, because chances are they will make a statement clarifying that their NDA doesn't cover GPL/LGPL code, just like Corel did in the same situation.

      The spirit of the GPL isn't "It'll be Free soon"; the spirit is: whoever uses the software has the freedom to use, examine, modify and redistribute the software. An NDA takes away that freedom. By using an NDA at all, UnitedLinux makes it clear that they are not interested in "the spirit of the GPL", but at least the law of the GPL can be enforced.

      --

      ----
      Open mind, insert foot.
    24. Re:Hardly unusual by Fastolfe · · Score: 1

      You can call it whatever you want out loud, but it's the contents of those NDA's and other contracts the participants have to sign that will be the deciding factor here..

    25. Re:Hardly unusual by Fastolfe · · Score: 1

      The relationship of a beta tester to the company is at most a contract. The beta tester is a completely separate entity.

      They are signing "an NDA", which could easily include clauses or other contracts outright that could quite easily classify the tester as an agent of the company. That's the big question here.

    26. Re:Hardly unusual by Fastolfe · · Score: 1

      I'm not sure I understand how your comment relates to mine. I was specifically referring to potential code modifications a company may wish to make with GPL'd software.

      For example, I have seen Apache authentication modules in a corporate environment that "hook in" to a proprietary authentication system within the company. This code is based on GPL'd code, but the additions are proprietary.

      If the GPL is to be interpreted the way some of you are saying, then this company would be prohibited from even passing this code around the company for use, since it would permit any Joe Employee to release it to the general public, which could potentially be very bad.

      This is probably a poor example, but it should illustrate the issue. If companies were obligated to release all of their copyrighted code along with any modifications they make to GPL'd software just by trying to use that software internally, nobody would use GPL'd software in this capacity, and that is not what the authors of the GPL ever intended. They want companies to be able to make proprietary modifications to GPL'd code. Only when that company decides to try and sell (or give away) that software (i.e. to others outside the company, obviously) should they be required to send the code along with it.

    27. Re:Hardly unusual by leastsquares · · Score: 2

      ...what if another company tries to sell you GPL software but you must agree to its NDA...

      In that case the company would be SELLING (i.e. distributing) software. I wouldn't be an agent of the company, which is what the sticky issue is here. That clearly would be a violation of the GPL.

    28. Re:Hardly unusual by Alien+Being · · Score: 1

      What other contracts? Unless they have something that shows that the "participants" were acting as partners rather than consumers, they did in-fact distribute the code just as the word Beta suggests.

      Calling it a "closed beta" is an admission that their intent was to discriminate about who was elligible to receive the product.

      UL was trying to pull a fast one and they got bagged. Their lawyers will sound like Bill Clinton trying to show how they never had "consumer" relations with those "participants".

      "Well yes, we 'gave' it to them, but we never 'distributed' it, and in any case, they were told not to inhale it."

  20. I Agree With This Post by Anonymous Coward · · Score: 0

    I agree with this post.

  21. Re:Who enforces the GPL ? by mAIsE · · Score: 0

    these guys are making redhat's look good.

    and debian look like heaven

  22. Excuse me... by stubear · · Score: 5, Funny

    ...I saw all the torches and hayforks. Is this the Frankenstein lynching party or is that one two villages over?

    1. Re:Excuse me... by Phil+the+Canuck · · Score: 4, Funny

      Nope. This here's a hangin'. You wanna be gettin' back on the highway. Head north, take the second exit.

    2. Re:Excuse me... by stubear · · Score: 2

      FINALLY!!! Someone who saw the humor in this. I was beginning to think the slashbot moderators were asleep at the wheel again, letting their autonomous anti-linx comment 'bots scour slashdot for negative comments regardless of humor value.

  23. Re:Who enforces the GPL ? by Squarewav · · Score: 1

    the GPL is just another EULA, its up to who ever created the software to sue. If they are lucky they could get some support from the free software community, but 99% of GPL software is written by people in their free time who don't have the money to sue, the thing about it is, is that most GPL software is free and as such there is no loss of money if someone steals your code, I think the most you can get is the software that uses the code to open the src that uses the gpl code, but IANAL

  24. Public Release vs Distribution by nuggz · · Score: 5, Interesting

    Being a public release or not is irrelevant.

    If it is distributed, it MUST be distributed under the terms of the GPL.

    1. Re:Public Release vs Distribution by Richard_at_work · · Score: 3, Interesting

      Ahem, bollocks. I can release a GPL program to a select few individuals who have signed agreements with me with no problems, as they can be deemed part of my company now. It has already been stated before that a company releasing software to its employees or affiliates is basically the company distributing to the company, ie itself. Thus the GPL doesnt stand.

      Do you give the source code for GPL programs to everyone who works for you? Doubt it.

    2. Re:Public Release vs Distribution by bwt · · Score: 5, Informative

      You actually have to actually be a company and they have to actually be employees. You can't just pretend you are a company. That is a sham and trying to pull that in front of a judge would not be wise.

      They can't even be "contractors", because the GPL forbids you to distribute to people with additional conditions, which your contract would impose.

    3. Re:Public Release vs Distribution by MrResistor · · Score: 5, Informative

      It is you who are incorrect.

      The only way you can release GPL code under an NDA is if you are the origional author of every single line of the code. Otherwise the origional author can invoke the GPL death penalty, removing all your rights to whatever code they wrote, and thus invalidating your NDA.

      Since UL obviously isn't the origional author of all, most, or likely even a significant amount, of the code in their distro, their NDA can probably be shot down quite easily.

      Do you give the source code for GPL programs to everyone who works for you? Doubt it.

      If you have the employees install the software themselves you are legally required to provide them with source if they request it. If you are installing it and they are merely using it, then you aren't distributing it and there is no requirement for you to provide source.

      --
      Under capitalism man exploits man. Under communism it's the other way around.
    4. Re:Public Release vs Distribution by Anonymous Coward · · Score: 1, Interesting

      If your employees screw up --- the employer is deemed to make the mistake. That's why employee distribution is an internal distribution. Doesn't work for outsiders.

    5. Re:Public Release vs Distribution by nuggz · · Score: 2

      No you can't. You would be restricting further distribution.

      6. Each time you redistribute the Program (or any work based on the Program), the recipient automatically receives a license from the original licensor to copy, distribute or modify the Program subject to these terms and conditions. You may not impose any further restrictions on the recipients' exercise of the rights granted herein. You are not responsible for enforcing compliance by third parties to this License.

    6. Re:Public Release vs Distribution by Fastolfe · · Score: 4, Interesting

      So long as a piece of code remains within a company or organization, it's not redistribution. It is a company that takes posession of GPL'd code, not individuals that happen to have a business relationship with one another. As far as contracts or licenses are concerned, a corporation is a single distinct entity, and employees of that corporation operating as employees or agents of that corporation are not "individuals" that can extend license agreements to apply to themselves individually.

      I cannot buy software on behalf of the company and interpret the terms of the agreement to mean that I can take it home and start using it for my personal purposes.

      By participating in a closed beta, you are acting as an agent of the company. The software is not being redistributed here.

      This issue has come up time and time again on Slashdot, and every time, we hash out these same arguments.

    7. Re:Public Release vs Distribution by Fastolfe · · Score: 3, Insightful

      A "recipient" is not explicitly defined to be a human being. Corporations enjoy status as individuals just as people do. You can license software to corporations, and the corporation is what ends up taking possession of the software. People acting as agents or employees of a company do not receive individual rights to software licensed to the company (which is what's happened here).

      You are *perfectly* free, however, to go download the same GPL'd software on your own time and do whatever the hell you want with it. But don't expect to be able to include your company's copyrighted code in your derivative until your company has released that code.

    8. Re:Public Release vs Distribution by Rich0 · · Score: 1
      I agree that a company is under no obligation to publish code for software internally distributed under the GPL - as long as anyone they give the software is given access to the source and allowed to distribute it freely themselves.

      That is not happening in this case. UL doesn't have to distribute the source or binaries to anybody outside of UL. However, they do have to make both freely available to any employees within UL who are part of the beta. And the employees cannot be prevented from giving it to anyone they want. If the employees choose to keep it a secret, nobody from outside can force them to publicize it - just as nobody can force you to publicize any mods you made to the kernel you are running at home. However, you can't give your specially tweaked version of the kernel to someone under the condition that they have to keep it hush-hush.

      If UL wrote the code that would be one thing. And any parts of the OS which are 100% their work which were not part of GPL projects (ie their own apps built from separate code) can be hushed by an NDA. However, any GPL code that they modified does not belong to them exclusively - they cannot release it under an NDA unless every previous author grants them a liscense to do so.

      Think of it this way. I write a book - I own copyright. I DON'T release it under the GPL. You steal my book and make 100 copies of it after changing one line in the book without a license to do so. Then you give them out to your employees making them sign an NDA saying they won't distribute them. As the author I have exclusive copyright to the book and any derivative work - therefore the book did not belong to the company to liscense in the first place. I am the only one who can decide to enforce the copyright.

    9. Re:Public Release vs Distribution by Fastolfe · · Score: 2

      However, you can't give your specially tweaked version of the kernel to someone under the condition that they have to keep it hush-hush.

      Absolutely correct. But if a company is developing a tweaked version of the kernel for use internally with their servers, those "tweaks" are copyrighted by the company. Just by passing this new kernel around, getting it deployed, or getting other developers in the group to participate, there is no redistribution going on in the context of the GPL.

      Now, if you were an employee and received one of these tweaked kernels, you would not be permitted to simply redistribute it, since you do not own the copyright on the code that the company wrote. If the company decided they wanted to redistribute it (i.e. to entities not working for the company), they'd have to do so under the terms of the GPL and would then be obligated to distribute the source as well.

      I think many of us are working under the assumption that some aspects of this UL work do have portions copyrighted by UL. Until UL decides to release this to people not acting as agents or employees of UL, their copyrighted portions cannot legally be redistributed.

      However, any GPL code that they modified does not belong to them exclusively - they cannot release it under an NDA unless every previous author grants them a liscense to do so.

      Correct, but again, I think you're overlooking a vital fact here: employees or agents for a company are not individuals. If someone downloaded GPL'd software on behalf of the company, the company received that software (and is the "recipient" in the context of the license), not the individual. When the company adds code or otherwise creates a derivative work, they can do whatever they want with that so long as it doesn't leave the company.

      The real question is whether or not a closed beta does indeed qualify the participant as an agent of the company. If it does, the software never changed hands: it remained within the company, no redistribution occurred, and no GPL requirements were violated.

    10. Re:Public Release vs Distribution by MobileC · · Score: 0

      It looks like the problem is the terms of the NDA, that is why they are asking to see a copy of the NDA before they do more jumping up and down.

      --

      Fran
      :):):)
      1st 1st Poster of the new Millennium!

    11. Re:Public Release vs Distribution by HopeOS · · Score: 2
      The GPL explicitly states that it cannot be released in this fashion. It further states that if the distribution cannot be released such that it complies with the GPL terms, it cannot be released at all. Hence, the addition of an NDA violates the GPL, and would prevent you from legally distributing.

      From the GPL FAQ:
      Does the GPL allow me to distribute a modified or beta version under a nondisclosure agreement?

      No. The GPL says that anyone who receives a copy of your version from you has the right to redistribute copies (modified or not) of that version. It does not give you permission to distribute the work on any more restrictive basis.
      And again from the GPL itself:
      6. Each time you redistribute the Program (or any work based on the Program), the recipient automatically receives a license from the original licensor to copy, distribute or modify the Program subject to these terms and conditions. You may not impose any further restrictions on the recipients' exercise of the rights granted herein...
      Seems fairly clear to me.

      Also, claiming that the individuals under NDA are thereby employees of your company will not stand up in court. The copyright holders would naturally subpoena your payroll and invalidate that argument. If you don't pay them wages, not to mention maintain and submit all the associated tax records, you do not employ them. Period.


      -Hope
    12. Re:Public Release vs Distribution by Micah · · Score: 2

      Interesting.

      The real question is whether or not a closed beta does indeed qualify the participant as an agent of the company.

      I would guess that it does not. A closed beta recipient is (generally) not being paid by the company, has no permanent relationship, is installing the software himself, and is not using the company's hardware. IANAL.

      However, UL might just be intending to apply the NDA to the non-GPL parts of the distro. Why would they care if someone took the gcc from their closed beta and redistributed it? The installer and config utilities are what they're concerned about (I think). Of course, if they have a heavily modified KDE, then they would NOT be able to keep their beta testers from redistributing that, including their modifications.

    13. Re:Public Release vs Distribution by Fastolfe · · Score: 2

      A closed beta recipient is (generally) not being paid by the company

      Compensation need not be in the form of money. The compensation here could easily be the "sneak preview" that the testers receive. If the participants got nothing back, few would want to be testers.

      Of course, if they have a heavily modified KDE, then they would NOT be able to keep their beta testers from redistributing that, including their modifications.

      There's no "of course" about it. The answer to this question depends on the first: whether or not the contractual agreement (NDA, etc.) the testers make qualify them as agents of the company. If they don't, then I agree, but if they do, then redistribution depends on the terms of that contract. The terms of the license (whatever style license it is) apply to the company here, remember.

    14. Re:Public Release vs Distribution by Chops · · Score: 2
      Nay, bollocks to you, sir. GPL 2 section six, straight from /usr/share/common-licenses:
      6. Each time you redistribute the Program (or any work based on the Program), the recipient automatically receives a license from the original licensor to copy, distribute or modify the Program subject to these terms and conditions. You may not impose any further restrictions on the recipients' exercise of the rights granted herein. You are not responsible for enforcing compliance by third parties to this License.
      Emphasis is mine.
    15. Re:Public Release vs Distribution by Micah · · Score: 2

      Granted that this is just gut instinct, but I really don't think that would fly. By any reasonable definition, a beta tester is NOT part of the company. In fact, going back to the original definitions, alpha testing is done inside the company and beta testing is done outside the company, once the product is deemed to be in somewhat stable shape internally.

    16. Re:Public Release vs Distribution by Fastolfe · · Score: 1

      a beta tester is NOT part of the company

      All things being equal, I agree.

      But I don't know what those NDA's and other contracts the participants had to sign said.

    17. Re:Public Release vs Distribution by Anonymous Coward · · Score: 0

      pwned!

    18. Re:Public Release vs Distribution by Anonymous Coward · · Score: 0

      read

      Contracts are incapable of aural impression upon the observer.

    19. Re:Public Release vs Distribution by Fastolfe · · Score: 1

      http://www.dictionary.com/search?q=said

      say
      v. tr.
      5. To report or maintain; allege.
      6.
      a. To indicate; show: The clock says half past two.
      b. To give nonverbal expression to; signify or embody: It was an act that said "devotion."

      Go away.

    20. Re:Public Release vs Distribution by Rich0 · · Score: 1
      I'm not 100% in agreement on the individual vs. corporate arguemnt you're making, but IANAL, so let's take a different approach.

      What happends when beta tester gets annoyed with company one day after receiving the code and decides that they are no longer part of the company. Now they are an individual, and they are in possession of the software. Is it legal for the NDA to prohibit post-employment distribution?

      Also - I think that most of those corporate lawyers working for UL would argue rather vehemently that those beta testers are NOT company employees were one to sue to receive benefits (ala contract employees at Microsoft). Companies generally prefer to keep the number of official employees low so that they can get around labor law requirements. (Aside - pretty soon a typically company will have one employee - a secretary who pays the bills submitted by the agencies managing every employee from the CEO on down... Actually - it will be one bill - a huge check in the amount of the balance sheet expenses, as the subcontractor will effectively do all the work but won't keep any cash onhand to settle lawsuits with.)

  25. Amazing! by Jason+Earl · · Score: 5, Insightful

    RedHat has been handing these guys their hats for years now, and they still don't get it. It's the developers and the systems administrators that get Linux in the door, and likewise it is the developers and systems administrators that end up picking the distribution that gets deployed when the suits finally get the go-ahead. This is actually good news for distributions like SuSE, or Connectivain that if management makes the decision you can bet that they are going with RedHat, because they are perceived as the front-runner.

    SuSE, SCO, Turbo, and Connectiva have to have made this connection by this point. After all, SuSE and SCO have had distributions that were as good or better than RedHat since the earliest days of RedHat's existence. Yet RedHat consistently has grown their market share and nabbed the big customers while the rest have struggled. The reason for RedHat's success is simple, they release their code under the GPL, and they actively court developers and systems administrators. Not that RedHat is neglecting CIOs. I am sure they are schmoozing the heck out of those guys too, but they realize that Freedom is an important selling point for Linux.

    Think about it for a moment. As a developer or systems administrator which distribution would you rather deploy? Would you deply the distribution with FTP access to their emerging beta version or the distribution that requires you to sign an NDA before they will send you the binary-only CD? The choice for anyone that has ever banged his head against some piece of black-box software is obvious. Even CIOs are starting to get this.

    1. Re:Amazing! by Anonymous Coward · · Score: 0

      AGREED 100% !!! AND i don't know about you guys BUT RedHat will continue to be the product THAT I BUY FOR MYSELF AND MY COMPANY simply because their support for the community and the user is VERY CONSISTENT.

      You want to see what the next redhat release is...

      Get the NULL Beta ISOs (or any redhat ISO for the matter of fact).

      You need a good online database to look for bugs

      Go to redhat.bugzilla.com

      Also RedHat has TONS of online documentation and they are always helpful when we call for support (which is not very often).

      I do like some other distros alot, but redhat has a good thing going and they are RELIABLE.

      sorry to sound like a redhat cheerleader.

    2. Re:Amazing! by Anonymous Coward · · Score: 0

      I get my Red Hat CDROM sets from CheapBytes, even though Red Hat doesn't allow them to call it Red Hat Linux anymore. They sell the same thing, but it's only about $5.

      Spread the word.

    3. Re:Amazing! by Anonymous Coward · · Score: 0

      I would much rather deploy SuSE and tell everyone it's fscking RH if that's what
      matters to the image fascists.

      my unknown, taxed .02

    4. Re:Amazing! by 1gor · · Score: 1

      Fully agree. The main selling point of Free Software for corporate sector is not its short-term price sticker. It is mitigation of single-vendor risk and therefore long-term costs. RedHat adherence to open source is just sound business strategy. And UL looks clueless as far as business is concerned. Maybe they are better programmers...

      --
      --
  26. Is this only a temporary violation? by gosand · · Score: 2
    I find this interesting, because it seems like this is just a temporary violation. They distributed their beta with an NDA, but it is assumed that once they go GA with it, there will be no NDA and the source will be available.

    Yes, releasing a closed-beta seems to be in violation of the GPL, but how else would you do it? If you created some software, and you wanted to just give it to a few select people for evaluation, you couldn't do it under the GPL. Distribution is distribution, and you must allow them to re-distribute it. This seems like a flaw to me. This assumes, of course, that you are planning to "officially" release it at a later date under full compliance of the GPL. Hmm, anyone have an answer to this?

    --

    My beliefs do not require that you agree with them.

    1. Re:Is this only a temporary violation? by Lumpy · · Score: 1

      yes do what redhat and mandrake does... public betas...

      why not? whata re you trying to hide?

      --
      Do not look at laser with remaining good eye.
    2. Re:Is this only a temporary violation? by Anonymous Coward · · Score: 0

      Easy. Make the collection undistributable (you can't distribute the whole as "Foo beta 1"), but the components distributable with the caveat you can't distribute them as a set or say where they come from.

  27. Another violation: the process by Anonymous Coward · · Score: 0
    I've reported a pretty ginormous GPL violation to the FSF. They got back to me pretty quickly, investigated, and now..? Now it's on queue waiting for free lawyer slots. I guess it's a money issue: although I always thought the FSF, along with the EFF, would be the two best funded community organisations, it seems that not many of us have actually sent them any cash!

    That said, I'm sure when they do get to tackle the large nasty infringer, they'll take 'em to the fsckin' cleaners . And I'll be cheering! :-)

  28. Find a user! by nuggz · · Score: 2

    Has anyone been able to find a user who has this distribution.
    Perhaps the FSF can get the terms from them

  29. The adventures of RMS: Defender of the GPL by sfraggle · · Score: 5, Funny
    Deep inside the Free Software Foundation's secret underground headquarters:

    BMK: RMS! The GPL software alarm! Someone somewhere is releasing GPL'ed software under a non-GPL compatible NDA!

    RMS: I might have guessed.. my arch nemesis the greedy capitalist Ransom Love, now using the power of his UnitedLinux alliance. Quick, Bradley, to the GNU-mobile!

    ....... several minutes later, outside the UnitedLinux building ....

    RMS: So, Ransom Love, still up to your old tricks eh? And still using names for products that dont properly reflect the GNU project's contribution as well!

    RL: Theres nothing you can do this time, Stallman! I'm releasing this beta and theres nothing you can do to stop me!!

    RMS: Not so fast, Love. You didnt reckon with my MAGIC BEARD!

    RL: OH NO!!!!

    **** ZAP ****

    ....... later, back at the FSF headquarters ....

    BK: Well, RMS, we certainly stopped that evil Ransom Love.

    RMS: Yes Bradley, for the time being the world is safe again from the evil of Proprietory Software. But who knows when software hoarders will attack next?

    Meanwhile, in the ruins of the UnitedLinux HQ..

    RL: It's not over yet! I'll get you next time Stallman, next time!!!!

    --
    were you expecting to see a sig here? perhaps you'd rather see the inside of an ambulance!
    1. Re:The adventures of RMS: Defender of the GPL by Anonymous Coward · · Score: 0

      well as funny as this sounds... unfortunately it's not RMS who writes all the nice opensource software that dirty companies are going to sell for their own profit. at the final end it's the little programmer that wasted all his energy for nothing.

    2. Re:The adventures of RMS: Defender of the GPL by Anonymous Coward · · Score: 0

      It's RMS and the FSF who protect it, tho.

    3. Re:The adventures of RMS: Defender of the GPL by LMCBoy · · Score: 1

      hilarious! thanks :)

      --
      Liberal (adj.): Free from bigotry; open to progress; tolerant of others.
    4. Re:The adventures of RMS: Defender of the GPL by Anonymous Coward · · Score: 0

      yeah dream on.

  30. How does an NDA violate the GPL? by dasmegabyte · · Score: 2, Insightful

    NDAs generally prevent you from talking to people OUTSIDE a beta group about the product. Little prevents you from talking to others in the group about it.

    The GPL guarantees copyleft to the "community" and availability of source to customers. As long as the beta members can get the source are free to share their changes to the source with other members of the beta group, they've maintained these rights, NDA or no. And UL doesn't have to worry about supporting a thousand different takes on a hundred different betas -- or about unfair reviews based on "stolen," partially working prereleases of their distro.

    I've read the GPL a couple times, and have never gotten the perception that it prevented a company from preserving its right to sell a product and not offer Joe Q. Hacker full rights to recompile the source. As long as actual customers have rights to source, and a forum for sharing updates, I think there can be "closed" projects that maintain the GPL.

    --
    Hey freaks: now you're ju
    1. Re:How does an NDA violate the GPL? by J'raxis · · Score: 1

      Anyone to whom the binaries are distributed must receive the source code, without restrictions. The beta people have received binaries, and thus must be able to A) receive the source and B) cannot be bound by any contract that prevents them from giving said source code to anyone they choose to.

    2. Re:How does an NDA violate the GPL? by Chops · · Score: 2
      I've read the GPL a couple times, and have never gotten the perception that it prevented a company from preserving its right to sell a product and not offer Joe Q. Hacker full rights to recompile the source.
      Ah yes, when you download a pile of software other people wrote, slap a shiny new sticker on it, and sell it for a profit, nothing is more important than the right to prevent the greedy thieving unwashed masses from copying it amongst themselves without paying you for the privelege.

      Pity the founding fathers didn't think of that one, isn't it? All this hassle could have been avoided.

      ;-)
  31. Why UnitedLinux is doomed by Walter+Bell · · Score: 1, Troll
    Having worked in the past for a large Linux company as an evangelist and valuation forecaster, I can assure you that UnitedLinux has a bleak future. However, it is not because of the GPL or any other reasons that most often get mentioned on Slashdot. The weaknesses of this coalition go far beyond licensing issues. To start, let's take a look at the founders:
    • SCO. Formerly "Caldera," the one Linux company who released their distribution as crippleware as they tried to compete with dozens of other vendors who gave their distros away for Free. You can see where this is heading. Caldera is run by a bunch of Ivy League suits who think that the old fashioned business ideas of monopoly, per-seat licensing games, and control over the source code can easily be used to sell a Linux distribution. SCO has an abundance of clue, but unfortunately it all left the company when they laid off the Unixware developers.
    • TurboLinux. Are they even still alive? I have many friends who are Linux geniuses (one of them is the president of the local LUG) and none of them know anybody who runs TurboLinux, much less pays for it. The simplistic reasoning behind this is that if somebody wants to run RedHat 3.0, they will just download a copy of RedHat 3.0, instead of buying it from TurboLinux.
    • Connectiva. This is another pointless Linux distribution. The one advantage that Connectiva has is that their VCs did not wise up as quickly as other VCs did, to the fact that they produce nothing of value. Everything that Connectiva offers is done better by some other distribution.
    • SuSE. The distribution that prides itself on a half-baked, closed-source installer and too many installation CDs to count is also a distribution that has no future. Mandrake has usurped the European market and most other potential SuSE users, simply by virtue of being a better distribution. SuSE once earned a bright yellow star in my book for funding so much research and Linux development projects, but nowadays the only such project they have left is ReiserFS and that is so unstable that even Gentoo (!) recommends against its use.
    Now, now that we can see that every company that is a major part of UnitedLinux is doomed, let's take a look at the other stumbling blocks that they will face before they each go bankrupt:
    • UnitedLinux aims to make money off the backs of the best developers. The UnitedLinux coalition, unable to cobble together a decent distribution of their own, fully intends to pilfer the best features of Debian, RedHat, Mandrake, and Gentoo Linuces, and then add a tiny bit of closed-source software to make their distro difficult to copy legally. This is unethical and violates the spirit, if not the letter, of the GPL.
    • UnitedLinux lacks a good package manager. As a so-called "cracker," package management is *the* most important thing I consider when I choose a distribution. Debian has dpkg/apt (which is excellent, if you are lazy enough to use binaries). FreeBSD and Gentoo have their superior ports trees, which make bug fixes a cinch. And Mandrake has its own proprietary system, which is also great. UL has none of the three, and will rely on the outdated and frequently annoying RPM system. Shame on them.
    • UnitedLinux has no business support. Businesses prefer to get things for free instead of paying for them, so it is no wonder why my company tells us to head to linuxiso.org instead of UL when we need a new Linux CD.
    In summary: I will not be sad to see UnitedLinux die. It is a terrible idea whose day of reckoning has arrived.
    1. Re:Why UnitedLinux is doomed by justins · · Score: 2, Informative

      SuSE. The distribution that prides itself on a half-baked, closed-source installer and too many installation CDs to count is also a distribution that has no future.

      Of course, it's not actually closed source. Unless your definition of closed source is "not GPL."

      Hint: the yast*src.rpm files have what you seem so worried about. ftp://ftp.suse.com/pub/suse/i386/8.0/suse/zq1/

      --
      Now before I get modded down, I be to remind whoever might read this that what I am saying is FACT. - bogaboga
    2. Re:Why UnitedLinux is doomed by Anonymous Coward · · Score: 0

      nice troll you dumb dick

    3. Re:Why UnitedLinux is doomed by rossz · · Score: 3, Informative
      SuSE. The distribution that prides itself on a half-baked, closed-source installer and too many installation CDs
      That half-baked installer is the best, easiest to use installer of all the Linux distros. I always recommend SuSE to Linux newbies because of their outstanding installer. Too many CD's? There's a funny argument. They're giving you too much! Stop this evil! What bullshit. Three CD's for the personal version, that includes source code. Seven CD's for the professional version (or a single DVD), again the source code is included. You don't have to spend hours downloading everything if you want to do some kernel bashing.

      --
      -- Will program for bandwidth
    4. Re:Why UnitedLinux is doomed by Ed+Avis · · Score: 3, Informative

      Er, both Mandrake and SuSE use RPM for package management. I think you are talking about whatever layer they slap on top for resolving dependencies and the like. Mandrake has urpmi (which is free software); SuSE has some new thing for their upcoming distribution (which will probably be non-free, like YaST).

      BTW - if you value package management so highly, why dismiss Conectiva? They're the folk behind apt-rpm.

      (I realize the parent post may have been a troll but if so it was a fairly cogent troll and worth replying to.)

      --
      -- Ed Avis ed@membled.com
    5. Re:Why UnitedLinux is doomed by fire-eyes · · Score: 1

      * SuSE once earned a bright yellow star in my book for funding so much research and Linux development projects, but nowadays the only such project they have left is ReiserFS and that is so unstable that even Gentoo (!) recommends against its use.

      The x86 Gentoo install guide no longer has such a recommendation.

      P.S. I've been using reiserfs for about a year and a half, no major problems. But i've had major problems with ext2, ext3, xfs...

      --
      -- Note: If you don't agree with me, don't bother replying. I won't read it.
    6. Re:Why UnitedLinux is doomed by Anonymous Coward · · Score: 0

      So, you recommend SuSE for newbies, and then recommend what? They install three dozen text editors? Four score e-mail clients? A trio of webbrowsers?

      Pick one of each when they have no experience with any?

      Oh, wait, that's right, they should just listen to your totally unbiased opinion. *nods sagely* ..And they wonder why some people find Linux not to be user friendly.

    7. Re:Why UnitedLinux is doomed by jfunk · · Score: 2
      Of course, it's not actually closed source. Unless your definition of closed source is "not GPL."


      C'mon, most Slashdotters are completely incapable of performing basic fact-checking. It's as if they've never written a paper before.

      I think I'm the only person on Slashdot to ever point out the GPL parts of SuSE's installation programs.

      That's pretty sad.
    8. Re:Why UnitedLinux is doomed by Anonymous Coward · · Score: 0

      UnitedLinux=Baby(Microsoft)

    9. Re:Why UnitedLinux is doomed by Anonymous Coward · · Score: 0

      You better have a talk with Ed Avis. His post (on the level of the parent of your post) mentions the "non-free" SuSE tools. There are a few fashionable things to say at any given time, and when SuSE is concerned, their installer/maintainence tools always catch shit. As a big fan of SuSE, I'm always happy to see any misinformation pertaining to this corrected. I think that SuSE is a good choice for just about anyone who doesn't want to compile his/her box's apps from source (gentoo), regardless of experience.

    10. Re:Why UnitedLinux is doomed by Anonymous Coward · · Score: 0

      Goddam..thank you, thank you...
      reiserfs is so nice to me.
      I have had jfs, ext3 support shit all over
      the fs.
      Using reiserfs with LVM volumes is the best effing thing that ever happened to me.

    11. Re:Why UnitedLinux is doomed by kuiken · · Score: 1

      No i do it constantly aswell but, ppl here seem to think its its more fun to spread FUD

      --

      42
    12. Re:Why UnitedLinux is doomed by kuiken · · Score: 1

      Jezus, the Yast liscence basicly says do what you want but dont make money of it.
      can we stop beating this horse already ppl

      --

      42
  32. The question si really... by greenskyx · · Score: 1

    Should we care about this right now? They are working on getting a good product ready. If they ship a product and don't give access to the source then we should get upset. Maybe everyone should chill on this and just be happy that people are working on a standard Linux base.

  33. wake up!!!! by Anonymous Coward · · Score: 0

    these guys don't give a FUCK about the "community".... and guess what.... they don't need to. If they *barely* comply with the GPL and the community hates them,..... who cares? They get your software anyway. And even if they don't comply with the GPL, who is going to sue them? I find it comical the the linux "community" feels that its "support and trust" are so vital to a Linux company. To be honest, it doesnt mean shit. And they know it. You support doesnt generate revenue. Selling software does. Now, this is not to say that what they are doing is right. I don't believe it is. But until the GPL can be strongly held up in court as a legitamately enforcable license.... all the community support doesnt mean shit.

  34. +5, INFORMATIVE?? by Anonymous Coward · · Score: 0

    He linked to the Register's mirror of the exact same article the story links to!

  35. Call me a cynic... by perrin5 · · Score: 4, Insightful

    Look,

    Anyone commenting "Those bastards shouldn't violate the GPL!!!!" need to read the article, and if they have, they need to get their critical thinking caps on and RE-read the article. For all of you who just skim over the comments before making your own (I know you're out there), Here's a brief synopsis:
    our "heroes" (the writers of this rather elitist sounding article) were concerned about the closed beta testing that went on, and asked how they "got away" with it w/o violating the GPL. UL said something non-commital, which the article attempted to paint as evil, and included a letter from the FSF asking to SEE the NDA that beta testers had to sign.

    THAT'S IT!! There is NO PROOF OF ANYTHING. TO my mind, this is just a giant FUD (yep, I said it) to drum up anti-UL sentiment. The UL people didn't say anything bad during the conference call, as far as I can tell, but the tone of the article is set up to riducle and shame the UL project for anything it said out of line. (see the crack about "line-ux"...

    So maybe I'm over-reacting - but on the other hand, just cause you're paranoid, doesn't mean they're not out to get you.

    just my $.02

    --
    hmmmm?
    1. Re:Call me a cynic... by Jungle+guy · · Score: 1

      I was at the conference call and they said the beta and the sources would be abaliable for selected partners. It seems the NDA was made to prevent leaks outside this "circle of thrust". I don't know if it violates the GPL, but the FSF is trying to read the NDA. They are not accusing United Linux of breaking the GPL, at least not yet.

  36. Re:Who enforces the GPL ? by tchuladdiass · · Score: 2, Informative

    Actually, you can sue for what would be a resonable ammount for you to charge for an alternate license. That is, you can license your code under the GPL, but if soneone doesn't want to be bound by it, they can negotiate a seperate license with you (i.e., if they wanted to keep their changes proprietary). Therefore, you could sue for what you would charge for this alternate license, plus treble damages.

  37. The FSF owns the copyright on glibc by JoeBuck · · Score: 3, Informative

    We don't know whether any actual violation has taken place. However ...

    No Linux distribution can do anything without the C library, which is owned by the FSF; they would have grounds to shut down UnitedLinux totally if, in fact, UL has violated the LGPL. All they have to do is invoke the clause saying that a violator permanantly forfeits rights to distribute the work in question. Without the right to distribute glibc, you can't ship a Linux distribution (unless you want to write your own C library from scratch or try to port one of the BSD C libraries).

    1. Re:The FSF owns the copyright on glibc by Frater+219 · · Score: 3, Informative
      All they have to do is invoke the clause saying that a violator permanantly forfeits rights to distribute the work in question.

      I don't see a clause like that in the GPL. Could you point it out?

      I do see section 4, which says that "[a]ny attempt otherwise to copy, modify, sublicense or distribute the Program is void, and will automatically terminate your rights under this License." However, that provision does not imply that the violator is attainted against receiving a new license ... which is as simple as downloading a new piece of the covered software.

      (In programmatic terms, you need an instance of permission in order to legally redistribute copyrighted works. If you violate GPL, you destroy your instance of permission (and, more importantly, you break the law in so doing). However, just because you destroyed an object doesn't keep you from getting a new object of the same class later on ... and you get a new GPL license with every copy of the software.

      License * foo; /* pointer to a license instance */
      foo = new License(LGPL, glibc); /* get a license */
      foo->violate(); /* implicitly deletes foo */
      foo = new License(LGPL, glibc); /* can still get a new one */

      To summarize: The GPL does not contain any terms which "taint" violators from re-accepting the license in the future, nor which withdraw the offer of future licensing. The GPL's "teeth", basically, are not license revocation but copyright law.

    2. Re:The FSF owns the copyright on glibc by GooberToo · · Score: 2
      However, that provision does not imply that the violator is attainted against receiving a new license ... which is as simple as downloading a new piece of the covered software.

      I'm so tired of seeing this odd logic. The fact of the matter is very simple. The spirit on the license is very clear. You violate, you no longer have a legal license. Period. That's the spirit. Why is it clear? Well, obviously the intent it to prevent people from violating the terms of the license. It's not much of a deterrent if you can simply do a download per day to receive free reign to violate the law.

      I have no idea why this concept is so hard for people to grasp.

    3. Re:The FSF owns the copyright on glibc by lmfr · · Score: 1
      You don't get a new licence with each copy, you just get a licence to use the software. You break the licence, you forfeit any use to the software.

      This is the same case as the MySQL vs Nusphere that ended up being solved without the GPL.

    4. Re:The FSF owns the copyright on glibc by Chris+Burke · · Score: 2

      I don't think that is the spirit of the license. The spirit of the license is not to punish noncompliance, but to encourage compliance. If they start distributing again and comply with the GPL, making their changes available, that is the best outcome, no?

      Punishment is already available through copyright law, if you wish to seek it. The GPL need do nothing more but say "if you don't agree to these terms and distribute, you are violating the law".

      --

      The enemies of Democracy are
    5. Re:The FSF owns the copyright on glibc by GooberToo · · Score: 2

      Somehow you've missed the point completely.

      You came real close. Someone stated that I can break the law all I wany by simply downloading another copy, thereby, obtaining a new license to use. In that vein, if such logic were true, then copyright doesn't even come into play as you've granted me right to the software therefore, I'm not in copyrigh violation.

      Such assumptions are insane. In other words, simply downloading again does not suddenly make you in compliance with the terms of license if you have previously broken them. This is why when these things happen it's been so important that the violators be forgiven. Which means, they can once again download and then reasonably expect to have a valid license for use.

    6. Re:The FSF owns the copyright on glibc by Chris+Burke · · Score: 2

      Someone stated that I can break the law all I wany by simply downloading another copy, thereby, obtaining a new license to use.

      No, that's not what he said. I think you missed the point by mistakenly seeing that. In fact, he was saying the opposite -- that despite the fact that you can get a new license to distribute, you have already broken the law, and thus the GPL itself need do nothing to try to punish violators. That's what the phrase "the GPL's "teeth", basically, are not license revocation but copyright law" meant.

      The argument was about whether violating the GPL means you can never distribute that piece of code again, and the answer is that the GPL does not say that you forever lose access to the code. But just because you can distribute the code in the future without breaking the law doesn't mean you aren't liable for breaking the law before (duh).

      Are we in sync now?

      --

      The enemies of Democracy are
    7. Re:The FSF owns the copyright on glibc by dmelomed · · Score: 1

      Then, there's also the issue of legality of licensing. Does the law say anything about EULAs being a binding legal contract? No. AFAIK the law is only concerned with copyright. Therefore, as long as copyright is not violated, anything else the license disallows can be ignored.

    8. Re:The FSF owns the copyright on glibc by unleet · · Score: 1

      sorry, but the (L)GPL also states that your right to use the software is outside its scope.

      so the right to distrubute may be lost for violation, but your right to use can never be taken.

    9. Re:The FSF owns the copyright on glibc by mpe · · Score: 2

      Then, there's also the issue of legality of licensing. Does the law say anything about EULAs being a binding legal contract?

      Which isn't relevent here since the GPL is not and EULA in the first place.

      No. AFAIK the law is only concerned with copyright. Therefore, as long as copyright is not violated, anything else the license disallows can be ignored.

      If you attempt to distribute GPL copies works in violation of the GPL then you have broken copyright. Remember that by default you cannot distribute copies at all.

    10. Re:The FSF owns the copyright on glibc by lmfr · · Score: 1
      You violated my rights, you lose all rights to use my works. That seems simple to me.

      Please note that the gpl states that the rights to use are outside of its scope because they are already covered by standard law. You (hypothetic, of course) violated that law.

  38. doomed by Anonymous Coward · · Score: 0

    opensource is a fucking hype GPL and LGPL are too. as some of the other writers said. you can't sue these companies. if you start to sue them for every violation then at the final end FSF will loose a shitload of money for the lawyer etc. so who the fuck cares as soon as you start releasing for free others come up and rip your shit.

  39. Slashdotted! by Anonymous Coward · · Score: 0

    UtedLinux held a telephone party today t' annouss new genehal manageh Paula Hunteh 'n talk bou' its open beta release. Lots of curious dgournalists showebuhd up. De kesshun-askehs all had a cynical air bou' dem, 'n yet UtedLinux bigwigs didn't seem surprisid by de grilligg. De undehlyigg kesshun still: what will UtedLinux mean in de big picture dat is Linux bidness, duh...uh...? Our kesshun: what bou' de GPL, duh...uh...? (Also inside, uh uh uh, an open letteh t' de UtedLinux group from de FSF.)

    De UtedLinux peoble shieldid Hunteh from habigg t' answebuhr any technical kesshuns bou' Linux (or Line-Ux as the, errr, confehess call coordinator pronoussd it), when someone askid dgust duh, how much expehiess she's had wid Linux 'n Free Soffware anyway. Um uh.Some dought it obb dat Ransom Lobe is no longeh in de picture eideh at SCO or UtedLinux (Paula didn't real habe an answebuhr f' dat eideh.)

    And dehe was talk from some dgournalists bou' de possibiltiby of the, ERRRR, seprit Linux c'panies dat make up UtedLinux sip mehgigg t' f'm one gigannic Linux behemod dat cudd be de unstoppaggle Goliad all corporate guys lust affeh. Duh.UL battid its eyelashes at dat suggesshun, not willigg t' play kiss 'n tell dgust yet.

    But what webuh at NewsF'ge real wantid to know was duh, how UtedLinux is plannigg t' stay true t' de heart of Linux -- de GNU Genehal Public License. Nobody else seemid innerested, uh uh uh uh, so webuh askid how UL managid to release a closid beta 'n still c'p wid the, duh uhh, tehms of de GPL.

    Duh. UtedLinux admittid it had its partnehs sign a non-disclosure agreemin in ordeh t' use the, errr, closid beta, which like means dat UL biolatid the, errr, copyrite of kehnel debelopehs ebehywhehe 'n odehs who habe contribootid t' GNU/Linux. If de NDA was struckurid so dat de GPL wudd take precedess on non-propriet, Free Soffware elemins of the, ERRRR, soffware, den dat NDA wudd not biolate the, duh uhh, tehms of de GPL. It is more like, duh, howebeh, dat de NDA skashid de GPLid freedoms by f'cigg recipients of the, errr, closid beta t' agree dat dey wudd not redistriboot any porshun of the, ERRRR, soffware.

    Brabbley Kuhn, executibe direckor of de Free Soffware Foundashun, was also on the, errr, confehess call, 'n he askid de UtedLinux hosts if dey wudd be willigg, as a show of solidarity wid de Free Soffware 'n Open Suhce commuties, duuhhhh, t' open up deir NDA t' inspeckshun in ordeh t' show dat dey did c'p wid the, duh uhh, tehms of de GPL. Dey said dey'd take dat undeh adbisemin. Uhhh....But I wuddn't hold my bread.

    Kuhn follid up his phone kesshun wid dis open letteh, sent today t' all membehs of UtedLinux:

    Dear UtedLinux Board of Managehs, duuhhhh,

    On the, errr, confehess call annoussmin dat occurrid on 18 Septembeh 2002, you indicatid dat you'd be willigg t' release t' de Free Soffware commuty the, duh uhh, tehms dat of your "closid beta" NDA, t' show dat your closid beta was indeid distribootid in c'pliass wid the, duh uhh, tehms of de GNU Genehal Public License 'n de GNU Lesseh Genehal Public License.

    As you know, uh uh uh uh uh uh, distribushun of any type is still distribushun undeh copyrite law, uh uh uh uh uh uh, 'n dud rekires dat you propeh c'p wid tehms of GPL 'n LGPL. Of cusse, uh uh uh, it is your prehogatibe t' distriboot on to dose parties you wish t' receibe a copy, but you may not restrict dose parties' rites undeh GNU GPL 'n LGPL.

    Duh, howebeh, siss near all of de bolunteehs from de Free Soffware commuty (your fellow debelopehs) did not receibe a copy of the, ERRRR, so-callid "closid beta", webuh ask dat in a show of good faid, you make abailaggle at least the, duh uhh, tehms of distribushun you usid f' dat produck. GEE danks.

    Eben as you release your new produck t' de public, de past situashun must be clarified. Not on does the, errr, commuty desehbe t' know, uh uh uh uh uh uh, but I also beliebe it behoobes you t' put t' rest 'n clarify de legal ambiguities dat arise natural from doigg a "closid beta" of GPL'id soffware.

    I look f'erd t' your pr'pt reponse, uh uh uh, 'n dank you f' takigg my kesshun today. I presume dat you are ackigg in full c'pliass wid GPL; dis is dgust a matteh of clarifigg dat fack f' the, errr, commuty.

    Sissere, Brabbley M. Kuhn
    Executibe Direckor, Free Soffware Foundashun

    Odeh so-callid Linux adbocates don't seem t' be too cossernid bou' the, errr, closid tendencies showigg up in UtedLinux: Linux Innernashunal 'n de Free Standards Group are two .orgs dat habe endorsid de group, c'posid of Turbolinux, SCO, SuSE, 'n Coneckiba. Uhhh....Pundits habe suggestid dat Linux Innernashunal 'n de Free Standards Group may habe eben signid NDAs demselbes.

    So what's de big deal, duh...uh...? UtedLinux is goigg t' put a public beta online in de next weebuhk or so, 'n the, ERRRR, source code will be inclubed f' free (eben dough it doesn't habe t' be free). UL will on charge f' commehcial use. But will dey inclube the, ERRRR, source on dat, duh...uh...? And will dehe be anodeh NDA t' sign, duh...uh...? Dat's de big deal: Is UtedLinux down wid de idea behind soffware libre, uh uh uh, or are dey dgust tryigg t' become a Rid Hat killeh 'n Linux oligopo in ordeh t' make some fast bucks, duh...uh...? Afteh all, Turbolinux, SCO, SuSE 'n Coneckiba habe not been known as staunch Free Soffware adhehents -- unlike two odeh commehcial distros: Mandrake 'n Rid Hat, GEEEHEEHEEE.

    Alittle more openness, duuhhhh, alittle more commucashuns, duuhhhh, 'n maybe a peek at de NDA wudd go a long way in debelopigg trust in the, errr, commuty which has so genehous probidid to UL years of hard work on de Linux kehnel 'n odeh Free Soffware.

  40. GPL guarantees copyleft to the ?? by nuggz · · Score: 4, Informative

    The GPL gives you the right to distribute the source and binary to anyone YOU choose, and does not allow anyone to restrict you from doing so.

    If the NDA does not permit them to use the GPL redistribution clause, then they were not provided with the software under the terms of the GPL and hence UnitedLinux was distributed illegally, in violation of copyright law.

    1. Re:GPL guarantees copyleft to the ?? by Anonymous Coward · · Score: 0

      No. Go and actually read the GPL. Conditions 5 and 7 specifically. You can enter an agreement to not accept the GPL license and still use the software. The GPL does not restrict any rights you have if you choose not to accept the license. Moreover, if you do agree to the GPL and have an additional agreement, such as an NDA, that agreement restricts only your ability to distribute the software when you cannot fulfill the obligation of the GPL. It in no way restricts distribution of the software when you can fulfill the obligation of the GPL or usage of the software according to any rights you may have without acceptance of the GPL.

    2. Re:GPL guarantees copyleft to the ?? by nuggz · · Score: 2

      Actually if you choose not to accept the agreement, you may not distribute the software.

      Read Section 6 in the middle of those two points.
      When UL distributes it to someone they automatically get the right to redistribute it and UL may not impose any further restrictions on the recipients' exercise of the rights granted herein

      http://www.gnu.org/copyleft/gpl.html

    3. Re:GPL guarantees copyleft to the ?? by bovinewasteproduct · · Score: 2

      The questions is: What does the NDA say?

      If the NDA only applies to installers, custom software and the like, all bets are off. Sure they can talk about libc, KDE and gcc all they want, they can even redistribute them. But they can't talk about the installer, the enterprise management system or whatever. Nor can they redistribute those programs or the source, they are NOT GPL.

      As long as any of those programs do not require GPL software to function (outside the granted exception of kernel modules), then the NDA can apply to them just fine.

      BWP
      obDisclaimer: I have NO IDEA what is under the hood of UL, these things just came out of thin air.

  41. And you didnt see this coming from that crew? by nurb432 · · Score: 1

    With their general history, im suprised they just didnt go for *bsd and make it 100% commercial.. they still may before its all over..

    Much like lindows is doing as a side note..

    --
    ---- Booth was a patriot ----
  42. GPL and commercial stuff like drivers... by __aawavt7683 · · Score: 1

    This really annoys me. You people bitch and bitch about GPL violations... "You use this library and didn't GPL your code!" Heh... I understand that it's worth it much of the time, such as when they're putting out distributions, but this kills much of the potential of people and corporations doing things for linux.

    Such an example would be drivers... companies don't wanna give out drivers because it'll give away their secrets an such. Just let them violate the GPL on such things.. everyone wins. Linux people get to stop bitching about lack of drivers for the product, the company can sell more of the product since it's supported on yet another OS. Sure, it may be some what unstable since the community can't review it, but at least it'll be in existance. Heh..

    Personally, if there was something I would make but didn't wanna give the source out to, I'd make it and release it binary only. If I got bitched at for not providing source, just remove it completely, hurting all the people who're using it.

    -DrkShadow

    1. Re:GPL and commercial stuff like drivers... by jbn-o · · Score: 1
      Just let them violate the GPL on such things.. everyone wins.

      No, the community certainly does not win. The GNU project and Free Software were based on spreading the freedoms to share and modify software because these freedoms help make our world a better place. It sounds like you aren't familiar with why the GNU project was started.

      Linux people get to stop bitching about lack of drivers for the product [...] Sure, it may be some what unstable since the community can't review it, but at least it'll be in existance.

      Free Software advocates are not after mere popularity. Stability is one of the practical benefits one gains as a result of having the freedoms of Free Software.

      Personally, if there was something I would make but didn't wanna give the source out to, I'd make it and release it binary only. If I got bitched at for not providing source, just remove it completely, hurting all the people who're using it.

      So long as your program is not a derivative of copylefted Free Software, you might be able to legally do that (one would need more information about your program to be sure). You would be unwise to forgo all the trust you might have gained in the community, but that's your choice. Your dismissal of software freedom is remarkably short-sighted: this would hurt you too because someone who receives a copy of Free Software might help you develop the program, improving it in ways you never imagined. Distributing proprietary software cuts off the possibility of building a community of equals and encourages people to think poorly of you. After releasing GPL-covered software I'm pleasantly surprised at how inventive the community is and how much I benefit from their collective wisdom.

    2. Re:GPL and commercial stuff like drivers... by Anonymous Coward · · Score: 0

      Well considering that all that bravado over the last 10 years has specifically made Linux the loser that it is today. I'd say that maybe you aught to think seriously about the other guys opinion...

    3. Re:GPL and commercial stuff like drivers... by Anonymous Coward · · Score: 0

      Yeah, I see now. The hardware makers don't release the specs for their hardware so that... uh... people that have the time and knowledge won't write drivers for it for free!!! Yeah, getting that piece of hardware working under another operating system, thus increasing potential user base and sales, at *no cost*, sure is a bad thing. Wait, what? That doesn't make sense...

      Plus there is absolutely *NO RELEVANT INFORMATION* that could be obtained about the "secrets" of how a piece of hardware works. All info would either already be known, easily obtained otherwise, or just completely useless to anyone who would want to make a competing product from the information. Not to mention the fact that most if not all of the secrets are covered by patents.

    4. Re:GPL and commercial stuff like drivers... by Anonymous Coward · · Score: 0

      Ah! You must be one of those dolts that thinks Linux is all about 'taking down Microsoft'!

      That explains a lot. Sadly, what it doesn't explain is your total lack of understanding anything at all about Linux.

      Drivers? nVidia releases Linux drivers quite often, without source, and they fail to violate the GPL.

      Though I'm sure Stallman would if he could, no one holds a gun to anyone's head and forces them to use the GPL for their Linux-based software.

    5. Re:GPL and commercial stuff like drivers... by Anonymous Coward · · Score: 0

      Yeazh, ,and they'd be re'd and then you'd be left profitless by smarter people than you, with your worthless attitude, fascist mentality and caustic commentaries.
      But, shit..you're already there aren't you?

  43. Or just the accusation by ACNeal · · Score: 4, Insightful

    Why have proof or anything like that.

    If they haven't modified anything GPL, then they CAN'T violate the GPL.

    If the basis of the distro is security and configuration scripts slapped around the outside of the normal kernel, then there is nothing to fear.

    And since this was my understanding of what the distro was supposed to be, they can't be violating the GPL. If they give you a piece of GPL'ed software, they can't keep you from distributing it.

    They can keep you, with an NDA from distributing their distribution, with all the proprietary products slapped around it. They can keep you from spilling the beans as to exactly what little tools they have produced.

    This is not to say they havn't, but the simple fact of an NDA and a closed beta doesn't even begin to smell of a GPL violation when you take into account what you already know of the companies involved, and what they have already stated their goals to be.

    But lets accuse 'em anyway, just cause we already hate 'em. We can always apologize later, and claim absence of malice.

  44. Demonstration of priorities by Neumann · · Score: 1

    Its kind of funny that the largest thread on the discussion board is the proper pronunciation of Linux.

  45. This is a pre-beta so, by ebuck · · Score: 2, Insightful


    Since this is a pre-beta, can the software be considered released?

    If you can consider it released, clearly they are in the wrong, but if the company wants some extra eyes to overlook their bug-laden code, what do they do?

    Can they not release it, yet distribute it to developers they can trust as to not spill the beans to their competition?

    What sort of arrangement must be made to be considered an "inside" developer?

    Perhaps I'm simply not ready to burn UL since I haven't heard any FSF / GNU statements demonizing this action.

    The intro to the article sets the tone for big business bashing, and the allusions to removed executives and emphasis on mis-pronunciation only create a literary atmosphere of distrust.

    Which brings me to my only useful question. Why are we reporting about a "May be" on NewsForge? If we can get a "They violated X" that's real news!

    1. Re:This is a pre-beta so, by josh+crawley · · Score: 1

      Heh... if read correctly, that's a funny joke. Let me explain.

      OMG!! SCO just violated X!! They took startx and bent it over the /etc/table and gave it hard into the bash. And how dare they! X is only 17 years old!

  46. Goddamn by Anonymous Coward · · Score: 0

    +5 Informative since the /bots can't see their own behavior even when it smacks them in the face

  47. So specifically, how did they violate the GPL? by ComputerSlicer23 · · Score: 1
    Presuming they let you send out source packages, which I thought they announced we're on a public FTP server, how'd they violate the terms? Hmmm, I don't see them on a public server so maybe I'm wrong on that one... So if they don't let you send out the source code that's an obvious GPL violation. However, if they dictate that you can't send out the Binaries they PGP signed, is that a GPL violation? I don't believe so, the sources are GPL'ed, the binaries aren't. If you recompile the binaries and distribute them, there isn't much anyone can do to stop you.

    They won't let you post an ISO, that's just the same as the OpenBSD guys copyrighting it, rather then putting it out under the BSD license...

    It's just like RedHat saying you can't redistribute a RedHat ISO as a RedHat CD. That's not a GPL violation, you are violating their trademark.

    The only way they it can be a GPL violation is they don't let you send out the source code to anybody you want to. That's the only piece the GPL applied to. If the NDA says you can't send either the ISO's or the binaries, they are in the clear to the best of my IANAL knowledge.

    Kirby

  48. jews all overwhere by Anonymous Coward · · Score: 0

    JEWNITED JEWNUX

  49. random loveless by Anonymous Coward · · Score: 0

    did n't random comment on slashdot at one point that the GPL was restrictive that he was hoping to move the verison to mpl? or something along those lines.

  50. Research before you speak by Anonymous Coward · · Score: 4, Interesting

    OK, the usual crowd of ininformed slashdotters has spoken. Let's get some facts in here, and raise the clue level:
    1) I an a UnixWare developer. Obviously, we're not all laid off, but some of our good friends and coworkers were tossed out
    2) Please indicate, concretely, where UL violates the GPL
    3) Newsforge is the only FUD-distributor that uses extortion to get details: "tell, or we'll print misinformation". Really, people. With the same intensitity that you mistrust anything but the One Pure (RedHat|Debian), verify your other sources
    4) Ransom never put down hte GPL; he said it was great for development but had no business case
    5) SCO-formerly-Caldera was formerly SCO, and is well-known in the retail industry. Again, check your facts, and check under the hood of the places you're buying your junk food and brand-label-knockoffs. We just don't advertise. With the hatred of popups, you'd think this was a good thing in this community
    6) for the record, I call it "Linux", not "FNU/Linux" nor "GNU/Apache/X/Linux", since, although all these tools and more are part of Linux, Linux is Linux is Linux. Thanks for the work thus far in what you have contributed to LINUX.

    Of course you're going to frag my comments, go ahead. You might want to include some factual arguments.

    The non-factual FUD shouting here is only one step above "woo hoo! first post!"

    1. Re:Research before you speak by fault0 · · Score: 1, Flamebait

      > for the record, I call it "Linux", not "FNU/Linux" nor "GNU/Apache/X/Linux", since, although all these tools and more are part of Linux, Linux is Linux is Linux. Thanks for the work thus far in what you have contributed to LINUX.

      Exactly, if Linus himself doesn't care about this, why should users?

    2. Re:Research before you speak by swv3752 · · Score: 2, Informative

      I'd have modded you down but you are already +5 so...

      Ransom love is the one Linux CEO (or former CEO) that defended Micrsofts FUD attacks on the GPL. He has routinely put down the GPL.

      While I could flog you for your poor grammar and spelling, I am not one to go throwing stones.

      Newsforge like many other "Wathcdog publications" uses whatever pressure they have to get at the "Truth". This what true journalism is about. If someone is hiding something you call them on it. Maybe UnitedLinux has done nothing wrong, but like gary Condit and OJ Simpson, I doubt it.

      About SCO, SCO was bought by Caldera, formerly a part of Novell. So, Caldera absorbed SCO, but was never formerly SCO. And yes, SCO is well known, but many do not have fond meories of it. It ranks right there with HP-UX. It might work well but admining it is a bear.

      It is GNU/Linux, though I sometimes abbreviate it to just Linux.

      Once a troll reaches +5 you do have to respond.

      --
      Just a Tuna in the Sea of Life
    3. Re:Research before you speak by Anonymous Coward · · Score: 0

      Congrats, you've made the first intelligent SlashDot post in... years maybe.

    4. Re:Research before you speak by Anonymous Coward · · Score: 0

      Do you know what a site called 'NewsForge' makes the man on the street think of?

      Forged News. In case you're wondering, that would also mean 'made up shit.'

      I can't believe that somebody thought 'NewsForge' was a good name for a news site that would have any credibility at all.

    5. Re:Research before you speak by mandolin · · Score: 1
      "Wathcdog publications" ... "but many do not have fond meories of it" ... While I could flog you for your poor grammar and spelling, I am not one to go throwing stones.

      Yeah, your glass house is thanking you right now.

      On-topic, I'll personally wait to see the NDA; for all we know it only forbids redistribution of their bundled proprietary programs. And maybe not even that.

    6. Re:Research before you speak by Gooba42 · · Score: 1

      It "is" GNU/Linux? According to what authority?

      Unless it is actually a brand name, trademark or copyright then there is no governing entity that gets to tell me how to refer to the product. In this case I use Mandrake Linux, an assembly of GPL software including portions of the GNU project.

      If I was asked, I would say that I use a Linux system and if it would mean anything to the person asking maybe mention the GNU tools. GNU/Linux is a nonexistant entity invented for the purposes of trolling Slashdot for all I'm concerned. When the FSF makes a distro, then I'll say GNU/Linux.

      --
      I just found out there's no such thing as the real world. It's just a lie you've got to rise above. - John Mayer
    7. Re:Research before you speak by Anonymous Coward · · Score: 0

      Dude , but GNU Hurd was so almost ready for prime time...

    8. Re:Research before you speak by Jungle+guy · · Score: 1

      Actualy, I refer to Gnu/Linux only when I am talking about Debian. They want their distribution to be named this way...

  51. now it's startigg to make sense by Anonymous Coward · · Score: 0
    Dese four companies had two proglems:
    1. RedHat's market dominass 'n
    2. customee avershun to peh-seat licensing, which is needid f' a sustainable bidness model. Uhhh....
    3. By pooligg deir distros and bundling in some non-GPL soffware, dey can tell customehs "licenses are per seat, dat's the way it is, take or it lee it", GEEEHEEHEEE. Of cusse, uh uh uh, many will lee it and opt f' RH instead. Uhhh.... But maybe dey're betting dat RH will run into financial problems of its own (it dgust reportid anoder loss) 'n will be f'cid to take a similar tack. In de meantime, uh uh uh, dey can still claim deir licenses are cheap relatibe to Winblows and de propriet *NIX vendors.
  52. linux is imploding by Anonymous Coward · · Score: 0

    The signs are everywhere: linux is dying. All the linux distros are going out of business. The kernel still doesn't have a stable VM and robust filesystem, even after years of lying about how stable it is and how ext2fs is safe. All the developers and users are wising up and switching to FreeBSD. Now not even GPL is sacred.

  53. Am I missing something... by Rufty · · Score: 1

    So it's under an NDA and includes GPL'ed stuff. And stuff that's unique to United Linux. The GPL'ed stuff is still as GPL'ed as ever, and the beta-testers can take that and it's as free as before. It's just the bits that are United Linux specific that are currently NDA'd. Whether this is software or just the arrangement of GPL'd stuff, well I dunno. (Can you copyright an arrangement of purely GPL'd code???????)

    --
    Red to red, black to black. Switch it on, but stand well back.
  54. Copyright holder(s), possibly a class action suit. by Kjella · · Score: 2

    IANAL, not even american so take my understanding of US law with a ton of salt, but it sounds like there'd be grounds for a class action suit, the class being all the copyright contributors to the infringed code. If you don't care about the personal benefit you might recieve, I suppose you could give the copyright to FSF or something similar to let them do the job, but they might be willing to take your case on your behalf (as long as you're defending free software) anyway...

    Kjella

    --
    Live today, because you never know what tomorrow brings
  55. Maybe you should read it once more? by Subcarrier · · Score: 3, Informative

    I've read the GPL a couple times, and have never gotten the perception that it prevented a company from preserving its right to sell a product and not offer Joe Q. Hacker full rights to recompile the source.

    If a company reuses GPLed software written by others, there is no such right in the first place, so it cannot be preserved. The GPL is very clear on this:

    "To protect your rights, we need to make restrictions that forbid anyone to deny you these rights or to ask you to surrender the rights.
    These restrictions translate to certain responsibilities for you if you distribute copies of the software, or if you modify it.

    For example, if you distribute copies of such a program, whether gratis or for a fee, you must give the recipients all the rights that you have. You must make sure that they, too, receive or can get the source code. And you must show them these terms so they know their rights."

    --
    "I have opinions of my own, strong opinions, but I don't always agree with them." -- George H. W. Bush
  56. Re:Why UnitedLinux is---- YAST by Anonymous Coward · · Score: 0

    YAST the knights that say YAST. If there is one word that seems to piss off debian users more than anything its YAST. Source code for YAST is on the cds.

  57. Misunderstandings... by Anonymous Coward · · Score: 0
    My god, I was at the conference call and am amazed by the number of misunderstandings. UL is releasing the beta to selected partners, and is going to provide the sources to them. The NDA is to make sure these parties don't leak the software to other companies.

    The real sad thing is that UL will use Yast (a closed software) as the instalation tool. In the long term, it might hurt their costumers that would think they have a free software OS. The same problem of SuSE, and the reason why RMS loathes them.

  58. What does the GPL have to do with an NDA? by Anonymous Coward · · Score: 0

    As near as I've been told, if I make GPL software, and I sell it to someone, only the people who buy the software from me are entitled to the source code, right? Just because I work hard to make something to sell doesn't mean I'm forced to give it away to clueless retards who whine "GPL GPL GPL!!!!" and stamp their foot.

  59. I don't get it. by ElGuapoGolf · · Score: 1

    How is this really any different from joe schmoe creating his own distro and passing it off to a few friends to test out before he announces it to the public. Answer: It's on a larger scale, and it isn't. Seriously... it's a freakin beta folks. They want to test it, and I'm sure they have a ton of beta testers with specific hardware and setups that they need. Sure, releasing it to the general computing public may be better, but they're probably not ready for that yet. So I'd back off and wait. And second... stop bashing SUSE folks. The source for their installer is available. You can use it. People like it. People use it. It isn't the largest distro in europe without reason. So uh, there.

  60. Comment removed by account_deleted · · Score: 1

    Comment removed based on user account deletion

  61. How many of you have actually READ the GPL? by Anonymous Coward · · Score: 1, Insightful

    I am not a lawyer, so what follows is 100% fictional, and bears no resemblence to anything:

    A lot of people seem to think that if you edit a GPLed program, you have to give away the source code. WRONG!

    You do not have to give it away at all, but if you distribute a binary you must make the source code available to everybody that you make the binary available to.

    So, say I edit a GPLed program, and give a copy of the source code to my friend. Now, say you ask me for a copy, the GPL says I have to give you a copy, right?

    WRONG! It says no such thing.

    So, you ask my friend for a copy, he has to give you a copy, right?

    WRONG! If we both want to, we don't have to give a copy to anybody else.

    However, what I am not permitted to do under the GPL, is to prevent my friend from giving a copy to you, or to then prevent you from further distributing it.

    1. Re:How many of you have actually READ the GPL? by coolfrood · · Score: 3, Insightful

      That is precisely what the NDA says. When they give you a software with the associated NDA, they are telling you to NOT give out the source code. If the software is GPL, you cannot force someone to not distribute it if he wishes to.

  62. SCO? Point? never the twain shall meet by fanatic · · Score: 2

    You'd think that the likes of Suse, Turbo, SCO, and Conectiva would get the point by now...

    The others, maybe, but SCO is probably hopeless. They're also the ones who introduced per-seat licensing. Also, the fact that, given a chance to choose the Caldera name or the SCO name, they went with SCO, was a very bad sign.

    I thought that UnitedLinux was an interesting concept until I saw SCO was involved - my interest level went way down at that point.

    --
    "that's not encryption - it's a new perl script that I'm working on..." - from some Matrix parody
  63. Re:Why UnitedLinux is doomed (now OT) by robson · · Score: 2

    ...but nowadays the only such project they have left is ReiserFS and that is so unstable that even Gentoo (!) recommends against its use.

    Is it generally accepted that there are problems with ReiserFS? I don't *think* I've had any problems with it...

  64. NDA parts vs GPL's parts by Sabalon · · Score: 2

    So...what actually could fall under the NDA that is not GPLed?

    File locations? Config files? Any code that UL has added on.

    So what if the beta people get gcc, the kernel and bash and redistribute that or get the source code - probably the same from the gnu site.

    Nothing lost to UL. But one should not assume that EVERYTHING on the system is GPL'ed. Perhaps UL has written some uber-cool init scripts that aren't GPL'ed.

    It doesn't sound like UL is even giving them that much leeway though, but it does make for an easy out for UL.

  65. It depends on the nature of NDA ... by bockman · · Score: 3, Insightful
    if the NDA force them not to distribute some GPLed software, then it is a violation.

    If the NDA is only related to some proprietary add-on software (like SuSE Yast2), or more generally to the way in which the distribution is assembled, it is not (IMO) a violation. It may be a stupid move, but not illegal.

    This is, I think, why FSF asked UL to disclose the terms of the NDA.

    --
    Ciao

    ----

    FB

  66. A Question about the GPL by gamorck · · Score: 2

    Can anybody here tell me what the difference is between the GPL and a EULA? It seems to me that both are very similar. In fact I find it somewhat amusing how people on /. claim EULAs are null and void yet do not realize that if EULAs are null and void that most likely means that the GPL license distributed with an OpenSource app is likely null and void.

    1) You download app and uncompress
    2) The app has an agreement which nobody ever reads (at least the EULA makes you click through it)

    Really what is the difference between the two? It seems to me that they are one and the same. This of course means that neither will stand up in a court of law. AFAIK the GPL has never actually been tested in court, since I believe all cases involving GPL violations have been settled out of court. Can anybody provide any examples of the GPL and/or EULAs being tested and determined to be legally binding in a court of law?

    J

    --
    I love idealists not because I am one, but because they make life bearable for pragmatists such as myself.
    1. Re:A Question about the GPL by vadim_t · · Score: 1

      That it's not an EULA. EULA stands for "end user license agreement". The GPL doesn't require an user to do anything at all. You can download a GPLd program and use it without agreeing to anything. However, unless you agree to the GPL you
      can't redistribute the program due to the copyright law.

      EULAs impose restrictions on you that aren't present in copyright law, GPL gives you additional freedom if you agree to it.

    2. Re:A Question about the GPL by spitzak · · Score: 2
      As people have tried to explain about 6000 times here, the difference is that the EULA tries to reduce the rights you have by default under law.

      The GPL tries to add to those rights. If you don't agree to the GPL you can do less with the code than you could do if you did agree to it (basically you can't redistribute it at all because that violates US and many other countries copyright laws). So you have no incentive to not agree with the GPL.

      If you disobey the EULA (while still not violating copyright or other laws) you are ok if EULA's are unenforcable, but in legal trouble if they are not. But it is not possible to disobey the GPL without also breaking copyright laws, so you are in legal trouble anyway, whatever the legal status of the GPL is.

    3. Re:A Question about the GPL by Anonymous Coward · · Score: 0

      Not only has it been answered six thousand times before, but the question is asked by the same five people over and over again.

  67. Comment removed by account_deleted · · Score: 1

    Comment removed based on user account deletion

  68. Comment removed by account_deleted · · Score: 5, Informative

    Comment removed based on user account deletion

  69. It's about the MONEY$$$$$ by Anonymous Coward · · Score: 0

    Seeing that companies such as Turbo, SUSE, SCO, and Connectiva, have decided to focus on Enterprise only, their target market would be more than happy to purchase United Linux vs Mandrake since it has support, its closed, and non gpled which means the software maker will get its fair share of revenue....

  70. Comment removed by account_deleted · · Score: 1

    Comment removed based on user account deletion

  71. defending a GPL by chongo · · Score: 3, Insightful
    but exactly who is going to prosecute them?

    As the first person who ever took legal action against somebody who wanted to violate a GPL (back in 1989) I can definitively say: The GPL Copyright holder is the one who has standing to seek legal action against the party they suspect is violating the GPL.

    I.e., somewhere in your GPL / LGPL there is a:

    Copyright (C) date name

    The name, or somebody to who they have signed over the copyright to, is the one who has standing to bring suit against a potential violator.

    --
    chongo (was here) /\oo/\
  72. this isn't the generally accepted position by Trepidity · · Score: 3, Insightful

    Corporations are legal entities, so distributing within a corporation is "private use", which the GPL explicitly exempts, since all the various copies of the code within the company are all licensed to the company, not the individual employees. I don't believe the FSF disagrees with this interpretation.

    What's at issue here is whether distributing a beta to non-employees under NDA can count as private use, which it probably can't.

  73. depends what you mean by freedom by Trepidity · · Score: 2

    If you take the FSF's definition of freedom as applied to software -- the ability to relatively easily modify a program through access to the original source code (and a license that permits you to make such modifications and distribute them), then your analysis is correct. If you take a more libertarian view of softare freedom -- the ability to do whatever the hell you want to the software -- then requiring one to distribute source code when one prefers not to is actually restricting freedom.

    1. Re:depends what you mean by freedom by Chris+Burke · · Score: 2

      I don't think you accurately represent Libertarian thinking on the subject.

      If you did, that would suggest that it being illegal for you to make me your slave is a bad restriction of your freedom, from a Libertarian point of view.

      Live human libertarians I know don't think that way.

      Thus I doubt what you say.

      --

      The enemies of Democracy are
    2. Re:depends what you mean by freedom by Mr.+Slippery · · Score: 2, Insightful
      If you take a more libertarian view of softare freedom -- the ability to do whatever the hell you want to the software -- then requiring one to distribute source code when one prefers not to is actually restricting freedom.

      When compared against a situation where everyone has the right to "do whatever the hell you want to the software", perhaps. But that's not the case under current copyright law. Under current conditions, the GPL adds to your freedom - without it, nothing permits you to distribute the software at all.

      If copyright law went away and we could copy and distribute binaries willy-nilly, there's be no reason not to make source available, and market forces would make open source the norm. But given the interference of copyright applied to software, the GPL is a freedom-enhancer.

      --
      Tom Swiss | the infamous tms | my blog
      You cannot wash away blood with blood
    3. Re:depends what you mean by freedom by ClosedSource · · Score: 1

      " But given the interference of copyright applied to software, the GPL is a freedom-enhancer."

      No. Software that is copyright free(which has always been available) has no restrictions on it. GPL'd software has restrictions on it. So the GPL may enhance freedom in the sense that it requires any changes to be distributed, but it diminishes freedom relative to uncopyrighted software for the orginal work.

      In addition, changes made to uncopyrighted software might also be distributed in the public domain thus derivative works could also be more less restrictive than GPL derived works.

      To conclude that the GPL is really a freedom-enhancer you have to assume specific behavior on the part of those who receive software distributions. Since, in general, this cannot be determined in advance, you can't prove it.

    4. Re:depends what you mean by freedom by Gooba42 · · Score: 1

      Does the author's freedom to choose how his product is used to steal his recognition or profit enter into it?

      Under an unlicensed, uncopyrighted scheme he has no reason to distribute the product at all except for pure altruism as he can expect no participation, recognition or profit from his work whatsoever. Under the GPL at least recognition is given and in many cases is considered plenty of payment for services rendered.

      Moreover, the license holds on an international level whereas US "public" domain does not. Public domain means that it belongs to the US citizens at large. The GPL provides an area that isn't public domain and is also not proprietary.

      The bottom line is that you can choose a different license. UL has the freedom not to comply with the GPL so long as they choose not to use software for which the author practiced. Restrictive or not, they must comply with the license of their choosing.

      --
      I just found out there's no such thing as the real world. It's just a lie you've got to rise above. - John Mayer
  74. a bit of further analysis by Trepidity · · Score: 2

    Upon some further thought, I'd consider the FSF's position on software freedom a kind of utilitarian compromise position. For the individual, being able to do whatever one wants with software -- modifying it, distributing it with source code, distributing it without source code, etc. -- is the highest level of freedom. However, permitting this can potentially restrict the freedom of others, as if this individual exercises his freedom to distribute modified binaries without source code, he makes it much more difficult for others to exercise their freedom to modify the code (in the absence of legal restraints they can still do so, by disassembling the binary for example, but it makes it significantly more difficult). Thus the individual's freedom is limited by requiring that he distribute source code whenever he distributes a modified binary in order to make it significantly easier for the everyone else to exercise their freedoms. All things considered, I see this as a relatively good trade-off.

    1. Re:a bit of further analysis by Chris+Burke · · Score: 2

      Ah, now you've got it.

      We each give up a little freedom to ensure that everyone has as much as possible.

      If you only consider the recipient of the GPL code and what he can do, the GPL seems less free. If you consider the recipients of the code the first recipient produces (based off the GPL code received), then the GPL guarantees -more- freedom.

      I take issue with those who consider only the freedom of the first recipient -- who is presumeably themselves -- because it seems they would be happy to be dictators (who can, after all, do whatever they want).

      --

      The enemies of Democracy are
  75. Comment removed by account_deleted · · Score: 1

    Comment removed based on user account deletion

  76. But what is it they want to protect with an NDA? by rsilvergun · · Score: 1

    I'm a little confused about why they'd need an NDA at all. I can see a closed beta (it's probably a hassle dealing with the user community that pop's up around open betas), but given how simular most linux distros turn out after the install, what's it matter if their testers talk about it? What's could possibly be in there that they don't want disclosed untill after the beta?

    --
    Hi! I make Firefox Plug-ins. Check 'em out @ https://addons.mozilla.org/en-US/firefox/addon/youtube-mp3-podcaster/
  77. it's probably OK from a GPL point of view by g4dget · · Score: 2
    They can ask anybody to sign a non-disclosure agreement as long as they still give the sources of GPL'ed programs to people who ask and allow them to redistribute those. The GPL is only about ensuring obtaining and redistributing source.

    So, they are probably not violating the GPL by having a non-disclosure agreement or not permitting redistribution of the entire distribution. And their installers can check for the presence of non-GPL'ed software and refuse to install. The GPL does not guarantee that entire distributions are redistributable in binary format. All they need to do is provide sources to GPL'ed programs on request, and only to people they distributed the binaries to, who then have the right (but not necessarily inclination) to redistribute those sources further.

    Whether that's a good thing or not I can't say. I think a user would not be very smart to start relying on such a company for their Linux distribution, since there are so many better alternatives out there.

  78. I'm glad none of you serve on juries... by erat · · Score: 4, Insightful

    Without seeing UL, without seeing the NDA, without having any evidence whatsoever other than the dent in your chin from your knee jerking upward unexpectedly, most of you already seem to have tried and convicted the UL folks for GPL violations.

    Tell me, what are you going to do if the UL closed beta NDA stated that only the proprietary components of UL are not distributable but the open sourced and GPL'd components are? Pull the usual trick: sit back and pretend you never said anything, then wait a month and start bashing UL as Satan's distro again?

    That's just plain creepy... You let your senseless rage get in the way of reason. You probably don't even know why you hate UL so much other than the fact that you simply WANT to hate it.

    If the UL team violated the GPL, fry 'em. Until I see damning evidence, though, they're innocent until proven guilty.

  79. Here's the way I see it. by shren · · Score: 3, Insightful
    United Linux has a GPL piece of software. United Linux offers you that GPLed piece of software. You accept. United Linux says, "Wait. If we give this to you, you can't give it to anybody else." You sign the NDA and accept the copy of United Linux.

    The GPL just says that if you do give it away, then you must give the source too. I don't see anything in the GPL saying that you can't forbid redistribution - it just governs what you must do if you distribute.

    If UL gives you the software with source and binaries, then they have obeyed the GPL. If you sign the NDA, you waive your redistribution rights.

    If you gave out the source after signing the NDA, you're breaking the NDA. If you give out the binaries alone after signing the NDA, you're breaking the NDA and the GPL at the same time.

    Unless I'm reading the GPL wrong, you could GPL photoshop and sell customers both the source and the binaries, then require that they not redistribute the source. If you waive your distribution rights, then it doesn't matter if it's GPLed or not - you're forbidden to redistribute it.

    It'd be interesting to see a license that combined aspects of the GPL - in that you must distribute the source - and some kind of micropayment screme, where your software or any software based on it requires n cents per day to run. Like, you can give it away all you want, but you can't use it without paying all of the authors of the software.

    I write, say, a graphics library, and license it under this model. I give out the code of my graphics library, and in addition my graphic library requires a payment of one cent per day, which is managed by a central micropayment program running on each machine.

    You can base code off of my library. You can charge a cent per day for your new version of the library. However, you can't take away my cent. Alternatively, you can write code and not charge anything - but I'll still get my cent, as you accept my license when using the code which says I get a cent.

    That variant would be interesting. The source is open and free, but running the source costs money. Developers would be paid, but you'd get the advantages of seeing the inside and even the ability to redistribute different versions.

    I'm sure the open-source commies are ready to cruicify me, but you could have a lot of pull to get people who sell software to open thier source under this model. They'd be releasing open code and making money at the same time. It's no more or less circumventable than normal software distribution, but it has open code.

    --
    Maybe the state's highest function is to grind out insoluble problems. (Zelazny, Hall of Mirrors)
    1. Re:Here's the way I see it. by Anonymous Coward · · Score: 0
      6. Each time you redistribute the Program (or any work based on the Program), the recipient automatically receives a license from the original licensor to copy, distribute or modify the Program subject to these terms and conditions. You may not impose any further restrictions on the recipients' exercise of the rights granted herein. [...]

      This section is half of the purpose of the GPL, and UL would have had to word their NDA pretty carefully to comply with it.

    2. Re:Here's the way I see it. by RealAlaskan · · Score: 2, Insightful
      I don't see anything in the GPL saying that you can't forbid redistribution ...

      I do. Look here:

      6. Each time you redistribute the Program (or any work based on the Program), the recipient automatically receives a license from the original licensor to copy, distribute or modify the Program subject to these terms and conditions. You may not impose any further restrictions on the recipients' exercise of the rights granted herein. You are not responsible for enforcing compliance by third parties to this License.
      What part of that is hard to understand? You have no right redistribute GPLed software unless you accept, and abide by, the GPL:
      5. You are not required to accept this License, since you have not signed it. However, nothing else grants you permission to modify or distribute the Program or its derivative works. These actions are prohibited by law if you do not accept this License. Therefore, by modifying or distributing the Program (or any work based on the Program), you indicate your acceptance of this License to do so, and all its terms and conditions for copying, distributing or modifying the Program or works based on it.
      If UL gives you the software with source and binaries, then they have obeyed the GPL. If you sign the NDA, you waive your redistribution rights.

      If UL requires you to sign the NDA, they are violating the GPL, and have no right to redistribute. You, on the other hand, do have the right to redistribute the GPLed code they gave you:

      4. You may not copy, modify, sublicense, or distribute the Program except as expressly provided under this License. Any attempt otherwise to copy, modify, sublicense or distribute the Program is void, and will automatically terminate your rights under this License. However, parties who have received copies, or rights, from you under this License will not have their licenses terminated so long as such parties remain in full compliance.
      Unless I'm reading the GPL wrong, ...

      You are.

  80. My two cents by Anonymous Coward · · Score: 0

    United Linux, except for Suse, is composed of a bunch of companies that have been producing those Linux distributions - you know, the distributions that no one ever uses and attempts direly to steer potential Linux users away from. There is a post by Walter Bell somewhere up above (labeled a "troll" simply because he has an opinion - funny how you hopeless computer nerds can never take an ounce of criticism) that I agree largely with. Each of these distributions have been largely neglected for being bad, and some of the companies that produce them have obviously not had the best interests of the community in mind.

    There are rather simple and obvious reasons why UL will likely fail (though it is in no way certain). If you analyze the new organization as a whole, that is consider the quality of all of the distributions and companies involved, then you could imagine that the finished product of their labor will not be very tempting - certaingly not tempting enough to persuade people to pay for it, not when they can obtain the same level (if not far better) of craftsmanship from Redhat or Mandrake. Also stepping into the game are large market players like IBM and Sun. IBM and Sun have a different motive then UL, true, but they intend to use their muscle to push either their own solutions or Redhat (in IBM's case). The ability to get Redhat with an underlying cussion of support by IBM is far more tempting then the possibility of having a video card driver standard with UL.

    Again, I don't mean to troll, just wanna point out the obivous.

    - Tai

    1. Re:My two cents by Anonymous Coward · · Score: 0

      you hit the nail on the head my friend

  81. I know Paula Hunter by Anonymous Coward · · Score: 0

    Paula does many things well, but she is not "technical" (whatever that means). It's a little surprising to me that she would be considered / would take a position of this type where the community culture is based on technical meritocracy. As far as I know, she has not had any direct professional affiliation with Free / Open Source software in the last 4-5 years.

  82. linux is too commercialized by Anonymous Coward · · Score: 0

    This is the problem with linux today and for a long time now --- everyone's trying to make a buck off it. It's way too commercialized. For pure hacking fun, more and more programmers are switching to FreeBSD.

  83. So what if they are by Anonymous Coward · · Score: 0

    Whats the worse that could happen? All of us free software developers will unite and hire lawyers to sue the pants off of this company? With what? all that money we make off the GPL.

  84. The Real Question by Quixadhal · · Score: 3, Insightful

    Ok, let's see. "United" Linux wants to make a single unified base for linux distributions, what once upon a time was called a "standard". Good for them!

    Since too many people have different ideas about what the "right" way is, and many of them have the technical ability to say "Fine! I'll go build my own linux distro, with blackjack, and hookers!"... they decided to make a corporate entity and just say "I am the law!" instead of continuing to argue with everyone else. Ummm, ok.

    Now, they decide that all that GPL stuff, which each of the members has -- at one time or another -- spoken lots of pretty poetic phrases of support, and did much clapping of hands for... is not really as important as making their new business model/standards base work. Sooo, they ignore the SPIRIT of the GPL, even if they might or might not be violating the letter of the law. Ewwwww.

    Let me ask this question of the United Linux folks... what are you afraid of? The traditional reason people DON'T embrace the GPL is fear that if their code (and thus algorithms) became public knowledge, others might do it better than they have, and thus steal away their market share. The assumption there is that service means nothing, and that the original developers would rather sit back and drink beer than continue to advance and evolve their product.

    Why should I buy into the "United Linux" front? What do they do for me? It sounds to me like they want to be RedHat, but NONE of them individually have the talent, ability, or balls to make a better Redhat than RedHat. Don't get me wrong, I don't like RedHat... I actually like SuSE -- but that's why I don't want UL. I don't want SuSE, SCO, and all the others to become the next RedHat. We don't need it. We need cooperation, not more "our way or the highway" attitude.

    Grow up people. If you don't like the GPL, then go rewrite things for yourself and call it something other than linux... call it ulix, call it moneyix, but play nice or go away.

    1. Re:The Real Question by kuiken · · Score: 1

      Did your read The NDA ? if so did it say you could not distibute the GPL'ed pieces of the distro ? if it didnt they did not break the GPL

      And further more since this is a CLOSED beta, they consider consider the ppl who got the distro agents of the company/organisation so no distribution has taken place so the GPL does not mater

      And about the spirit, its a CLOSED beta not a PUBLIC, like the P in GPL. And so far it also looks like they just want a limited tesing cycle, maybe they should have called it Final Alpha
      , and nobody would have minded the NDA

      This whole discusion is just hiar spliting, specultain and semanthics

      --

      42
  85. There are greater ideals than the GPL by JamesGreenhalgh · · Score: 1

    I'll probably get modded as a troll for this, but:

    Despite this being currently of questionable factual quality - IF the make a slight infringement of the GPL, but their product takes off and starts to help linux in general against the Microsoft monopoly, perhaps that is a greater goal.

    If someone said to me that if United Linux would have to break the GPL in some way, but their actions would result in say a 20% desktop share by the end of next year, I would say thats a worthwhile sacrifice.

    There's a greater issue here folks, and it affects computing as a whole, not just open source software. Microsoft need to have a competitor or we're all fucked.

    --

    --
    ALL YOUR BASE ARE BELONG TO US!
    1. Re:There are greater ideals than the GPL by Anonymous Coward · · Score: 0

      Without open source, we'll be just as fucked by Microsoft's successors.

      Since UL claim they're going to ship source, they certainly don't have to violate the GPL to succeed.

  86. Well, this should put Red Hat in some perspective by GauteL · · Score: 1

    I'm not trying to say that Red Hat is better than any other Linux-company, I'm just trying to put down the baseless whining about Red Hat being evil.

    AFAIK, Red Hat has never distributed software outside the company without releasing source at the same time.

    Red Hat is still among the most dedicated followers of the GPL-license. All their tools are free software.

    Why are Red Hat still up there then, if all their software can be easily poached by others?

    1. Brand
    2. Good quality and good professionalism. Not necessarily better than anyone else, but certainly much more professional than most others.
    3. Playing nice. Lots of people call fowl about anything Red Hat does, but hardly anything is much more than childish outcries.

    You can bash Red Hat for some of the technical decisions they have made, but they have done nothing at all to deserve a reputation as "evil".

    In fact.. UnitedLinux are trying to compete with the market leader by being more closed. At least Mandrake got that right and was sensible enough not to join this initiative.

  87. er, not obvious at all by DrSkwid · · Score: 2

    There's these little legal loopholes, you see, called evidence, burden of proof and innocent until proven guilty. You may of heard them on Matlock.

    Your statement is akin to "they lock their door, they are obviously up to no good".

    [ianal]
    The copyright holder would have to bring the case before the court personally [or though counsel].
    If it was a criminal case the crown would have to be sure that conviction was likely and that such a prosection was in the public interest before bringing the matter before the courts.

    --
    There are places where the networks are not touching,and there are places where they are-Boeing's Lori Gunter
    1. Re:er, not obvious at all by Anonymous Coward · · Score: 0

      The presumption of innocence only applies in criminal cases. In a civil suit (like for copyright infringement) whoever has the preponderance of evidence wins. Not the kind of thing you see on Matlock.

  88. Morons... by Anonymous Coward · · Score: 0

    Whats the best way to get companies, groups or individuals out of open source development/support? By spreading unfactual FUD and accusations right and left when there is the slightest hint of GPL violation. Instead of somebody confronting the accused party the accusation is posted as fact on a major news site (slashdot) and they are tried and convicted by the trolls in the comments forum without a shred of proof or further investigation. Their reputation is damaged in the community and they are embarrassed because of something they are possibly innocent of or something that they would have voluntarily fixed if they had just been asked. This is not the way to "fix a problem" - by posting it on slashdot. This only creates hard feelings and anti-opensource/gpl sentiment with the accused and their supporters and this mob-mentality is one of the things that will eventually drive this community into the ground.

  89. Selective Angst by Arandir · · Score: 2

    Why the focus on on United Linux? Is it because of it's tenuous association with Ransom Love? Why are other betas under NDAs not targeted by the FSF?

    --
    A Government Is a Body of People, Usually Notably Ungoverned
  90. NDA vs non-redistribution. by Alexey+Nogin · · Score: 1

    NDA would not necessary be ioncompatible with GPL. One can have an NDA that allows redustributing the GPLed packages and source, but would prohibit mentioning that the particular code is a part of some bigger distribution, that it was produced by the company X, etc.

    In other words, NDA may allow redistributing the code, but not the meta-information (e.g any information on *where* the code came from).

    1. Re:NDA vs non-redistribution. by MrResistor · · Score: 2

      Yeah, you're right. That would be a pretty stupid and pointless NDA, though.

      --
      Under capitalism man exploits man. Under communism it's the other way around.
  91. greetings from Mandrake. .-) by deno · · Score: 3, Informative

    Not only that - we are in fact sensible enough to understand that RH isn't a big red devil either. .-)

    These games with closed beta testing, NDAs, and such are really bad, because they hamper the development. I'll leave SuSE in peace this time, but let's recal the Correls mistake:

    1) Take a KDE as it is, then quietly change it in-house, never releasing anything back, and withouth consulting the KDE team.This pisses up the KDE team.
    2) Release the product with "enchanced" version of KDE six months later, and wonder why nobody wants to see your patches anymore, and why the KDE team went on next version of KDE without you.
    3) Look at the cost involved to port all of your changes to next KDE version, and shoot yourself.

    In short, everyone lost. Now:

    * if SuSE and co. want to hide new capabilities of the Yast, more power to them.
    * If they start holding back changes/fixes they implemented on 3-rd party GPLed code in-house, in order to be able to ship better versions of free aplications that anyone else could, then we have a real problem.

    Think I'll let RMS clear this up, in the meantime I believe they are just hiding the new version of Yast, because they feel too embarassed by it. ,-)

  92. GDP = Gross Domestic Product by moogla · · Score: 2

    That's what I think of when someone says the "GDP". Now, next to the word "invoked", it may take on a different connotation.

    No UnitedLinux, don't release under the NDA, or you will incur the wrath equaling the total market value of all goods and services originating in the United States this year!!!!

    --
    Black holes are where the Matrix raised SIGFPE
  93. Sounds like Lindows by Dynedain · · Score: 2

    Except that Lindows actually charges for their 'beta' which is version 2.0 btw...oh, and you have to purchase the 'beta' in order to get the sourcecode.

    --
    I'm out of my mind right now, but feel free to leave a message.....
  94. Geek Mass Media by Bob+Snuffy · · Score: 1

    You know, I find it ridiculously hard to even read the newspapers anymore, and sometimes hard to read the magazines.

    The basic reason is that people don't report news facts, but rather they report news opinions.

    I'm just so sick of seeing these headlines that scream The Sky is Falling! and their proof is based on screenshots of a product they haven't used, or even worse, rumors of such-and-such without having validated it true or false.

    The worst part is that we (geekville) are doing the exact same thing!

    If we could stop this garbage race to see who can post the latest blah blah blah before we back it up ourselves with true proof that we've seen with our own eyes... we would probably see more progress in development instead of time wasted on pointing fingers and lawyer fees....

  95. Have you read XFree86's license? by Anonymous Coward · · Score: 0

    The only thing I don't see them rewriting "overnight" is the X server. Even if they build it for a framebuffer target, it's still a massive, complex piece of software. I don't know how much the X Consortium's code would help.

    XFree86 (the defacto Linux X Window System) isn't infected with the GNU General Public Virus. It is irelevant in this discussion.

    1. Re:Have you read XFree86's license? by Gooba42 · · Score: 1

      Don't release code under GPL if you don't like it and don't try to restrict my freedom to choose to release under GPL as I see fit.

      --
      I just found out there's no such thing as the real world. It's just a lie you've got to rise above. - John Mayer
  96. haha by Anonymous Coward · · Score: 0

    You people are always down on united linux's case, but I don't hear anyone complaining about people like lindows.com. What about their 'closed betas', and the fact they include nvidia binary drivers with their iso images/base install? Nobody else is doing that "because of nvidia's license" which is supposed to prohibit any 3rd party distribution.

    Blah blah blah you people make me sick. Just like the 'oh redhat is the next m$ - they are becoming just as evil and destroying our beloved kde/gnome'. TIME TO GET A BRAIN PEOPLE.

  97. Re:Who enforces the GPL ? by Anonymous Coward · · Score: 1, Informative

    The GPL is not another EULA. An EULA restricts your usage (End *User* License Agreement). The GPL only dictates how the program is redistributed. You can use your GPL'd software however you wish, without ever looking at the GPL. When you wish to redistribute the software, though, you are obligated to comply with the terms.

  98. Dont worry until RMS starts bitching... by Tonetheman · · Score: 1

    Don't worry about it until RMS starts whining about how Linux... oh wait I mean to say GNU/Linux is GPL'd and how United Linux is the devil for having a closed beta.

    It is a sad statement when the only /. news is the purist fuck rods complaining about not being able to see beta code... I think UL should just tar everything they do everyday and put it up on the web for RMS and all of the rest of the elite gods of programming can read all the source code and figure out what they have or haven't changed.

    Truly the open source community is led by a hyrda of morons. No wonder people think we are freaks.

    1. Re:Dont worry until RMS starts bitching... by Anonymous Coward · · Score: 0

      >>>Truly the open source community is led by a hyrda of morons.

      90% of the open source community are "1 man" projects --- they really care about GPL licensing violations. They are the typical "Linus" --- they don't care about making billions of dollars off their codes, their projects are just for fun and they really care about these GPL violations.

      Everybody else are tainted by employment contracts and stock options. They aren't the open source community.

    2. Re:Dont worry until RMS starts bitching... by Tonetheman · · Score: 1

      You are correct. I wish you had not been anonymous... I think that what you have said is really important and shows some thought.

      Most open source projects are one man projects and really do not care about GPL...

      Sorry to just put a "me too" post but you are correct.

  99. Ransom Love and the GPL by Anonymous Coward · · Score: 0
    Ransom Love never put down the GPL


    Are you kidding? Ransom Love has been bashing the
    GPL for years; and since this is common knowledge
    I don't have to post links as proof, for the same
    reason I don't have to post links when I claim
    that World War II actually happend.


    Mr. Love's dislike for anything GPL has been well known for ages
    and very predictable. (If he is your boss, asks him!)

  100. Oh my... by Anonymous Coward · · Score: 0

    Ransom Love doesn't even give credit to his last name :P

  101. Who cares, but UL is still a dumb idea. by Ogerman · · Score: 2

    You'd think that the likes of Suse, Turbo, SCO, and Conectiva would get the point by now..

    Well, these are folks who actually believed there was money in Linux distros in the first place.. so go figure. GPL violation or not, UL is an unnecessary muddying of the waters. Why don't they do something intelligent with their resources instead of re-inventing the same old wheel yet again. You know, like.. providing consulting services, developing custom software, improving existing OSS projects.. things that would actually do something for the cause of Linux and Free Software and maybe help our struggling economy! Instead, they're still daydreaming of dot-bomb companies that sell (branded) free software. Give it up guys. Learn from your mistakes and move on.

  102. How would you know? by Anonymous Coward · · Score: 0

    So what happens when the GPL is violated?

    What if someone actually took a GPL covered program ,used parts of it in his own program and then released a binary only version? How would one know that GPLed code had been used in this non-free program since the source is not available anyway? I believe there was some issue like this regarding some drivers for X but I don't really recollect the details.

  103. MyGroovyLinux(tm) by Anonymous Coward · · Score: 0

    So is it ok to make people sign NDA and not to release the source code in public without breaking the GPL? What if I start to sell MyGroovyLinux(tm) only for customers who sign the NDA? Or just accept my EULA...

  104. Question: Is a beta a distribution? by aug24 · · Score: 1
    The GPL specifically says that the source must be opened if the product is distributed but not if it is just used privately.

    This is a beta, in which case I wouldn't say it is being distributed. I also have every expectation that the source will be open when the product is actually distributed.

    Justin.

    --
    You're only jealous cos the little penguins are talking to me.
    1. Re:Question: Is a beta a distribution? by Phil+Hands · · Score: 2

      Try reading the article.

      As stated there, any distribution, including distribution to your business partners, is distribution under the terms of copyright law.

      If they've tried to restrict the other partners' redistribution rights, by imposing a GPL-incompatible NDA, then they are in violation of the GPL, and lose all rights to distribute the GPL licensed code in question.
      That would put them out of business.

      --

      Debian: GNU/Linux done the Linux way
  105. Curse of the MBA by Jeppe+Salvesen · · Score: 2

    Linux is ever growing. This UnitedLinux move is almost certainly initiated by some MBA (call me prejudiced..). What we need to do, is to determine whether this in fact is breaching the GPL, and then determine the best remedy.

    It is vital that we don't scare business away, but it is also vital that they get the point of the GPL. Whenever there is a problem, it is almost always best to deal with it while it is small. If a large industry is allowed to grow while being in violation of the GPL - well, history will not take kindly on the outfall of that.

    What do the stragetists among us think?

    --

    Stop the brainwash

  106. Nope. Copyright, right? by OmniGeek · · Score: 2

    As I understand it, copyright law prevents you from making ANY copies of a copyrighted work without special authorization (which the GPL provides). Thus, a firm CANNOT internally distribute GPL'ed software without observing the GPL terms. If you're not following the GPL, you lose all rights except those under copyright's "fair use" provision.

    Think of it using Borland's "like a book" analogy: Under copyright law, a company can't buy one copy of a book and duplicate it for internal use, so the same applies to the software.

    Of course, if EVERY employee separately downloaded it from a GPL-observant source, they'd be OK, but only for internal use, and they'd best be ready to prove that they did exactly that...

    --

    "My strength is as the strength of ten men, for I am wired to the eyeballs on espresso."
    1. Re:Nope. Copyright, right? by Fastolfe · · Score: 2

      This is a very good point, but compare your analysis with the real world and the intent of the GPL here.

      The GPL was designed so that companies could make use of GPL'd software and modify it to suit their purposes without having to worry that they'd be required to divulge trade secrets or proprietary code, unless they wanted to sell/give away that software.

      By your logic here, these ramifications extend far beyond a simple closed beta. You're essentially saying companies cannot make any meaningful use of customized GPL'd software in their company without being forced to release those changes.

      This is not in the spirit of the GPL and is not what happens today. A lot of companies would be in violation of the GPL if this were intended to be its interpretation, and a lot of companies would shy away from customizing GPL'd software for their own needs out of fear that they'd have to release details about some proprietary/secret aspect of their business, even though they have no intention of selling the software or giving it away.

    2. Re:Nope. Copyright, right? by Anonymous Coward · · Score: 0

      FSF's mandate isn't to design GPL licensing terms to suit businesses. That means that there are a lot of companies are in fact violating GPL.

      There are valid legal reasons for IBM never ever making an official IBM linux distribution. There are valid legal reasons for IBM to mandate that their employees to only work on stuff that are going to be incorporated into the main source tree to GPL projects (so that IBM doesn't have to make a distribution).

  107. Question About the GPL by Anonymous Coward · · Score: 0

    Lets say a company is working with software obtained from somewhere else that is under the GPL. The company modifies the GPL'ed software for its own needs. The company does not want to give the modified software to anyone outside the company--just people in the company can use the modified GPL software (or for that matter even know it exists). Is this legal?

  108. not any worse than any of the others by alpg · · Score: 1

    Mandrake, RedHat, Suse - all the 'commercial' ones skirt the GPL, why shouldn't United Linux?

  109. ...and another thing about commercial distros by alpg · · Score: 1

    Worse than RedHat, Mandrake, Suse is Lindows!