Slashdot Mirror


Bruce Perens Discusses Lawsuit Against Corel (UPDATED)

ac writes "It seems that Corel has made one mistake too many. Bruce Perens [?] is calling for a lawsuit against Corel on the behalf of Debian. The text of his message follows and should appear here soon. " Wow - check out the recent story regarding the 18 and older EULA. Update by RM: Bruce later backed off on the lawsuit threat. He reads Slashdot comments and takes them seriously, and he's a good dude at heart, okay?Update: 11/26 08:53 by H :And for all the people e-mailing me, mea culpa. Shoulda checked.

To: debian-legal@lists.debian.org
Subject: Corel Lawsuit
Date: Fri, 26 Nov 1999 10:09:00 -0800 (PST)
From: bruce@perens.com (Bruce Perens)
Message-Id:

It's time for us to bring suit against Corel for this "can't download unless you're 18" stuff. That's not in our license and they know it. I've tried to help them several times, and they continue to be 100% clueless. I think at this point they are not representing Debian well, and should not distribute it. I'm not going to help them any longer.

Bruce Perens

374 of 535 comments (clear)

  1. minors and EULA's by Barbarian · · Score: 4

    The problem is the EULA on the Corel software--in Canada at least, you cannot sign a binding contract if you're a minor.

    1. Re:minors and EULA's by ewhac · · Score: 5
      ...you cannot sign a binding contract if you're a minor.

      Which is precisely why license "agreements" of any kind are not only monsterously unethical, they are stupid. Do the clerks at EBX check your ID before selling you a copy of Unreal Tournament (which comes with a shrinkwrap "license")? Are we to suppose that such instruments should be enforceable against a minor's parents or guardian?

      Please, stop deluding yourselves into believing that you're purchasing a "license." You are purchasing a copy, and enjoy all the rights and responsibilities afforded to you by copyright law. Any other responsibilities imposed by any so-called "agreement" are fictional.

      Gratuitous link to my editorial on shrinkwraps.

      Schwab

    2. Re:minors and EULA's by otto+parts · · Score: 1

      hmm. given the packaging typically ties tacit agreement to the EULA to breaking of the shrinkwrap, the onus should be on the vendor to ensure that any of their product is not being sold to minors.

    3. Re:minors and EULA's by Brett+Glass · · Score: 2
      Which is precisely why license "agreements" of any kind are not only monsterously unethical, they are stupid.

      Good point, Leo. However, this begs the question: is any license which comes attached to a product and unilaterally imposes onerous requirements upon someone who uses it for a particular purpose likewise "monstrously unethical?"

      If so, it is possible to argue that the GPL, too, is monstrously unethical. Like the shrinkwrap license, it unilaterally imposes serious (and possibly unenforceable; we don't know yet) restrictions. Just like a spreadsheet license which said that the software vendor owned all the data you processed with the spreadsheet, the GPL stakes a claim upon the code of developers who wish to reuse code and avoid reimplementing the wheel. It is, in some fact, worse than the shrinkwrap license, in that shrinkwrap licenses are not (at least in any situation I've seen) "viral."

      I think that the real cause of conflict in this situation is, in fact, the GPL.

      --Brett

    4. Re:minors and EULA's by ewhac · · Score: 2
      ...is any license which comes attached to a product and unilaterally imposes onerous requirements upon someone who uses it for a particular purpose likewise "monstrously unethical?"

      In the general case, yes, this is my opinion. I have yet to be shown a situation where a vendor has any ethical, moral, or even economic claim to the kinds of restrictions found in shrinkwrap "agreements."

      If so, it is possible to argue that the GPL, too, is monstrously unethical. Like the shrinkwrap license, it unilaterally imposes serious (and possibly unenforceable; we don't know yet) restrictions.

      As I outlined in another Slashdot post, the GPL differs significantly from all other shrinkwrap licenses. Nearly all shrinkwraps attempt to constrain use; the GPL constrains copying. The GPL in no way constrains your ability to use the code for your own purposes. If, however, you wish to make and distribute copies, then the GPL stipulates the conditions under which you will be granted a license to do so.

      Schwab

    5. Re:minors and EULA's by Znork · · Score: 1

      The GPL does not impose any restrictions at all. The GPL grants you certain rights above and _beyond_ copyright law, _if_ and only if you agree to the license. If you do not agree you have no rights to do anything with the code.

      The GPL is not viral any more than any other license. The difference is that the GPL allows merging, which makes those properties of licenses apparent. All other licenses work the same way. If you combine works you must fulfill the terms of all the licenses in question.

      Try again.

  2. clueless by matman · · Score: 2

    well, he is right... corel does seem to be clueless. its like a kid being told by their parent to give something back to their sibling, but the kid only gives back part of it - like the remote control minus the batteries. hehe :)

    Hopefully this'll be the proverbial spanking that they need :)

    And why in the hell would they possibly say 18 only download? is it maybe because a minor can not enter into a legally binding contract or something?

  3. Didn't Bruce Mention this in the earlier article? by SgtPepper · · Score: 1

    And he should be keeping us up to date...so why did an AC post this? BTW Bruce's earlier post is here Someone may want to link this in the article posting if they haven't all ready, personally i like seeing someone taking this inceiteve(sp), we won't take our rights being violating standing down. Normally i wouldn't care, but this a blantent violating of the GPL in the EULA as bruce pointed out in his earlier post. :)

  4. Ick...my mistake. by SgtPepper · · Score: 1

    Got two posts confused, it was ottffssent's post i was refeering to here which i find more intresting and would really like to know more about the reply to :)

  5. I agree by finkployd · · Score: 1

    I agree with this, I know that in the previous story about the 18 year old restriction there were many people trying to rationalize it or say it was a good way to prevent lawsuits.

    The fact remains, it is a violation of a license, and this kind of stuff cannot go unchecked. Granted, it's minor, but we do not want to send the message that these open source licenses (especially GPL) can be violated in ANY way.

    As more clueless companies (I honestly had hope for Corel) get into open source, we need to be really be on guard to make sure they do it correctly. This kind of thing can only get worse if left alone.

    Finkployd

    1. Re:I agree by RichMan · · Score: 1

      The problem is that there are too many lawyers involved in this release.

      The problem is that according to Canadian law someone under 18 cannot be bound to license restrictions. So someone under 18 is free to violate the GPL along with all the other Corel license stuff anyways. In placing the restrictions on the software Corel is actually protecting the GPL.

      This is part of the stupidity of license restrictions in general.

      Any under 18 Canadian wanting to go buy some copies of Microsoft Software and violate the license agreement is free to do so. Seems like a good time to contract qsome high school Canadians to set up a Microsoft Network, they could do it with only 1 purchased copy of the software.

      Similarly under 18 Canadians are free to use Linux to make full commercial releases with private modified code. The GPL don't stick.

      Now say ARRRGGGHHHHHH!

    2. Re:I agree by Tarnar · · Score: 1

      I'll requote what I said in the previous thread.

      The GPL is a license. Canadian law prevents minors from entering into license contracts. Hence, Canadian minors can't agree to the GPL, no matter how free it's terms are. The GPL is free enough, the people just aren't free to enter the freedom.

      So it technically can't be called a violation of the GPL, but rather a weakness in EULAs and license laws in general. A lawsuit is not the way to fix this either. Corel is just following the letter of the law. It's a shame the spirit of the law sucks ass.

    3. Re:I agree by limpdawg · · Score: 1

      But what about copyright? The copyright on the code still applies and it forbids the redistribution of the code without the consent of the author. The authors of GPL software usually only consent to the redistribution of their software under the GPL. Therefore to redistribute it they would have to relicense it under the GPL or face copyright infringement litigation.

      --

      Nascantur in Admiratione. (Let them be born in Wonder)

    4. Re:I agree by sandman71 · · Score: 1

      I hate to say it but.. To be able to agree to a license, you CANNOT be a minor. To say it's against a license to put an age limit, it doesn't make any sense. How can it be against a license when that license in itself cannot legally be agreed upon by a minor! That includes *all* licenses as they are legally binding contracts. And as we all know (at least I hope most of you do),a minor cannot enter a legally binding contract on his/her own. So think about it. You guys are too quick to flame and start bitchfests. Think before typing. Midols for everyone! ;P Sandman Stop your bitchin and pick up a law book or two on the subject before starting to flame a company.

      --
      It's better to burn out than to fade away!
    5. Re:I agree by RichMan · · Score: 1

      As those under 18 in Canada are legally unable to consent to the GPL restrictions. No one under 18 in Canada is allowed to copy the Linux code in any form, by the copyright consent part of the GPL. Thus we have the perfect reason for Corel to tag the code the way the did. Corel is simply clarifying the legal restrictions placed on distribution under copyright and the GPL by Canadian law. For Corel to tag the code otherwise would have been negligence.

      Now say ARRRGGGHHH again.

      Because of its end user license agreement, it sould be illegal to sell Microsoft software to anyone under 18 in Canada as they are legally unable to agree to the terms of the licensing agreement. The fact that this has not been done is probably another good argument for the total unenforceability of the license agreement.

      This whole license agrement mess is stupid but points to some very interesting problems in the current structure of property laws.

    6. Re:I agree by Jon_S · · Score: 1

      I'm pretty sure that once Corel notices the hubbub they'll probably just change their licencing agreement. Wait out the holiday weekend, and I'm sure we'll see some reponse from them after everyone comes back from vacation.

      Um... Canadian Thanksgiving is in October. They aren't "on vacation".

      Jon_S...from just east of the (Buffalo, NY)

  6. Oh yeah -- way to support them by davidu · · Score: 5

    Let me first say that I agree, Corel has made _some_ mistakes. However, it is obvious that a big company with a huge legal department would have such problems.

    We should NOT however alienate them. Do you think that they would have spent so much money into Linux and made such a huge booth at Comdex if they were just around for the hype? of course not.

    We need to be forceful, yet forgiving in the way we handle the corel situation. If we alienate the first major company to support Linux then we may be jeoperdizing our future.

    I think Bruce Perens simply misses the spotlight. I respect him for what he has done and accomplished, but a lawsuit will not solve anything for Linux users and for the image of Linux.

    Bruce: you really ought to give this some more thought.

    -Davidu

    --

    # Hack the planet, it's important.
    1. Re:Oh yeah -- way to support them by boletus · · Score: 1

      has the gpl ever been tested in court?

    2. Re:Oh yeah -- way to support them by davidu · · Score: 1

      good point, I like the GPL, I code using the GPL as my license, however, I often have wondered, how legally binding is the GPL? Those of you who know what has happened to the LAME project, know that the GPL might be tested in court...
      -Davidu

      --

      # Hack the planet, it's important.
    3. Re:Oh yeah -- way to support them by willey · · Score: 1


      Jeopardizing our future by alienating a corporation? Get real. Free Software doesn't need corporate sponsorship to be a success. It already is a success! Break out of your feudal mentality.

      Mark

      --

      Mark
    4. Re:Oh yeah -- way to support them by hadron · · Score: 2

      Either it's valid, or everyone is violating copyright law due to it not being valid. All it does is allow you to do stuff you would not normally be able to do legally.

    5. Re:Oh yeah -- way to support them by dufke · · Score: 2

      This depends greatly on your definition of success. If your definition is that the software is working, you can get it, it's legal, and a lot of people are helping make it, then yes.

      But my definiton of success is that my friends will ask me to install Linux instead of Win98 on their gaming and schoolwork boxes. And every single game/chat/hardware they could download/buy would be available and supported for. (I'm not saying that there shouldn't be any competitors - long live the BeOS! :)

      Of course, there is no 'correct' definition, but one has already been achived... I'd like to go for the other one, wouldn't you?

      -

      --
      __
      Comment submitted. There will be a delay before you understand what you posted.
    6. Re:Oh yeah -- way to support them by Bruce+Perens · · Score: 2
      Point taken - anything I say or do may end up being publicized way out of proportion and I'd better be more careful about it.

      I get enough of the spotlight, don't worry about that. There's no chance that I'd miss it at this point - in fact I am fully aware of its disadvantages.

      I think that you have to count Red Hat as a major company now.

      Thanks

      Bruce

    7. Re:Oh yeah -- way to support them by davidu · · Score: 2

      1:
      Bruce Writes: I think that you have to count Red Hat as a major company now.

      Of course, but they are a 'major' company that already understands the premise of Free/Open/GPL software; that comment didn't help your point at all.
      2:
      I am shocked that so many people are taking the offensive and getting pissed at Corel. Like another poster said, sure we don't need big companies to keep Linux around in the server arena (I question that, but I'll give it to you) but for the workstation arena, we NEED support. Games like QuakeIII would have no chance if there weren't drivers for things like 3D cards and sound cards. Do you want to play Q3A in software render mode?...I think not! :)

      -Davidu

      --

      # Hack the planet, it's important.
    8. Re:Oh yeah -- way to support them by alprazolam · · Score: 1

      true but
      i understand how this is frustrating for bruce.
      corel really needs to reign in their legal department. its not fair for bruce to have to constantly step up and fix what corels broken. maybe its time for some sort of gpl legal group, i know you cant trust lawyers, but with more and more companies using free software, were gonna need protection

    9. Re:Oh yeah -- way to support them by davidu · · Score: 1

      this is nuts, how do my posts go from informative, to interesting and +5 to +4;flamebait...I think we need a glossary of terms to help out some of the dumb moderators. Now this could be flamebait -- hehe, but my original post, far from it.

      -Davidu

      --

      # Hack the planet, it's important.
  7. Woah... Back up. by wilkinsm · · Score: 1

    What "other stuff"? Help them "several times"?

    This "over 18 stuff" has already been discussed - it just the same "minors can'y enter into legal agreements stuff." Is this really so horrible that it's "the last straw?"

    You have to rememeber that businesses can't move as fast as individuals. Remember the Comdex thing? Give them a little room to think, and I think this will be fixed.

    1. Re:Woah... Back up. by Nodatadj · · Score: 1

      The "Beta test is under an NDA and you can't have the source" or whatever it was about 2 months back.

      They fixed that happily.

    2. Re:Woah... Back up. by SgtPepper · · Score: 1

      wilkinsm....have you tried going to The List? http://slashdot.org/comments.pl?sid= it intrests me that everything is from June....what's up with that?

    3. Re:Woah... Back up. by JatTDB · · Score: 1

      >>Is this really so horrible that it's "the last straw?"


      Think about the phrase "the last straw." By its very meaning, it is not necessarily something of overwhelming importance, just the latest in a pile. Just as with its origin phrase ("straw that broke the camel's back"), it is referring to a limit being breached that was nearly there already.

      For example, I used the "last straw" metaphor when I quit a job I had a while ago. I quit after a friend of mine was fired for rather flaky reasons, but in reality it was just one small issue on top of many others (low pay, bad work environment, boss became a real asshole, crappy coworkers, etc). What was really great though was when my boss asked me if I really wanted to "ruin my career" over something that small, and then I enumerated everything ELSE to him.

      --
      "That's Tron. He fights for the Users."
    4. Re:Woah... Back up. by wilkinsm · · Score: 1

      'Is this really so horrible that it's "the last straw?"'

      Think about the phrase "the last straw." By its very meaning, it is not necessarily something of overwhelming importance, just the latest in a pile. Just as with its origin phrase ("straw that broke the camel's back"), it is referring to a limit being breached that was nearly there already.


      Yeah, I implied the "this" was this EULA clause when I should of meant that "this" was Corel's additude over open source.

      From Bruce's original message, it appeared that they were one in the same.

      This really brings up an interesting problem - one which actually open source works against itself - Sometimes we move TOO FAST and without thinking.

      Measured cool responses to threats needs to become our standard practice or otherwise we will end up scaring everyone levelheaded away. As bad as Microsoft is, they don't sanction an anti-slashdot/anti-linux site, do they?

      Or, take this for example:

      *** Press Release from Microsoft
      Linux SUX! Opensource SUX! You reversed engineered our filesystems and SMB code
      so we are going to sue your ass off!
      - B.G.
      *** END Press Release

      Are we any better?

  8. Lawsuits by Tony · · Score: 1

    Yes, Corel is clueless about the Free Software licensing schemes. However, there is a catch to all this:

    In the US, you have to be of a certain age to be legally bound to any agreement you make. Since the GPL is a legal agreement, it is possible someone could circumvent the agreement and avoid any consequences, simply based on being a minor.

    What could a minor do with GPL'd software that isn't covered by the GPL? Beats me. Perhaps use the code in a non-GPL program. How does this affect Corel? It doesn't. So, it's rather senseless for them to include this in their license agreement.

    But I suspect that is the reasoning for this little bit of silly legalese. And this is yet another example of how our world is changing beyond our current society.

    --
    Microsoft is to software what Budweiser is to beer.
    1. Re:Lawsuits by tgd · · Score: 2

      Yes and no. As a minor you're not legally bound by contracts you agree to, but your parents can be if it can be shown that your acceptance of a contract or ability to accept a contract is the result of negligence by the parent.

      Ie, if you vioilate a EULA under 18, and it can be shown that your parents knowingly allow you to install software on your PC, your parents can be held liable.

      That'd be an extreme case, but a valid one.

    2. Re:Lawsuits by ewhac · · Score: 5
      Since the GPL is a legal agreement, it is possible someone could circumvent the agreement and avoid any consequences, simply based on being a minor.

      This is true for shrinkwrap "agreements" (which are a legal fiction, anyway), but not true for the GPL.

      Normal shrinkwrap "licenses" offer an array of ludicrous restrictions and covenants to which you are expected to agree before the vendor will "allow" you to use the software.

      The GPL, however, is different. It acknowledges the fact that, as a copyrighted work, the right to use software is concomitant with lawful possession and, thus, you are free to make use of the software as you will. What the GPL does is stipulate the conditions you must fulfill if you want to make copies of the software.

      Note the distinction: Shrinkwraps purport to offer a license to use. The GPL offers a license to make copies.

      Copyright law is criminal as well as civil law. Minors are not exempt from criminal statutes. Thus, a minor making and distributing copies of GPL'd software, but not meeting the terms of the GPL, would therefore not be granted a license to make those copies, and would be criminally liable for copyright infringement.

      So, no, being a minor does not escape you from the GPL.

      Schwab

    3. Re:Lawsuits by harlows_monkeys · · Score: 1

      Almost all copying a minor would do would be civil copyright infringement, not criminal copyright infringement. It is relatively hard for anyone not going into professional pirating to run afoul of the criminal copyright laws in the United States.

    4. Re:Lawsuits by Luis+Casillas · · Score: 1
      In the US, you have to be of a certain age to be legally bound to any agreement you make. Since the GPL is a legal agreement, it is possible someone could circumvent the agreement and avoid any consequences, simply based on being a minor.

      However, Corel is a corporation. Corporations can enter contracts.

      I can go to Corel's site and download the binaries for Corel Linux. I'm over 18, so no problem there. I can give these binaries to a minor. The GPL allows me to do so, as long as I comply with certain conditions-- which I do by passing along the offer from Corel to give out the source for the binaries they gave me for the cost of the reproduction. Now if this minor goes to Corel and asks for the source, Corel is bound by the GPL to give them the source.

      ---

    5. Re:Lawsuits by Luis+Casillas · · Score: 1
      From the GPL:
      3. You may copy and distribute the Program (or a work based on it, under Section 2) in object code or executable form under the terms of Sections 1 and 2 above provided that you also do one of the following:

      [snip]

      c) Accompany it with the information you received as to the offer to distribute corresponding source code. (This alternative is allowed only for noncommercial distribution and only if you received the program in object code or executable form with such an offer, in accord with Subsection b above.)

      Of course, this only applies to Corel if they are distributing binary-only CD's.

      ---

    6. Re:Lawsuits by James+Youngman · · Score: 1
      The GPL is *not* a legal agreement which is why you are not required to sign your name on it and send it back to the vendor before using GNU/Linux. The GPL is very clear about exactly what it is.
      Activities other than copying, distribution and modification are not covered by this License; they are outside its scope. The act of running the Program is not restricted

      ...

      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.

      In other words, the GPL is a license that covers the acts of copying or modifying the original work. You don't need to be able to agree to anything at all, and simply using the software is not a restricted act.

  9. Suing does not show gratitude to Linux dev's by Paolo · · Score: 1

    Regardless of how many mistakes Corel has made, suing is not the answer. Suing does not make Corel feel very happy about spending dollars developing for a platform that only turns around and hits them with a lawsuit. Instead, try contacting Corel's legal department civilly about the concerns. It'd be a mistake to ruin development for the community.

    --
    "In individuals, insanity is rare, but in groups, parties, nations, and epochs it is the rule." -Nietzsche
  10. I'm sure he doesn't mean this to come to court... by Paul+Crowley · · Score: 5

    I can only read this as "Perens calls for Corel to be sent signal that Debian's patience has limits". Debian would surely win if they sued, so I guess perhaps he's come to the conclusion that threats are the only language Corel's lawyer's speak. In other words, if all you recognise is "cover your ass" thinking, then you'll have to cover your ass from GPL violations too.

    I'm surprised, and I advocated showing patience to Corel earlier, but maybe Bruce is right: maybe it is time to say that the GPL demands attention and has backup if it's needed.
    --

  11. Just sent this to Bruce (Possible flaw in GPL?) by trims · · Score: 5

    Following is a letter I just sent to Bruce. I'm wondering if this is more a problem with the GPL than Corel; the GPL is not sacred folks, and it may indeed have flaws that need to be fixed. Anyway, we're getting ahead of the deal.

    I'm getting tired of the community going off half-cocked. Less than 24 hours after a problem DOES NOT MEAN we've looked at the things from all sides. Have we gotten REAL legal advice? From at least 3 different sources? Are we SURE of what we're doing? I'm getting really suspicious of the "witchhunt" mentality everyone someone screams "GPL violation!!!" Hysteria is bad for us, and I want us to think things through before we jump with both feet into the quicksand....

    -Erik

    Letter follows:

    Bruce,

    This is a followup to my thread on /. (found here) about the possibilities that an age restriction might be necessary to uphold the GPL.

    On further thought, I was wondering about this:

    The GPL requires that in order to use the software, I agree to the term (the contract) that forces me to distribute it to anyone who asks. And I must insure that the code is passed along with the GPL.

    Implicit in this is that I must insure that the person I'm passing the code to must uphold (or at least legally agree to uphold) the GPL. If they cannot, or willnot, I cannot pass the code to them, since I would be responsible for breaking my contract.

    This, however, is a catch-22 (or paradox) when talking about minors. The GPL requires that I give it to anyone who asks; however, I cannot give it to a minor, since I cannot insure that they abide by the contract (indeed, I have foreknowledge that they CANNOT), which is a further condition of the GPL.

    Paradoxes in contract law are EXTREMELY BAD, as it immediately invalidates the contract.

    Is this a flaw? Does the GPL need to be modified?

    Also, here is another pertinent question: suppose I am restricted from distributing the program due to content it contains. I've looked at sections 7 & 8 of the GPLv2, and it's not clear as to what the ramifications are in this situation. My reading is that any legally required restriction on code makes that code ineligible for coverage by the GPL (in otherwords, the author cannot GPL the program, nor can GPL'd code be included in the program).

    Have we got ourselves a serious problem here?

    --
    There are always four sides to every story: your side, their side, the truth, and what really happened.
    1. Re:Just sent this to Bruce (Possible flaw in GPL?) by copito · · Score: 2
      This, however, is a catch-22 (or paradox) when talking about minors. The GPL requires that I give it to anyone who asks; however, I cannot give it to a minor, since I cannot insure that they abide by the contract (indeed, I have foreknowledge that they CANNOT), which is a further condition of the GPL.


      I see nothing in the GPL that requires me to give software to anyone that asks. I just can't restrict further redistribution.

      As for a danger in giving the software to a minor, the GPL states:

      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.


      It seems to me that a minor would simply not be able to redistribute GPLed software, since they can't agree to a contract.


      --
      --
      "L'IT c'est moi!"
    2. Re:Just sent this to Bruce (Possible flaw in GPL?) by copito · · Score: 5
      Sorry about the formatting.

      This, however, is a catch-22 (or paradox) when talking about minors. The GPL requires that I give it to anyone who asks; however, I cannot give it to a minor, since I cannot insure that they abide by the contract (indeed, I have foreknowledge that they CANNOT), which is a further condition of the GPL.


      I see nothing in the GPL that requires me to give software to anyone that asks. I just can't restrict further redistribution.

      As for a danger in giving the software to a minor, the GPL states:

      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.


      It seems to me that a minor would simply not be able to redistribute GPLed software, since they can't agree to a contract.


      --
      --
      "L'IT c'est moi!"
    3. Re:Just sent this to Bruce (Possible flaw in GPL?) by Zach+Baker · · Score: 5
      The GPL requires that in order to use the software, I agree to the term (the contract) that forces me to distribute it to anyone who asks.

      This is a common misconception. The GNU GPL restricts modification and/or distribution, not use. This is not a minor distinction. For your edification, Term 5 of the GPL, italics mine:

      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.

    4. Re:Just sent this to Bruce (Possible flaw in GPL?) by bogado · · Score: 1

      I would like to say that by the same reasoning minors could not modify the program, for this they must agree to the contract, witch they can't. I don't know all the GPL by heart, but I think that it says that every one can modify the program, and here is the catch 22 again.


      --
      "take the red pill and you stay in wonderland and I'll show you how deep the rabitt hole goes"

      --
      []'s Victor Bogado da Silva Lins

      ^[:wq

    5. Re:Just sent this to Bruce (Possible flaw in GPL?) by sreeram · · Score: 2
      Implicit in this is that I must insure that the person I'm passing the code to must uphold (or at least legally agree to uphold) the GPL
      Dude, there is no such implicit statement in the GPL. If you want to distribute GPL'd software (say, to Joe), then the GPL says that you must distribute it under the GPL. It does not say that it is your responsibility to make sure that the GPL is honoured by Joe.

      Let me say that again: You have to abide by the GPL. It is not your responsibility to see whether or not others do. If Joe does not uphold the GPL, then it is none of your business. It is upto the copyright holder to sue Joe (if you hold copyright on parts you modified, then yeah, you may want to sue Joe too). If Joe is a minor, and thus by definition, is not legally bound to abide by the GPL, then yeah, maybe he can't be sued. But that doesn't make you liable. As someone pointed out, if the minor is not liable, then the liability falls on the minor's parents. Not you.

      Someone pointed out that, just because Joe (a minor) is not bound to obey the license, he cannot modify and redistribute at will. If Joe does not abide by the GPL, then he doesn't have any rights at all. All the rights are reserved (by default) by the copyright holder, and the GPL is the only thing that gives you the right to modify/distribute. There is no danger that a minor can make a proprietary version of GPL'd software.

      Someone else wrote:

      Corel could refuse to sell their software to anyone other than Tibetan monks between the ages of 65 and 70.
      Partly true. The GPL says explicitly that you agree to provide source code to any third party who asks. Some say "third party" here refers to anyone and everyone in general. But others say it refers to whoever you distributed the binaries to. In any case, if Corel sold Joe a copy of GPL'd software, then Corel must give Joe the source if he asks. Of course, Corel can refuse to sell the software altogether to Joe, but they cannot give only the binaries and withhold the source. The GPL doesn't force you to distribute to anyone. You can choose who to give/sell the software. But if you do give/sell it, then the source must be part of it.

      Sreeram.

    6. Re:Just sent this to Bruce (Possible flaw in GPL?) by Bruce+Perens · · Score: 3
      Erik,

      Agree that the witch-hunt mentality is bad for us. I headed it off twice before. I just got too darned frustrated about heading it off yet another time. Stupid me, I didn't realize that one message posted to an obscure Debian mailing list would mean a slashdot headline.

      Regarding the GPL, it's not a tear-open license that constitutes a contract like some other Open Source licenses. It's a straight copyright permission. So your objection might not apply.

      Thanks

      Bruce

    7. Re:Just sent this to Bruce (Possible flaw in GPL?) by Jonas+�berg · · Score: 2

      Why did you send this to Bruce? It should be perfectly obvious that it's better to contact the FSF about issues regarding possible flaws in the GPL. If your conclusion would have been right (I don't think it is), the FSF lawyer could have looked at it together with RMS to draft a change.

    8. Re:Just sent this to Bruce (Possible flaw in GPL?) by Compuser · · Score: 1

      So does this mean that all GPL code written by
      minors needs relicensing by their legal guardians?

    9. Re:Just sent this to Bruce (Possible flaw in GPL?) by 2RockStars · · Score: 1

      Moderate the above post up, dammit! He gets it all right. This is a great explanation of the part the GPL plays in this whole farce...

      As an aside, it seems to me that GPL has the perfect amount of "non-proscription" built into it, and that clever "viral" mode of transmit forces a certain amount of "non-proscription" onto other license writers... I assume that BP is worried about Corel trying to proscribe on top of the GPL, not about the particulars of whether or not a minor can agree to a license, or copy, or whatever...

    10. Re:Just sent this to Bruce (Possible flaw in GPL?) by samantha · · Score: 1

      So what does the entire brouhaha have to do with GPL? It seems a comment was desired to say the GPL is not sacred when what
      was said about the GPL actually applies to all contracts of any kind and has zero GPL specificity that I see.

      What am I missing?

    11. Re:Just sent this to Bruce (Possible flaw in GPL?) by Gleef · · Score: 2

      copito wrote:

      I see nothing in the GPL that requires me to give software to anyone that asks. I just can't restrict further redistribution.

      In general, this is true. In this particular case the software in binary form can be distributed without regards to age, but when a minor goes to retrieve the source code, as per the GPL, the 18+ restriction comes to play.

      ----

      --

      ----
      Open mind, insert foot.
  12. Interesting point (on contracts and 18) by ebrandsberg · · Score: 3

    Basically, the way I see it, if Canada law says that you can't enter into a binding agreement, and even a GPL license is an agreement, than that means that in Canada, an 18 year old can't agree to honor the GPL. As such, Corel is insuring that anybody that downloads has to otherwise agree to all the license requirements, including GPL. If they are correct, then any minor can break the GPL and use the software however, and whereever they want, without having to return modifications, etc.

    1. Re:Interesting point (on contracts and 18) by SL2C · · Score: 1

      But if someone can not legally enter into a contract, and the contract (or GPL license agreement) is therefore void (or whatever the appropriate legal term is), doesn't this simply mean that the person does NOT get the right to redistribute the code?

      I think the situation is this:
      A gives B a copy of a GPLed program, with A being either the author (copyright holder) or being allowed to do so via the GPL.

      The GPL gives B the right to redistribute copies under certain conditions (such as doing so under the same licenseing terms), which right B would not have without the GPL.

      If B did not legally agree to the contract/GPL, and B gives the software to someone else, B is simply infringing on the author's copyright!

      This is exactly the same situation as if B would copy a commercial, copyrighted program and give the copy away!

      For example, if a minor gets some cool game from their parents as a present and then copies it, that's surely copyright infringement even though he is a minor?

  13. Bad Mojo for the Linux Community by FPhlyer · · Score: 1

    This really puts us in a very odd position. Corel's EULA is likely to cause a boycott of it's product by us, the Linux community. But that would be a VERY bad thing for Linux' continued acceptance and integration into the coorporate mindset.
    I think we all need to be calm right now and don't jump Corel's case too quickly. Give them a day or two to get this rectified. I have faith (I hope well placed) that Corel will do the right thing here and recend this part of the language in their EULA.
    If not, Debian users still have, well... Debian. And Corel's version will never catch on (which will be bad for everyone, but may be necessary to protect the spirit and letter of the GPL.

    --
    Brought to you by Frobozz Magic Penguin Fodder.
  14. GPL under fire by Camelot · · Score: 1
    Let's face it - this was inevitable. No matter what the terms of the GPL are, there was bound to be someone who would break them. As a result, GPL has to be tested in court - or Corel will have to bend.

    I only wish it wouldn't have been an entity that is friendly towards Linux (well, at least in theory). And no, I didn't mention that one special everyone's favorite company, they have enough lawsuits anyway.. ;)

    I wonder if Corel felt like they can do whatever they want, pee on Debian people and the whole Linux community just because Debian isn't a commercial distribution.. Could you see them do this if Corel Linux was based on RedHat ?

  15. Hold on by copito · · Score: 3

    IANAL, but it seems to me that any restriction Corel places on the original download of their distribution is legal. The GPL allows me to distribute software for money or with a warranty, and AFAIKT, any further restrictions that do not restrict the ability of my customers to redistributing the binary and source.

    Corel could refuse to sell their software to anyone other than Tibetan monks between the ages of 65 and 70. They just can't keep those monks from redistributing the GPLed portions.

    So in short, Corel's actions may not be in keeping with the spirit of Free Software, but I see nothing in the GPL to prevent them.
    --

    --
    "L'IT c'est moi!"
    1. Re:Hold on by IIH · · Score: 2
      IANAL, but it seems to me that any restriction Corel places on the original download of their distribution is legal

      I'm not so sure - From the GPL (emphasis mine):
      "You must cause any work that you distribute or publish, that in whole or in part contains or is derived from the Program or any part thereof, to be licensed as a whole at no charge to all third parties under the terms of this License"

      Corel could refuse to sell their software to anyone other than Tibetan monks between the ages of 65 and 70. They just can't keep those monks from redistributing the GPLed portions.

      Hold on, either Corel can add any restriction (like you said), or they can't. What if one of the restrictions was "You may not redistribute any of the enclosed software." Would you still regard that as legal?

      If a precedent like this is set, what would stop a company trying to add "The program is covered by the GPL, but before we allow you to download it, you must agree to waive your GPL given-rights"?

      Not as far fetched as you might think, and the thin edge of the wedge is always easier to stop, if you see it coming.
      --
      --
      Exigo spamos et dona ferentes
    2. Re:Hold on by copito · · Score: 2
      You must cause any work that you distribute or publish, that in whole or in part contains or is derived from the Program or any part thereof, to be licensed as a whole at no charge to all third parties under the terms of this License"

      This is a bit ambiguous, I agree. But I think "all third parties" means all third parties to whom you have distributed the derivative program, any other meaning is too onerous.

      Hold on, either Corel can add any restriction (like you said), or they can't. What if one of the restrictions was "You may not redistribute any of the enclosed software." Would you still regard that as legal?


      Hold on, yourself. I said they could do most any restriction except preventing their customers from redistributing GPLed software. This obviously puts severe practical restrictions on their power, but it does not preclude them from restricting primary access.
      --
      --
      "L'IT c'est moi!"
    3. Re:Hold on by jareds · · Score: 1

      I'm not so sure - From the GPL (emphasis mine):
      "You must cause any work that you distribute or publish, that in whole or in part contains or is derived from the Program or any part thereof, to be licensed as a whole at no charge to all third parties under the terms of this License"

      Note the use of the word "licensed," not distributed. That means that if I modify GPLed software, I am not required to distribute it to everyone in the world. However, anyone who obtains a copy of my modifications through any means automatically has a license (GPL) from me under the terms of the GPL.

      Therefore, as copito said, Corel may arbitrarily limit the distribution done by Corel. However, they cannot restrict the distribution of Corel Linux by others. (Except, of course, for such portions as WordPerfect which are not under the GPL.)

  16. Let them explain themselves. by Tyrell+Hawthorne · · Score: 2

    Make sure Corel has explained why they have added this clausule, and check whether they might change it. If not, do *something* about it (still not sure suing is the answer, see post below), but don't be too quick with a lawsuit. My two cents...

  17. 3 strikes and you're out by Nodatadj · · Score: 2

    Is this the rule we're playing by in the Open Source community? Make 3 mistakes and then we get the big guns on you and stop being friendly?

    Every other time Corel arsed up their licenses they complied without any fuss, why is this time any different?

    I think his lawsuit threat will scare people off rather than make them release open source stuff

    Iain

    1. Re:3 strikes and you're out by fibonacci · · Score: 1

      How about all the other times they've "arsed up", like the insider trading fiasco, using the photo of a recently deceased child on the cover of Draw! without asking the parents' permission, and using the photo of an old-time actress (who they probably assumed was dead) on the cover of Draw! without asking her permission....

      Within the open source community or not, they've more than used up their 3 strikes. Now they're working on their 9 lives!

      [really, their worst mistake was building their corporate headquarters using that shiney gold reflective glass to cover the outside. The sun reflects off it and blinds you as you drive by it on the highway going east at sundown!]

    2. Re:3 strikes and you're out by Nodatadj · · Score: 1

      But those other things are not related to open source, and while they were stupid, I think we (the open source commnuity) should be forgiving. They are working very hard, and it's a new market thing for them and their lawyers, who are the ones really at fault, because they don't understand the way this free software thing works.

    3. Re:3 strikes and you're out by acidrain · · Score: 1
      [really, their worst mistake was building their corporate headquarters using that shiney gold reflective glass to cover the outside. The sun reflects off it and blinds you as you drive by it on the highway going east at sundown!]

      Given Ottawa's freeways it really is dangerous. I think I'll add that the next time I feel the need to write Corel about their lack of understanding of GNU/Linux. Sigh.

      --
      -- http://thegirlorthecar.com funny dating game for guys
  18. Hmm ... GNU shows some teeth? by RNG · · Score: 3

    I'm sure Corel has had enough contact with people like BP (and Linux folk in general) that there's really not much of an excuse for being contiunally clueless ... I was (or still am) willing to give Corel the benefit of the doubt about their Linux/OpenSource romance but things like these make me very skeptical ... I think it's about time they wised up and manage to produce a licence without any obvious problems ... this is not rocket science and should be an achievable goal for a company that manages to writes pretty good software ...

    On the other hand, maybe a GNU inspired lawsuit against something as obvious a violation of the GPL as this one, might actually make other potential offenders think twice about actually doing so.

  19. Who's gonna sue? by Bitscape · · Score: 2

    So whose shoulders would it fall on to enforce the license, when push comes to shove? I suppose since the Free Software Foundation owns a lot of the code, they could press the issue, but I don't see someone like Linus (or any small time developer) wanting to spend time in a lengthy court battle over this stuff. I certainly wouldn't.

    1. Re:Who's gonna sue? by I+R+A+Aggie · · Score: 1
      So whose shoulders would it fall on to enforce the license, when push comes to shove?

      Well, take a look at www.debian.org and about 80% of the way down you see this:

      Software in the Public Interest, the non-profit umbrella organization that manages Debian's assets

      James

  20. "Minors can't enter into legal agreement" BS by roystgnr · · Score: 5

    IANAL, and I don't know what the law literally states... but there's absolutely no way that the software industry would let a "minors aren't bound by software licenses" precedent be set. What, is it OK to be a warez dude as long as you're under 18? Does CompUSA have to start checking IDs before it sells the next Kings Quest installment?

    1. Re:"Minors can't enter into legal agreement" BS by Augusto · · Score: 1

      So you're saying any person of any age that can read and use a computer will understand all the implications imposed by this license ???

      I'm over 18 and involved in programming since 10 and most software licenses seem like Klingon to me !!!

      --

      - sigs are for wimps.
    2. Re:"Minors can't enter into legal agreement" BS by DJerman · · Score: 1

      No, we're saying that no 8-year old is allowed to photocopy _House_at_Pooh_Corner_ and give it to his friends, unless he has a letter from the publisher giving him that right. A EULA is just a letter from the legal author or someone licensed by the legal author giving you the right to copy something that you ordinarily would not have the right to copy. All that oh-by-the-way-you-can't-sue-us stuff may or may not be hogwash, maybe depending on your majority, but the grant of the right to copy and the ability to restrict it applies to anyone.

      --
    3. Re:"Minors can't enter into legal agreement" BS by Augusto · · Score: 1

      Yes. I understand your point. But I still think there is a problem if said 8 year old has to sign a license by reading a README and clicking "OK". How can he sign & agree to licenses/contracts if he can't even wipe his you know what correctly. ;)

      --

      - sigs are for wimps.
    4. Re:"Minors can't enter into legal agreement" BS by cduffy · · Score: 2

      Yes, it's OK to be a warez dude as long as you're under 18.

      That's what the law states; That's How It Is.

      Now, the software publishing companies would really rather be ignoring that fact...

  21. Our "leaders" ... by Augusto · · Score: 1

    ... need lessons in PR and/or human interaction.

    These type of comments from our unelected open source leaders turn off companies to adopt any type of open source license.
    Imagine if you're a small company with little budget for expensive legal advice. Will you be willing to try out one of these licenses and then be sued by Mr. Open Source (tm) here ?

    Geez, give me a break. Are we lawyers or coders here ?

    --

    - sigs are for wimps.
    1. Re:Our "leaders" ... by Bruce+Perens · · Score: 2
      No, I no longer lead the Debian project, and when I did we didn't count votes. And I got a little too upset this morning and said stuff I should not have.

      Bruce

  22. Re: Hey, minor doesn't mean bad person! by greed · · Score: 2

    however, I cannot give it to a minor, since I cannot insure that they abide by the contract (indeed, I have foreknowledge that they CANNOT), which is a further condition of the GPL.

    Well, I think this is a bit strong. Although a minor cannot be compelled, by Canadian law, there is no reason why a minor cannot act in good faith and uphold the contract even though he is not legally bound to do so.

    I think this is well demonstrated by the number of minors making successful contributions to GPL projects.

  23. Re:here they come. nail in the coffin by Anonymous Coward · · Score: 3

    Mistake #1: Slashdot is NOT THE LINUX COMMUNITY. Slashdot is a locker-room full of nitwits and posers who like flicking the towel at whoever passes by. (This is sure to get me 'moderated' down or whatever)

    Mistake #2: Yah, as if going back to Microsoft is going to magically make anything better. You think that by 'going back to Microsoft' you're going to avoid the lawsuit morass? Are you living under a rock or something?

  24. I'll chill out now, thanks by Bruce+Perens · · Score: 5
    Guys, I am having a real bad morning and I spoke too soon. I meant to open a discussion on a mailing list, not to be on top of Slashdot by sending one email. Everybody else on the list said it's too soon for a lawsuit.

    Bruce

    1. Re:I'll chill out now, thanks by Eg0r · · Score: 2
      Dear Bruce,

      You're a respected figure as far as the free software Ultimate Goal is concerned, same whenever you talk about Debian, GNU or Linux and are also admired by billions of people who read /.

      "look at his karma maaaaaaan, who is he? Is he... God??"

      Besides, you can't just go around and say stuff like

      "I think it's time to start talking lawsuit."

      As usual, you got moderated up because you spoke, and Your Words made the exclusive /. news 5 minutes later, and MSNBC, MSBBC, MSCNN or MSTimes the day after... Hell I'm sure you'd get moderated up to +5 insightful if you posted your shopping list or something...

      So be careful,

      "having a real bad morning"
      ...is definitely no excuse :-)

      But anyway, who am I to dare talking to You?

      ---

      --
      "Hasta la victoria siempre!" El Comandante
    2. Re:I'll chill out now, thanks by Bruce+Perens · · Score: 2
      Point taken. I guess "I screwed up" is no excuse either, but there isn't much more I can say.

      Besides, I don't have Ulitmate Karma on Slashdot. Sig11's is higher than mine (I just happened to look at his user record a while back), probably other people as well.

      Thanks

      Bruce

    3. Re:I'll chill out now, thanks by tgd · · Score: 2

      Hey Bruce,

      It sucks this happened on here, its yet another example of how /. has really been going downhill in the last six or nine months. It used to be the worst things that got posted were stories posted as new info that were duplicates of things posted in the past by other /. honchos.

      Since the beginning of the year, that seems less of a problem, and a bigger problem is poorly researched stories being posted and thus given validation when they're wrong, or cases like this when things get blown way out of proportion.

      Its like seeing Newsweek turn into the Enquirer.

    4. Re:I'll chill out now, thanks by evilad · · Score: 1

      Dude: You chill out.

      Much like the Corel/Wine debacle, if the original submitter had taken the couple of minutes to confirm what they were posting, the entire 150K of wasted human life would have been avoided.

      "Hey Bruce, did you mean this?"
      "Uh, no. Bad morning."
      "OK. I won't post it on /. and get 1000s of people's hackles up, OK?"
      "Yeah, good idea."

      But of course that couple of minutes might have meant someone else beating them to the punch, and if you can't have the glory, what's the point in even participating, right? I too have had bad mornings, and I'm even smarter than you are, you knee-jerk jerk.

    5. Re:I'll chill out now, thanks by Eg0r · · Score: 1
      Man, my post was supposed to be funny... I sure hope Bruce understood it as in:
      I too have bad morning syndrome (BMS?) sometimes, heck, I sure know exactly how you feel, don't be too depressed though, you are still our god :-)

      I somehow think you are barking at the wrong tree...

      You made one good point though, let's not spoil Bruce's day any further, I think he's deserved enough of our kind help for one day! (BTW, for the humour impaired reader, this is called sarcasm...)

      ---

      --
      "Hasta la victoria siempre!" El Comandante
    6. Re:I'll chill out now, thanks by ucblockhead · · Score: 1

      Uh....do we really want people like Bruce Perens afraid to say what is on their minds for fear of it being plastered all over /.? I don't know that this is a particularly good thing. I'd much prefer people, even "important" people, felt free to speak their minds.

      The real problem is that /. seems to be getting infected with some sort of media jouralism meme, where everything must be a REAL BIG DEAL!!!! and headlines must be blown out of proportion to catch eyeballs.

      For things such as this, I think that people ought to adopt more of a wait and see attitude before getting all in a lather, both when reading, and when deciding whether or not to submit. It doesn't hurt to wait a day or two to see if something really is the huge threat to dogs, apple pie and "Open Source" that you think it is.

      (Caveat: I own Corel stock.)

      --
      The cake is a pie
    7. Re:I'll chill out now, thanks by evilad · · Score: 1

      It's like this, man: sarcasm is never funny. Not unless it's in italics.

      I'm very glad to hear that you were being sarcastic, BTW. I hereby retract the "even" bit about being smarter.

  25. Corel and other sue-phobic companies by mr_organic · · Score: 2

    As more publicly-traded companies try to get in on the popularity of Linux, we are going to have more problems like this. The basic problem is that companies are shared shitless of getting sued, and will always try to put in contractual language to limit their liability. This, unfortunately, is completely at odds with the tenets of Free Software (particularly the DFSG). I think what has got Bruce Perens so angry is that he has *repeatedly* dinged Corel on this issue, and apparently they have ignored his cautions. In essence, Corel has violated the DFSG by the restrictive language in the EULA. This has happened before -- Corel linked the apt package (a GPL'd component) to the QT library (non-GPL'd) and had to get special dispensation from the apt author to do this. It just depresses me because I had hoped that Corel *really understood* the DFSG and what it meant to the community. I'd like to think that this was just an oversight, but it would have to be pretty gross negligence on Corel's part to let this get by. At the very least, it shows that Corel has been sloppy in their technical understanding of the DFSG, which is unforgivable given that they have had the direct cooperation of Bruce Perens for several months. Corel should be given to understand in no uncertain terms that this kind of behavior is unacceptable.

  26. 18 crap by sirkut · · Score: 1

    I know there is more to the point then the whole being 18 thing.. But how many minors are actually gonna stop using the distro, let alone even READ the EULA? I think we should treat this like porn sites... No one but yourself knows your real age. :)

  27. A quick question. by quasipunk+guy · · Score: 1

    As I understand, the Corel license prohibits minors from downloading their distro, right? So, if say, a minor was able to email or call and get a CD sent to them (for cost) wouldn't Corel be perfectly within their bounds?

  28. right to refuse sale by MrChips · · Score: 1
    Does the GPL really insist that Corel must sell (give) their software to anyone and everyone who wants it? It seems to me that Corel has the right to refuse to sell (give) its product to anyone they choose. What Corel does not have the right to do is attempt to restrict who its customers are allowed to redistribute the software to. A minor must be able to get Corel Linux from anyone willing to give (sell) it to them (even if Corel itself won't). Is Corel trying to prevent this?

    Chris.

    1. Re:right to refuse sale by Luis+Casillas · · Score: 1
      You are looking only at the transaction between Corel and a customer, and not at the responsibilities that Corel acquires when it distributes GPL software. It must distribute it either with a copy of the source, or with a written offer to give the source for the price of copying. The person who gets the binaries from Corel may pass them on to a minor, who could ask Corel for the sources.

      But IIRC Corel is selling the CD's with the source code along...

      ---

  29. Re:here they come. nail in the coffin by Bruce+Perens · · Score: 5
    Look, I'm frustrated because I have tried to help them with this stuff twice and they keep making the same mistake. I sent mail to a Debian mailing list looking to open a discussion, not to be in a Slashdot article about it. Everybody else on the list said it was too soon for a lawsuit and I dropped it there.

    Thanks

    Bruce

  30. well... by ransom · · Score: 1

    Why not be quiet about what a shitty job Corel is doing and just stop using their distro? It's just a Debian spinoff, so use Debian! Easy way to avoid many unneccsary problems. If we don't use it, they won't sell it or get hits, therefore, they will stop making it because it is not profitable. Remember, they are a commercial company, which is why they are doing all this in the first place... so use their own tactics against them. They don't want peolpe to download it, ok, we won't! :)

    If you think you know what the hell is going on you're probably full of shit.

    --

    If you think you know what the hell is going on you're probably full of shit.
    jdube is who I am
  31. Corel may now learn its lesson. by Brett+Glass · · Score: 1
    Corel embraced Linux without realizing that the GPL, under which Linux is licensed, was motivated not by a true spirit of openness and sharing but rather by bitterness and spite. The targets: business, entrepreneurship, and programmers who desired to make a fair living from their work. Contrary to the FSF's attempts at PR "spin," this has always been the agenda of Richard Stallman and many othe promoters of this license.

    Corel, which is now finding itself attacked at every turn by the GPL "faithful," should now recognize that it jumped on the Linux bandwagon too hastily. Because Corel is a commercial software developer, the GPL is not its friend but rather its enemy, and is in fact designed to destroy it. (The GPL does not even conform to the "Open Source Definition," as it discriminates against Corel's field of endeavor: the creation and publication of commercial software.)

    Hopefully, Corel will be smart enough to do an about-face and promote software which is not encumbered by the GPL's "poison pill" provisions. I'd recommend OpenBSD, since it is not only perhaps the world's most secure OS but also a Canadian product which makes better use of encryption than an exportable American product could.

    --Brett Glass

    1. Re:Corel may now learn its lesson. by Menthos · · Score: 1
      And this is worth score +3? It seems more like flamebait to me. Last time I checked the GPL passed the Open Source Definition perfectly.

      --

      GNU/Linux. The Freshmaker.

    2. Re:Corel may now learn its lesson. by bkosse · · Score: 1

      Brett, you're an idiot. (Why do I find myself repeating truths so dang often around you?) Brett, you've made several rather large and, potentially, unsettling claims. However, your only evidence is that you *THINK* something. Why should I accept *YOU* at face value when you won't accept RMS at face value? After all, you want to use other people's work for *YOUR* benefit, to hell with them.

      --

      --
      Ben Kosse
      Remember Ed Curry!
  32. What is the goal, here? by wasted · · Score: 1

    IANAL, and I haven't spent any time studying the GPL and its implications, but I doubt the lawsuit will accomplish anything. The EULA looks like a cut and paste job. (Note that the generic portions, including the offending portion, are in all caps, and the parts specific to Linux were written using both upper and lower case.) It doesn't look like Corel has any intent to be anti-GPL. They do need help keeping things straight, maybe a my-lawyer-call-your-lawyer thing at most. Corel (or the clerk who types these things) seems to be a "GPL newbie". If the community treats Corel bad, they will have reason not to deal with the Linux community, and the Linux community will be setting a bad precedent, probably scaring off other developers, including hardware developers whose drivers we might like to have. So even if we win the battle, we lose the war.

  33. seems GPL compatible to me by fasten · · Score: 1

    The GPL doesn't force me to give covered software to anybody. If I choose to do it I have to include the source but if I refuse to distribute the software that's my business. So why can't Corel refuse to give the whole package to certain people?

  34. Idealistic people by fizik · · Score: 2
    This reminds me of the controversy surrounding the kid who couldn't get into Comdex. They don't check for ID at Comdex, go and have a good time. The same applies in this case. If you're a minor and you want a copy of Corel Linux, go and buy, go and download it, I really doubt the 'EULA Police' are going to come to your door and bash it down and confiscate your computer.


    I think we need to step away from this 'holier the thou' attitude and take a closer look at the situation. Companies like that don't get into the position they are currently in by leaving themselves wide open to stupid lawsuits. Judging by the amount of posts on Slashdot regarding the whole 'if user x is a minor, then x cannot legally accept the GPL therefore . . . ', i'd say that the entire issue is very grey and Corel is just covering their ass.


    As for the people at Debian, chill the hell out, Have you tried to contact Corel and ask them their reasons for putting such a clause in their EULA. One thing I appreciate about the open source community is that fact that people are willing to look at problems from a variety of angles. However, it seems to me that everyone automatically has a problem with Corel because they are a company that 'GASP' actually makes money by selling commercial software. Instead of jumping all over them, why isn't a little constructive criticism offered. If I was running the Corel Linux development I would seriously get discourged by having the Linux community try to bite me in the ass every time I took a step.

    My point is this, the issue is obviously somewhat complicated because it doesn't seem like anyone on Slashdot has posted a definitive legal opinion on the matter. Lets take a bit of time and analyze things before we start making accusations.

    1. Re:Idealistic people by blacklambda · · Score: 1

      I think you are missing the point. Just because not everyone will read the EULA does not mean it isn't there. And although many minors will undoubtedly download it any way doesn't change the fact that they are not welcome. Linux was not meant for a privilaged few no matter if it's by age or any other discriminating factor.

      --
      Ryan Dorman, CCNA Network Communications Specialist Millersville Univesrity
  35. Apology to Corel by Bruce+Perens · · Score: 5
    Oh darn, I have really screwed up this morning. I'd better admit it and control the damage before it gets worse.

    I got frustrated with Corel because I have worked to smooth these things out twice before. I sent a message asking if it was time for a lawsuit to a Debian mailing list. I did not expect that message to be posted to Slashdot. The people on the Debian list told me to chill out, which was good advice.

    So, Corel folks, I apologize. You need to sort our some issues with the community, but any talk of a lawsuit at this time is way out of proportion.

    Bruce Perens

    1. Re:Apology to Corel by Bogus+Nick · · Score: 1
      You're attempting to put the genie back into the bottle with this one. There have been several people here who agree with your original email about suing Corel, they are not likely to change their mind just because you retract your 'shoot from the hip' email.

      Good luck controling the damage on this, the thread so far is enough to convince many companies that it's not worth the trouble to go open source/GPL at this time.

    2. Re:Apology to Corel by Bruce+Perens · · Score: 3
      Well, Nick, we have Red Hat stock at over US$200 today from its original $14. That is going to convince some companies that it's worth it. I doubt there is much I can do to stop them. :-)

      Bruce

    3. Re:Apology to Corel by mrdisco99 · · Score: 1

      I think this just goes to show that having a big public voice like you do, Bruce, is a big responsibility. When you talk, everyone listens. That is, of course, a sign of your credibility and a result of your accomplishments. However, that could also be your credibility's worst enemy. You've done a lot to further the cause of free software, and we respect you for that. However, it's not us you need to impress anymore. You're becoming a major player in the software industry, and with that comes the responsibility of knowing that everything you say in a public forum is a press release.

      --

      +++
      NO CARRIER

    4. Re:Apology to Corel by FPhlyer · · Score: 1

      I think that everyone needs to keep some perspective here. Slashdot is more of a forum than it is a "hard news" site. At the rate at which things get posted to Slashdot, it is easy for something like this to make it through.

      In this case, Bruce posted something ONLINE which he never intended to have leaked to OUTSIDE world. How many of us have posted something ONLINE that we would never say in "the real world."

      Most of us can "flame" someone on the internet, but we won't even return a sandwich that has mayonaise instead of the mustard we ordered.

      Let's give both Corel and Bruce a break on this one.

      --
      Brought to you by Frobozz Magic Penguin Fodder.
    5. Re:Apology to Corel by Bruce+Perens · · Score: 1

      Point taken.

    6. Re:Apology to Corel by Future+Linux-Guru · · Score: 1

      In this case, Bruce posted something ONLINE which he never intended to have leaked to OUTSIDE world. When the thought bubbled up into his brain, he had the decision to keep it there, or to express it. Once he expressed it in a public forum, he became responsible for the effects it caused...wheresoever it might end up. As it is...this will be used by some detractors to show the confusion the community finds itself in. Perhaps not having one company control linux is good for coding...but it can be awful bad for PR.

    7. Re:Apology to Corel by fwr · · Score: 1

      Nick said:
      Good luck controling the damage on this, the thread so far is enough to convince many companies that it's not worth the trouble to go open source/GPL at this time.

      And Bruce said:
      Well, Nick, we have Red Hat stock at over US$200 today from its original $14. That is going to convince some companies that it's worth it. I doubt there is much I can do to stop them. :-)

      And I say, I agree with Bruce. While it may be "enough to convince many companies that it's not worth the trouble to go open source/GPL at this time" seems to be Nick's opinion, remember that it's exactly that, an opinion (just like mine). I was kind of shocked about the RedHat stock also, but a little digging shows that a Fool posted some articles that were referenced on the MS news section on Yahoo! after market close on Wednesday that basically regurgitated ESR's papers. Seems that the investment community, or at least a "new" part of it, is taking a look at the whole open source thing and, may be, really understanding it...

    8. Re:Apology to Corel by Gery · · Score: 1
      A good point.

      The higher you get, the harder you fall...

      Try to use a pseudonym and use your name more as a trademark - companies also often use pseudonyms to try things out and "relaunch" them with their trademark if they succeed.

      Anyway, live a good live, Bruce.
      ------------------------------

      --
      The answer is yes, me.
  36. Idea for Slashdot by Spirilis · · Score: 1

    Now I know this could turn into a heated "should-not-have-ever-been-idealized" idea, but could it be possible for Slashdot admins to take away articles/threads after they've been posted? Like keep them in the archives, but not let anybody see them any more... Because sometimes when you speak too soon, it'd be nice if you had some way of recovering from the matter. Although... maybe this isn't such a good idea.

    --
    the real at&t mix
    1. Re:Idea for Slashdot by mwillis · · Score: 1

      Not really worth it except in extreme circumstances. Certain noisy people would go ballistic, and make all sorts of negative statements about Hemos and Taco being censors and later it would boil down to a comparison with Hitler and a soon enough, a gun debate would ensue.

      That being said, there have been comments that were taken down, like the horribly cruel things said when R. Stevens died (the worst of the filth seems to be permanently below threshold).

      I personally like the update comments that accompany a story with new info. It works well enough, and avoids tons of people flaming Taco and Hemos for arbitrarily closing a discussion.

  37. Re:I'll chill out, and gratuitous Simppsons ref. by Griim · · Score: 1

    Still, I think it's a Good Thing you did this. Sometimes Marketing/Lawyer drones don't understand anything else. Kinda like the dog in Simpsons.
    "blah blah blah SIT!"
    "blah blah blah LAWSUIT!"

    Maybe they'll *read* the GPL this time. Who knows? :)

  38. Flaw in the 'Must be 18'! by DanaL · · Score: 2

    There is one little flaw in the 'Must be 18 so they cannot agree to the GPL' argument...plenty of software is sold to minors under various lisences. I bought DOS and a couple of compilers when I was minor and even though there was a EULA, no one asked me for ID. When I bought WordPerfect from Corel, no one checked to see if I was of age. Why are they treating their Linux differently? I've downloaded browsers by clicking on 'Yes I agree' buttons, never asked if I was 18.

    (Side note: does that then mean my little newphew can make illegal copies, and de-compile games because he cannot be bound by the EULA?)

    Dana

    1. Re:Flaw in the 'Must be 18'! by Plasmoid · · Score: 1

      Can he legally copy games?
      No. Doing so would violate copyright law.

      Can he decompile games?
      Yes. Nowhere in copywrite law does it say. You cannot decompile programs. What he does with the output might or might not be illegal. But the act of decompiling is legal.

      --
      You don't exist. Go away. --SysVinit Halt
  39. Whip them!!!!!! by John+Scott · · Score: 1

    Theyve gone too far now... Corel wants to turn itself into the new Microsoft. Theyve abused the goodwill of the Linux community, insulted all that GPL stands for, and ripped off the poor sods who bought their dist. DOWN WITH COREL NOW BEFORE ITS TOO LATE!!!!!!

  40. Bruce, that makes no sense. by Roberto · · Score: 2

    What Corel is doing, is that they are NOT giving binaries to anyone under 18.

    The GPL does NOT say that you have to give binaries to anyone who asks you. It simply says that if you give them binaries, you have to give them source.

    Now, As long as you are 18, you can get binaries from Corel, and you can also get sources from Corel.

    In what specific way are they breaking any license?

    They are just not redistributing their GPL-based product, which is a long stablished right: consider in-house packages based on GPLd code.

    Further, does Corel say that if you are over 18 and get their package you can not give it to a minor?

  41. Re:Slashdot's irresponsible "news" reporting by sirkut · · Score: 1

    As a gaming journalist I have to agree with you on this, but also I think /. was just trying to let the people know what is going on here.

    It's one thing to have a discussion on the implications of the EULA... But when you have Bruce making statements screaming LAW SUIT, LAW SUIT... I think there is the big problem.

    /. was just reporting, blame the horses mouth for creating the havoc.

  42. The contract law thing is irrelevent. by Anonymous Coward · · Score: 1

    All that is relevent is that our community has certain rules. Corel's license agreement is not acceptable by our rules; if our rules mean anything, then we cannot allow Corel to break the rules while operating under our blessing. You talk about minors entering into obligations? Corel entered into an obligation, too... if they can't handle the fact that free software means free software (as in freedom, not just gratis), they should never have jumped on this bandwagon. We never claimed to be anything other than revolutionaries.

    It doesn't matter if minors can't be held by legally binding software licenses. Non-minors can't be held by those licenses either! It doesn't matter if taking a stand on this issue would harm our acceptance by the business community. I'm not writing free software for the business community. (I have this image of Dr. Frank N. Furter telling Janet Weiss, "Well, I didn't make him for you!") I'm happy if they get some benefit from the free software I write for other reasons, but it doesn't really matter to me whether business uses it or not.

    What does matter is that everyone with a brain, regardless of trivia like age, is welcome to participate. That inclusion, specifically as applied to people's ages, is the top reason for my involvement in the free software movement. It's fundamental to what we're all about. If the business community can't handle that, I don't want them. If you would excuse it away on the grounds of antiquated contract law, then I don't know which team you're playing for, but it's not the same one I joined.

    I agree with Bruce's original, extreme stand, before he toned it down.

  43. Re:Slashdot's irresponsible "news" reporting by BDaniels · · Score: 1

    Hey, easy on /.

    Bruce posted this on his vanity site (technocrat.net). It's now been removed, but the lead item there was him calling for a lawsuit.

    /. picked the story up and now Bruce wants it all
    to be forgotten. Well, grow up. You can't go around threatening lawsuits and then say you were only kidding. Don't blame /. for repeating your hot-headed announcements.

    Call the police on ESR, call a lawsuit on Corel, Bruce really needs to relax a bit. The Linux community does not need the bad press this sort of shooting-before-thinking creates.

    --Brian

  44. All of you - Get a grip! by sarkeizen · · Score: 1

    There's no reason to get lawsuit happy *or* to say that this is the "end of linux" or to advise people to "go back to NT". Such extremism is unwarrented.

    The "under 18" was obviously a boilerplate legal thing. Even if they won't remove it. It isn't against the GPL and affects a fraction of the community.

    Why is it that half of you act like tightly coiled springs just waiting to rag on someone? All we need right now to make this paranoid fantasy complete is for the opportunistic John Katz to write an article about it.

    So instead get a grip, take a nap, have a long talk with your therapist (this means you Mr. Katz). Sometimes the lack of maturity here ticks me off.

    1. Re:All of you - Get a grip! by thenerd · · Score: 1
      I can see it now... Geek Kids Under-Represented In The Post-Corel Era

      from the Geek exclusion department

      After the Columbine disaster... (blah)

      Now a new age has dawned - we are now in the post-Corel civilisation. This is an age in which Geek kids worldwide have been discriminated against. One report from a Geek kid who did not want to be named said: "I am really nervous about the situation. I don't know where to turn. I feel excluded. I feel repressed." Many wired kids have found... (blah) post-(blah) age, geek kids, (blah).

      But, seriously... It is inevitable that in the 'clashing' of two completely different cultures - one of NDA's, complex licensing, 'enterprise class solutions', and the other of hard graft, freedom, and just making it work, that there is going to be problems. Sadly for poor Bruce, this may not be the first as other companies start to adopt a solution that neither cripples them financially or technically. thenerd. The camels are coming.

      --
      The camels are coming. I'm in love.
  45. Changes on http://linux.corel.com???? by FPhlyer · · Score: 2

    Just wanted to let everyone know, I pointed netscape over to corel's linux site and guess what?? The html is there, but it brings up a blank page. I have a feeling that Corel is gearing up for an apology (or explanation) for their EULA.

    --
    Brought to you by Frobozz Magic Penguin Fodder.
  46. Re:Changes on http://linux.corel.com???? NO! by FPhlyer · · Score: 1

    Okay. I was wrong.

    --
    Brought to you by Frobozz Magic Penguin Fodder.
  47. Re:Slashdork jumps the gun, again. by dmacon · · Score: 1

    hehehehe... this was a lot of fun though.

    Well slashdot isn't exactly famous for it's thorough journalism :-) But that's just part of the charm, it teaches us to think for ourself.

    It was kind of exciting though, the possibility of lawsuit and everything.

    --
    -- Tov Are Jacobsen
  48. Where's Justin when we need him? by Nexeslad · · Score: 1

    Hey Hemos, take an example from Justin. When you make a mistake, you admit it. Slashdots making a few too many lately and its time they became more careful before they hurt some one.

    --
    Do not wright in this space.
  49. Re:Slashdot's irresponsible "news" reporting by platypus · · Score: 4

    I agree with you, slashdot this was one of the occurences where slashdot has to decide whether they want to be pure journalists or journalists with a positive relation to linux/opensource.
    If they decide to be the latter, they should have rechecked this, because bruce seemed to be a little too fast in this case.
    But this shows that one has to doublecheck what he posts in public/semi-public forums, cause there's _no_ privacy.
    That was Bruce's fault and could have led to a zdnet headline without slashdot.
    OTOH slashdot shouldn't have been the first to carry this in the public.

  50. Of course, the important question is... by IMarshal · · Score: 1

    Is Bruce Perens over 18?

    1. Re:Of course, the important question is... by Rogain · · Score: 1

      Are you developementally over 0.18?

      --
      The current Slashdot moderation system is made by gay communists!
  51. Re:WTF??? by Daverz · · Score: 1

    The GPL does not allow such restrictions. Period. If you must have such restrictions in your license
    then don't derive from GPL software.

    FreeBSD
    would probably have been a better choice for Corel, but they probably wanted to ride on the Linux hype wave.

  52. Stupid? Corel license paradox by Empty+Sands · · Score: 1

    Seems a bit stupid to me that Corel have written a EULA that requires a person to 'click-sign' to the effect that they are older than 18. We are assuming that they have written this because you cannot sign a binding contract if you're a minor.

    So an under 18 year old downloading the software can't 'legally' agree to the EULA anyway.

    Too me this seems somewhat of a paradox.

  53. Screw Corel! by Mojojojo · · Score: 1

    Man, everyone says that it's because you have to be 18 to enter a legally binding contract. That's all well and good, but a minor can go buy windows without this restriction. It seems to me that through all their little foul-ups that they're trying to own Linux in the end. I hear a lot about how much they've given to Linux, but that's a load of crap too. All I've seen is Word Perfect, which isn't worth a shit anyhow. It's got its own printer drivers that futher confuse its crappy program. I see much more promise with Abi-word (despite bullets ;). Corel seems to have too much of an alterier motive with Linux. They can't beat MS with Dr. DOS, so they're going to try and cash in on Linux since its bound to take over. Also, outside of some pretty backgrounds and a modified kfm (K File Manager) and a gui install, they're just like any other distro. RedHat doesn't require you to be over 18 to download it. I've never understood everyone's excitement over Corel. They haven't offered anything good. They bought Dr. DOS and WordPerfect after DOS and WordPerfect weren't cool anymore (not that dos ever was). I dunno, they suck.

    1. Re:Screw Corel! by Pierce · · Score: 1
      Man, everyone says that it's because you have to be 18 to enter a legally binding contract. That's all well and good, but a minor can go buy windows without this restriction.


      I'm not certain, but it might have something to do with Corel being a Canadian company and MSFT being a US company. There could be different requirements and restrictions.


      All I've seen is Word Perfect, which isn't worth a shit anyhow.

      There's the work they've been doing with WINE as well. In addition to helping promote and adopt Linux when other companies were still "on the fence" taking a wait-and-see approach.

      They can't beat MS with Dr. DOS, so they're going to try and cash in on Linux since its bound to take over.

      Dr. DOS? I think you have the wrong company. Corel has never developed an operating system before. They have had an interesting history though, check out a book called "Random Excess" if you're interested.

      They bought Dr. DOS and WordPerfect after DOS and WordPerfect weren't cool anymore (not that dos ever was). I dunno, they suck.

      No, they didn't. Caldera still has Dr. DOS and it's doing rather well in the embeded space from what I've heard. IMO, WordPerfect is hands-down the best word processor there is, the only problem is that I seldom have a need for a word processor anymore..everything is usually typed in email.


      Wayne

  54. Out of Control by MrEfficient · · Score: 1
    This is an excellent example of how quickly things can get out of contol and blown out of proportion on the internet. Bruce Perens made a half cocked statement about a lawsuit against Corel. He has since admitted that this was a rash decision.

    What bothers me is that slashdot even posted this. I've never seen such a low quality post on slashdot before. I agree with the earlier comment by someone who said that posts like this should removed from the main page and archived instead. I just hope the mainstream media doen't get ahold of this. It really makes the Linux community look bad in my opinion.

    --
    Check out AbiWord.
  55. Normal reactions by Jonas+�berg · · Score: 3

    This seems to be the way our community works now that we have "news" agencies such as Slashdot to focus our attention to specific issues. You're busy hacking for 12 hours and when you return to the world, perhaps looking quickly at Slashdot, all hell has broken loose. I trust Bruce, RMS and others to handle these situations perfectly well and there's no need for me to get particularly upset about it. I'd rather spend my energy on writing free software instead, wouldn't you?

  56. Can we add an update to the main page? by sugarman · · Score: 1

    Seeing as Bruce has commented on his words in this column, can someone add ad update to the main page so that people don't think we're going to be sitting at Corel's doors with torches and pitchforks this evening?

    Just a thought.

    --
    --sugarman--
  57. Contracts and Minors by youngsd · · Score: 2

    I am a lawyer, but what follows is off the top of my head; don't quote me and don't rely on this as legal advice.

    My recollection is that the general rule regarding contracts entered into by minors is that they are not void but are voidable. This means that minors can decide, after entering into an agreement, that they no longer want to be bound by the agreement. They are released from their obligations under the agreement, but they also give up any rights and benefits they obtained under the agreement.

    That means that Corel doesn't have any legitimate reason to be worried about minors downloading their distribution. If a minor decides to void the EULA, the minor loses the rights granted under the EULA. At that point, the distribution is covered by background copyright law, so the minor is not legally permitted to copy the distribution. Only the EULA gives someone the right to copy the distribution. It makes sense, really. If the minor agrees to be bound by the EULA, the minor is permitted to do all of the things that Open Source is all about. If the minor rejects the agreement, the distribution is protected by copyright just like any other software.

    I don't think Corel has any justifiable reason to be worried about minors downloading their distribution. And, of course, even if they did have a good reason to be worried, they do not appear to have the right under the GPL to add this clause to their EULA.

    -Steve

    --
    Democracy is a poor substitute for liberty.
    1. Re:Contracts and Minors by fReNeTiK · · Score: 1

      Moderator!
      Please give this post a couple of Informative ratings. Even if it is not to be taken as legal advice ;)
      --

      --
      I strongly believe that trying to be clever is detrimental to your health. -- Linus Torvalds
  58. this article should be deleted!! by iso · · Score: 1

    okay, i love slashdot, been reading it for years, but the posting of this article isn't just Bruce's fault.

    this article should be deleted. there are many people who read slashdot, but don't bother reading the comments (effectively). they'll jump to conclusions. not to mention the fact that Corel will be very pissed off (as they rightfully should be) when they hear about this.

    perhaps its setting a slashdot precidence, but i don't care. please guys, DELETE THIS ARTICLE. and next time you decide to print somebody's email, ask them first if they want it printed! i can't believe you just posted Bruce's email from an obscure debian mailing list and made it a slashdot headline! does anybody else think this was stupid?

    - j

    1. Re:this article should be deleted!! by fReNeTiK · · Score: 1

      i can't believe you just posted Bruce's email from an obscure debian mailing list and made it a slashdot headline!

      Ok, I agree it wasn't a good idea to post this story. The damage is done. But what's the problem with his email address? firstly, he has a slashdot account with the email in it. Anyone can check this out. Then, if you go to www.perens.com, there's a nice link where you can download his VCard It's not as if it were a big secret, no big deal.
      --

      --
      I strongly believe that trying to be clever is detrimental to your health. -- Linus Torvalds
    2. Re:this article should be deleted!! by iso · · Score: 1

      urhmm..what? i never mentioned that it was a problem to post his email address. i only stated that it was an issue that they re-created his email without permission.

      - j

    3. Re:this article should be deleted!! by fReNeTiK · · Score: 1

      ah sorry... I misunderstood, that's all.
      --

      --
      I strongly believe that trying to be clever is detrimental to your health. -- Linus Torvalds
  59. Know what i find intresting? by SgtPepper · · Score: 1

    They don't seem to care about your age if you download the source :)

    1. Re:Know what i find intresting? by jacobm · · Score: 1

      So perhaps we're misinterpreting the whole thing! Maybe they just threw that stipulation in there so that the young'uns would learn to use programming development tools like make!

      Calm down, everyone, I figured it out. Corel is trying to give back to the community by encouraging under-18 Linux hackers!

      =)

      --
      -jacob
  60. GPL isn't universally applicable.. :-( by xmedh02 · · Score: 1
    Perhaps more troublesome is that GPL (and other free licenses) could be fairly problematic in certain legal systems, namely european continental (read: non-british) law, which normatively orders to have certain things even if you disclaim them.

    For example, the disclaimer of warranty could be a problem, GPL isn't good enough as a contract in some legal systems, the author cannot agree to have no compensation for his work, gift taxes problems etc.

    I am no lawyer and don't know much about other countries' law, but at least here in Czech Republic the GPL is fairly problematic. (See here, sorry, in Czech only.)

  61. Another More Serious Problem. by the+eric+conspiracy · · Score: 5

    It seems to me that the Corel EULA has problems in addition to the 'minor' business. In particular this little gem:

    B. PROPRIETARY RIGHTS:

    All right, title and interest in the Software Programs, including source code, documentation, appearance, structure and organization, are held by Corel Corporation, Corel Corporation Limited, and others and are protected by copyright and other laws.


    How can Corel just paste in something like this? They don't own any such rights to the bulk of what constitutes Corel Linux. To pass through something like seems to me to be an indication of total lack of clue.

    1. Re:Another More Serious Problem. by rantenki · · Score: 1

      held by Corel Corporation, Corel Corporation Limited, and others...

      IANAL, but i see nothing really wrong with this statement, since some of the software is owned by corel (some small part I am sure) and the rest is owned by others (Debian, KDE developers etc...), licensed under the GPL. Shouldn't be a problem.


      The lawyers for the FSF have doubtless spent a great deal of time proofing the GPL, so we are unlikely to find any major flaws under cursory examination here (not that it would be impossible).

    2. Re:Another More Serious Problem. by bem · · Score: 1

      How is this a problem?

      Linus, Alan and the rest of the kernel developers certainly do own the copyright (ie, the "right, title and interest") in the kernel. XFree86 owns the copyright on much of the X code, The Open Group owns the copyright on a bunch more of the X code. All of them fit in the "others" category above.

      And most importantly, the rights of all of them (and all the other individuals and organizations contributing to Linux) -are- protected by copyright.

      One of the ironies of the copyleft is that it acheives its power because of copyright law. Were it not for the protections of copyrights, the GPL would not be enforcable.

    3. Re:Another More Serious Problem. by Wodin · · Score: 1

      I also thought about this when I initially read the license, but then I noticed the "and others".

      They are not saying they have the rights to all the source etc. They are just saying that all the source code etc. is copyrighted. (Some by them, and the rest by other people/organisations.)

      --
      -- Wodin
  62. The Ability To Be Human by Kostya · · Score: 1

    Ok, it might be time for everyone to stop and think on what it means to be human. I would suggest the following two points:

    1. Making mistakes
    2. The ability to rationally think through a problem

    The first one applies to Bruce--to ALL of us. We all make mistakes. Often. Many times. To inifinity. Each and every day. That's part of the reason we love Open Source--it gives us many ways to compensate for making so many mistakes in an average day! :-) So cut Bruce some slack. I appreciate him stepping forward and admitting being wrong. That shows character. It takes a lot to admit your wrong. It takes even more to admit it to the large crowd that is Slashdot and the linux community at large.

    The second point is for all of you who immediately jumped the gun on this. You know who you are. When I saw this post, the first thing that came to my mind was, "Ah, Bruce." That is not an insult to Bruce, but an understanding of his passion. I'm a passionate guy too--we passionate people tend to overreact and act before fully thinking through our actions. So when I saw this post, I thought back to the Bruce Perens I have come to know over the past two years in conferences and news stories and I thought, "I'm sure this isn't the last word." Thinking through tough, emotionally-charged situations like this is something the ENTIRE community needs to grow in. Perhaps the more "calm" (I don't want to say passion-less--they are just better at separating emotion from the moment) folk in the community can serve as a balance to the passion that this community seems to have no shortage of.

    Everyone just cut everyone else some slack and be calm. Grace would be a good characteristic to show in this situation.

    --
    "Doubt your doubts and believe your beliefs." -- Switchfoot, Ode to Chin
  63. Parser error! by Bald+Wookie · · Score: 2

    Man, I must need more caffiene. Am I the only one who misread this sentence?

    can't download unless you're 18"

    Whoa, you need to be really well hung to use Corel Linux!

    No, but seriously folks. Lets not go off half cocked on a (USA centric) holiday weekend. Obviously Corel's legal staff needs some clues. The standard boilerplate just isn't going to work alongside the GPL. A lawyer who is trusted by the community and a master of open source legal issues could make a killing right now. Corel really needs an expert on their staff. On the other side, the Free Software community needs to politely and firmly correct them. Keep the lawyer on speed dial, but don't make it the first button you hit.

    They need to be given some time to be able to resolve the issue and explain themselves. Have they made a statement? Hell, linux.corel.com is 404ing right now. The power of the Internet may be rapid communication, but evicerating a company over a long weekend is not its best use. Personally, I'd rather not force them into making hasty decisions about matters of legal importance. Lets give their semi-clued lawyers a day or two to figure things out and make a statement before heading to Canada with pitchforks and torches.

    -BW

  64. ...and others.... by Chuck+Chunder · · Score: 1

    It isn't claiming that Corel owns the rights to the bulk of it, everyone else is merely covered by the "and others" bit.

    Basically it's saying that the people who own the various bits of software have their rights and interests protected by laws.

    Who'd a thunk it?

    --
    Boffoonery - downloadable Comedy Benefit for Bletchley Park
  65. massive pornography! by VAXGeek · · Score: 1

    I think we all know why Corel is withholding their distrobution from minors. Instead of playing Tetris while you install, Corel Linux connects to pr0n.corel.com and streams you live pictures of nekkid dancing penguins. Minors beware!

    --
    this sig limit is too small to put anything good h
  66. Not Another More Serious Problem. by Tony · · Score: 1

    All right, title and interest in the Software Programs, including source code, documentation, appearance, structure and organization, are held by Corel Corporation, Corel Corporation Limited, and others and are protected by copyright and other laws.

    I think we're the "..and others..." Corel isn't claiming copyright; they're just saying that the code is copyrighted, and Corel owns part of that copyright.

    --
    Microsoft is to software what Budweiser is to beer.
  67. Its all moot by BigDaddy · · Score: 4

    Frankly, the whole issue is moot. Here is why: 1. If one is 18+ yrs old, then the clause does not apply to him or her and that person can download the software with both a clear conscience and a legal right to do so. 2. If the person is less than 18, the agreeing to the contract is pointless because a minor cannot be held responsible anyway. In either case, the clause serves no purpose because either it doesn't apply because of age, or because of age, the responsibility is negated. This is not to say, that I support Corel. I think they were wrong to add this clause. But I think the real point is being missed. The question is not why are minors being licensed, but rather, why is anybody being licensed? Each individual piece of software has its own license. Be it GPL, BSD, or Corel. Why included the EULA at all?

    --
    You can't get a blue screen on a black and white monitor.
    1. Re:Its all moot by Tim+Pierce · · Score: 1

      I believe this is correct. If the reason that Corel added the "not a minor" clause to their EULA is that minors cannot enter into contracts, then they might as well have added a clause that said, "I am legally able to enter into this contract." Like the liar who always says he tells the truth, this is a meaningless clause -- what is to prevent a minor from signing the contract with or without this clause? It is still not binding.

      The whole issue seems completely bogus. I don't trust the conventional wisdom.

    2. Re:Its all moot by Chandon+Seldon · · Score: 1

      Just having "I agree to the licences for all the included software programs" above "Yes" and "No" buttons would probably have caused them less problems than an EULA.

      --
      -- The act of censorship is always worse than whatever is being censored. Always.
  68. Re:here they come. nail in the coffin by Gedge · · Score: 1

    Bruce,

    It's not worth replying to flamebait AC's like this.

    I think if nothing else there is going to have to come a time where the line is drawn and these companies are given a clear message that the GPL is not there to be stomped over whenever they feel like it. This sort of thing has to be dealt with otherwise it will only happen more often.

    Perhaps this is the time, perhaps it isn't. It's got to be Debian's call.

  69. Karma Inflation by LL · · Score: 2

    Bruce Perens wrote
    Besides, I don't have Ulitmate Karma on Slashdot. Sig11's is higher than mine (I just happened to look at his user record a while back), probably other people as well.

    Well, IMHO the absolute karma becomes rather meaningless after a while. I think what is more important is the relative karma/post ratio, ie some sort of median of how often your score goes up relative to the postings you make per week. I suspect people goes through a number of stages, initially posting lots to get the +1 bonus. Then more strategically (e.g. very early on in the thread to get noticed early) to race against the competition in running up your karma. Then I suppose the boredom stage sets in or your time runs out when more important things intrude in your life like an SO.

    The biggest problem is that because you can create unlimited karma, the whole process gets out of control (can we say unbounded feedback loop?) and the whole system becomes inflated beyond recognition. To paraphrase Peter Drucker's saying that governments only do two things well, wage war and inflate the currency, I'd toss in the contention that /.ers only do two things well, initiate flamewars and inflate their karma :-). Don't know what the solution is, perhaps introduce a new rule that once your karma reaches 100 (tribal elder status?) you can moderate at any time and simultaneously post iff you're willing to sacrifice your existing karma. The alternative is to make sure that karma moderations on average sum to zero (or 1) (more difficult) so that people have an equal chance of going up/down and that the total karma doesn't tend to infinity and thus become overinflated (and thus devalued).

    Ahhh ... the fun of designing a social currency.

    LL

  70. Shameless ploy by scumdamn · · Score: 5

    I think the whole thing is a ploy by Bruce to get Karma points ;> He got four for just apologizing!

    1. Re:Shameless ploy by Chandon+Seldon · · Score: 1

      Not four, six =P

      --
      -- The act of censorship is always worse than whatever is being censored. Always.
  71. Bad Slashdot, No Scoop-y Snack! by Greg+Merchan · · Score: 1

    This was a rather nasty thing to do. As Mr. Perens has already stated, he did not intend for the email to be posted to Slashdot. Couldn't somebody have, as a courtesy, checked with him before this went up? Even if only to make sure that he was really the one that sent the message?

    There were 11 follow-ups on the Debian mailing list last I checked and then I reload Slashdot to find nearly 100 comments already posted to this article. I think it took a total of 30 minutes for all of this.

    Will Slashdot be changing from green to yellow? This kind of sensationalism within the community only hurts us. I first started reading Slashdot early this year and in that short time I've been here the tone of the articles has gone from 'Stuff that matters.' to that of the mock page 'Stuff that splatters'. Not entirely, of course, but the average is moving that way.

    Maybe there should be some sort of flag system for articles. As an over-simplified example, good vs. bad news. New advances, project completions, et al. are good. Censorship, legal action, things that Microsoft does are bad. Bad news seems to have five times the impact as good news, judging from what I recall of comment counts. If there aren't five times or more 'good news' articles, Slashdot becomes the hive of raving lunatics that other news wires think it is.

    Perhaps a survey of articles should be done. Maybe weigh the value of an article by the number of comments and their moderation points. It would probably be best to exclude funny moderations. Then classify the articles according to a flag system and see what is most beneficial to us. Hell, that could probably be the start of a doctoral thesis in something.

    I don't mean to say that 'bad news' is unimportant or should be ignored. But since bad trends are more important than bad events, perhaps the reporting should reflect that. Somethings are urgent ('Congress voting on suprise bill tomorrow' et al.); but most bad news isn't really new, it's the same-old-**** in a new form which indicates that there is a more fundamental problem that hasn't been addressed.

    Darn it, my fingers are starting to hurt. Ciao.

  72. Re:o/~ it's a small world (net) after all o/~ by Money__ · · Score: 1
    Bruce, You have that Madona thing happening now.

    If you burp, it'll make the news.

    So be carefull where you burb.

    It's a small net, and your words get around fast.

    Kudos to /. for informing the public.

    and Bruce, let's be carefull out there.

  73. Re:The EULA is perfectly legal by youngsd · · Score: 1

    Boy, am I glad I put all of those lawyerly disclaimers in my post. I went back and looked at what Corel did, and it does appear that you are correct.

    The gist of this is that anyone (over 18) who downloads the Corel distribution is free to distribute the GPL components of it to anyone (regardless of age). As you note, Corel is not prohibiting downloaders from distributing GPL programs to anyone.

    Until I am once again informed I have overlooked the obvious, I agree with you.

    :-)

    BTW - I still think I am correct that Corel has no legitimate reason to be worried about minors downloading thier distribution.

    -Steve

    --
    Democracy is a poor substitute for liberty.
  74. ugh. poor Corel by rikek · · Score: 1

    I'm beginning to feel very sorry for Corel -- They want to be able to offer a bunch of services to the linux community, as well as broaden linux's acceptance as a viable operating system (yadda yadda, you've heard this all before), but they're getting hit left and right by technicalities in licensing agreements. I suppose somebody can argue against me here, but isn't this why we have the BSD/GPL/Etc all in the first place? Not to intentionally stuff words into anybody's mouth, but programmers who are working for free just want to be saved from the hassle of writing up something to protect their code, and I am beginning to think that all these issues will be extremely destructive to the concept of linux by linux users themselves. I know that this certainly dropped my respect for Bruce Perens quite a bit. Good luck to Corel's overtaxed legal team as they try to find a way around this.

    1. Re:ugh. poor Corel by TrentC · · Score: 1

      I suppose somebody can argue against me here, but isn't this why we have the BSD/GPL/Etc all in the first place?

      Part of Corel's problem is they're (unintentionally or not) running up against exactly what the GPL prevents them from doing.

      They can't prohibit destribtution of the "Developer Preview" Linux distribtion outside of their developer pool; the GPL forbids it. (Well, more precisely, they can prohibit the distribution of any non-free parts, but not anything covered by the GPL.)

      They can't prohibit "minors" from downloading their Linux distribution (with the exception noted above); the GPL forbids it.

      I am beginning to think that all these issues will be extremely destructive to the concept of linux by linux users themselves.

      The problem is, you don't get exemptions from the GPL. If you're writing your own software and want to do something akin to the Mozilla Public License or Apple's Open Source(r) license, that's fine. But if you use software licensed by the GPL, you have to abide by the GPL's provisions. Period, end of story.

      Corel is apparently trying to figure how to build business based on a proprietary-software model using open-source software, and it's not working.

      I know that this certainly dropped my respect for Bruce Perens quite a bit. Good luck to Corel's overtaxed legal team as they try to find a way around this.

      You must have posted this during the period between Bruce's apology and the update on the main story; he didn't mean for his comment to be taken so seriously.

      Jay (=

  75. Corel, altruism, and licensing by Assistant+Madman · · Score: 1

    Being a Canadian (this doesn't, by itself, mean I'm more qualified to answer) I may have heard more about Corel pre-linux than others since it is a Canadian company. Over the years, watching one of the largest, if not the largest, software company in Canada, I have had a distinct impression that Michael Cowpland only supports one thing - himself.

    Corel has gotten creamed in the Office software department, losing miserably to MS Office. This is Corels big opportunity to get in on something great on the ground floor. If they can get their products ported and included in linux now, if it turns out to be the Next Big Thing, then they have the market, to some extent, cornered. I do not believe for one second that Corel and Michael Cowpland are supporting Linux out of altruism, or because they "believe" in it. It is for money, pure and simple, and if they can change the licensing without people suing them, they damn well will.

    Just my $.02 canadian,
    GC

    1. Re:Corel, altruism, and licensing by Pierce · · Score: 1
      I do not believe for one second that Corel and Michael Cowpland are supporting Linux out of altruism, or because they "believe" in it. It is for money, pure and simple, and if they can change the licensing without people suing them, they damn well will.

      Absolutely, but you are forgetting a few things.

      Corel needs to stay on the good side of the developers, or someone else will come along and fill the role for them. Sure they are ultimately after money, they are a public company after all. IMO, they might be having some problems, but do you really think any other company, having gone to the extent of using "OpenSource" software, wouldn't have run into the same problems? IMO, it would be smarter for Corel to want to use the current licenses, rather than try and make loop-holes. This would prevent anyone else from comming along later and using one of the loop-holes against them.

      Wayne

  76. Re:Apology to Corel (needs the BS removed) by BDaniels · · Score: 2

    You may not have expected that message to be posted to SlashDot, but you _DID_ put your "I'm not working with Corel any more and I'm thinking of suing" message as the first item on your site (technocrat.net).

    Now you've removed it from Technocrat and you're trying to make it sound like /. reposted a private email. Sorry, but that's BS. You posted it publicly, you even trumpeted it on your site, and you should have known that such a dramatic statement would draw attention.

    This morning you wanted the world to know. You regret your words now, fine. But you can't rewrite what happened to make it sound like you were victimized by /. Try taking responsibility for your messages _and_ your site.

    --Brian

  77. Lawsuits are inevitable unless we change course. by Brett+Glass · · Score: 5
    The GPL, by its very nature, creates conflicts between open source developers and honest businesses -- large and small -- by putting them at odds with one another. It doesn't take more than a few minutes' reading at the FSF Web site -- in which Stallman repeatedly issues a call to arms against "proprietary" software (i.e. software which one can make money by licensing) to see the antagonism. (His essay in which he renames the Library GPL the "Lesser GPL" is an especially good example of this attitude.) A movement whose focus is the destruction of people's businesses and livelihoods can only lead to a battle -- no, rather, to a war consisting of many battles and many casualties.

    Everyone -- businesses and the open source community -- would be better off if we adopted the win/win, "live and let livee" approach of other software licenses, such as the BSD license, the MIT X license, and the Artistic License.

    Open source that's reusable by all -- such as the BSD TCP/IP stack -- is responsible for the growth of the Internet and the success of the World Wide Web. Instead of threatening lawsuits based on overly restrictive licenses such as the GPL, we should say, "Use this code as you will. You can't un-publish what's already been published for the world to see, so you can't 'take' it; you can only use it to avoid tediously reinventing the wheel. Now, let's see what you can do wih it! If you do not choose to publish the source to what you build with it, good luck to you -- it's not easy to make a living that way. If you are good enough to do it you deserve success."

    Bruce, in the past you have had the strength and foresight to opt out of movements and groups which have become dogmatic and/or territorial. Perhaps it is time to reconsider your support of the GPL.

    It seems that the only thing that the GPL has done which less restrictive licenses have not is to alienate and hurt people. (The GPL hasn't "forced" the opening of any code; people who don't want to publish their source, such as Be, have merely worked around it or reimplemented the algorithms themselves.) It even appears to violate Point 6 of the Open Source Definition -- which you helped to write! -- by discriminating against a field of endeavor: the creation of software which does not happen to be open source.

    I realize that this would be a bold move, to be sure, but you're one of the few people I've encountered who has the guts to make it. Let's end the conflict, the bitterness, and the spite. It's time to get on with writing software, and to publish it in a way that quells conflicts rather than creating them. We will all be more productive, and happier, if we do.

    --Brett Glass

  78. Perens burps!!! by mtngrown · · Score: 1

    Lawyerclysm imminent!!! News at 11!!!

    One semi-hothead spouts off, 13 bazillion
    other buffoons jump in.

    Lot more talking than thinking going on around
    here this morning.

    Isn't peer pressure an awesome force? ;>
    Situations like this really point out the strength
    of the open sources (sores heh heh heh) community.
    Would Bill Gates listen to anyone telling him he
    was full of buffalo sh*t? Don't think so. So,
    BP gets a mouthful of shoe leather. Once he gets
    tired of the taste of pavement, he will think
    harder before speaking... ;)

  79. Well, on reflection- by Chris+Johnson · · Score: 2

    It's all very well to be calm and rational and reasonable. However, in the event of someone calmly and rationally taking actions to basically weaken the GPL by setting a precedent to alter pre-existing licenses on the grounds of convenience, I would calmly and rationally have their head for it :)
    More accurately, since I _have_ read the GPL, do have a reasonable idea of what it requires, and have released software under it based on my desire for my licensing terms to be _just_ _like_ _that_, I will calmly and rationally suggest that Corel not only has to either recant quickly or lose their permission to redistribute GPLed software, I would also suggest that this 'worsening of the signal to noise ratio' is harmful. It is harmful because the more this is allowed, the more will happen. I would suggest (calmly and rationally) that it is very much a bad thing that Corel is permitted to blunder in this manner. Their mistakes make it appear that the GPL isn't really a license, or doesn't really bind, or doesn't really mean what it says. Never mind that no commercial vendor would _want_ licenses in general to be questioned- that their own EULAs and agreements depend on the same respect for the wording of licenses- the reality is that for Corel's legal people and many other people in their position, 'some are more equal than others' if they can get away with it. And that's not something that can be encouraged.
    In other words: yes, somebody at Corel would have no problem with simultaneously arguing that the GPL doesn't really need to be taken literally, yet the Corel EULA _does_ need to be taken literally. Hence this confusion, and this problem. The central irony is this: in order for Linux to be properly protected, Linux has to _demand_ equal protection for its intellectual property under the law, and equal respect for its licenses. On the other hand, the people responsible for endangering this IP protection are the people who _most_ depend on it. The logical consequence is that Microsoft ought to donate huge sums to the FSF in order to fight Corel in court over the GPL, because then Microsoft is rid of Corel, and the GPL is finally tested in court and given the same protection as EULAs and such. It's nuts, but it's logical. Who better to protect the rights to IP than corporations? And what is this but a challenge by Corel (intentionally or not) that risks weakening the GPL's right to impose terms on IP? Calmly, rationally, this nonsense has to stop.

  80. When in doubt... by Graymalkin · · Score: 1

    blame Hemos!

    --
    I'm a loner Dottie, a Rebel.
    1. Re:When in doubt... by jdub! · · Score: 1

      I was of the understanding that by accepting the Slashdot EULA, that "when in doubt", one should blame CowboyNeal...

      Perhaps I'm just going off half-cocked. Certainly not a full 18".

  81. Give it a break brett. by mtngrown · · Score: 1


    BSD license is a fine license for many. Others,
    such as myself, prefer GPL/LGPL. In fact,
    given a choice of proprietary or BSD, I would
    pick purely proprietary. I am sure many others
    would do the same.

  82. once more? by Lazy+Jones · · Score: 1

    Why not just explain it to them one more time? It may be tiring, but it sometimes pays off to stay friendly.

    --
    "I love my job, but I hate talking to people like you" (Freddie Mercury)
  83. EULA: Non-Binding contract? by UnknownSoldier · · Score: 1

    I thought that for a contract to be legally binding it had to be signed in writing?

    Any lawyers in the house to answer this question?

  84. If licenses are unenforceable, so is this by Dwonis · · Score: 1

    The clause is actually quite moot in Canada, where that law applies, because minors cannot be held to the "I agree that I am under 18" clause. The only thing this clause does is cause problems for minors in other countries.
    --------
    "I already have all the latest software."

  85. Re:Wow, he's pissed! by johnburton · · Score: 1

    If somebody has written some software and kindly allowed people to package and distribute it under their own label for profit, then they have an absolute right to dictate the conditions under which this may be done. I corel don't want to, or can't meet those requirements they mustn't distribute it.

    --
    Sig is taking a break!
  86. License proliferation by maroberts · · Score: 2

    I did mention in this post that I couldn't see the reason for the proliferation of licenses. I still can't see why there are just a few standard licences that we're all familiar with. I wouldn't have to read the Norton License, the Mozilla licence, Corel license etc if they just simply stuck to one of the more common license agreements out there. I'm sure we could get it down to about 3-4 different licenses in the end. Another good thing about cutting down on the number of licenses is that we are more likely to get litigation which hopefully would validate these licenses in law courts i.e. create precedents. AFAIK, we STILL don't know if the GPL is legally binding and effective. As far as I can see, Corels' 18 year old license restriction would have little effect anyway; since minors can't be bound by licenses in Canada, the term itself is paradoxically invalid. It MAY be valid in other countries though.

    --

    Donte Alistair Anderson Roberts - hi son!
    Karma: Chameleon

  87. Wrong: Read the GPL by Dwonis · · Score: 1

    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.

    --------
    "I already have all the latest software."

    1. Re:Wrong: Read the GPL by jareds · · Score: 1

      So how are they sublicensing it? Refusing to distribute it to everyone isn't a sublicense.

  88. Re:Apology to Corel (needs the BS removed) by My_Favorite_Anonymou · · Score: 1

    Maybe Bruce has more intension to sue Corel than he now indicated. But the ultimate question is, what if Debian sue Corel, so what?

    Corel has been cutting GPL corners left and right. They are the ones who's putting it, whob know what's coming after that if they push one more hand. Exactly who is giving a shit about Corel anymore? In the win32 platform? Do you know aol is going to bomb american with staroffice with their CDs? Do you know how much AOL cd my little cousin has collected? 4 Aol5.0 and about 5,6 AOL 4.0. (She uses Netzero :)

    Who give Corel permission to be so disrepectful to GPL? If open source community can sustain a tiny law suit, then GPL is not a good license. I say sue them asses off. Use a law suit to clear up the shadom area.


    CY

  89. Re: Hey, minor doesn't mean bad person! by Bishop · · Score: 1

    You are correct about a minor acting in good faith. It is not law, but is common practice. "Common practice" means a lot in English Common Law as many of the laws aren't written down. In this case the law will generally look the other way. However if there is any damage caused, even if the minor was acting in good faith, then you have all sorts of trouble. The law was designed to protect against minors entering contracts that they could not fullfill. Under the Canadian Contract law minors cannot make purchases over $50. I have never heard of that being enforced. However whenever a contract is signed, say a damage waiver for paintball, the parent's or legal gaurdian's signature is required.

    Basically Corel feels that it must include this clause under Canadian Law.

  90. Re:Karma Inflation (leaving topic) by cdlu · · Score: 3

    Well...looking at the karma system I have an idea.

    All users with positive karma should always be allowed to moderate. But every time they moderate, they lose one point of karma. They gain it back, or lose more, depending on how well they faired at metamoderation.

    The only catch is that Signal 11's 270 or so karma points will be enough to moderate this entire discussion. :)

  91. Re:here they come. nail in the coffin by norton_I · · Score: 2
    I am generally anti-lawsuit, so I sure how I feel about this idea, but look at it this way. Linux was not created to be a huge corporate phenomenon. It was not created with the intent that everyone would use it. Nor was it created with the intent that people should be excluded. I am perfectly willing to let anyone play with my toys, as long as they play by my rules. The rules are simple: Let others play as well.

    Now, I believe that Corel honesty is trying to "do the right thing" and respect those rules, but is having a hard time getting used to our rules. If I thought that Corel was really trying to proprieterize Linux and other free software, I would be the first to sign up on a suit. A corporation that doesn't play fair is not welcome. As it stands, I am unsure. Their intentions may be good, that does not excuse their behavior.

  92. The license is at the root of the conflict. by Brett+Glass · · Score: 2
    I don't like debating licenses either. However, we must face facts: licensing is the root of the problem here. The only way to resolve this conflict -- and many others past, present, and future -- is to adopt a license which admits itself to fewer conflicts.

    Any license which requires a developer to give up the value of his work in order to adapt or adopt freely available open source will inevitably cause friction between authors of open source and those who publish software for a living. The LGPL, which you mention above, is far less extreme than the GPL in terms of what it demands. However, because it still attempts to appropriate the work of others (some would say "confiscate," though I think the term is a bit strong), it is problematic and subject to serious legal questions. And these questions will cause court battles. (I don't want to go into this in great depth here, but the most serious problem with a license that requires disclosure of modifications under the same license is that it is a "contract to execute a contract," which -- according to basic contract law -- is per se unenforceable.)

    I do not believe that many people are really so spiteful that they would withhold their code altogether, as you suggest above, just because someone else could use it to construct his or her own product. Apache -- which with 50%+ market share is arguably the most successful open source project of all -- has no problems obtaining code. And it uses the most liberal open source license of all -- in fact, it's a hair's breadth away from putting the code in the public domain.

    We will all have the opportunity to prosper as the base of code that's truly free grows. While Stallman, and others, attempt to fan the flames of petty jealousy, I am inclined to believe that most people will be able to see past this appeal to childish spite and pettiness and recognize that it hurts rather than helps. I believe that all programmers will ultimately come to recognize the benefits of universally reusable open source -- code with no strings attached. Let's start now by consigning the GPL to history and moving on.

    --Brett Glass

    1. Re:The license is at the root of the conflict. by fwr · · Score: 1

      Will you go away already! You say that "Stallman, and others, attempt to fan the flames of petty jealousy" and I ask who's jealous and what do they do that makes you jealous? The only logical answer is that you are the one that is jealous, because you can't use GPL code for your own profit, and the act that they are doing that "fans the flames" is producing GPL code and giving it to their "friends." Well, get over it! If you can't accept the GPL then don't use the code. You sound like Sun, wanting everyone to write code for you so that you can integrate it into your own products and license it back to people for a fee! Well, it isn't going to work. Begone already! Leave us alone!

    2. Re:The license is at the root of the conflict. by Waldo · · Score: 1

      "While Stallman, and others, attempt to fan the
      flames of petty jealousy, I am inclined to believe that most people
      will be able to see past this appeal to childish spite and pettiness
      and recognize that it hurts rather than helps."


      The only one fanning the flames here is you. Put down the gasoline and back away.
  93. Re:Apology to Corel (needs the BS removed) by My_Favorite_Anonymou · · Score: 1

    I mean If open source community can't
    sustain a tiny law suit, then ...
    and two other tpyo :)

  94. Corel has a weak defence. (IANAL) by Kartoffel · · Score: 1
    Argument 1: The GPL [does not|cannot|may not] apply to minors in Canada because they may not be held legally responsible. Corel is protecting the letter of the law and covering their backsides by not allowing minors to d/l their distro.

    Argument 2: Since EULA's of any kind do not apply to minors, (per Corel's arguement 1) it follows that 13-year-old Canadian warez d00dz are can't be held responsible for their actions either. Corel's logic here implies that even though warez kids break the licenses of the SW they pirate, you can't go after them. Let's compare a 13 year old downloading Corel Linux to one who distributes warez. Both kids broke a license. If one can't be held responsible, neither can the other. Oops!

    1. Re:Corel has a weak defence. (IANAL) by sandman71 · · Score: 1

      Actually, your thinking is a bit flawed.

      A warez d00d breaks more than just a license agreement/legally binding agreement/contract. It is illegal to make and distribute copies of software/music that you don't own. Piracy is a total separate issue than license agreements.

      A warez d00d only technically breaks the license agreement (cuz he's a minor) if he installs the software. If he doesn't, he's only guilty of owning pirated software.

      There's currently no software out there that prohibits you from purchasing it if you're a minor (there may be some, but I personally don't know of any). The license agreement only comes into effect when you attempt to install said software.

      So to follow your logic, a 13 year old warez d00d can be pursuited for owning pirated software. But he/she can't be pursuised for breaking the license agreement. Both are individual and seperate entities.

      --
      It's better to burn out than to fade away!
    2. Re:Corel has a weak defence. (IANAL) by sandman71 · · Score: 1

      Please excuse the bad spelling. Above should say pursued (or however it's spelled. Lack of caffeine will do that to a guy).

      I'd also like to point out that I did state prohibit from purchasing, as in a store (or online).

      Sandman

      --
      It's better to burn out than to fade away!
  95. Good way to shoot your karma to the star ;) by Le+douanier · · Score: 1


    1. Be called Bruce Perens or another proeminent Free Software/Open Source community

    2. Make a big mistake (hey, this happen to everybody), big enough that it get caught on /.

    3. Post 10 comments to apologize and explain why you were wrong... so you get moderated up for these explanations.

    Bingo, your Karma is much bigger than this morning ;)

    --
    "The obvious mathematical breakthrough would be development of an easy way to factor large prime numbers." Bill Gates,
  96. Re:Wow, he's pissed! by Dwonis · · Score: 1

    no he doesn't. depending on how the law (not corel's motive, but canadian law, which corel is SUBJECT to, and does not control) is interpreted, they may be REQUIRED to put such a clause in whether they want to or not! open source people should read into things before they open their mouths for their feet to enter....

    So you're basically saying you shouldn't have posted this until you actually checked out Canadian law and seen if it's actually required, instead of just speculating, like the rest of us are.
    --------
    "I already have all the latest software."

  97. You guys can't see the forest for the trees.... by Dktr+Jkyl · · Score: 1

    My stocks are going *up* (Corel, RedHat, etc...), I have a stable, configurable, excellent alternative to (b. gates' private parts are)Microsoft, and everyone gets to put their two cents into this entire Linux adventure. Great game, huh? OOPS! someone fouled - but I don't think it's the end of the GPL, Corel, or minors being able to download software (do you?). I have scoffed minor laws all my life and will continue to do so, as I expect will others. Corel isn't sending out the "catch-those-lying-minors-and-throw-them-in-jail" police. Don't worry, if they posted a standard form, they'll either remove it, or ignore it. If they think they can impose their will, they'll be unpleasantly surprised. The power of the computing community has finally overwhelmed corporate 'hugeness' - with Linux.

    --
    Without empty space there would be nothing...
    1. Re:You guys can't see the forest for the trees.... by PigleT · · Score: 2

      Yes, thanks for the pointer in the direction of normality!

      But.. it's not by sitting on one's communal derriere that we've got to the state of play where we can challenge corporations like that. Something needs saying, sensibly / rationally / presentably / pointedly, to Corel, with the weight of the community's backing behind it - then there's no excuse for them not to change it.
      They *will* *have* to change it. Not everything is got right the first time round, but I expect things to right themselves in time too.

      --
      ~Tim
      --
      .|` Clouds cross the black moonlight,
      Rushing on down to the circle of the turn
  98. Re:Being set-up? by Pierce · · Score: 1
    Does anyone get the feeling that Corel knows more about what they are doing than they lead us to believe? I wouldn't be suprised if this is all a trap to give Debian, Linux, GPL, and related things (opensource namely) a bad name in the media.


    No, but lately I'd be half-tempted to think about it the other way around. Corel has been getting screwed on Slashdot these days.


    Wayne

  99. hmmm I am running it and I'm 16 by browser_war_pow · · Score: 1

    They can bloody well go to hell for all I care if they think they can stop me from running it. If they try then back I go to redhat or hell.... I will just give the real debian a try.... not that pseudo-debian distro from corel. BTW corel's distro is pretty good... but it still needs work. The boot loader is pretty disgusting. I miss the BeOS bootmanager already.

  100. what about copyright by qha · · Score: 1

    Are minors required to follow copyright law? If I've understood this correctly the GPL gives you more rights than copyright law. So if you are a minor and don't want to agree to the GPL you instead have to follow (c)-law which is more restrictive.

  101. Corel has put a pretty face on Debian that's all by Rares+Marian · · Score: 1

    Corel is not the first order distributor for the distro. Debian is.

    Debian decided to put stuff under the GPL, therefore they cannot change it.

    As for /. jumping the gun, that's what /. is for a public discussion. This isn't a news wire, this isn't a chat room, it's a discussion forum. Just because everyone knows about it makes it no different than posting on USENET or a mailing list.

    "Computers should be ... tools... (siglim 120 chars)" Like cars... to the office no more no less.

    --
    The message on the other side of this sig is false.
  102. Re: Minors and EULA by gatekeeper-eu · · Score: 1

    It's all a matter of 'tortology'!

  103. Re:Lawsuits are inevitable unless we change course by Bruce+Perens · · Score: 2
    There's not a chance that I'll opt out of the GPL. Businesses have to realize that free software is something we share with them. Red Hat does just fine with this, other businesses have to learn how.

    Bruce

  104. Corel - Shoot youself in the foot dept. by gatekeeper-eu · · Score: 1

    A a retired CEO of a consultancy/VAR selling WordPerfect/Corel products and related services I was not amused by the Corel license on Linux, to put it very mildly. I have today written to Corel to express my concerns but as I do not have the purchasing power anymore, I suspect my critism will have no effect. I made the point that the 14, 15 and 16 year-olds of today are the IT directors of tomorrow. I would be very sure whose product I would NOT allow through the doors!

  105. Thoughts on Corel by PigleT · · Score: 2

    Hmmm.
    Good on you, I guess...

    Some thoughts from me: I downloaded and tried this last week, and was frankly disgusted. It took too long to boot into the GUI. The package selection was foul - clicking 2 levels of trees to find only one package where I *know* the real debian has masses. Then the worst insult of all - repartitioning. No, you can't assign a mountpoint to an existing partition, you have to delete and recreate it. No, when you recreate it you specify a size in megs and it uses that as the cylinder difference instead. Then it complains that there's not enough space to install your selected packages. Having gone through this rigmarole twice, at about 15mins apiece, the CD hit the opposite wall with a satisfying thud, although it still works (worse luck) - oh, and I posted to my favourite local Linux newsgroup with a flame of a review and forwarded a copy to the Corel feedback email address.

    It says it all that I've not even had an acknowlegement of the email I sent them, let alone the time I wasted one evening setting it all up.

    I *have* gone back to the real Debian, and intend to stay with it for a while - on both desktops (the home one has just been reinstalled) and my notebook.

    So as for these petty licensing derangements - Corel can indeed go to hell. I'm totally in favour of boycotting them, especially given what it says for the real debian.

    --
    ~Tim
    --
    .|` Clouds cross the black moonlight,
    Rushing on down to the circle of the turn
  106. In theory and in practice... by General+Jenkins · · Score: 1

    First off, IANAL. I do believe that GPL loopholes will have a significant influence on the direction taken by commercial Linux development and should be worked out by legal types. However, I also believe that falling back to legalease behavior will help neither the Corel situation nor GNU/Linux effort in general. In fact, it could have disasterous consequences.

    Lawsuits involving licensing issues in Linux development and distribution will put the GPL to test and set dangerous legal precedents for OSS. They could partition development and restrict the freedom of distribution that has always been the cornerstone of the GPL for commerce. And if the GPL stops being applicable to commerce, OSS stops being applicable to the free-market economies that determine what lives and what dies for the mainstream.

    BESIDES.

    There is a big difference between what the Corel license accomplishes in theory and in practice. Frankly, I see the term at the top in a lot of licenses I don't read. And It's the *only* one I see. I scroll past the rest and hit the big, friendly button. For most practical intents and purposes, it's meaningless. Corel can't tell whether the guy that clicks "Accept" is 90 or 14, and they don't care anyway until they see him in court.

    So, I say address the issue, but keep it out of court. Refine the GPL. Make sure that OSS has a very sound legal foundation. If it's good enough, you'll never have to use it.

    --
    -the gentleman general jenkins
  107. Re:Lawsuits are inevitable unless we change course by bkosse · · Score: 1

    Brett, you're an idiot. We all know you think the GPL is the most evil thing since communism (which is, itself, a load of B.S.), but your attempts at mincing words and being duplicitous ("would you Lynx authors please let me have your code, without any recompense to you, so that I can make lots of money writing software for blind folks") are *NOT* welcome here. Except that you've proven a distinct failure to grasp English during our "debates" (rather one sided, given your lack of reasonable discourse) on Infoworld, I'd continue pointing out how assanine your post is. Now GO AWAY! If *YOU* don't like the GPL, *YOU* *DON'T* *USE* *IT*. Sheesh.

    --

    --
    Ben Kosse
    Remember Ed Curry!
  108. Oh, read. by Roberto · · Score: 1

    They are not sublicensing.
    If they were sublicensing, you would be getting the software under a license that is NOT THE GPL.

    Here, you are getting it under the GPL, or you are not getting it at all.

    Now, the only place where they could be breaking a license is if the GPL would force them to give it to you, "you" being one specific minor, and they refused.

    Now. If you can show me a case for it, I'd happily agree they are violating the GPL.

    Please: I think the limit sucks. I think it is legal, too.

  109. Minors *are* covered by licenses by Morgaine · · Score: 2

    That's rubbish, because if it were true then minors wouldn't be bound by the licenses in shrink-wrapped games either.

    Now just go and ask games manufacturers whether their licensing binds minors as well. I don't think you'll find any disagreement or hesitation in their answers.

    --
    "The question of whether machines can think is no more interesting than [] whether submarines can swim" - Dijkstra
  110. Re:Lawsuits are inevitable unless we change course by fwr · · Score: 1

    Well said. I was going to post a reply like this but I just couldn't think of a way to respond without going into flame mode. The guy is so clueless that it's a waste of time attempting to respond. Just let the moderators handle it.

  111. Minors not legally binding, etc. by Kukuman · · Score: 1
    I'm 14 years old. I've been using Linux since I was 12, starting with Slackware 3.2. I'm much, much smarter about computers than most adults.

    By US law, I cannot be legally bound to contracts. That also means I could legally violate the GPL. But would I? HECK NO!

    In my mind, common sense comes over law. I would never, even take advantage of loopholes such as that, especially when it comes to GPL and the free software dogma. Basically, my karma did not, and will not, run over the dogma.

    Not like I would download or even use Corel Linux anyway...I'm happy with Slackware 7.0, thank you!

  112. Eliminating conflict by Brett+Glass · · Score: 2
    My comments weren't at all posted as flamebait. My goal in posting here is, in fact, to head off conflict -- the conflict we are sure to see as a result of the problematic provisions of the GPL. Our world is tumultous and chaotic enough; the last thing we need is to divide programmers into multiple warring camps.

    Alas, the FSF seems eager to do this. Via the GPL, it attempts to turn code into a weapon and set up a battle -- open source vs. closed source -- which need not be. The two can, and should, coexist gracefully and complement one another.

    The only way that this can happen, however, is if we eliminate licenses with so-called "copyleft" provisions. These provisions truly do discriminate against the creation of software which does not happen to be open source. This is a field of endeavor -- in fact, a whole industry. By discriminating against it the GPL truly does violate the Open Source Definition. What's more, as I've mentioned earlier, "copyleft" restrictions are almost certein be ruled unenforceable by any court, because by agreeing to them one is making a contract to make a contract (in fact, to make many contracts).

    The problematic provisions of the GPL stem from author Richard Stallman's having declared war on the very concept of intellectual property -- the coin of the realm in the electronic age. But no one bemefits from war. What we need instead is a positive, cooperative, synergetic relationship between open source -- truly open source -- and closed source. Between free sharing and the fundamental needs of creative people to be compensated for their work. The incident we see here is just one of the many possible problems we can avoid if we return to the classic, unencumbered form of open source that was pioneered at MIT and Berkeley long before the GPL.

    --Brett Glass

    1. Re:Eliminating conflict by Menthos · · Score: 2
      To me, your comments make absolutely no sense.

      I think that there's no "conflict between licenses" in the first hand. The BSD-stylish licenses and copyleft licenses (à la GPL) can coexist gracefully. Each of them has their own purposes, goals, and it's up to each developer to choose a license that fits them.
      You say too that they can, and should, coexist gracefully. But in the next sentence you want to "eliminate" all copyleft licenses??

      Let me ask why copyleft discriminates open source? Copyleft is just "hey, here's the code, do what you want, but let it be free, just like it were to you". I don't think that's discriminating. If you find a piece of code that you want to use, you have to accept the rules before you use it. In this game, the rule is the license. If you don't accept it, don't use it. Write your own code, or find another one. But don't complain about what's given to you.

      What you fail to see is also that many developers prefer GPL style licenses over BSD style licenses. This is because they want to be sure that their code never gets hidden away in a closed source commercial package. I think you should respect these developer's desiscions.
      Many others prefer BSD style licenses, because it insures them that their code will get used and wide-spread now and forever. Each of them have their own philosophy, and uses.

      You think that there's a war going on. I see no war. I don't think there's a war, nor will there be, unless people like you, ranting and shouting that the GPL is evil and only BSD is the truly Open Source license, get too noisy. Grow up.

      --

      GNU/Linux. The Freshmaker.

  113. /. needs a clue by rcooper · · Score: 1

    As far as I'm concerned /. does far more harm to the open source and the Linux community with premature nonsense articles like this than anything else. Yet another blindly posted article that was not investigated to any degree whatso ever. This is good flamebate against Open Source and basically shows the acute immaturity in the Linux Community. You people who run /. have an obligation to the community to report things that are correct, complete and fair instead of acting like a bunch of immature kiddies who post garbage like this. Any RESPONSIBLE person would have contacted Bruce for a clarification of the issues. Instead you post this crap and create waves within the community. It should have stayed on the mailing list where it orginated.

    --
    You have been assimilated.
  114. Can you blame him? by Inoshiro · · Score: 2

    I know he's backed off now, but I agree with his actions. Corel must be held accountable.

    Corel has dropped the ball so much recently. They must have some lawyers -- did it ever occur to them to consult with these lawyers? If they did, why did the lawyers not stop them?

    First, they break the GPL by trying to be the same old closed-source company. Why did we accept this? Because they were new, and a mistake is OK the first time.

    Next, they decided to link in GPLed code with code that does not share a similar licence. Why? There was no excuse for this one, but we forgave them because they were well intentioned. Heck, I've worked on a GPL program that uses libraries that are not GPLed. However, I did check to see if the licence permitted it (it did).

    And now, they seem to have decided that only people who can be held responsible for using a free as in freedom operating system shall have it. IT IS FREE! FREEDOM! Who do they think they are? How do they think they can dictate fair usage of FREE, OPEN code?

    I'm Canadian, and so are they. Corel makes me feel ashamed to be in the same country. Why? Because they are too apathetic to even get a Linux distribution done correctly. Hopefully Linux One, and a similar slew of "We have a distro, too!" companies won't make the same screwups, otherwise we're in for a hellish new year.
    ---

    --
    --
    Internet Explorer (n): Another bug -- that is, a feature that can't be turned off -- in Windows.
    1. Re:Can you blame him? by Imperator · · Score: 2

      LinuxOne just did a s/Red Hat/LinuxOne/ over the entire RH6.0 CD and called it a distro. It's just a make-money-fast scheme. Many of the other me-too distros will be the same way.

      --

      Gates' Law: Every 18 months, the speed of software halves.
  115. Re:Lawsuits are inevitable unless we change course by Brett+Glass · · Score: 3
    Businesses have to realize that free software is something we share with them.

    There's no conflict between this notion and that of moving to a license which is not antagonistic to business.

    "Sharing" does not mean demanding something unreasonable in return -- which is, alas, what the GPL does. "Sharing" must be done willingly. If you start by demanding things in return, you are not sharing; you are negotiating a transaction. You are being adversarial, not cooperative.

    And, yes, individuals and businesses will and do give back, as has been shown in every open source software project which uses a license other than the GPL. Why? Because it is in their interest to do so. Who wants to maintain thousands of tiny enhancements through different versions of an open source program? The only thing which businesses will keep private -- and they are justified in doing so! -- are major creative works for which they deserve the chance to be compensated. So, things sort themselves out properly without the need for undue restrictions -- or for lawsuits.

    Self-interest is a far stronger and more pleasant motivator than any license.

    --Brett

  116. You need to learn... by Roberto · · Score: 1

    ...what sublicensing means.

    In particular, how can they be sublicensing when they are giving it to you under the GPL?

    Please notice: they are not saying you can't use the software if you are a minor. They are not saying you can't copy the software if you are a minor. They are not saying tou can't modify the software if you are a minor.

    All they are saying is that if you are a minor, THEY will not give the software to you. I could give it tou you. I WILL NOT give it to you. Am I breaking the GPL too? Am I "sublicensing"?

    Of course not!

  117. Slashdot should get a smack for this by anewsome · · Score: 1

    Rob, Hemos, Roblimo and all, ... I hope you're listening. This story should have never been posted at all. I've read through all of the comments (moderated @ 3 or higher) and I tend to agree with most of them. This story should have stayed on debian-legal until it really was a story. Obviously Bruce was upset and *shouting* a bit to his closest correspondence partners to let off some steam. Only problem was his steam happens to be publicly available on the Internet and you folks choose to run a story on it,... big mistake judging on the proportions that this hype has grown to.

    And Bruce apologizes to Corel ? Slashdot should apologize to everybody including Bruce and the Slashdot reader community.

    Bottom line is, I'm a 4 year Linux only user who has been *DESPERATELY* waiting for Windows quality apps to come to Linux. Replacements for apps like Corel Draw, Pagemaker, Microsoft Money, etc would make my life a hell of alot easier. Corel is the first company that has even come close to giving me hope that I will eventually get Linux replacements for these apps.

    Let's try not to piss them off before they even get the first app out the door (wp doesn't count, there are plenty of word proc apps and I use vim mostly anyway). I'd also like to see for once the Linux "lynch em all" attitude chill just for a moment and realize that everything that Corel is doing for the Linux users is ultimately a good thing.

    Thanks, Aaron Newsome

  118. Who Gives a Shit? by Chasuk · · Score: 1

    Who gives a shit? Do you really know any 14 years who are such dorks that a non-enforceable clause in a EULA would stop them from downloading anything? I mean, it certainly doesn't stop them from downloading mp3's, or NES ROM's, or porn, or warez, or super-strength versions of PGP (disregarding nationality), so why should we care about a stupid clause included by Corel's clueless legal department? Le's get up in arms about things that actually impact our lives.

    I know, now that I have broached the subject, a few dorks will identify themselves and try to make an issue out of this dead horse. Others will mis-read my words and accuse me of encouraging the deliquency of minors.

    Bruce Perens, any respect that I might have had for you has been destroyed utterly.


  119. Who cares about anonymous cowards? by Tridus · · Score: 1

    I mean they only have really stupid things to say, and they're all cowards, not willing to sign their real name to their idiocy!

    Anonymous Cowards should be shot and never heard from again.

    - the above sarcasm is brought to you by the society for the abolition of annoying people.

    --
    -- "So they told me that using the download page to download something was not something they anticipated." - Bill Gates
  120. Re:Lawsuits are inevitable unless we change course by Brett+Glass · · Score: 1
    Unfortunately, Ben, the GPL is doing a great deal of damage -- to programmers' livelihoods, to markets, to end users, and to the relationship between open source and closed source.

    Thus, while it might be nice to sit idly by, we must do more. If we care about what our world will be like in the future, it is insufficient to "go away" or "just not use the GPL." Instead, we must take action to dissuade programmers from using the GPL and to help them see through the deceptive rhetoric which Richard Stallman uses to promote it. We must actively free code from the GPL by any means possible. (It's a shame that it is necessary to expend the enerty to do this, but we may not be able to rid ourselves of the scourge in any other way.) If necessary, we may have to have the GPL's onerous "copyleft" provisions ruled invalid by a court of law (though I would hope that this is not necessary; lawsuits consume time, money, and energy and create conflict).

    The GPL destroys markets, retards programmers' progress by forcing them to reimplement the wheel needlessly, and hurts livelihoods. In the case of the browser project for the blind to which you allude above, licensing problems (including the presence of the GPL on much of the code in Lynx) has caused our group to reimplement and re-test code needlessly. No good comes of this -- only harm which would have been avoidable were it not for the GPL. We'd be much closer to the finish line -- and those blind users would be much closer to having a good browser -- were it not for the GPL and for attitudes such as the ones you express above. I am not sure why you seem to be spoiling for conflict, but I, personally, am not. I want to build, to share, and to give back. Our group's goal is not to make "lots of money" but merely to be fairly compensated for our hard work. If you begrudge this to your colleagues, you are being spiteful and destructive -- for no good reason. This is what we should eliminate: the conflict and the spite. And this is why we should eschew the GPL, which was designed to embody these things.

    --Brett Glass

  121. Re:Lawsuits are inevitable unless we change course by craigly · · Score: 1
    Brett, you have already illustrated both your ignorance of the GPL and FSF, as well as your obvious bias with such statements as:

    From ZDNet news talkback

    "The express intent of the GPL (see Richard Stallman's "GNU Manifesto") is to eliminate commercial software, thus hijacking the entire industry and forcing users to run only software which Stallman's "Free Software Foundation" controls. An Orwellian prospect."

    It seems you are unable to distinguish between commercial and proprietary software. RedHet is Free Software and commercial, and the FSF has no problem with them. Cygnus sells gcc as a commercial product, and they also sign over copyright on their work to the FSF. The only thing the FSF is against, is the use of proprietary licensing, regardless of the commercial or non-commercial nature of the software in question.

    RedHat, Cygnus and dozens of other companies have no problems respecting what the GPL required of those who distribute or modify GPLed software. The only people it seems to be paining are those who are incapable of reading, or actively seeking to take the rest of us for a ride.

    --
    craig
  122. Under which license do you release your source ? by Waldo · · Score: 1

    Have you released ALL your source under BSD ? If not, which licenses have you used ?

  123. Re:Lawsuits are inevitable unless we change course by fwr · · Score: 1

    I'm not aware of any programmer's livelihood, market, or end users that have been harmed by the GPL. If you have evidence of any, I'm sure everyone would like to hear it.

    Man! You are one bitter person. Don't you have anything better to do that spew forth hate and loathing for the GPL? What, specifically, has got your panties in a bunch, or are you always such a mean person? Are you pissed because you can't take a GPL browser and extend it for blind people so that you can sell it for proprietary reasons? If so, you'll get no simpathy for me. The moral and ethical thing to do would be to get a job actually doing something and work on your browser enhancements in your spare time. That way, you could do the blind community a great service and still be able to support your family. Hell, do something else for your paying "job." You could be a network person, as that is tied closely to programming and in my expereince people with programming skills are very good at networking. Besides, it probably pays better than you could get programming. Be constructive, not destructive. Love, don't hate. Paraphrasing an insurance commercial I hear recently, "raise that other finger when you make a gesture. See, doesn't that feel better, now you have a peace sign!"

    And what do you mean you're not spoiling for conflict! Don't you realize how hateful and inciting your comments are? Don't you know that for a person who believes it's our right to be able to do anything we want with our code and release it under any terms your comments are unbelievably objectionable? I know my comments must be objectionable to you, and you may even view them as flamebait. If you take them that way, then accept my appologies but now you know what it feels like. I think we are just sick and tired of listening to people like you, and Sun with their SCSL, and the BSD people (although most of them are O.K.), try to put us into some guilt trip and force us to release our code under a license that we fundamentally disagree with. Just accept the fact that some people have different views than you and get on with your life.

  124. Re:A prime example of Slashdot CENSORSHIP by norom · · Score: 1

    It isn't really censorship. All we have to do is broswe at -1 (if you have an accout) But you are right, less people will read the comment than if it had been moderated up. And my comment on the situation (probably redundant, I didn't read the ~ 300 comments) Bruce sent a message to a Debian Mailing List. An AC misinterperated this message. Hemos misinterperated this message. Corel still needs to correct the EULA. Not much else to it.
    ---

  125. Re:Slashdot's irresponsible "news" reporting by Imperator · · Score: 2

    Big difference: ZDNet wouldn't have known who Bruce Perens is. Slashdot knows and places too much emphasis on it.

    --

    Gates' Law: Every 18 months, the speed of software halves.
  126. Debian/Slashdot paparazzi ? by Morgaine · · Score: 3

    So, somebody on that Debian list is your typical paparazzi and someone in Slashdot is your typical sensation-seeking news editor. Doesn't that just make one feel all warm and fuzzy? ;-(

    What annoys me more though is that people are making silly interpretations of the GPL instead of examining Corel's stuff. I would have thought that the relevant statement in the GPL was clear enough: '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.' How can that leave any doubt that there is no requirement in the GPL for contractual binding, since the GPL is not a contract binding its signatories but a legal copying and distribution constraint binding the software, and that therefore contract law is irrelevant? And as if that weren't enough, anyone with half a clue can see that games licenses do not lose validity when games are sold to minors, else the games industry would be in utter shambles. So what is there to discuss? About the GPL, nothing as far as I can see.

    But about the EULA there's plenty to discuss so let's discuss it, without throwing irrelevant contractual nonsense about the GPL into the works.

    --
    "The question of whether machines can think is no more interesting than [] whether submarines can swim" - Dijkstra
  127. Apologies. by Chris+Johnson · · Score: 5

    I'm seeing quite a bit of sentiment indicating that Linux users and GPL-using authors should ask Corel to apologize, to say 'oops', and then should sit back and trust them.

    Well... of course somebody at Corel will be told to say 'oops'. That's his job. Its name is 'Public Relations'.

    There's also people there whose job it is to figure out the next testing of the outside of the envelope. They are called 'lawyers'.

    Forget that they have PR people for a minute, and also forget about their lawyers, and let's just look at their ACTIONS, okay? Their actions have consistently been causing problems. It doesn't matter that there's somebody to say 'oops'. That is a PR person, that's their job, it does not mean as much as people would like to believe.

    I personally have a lot more respect for Bruce Perens for momentarily _refusing_ to listen to the PR flacks and looking at what Corel is repeatedly doing. I'm not sure if people realise that permitting such abuses of the GPL is very similar to letting people talk about xeroxing documents...

    If you do that, the Xerox people _will_ speak to you and make sure you are aware that you are using their registered trademark as if it were a generic term, that other companies have lost their trademarks over just such weakening of the mark, and that Xerox (r) does not intend to weaken its mark in such a manner.

    Well, the behavior by Corel obviously weakens the GPL- to the extent that it goes unchallenged. Anybody picking a fight with the GPL will be able to point at the Corel actions involving it, and the community responses to it. They will be able to truthfully say to a judge or jury, "This is not actually binding, because it is not obeyed or respected by even the people who use it. Look, here are 500 slashdot posts saying that Corel should not be penalized in any way for their alterations of the license, because Corel will benefit the community. Isn't it true that the GPL is a legal fiction that is not actually intended to be followed- as seen by these posts effectively waiving it in the court of public opinion... and therefore, shouldn't it be declared null and void?"

    That's a perfectly legitimate approach for a lawyer to take, to invalidate the GPL. It's Corel above all who are making that argument possible, by repeatedly adding and altering conditions- and it's Linux users who are helping, by assenting to this alteration of the license, and making the argument that Corel should not be held responsible to the terms of the license.

    I'm sorry, but I don't assent to the alterations of the license. I have software out there under the GPL, and I don't remember giving Corel permission to alter, challenge and weaken the license for their own convenience. I'm not concerned with how quickly a PR flack can be found and made to say 'oops'. These changes need to stop, or Bruce Perens' hasty reaction will be the only sensible course of action in the long run.

    I _realize_ people want to be nice and not seem threatening or combative, but this is not fantasyland, or high school: this is the real world, there are consequences, and allowing a widely used agreement like the GPL to be defined differently in practice than it is in writing is bad. It makes an argument possible that the written version isn't really the applicable one- just as we need to look at Corel's _action_, so the courts will assuredly look at the Linux community's _action_ to ascertain how valid the GPL is when challenged. Do we, seriously, want to establish the precedent that you get to do whatever you want as long as you don't keep doing it for so long that it gets annoying? More relevantly, how many people advocating that Corel be let off easy have themselves written GPLed software- which of these people don't actually have anything to lose?

    I think if attention is paid to the Linux community's wishes as to how closely the GPL must be followed, the attention needs to go to the people who have written software that uses it. I don't think it's at all helpful for people who aren't actually using the license on their own work to say 'Take it easy, maybe they don't have to obey this license that closely'. I think most people who do use the GPL on their own work would not wish legal precedent to be set that the license isn't really real, that in practice it's customarily altered and bent to fit situations. I certainly do not. From Bruce Perens' initial reaction, I don't think he wishes that conclusion to be drawn either.

  128. Re:Satire by Menthos · · Score: 1
    Someone moderate that to "funny". Made at least me laugh my pants off...

    --

    GNU/Linux. The Freshmaker.

  129. Re:Lawsuits are inevitable unless we change course by DaemonDownTheHall · · Score: 2

    "Sharing" does not mean demanding something unreasonable in return -- which is, alas, what the GPL does. "Sharing" must be done willingly. If you start by demanding things in return, you are not sharing; you are negotiating a transaction.

    You are mistaken here. "Giving" is done willingly, without demanding something in return. "Sharing" is done with the expectation that the other person will "share" back.

    Demanding something unreasonable in return is neither of those, and nor does it pertain to the GPL. The GPL enforces sharing, the BSD license expects the other person to want to share. The businesses I have worked with in the past have absolutely no intention of ever sharing code, so I release under the GPL. If businesses in general were willing to share, I'd put my code in the public domain.

    You are being adversarial, not cooperative.

    No, I'm being realistic. If your experience with businesses and other people leads you to view the world as rosey, then feel free to BSD your code. I have a less-rosey view of businesses, so I GPL mine.

  130. GPLed software is not commercial. by Brett+Glass · · Score: 1
    GPLed software is not commercial, because those who sell copies of it (e.g. Red Hat) do not own it and do not have the ability to license it. What you are paying for, when you buy Red Hat Linux, is the plastic disk, the box, the manual, the support. You are not buying a license to use the software. It is not Red Hat's to license!

    To say that Red Hat Linux, and other distributions of Linux which are published by companies like Red Hat, are "commercial" is intentionally misleading. It is part of Richard Stallman's rhetoric, and is an attempt disguise the anti-business mechanisms of the GPL. (Richard Stallman endorses a strategy which he calls "pragmatic idealism" -- i.e. "The end justifies the means." Alas, he appears to condone the use of deceptive rhetoric so long as it furthers his ultimate cause: the destruction of truly commercial software.) In fact, the GPL is anti-commercial.

    --Brett Glass

    1. Re:GPLed software is not commercial. by DaemonDownTheHall · · Score: 1

      GPLed software is not commercial, because those who sell copies of it (e.g. Red Hat) do not own it and do not have the ability to license it.

      OK. This is my third attempt to respond to your obviously misinformed posts. The GPL is not a long license as licenses go, but apparently you haven't read it. One of the rights given when licensing under the GPL is the ability to relicense all of the rights you got to anyone else. Hence, Red Hat most certainly does have the ability to license it.

      You are not buying a license to use the software.

      Yes, you are. You are paying for:

      1. A physical instantiation of the software (i.e. the media)
      2. A physical instantiation of the ocumentation
      3. A license to use the software included on the media (with regards to GPL'ed software on the media, you get all the rights that Red Hat got)
      Had you read the GPL, you would have understood that they are not only able to license the code to you, they are required to do so.

      To say that Red Hat Linux, and other distributions of Linux which are published by companies like Red Hat, are "commercial" is intentionally misleading.

      Only if your definition of "commercial" is far different than mine. The relevant definition from my handy dictionary is:

      commercial: a. made or done primarily for sale or profit
      which (I feel) fits Red Hat. Perhaps you might argue that their primary purpose is "for the good of the community", but that would be illegal, as they are now a publicly-traded corporation (they are required to maximize shareholder profit, and hence must work "primarily for sale or profit").

      Alas, he appears to condone the use of deceptive rhetoric so long as it furthers his ultimate cause: the destruction of truly commercial software.

      Ah, I see that you use the word "commercial" to mean "only available to companies". That definition goes far beyond even that of "proprietary" in terms of hostility to, and incapacitation of, non-companies (i.e. people). This "businesses can do whatever they want; screw the people" stance would logically extend towards allowing (for instance) car companies intentionally to make deathtraps. Surely you aren't advocating that businesses are more important, or are allowed to do more things than, people?

      P.S. to other people - I realize that this guy is a lost cause. I'm just practicing ripping posts apart (and realizing I could be a lot better with practice and feedback). Please send me an email (or respond to this post) if you can see where I could improve my posts.

  131. Wow. That's trippy. by DaemonDownTheHall · · Score: 1

    Wow. That's trippy. I could almost see the froth coming from your mouth.

    ...we must take action to dissuade programmers from using the GPL and to help them see through the deceptive rhetoric...

    So you'd suggest re-education camps for everyone who uses copyleft? How about copyright?

    If necessary, we may have to have the GPL's onerous "copyleft" provisions ruled invalid by a court of law

    Uh... wow. Once again I find myself dumbstruck. You realize that removing the ability of people to license their software means that you'll have to sell your software instead of licensing it? That I'll have free reign to disassemble it, code a new version, and release mine for free with each AOL CD, and that you won't be able to do a damn thing about it? Are you sure that's what you want to do?

  132. You have to be deliberately ignoring this. by bkosse · · Score: 1
    In the case of the browser project for the blind to which you allude above, licensing problems (including the presence of the GPL on much of the code in Lynx) has caused our group to reimplement and re-test code needlessly. No good comes of this -- only harm which would have been avoidable were it not for the GPL.
    Brett, it's been said before, and I *WILL* continue to say it until you give up on this tirade of yours.

    The GPL is a way for the Lynx programmers, in your words, "to be fairly compensated for their (orig. 'our') hard work." In the US, and probably most other countries, one form of exchange is to give up certain rights or to ask for someone to give up certain rights. This is the principle behind NDAs and, ironically enough, your code. You ask people to, amongst other things, give up the right to disassemble their code, in exchange for receiving a binary that hopefully does what they want it to do. With the GPL, all that's being asked is for you to give up your right to subsequently keep code private. In exchange, you receive a specific amount of code (namely, the GPLed software). Whether or not the code you get is enough to sway you towards using GPLed code is another matter. If you feel the value of the GPLed code isn't high enough, then you obviously feel that the value of the code is worth less than your time to reimplement it.

    I don't spite, nor begrudge my colleagues, Brett. Rather, I say, use what works for you. You, on the other hand, *DO* begrudge any and all who use the GPL. You insist that all people coding open source software release it in a way *YOU* can take and make money on. I don't suppose you feel any desire to then funnel a fair amount back to the coders, do you? No. You'd rather that coders just give you stuff, to hell with their rights, time, etc.

    By the way, nice attempt at making those who like the GPL out to be the bad guy. After all, it wasn't your choice not to GPL your software. To put it differently, "We'd be much closer to the finish line -- and those blind users would be much closer to having a good browser -- were it not for my desire to keep my code private and for attitudes such as the ones you (Brett) express above."

    --

    --
    Ben Kosse
    Remember Ed Curry!
  133. Enforced "sharing" is confiscation. by Brett+Glass · · Score: 1
    This, alas, is what the GPL attempts to do. In his essay, "Why Software Should Not Have Owners," Richard Stallman actually encourages employees to integrate GPLed code into the company's product, so as to force it to release all of its source code. This "monkey wrenching" is not sharing; it's an attempt to use a license -- and the might of the government -- to literally confiscate the company's code. Which is what Stallman, and the FSF, have always intended the GPL to do. In his many essays, Stallman uses the word "free" in the same way as revolutionaries in a third world country:

    Revolutionary #1: We have 'liberated' this evil person's car, house, and food for the benefit of the Revolution. He was hoarding them, which is an affront against the People.

    Revolutionary #2: Yes, these things are now Free! Long live the Revolution! Oh, and pass me another turkey leg....

    In short, Richard Stallman believes that it is legitimate to confiscate intellectual property to benefit the organization which he controls: the FSF. The GPL is the instrument via which, he believes, he can harness government power to do this.

    What is real sharing? Well, for one thing, true sharing is always speculative. When one shares, one recognizes the a possibility that that the other person might not reciprocate. But this is part and parcel of sharing.

    Insisting that the other person give up his or her livelihood (which is the effect of forcing a professional programmer to release source without compensation) is not sharing; it is confiscation.

    --Brett Glass

    1. Re:Enforced "sharing" is confiscation. by DaemonDownTheHall · · Score: 1

      This "monkey wrenching" is not sharing

      You are correct, that is not sharing. Nor was it what I was referring to. I will rephrase: sharing is two-way giving. The situation you refer to here is more appropriately termed "screwing over" - the employee is not there to "share" with the company, he's supposed to be working for it. This is no better than an employee who secretly tells the competition what they bid for a project. Your's is a strawman argument.

      Which is what Stallman, and the FSF, have always intended the GPL to do.

      No, they have always intended for the GPL to act as a "if you don't want to play nice with us, we won't play nice with you" type of force. You cannot claim that RMS's motives are unclear; you yourself refer to his many essays. Are you deliberately refusing to understand his stance, or are you trying (and failing) to understand it? Perhaps this is all just an elaborate ruse?

      In short, Richard Stallman believes that it is legitimate to confiscate intellectual property to benefit the organization which he controls: the FSF.

      This is a continuation of the above strawman argument. "Monkey wrenching" is unethical (and possibly illegal, depending on where you are). He has never (to my knowledge) supported the confiscation of "intellectual property", except insofar as he advocates the abolition of "intellectual property" altogether (which would itself remove the ability to "monkey wrench" in that way).

      Second, the GPL does not in any way benefit the FSF. GPL'ed software benefits the people who need to use that software. The only software that "benefits" the FSF is changes to FSF-owned code; no other code has any relationship with the FSF.

      The GPL is the instrument via which, he believes, he can harness government power to do this [IP confiscation].

      No, he does not. You have fallen victim to your own strawman argument here; if you make a case based on a point, then your case falls apart if that point does. I have shown your argument to be false, so I shall take this shortcut to not show this statement to be false as well.

      Insisting that the other person give up his or her livelihood ... is not sharing; it is confiscation.

      Of course it isn't. Just as it isn't sharing to insist the the mugger in front of me not take my wallet, or to force a rapist off the streets. In order for you to claim an inherent "right" to do what you currently do for a living, you must first show that it is inherently right for you to be doing it in the first place. This is not to say that it isn't right, but you certainly haven't shown that it is inherently right. If you would care to put forth an argument as to why I should be forced to give you my code, when you aren't willing to give me yours, I'd be happy to point out where you went wrong.

    2. Re:Enforced "sharing" is confiscation. by Keith+McClary · · Score: 1

      In his essay, "Why Software Should Not Have Owners,"
      Richard Stallman actually encourages employees to integrate GPLed code into the company's product,
      so as to force it to release all of its source code.

      You mean this?:
      http://www.gnu.org/philosophy/why-free.html

      I don't see where he says anything like that.

    3. Re:Enforced "sharing" is confiscation. by GregWebb · · Score: 1
      Insisting that the other person give up his or her livelihood ... is not sharing; it is confiscation.

      Of course it isn't. Just as it isn't sharing to insist the the mugger in front of me not take my wallet, or to force a rapist off the streets.
      You seriously compare the release of closed-source software to violence and theft? Ouch. Do you care to explain exactly how I am harming you by releasing software as binary only? I make no compulsion on you to accept the license or purchase the software.

      Note that I fully understand that this argument falls over very quickly for something where a network effect has kicked in such as Windows. But that's an exception - there are millions of software developments out there and Windows is one of only a handful where this problem exists.

      In order for you to claim an inherent "right" to do what you currently do for a living, you must first show that it is inherently right for you to be doing it in the first place.
      Certainly. I claim the right to profit from my knowledge and experience based on the fact that until such a time as my software becomes sufficiently ubiquitous to allow me to exert control over a given market, its release cannot by definition harm anyone. If and when ubiquity for any of my software is reached, I will consider releasing it in such a way as to remove any stranglehold I may posess over a market. But until such a time, harm is not possible. Were I to try and exert unreasonable control over a market in which reasonable competition still existed, I would lose market share.

      Note that I'm not currently a commercial developer so this is all in abstract. Also note my support for KOSH, showing that my preferred model is the mutual cooperative society, controlled by and profiting those who have given it market position - users, developers and retailers. Which I consider far fairer than the abstract freedoms many seem to desire.

      This is not to say that it isn't right, but you certainly haven't shown that it is inherently right. If you would care to put forth an argument as to why I should be forced to give you my code, when you aren't willing to give me yours, I'd be happy to point out where you went wrong.
      And here lies the flaw in your argument - you seem to feel that your altruism in releasing your code should be forced on others. True altruism should be what the GPL and associated movements are promoting - that is, selflessly giving to others without expecting anything in return.

      I saw nothing in the original post suggesting that you be compelled to release your code - indeed, quite the reverse. I would make no such demand until very exceptional circumstances had developed - as I outlined above. Under those circumstances I would happily call for unilateral forced release but until such a time, that is simply not sensible.

      Greg
      --

      Greg

      (Inside a nuclear plant)
      Aaaarrrggh! Run! The canary has mutated!

    4. Re:Enforced "sharing" is confiscation. by rking · · Score: 1

      "You seriously compare the release of closed-source software to violence and theft? Ouch. Do you care to explain exactly how I am harming you by releasing software as binary only?"

      I agree that his analogy isn't really valid.

      "I make no compulsion on you to accept the license or purchase the software."

      Agreed, just like noone is forced to accept the GPL. If you want to accept the licence and copy the code / distribute derivative works subject to the licence then you can, and if you'd rather do without those rights than accept the licence terms then that's okay too. I don't understand why people have a problem with this licence who have no problem with closed source licences, it makes no sense.

      "And here lies the flaw in your argument - you seem to feel that your altruism in releasing your code should be forced on others."

      But he's not, he's claiming the same right to licence his code how he chooses as others have to licence theirs, what's the problem?

      "True altruism should be what the GPL and associated movements are promoting - that is, selflessly giving to others without expecting anything in return."

      Why "should" it be? Is this what Corel "should" also be about doing? If you want to encourage True Altruism TM then go ahead, why do you feel that others "should" be promoting your philosophy instead of their own? And no, the GPL doesn't compel others to follow its philosophy it just proposes a bargain that they can enter into or reject as they choose.

    5. Re:Enforced "sharing" is confiscation. by GregWebb · · Score: 1
      I don't understand why people have a problem with this licence who have no problem with closed source licences, it makes no sense.
      I have a problem with many closed licenses myself, but the reason for my particular dislike of the GPL is that its proponents will claim it is the ultimate in free licenses. It isn't. The most free out there is to release your code into the public domain, followed by a BSD-style license which doesn't restrict use.

      snip - you can just look up :)
      But he's not, he's claiming the same right to licence his code how he chooses as others have to licence theirs, what's the problem?
      Simple - if you re-read his original post (or my quote of it, for that matter), you'll see that he said:

      If you would care to put forth an argument as to why I should be forced to give you my code, when you aren't willing to give me yours, I'd be happy to point out where you went wrong

      In other words, he seems to feel that his altruism should be forced on others. Rather different.

      I'm happy for the GPL to exist and for people to release their software under it if they so choose, but do I like the license or think it's a particularly good, community-friendly license? No.

      "True altruism should be what the GPL and associated movements are promoting - that is, selflessly giving to others without expecting anything in return."

      Why "should" it be? Is this what Corel "should" also be about doing? If you want to encourage True Altruism TM then go ahead, why do you feel that others "should" be promoting your philosophy instead of their own? And no, the GPL doesn't compel others to follow its philosophy it just proposes a bargain that they can enter into or reject as they choose.
      It "should" be about true altruism as opposed to compulsion. Some seem to feel that the GPL is all that should be allowed, which is what I was arguing against.

      I agree that the GPL doesn't force you to follow its philosophy BTW, but it's not creating this open-code paradise that some seem to want as it forces people to reimplement code if they don't want their work covered by the GPL. And I can't see that that's true freedom or a truly useful bit of work as it's forcing them to repeat someone else's labour. A BSD-style license does not do this and so should be considered freer.

      Greg
      --

      Greg

      (Inside a nuclear plant)
      Aaaarrrggh! Run! The canary has mutated!

    6. Re:Enforced "sharing" is confiscation. by fwr · · Score: 1

      snip - you can just look up :)

      But he's not, he's claiming the same right to licence his code how he chooses as others have to licence theirs, what's the problem?

      Simple - if you re-read his original post (or my quote of it, for that matter), you'll see that he said:

      If you would care to put forth an argument as to why I should be forced to give you my code, when you aren't willing to give me yours, I'd be happy to
      point out where you went wrong

      In other words, he seems to feel that his altruism should be forced on others. Rather different.


      No, I think you are turning it around here. He's saying that you (or whoever) would be wrong to believe that he should be forced to give away his code using a license that he does not agree with. In other words, that he should not use the GPL and should use a license which you (or whoever) believes to be more "free." His reason for saying that he would be "happy to point out where you went wrong" seems to center on the fact that you (or whoever) don't want to give your modifications back to him and the community and instead want to take the code proprietary. In effect, you (or whoever) is taking but not giving back. In fact you (or whoever) wants to charge for the results of you using "free" code. How can that be right?


      And, this has nothing to do with altruism or him forcing his views on you. I don't think that he's saying you should be forced to release your code as GPL if you don't use his, is he? If so, I disagree with him. He just wants what is "fair" and balanced. To expect someone to expend effort and give it away without doing so in kind is not right. If you choose to do so yourself, then more power to you. To judge others and say that they are doing something "wrong" because they won't support people out to make a profit is wrong.

      It "should" be about true altruism as opposed to compulsion. Some seem to feel that the GPL is all that should be allowed, which is what I was
      arguing against.


      I would agree with this, that the GPL should not be the only option. I think everyone should be able to choose whatever license they want for their contributions. For some to argue that no one should use the GPL seems a little selfish, no?

      I agree that the GPL doesn't force you to follow its philosophy BTW, but it's not creating this open-code paradise that some seem to want as it
      forces people to reimplement code if they don't want their work covered by the GPL.And I can't see that that's true freedom or a truly useful bit of
      work as it's forcing them to repeat someone else's labour.


      I don't see anything wrong with this. If you are going to force us to "repeat" your labor for the enhancements you make to our code, then why shouldn't you be forced to do the same? I don't see the logic in it. Why do I think it necessary to "force" you to release your code if you happen to use mine? History. Plus, you (or whoever) flat out say that you won't release your code back to me and that you want to take it proprietary! (until you have a "stranglehold" over the market that is, oh, how altruistic is that!)

    7. Re:Enforced "sharing" is confiscation. by GregWebb · · Score: 1
      In other words, he seems to feel that his altruism should be forced on others. Rather different.
      No, I think you are turning it around here. He's saying that you (or whoever) would be wrong to believe that he should be forced to give away his code using a license that he does not agree with. In other words, that he should not use the GPL and should use a license which you (or whoever) believes to be more "free." His reason for saying that he would be "happy to point out where you went wrong" seems to center on the fact that you (or whoever) don't want to give your modifications back to him and the community and instead want to take the code proprietary. In effect, you (or whoever) is taking but not giving back. In fact you (or whoever) wants to charge for the results of you using "free" code. How can that be right?
      It's probably safer if we agree to disagree on this one :) You say you're right, I say I'm right, let's leave it at that.

      I wasn't actually talking about the morality of taking code into a closed product, though. That's up to the coder to decide upon. My simple point was that shouting regularly that nothing is freer than GPL is wrong. GPL may keep the code free (according to FSF definitions) but it certainly imposes restrictions on your use of the code. And since RMS (IIRC) has said: 'Good programmers write good code; great programmers re-use good code' (to paraphrase, I haven't got the exact quote in front of me) that's not allowing great coding.

      I'm perfectly happy that there are people out there who subscribe to the FSFs ideals. But, make no mistake, those ideals are anticapitalist and their code is not as free as it might be as its reuse is extremely tightly controlled. There are too many people (such as our original poster) who don't recognise that to be the case, overstate their altruism in releasing their code under the GPL or feel hurt that others don't share their ideals. Or, worse (though rare and I'm not suggesting it was the case here) flame people for not sharing their ideals.

      For some to argue that no one should use the GPL seems a little selfish, no?
      Certainly, that's a silly position. But it's equally silly for people to get all religious about the GPL or to assume that GPLing your code is the best way to give something to the computing community.

      If you are going to force us to "repeat" your labor for the enhancements you make to our code, then why shouldn't you be forced to do the same? I don't see the logic in it. Why do I think it necessary to "force" you to release your code if you happen to use mine? History. Plus, you (or whoever) flat out say that you won't release your code back to me and that you want to take it proprietary! (until you have a "stranglehold" over the market that is, oh, how altruistic is that!)
      Er, not what I meant at all...

      My argument here is relatively simple: GPL isn't as free as it might be. I'm not demanding the right to your code without reciprocal action on my part by any means: I'm merely illustrating that true altruism doesn't require the reciprocal action, which some people seem to have missed. Along with a side effect of the GPL in that a potentially useful project is harmed due to a lack of altruism.

      To go back to the speaking web browser thing, while the Lynx authors are free to insist that it's only used by the owners of Daffodils for all I care, their stipulation in the license that it may not be used by anyone who will not release it under the same license has hurt this project. They feel that it isn't in their business interest to release GPL code, which is their judgement and they're entitled to it right or wrong. So, they have a large pile of code to re-implement which takes time and costs money. This delays the final product and increases its cost, but wouldn't have been an issue if a freer license (such as a BSD-style license) had been chosen. Lynx's authors are entitled to their choice of license, but this is the end result. There could be a GPL browser made this way, but that would require a community effort to develop such a product despite it being notably unglamorous, a well-known problem with GPL development.

      As for the stranglehold bit, perhaps I explained myself badly there. My view is that almost no-one should have restrictions placed on how they can license their software. The exception is where a stranglehold has developed: at that point, standard licensing rules no longer apply and it is clear to me that there should be restrictions placed on how your code is licensed, otherwise the developer (if commercial) has the effective right to tax the relevant market. One possible solution would be to open the code - and by open I mean entirely open, in the public domain. One other solution would be a solution similar to that we are setting up with KOSH - make the company the property of the communities who depend on their products, at which point management's just not going to go for the sort of screwy business practices some have or they lose their jobs. Unfortunately, I understand neither is permitted by US law, which I regard as a real pity and extremely strange.

      The main point to note, though, is that I was not suggesting that this should be a voluntary process - I was suggesting compulsion, whether that was what I actually said or not ;)

      Greg
      --

      Greg

      (Inside a nuclear plant)
      Aaaarrrggh! Run! The canary has mutated!

  134. Re:Lawsuits are inevitable unless we change course by Chilli · · Score: 1
    Did you ever consider that the GPL is actually better for businesses than weaker licenses such as BSD? Take Red Hat as an example. Other companies can copy their distro and sell it, but Red Hat knows for sure that nobody will, e.g., improve their installer and distribute it without giving all the changes back to Red Hat. By building a brand recognition Red Hat can make a lot of money although other companies can sell the same code. If other companies (in particular those with more money) could use an embrace and extend strategy, I wouldn't be sure how long Red Hat could survive.

    Chilli

    --
    -=- Just a random lambda hacker
  135. Maybe we should ease up a bit.. by srcosmo · · Score: 1
    Exactly, maybe we should go a little lighter on pounding Corel for this GPL violation.
    As pointed out earlier, it's not entirely certain that the GPL couldn't use a bit of reworking to fix that 'paradox' deal.

    - Plus, I think it's fairly safe to say that a lot is riding on how Corel does in the Linux world- we can be sure many other companies are watching this, a bit hesitant on whether to jump on the wagon or not. Will they look kindly upon developing distributions (maybe even software) if Corel gets torn to pieces by holy soldiers of the GPL?

    Just a thought.

    --
    free speach
    Did you mean: free speech
  136. Compensation by Brett+Glass · · Score: 1
    The GPL is a way for the Lynx programmers, in your words, "to be fairly compensated for their (orig. 'our') hard work."

    Not so. In fact, by stamping the GPL onto their code, they have forfeited any hope of compensation for their efforts. They have done so by reducing the market value of their work to zero (users will not pay for the functionality, because they can obtain it for free) and eliminating any opportunity to do parallel commercial licensing. (They don't own changes introduced by others, and so cannot license the latest version for money.)

    I don't spite, nor begrudge my colleagues, Brett.

    It appears that you do. By supporting the GPL, you are supporting a mechanism of spite and malice. You may not recognize that this is so -- possibly due to the misleading rhetoric which accompanies the license. But the fact remains that the purpose of the GPL is designed to deprive programmers of their livelihoods and destroy their businesses.

    Rather, I say, use what works for you. You, on the other hand, *DO* begrudge any and all who use the GPL.

    I do not "begrudge" them anything -- rather, I point out that their actions are harmful and they therefore should stop. By adopting the GPL -- either without realizing its effects or because they desire to be malicious -- they hurt people. They further sow the seeds of conflicts such as the one we see here between the GPL zealots and Corel.

    You insist that all people coding open source software release it in a way *YOU* can take and make money on.

    Not so. Your statement above is replete with loaded and misleading language.

    In fact, I advocate the release of open source software in such a way that anyone can build on it, advance the state of the art, and avoid needless duplication of effort. Since the source has been published, it cannot be "taken" -- it's still out there. And any profit which is made on a derivative work will stem solely from an author's improvements, since the original functionality is available for free. The creator of the derivative work is not making money "on" the original; he or she is merely saving tedious and redundant coding by incorporating code which no longer has market value.

    Anyone can do this -- not just me in particular, but the whole world. The benefits are tremendous. The Internet exists today in its current form because the Berkeley TCP/IP stack was available to all comers -- open source, closed source, commercial, or non-commercial.

    This entire discussion is, alas, an example of the conflict that the misleading rhetoric of the GPL creates. The FSF's rhetoric appears to have created in you such hostility toward alternatives to the GPL -- or even toward recognizing its true agenda -- that you are flaming me and refusing to see the big picture.

    --Brett Glass

    1. Re:Compensation by DaemonDownTheHall · · Score: 1

      In fact, by stamping the GPL onto their code, they have forfeited any hope of compensation for their efforts.

      I'm sure this will come as a great surprise to the many people who work for Red Hat, and take home paychecks every day by writing software to be licensed under the GPL.

      ... eliminating any opportunity to do parallel commercial licensing. (They don't own changes introduced by others, and so cannot license the latest version for money.)

      I'm sure that this will come as a surprise to Red Hat, who is doing parallel commercial sales ("Power" vs. "Regular", or whatever they're calling it nowadays).

      I advocate the release of open source software in such a way that anyone can build on it, advance the state of the art, and avoid needless duplication of effort.

      As per your previous posts, this is something I doubt. However, I shall give you the benefit of the doubt; if this is truly what you mean, then you should be campaigning for the abolition of software copyright, not the abolition of copyleft. Removal of software copyright allows me to build on your software (albeit not as easily as I would be able to with the source), advance the state of the art, and (under some circumstances) reduce needless duplication of effort.

      ... code which no longer has market value.

      Once again, you have built your argument upon shaky ground; there are two ways to go on this issue, and you keep attempting to straddle the fence. Are you for for government-imposed sharing (i.e. copyright+copyleft), or laissez-faire sharing (i.e. lack of software copyright)? I think you will find it untenable to support the one-sided argument you keep proposing.

      This entire discussion is, alas, an example of the conflict that the misleading rhetoric of the GPL creates.

      No, the GPL contains no rhetoric in and of itself; it merely has explanatory messages amongst the license, which is supposed to strengthen its legal enforcability. If you remove the explanatory messages from the GPL, you are left with a dry, boring license, which does exactly the same thing as the original. How do you propose that a software license is misleading rhetoric?

      ... you are flaming me and refusing to see the big picture.

      I do see the big picture, or at least more of it than you appear to have seen. While there is certainly room for argument on a good number of points, it is apparent to a disinterested observer that you are losing this argument.

      As a side note, my sole purpose for posting in this thread is to better my skills in rhetoric. How about you?

    2. Re:Compensation by Mr.+Gus · · Score: 1

      I'm not going to bother repeating the comments to you that I've heard so far, but I do want to say something. Two of the points you like to express seem to be (politically) in direct conflict with each other:

      First, that by GPL'ing something you are forcing programmers (who wish to use a GPL-incompatible license) to re-invent the wheel.

      Second, that the GPL doesn't allow the "freedom" for an entity to use portions of code in a closed-source project.

      The victim of the second point would also cause the problem of the first point. Proprietary code forces programmers to re-invent the wheel, and also eliminates "example code". And yet, you seem to hold no malice toward proprietary code?

    3. Re:Compensation by GregWebb · · Score: 1
      In fact, by stamping the GPL onto their code, they have forfeited any hope of compensation for their efforts.
      I'm sure this will come as a great surprise to the many people who work for Red Hat, and take home paychecks every day by writing software to be licensed under the GPL.
      And how simplistic is this?

      Red Hat software are a short-term phenomenon. They can afford to pay people to write GPL software simply as they hold a strong enough market position that they can still benefit financially from advancing the community as a whole. Were their market share to drop substantially then this would cease to be the case - their programmers work would start to cost more than its benefit to Red Hat.

      So how do they make their money? Support? Come on, don't be silly. Support revenues are dependent on the amount of time the support technicians are used for by the client. In other words, the harder the software is to use and the less reliable it is, the more they make. Yet reliability is reckoned to me a major advantage of GPL (heck, any open-source) code, due to the ease of peer review. So, they have a financial incentive to write worse code... And with ease of use, if you want GNU/Linux on the desktop (most seem to) it is not going to be pushed forwards by a company which has a financial incentive to holding back one of the main things stopping this movement - ease of use.

      Red Hat and the other commercial vendors can survive simply as the market is in rapid growth due to infancy. The Linux distribution market will, by definition, ultimately stabilise. At which point the current business model is extremely likely to founder.

      Greg
      --

      Greg

      (Inside a nuclear plant)
      Aaaarrrggh! Run! The canary has mutated!

    4. Re:Compensation by fwr · · Score: 1

      So how do they make their money? Support? Come on, don't be silly. Support revenues are dependent on the amount of time the support
      technicians are used for by the client. In other words, the harder the software is to use and the less reliable it is, the more they make. Yet reliability
      is reckoned to me a major advantage of GPL (heck, any open-source) code, due to the ease of peer review. So, they have a financial incentive to
      write worse code.


      Oh grow up. You don't really believe this, do you? We just bought a bunch of Suns and guess what? We paid for a support contract on them. Why? Surely not because Sun makes crappy hardware! It's insurance. Insurance for a fluke in the hardware, or if I do something stupid and need assistance in configuring something. Companies don't but commercial software with support contracts because the software is a peice of crap. They buy it for insurance. And, no one makes more money by having their support personnel tied up all the time. The goal is to have more contracts per employee. The only way you can do this is if the actual support is not needed constantly. People who try to rip others off with support contracts charge on an hourly basis, like Microsoft. People who have confidence in their software charge per-incident or on a yearly basis. That's why RedHat has their incident support to get people started and their new Silver, Gold, and Platinum unlimited incident support contracts on annual basis. You don't think that your car insurance company makes more money when more people get into wrecks do you? That's why you have to have a current car inspection in order to get a insurance contract. RedHat's not going to sell support based on a crappy product.

      Either you've never designed a support business or don't have the experience working in one to know what you're talking about. Or, you're just spreading FUD about RedHat to support your views on licensing issues. Do you honestly believe that Intel and others would have invested in RedHat had they not performed their due diligence and reviewed their books and business plan? If you believe that I've got a bridge in Brooklyn I'll sell ya.


    5. Re:Compensation by GregWebb · · Score: 1
      Oh grow up. You don't really believe this, do you? We just bought a bunch of Suns and guess what? We paid for a support contract on them. Why? Surely not because Sun makes crappy hardware! It's insurance. Insurance for a fluke in the hardware, or if I do something stupid and need assistance in configuring something.
      So, you bought the support contract for:
      1. Insurance against random hardware failure
      2. Insurance against you screwing up the software
      Point (1) is entirely irrelevant in this discussion. Hardware is physical and thus subject to potential physical failure. Software (Red Hat's core business last time I checked) is logical and is not. With badly written code an install may degrade so it needs reinstalling after a certain period to provide reliable operation, but this is still not an absolute failure as your disctribution CD is still there. And it's also only an issue with bad code, thus emphasising my point that such a business model provides a financial incentive to write poor code.

      Point (2) is only an issue if the software is sufficiently unfriendly as to make that a problem. Well designed software has taken user friendliness into account and so is monumentally unlikely to break. In the event that it does fail, it's properly documented and relatively easily recoverable. In addition, consider my remarks about point (1) - namely, software is logical not physical. If I make a mess of some hardware configuration, it is entirely possible that I may render the hardware unusable and so have to replace it. Short of deliberately destroying the CDs, there is no equivalent with software. So, again, they have an incentive to write poor code.

      And, no one makes more money by having their support personnel tied up all the time. The goal is to have more contracts per employee. The only way you can do this is if the actual support is not needed constantly.
      Didn't say they did. You make your money by selling the support contracts with the technicians required to make that a reality a running cost. That's a rather simplistic reading of the situation though.

      Let's have a quick illustration. When I bought my current computer, it was my first non-Amiga. I had no experience of owning a Wintel box, so I was mildly scared. I had little or no idea of how to fix it if it went wrong, even to set it up in the first place. So, I went to a dealer and got a readymade machine with a support contract. Would I do that again? No, probably not. I've got vastly more confidence now than I had then, so could do the overwhelming majority of the task myself. Now, the same's true with support contracts. When you first buy into a market, you may decide that you want a safety net in case of failure. A few years later, you may observe that your confidence is substantially higher while your safetynet sits getting dusty having never once been used. So do you renew the contract? Probably not, after a while.

      While Red Hat (and Linux in general) are growing, there are always going to be green users who will feel they require the safetynet of a support contract. As they gain confidence, this number will decrease. If they are replaced with more new users, the economic model holds. But ultimately, the world will run out of new users. In which case, the only need for support becomes the few users who will never be able to help themselves and the terminally pessimistic. Yes, I understand the concept of children but how many kids who grew up around computers need all that much help with them?

      In other words, the support contracts market is dependent on the amount of time the technicians are used for (though with a lag) and will ultimately shrink in relation to the operating systems market, provided the software is relatively stable and easy to use. So, again, Red Hat have a financial incentive to write bad code.

      You don't think that your car insurance company makes more money when more people get into wrecks do you?
      No, as car insurance is legally required. If I drive down the road without Third Party insurance, I risk a substantial fine and a ban. Hence, this isn't a valid comparison.

      Do you honestly believe that Intel and others would have invested in RedHat had they not performed their due diligence and reviewed their books and business plan? If you believe that I've got a bridge in Brooklyn I'll sell ya.
      Interesting example considering my country sold your London Bridge... ;)

      Seriously, I'm not entirely sure what posessed Intel to invest. Red Hat probably have several years of growth left in them (assuming Linux can continue its current growth across market sectors, which is a BIG assumption) but long-term, forget it. This business model just isn't viable in a stable market, AFAICS.

      Greg
      --

      Greg

      (Inside a nuclear plant)
      Aaaarrrggh! Run! The canary has mutated!

    6. Re:Compensation by fwr · · Score: 1

      His fist computer was an Amiga, which explains a lot. Like Apple Mac users, a certain percentage of them believe that computers should all be point-and-click and all users should be able to comprehend and use them without any assistance regardless of the complexity of the task. Not all Amiga or Mac users believe this but some do (hell some "PC" users do, but I believe it's more common for "user friendly" computer users to have this attitude).

      The facts are that some computing tasks are fundamentally complex and no one knows everything. By taking these two fundamental truths in combination it's easy to see why businesses have one of two choices. Either they can hire a large number of people with very high levels of technical skill to cover all possible trouble areas or they can hire a few people that specialize in the core competencies and purchase support contracts to cover the remaining areas. A simple investigation into the relative costs of the two resources makes this a no-brainer.

      He doesn't seem to comprehend that insurance is a Good Thing in certain circumstances. Business is one where it is practically essential. Part of my work is to monitor peoples networks and assist them if they have problems. Do you think they would be so willing to hire me for support if I did not have support on the equipment we use? If we didn't purchase support contracts we would have to hire people with the skills in areas that we don't utilize much but would be required if we had issues and threaten our ability to support our customers. Do you think our customers want us to be spending all that money on mostly idle resources instead of purchasing relatively cheap support contracts? Hell no.

      Besides, he seems to want to ignore the real facts of computer life, such as only "suggested" "security" patches are available to support holding Sun customers. While RedHat does not do this, I would insist on a support contract with them if I used the Official RedHat Linux Boxed Set in my work, just like I would insist on HP support if I were running HP-UX or, gasp!, Microsoft support if I were running Windows NT.

    7. Re:Compensation by GregWebb · · Score: 1
      His fist computer was an Amiga, which explains a lot. Like Apple Mac users, a certain percentage of them believe that computers should all be point-and-click and all users should be able to comprehend and use them without any assistance regardless of the complexity of the task. Not all Amiga or Mac users believe this but some do (hell some "PC" users do, but I believe it's more common for "user friendly" computer users to have this attitude).
      Actually, my first computer was my Dad's Spectrum, but I didn't consider that relevant to the subject sodidn't mention it. So I'm not just a point-and-click user.

      But this does suggest that you haven't spent any significant amount of time using Amigas. Sure, they're more user-friendly than DOS/Windows or *nix, but don't confuse us with Macs. There's very little common ground. There's a very powerful shell and scripting system, it's extremely easy to poke around in the system internals and it's pretty well known by mpost users at least what makes up the internals, if not much more with some. But the Amiga is a very long way from being a Point-and-Click only MacAlike. Part of the reason I still like mine is I think it does an excellent job of being a halfway house between MacOS and Windows, but with many of the benefits of Unix.

      Of course I understand that there are always going to be people who want the insurance due to their perception of the risks (incidentally, that's why there's planty of people with comprehensive rathe than third party insurance - they think it'll save them money if they crash) and companies who are plain jumpy. But both of these are still a function of the actual risk - if the risk is minimal to non-existent, then the number who decide to insure themselves against this risk will decline. Yes, there'll be holdouts, but not necessarily very many. Certainly not enough to fund Red Hat assuming they stick with their current business model.

      I'm not stupid, despite your apparent low (if uninformed) opinion of Amiga owners past and present. But the fact remains, Red Hat's business model provides them with a financial incentive to write poor code and hold Linux back. And you have failed utterly to convince me to the contrary.

      Greg
      --

      Greg

      (Inside a nuclear plant)
      Aaaarrrggh! Run! The canary has mutated!

  137. What the GPL constrains by Brett+Glass · · Score: 1
    As I outlined in another Slashdot post, the GPL differs significantly from all other shrinkwrap licenses. Nearly all shrinkwraps attempt to constrain use; the GPL constrains copying.

    Actually, both types of licenses constrain both use and copying. The shrinkwrap license constrains when, where, and how you can run the software and also generally prohibits you from making copies. The GPL attempts to constrain the ways in which you can use the source on which it has been stamped for your own purposes -- in particular, in code you write for a living. It also prevents you from making copies in some cases and demands that you make copies in others.

    The GPL is, ironically, longer and more complex than most shrinkwrap licenses. Worse still, it is deceptive. It implements an intentionally veiled agenda: the destruction of commercial software businesses. (The "preamble" to the license makes misleading claims about its goals which are belied by Stallman's writings and public statements.)

    --Brett

    1. Re:What the GPL constrains by Chandon+Seldon · · Score: 1

      Normal copyright law would restrict you from distributing copies at all.

      The GPL allows you to distribute copies under certain circumstances - thereby giving you more freedom than you would otherwise have.

      --
      -- The act of censorship is always worse than whatever is being censored. Always.
    2. Re:What the GPL constrains by Brett+Glass · · Score: 1
      Stallman's destructive agenda is very thinly veiled indeed. Read the "GNU Manifesto," in which Stallman openly claims that if he achieves his goals programmers will be no more useful than someone who stands on a street corner and makes funny faces.

      --Brett Glass

    3. Re:What the GPL constrains by Luis+Casillas · · Score: 1
      The GPL attempts to constrain the ways in which you can use the source on which it has been stamped for your own purposes -- in particular, in code you write for a living.

      The problem here is the meaning of the word use. What precisely do you mean when you say "use the source"? Does it mean to compile and run it, does it mean to link the object code it produces to your own code, does it mean to take out fragments and include them in your own source files, and does it mean to take a complete program and make it proprietary? The GPL will restrict your right to "use" a program if your definition of "use" is broad enough.

      If you look at the GPL, it seems to avoid the word "use", and instead talk of "running the program", "distributing the program", and "making works derivative of the program". I just did a grep for 'use' in the GPL, and it doesn't show up in the critical parts. The Preamble (which doesn't really count) talks about "using pieces of the software", which unambiguously refers to copying or linking; Section 2 mentions "interactive use", which unambiguously refers to running a program; Section 3 talks about storage media "used" in the distribution of programs, but to exempt the case from the license, and about scripts used to control or compilation or installation of the program (which are clearly run); Section 8, finally, talks about the "distribution and/or use" of a program being geographically restricted by existed laws (so what constitutes "use" in this case is externally defined by such laws).

      ---

    4. Re:What the GPL constrains by Brett+Glass · · Score: 2
      As you observe, the GPL says -- in effect -- "Some uses are more allowed than others." And programmers, in particular, get the short end of the stick: the uses from which they could benefit most are prohibited unless they give away the farm.

      --Brett

    5. Re:What the GPL constrains by Brett+Glass · · Score: 2
      He goes farther. Stallman suggests banning high pay for programmers so as to encourage them to stay in low-paying jobs -- e.g. in academia. He says:

      For more than ten years, many of the world's best programmers worked at the Artificial Intelligence Lab for far less money than they could have had anywhere else. They got many kinds of non-monetary rewards: fame and appreciation, for example. And creativity is also fun, a reward in itself.

      Then most of them left when offered a chance to do the same interesting work for a lot of money.

      What the facts show is that people will program for reasons other than riches; but if given a chance to make a lot of money as well, they will come to expect and demand it. Low-paying organizations do poorly in competition with high-paying ones, but they do not have to do badly if the high-paying ones are banned.

      --Brett Glass

    6. Re:What the GPL constrains by Luis+Casillas · · Score: 1
      As you observe, the GPL says -- in effect -- "Some uses are more allowed than others."

      Yes, though your Orwelling way of stating it is completely unwarranted.

      And programmers, in particular, get the short end of the stick: the uses from which they could benefit most are prohibited unless they give away the farm.

      And isn't the GPL's point freedom for the users of the software?

      For RMS the user's freedom to use, modify and share software is of prime importance. And he believes that there is no reason why a programmer (or a company) should have a right to restrict a user from using, modifying and sharing software. I don't think he has ever denied this.

      And software, BTW, does not grow in trees-- it is written by programmers, who are only a small minority of the world's people. And new software, or improvements to old software, are constantly in need. It is simply false that programmers would go out of business in a free software world.

      ---

    7. Re:What the GPL constrains by Christian · · Score: 1

      Oh please, Brett. What have you contributed to GNU/Linux lately? If it's more significant than gcc, gdb, emacs, ... (and the existence of the rest of the GNU software) then maybe you have right to spout these ridiculous comments. If, on the other hand, you're just some ZDNET luser, perhaps you should go and bother someone else. Honestly, the objectives of the GNU project are very plain and openly stated. If you don't like them, use another operating system. (btw, this is all very off-topic. the problem is with Debian's license being subverted which doesn't just include GPL software... or do you have a problem with all types of free software too?)

    8. Re:What the GPL constrains by Znork · · Score: 1

      Im sorry, but as a programmer, Im not going to let you get a free ride unless you fulfill my terms. The GPL license protects MY code, and I dont want you going off and using that in closed source marketed software. Just because the code is open doesnt mean you have any special right to it, unless you can fulfill the terms.

      The only ones who get the short end of the stick are those who want to cash in on other peoples work. Thats perfect with me.

    9. Re:What the GPL constrains by Rogain · · Score: 1

      And what does that have to do with the GPL? Is that in the license?

      Do you think its better to be dead that GPL'ed?

      --
      The current Slashdot moderation system is made by gay communists!
    10. Re:What the GPL constrains by talldark · · Score: 1

      Money is nice though (I will go where the pay is highest)

  138. Business sucks, anti-business is a desirable goal by Helmethead · · Score: 1

    Most of the corporately braindead things you spew are not easy to unconvince you of, but I will say this. I, at least, do not agree with the ideals of business. It's selfish, profiteering and soulless. I suspect that alot of other GPL supporters feel the say way. not sure though.

    --
    /* no comment */
  139. We are all businesses by Brett+Glass · · Score: 1
    I do not agree with the ideals of business. It's selfish, profiteering, and soulless.

    It seems to me that this is rather a sweeping condemnation. What about the many good and ethical businesspeople out there? Or, in fact, all of the individuals out there? (In the most basic sense, each one of us is really a business comprised of a single worker.)

    One of the greatest deceptions of the Free Software Foundation is that it goads adherents into attacking "business" as if it were the enemy. But ironically, as Pogo Possum once put it, "I have seen the enemy, and he is us!"

    The GPL creates conflicts by setting one programmer against another. And only the FSF wins.

    --Brett

    1. Re:We are all businesses by Helmethead · · Score: 1
      I think that good/ethical and business are contradicting adjectives and cannot exist together. Probably wrong, but in any case it's no use arguing with me on that front.

      I didn't make my problem with business clear. Business's ultimate goal is to make money. In my view, things of real value get hurt in that process.

      --
      /* no comment */
    2. Re:We are all businesses by kcbrown · · Score: 1
      I do not agree with the ideals of business. It's selfish, profiteering, and soulless.

      It seems to me that this is rather a sweeping condemnation. What about the many good and ethical businesspeople out there? Or, in fact, all of the individuals out there? (In the most basic sense, each one of us is really a business comprised of a single worker.)

      One of the greatest deceptions of the Free Software Foundation is that it goads adherents into attacking "business" as if it were the enemy. But ironically, as Pogo Possum once put it, "I have seen the enemy, and he is us!"

      The GPL creates conflicts by setting one programmer against another. And only the FSF wins.


      There is a sharp distinction between the behavior of an individual and the behavior of a business, and you don't seem to grasp why that difference exists. Perhaps I can explain.

      Beyond meeting the basic needs of survival (which includes providing for his family if he has one), what is usually the primary goal of an individual? Answer: to be as happy as possible. Most people are pretty happy with their situation as long as their needs are being met. There may be things that they feel would be nice to have but which would require too much sacrifice in other areas to achieve. These people will do things like take vacations, play sports, play computer games (well, some of them anyway :-), improve their house, etc., etc. They do many different things in large part because they like to do many different things. They are willing to sacrifice some of their resources to the greater good as long as it doesn't impact their survivability, because doing so makes them feel better. Many of the things they do are because they feel it's the right thing to do...someone else benefits from it and that's a good thing.

      Now, beyond meeting the basic needs of survival, what is the primary goal of a business? Answer: to make as much money as possible for its owners. In fact, my understanding is that the law REQUIRES this of a publicly-traded company. So the business itself is generally willing to do anything it can to make money. If that means tempering its responsiveness to customers (for instance, by limiting the size of the customer support department), so be it. These decisions are NOT made based on whether or not it's the RIGHT thing to do, but on whether or not it's the PROFITABLE thing to do.

      This distinction between an individual and a business is so fundamental that I can't believe you don't see it. Why the hell do you think the most successful companies (to wit: Microsoft) are often (if not usually) the worst from an ethical standpoint? The answer should be obvious: because NOT ONLY do you not have to be ethical to be profitable, it's often UNPROFITABLE to be ethical! As an example, it's often more profitable to kill your competition through out-of-band means (e.g., FUD) than it is to improve your product.

      If you don't believe that, as an individual, the behavior of businesses isn't something to worry about, you need only ask yourself who out there wants to make your private information into a tradeable commodity and is willing to attempt to coerce Congress into passing legislation making this possible. Ask yourself whether it's businesses or individuals who are responsible for the current state of the patent system and who are taking the greatest advantage of it. Ask yourself whether it's individuals or businesses that wish to impede the use of MP3s as a means of music distribution. Ask yourself how many businesses aren't willing to lay off a part of their workforce unless the company will unequivocally die if they don't. Contrast that with how many businesses lay off a part of their workforce regularly only in order to INCREASE the profits, even though the individuals in that workforce depend on the business for their livelihood (i.e., the layoff hurts the individuals being laid off a lot more than the company would be hurt by keeping them). Ask yourself exactly WHO is pushing for the UCITA legislation -- it ain't individuals, that's for sure.


      As for the GPL, you must have some strange ideas of what it means to truly advance the state of the art when, through binary-only publication (i.e., proprietary software releases), those advances aren't made available for everyone to see and improve upon. And I don't know about you believing that it should be your right to use someone else's freely-available code in your for-profit product when you're the only person who will see the profits (you're a business, remember? That means that your goal is maximum profit. Can't achieve that by paying someone for their freely-available code when you can just grab it and use it without paying him a goddamned thing. This is EXACTLY what the GPL is designed to prevent).


      --
      --
      Use 'slashdot stuff' in the subject line in any email you send me if you want to get past the spam filter.
    3. Re:We are all businesses by sheldon · · Score: 1

      Bah, I for one like to eat and have a roof over my head!

      You are certainly welcome to move to China or some other socialist country if you would rather have the government provide for you.

  140. Re:Slashdot's irresponsible "news" reporting by gehrehmee · · Score: 1

    Let's keep in mind what context Slashdot is posted under...
    We have an open-source community, which is based on free and open dialog/development, in the hopes that this environment of constant evolution (positive and negative) will, in the end, benefit the community.
    This wasn't a press-release, it wasn't legal notice, and it CERTAINLY wasn't a call-to-arms.
    Instead, what this post attempts to do is to alert the community to a possible illegality in Corel's license. It didn't ask users to boycott Corel, to burn their WordPerfect CD's, or anything else in the least bit extremist. It was done in the hopes that the error will be corrected, and that, through education of the public, this kind of mistake might not happen so often in the future.

    --
    "You know, Hobbes, some days even my lucky rocketship underpants don't help" -- Calvin
  141. Re:Slashdork jumps the gun, again. by gehrehmee · · Score: 1

    i'll refer you to my post, here.

    --
    "You know, Hobbes, some days even my lucky rocketship underpants don't help" -- Calvin
  142. Trendy dipshit alert! by Anonymous Coward · · Score: 1

    The trendiness siren went off, so here I am to put out the fire!

    So you run an OS based on what other people do or don't do, and not what it does for you? Sounds like you'll be a pox on ANY "community", based on that alone.

    Linux may attact script kiddies, pups, and riceboys (you know who you are), but that doesn't affect MY reasons for using it. Get a clue.

  143. ummm by / · · Score: 2

    Star Division had produced a linux port of star office long before Sun bought them out. If you step out of the past conditional and start talking about future development, then your point would be correct. Still, I would not tie my continuing linux use to Corel if I were you; they have a history of jumping onto bandwagons without following through. Hopefully this time will be different, but such hope is no reason to be rash.

    --
    "If one is really a superior person, the fact is likely to leak out without too much assistance" -- John Andrew Holmes
  144. Re:Lawsuits are inevitable unless we change course by dennisp · · Score: 2

    I agree. Each to his or her preferred license. I'll say outright that I prefer the BSD license and dislike the GPL definition of free -- but I am very willing and happy to reinvent the wheel if I do not agree with the license put forth.

    I think Brett's problem is that he views the GPL as an evil disease that will eventually take over the software industry if not combatted by his presentation of logic. Truthfully though, when push comes to shove, if livelihood is damaged, then people will stop using a particular license.

    There is also no risk of widespread GPL "infection". Really, the GPL, BSD, and some other licenses aren't particularly compatible with many types of software. Really.

    What I don't like, is the license zealots trying to force others into their license preference. If sun were to GPL all their software (their OS in particular) -- as some would have it -- then there is nothing stopping people from integrating that code into linux (or whatever), partly eliminating their hardware advantage, as we could then probably easily scale x86 smp, and whatever else to competitive levels.

  145. Man, don't you see? by Helmethead · · Score: 1
    Not so. In fact, by stamping the GPL onto their code, they have forfeited any hope of compensation for their efforts. They have done so by reducing the market value of their work to zero (users will not pay for the functionality, because they can obtain it for free) and eliminating any opportunity to do parallel commercial licensing. (They don't own changes introduced by others, and so cannot license the latest version for money.)

    This is a perfect example of the business man's inability to grasp concepts foreign to him. You need to spend far less time arguing and pointing out what you see as faults, and far more time reading, and trying to really understand us. Here's a few hints. Compensation does *not* have to mean money We restrict our code with the gpl so that large companies can't take it, market it and sell it under proprietary terms, to make money at the world's expense. This is our compensation, the knowledge that our creations will never be ripped off by some company for their money-making purposes. We resent this activity, yes. Sue us.

    Most of everything else you say is just a difference in perspective, not right or wrong. You say that this lawsuit discussion is a bad thing though, and we freely admit that, it's a mistake. These things happen when people have the values that we have, not when people use the licenses that uphold these values.

    --
    /* no comment */
  146. More business stupidity. by Helmethead · · Score: 1

    what is wrong with zealots and revolutionaries??!?!?!?!?!?! Bad current pratices can't be changed without them

    --
    /* no comment */
  147. slashdot/enquirer ...separated at birth? ;-) by x0 · · Score: 1

    Having read the majority of the posts, it seems to boil down to the following: 1)BP posted an angry letter to a debian mailing list. 2)Slashdot picked up the story and headlined it. So, where does the fault lie? BP has already posted a few times claiming that the post he made was in anger and, he thought, to a relatively obscure Debian mailing list. Somewhere in the mix Slashdot [finds|gets alerted to] that post and runs with it. Like nearly everyone else, I have said things in anger that I wish later that I hadn't said. Fortunately, not being quotably famous, in general the only ones affected by it are those around me. I am not sure what the staffing level of Slashdot is, but it seems that there is at least the need for one additional to do some crosschecking of headlines before they get posted, or at a minimum, that the subjects of the headline get contacted before inflammatory headlines get published.

    --
    In the immortal words of Socrates, who said; 'I drank what?'
    1. Re:slashdot/enquirer ...separated at birth? ;-) by Spirilis · · Score: 1

      LOL. You know, if I was a moderator or was able to be one, I'd mark that one as funny. I think it portrays this situation the best.

      --
      the real at&t mix
  148. Sorry, but I don't like hemlock. ;-) by Brett+Glass · · Score: 1
    Like the man said before, programmers using the GPL *are* asking for compensation, it's just that the compensation is not monetary. Can you not get that through your thick fucking skull?

    Let's examine these remarks (except for that last question there, which is clearly meant to be inflammatory.) We know that programmers who release code under the GPL can't be expecting any monetary compensation, since the GPL works very well to preclude that. So, what sort(s) of non-monetary compensation would someone who opted for the GPL over the BSD or Artistic License want? Let's see:

    1. To feel good about doing the maximum good for one's fellow programmers? Nope; if this were so, there'd be no reason to opt for the GPL over the BSD license. In fact, the code would be more available and see more widespread use under a non-GPL license.

    2. To get credit and respect from other programmers? Nope; there's nothing about the GPL that ensures that the programmer will get any more recognition than if he or she had published under another license. In fact, the GPL can prevent the programmer from getting recognition, since he cannot insist upon being credited for his work in documentation or advertising. (The original BSD license specifically required this.) Furthermore, if the programmer contributes to one of the FSF's "GNU" projects, the situation is even worse. He or she must sign over all rights to the code; it bears the FSF's copyright, not his.

    This leaves only one thing:

    3. To prevent the code from being used by programmers who publish commercial and/or closed source software.

    Bingo.

    But this is an odd form of "compensation" indeed, as the programmer does not benefit from it. In fact, he hurts his profession by undermining software companies' ability to benefit from published source code -- potentially depriving himself of a job in the future.

    So, the only way for our programmer to derive non-monetary compensation from the use of the GPL rather than one of the other licenses is if he or she derives satisfaction from creating handicaps for businesses which could potentially produce good, creative work. At the same time, he must derive joy from hurting his profession and his own job prospects. This is a perverse sort of pleasure indeed!

    Worse still, the GPL drives a wedge between open source and closed source when they should be synergistic. (Those who publish closed source will be less inclined to open it because they are not able to benefit from as much open source -- and because they see open source as hostile to their interests.) This is not something in which I think one should take pleasure.

    --Brett Glass

    1. Re:Sorry, but I don't like hemlock. ;-) by Rogain · · Score: 1

      1. ..... In fact, the code would be more available and see more widespread use under a non-GPL license.

      You seem to think that any use is a good use. I could 'use' a bound print-out of it to hit you in the head, you probably wouldn't like that. People using the GPL have decided that certain uses are counter productive.

      2. ........ Furthermore, if the programmer contributes to one of the FSF's "GNU" projects, the situation is even worse. He or she must sign over all rights to the code; it bears the FSF's copyright, not his.

      Well duh, you're GPL'ing your code. Signing over your rights is how you make sure everyone can always use/extend it. Do you want to GPL code, have others submit patches, help you work on it, etc, then suddenly you decide to declare you're removing the GPL, and now it's your personal property again. I don't think so.

      As far as recognition, I've seen tons of code, with comments like, hey this is mine, if you have questions/comments email them to whoever@where.ever.org blah blah blah.

      This leaves only one thing:

      3. To prevent the code from being used by programmers who publish commercial and/or closed source software.


      You are half-right. There is nothing in the GPL that says your software cannot be commercial, have you ever heard of Redhat? Ever hear about its IPO? The point is to make sure the code is always free, and if someone makes a product, their improvements are available to the community, BECAUSE THEY BUILT ON A BASE PROVIDED BY THE COMMUNITY! If you don't like the GPL, then don't use GPL software. You seem to want to get something for free! The GPL is the price of admission, it gives you so much great software, and helps make sure Free Software grows and is not at the mercy of suits & lawyers.

      So, the only way for our programmer to derive non-monetary compensation from the use of the GPL rather than one of the other licenses is if he or she derives satisfaction from creating handicaps for businesses which could potentially produce good, creative work. At the same time, he must derive joy from hurting his profession and his own job prospects. This is a perverse sort of pleasure indeed!

      I think you're insane. The list of company's making money on GPL software is growing everyday. They often give back to the community: hardware, doc, etc. Many of them employ developers.

      I think the best way to make sure you never have to worry about a housepayment or where your dinner is comming from is to write good Free Software. While reading resumes for a job, you see one with something like "9/8/98 to present -Wrote significant portions of the code for APT." (insert your favorite GPL app). I think that's better than any certification you could take a test for.

      --
      The current Slashdot moderation system is made by gay communists!
  149. Re:Someone moderate this bozo's posts down by DaemonDownTheHall · · Score: 1

    Au contraire! This presents a great challenge and opportunity: a challenge to sway the possibly unswayable, and an opportunity to hone your skills of argument. Which is better: the man who calls for another to be silenced, or the man who shows his opponent to be so utterly wrong that the other man shuts up to avoid further humiliation?

    I urge you and others (no matter what your stance on a given issue) to join in with reasoned, well thought out arguments.

  150. Re:Canadian Law by dbzero · · Score: 1
    I believe your right. But if the kid reaches the age of majority [18] while doing whatever it is he or she is doing then they would become subject to the contract.

    I once took a business law course where the professor illustrated this. If a kid were to purchase a computer system with cash and after three years and before the kid reaches the age of majority, the kid were to take the computer back to the computer store, the computer store would have to refund all of the money. But if the kid reaches the age of majority, the kid will not be able to return the system for refund. Specifically, a minor is not allowed, under the law, to enter any kind of contract; but if the kid reaches the age of majority, the kid then becomes a legal party to the contract. BTW, the business law course I took was in Florida.

  151. Thank you for catching that. by Brett+Glass · · Score: 1
    Stallman actually says this in an essay called "What is Copyleft." Until January 1999, the version of the essay posted on the FSF site said the following:

    People who write improvements in free software often work for companies or universities that would do almost anything to get money. A programmer may want to contribute her changes to the community, but her employer may 'see green' and insist on turning the changes into a commercial product.

    When we explain to the employer that it is illegal to distribute the improved version except as free software, the employer usually decides to release it as free software rather than throw it away.

    Interestingly, in a case of almost Orwellian revisionism, Stallman removed the bit about "seeing green" from the version of the essay that's now published at http://www.gnu.org/copyleft/copyleft.html . He did this after I cited it on a public mailing list as an example of his strongly anti-business agenda. However, the Web remembers: mirrors of the original text may be found throughout the Internet. The revised essay still encourages programmers to incorporate GPLed code in their work as a way of "monkey wrenching" private enterprise, but it is now more subtle.

    It's also worth noting that, shortly thereafter, Stallman changed the word "commercial" (used in the original version) to "proprietary." The shift to the word "proprietary," which has more negative connotations, cleared the way for another rhetorical device: the FSF's claim that Linux can be "commercial."

    I believe that this may not be the only place on the site where Richard has honed his rhetoric to cloak his animus against businesses of all kinds.

    --Brett Glass

    1. Re:Thank you for catching that. by DaemonDownTheHall · · Score: 1

      Interestingly, in a case of almost Orwellian revisionism, Stallman removed the bit about "seeing green"

      I don't see any Orwellian tendencies in that at all. Are you claiming that the FSF is not allowed to change their web pages to make them more palatable to a wider audience?

      The revised essay still encourages programmers to incorporate GPLed code in their work as a way of "monkey wrenching" private enterprise

      No, it still does not. The case it talks about is when a company wants to take the changes made to an already-GPL'ed product and directly violate the license by selling the product without making the source available (clearly illegal). Are you suggesting that the FSF cannot put up a web page that says the blatantly obvious? Or that they cannot put up a page explaining why the GPL is what it is?

      The shift to the word "proprietary," which has more negative connotations, cleared the way for another rhetorical device: the FSF's claim that Linux can be "commercial."

      Once again, your misuse of words hampers your ability to communicate with your audience (if there even is much of an audience left). Communication dictates that you must use language that will be understood by the people you wish to communicate with. I don't speak Swahili to my neighbors, and I don't use "hacker" when speaking to clueless media people. If you wish to define what you mean by those two words, then I shall abide by those definitions for the remainder of this thread. Otherwise, you are bound by the common usage of those terms in this context, which would make your statement both obvious and unrelated to your argument (if a series of isomorphic rants can even be considered an argument).

    2. Re:Thank you for catching that. by Luis+Casillas · · Score: 1
      People who write improvements in free software often work for companies or universities that would do almost anything to get money. A programmer may want to contribute her changes to the community, but her employer may 'see green' and insist on turning the changes into a commercial product.

      I think your reading comprehension skills are lacking in your interpretation of this fragment, Brett. I really don't know whether to hope that you misread intentionally or unintentionally.

      The fragment clearly says "improvements in free software"; that is, it refers to people who improve free software. All that it says it that if Eulalia (to use an archaic name) makes an improvement to gcc while working for Acme Evil Corp., Acme Evil Corp can't release her modified gcc as a proprietary product. In a not necessarily generous "what the heck"-ish expression of futility, they may just allow Eulalia to release her patch as GPL.

      ---

  152. Re:But... by DaemonDownTheHall · · Score: 1

    I am not suggesting that Mr. Glass is benefitting himself or anyone else by his actions. It is myself that I wish to benefit, by creating responses. I would throw them in the bit bucket, but that would preclude Mr. Glass from responding, and thus not allow me to demonstrate the errors of second generation "spew".

    I fully sympathize with the desire to occasionally do the world a favor by taking a complete moron out back and putting a bullet through his head, but that leaves me with minimal target practice, and not enough talking practice. I apologize if I have wasted your time.

    On the other hand, the cynic in mean feels that any Slashdot subthread buried three levels deep is already in the bit bucket, so... ;)

  153. Re:Wow, he's pissed! by DJerman · · Score: 1

    If they're REQUIRED to put such a clause in their license, then they're REQUIRED not to redistribute GPL'd code, since the GPL REQUIRES that the distribution not exclude one or more classes of people (in this case minors).

    --
  154. Lawsuits are inevitable, period. by DragonHawk · · Score: 2

    The GPL, by its very nature, creates conflicts between open source developers and honest businesses ... by putting them at odds with one another.

    That is, unfortunately, an inevitable result of the restrictions the GPL places on how you can redistribute code based on GPL'ed software. Many people like the benefits of the GPL, and they will have to live with those conflicts.

    It doesn't take more than a few minutes' reading at the FSF Web site ... to see the antagonism.

    The GPL has a number of advantages to many people. Just because the people who originated it are somewhat, shall we say, vocal in their opinions, does not mean we should abandon it. When I evaluate the GPL, I look at the words in the license, not the rhetoric on the FSF website.

    Everyone ... would be better off if we adopted the win/win, "live and let livee" approach of other software licenses...

    There is some debate over that issue (to put it mildly).

    People have made the very good point that the GPL helps prevent the forking we've seen with Unix. The lack of restrictions on the BSD license lead to the fragmentation of BSD into tens of free and commercial OSes, all mutually incompatible with each other.

    There is also the "Free Ride" syndrome. The GPL seeks to encourage open source development by preventing people from taking open code and using in their closed products, with no return to those who wrote the original code.

    I often think of this as an alternative form of payment. With commercial software, you pay a fee to use source code. With GPL software, you are required to give something back to the community to make use of the GPL code. You are always free to not use the GPL code, of course.

    The GPL hasn't "forced" the opening of any code...

    You are certainly correct there. The GPL cannot force you to do anything. Again, it comes down to what you are willing to "pay". If you are willing to open your own code, to the benefit of the community, the GPL is fine. Otherwise, you will have to invest time and money in reimplementing what the GPLed code would have done for you. This is no different then any other software license; if you are not willing to pay the price, you don't use the software.

    The reason I say lawsuits are inevitable, period, is because so many are sue-happy these days. What if some company decides that you are using a patented algorithm in your BSDL'ed code? A lawsuit, I am sure. Will the GPL lead to more lawsuits then the BSDL? Possibly. But those who use the GPL will doubtless say that the lawsuits are worth it.

    --

    dragonhawk@iname.microsoft.com
    I do not like Microsoft. Remove them from my email address.
  155. In other words, you're just arguing to argue. by Brett+Glass · · Score: 1

    Sorry, but I don't have time for that. Bye.

  156. BSD "forking" a myth. But Linux forks abound.... by Brett+Glass · · Score: 1
    People have made the very good point that the GPL helps prevent the forking we've seen with Unix. The lack of restrictions on the BSD license lead to the fragmentation of BSD into tens of free and commercial OSes, all mutually incompatible with each other.

    Actually, contrary to Raymond's "Halloween document," there hasn't been a new fork of the BSDs in several years. However, there are now a couple of dozen forks of Linux, and more are appearing all the time.

    The truth is that there is absolutely nothing about the GPL which does anything to prevent forking. However, the culture of the various BSD projects -- in particular, their greater willingness to share code -- has done a great deal to discourage forking. Hence, the fragmentation of Linux into many incompatible distributions.

    --Brett Glass

  157. There's a paranoid interpretation... by Mr.+Gus · · Score: 1

    Err, regardless of his overall intents, that single quote does not, IMHO, promote "sabatoging" a company's work. All it says is that if Entity A writes a free, open-source program, and Sally (employed with A) contributes code under the pretense that *her* code is free, Sally herself should retain rights to her code.

    The situation is both idealistic and a tad unrealistic, but it's not expressly to undermine the company's efforts. Sally doesn't want to find some GPL'd bit of code to ruin the commercial release of her company's product-- she just doesn't want her own code used for purposes other than the one she had in mind when she wrote it.

  158. Corel EULA by kamakazi · · Score: 1

    The EULA may specify 18 or older, but the Corel Public License on the source makes no such license. I guess this means that the only minors allowed to download this stuff are the ones with the experience and know-how to build and compile it themselves.

    --
    "Proximity to wonder has blunted our perception and appreciation of it" --Tim Hartnell in 'Exploring ARTIFICIAL INTELLI
  159. Defending The Nature of Slashdot by Horizon · · Score: 1

    People, you severely misunderstand slashdot.
    Slashdot is not your grandfather's news service.

    Firstly, the majority of its content is derived from outside sources. Not in terms of taking a source and basing something on it, but really just providing a pointer to it.

    Secondly, slashdot gives away old notions of editorialism. Completely, out-the-window. I think we all know that now. It's not a newspaper, and it doesn't try to significantly 'back up' any news posted. The news comes as-is.

    It is these properties that make slashdot a real marketplace in information. It's a real laissez-faire thing; caveat emptor is very much the rule of thumb. If anything, slashdot holds a closer resemblance to its historical precedents (mailing lists and usenet) than to any 'real' news group.

    This gives it a distinct disadvantage for certain people: ye gods, you actually have to think. Heavens forbid such an awful imposition on you poor suckers. You actually have to take your mouth off the teat and realise that slashdot is fallible, and that it should always, always be taken with a grain of ionised salt.

    Suddenly you may realise this is true of every single thing you have ever heard, ever read, ever known. All of it is subject to bullshit. If anything, I am more prepared to rely on slashdot. Why? Not because of some long-winded document about editorial method. I prefer to rely on the collective brainpower of people whose job it is to think about things. They will surely fuck up, but at least they will argue first.

    If the price of freedom is eternal vigilance, then the price of truth is eternal criticism.

    be well;

    JC.

    --
    -- The opinions expressed are not necessarily those of the fictional entity who may or may not have expressed them
  160. Re:Lawsuits are inevitable unless we change course by sh_mmer · · Score: 1

    DaemonDownTheHall wrote:

    The GPL enforces sharing, the BSD license expects the other person to want to share.

    --end quote--

    contraire. BSD expects nothing at all. people who use the BSD are not negotiating for the same kinds of things that people using the GPL are negotiating for. they are simply giving their code to the world. end of story. to say that people expect 'sharing' in return is to miss the point.

    sh_

    --
    Interested in learning Chinese or Japanese? check out Chinese/Japanese-English Dictiona
  161. Corel can do okay by craw · · Score: 2
    Another tempest in a teapot. Corel can easily save face and win nex converts if they respond to this "crisis" in a the proper manner. If they made a mistake, the they should say so in a gracious manner. Like Bruce said, mea culpa. If Corel has a legitimate point, but if it is not in keeping with the spirit of the GPL, then they should explain their decision. A stupid mistake would be to hide behind the wall of the legal system. If Corel mainly uses this, then they don't understand, nor appreciate, the open source concept.

    If Corel does the right thing, then could come out of this thing like angels. Remember when IBM went after CmdrTaco for trademark violations? After the storm receded, IBM clearly explained their view; /.'s logo was not correct. But here's the correct logo, and /. is clear to use it.

    Billy Carter was right.

  162. "Copyleft" versus "Free Software" by Horizon · · Score: 1
    Let's be completely clear here: What RMS calls "Free Software" and what he calls "Copylefted software" are two related but seperate concepts.

    Free Software has certain rights protected for the user. He wrote:

    ``Free software'' refers to the users' freedom to run, copy, distribute, study, change and improve the software. More precisely, it refers to four kinds of freedom, for the users of the software:

    • The freedom to run the program, for any purpose (freedom 0).
    • The freedom to study how the program works, and adapt it to your needs (freedom 1).
    • The freedom to redistribute copies so you can help your neighbor (freedom 2).
    • The freedom to improve the program, and release your improvements to the public, so that the whole community benefits. (freedom 3).
    A program is free software if users have all of these freedoms. Thus, you should be free to redistribute copies, either with or without modifications, either gratis or charging a fee for distribution, to anyone anywhere. Being free to do these things means (among other things) that you do not have to ask or pay for permission.

    I refer you to the original article for more detail.

    Copyleft inherits all the properties of Free Software and adds another one: that Copylefted software must only be combined with other Copylefted software; and that non-Copylefted software becomes Copylefted if combined with Copylefted software.

    This is the 'viral' clause of the GPL. It is the clause which causes the most angst and anger out there. I've criticised it myself as Freedom From Above; akin to 'liberation' by the Red Army (you are Free, under our terms).

    But be very, very clear on this: while all Copylefted Software is Free Software, not all Free Software is Copylefted Software. Just today, I got an email from RMS in reply to a question of mine:

    One thing that is *not* clear to me is the FSF's position on the modified BSD license (minus the advertising clause).
    Both versions of the BSD license count as free software.

    However, the BSDL is not necessarily a GPL-style Copyleft license.

    That's enough of my preaching for now.

    be well;

    JC.

    --
    -- The opinions expressed are not necessarily those of the fictional entity who may or may not have expressed them
  163. Bruce is right! Arm yourselves! by gregm · · Score: 2

    Assuming that Canadian law demands that Corel discriminate against minors:

    Read section 7 of the GPL, here's an excerpt.

    "7. If, as a consequence of a court judgment or allegation of patent infringement or for any other reason (not limited to patent
    issues), conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this
    License, they do not excuse you from the conditions of this License. If you cannot distribute so as to satisfy simultaneously your
    obligations under this License and any other pertinent obligations, then as a consequence you may not distribute the Program at
    all."

    Seems pretty straightforward to me. My interpretation:

    If you can't follow the rules for whatever reason you can't play.

    Section 8 says:

    "8. If the distribution and/or use of the Program is restricted in certain countries either by patents or by copyrighted interfaces,
    the original copyright holder who places the Program under this License may add an explicit geographical distribution limitation excluding those countries, so that distribution is permitted only in or among countries not thus excluded. In such case, this
    License incorporates the limitation as if written in the body of this License."

    Now if Corel won't or can't change their EULA then we must act swiftly and brutally. If we give an inch, we set precedent that will eternally weaken the GPL. If Canada is indeed the culprit then Section 10 might be a way out for Corel:

    "10. If you wish to incorporate parts of the Program into other free programs whose distribution conditions are different, write to
    the author to ask for permission."

    If Canadian law isn't the bad guy here and Corel is just totally clueless then we need to be hit them as hard and as fast as possible because they're testing the waters. According to many of the articles here on slashdot we're loosing our rights left and right :) We're loosing these rights IMHO because we're too lazy to keep our governments at bay. Same thing here people if we let this slide then Corel or someone else will keep chipping away at the GPL like the American government has been chipping away at constitution of the US.

  164. He practices what he preaches by Helmethead · · Score: 1

    ... he just considers you too much of a lost cause to try and convince you of his view.

    --
    /* no comment */
  165. Re:here they come. nail in the coffin by Anonymous Coward · · Score: 1

    People who casually violate copyrights are the sort of cheapskates who don't give a damn about licensing as long as they can get away with whatever the hell it is they're trying to do. People who advocate the GPL want to change the way the industry works, and we take rules very seriously (or we wouldn't care which ones are used!) I think you'll find the two groups don't overlap much at all. Some cheapskates use GPL'd code just because it can be had cheaply, but the real advocates want to pay fairly for labor.

  166. Re:A prime example of Slashdot CENSORSHIP by whois · · Score: 1

    "back of the bus" was never censorship, it was racism, and no matter how you try to sell it I don't see how moderation equates to racism. Comments are moderated by real-life people, they aren't infallible, but I think that most people try hard to be fair when moderating. I also think, that like the BBSs of old days, this is a free site with free access. On most BBS use was a privilege, not a right, and even though Slashdot now runs on Andover's hardware, I still think it's a privlidge extended to all of us to be here. In other words, free speech, censorship, and racism be damned, if you don't like the opinions expressed here, you can go elsewhere. If the community, or the site administrator doesn't like those opinions, they can moderate them down.

    I also think that its common curtosy to express opinions such as these to CmdrTaco and Hemos via email instead of publiclly flaming their ability to moderate. I seem to recall months of open-forum discussions regarding the best way to moderate, and who should moderate, or if moderation should be practised at all. They have put alot of time and thought into this system, but I believe they would still be open to ideas for improvements.

    Having said all that, I usually have moderation set to -1 so that I can see all of whats said in a discussion. Sometimes things are mis-moderated, and sometimes I find little pearls of wisdom in what is otherwise pure flamebait.

    whois

  167. Legal status of GPL by Anonymous Coward · · Score: 1

    Bruce Perens was wrong, admitted it, Corel won't be sued, and this discussion has once again raised many interesting points about the legal status of the GPL that need ampler discussion in some other forum.

    As one poster put it, the GPL is a license that must be fulfilled exactly, else the user has no rights, and the original copyright prevails to prevent further use, modification, copying, or distribution.

    Unanswered is how to resolve technical legal problems not foreseen when the GPL was drafted. The Canadian lawyers for Corel evidently believe it would be prudent to put in the EULA a clause about minors. Many Slashdaughters say that would violate the GPL. But if a corporation is to work with the free software movement and still stay inside the laws of its own country, it might need to add in its EULA some statements not fully covered in the GPL.

    The alternatives don't look good. Either commercial companies can try to help produce and distribute Free Software under GPL (and risk violating some laws not covered by GPL), or they can forego GPL code and turn to other licenses such as BSD (as Bret Glass eloquently argues), and stay within prudent commercial practice.

    I don't think at all justified the position of many here on /. that Corel and other companies are only in the business of making money and don't care about the Free Software developers. I would hate to have Corel people think that these posters represent the entire Free Software movement.

    If Free Software and GPL advocates wish Corel and other companies to be part of the movement, then they need to work more closely with these companies, and in a more professional manner. Uninformed and wild arguments on /. will not suffice. Instead, FSF should appoint a lawyer to meet with Corel and other companies and render some reasonable advice. Bruce Perens was supposed to have been doing that, but it seems the communication has badly broken down. It's time to get it going again, but not here on /.

    Hemos, please feed these ravaging dogs some other meat to keep them occupied while saner minds work on the real problems.

    1. Re:Legal status of GPL by Todd+Knarr · · Score: 1

      But if a corporation is to work with the free software movement and still stay inside the laws of its own country, it might need to add in its EULA some statements not fully covered in the GPL.

      But not where they contradict the GPL. If the company needs to distribute GPL'd software under terms not compatible with the GPL, then it has two choices:

      1. Contact the copyright holders of the software and negotiate a different license.
      2. Do not distribute the software.
      Whether the GPL is convenient for a corporation or not is irrelevant. It's purpose is to prevent the addition of clauses like the one Corel imposed. Corel is free to impost their terms on their software, but not on anyone else's without that party's permission. Were I to have redistributed Corel's software under terms not compatible with their license to me, they would have had their legal department contact me and their position would have been very non-negotiable: cease doing that immediately or face legal action. I see no reason to apply any different standard to them than they would apply to me.
  168. man that's just BS, read this by Helmethead · · Score: 1

    if this article doesn't tell you otherwise, you are 100% unreasonable

    --
    /* no comment */
  169. Re:Lawsuits are inevitable unless we change course by dennisp · · Score: 2

    When I see GPL software taking over traditional software such as quicken, notes, photoshop, anything with a limited market and high profit margins and/or very complex software, any number of productivity business solutions, industry specific software such as 3d studio max, lightwave, and softimage, I might believe you. Until then, no way. Things like games, of course, will likely always remain closed.

    Visiting freshmeat, there aren't many particularly innovative products. You can find anything there, and 100x better in the commerical software world. This may just be because this way of doing things is in its infancy, but I wouldn't hold my breath. There are only so many things that can be done in this recipricol or symbiotic manner. This becomes particularly apparent when making typical easy to use end-user software.

  170. READ THE GPL, for God's sake. by Luis+Casillas · · Score: 1

    Implicit in this is that I must insure that the person I'm passing the code to must uphold (or at least legally agree to uphold) the GPL. If they cannot, or willnot, I cannot pass the code to them, since I would be responsible for breaking my contract.

    This is utterly false.

    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. You are not responsible for enforcing compliance by third parties to this License.

    ---

  171. Re:Lawsuits are inevitable unless we change course by Brett+Glass · · Score: 1
    Your sweeping generalizations are unfair. Most programmers and software companies -- myself included -- take great pains to do good work. On the other hand, under the GPL, there's a TOTAL disclaimer of ALL liability. So much for "lemon laws!"

    Frankly, I'd favor such laws so long as they applied to the cash-rich FSF.

    --Brett Glass

  172. Re:Clueless Hemos by Runna^Muck · · Score: 1

    airing one's bottomless ignorance in public is, well, stupid?
    Like you're doing? Hemos helps run the place ya fucking moron.

  173. Re:Slashdork jumps the gun, again. by Runna^Muck · · Score: 1

    It's only a flame magnet if you make it one. Rob, Hemos et al, just put it up, it's the readers who turn it into a free for all. Some folks just need to think twice before hitting the submit button. Yeah like that'll happen.

  174. Re:Slashdot's irresponsible "news" reporting by Runna^Muck · · Score: 1

    I think you are confusing "Slashdot" the web site with "Slashdot" the morons who post. What are they supposed to do? Look at every story submission and run it through some filter and try and guess how people will react? Bullshit. People need to think for themselves, take responsibily for themselves and stop blaming Hemos, or whoever who posted the story for the comments it generated. Christ.

  175. Re:Yep, it was another Hemos article, too. by Runna^Muck · · Score: 1

    I wish Slashdot would dump AC's.

  176. Re:here they come. nail in the coffin by norton_I · · Score: 1
    1) I haven't threatened anything. I said I could see the justification for filing a lawsuit.

    2) If you are going to accuse me of pirating software, you better have some proof to back it up. I may have some unregistered shareware around, but not that I can think of. I have even pirated some software in my time. But in general, I have paid for most or all of the commercial software I use and quite a bit that I don't. Honestly I don't think about it a lot, since these days most all of the software I use is free.

    3) "You set unenforcable EULA's that unfairly restrict the use of your software for legitimate purposes by legitimate customers, make unresonable demands of customers simply because they have no other choice, yet when I make a few simple rules to prevent you from exploiting my hard work, and you are unwilling to follow them? Grow up"

    4) Me as an individual breaking a license agreement for personal use is much different than Corel as a company breaking a license for commercial gain. If Corel was distributing NT in violation of MS's EULA, you can bet that they would have filed suit immediately. They are not likely to go after me, even though I illegally transfered my copy of OEM copy of Win95 to a new machine when I upgraded my computer. Horrors!

    5) I bitch and moan about MS because I think they behave unethically and unprofessionaly to force merchants and vendors into enforcing their monopoly. But this is just my personal opinion. I generally avoid thrusting it upon people unless provoked, and in any case has no bearing on law. The GPL and any commercial EULA are both legal documents, and while the ability of them to bind is certianly disputable, that is a matter that can only be settled by a court.

    6) As I said, I am leary of filing a lawsuit against Corel, especially when I think they are trying to do the right thing. But I would rather see Linux never gain the kind of broad appeal I hope people like Corel can bring to Linux than have the freedom on which it was created be abridged.

  177. Re:Slashdot's irresponsible "news" reporting by Runna^Muck · · Score: 1

    What makes you think Slashdot is journalistic in any sense? They are a "portal" and "forum". When is the last time you've seen Slashdot break a story, researched, full text, etc etc? 99% of it is links to other sites where presumably the story has been researched, edited, passed by the lawyers etc. That's the portal part. Then when you're done reading the article you come back here and post a comment, or a comment to someone else's comment. That's the forum part.
    Remember this is "News for Nerds" and "Stuff that Matters" not "News we hope everyone will agree with and post really nice things about Linux and generate good press". Neither Hemos or anyone else can predict how people will react to a story. They just post it, and at the time it was posted Bruce was contemplating a lawsuit. It isn't incumbent on Hemos to contact Bruce and ask "are you serious? Are you really gonna do this?"
    As for Corel, I don't know if they've done anything wrong or not but I've seen enough problems reported that unless their distro cleans my apt and sucks my dick, I won't bother with it.

  178. Re:Sue Andover? by Runna^Muck · · Score: 1

    Sued for what? They posted a story, I'm sure they can come up with the message that prompted it on the mailing list. Not their fault if someone else picks up on it, and not their fault if people post out their ass.
    I'm thinking of renaming it "AC's are idiots, Shut the fuck up."

  179. Don't forget his default score by ToastyKen · · Score: 1

    Actually, he can get at most 3 karma points per post because he has a default score of 2.

  180. Re:Slashdot's irresponsible "news" reporting by platypus · · Score: 2

    In an ideal word you were right, unfortunately here someone from could easily construct an article with qoutes from slashdot which would give a very negative impression about the whole thing.
    Think of a headline like "Prominent open source advocat threatens to sue corel corp.".
    I know this could happen with other slashdot articles too, but in this case it's so easy for a clueless reporter to f*ck up.

  181. Why I disagree with your disagreement by ToastyKen · · Score: 2

    I'm a pretty big fan of free speech, and I can tell you why I do NOT believe /. moderation is censorship.

    Slashdot is not suppressing anyone's opinion to the point of making them unheard. It's merely giving you a suggestion.

    Do you have a problem against positive moderation? I think it's one of the most useful systems I've seen. Do you think it's also censorship because increasing the score of one post inherently devalues the other posts to some degree (since the more high-score posts a person reads, the fewer normal-scored posts they're likely to read).

    Think of -1 scores not as negative scores, but as giving everyone else a positive score.. In a way, it's just saying, "I think everything else is more worthwhile than this."

    Imagine if we all started out with default thresholds of -1, and people had to manually set their thresholds to 0, just like some people set their thresholds to 2 or 3 or more. Do you still think that'd be censorship?

    But the main point remains that you can very very easily read the -1 comments, and thus they are not being suppressed. In fact, quite to the contrary, Slashdot employs multiple mechanisms to facilitate your reading -1 comments. That's hardly suppression!

  182. Re:Slashdot's irresponsible "news" reporting by platypus · · Score: 2

    From Marriam-Webster dictionary:

    Main Entry: journalism
    Pronunciation: 'j&r-n&l-"i-z&m
    Function: noun
    Date: 1833
    1 a : the collection and editing of news for presentation through the media b : the public press c : an academic study concerned with the collection and editing of news or the management of a news medium
    2 a : writing designed for publication in a newspaper or magazine b : writing characterized by a direct presentation of facts or description of events without an attempt at interpretation c : writing designed to appeal to current popular taste or public interest

    They don't mention the need to do background research, I fear that is your idealistic interpretation of the word.
    You can't avoid it, even when you post just links to other news-stories, you are still _selecting_, that means editing, and that means journalism.
    I guess you and me wouldn't be reading slashdot if they would emphasize on windows nt success stories.

    And - this special case wasn't even one of the 99% you mention.

  183. You're dead wrong on copywrite law by alexhmit01 · · Score: 2

    Trademark Law and Copywrite Law are VERY different. There is NO dilution of a copyright, like there is with a trademark.

    Trademarks protect a company that utilizes a name from others profitting on that good will. If the term ceases to be specific to the company, than it is considered diluted and not trademarked.

    This does NOT apply to copyrights (or patents, another point that ./ers miss). If I create an artistic expression, it is copyrighted. It is MY work. I can do whatever I want. I can license it as arbitrarily as I want, because it IS mine.

    If I create a name for my business that becomes synonymous with the industry, then that word no longer refers to my business, so my trademark goes away.

    Do you understand the difference? It doesn't matter if the copyright owners do nothing 90% of the time and everyone on /. says "do nothing," if any copyright owner complains when his copyright is violated, he can sue. There is NO concept of dilution of a copyright.

    Alex

    1. Re:You're dead wrong on copywrite law by Chris+Johnson · · Score: 2

      I don't agree that it's that guaranteed. Perhaps what I'm saying is that I don't have the faith you have that this is the case- especially when we're talking about a community-used license going up against the lawyers of big corporations. You do realise that if (to use the most extreme example I can think of) somebody bribed the judge to make an exception and find the GPL 'not really a license', in other words defining it by usage rather than by the language, that would be the legal precedent? I really, really don't have the faith in the virtuous and incorruptible judicial system you do. I'm damn glad it works as advertised a lot of the time, but I'm simply not ready to assume that people can use the GPL differently than the wording of the license and not raise the question of later consequences. I think we will have to disagree there.

  184. reaction by harenet · · Score: 1

    I can understand Mr. Perens' reaction, as I have suffered the same in regard to feeling the need to protect a concept.

    One defense is that we are so innundated with corpirate BS, that we can be left suspicious of every action by any1 that is connected to megaslothism.

    It is clear that Mr. Perens has worked VERY hard (understatement) to promote/protect the concepts of o-s. He should be able to feel proud of his efforts, and not be judged per incident. same goes for Mr. Stallman, & Mr. Raymond. Obviously, peoples' emotions/personalities, are exposed in their efforts to work towards goals. look at FUDbilLIEgates.

    Experience that evokes my empathy:

    Last year, sensing the rise in (commercial) popularity of linux/o-s/gnu, and the corresponding onslaught of MS BS PR trashing, of the concepts/community, I felt inspired to do some protectionary things.

    I registered a whole bunch of linux/o-s related .coms/nets/orgs, with the main goal of keeping deceptive megasloth greedmongers from getting them. I then offered their use, for advertising/information to any/all in the community for free. I figured that I would at least break even on the expenses (enormous, and growing), and serve to promote the concepts that offer an alternative to megasloth greedmonger control of all that is PC.

    Well, the results were/are less than stunning. However, i have managed to retain control of a whole bunch of urls, and HAVE NOT succumbed to the sizable offers of fortune from the deceptive marketeer community.

    Anyway, the moral to the story, to me, is: all form of GOOD intention can be misconstrued, when negative judgement is applied, based on suspicious reaction due to preconceived notions, that are inaccurate.

    doesn't mean I'm going to start trusting in the kingdumb of fud.

    We haven't changed a bit in what we are attempting to accomplish, which is promotion of the concepts of gnu/linux/o-s. any positive input is appreciated. we've already heard ALL the reasons why knot.

  185. You are being silly... by Per+Abrahamsen · · Score: 2
    The GPL doesn't create conflicts. It demonstrates, like all licenses, that conflicts of interest exists. If there were no conflicts of interest, there would be no need for licenses.



    The conflict of interest that justify the GPL, is the interest of (some) free software programmers to ensure that all public enhancements to their code remain free, as opposed to some companies interest in keeping their enhancements to the code unfree.



    One way to resolve this conflict would be, as you suggest, for the free software programmers to give up their right, and let these companies keep their enhancements unfree. This particular brand of conflict resolution is called "unconditional surender."



    Another way to solve the conflict would be to note that the interest of the free software programmers are in no way helped by the unfree enhancements, while making free enhancements have proven valuable to many companies. This leads to to potential conflict resolutions: One is that the company ignore the free software, in which neither part have lost anything. The other is that the company makes free enhancements to the code, in which case both parts win.



    This later way of resolving the conflict is, to me, much prefereable than your suggestion which basically amounts to telling the free software programmers to "bend over and let them bugger you".

  186. Re:ANTI-LINUX POSTCARDS HERE! by Russ+Nelson · · Score: 1

    I love FreeBSD marketing: Look! We are evil! We have a devil for a mascot!

    Old-Unix (*BSD) partisans never understood marketing--and they still don't.
    -russ

    --
    Don't piss off The Angry Economist
  187. Re:Slashdot's irresponsible "news" reporting by Fuhrer · · Score: 1

    I agree with this definately. I submitted a news item saying that Windows 2000 RC3 had been released. Not only was my news rejected, but Slashdot never posted the story *at all*.

    If a major Linux distro kicked out a new beta, Slashdot would be throwing out news itemsjust like spammers throw out junk mail.

    Is Slashdot really "News For Nerds." or is it really "News for Linux Junkies"

  188. License by dodobh · · Score: 1

    Why don't we write a EULA and post it to Corel (and any other company which wants it)?. This should clear out the boiler plate that Corel is currently using.

    --
    I can throw myself at the ground, and miss.
  189. Re:Lawsuits are inevitable unless we change course by GregWebb · · Score: 1
    The moral and ethical thing to do would be to get a job actually doing something and work on your browser enhancements in your spare time. That way, you could do the blind community a great service and still be able to support your family.
    Come on, we all know this is ludicrous...

    Coding is "doing something". Anyone who tells you otherwise is either a liar, insanely talented or has never written a line of code in their lives.

    I don't know this guy or his work in detail, but from the crash course in this thread, the GPL is clearly harming the blind community. Were the relevant code released under a BSD-style license or as true FD/PD, they could take it, build in the necesssary bits for the blind users and release it. As it is, they're having to reimplement the GPL'd sections. Net result? More work, so the blind community has to wait longer and pay more for the software they need to fulfil a task we take for granted.

    Yes, he could work on this in his spare time but it would take how long? Y'know, some people do have lives. Could I (or anyone else, for that matter) seriously spend as long on a project in my spare time as I could if I was being employed full-time? No way. I need to sleep, eat and do certain household tasks. If I want to stay sane I hae to relax periodically. I'm lucky if I can devote a few hours a day to this sort of thing, frankly.

    What Brett appears to be attempting is entirely legitimate. The GPL, for all its claims of promoting freedom, is holding him back in this endeavour and is forcing higher costs on to a disadvataged minority's information access. To be blunt, in this case and from what has been said in this thread, the GPL is hurting the blind.

    Greg
    --

    Greg

    (Inside a nuclear plant)
    Aaaarrrggh! Run! The canary has mutated!

  190. You have nailed it! by Brian+Knotts · · Score: 2
    I don't spite, nor begrudge my colleagues, Brett. Rather, I say, use what works for you. You, on the other hand, *DO* begrudge any and all who use the GPL. You insist that all people coding open source software release it in a way *YOU* can take and make money on. I don't suppose you feel any desire to then funnel a fair amount back to the coders, do you? No. You'd rather that coders just give you stuff, to hell with their rights, time, etc.

    This is one of the best summaries of how the anti-GPL people come off to GPL people. They rant and rave about "freedom," when in fact what they really want is the "freedom" to restrict what others can do with software (i.e., restrictive binary licensing). But, what's worse is that they want a free ride from Free Software authors while doing so.

    If that isn't downright despicable, I don't know what is.

    Look, I have no problem with the BSD License, and similar licenses, as a general rule. It's not what I prefer, but I understand that some people prefer them. The GPL advocates I see posts from seem to feel the same way Now, if we could just get the remaining few rabid anti-GPL advocates to take the same view, everyone can be happy.


    Interested in XFMail? New XFMail home page.

  191. Re:You're ignoring reality by GregWebb · · Score: 1

    Interesting title :)

    Business is accepting GNU/Linux as it's visible, a headline-grabber and (currently) appears to be superior in the things they care about to *BSD. Cost is also a factor, but not a huge one as purchase price is a pretty small fraction of TCO.

    Business is actually very nicely served by BSD, simply as it allows them to release their own version. There is, after all, closed-source commercial software with a BSD-licensed base.

    Business doesn't prefer the GPL as a license in the main, it's simply that they've heard of this strange system called Linux, which is rapidly developing a network effect. But how many have heard of BSD?

    Greg

    --

    Greg

    (Inside a nuclear plant)
    Aaaarrrggh! Run! The canary has mutated!

  192. I have seen the light. All business is e-vile! by Brett+Glass · · Score: 1
    After reading your posting above, I have seen the light. All business is Necessarily Evil Incarnate. There is no such thing as a responsible or caring business, business owner, or entrepreneur. All software vendors everywhere, and all programmers who don't embrace the GPL and give away all of their work, are clearly only out to exploit users. Programming is an evil occupation and must be stomped out. Let's ban high salaries for programmers and destroy their jobs!

    Yeah, right!

    --Brett Glass

    1. Re:I have seen the light. All business is e-vile! by kcbrown · · Score: 1

      After reading your posting above, I have seen the light. All business is Necessarily Evil Incarnate. There is no such thing as a responsible or caring business, business owner, or entrepreneur. All software vendors everywhere, and all programmers who don't embrace the GPL and give away all of their work, are clearly only out to exploit users. Programming is an evil occupation and must be stomped out. Let's ban high salaries for programmers and destroy their jobs!

      Yeah, right!


      I don't dispute that there are some small business owners and entrepreneurs that are inclined to do the right thing even when unprofitable. THEY AREN'T THE PROBLEM. And they aren't terribly successful, either, are they? Not compared with behemoths like Microsoft, AT&T, Intel, etc.

      If you believe so strongly in the ethics of business then YOU tell ME why we have all those problems caused by business I outlined in my previous article.

      It's not my belief that all businesses are inherently evil or anything. To be evil is to take joy in the suffering of others. But I will contend that most of the larger ones, and perhaps most businesses in general, are amoral essentially by definition. It's the natural consequence of your primary (if not only) goal being to maximize your profit. In short, many (if not most) businesses don't give a shit about anything except their bottom line.

      If I write some code and let the rest of the world use it, I can generally rely on the individuals out there who improve it to release their improvements back to the community. Most of the programmers out there in my experience tend to want to do that since they aren't in it strictly for the profit. I can't rely on businesses to do the same. Why? Because their improvements give them a competitive advantage! Duh! You wouldn't want to give up your competitive advantage if you're a business, would you? Just so that others can use your improvements freely and perhaps gain a competitive advantage over YOU? Didn't think so.

      And yet, that seems to be exactly how you expect most businesses to behave, based on your previous articles. How naive can you get?


      Because of that, I'll use the GPL (or, in the case of libraries, the LGPL) or something similar to insure that my code AND ALL CHANGES TO IT remain free. It really sucks that I have to resort to a license to insure this, but it's the only way for me to INSURE that the code remains free. Otherwise some capable business can come along, snag my code, improve it enough that people will prefer to use their version instead, and never release the improvements back to the community because they want to maintain their "competitive advantage". The state of the art DOES NOT improve in that situation, now does it?

      You complain that the authoring of GPLed code forces you to reimplement that code in order to use it in your proprietary product. Well I will complain that the fact that YOUR code is proprietary to begin with forces ALL THE REST OF US to reimplement it ourselves just so we don't have to wait around for you to get around to fixing your bugs because you're too busy implementing snazzy new features. After all, it's the new features that sell, not the fixed bugs, right? Microsoft should be sufficient proof of that to you. And you're a business, so you'll do whatever generates the most profit, right?

      So: on one hand we have a few businesses that are "disadvantaged" because they have to reimplement something that already exists in GPLed form. And on the other hand we have the ENTIRE REST OF THE COMMUNITY that has to reimplement proprietary code in order to extricate itself from the support nightmare that proprietary software is famous for. Gee, it's real tough for me to decide which of the two needs is more important in the long run...


      I suspect it's because you ARE a business, and can only see your own needs, that you are having so much trouble with this. It would be nice if you could see and acknowledge the needs of the rest of the world. Perhaps then you would understand why a license like the GPL is a good thing to have available and why it has advantages in many situations. And why it may be the best thing for the world at large in the long run.


      Oh, by the way, I don't think you need to worry about programmers going hungry. Not as long as there's a need for new software. See, not all types of software get implemented by an individual hacker in his spare time. Many are implemented as a result of a company's specific needs. If that company wants the software to be implemented, they have two choices: wait indefinitely for someone in the community to do it on their own initiative, or pay someone to do it. I doubt they'd elect to wait if it's something they need. Interestingly enough, it's pretty reasonable to suspect that the software will be cheaper to implement if the programmer can GPL it (advantages: he can use any existing GPLed software as a foundation, and if the program is useful enough he can get the community to help in the development). But the programmer still gets paid either way.

      I also don't think you have to worry about programmers becoming commodities. A commodity is something that can be replaced at will. The very nature of programming is such that this won't happen: even the best programmer can't replace another and become instantly productive. It may take quite some time for him to become familiar with the existing code and the reasons for its current state. This makes an individual programmer (as long as he's reasonably good) valuable.


      --
      --
      Use 'slashdot stuff' in the subject line in any email you send me if you want to get past the spam filter.
    2. Re:I have seen the light. All business is e-vile! by Brett+Glass · · Score: 1
      Yep, just as I thought. Microsoft is a business. You are in business. Therefore, you are Microsoft.

      All business is evil; making money from one's creative work is evil; failing to give away one's entire output for free is evil.

      Thank Heaven for the GPL. One line of my code in your application, and I have the God-given right to prevent you from making any money off of your evil scheme.

      I'm really beginning to see the light here. Let's monkey-wrench all of those evil businesses with the GPL. They'll never make a dime! They'll go out of business! They'll die like the bastards they are!

      Sure.

      --Brett Glass

    3. Re:I have seen the light. All business is e-vile! by kcbrown · · Score: 1
      Yep, just as I thought. Microsoft is a business. You are in business. Therefore, you are Microsoft.

      All business is evil; making money from one's creative work is evil; failing to give away one's entire output for free is evil.

      Thank Heaven for the GPL. One line of my code in your application, and I have the God-given right to prevent you from making any money off of your evil scheme.

      I'm really beginning to see the light here. Let's monkey-wrench all of those evil businesses with the GPL. They'll never make a dime! They'll go out of business! They'll die like the bastards they are!

      Sure.

      Wow, you sure are doing an awesome job of addressing my arguments. Are you always this impressive? It sure takes a brilliant mind to equate "evil" and "amoral". You have to be equally brilliant to equate an individual and a business.

      So who is it exactly that is forcing you to use GPLed code in your proprietary software? Nobody? Thought so. Poor you, having to write the code yourself because you don't want to play fair with the author(s) of the code (um, it did occur to you to contact them and arrange a separate license, didn't it?) and the community at large. My heart bleeds for you.

      There are some people who are figuring out (or have done so already) how to make money with the GPL. Looks like you're not one of them. Pity.

      Well, good luck with your business. It must be at the brink of total annihilation with all that nasty, horrible, evil GPLed code running around out there.


      --
      --
      Use 'slashdot stuff' in the subject line in any email you send me if you want to get past the spam filter.
  193. Re:Lawsuits are inevitable unless we change course by sgml4kids · · Score: 1
    A movement whose focus is the destruction of people's businesses and livelihoods can only lead to a battle -- no, rather, to a war consisting of many battles and many casualties.

    It is a misrepresentation of the goals of the FSF
    to state that it's "focus is the destruction of [yadda, yadda]". The goal of the FSF and the GPL is to promote innovation in the software industry by removing proprietary obstacles. The only people who are threatened by the GPL are companies who make significant revenue from these proprietary obstacles.

    Don't forget that most corporations in the world use software, but very few make it. The GPL ensures that software is widely available. I work as a software engineer for an embedded systems company: My desktop is RedHat 5.2 with egcs; I port to VxWorks using the gcc cross-compiler that WindRiver sold us (all GPL'd) and I install my code on a Motorola chassis using their embedded version of (the GPL'd) RedHat Linux. Motorola, WindRiver and my company have all benefited handsomely by the GPL. There is not a significant BSD-licensed tool in our shop.

    The argument that the GPL removes the incentive to innovate might have some merit in an academic conversation, but the real world tells us that this is a false proposition.

    For every 1 company you can name that is threatened by the GPL, I can name 25 that benefit from it. The fact is, the GPL
    is a very good thing for capitalism and industry. Despite your protestations, the BSD-style licenses are not going to overtake the GPL in popularity and consumers, developers and software users all over the world are reaping the benefits.


  194. Eliminating obstacles by Brett+Glass · · Score: 1
    The goal of the FSF and the GPL is to promote innovation in the software industry by removing proprietary obstacles.

    Unfortunately, as stated in the GNU Manifesto, Richard Stallman and the FSF consider such things as good salaries for programmers to be "obstacles" that must be removed. Stallman advocates "banning" them.

    --Brett

  195. Why contribute to something destructive? by Brett+Glass · · Score: 1
    What have you contributed to GNU/Linux lately?

    Nothing -- and I will not do so. To contribute to Linux (I find it hard to believe that Stallman has managed to convince people to put the name of the organization he controls in front of it) would be to contribute to the base of GPLed software. This, in turn, would reinforce Stallman's intentionally spiteful and destructive agenda.

    The GPL is Richard Stallman's attempt to transform open source software into software which is not open to people he does not like -- and to use it as a weapon against them.

    I believe in making positive contributions. When I do publish open source, it is under the BSD license, not under the GPL's "poison pill" license.

    --Brett GLass

    1. Re:Why contribute to something destructive? by (void*) · · Score: 1
      To regard the GPL as existing in a logical vacuum is what is wrong with your argument.

      You should look at the _history_ behind the license. The the history says what was exactly wrong with BSD style licenses. Unix vendors took free code, improved it, slapped on a license and prevented other programmers to likewise as they have done. (Note: they making money out of it has nothing to do with it.)

      The GPL was designed to address this. And you have to understand history to see its logic.

      This is not to say GPL is the best free license there is. I look forward to the day (no, I'll probably not live to see it) when all sources are open by default. And that is when the GPL becomes irrelevant.

  196. Wrong, Wrong, Wrong, Wrong, Wrong!!!! by dcallred · · Score: 1

    This is not Slashdot's fault. Did they make up the statement? Did they post something that wasn't said? Did they double check their source and find that it had been said? Mr. Perens posted the comment to an Online mailing list and to his web site. Is it news that the driving force behind one of the major Linux Distributions wants to sue Corel? If I was to make these comments no one would care and I probably would only get one or two "go away" type flames. If Mr. Torvalds was to post these comments all hell would break loose. If you don't want to live with your comments then don't make them. I think even Mr. Gates has started to discover the consequences of making comments even in what he thought would be private emails.

  197. Re:Lawsuits are inevitable unless we change course by dmaxwell · · Score: 2

    "not antagonistic to business"


    Why is there this insistance that Open Source has to be particularly sensitive to business? Most academic institutions can play by GPL rules; most nonprofits have no problem with it and most individual users have no problems with it. It seems that the only people who think the GPL is a "restrictive" license are pro business zealots. I have no problems with business using this stuff and even pitching in a hand. Even RMS doesn't have a problem with business using the software.


    A business has no special right to Embrace and Extend community code. If a sufficiently large and powerful business were to Embrace and Extend free code then that version would become "canonical". This would impose restrictions...that word again..that the community users and developers would find intolerable. Why must we sanction attempts by large and powerful organizations to usurp this code? That is the freedom you are so ardently defending.


    You are defending a paradox. Does your concept of freedom include the freedom to sell yourself into slavery? If so, then there is a problem. No reasonable concept of freedom will countanance slavery. You argue a related case. That developers should be free to let bigger fish steal their code. This is not freedom. You mention "major creative works" for which business has the right to demand compensation. This may be so but what if this "major creative work" is based on code that is the product of the sweat of others? They have no pride of place in this context. That is what the GPL prevents. The GPL insures that in the very worst case...say Microsoft having untrammeled power to borg the entire industry..that there is a base of software immune to the tactics necessary for this to take place.

  198. Ah ha! by dmaxwell · · Score: 1

    Unfortunately, as stated in the GNU Manifesto, Richard Stallman and the FSF consider such things as good salaries for programmers to be "obstacles" that must be removed. Stallman advocates "banning" them.


    Is this what make you so sore on this subject? You seem to be worried that those evil GPL fanatics are going to come and take your job or at least reduce you to Burger King wages? Get real! A very few developers like Carmack get to drive Ferraris. Most of the rest have to subsist on upper middle class wages. How terrible for them! Even if ALL the software in the world were GPLed (never happen cool down Brett.....) quite a few people will be able to make a reasonable living making needed enhancements or spot bug fixing for.....hmmmm...Business users. Yes, you would still be able to make a good living. No, you are not "Going to get handjobs from women you hardly even know." on account of the Jaguar that proprietary software was going to buy you.

  199. Re:Lawsuits are inevitable unless we change course by fwr · · Score: 1

    No, but I think it would be completely accurate to say that people who urge others to release using a BSD license instead of a GPL license are more likely to expect other people to share without sharing themselves, as the major difference between the licenses is that BSD code can be taken proprietary while GPL code can not. Assuming that is the only major difference, what other reason would someone using the code prefer a BSD license over the GPL? I can see reasons for developers to possibly prefer to release code under the BSD license as it allows their code to be used in proprietary systems and therefore has a larger possible base of users. But, if you take a look at it from the point of the user of code, it's clear that those who want to take code proprietary would prefer the BSD license. So, if your a programmer and want to release your code to the "community" where "community" is defined as those who either author original works and give them to the "community" or extend/enhance existing "community" code and give it back the GPL is the only choice. If you don't mind someone taking your ideas and work and making any extensions or enhancements to them proprietary then you can't use the GPL and have to use the BSD license. The difference is that the GPL obliges those who use the "community" code, or in other words "takes from the community" to "give back to the community" while the BSD license does not. It definately allows for a "community" but does not oblige those who use community code to give back, ever.

    Why would you not want to oblige others to give back to the community and instead allow them to make proprietary extensions? Anyone remember the fragmentation of Unix? Would this have been possible if the original code was released under the GPL instead of the BSD license? Do you want to see this again? I'd rather not.

  200. Speaking web browsers by GregWebb · · Score: 1
    B*******. I've actually had first-hand experience with these kinds of browsers. For instance, I remember one that came out a few years ago, it was a Windows only program that interfaced to a speech synthesizer. It was 'designed for the visual impaired'. It was proprietary and cost $150. It was also a piece of ****.

    It took a few months for the thing to actually work properly (despite the fact we paid for it long ago). In the end, it was hopeless to use, and we ended up trying Lynx on DOS instead-- which was much better, not to mention $150 cheaper.
    So you had one bad experience with this sort of software and automatically assume that this is the case for all commercial development in this field? That's crazy.

    Oh, and sorry to have edited your post but I'm not having language like that in my name.

    There is a need for a decent speech interface browser, but I think an open development is the only way to go. You have to accept the fact that you're not going to get rich selling web browsers to the blind, and it would be better to have the greatest number of contributors (i.e. open source) than try to get a few people to work on it in secret and not make any money anyway.
    You miss the point of what I was saying.

    I agree that he probably won't get rich in this market. I agree there's every chance they'll fail. But they're trying. And is there a GPL-based project out there to develop such a product? If there is, it's awfully quiet.

    Y'see, the problem here is that programmers tend to want to work on fun or visible projects if they're going to work for free. I don't blame them, I would. But Mozilla hit this problem and so would a speaking web browser, as is rather suggested by the (apparent) absence of such a project.

    If someone wants to make a non-proprietary browser for the blind, all power to them. Until some kind souls decide to do such work, however, the GPL is harming the market as there is a developer who is willing to do this work but unwilling to do it without pay, which means they believes the GPL cannot be used. They may well be wrong, but that's their belief. It may well prove to be bad, it may well sell in low numbers and be dropped by its author. But they're trying and they cannot harm the market by trying.

    I repeat, having seen no sensible arguments to the contrary, my assertion that, in this case, the GPL is harming blind users. Think about this sort of scenario next time you release a new program, please. And think whether this was really what you wanted when you chose the GPL on any previous releases.

    Greg
    --

    Greg

    (Inside a nuclear plant)
    Aaaarrrggh! Run! The canary has mutated!

    1. Re:Speaking web browsers by rking · · Score: 1

      "I repeat, having seen no sensible arguments to the contrary, my assertion that, in this case, the GPL is harming blind users. Think about this sort of scenario next time you release a new program, please. And think whether this was really what you wanted when you chose the GPL on any previous releases."

      You're being silly and I'm begining to think that you're doing so deliberately. The only sense in which the GPL is "hurting the blind" is in that the code cannot be used in a proprietary project, correct? But exactly the same would be true for code released under a proprietary licence. But you don't seem to be screaming at Brett that his proprietary browser-for-the-blind project is hurting the blind, deaf, claustrophobics, or anyone else who might benefit from a project that his proprietary code can't be used in.

      You seem to approve of his actions, you say "They may well be wrong, but that's their belief. It may well prove to be bad, it may well sell in low numbers and be dropped by its author. But they're trying and they cannot harm the market by trying." But the authors of GPL code are trying to do something too, and somehow you feel that they are doing harm where the proprietary authors aren't, why is that?

      Of course, he might voluntarily consent to his code being used in those projects and not be subject to the normal restrcitions, but the authors of GPL'd code can do that too if they wish to. In what sense is the GPL "hurting the blind"?

      You might as well turn your comments around and say that next time people publish code under a BSD licence they should consider that they might be fostering proprietary projects that impose much greater restrictions on their code and thereby "hurt the blind" and wonder whether this is what they want.

    2. Re:Speaking web browsers by GregWebb · · Score: 1
      You're being silly and I'm begining to think that you're doing so deliberately. The only sense in which the GPL is "hurting the blind" is in that the code cannot be used in a proprietary project, correct? But exactly the same would be true for code released under a proprietary licence. But you don't seem to be screaming at Brett that his proprietary browser-for-the-blind project is hurting the blind, deaf, claustrophobics, or anyone else who might benefit from a project that his proprietary code can't be used in.
      No, I assure you I'm not playing Devil's Advicate here.

      I accept absolutely that Brett's (likely) refusal to release his code is harming other communities, but there didn't seem much point in screaming at the guy any more than he's been already. There comes a point where one extra abusive voice simply won't make a difference.

      The point, though, is that for many developers, GPL source is entirely irrelevant. If you make a business decision that you cannot GPL your work - which, right or not, is a separate debate - then the GPL source having been published is useless. It's off-limits. Now, I fully understand why it's off-limits and why people want it to be so, but it seems that many people don't truly understand that this is the consequence.

      You seem to approve of his actions, you say "They may well be wrong, but that's their belief. It may well prove to be bad, it may well sell in low numbers and be dropped by its author. But they're trying and they cannot harm the market by trying." But the authors of GPL code are trying to do something too, and somehow you feel that they are doing harm where the proprietary authors aren't, why is that?
      I assure you I do not think the proprietary code developers are doing any less harm than the GPL developers. But they're not claiming any great altruism, whereas GPL coders are. That's the issue here.

      While we're here, you refer to "GPL coders". Does anyone know of a GPL project to produce such a program? I have no use for one myself, but its existence (or not) is certainly relevant to this discussion, as we have a commercial developer who is trying but no current evidence of such effort from the GNU community.

      Of course, he might voluntarily consent to his code being used in those projects and not be subject to the normal restrcitions, but the authors of GPL'd code can do that too if they wish to. In what sense is the GPL "hurting the blind"?
      By both holding back a project that would be useful to them and failing to provide an alternative.

      This isn't really about the merits of the GPL versus closed commercial development, though - it's about the merits of the GPL versus other open licenses. If Lynx had been placed under a BSD-style license, it wouldn't be an issue.

      You might as well turn your comments around and say that next time people publish code under a BSD licence they should consider that they might be fostering proprietary projects that impose much greater restrictions on their code and thereby "hurt the blind" and wonder whether this is what they want.
      No, that's just being silly.

      The crucial difference here is that BSD-licensed development is promoting a generic codepool for all programmers to use in all projects, whereas GPL development is promoting a generic codepool for other GPL developers. In this respect, GPL development is essentially no different from corporate, closed development with the exception that the corporation concerned is the FSF and that anyone can choose to work for them if they're prepared to support their ideals. So which is truly freer?


      Make no mistake, this post (and my other posts to this thread) is not an attack on the GPL. As I said elsewhere, all are welcome to release their code under any conditions they wish until their control of the code represents an unjust control over a particular area computer use. But many fail to understand that the GPL's idealism can have consequences which they may not actually want. This is one such example.

      Greg
      --

      Greg

      (Inside a nuclear plant)
      Aaaarrrggh! Run! The canary has mutated!

    3. Re:Speaking web browsers by rking · · Score: 1

      "The point, though, is that for many developers, GPL source is entirely irrelevant. If you make a business decision that you cannot GPL your work - which, right or not, is a separate debate - then the GPL source having been published is useless. It's off-limits. Now, I fully understand why it's off-limits and why people want it to be so, but it seems that many people don't truly understand that this is the consequence."

      But which people? This just doesn't seem to arise from the posts that you reply to, in any way that I can see. Do you mean that the other posters you reply to don't understand that people who choose not to use GPL'd code won't be able to, or do you mean that Lynx developers don't, or that I don't, or who?

      For the sake of clarity, I assume you do realise that the the authors of code can also give permission to any group to use it on other terms if they so choose?

      "I assure you I do not think the proprietary code developers are doing any less harm than the GPL developers. But they're not claiming any great altruism, whereas GPL coders are. That's the issue here."

      All GPL coders are? The ones on the Lynx project in particular? All the ones you know personally? As a rule of thumb I suspect anyone claiming "great altruism" of themselves is an unlikely candidate to be acting out of altruistic motives, but I expect there are exceptions.

      Anyway, I'll let you into a secret, it's terribly embarrassing but I'm not a True Altruist. Sometimes I help people in all sorts of ways, but I help people I like more than people I don't like, and sometimes I even watch out for myself. I know, terrible isn't it? And sometimes, when someone wants my help I consider whether what they're trying to achieve is actually something that I want to see happen, or I consider whether they're actually making things worse, or even (awful this) I consider whether they're ever willing to help me when I need it. So not being a True Altruist anyway, I'm not worried that GPL isn't the One True Licence for True Altruists. As a matter of interest, are you a True Altruist?

      On the other hand, some people who want to enhance the base of code that's out there for them to play with think that the GPL is a good way of achieving this and think that that's a good thing. They might be wrong that the GPL achieves this but I doubt they care that you don't count them amongst the True Altruists of this world.

      "This isn't really about the merits of the GPL versus closed commercial development, though - it's about the merits of the GPL versus other open licenses. If Lynx had been placed under a BSD-style license, it wouldn't be an issue."

      Ah, but it would be an issue as I suspect you know. Because the code would now have been used as a building block for a proprietarily licensed project. As you've already said that you dislike proprietary licenses (for the same reason that you dislike the GPL) this would surely be an issue for you? Oh, or it would only be an issue if you decided that Brett thought he was being a True Altruist when he wasn't? I'm afraid I'm still a little unclear on your approach to that.

      "The crucial difference here is that BSD-licensed development is promoting a generic codepool for all programmers to use in all projects, whereas GPL development is promoting a generic codepool for other GPL developers. In this respect, GPL development is essentially no different from corporate, closed development with the exception that the corporation concerned is the FSF and that anyone can choose to work for them if they're prepared to support their ideals."

      Nonsense, if nothing else the individual users all have access to source code which they can modify for their own use (and never distribute under any licence if they so please, including never giving access to the FSF). In addition the average coder does not in any way answer to the FSF, if you have an employer then you have a very strange relatinship with them if you think that people working on GPL projects are effectively working for the FSF. As coders have free reign as to what they do with the code, suggesting that they're in the same position as if they were working for a corporation controlling the code is silly.

      There is no requirement at all that you support FSF ideals to make use of the GPL, and I've no idea where you got this notion. Try reading writings by Linus Torvalds, by Richard Stallman, and by Eric Raymonds, they clearly have different ideals to one another. More than that, suppose you run a company providing PCs with Linux preinstalled, and you think that a great idea would be to tweak a couple of GPL programs to flash your logo on the screen. You make the changes and, as required, GPL the result; did this mean signing up to the FSFs ideals? Doesn't seem to be anything idelaistic about that to me.

      "So which is truly freer?"

      But that's trivially easy, the BSD licence is freer of course. And equally obviously, proprietary code that builds upon it is less free. The question is, which people is it that you think don't appreciate this?

  201. Huh? by Luis+Casillas · · Score: 1
    Unfortunately, as stated in the GNU Manifesto, Richard Stallman and the FSF consider such things as good salaries for programmers to be "obstacles" that must be removed. Stallman advocates "banning" them.

    Huh? Would you care to quote where RMS says precisely that?

    BTW I just reviewed the GNU Manifesto, and that's not what it says. So either you give a TEXTUAL QUOTE where the FSF LITERALLY says that "good salaries" for programmers are "obstacles" that must be "banned", or you lose.

    Deliberate misquotation and misrepresentation are very vile practices, Mr. Glass.

    ---

  202. Re:Lawsuits are inevitable unless we change course by billybob+jr · · Score: 1

    It's always nice to hear personal and "real world" experience.

    Thanks sgml4kids

  203. Direct quote by Brett+Glass · · Score: 1
    I've already quoted Richard once on this topic, but since it appears that you haven't followed the thread, and/or insist on being spoon-fed the information, I will do so again.

    From Stallman's "GNU Manifesto," at http://www.gnu.org/gnu/manifesto.html:

    For more than ten years, many of the world's best programmers worked at the Artificial Intelligence Lab for far less money than they could have had anywhere else. They got many kinds of non-monetary rewards: fame and appreciation, for example. And creativity is also fun, a reward in itself.

    Then most of them left when offered a chance to do the same interesting work for a lot of money.

    What the facts show is that people will program for reasons other than riches; but if given a chance to make a lot of money as well, they will come to expect and demand it. Low-paying organizations do poorly in competition with high-paying ones, but they do not have to do badly if the high-paying ones are banned.

    --Brett Glass

    1. Re:Direct quote by Luis+Casillas · · Score: 1
      Ok. You were right. My apologies

      ---

  204. What should Corel do now? A proposal by Brett+Glass · · Score: 1
    Let's get back to the main topic a bit here. What should Corel do about all of this?

    Personally, if I were Corel, I would quickly move Corel Office, CorelDraw, and future open source development efforts to OpenBSD.

    This would have the following advantages over the current situation:

    1. Questions regarding the GPL would be moot, as OpenBSD -- of all of the open source UNIX-like operating systems -- uses the least GPLed code (and this only for the toolchain).

    2. Corel would no longer be subject to attack by GPL "zealots."

    3. Corel still be able to support versions of its applications for Linux, because the APIs of OpenBSD and Linux are very similar. Porting would amount to little more than a recompilation -- and possibly minor changes in the locations of a few files. (These could be handled by very simple logic in the installation programs for the applications.)

    4. Because OpenBSD is a Canadian product, Corel need not worry about the possibility that US export restrictions would prevent it from obtaining and/or redistributing parts of the OS that used encryption.

    5. Corel is often accused of shipping software which is not fully debugged and/or which crashes frequently. However, OpenBSD's code has been -- and continues to be -- fastidiously audited and maintained, and will raise the perception of Corel's code quality as a whole. The OpenBSD developers are fanatical about code correctness and will fix bugs that are pointed out to them promptly. They will also welcome the bug reports.

    6. There are no commercial distributions of OpenBSD, whereas there are dozens of Linux distributions. Corel, as a distributor of OpenBSD, would be alone in its niche with a unique and well-differentiated product. What's more, it could add unique enhancements -- e.g. binary hardware drivers -- without being forced to give them away.

    7. OpenBSD is reknowned for its security, but is a bit less user-friendly than the other BSDs. Corel, by bringing an office suite and other applications to the table, could turn this around, creating a symbiotic relationship between itself and the OS project.

    8. While Theo DeRaadt, the leader of the OpenBSD project, is noted for his cantankerousness, Corel always has the option of creating its own distinct fork of the OS. However, the ability to fork is actually a deterrent to forking, since both sides would realize that it would be a duplication of effort. So, the BSD license would encourage Corel and the OpenBSD team to cooperate for their mutual benefit.

    9. The transition could be done quickly and painlessly due to the similarities between the OSes and their APIs. Corel would not see an interruption in its revenue stream as a result.

    For all of these reasons, the best course of action for Corel is to recognize that it almost got it right, but needs to tweak its strategy a bit to maximize its effectiveness. OpenBSD is the way to go for Corel, and I believe that it should move that way before the next release.

    --Brett Glass

  205. Sarcasm is a last resort by divec · · Score: 1

    This post doesn't seem to refute any of the arguments of the previous post. Rather it seems to use sarcasm as a tool to avoid needing a rational argument.

    --

    perl -e 'fork||print for split//,"hahahaha"'

  206. Club Med is a fun resort by Brett+Glass · · Score: 1
    The posting to which I responded did not make a rational argument; it made unsupported, pontifical statements and judgments. There is no point in arguing with such pronouncements. However, there is some value in throwing them into sharp relief via satire.

    --Brett Glass

  207. Other advantages of OpenBSD for Corel by Brett+Glass · · Score: 1
    Another advantage of OpenBSD for Corel would be portability. Corel has expressed interest in entering the "thin client" market. OpenBSD, like NetBSD, is extremely portable. Its roots lie in OpenBSD, the world's most portable OS, and it already runs on a wide range of CPUs, including big-endian, little-endian, RISC and CISC processors. But unlike Linux, it can be customized without requiring Corel to reveal exactly how it builds its hardware. This allows Corel to preserve the unique value of its hardware designs.

    Yet another plus of OpenBSD for Corel would be the value inherent in the OS's emphasis on security. Corel, because it's in Canada, can export a secure OS to the world -- giving it an advantage over any American company (including Microsoft). And being able to demonstrate that one's OS is far more secure than Windows NT would likewise be a tremendous marketing point.

    Finally, because OpenBSD has Linux emulation, Corel can cross-develop for Linux directly on the OpenBSD platform. If the code runs on the emulation, it will run well under Linux. Cross-development for FreeBSD would likewise be a snap.

    It's ironic that Corel has, up to this point, overlooked a fantastic opportunity right in its own backyard! But fortunately, the animus of the GPL and its supporters toward private business has given Corel a "wake-up call." Now's the time for Corel to act.

    --Brett Glass

  208. Correction by Brett+Glass · · Score: 1

    Oops. I should have said, above, that OpenBSD's roots lie in NetBSD -- the world's most portable OS.

  209. Depends on what your motives are... by sheldon · · Score: 1

    If your motive is simply to create a experimental OS for use in University teaching environments, then embracing the GPL makes sense.

    If your motive is to create an alternative OS to take on Microsoft, you can forget about it.


    As Mr. Perens has so expertly shown, any company seriously trying to make money using Linux is likely to find themselves tasting something sour.

    1. Re:Depends on what your motives are... by Le+douanier · · Score: 2


      If your motive is to create an alternative OS to take on Microsoft, you can forget about it.

      Isn't that what Linux is doing? (you didn't mention making money while taking on MS in this phrase, so it is valid ;))

      --
      "The obvious mathematical breakthrough would be development of an easy way to factor large prime numbers." Bill Gates,
    2. Re:Depends on what your motives are... by sheldon · · Score: 1

      I don't think .25% of the market is all that signifigant.

      And there is very little money currently being made. Few of the Linux related companies are profitable, if any.

    3. Re:Depends on what your motives are... by Le+douanier · · Score: 2


      "I don't think .25% of the market is all that signifigant."

      It is not significant on the desktop yet but it is eating NT's lunch, that is Unix companies that would have switched to NT of there wasn't Linux, so it must be very frustrating for MS.

      The desktop will follow soon. Last year (Xmas 98) I was explaining to some friends what Linux was and I was telling them that it wasn't ready for the desktop yet but in two years time it very probably would be. This year I think that we are very close to the desktop level, we just need some more polishing, an easier config, USB supported more broadly and a few more killer applications (like Gnucash, KOffice,...).


      --
      "The obvious mathematical breakthrough would be development of an easy way to factor large prime numbers." Bill Gates,
  210. Uhhh.... by sheldon · · Score: 1

    All you need to accomplish that is put a provision in your license that says "For non-commercial use only. If you want to include this in a commercial product contact me."

    Us programers have been doing this for 20+ years. It's nothing new.


    Brett is absolutely correct in his analysis of the GPL. I don't understand why some people continue to grasp for straws in support of Stallman.

  211. Oooooh, its all a commie conspiracy!!!! by Rogain · · Score: 1

    Bhwhahahahahahahahahah!!!!!!!!!!!

    --
    The current Slashdot moderation system is made by gay communists!
  212. Re:TRUTH HURTS I GUESS for the moderators huh ? by I+R+A+Aggie · · Score: 1
    Prediction time - BSD will "win" this war.

    Counter-prediction: it will not. There are more people with SystemV experience than with BSD experience. Most of the proprietary unices are SystemV. I'm adequately old enough to have used both -- on a variety of systems. I've even gone thru one BSD->SysV transition. That was painful enough that I have no desire to transition back.

    James - tho BSD does have its advantages

  213. screw the kids by arielb · · Score: 1

    This is ridiculous. Corel has done alot for linux-a heck alot more than alot of other people. they are porting their whole line to linux, improved Wine and of course came out with their new distro. I don't know of any major company that ported its whole entire line of products except for maybe Netscape (but some people still think they are evil for not using GPL). I was pondering whether to try corel linux but this made me finalize my decision. I'm going to download it and try it for myself to show my support for Corel.

    --
    ---
  214. Re:BSD "forking" a myth. But Linux forks abound... by DragonHawk · · Score: 2

    Actually, contrary to Raymond's "Halloween document," there hasn't been a new fork of the BSDs in several years.

    I wasn't quoting Eric Raymond, and I was not referring only to the past few years. Don't reply to ESR or RMS; reply to me, if you please.

    BSD forked into many, mutually incompatible systems. There are the three major "free" forks: FreeBSD, NetBSD, and OpenBSD. IIRC, they all derive from a 386BSD project which is now defunct. Furthermore, many (most?) commercial Unixes trace their roots to those original, source available without restrictions, Unixes from AT&T and UCB.

    That is what I am refering to when I say BSD forked. Unix could have been the universal future of interoperability between all computers; instead, it turned into a bunch of petty turf wars between Unix vendors. As others have put it, snatching defeat from the jaws of victory.

    However, there are now a couple of dozen forks of Linux, and more are appearing all the time.

    There are? I was not aware of any. Perhaps you refer to the various projects like RT-Linux, HA-Linux, ucLinux, and so on? There is a difference here between those and your typical BSD fork.

    What we have here are a number of side projects. A bunch of people have a particular need or see a particular problem. To maximize development efficency, they start hacking in a high-density, limited system. Their work remains freely available -- because of the GPL -- and in every case I know of, they are ideally aiming to remerge with the Linux kernel proper. If not, the mainstream kernel people can take ideas they like and incorporate them back into the main kernell. The GPL ensures that nobody can make a propriatary, closed Linux variant. That is the major selling point of the GPL. Yes, it causes problems with some people, but many others feel it is worth it.

    Hence, the fragmentation of Linux into many incompatible distributions.

    I would like to call that FUD, but I was called out for over using that term, so I will instead call it an outright lie.

    As far as I know, there is not one single Linux distribution which is not compatible with every other Linux distribution out there (platform specific dependcies aside -- don't complain that LinuxPPC doesn't run on your Alpha).

    Do problems occur because someone's pre-compiled, third-party binary was dynamically linked against a different C library then which it was compiled for? Yes, that is not unheard of. But the problem comes from user X's system being out of date. Try to run a modern FreeBSD binary on a first-release 386BSD system, and I suspect you will have similar problems. You can hardly expect libraries to magically distribute themselves.

    I am not saying the GPL is the end-all and be-all of all existance, like certain people (*cough* Stallman *cough*) do. I am simply asserting that, like any license, it has its strengths and weaknesses, and that many people believe the strengths are worth the weaknesses.

    --

    dragonhawk@iname.microsoft.com
    I do not like Microsoft. Remove them from my email address.
  215. Re:Debian is not a first order distributor by Rares+Marian · · Score: 1

    Okay my bad. But the point is still the same. They have no business fucking with the license

    "Computers should be ... tools... (siglim 120 chars)" Like cars... to the office no more no less.

    --
    The message on the other side of this sig is false.
  216. Why your post is totally stupid by Le+douanier · · Score: 1


    I can't believe people can moderate this bullshit to 5 with *interesting*. Ok, we are not supposed to moderate because we agree or disagree but because it is interesting or stupid, so let me show you why this is stupid with a parody of his post:

    The EULA, by its very nature, creates conflicts between closed source developers and honest businesses -- large and small -- by putting them at odds with one another. It doesn't take more than a few minutes' reading at MS's Web site -- in which Bill Gates repeatedly issues a call to arms against "free" software (i.e. software which one can make money by selling a service) to see the antagonism. (His essay in which he asks hobbyists not tocopy his software is an especially good example of this attitude.) A movement whose focus is the destruction of people's businesses and livelihoods can only lead to a battle -- no, rather, to a war consisting of many battles and many casualties.

    Everyone -- businesses and the open source community -- would be better off if we adopted the win/win, "live and let livee" approach of other software licenses, such as the BSD license, the MIT X license, and the Artistic License.

    Open source that's reusable by all -- such as the BSD TCP/IP stack -- is responsible for the growth of the Internet and the success of the World Wide Web. Instead of threatening lawsuits based on overly restrictive licenses such as the EULA, we should say, "Use this code as you will. You can't un-publish what's already been published for the world to see, so you can't 'take' it; you can only use it to avoid tediously reinventing the wheel. Now, let's see what you can do wih it! If you do not choose to publish the source to what you build with it, good luck to you -- it's not easy to make a living that way. If you are good enough to do it you deserve success."

    Do you think Billy boy will throw is EULA and adopt the BSD license because of your rethoric?

    No, WHY?

    Because different licenses have got different aims. The EULA's aim is to forbid you to copy the software or to use the code, the BSD aim is to allow anybody to use the code, open source developers or close source developers and the aim of the GPL is to allow people that are willing to share code to the GPL'd base to do so, without helping closed source program (the poroblem is that it helps less the non-GPL programs that are Free Software too).

    Of course the GPL is more restrictive than the BSD,but it is his aim, and of course the GPL can lead to potentially more lawsuit, but only if people STEAL GPL'd code. You can't steal BSD code because he is given with quite no restrictions but if you use GPL'd code in proprietary product then you STEAL GPL'd code.

    You would want us to throw away all our rights to the code, including the right for it to remain open, i won't do it until big corporations (MS in particular, or their heir (in the sense that MS is IBM heir for monopoly things and unethical practices)) do the same thing.

    I may do it once in a while but this certainly is not my intent to give them all my code if they don't give me code or money back.

    You can keep your bullshit for yourself.

    --
    "The obvious mathematical breakthrough would be development of an easy way to factor large prime numbers." Bill Gates,
  217. Grasping at straws again... by sheldon · · Score: 1

    #1. No, someone cannot relicense your code without your permission since you hold the copyright. If your claim were true I could release GPL'ed code under a BSD license.

    #2. No, my example allows for commercial use, but requires the commercial entity to ask for permission. And possibly give a financial reward in exchange for allowing it to use your code.

    I see no reason for the GPL's existence other than Stallman's crazy idea that programmers should all work for the government(like he does).

  218. Slashdot NNTP backend needed by mihalis · · Score: 1

    I can't get into this thread that has some posts I really feel like responding to, because at the level of nesting and citation it's already at, I really want to be using Gnus in Emacs, not a web browser.

    I hate to be negative, but I can't help the feeling that a news interface to topic threads wont happen because there are no banner ads in an NNTP newsgroup. I keep writing long replies and then at some point hitting Meta-Q (format paragraph in Emacs, quit in Netscape) and losing my work. If you override this using a resource file, netscape seems to crash more often. Yes I did submit that as a bug to Netscape. Yes I have read the Slashdot FAQ regarding NNTP, yes this is a little offtopic, sorry!

    Chris Morgan

  219. Corporate Troll? by winterstorm · · Score: 1
    I can't help but wonder if the posting of this article is a troll by those who view Linux as a commercial competitor.

    Mr. Peren's mailing-list posting doesn't sound to me like the threat of a lawsuit. If fact it doesn't sound like "News for Nerds: Stuff that Matters" either. He posted a few sentences to a mailing list and some Anonymous Coward decided the whole world should read about it.

    Even if the coward was genuine it makes me wonder how many people are employed to read Linux mailing lists and misinterpret them publicly. Anyone care to admit to being a muckraker and identify themself and their employer?

    I'm especially suspicous because one of the more popular anti-Linux memes is "the Linux community is weak because it is fragmented" which is just a purposeful misinterpretation of "The Linux community is strong because it is diverse."

    I really think the editorial staff of Slashdot were way to quick to post this story especially when the "supporting evidence" links were didn't exist. Perhaps they should have emailed Bruce Perens and actually asked him if the Anonymous Coward's report were true.

  220. You have it the wrong way around. by Brett+Glass · · Score: 1
    Labor is not a capital asset, because once it is expended, it is gone.

    Information, on the other hand, is capital, because it can be reused again and again.

    Stallman's goal is to force people to give up their intellectual capital.

    --Brett Glass

    1. Re:You have it the wrong way around. by Brett+Glass · · Score: 1
      Yes, money itself is capital. And it is not consumed when it is spent; it is passed from hand to hand.

      Intellectual property is, most certainly, capital -- and, in fact, is the coin of the realm in the Internet Age. Lobbying to abolish it, as Stallman does, is akin to lobbying for the abolishment of money. Which Stallman, who does not like to so much as touch money, may find desirable. However, most of the rest of us need it to eat.

      --Brett

      P.S. -- I'd be interested in hearing the expansion of the acronym "LART."

    2. Re:You have it the wrong way around. by fwr · · Score: 1

      Yes, money itself is capital. And it is not consumed when it is spent; it is passed from hand to hand.

      The money is capitol thing may not be the best for you to support, as there are definately laws that forbid the "copying" of money by everyone except the government. This is, in effect, what people who believe in intellectual property are doing. Since they are able to make copies of capital with no measurable cost it argues against viewing "intellectual property" as property at all. Nothing else that is considered capital can be duplicated without cost.

      That's why I think it would be better, and financially rewarding, to view programmers as "professionals" in the realm of doctors (but not necessarily lawyers). Doctors are paid for what they can do in each individual visit, not for something they did 30 years ago without "producing" anything for the last 25 years. (Note that this is without considering doctors who try to make a profit off of "intellectual property" such as surgical devices, etc. IMO, they are doing more to retard the progress of medicine than anyone by restricting the use of their "property" to those who cough up the dough). Instead, they could be viewed as service "contractors" who are paid very highly if they are "good" and demonstrate the ability to produce consistantly "good" code. This would reduce the number of "professional" programmers as it would get rid of those who do not produce consistantly "good" code. But, they could still contribute or have a lower paying "side-job" if they could program but be unable to support themselves only by programming if they were not "good." Why would this be so terrible? Doctors can't simply take a few courses in a 4 year college and get their degree. It takes a couple extra years of extra study concentrating in a particular field of medicine in order to get a doctors degree. Plus, even after they are done with that they have to do internship where they don't make a whole lot and have to work excruciatingly long hours before they are actually financially independant. What makes you or anyone else believe that programmers should get paid comparable salaries without going through similar training and weeding-out trials?

      There will come a time, relatively soon, where all the "standard" applications are written and rewritten and rewritten the last time. Perhaps it will be when open source (preferably GPL) solutions are available for all the standard applications. Then, since there will be no financial incentive to make a new version of your word processor simply because you can, programming will concentrate on custom applications and those doctor-salaried programmers can go from business to business making buko bucks providing real solutions to people.

  221. Between two worlds by Brett+Glass · · Score: 1
    Those who see the entire world in terms of open source tend to forget: there is a necessary synergism between open source and commercial softare.

    The relationship -- at least up to the time when the GPL was created -- has always been similar to that between pure research and engineering. Researchers do their work in a rarefied, somewhat artificial environment where the sharing of information -- via publishing -- brings the maximum reward. The scientists in this environment know full well that they are foregoing some monetary rewards for their work, but are generally quite happy to do so -- since in return, they are allowed to live and work in an incredibly rich academic "playground."

    Once scientists publish their results, engineers who produce commercial (or, as Stallman calls them, "proprietary") products may use it to develop practical solutions for the real world. These engineers, being outside the research "bubble," world, do not reveal everything they build upon the scientists' work (though they may reveal some of it, in exchange for a temporary monopoly, via patents). Why? Because in their world, rewards arise from the unique value that they add to their products -- value that their competitors cannot duplicate.

    Richard Stallman worked in a research facility: the MIT AI Lab. However, like many hackers who have trouble dealing with the "real world," he failed to understand the symbiotic relationship between the artificial, rarified environment inside the research "bubble" and the world at large. What's more, he was jealous of his peers who left the research environment to join companies which made use of what had been done in the AI Lab. (In Stallman's "GNU Manifesto," he advocates that high programmer salaries be "banned" to prevent programmers from leaving academia.)

    Now, the truth is that not many of these people actually achieved great wealth. Symbolics -- the AI Lab spinoff whose creation enraged Stallman and led directly to the creation of the GPL -- failed miserably. But Stallman, in his rage, took it as a given that all of them were going to make tons of money. This is reflected in Stallman's writings, none of which recognize the fact that most commercial software companies fail.

    Feeling that he himself could never leave the research environment (he was so inured to it that he literally lived on a couch in the lab), Stallman sought -- out of spite -- to "queer the deal," as it were, between the two worlds. This was the purpose of the GPL: to prohibit reuse of work done in a research or research-like environment -- where knowledge is shared openly and the rewards are largely non-monetary -- to the commercial sector.

    What Stallman failed to recognize, however, is that the academic research environment is not self-sustaining. In fact, it is artificially created (and heavily funded) by government and by commercial interests in the hope that all of society can share and use the results. And, yes, some of us will use those results for profit. But that's a good thing -- it creates money which industry willingly feeds back into the research environment to generate more knowledge. And commercial spinoffs from publicly funded projects such as the Space Shuttle have improved all of our lives.

    The same is true of projects which make use of freely reusable (that is, non-GPLed) open source software. I and my team can spend less time re-inventing the wheel, and more time solving tough, new problems, if we can stand on other programmers' shoulders -- rather than, as Brian Reid once said, on their feet. But, like many companies that build on publicly available knowledge, we would not be able to consider doing a browser unless we can at least break even on our efforts. And this means making our product commercial. Given the limited market for our work, we do not expect to be able to use the "give away the source/profit from support" business model. The market simply isn't large enough. Without closed source, we couldn't contemplate the project at all.

    In short, the greatest benefit to everyone -- in this case -- will arise from a product which is, at least initially, closed source.

    Again, there is a symbiosis and a balance here. Giving some of one's work away is fine. But mandating that everyone give everything away destroys the relationship between the two worlds by attempting to impose the artificial rules of one upon the other. Instead, we must recognize, support, and sustain the very useful and positive relationship between the two worlds, and allow them to benefit from one another.

    --Brett Glass

    1. Re:Between two worlds by Brett+Glass · · Score: 1
      Stallman, in his rhetoric, attempts to redefine the words "commercial" and "proprietary" for his own purposes.

      GPLed software cannot be "commercial" because a license to use it cannot be sold. Copies of it are sold, but all that's being sold is the media -- not the software.

      --Brett Glass

  222. It's a good thing "copyleft" is unenforceable. by Brett+Glass · · Score: 1
    Fortunately, the GPL's "copyleft" provisions, which require derived works to be licensed to all comers under the GPL, are unenforceable because they embody a "meta-contract" -- a contract to make a contract. Thus, the GPL's efforts to "capture" BSD-licensed code and prevent its commercial reuse will fail. Thank Heaven.

    --Brett Glass

  223. Re:Slashdot's irresponsible "news" reporting by gehrehmee · · Score: 1

    So now we have to avoid spreading news that, when looked at through a squinted eye, from 5 kilometers away, under a questionable context, might possibly be used in a negative way against us? Hmm. Maybe we should just shut down. :)

    --
    "You know, Hobbes, some days even my lucky rocketship underpants don't help" -- Calvin
  224. Re:what about getting a life??????? by Rogain · · Score: 1

    Ok. I hereby now grant Bruce Perens, the status of SuperHuman!

    By my fiat*, he can no longer make mistakes, his position if far too important for that kind of thing. He is no longer allowed to discuss his ideas with friends/co-workers/etc. He must only speak The Utter Truth of the Matter. He must be better than you or me could ever hope to be.

    * not the car.

    --
    The current Slashdot moderation system is made by gay communists!
  225. Thinly veiled donations by Brett+Glass · · Score: 1
    Stallman, by his own account, only consults for "a few days a year." That's too little time to get much accomplished for a client. And FSF's high-priced "products" are either copies of what one can download elsewhere for free or "souvenir" items such as T-shirts.

    Hiring Stallman, or buying an FSF product, is a thinly veiled way of "donating" to his organization. While Stallman is very uncomfortable with money, he does want the FSF -- his "weapon" against commercial software -- to be well armed.

    --Brett Glass

  226. And a heavy club is a clumsy retort by CRConrad · · Score: 1

    Brett Glass writes:

    "There is no point in arguing with such pronouncements."

    That's why this will be my first and last reply to you in this thread.


    "However, there is some value in throwing them into sharp relief via satire."

    That only works if the "satire" -- in your case, snide sarcasm -- is *funny*. So scratch that, then...




    Christian R. Conrad
    MY opinions, not my employer's - Hedengren, Finland.

    --

    Christian R. Conrad
    mail me at iki.fi ; same user ID as here