Slashdot Mirror


Slides Of Microsoft Anti-GPL Advocacy

An anonymous reader links to these slides outlining Microsoft's position on Free software licenses, in particular the GPL, writing "Regarding the latest memo from MSFT, the current politics is to be against 'copyleft' type licensing... Protecting freedom is fundamental for Free Software and MSFT knows that. They don't want licenses that protect our freedom." Makes an interesting companion piece to the anti-OSS memo mentioned the other day.

423 comments

  1. they should have used OpenOffice by stonebeat.org · · Score: 0, Funny

    Impress!!! to create the presentation :)

  2. It's a bunch of freakin jpg's by t0qer · · Score: 5, Insightful

    What good is this to my lynx browser?

    Kidding aside..

    It's just a bunch of jpg's on a non MS site. Just pointing out the obvious, what verification do we have these came from M$?

    Please tell me and don't mod down, I think I have a very valid question here.

    1. Re:It's a bunch of freakin jpg's by loners · · Score: 3, Interesting

      Unfortunately, this crowd doesnt seem to care about truth at times. We all get pretty petty at times.

      Freedom without truth?

      Are you sure that you have freedom? or are they lying to you?

    2. Re:It's a bunch of freakin jpg's by Jose · · Score: 2, Funny

      It's just a bunch of jpg's on a non MS site. Just pointing out the obvious, what verification do we have these came from M$?

      did't you see the little "Microsoft" logo's on the pages?! It must be from Microsoft...

      --
      The basic sleazeware produced in a drunken fury by a bunch of UCBerkeley grad students was still the core of BIND. --PV
    3. Re:It's a bunch of freakin jpg's by zulux · · Score: 2


      It's just a bunch of jpg's on a non MS site.


      Just find your local script-kiddie and ask.

      I recommend http://www.microsoft.com/products/bob/sneaky-hidde n-directoy/

      --

      Moneyed corporations, non-working 'poor' and criminal prisoners are turning productive citizens into tax-slaves.

    4. Re:It's a bunch of freakin jpg's by thoth · · Score: 1

      Probably none, since if they are legit you can hardly expect the person who leaked them to announce that fact. They'd be terminated, as per Brian Valentine's policy on confidential material.

    5. Re:It's a bunch of freakin jpg's by Maxwell'sSilverLART · · Score: 5, Funny

      Verification? If you can't trust something you read on Slashdot, posted by an Anonymous Coward, then who can you trust?

      (</joke>, for the sake of the moderators)

      --
      Moderate drunk! It's more fun that way!
    6. Re:It's a bunch of freakin jpg's by Tony.Tang · · Score: 2
      It's just a bunch of jpg's on a non MS site. Just pointing out the obvious, what verification do we have these came from M$?

      Uh ... hello! It was posted on /.! It MUST be true. ;)

    7. Re:It's a bunch of freakin jpg's by Fishstick · · Score: 3, Informative


      well, it's an obvious hoax, isn't it? I mean, I would expect a presentation from MS to be with full-color, animated ppt slides and not something B&W that looks like it was made with wordpad!
      </t-i-c>

      No, I agree.. no real evidence it actually came from Microsoft, and if it did, so what? No real surprises here.

      --

      There is much cruelty in the universe, John.
      Yeah, we seem to have the tour map.

    8. Re:It's a bunch of freakin jpg's by njdj · · Score: 2

      These slides present Microsoft's position cleverly. They are well thought out, and the material is intelligently organized. It is clearly the work of an experienced presenter, not some nerd halfway through a CS program.

      Nobody from MS has disowned the slides.

      None of this is proof (what kind of proof do you want, anyway?), but in my opinion these slides are probably authentic.

    9. Re:It's a bunch of freakin jpg's by arkanes · · Score: 2

      Yeah, but the position, at least as shown in the slides, is pretty moderate and I wouldn't disagree more than trivially with anything there. Obviously can't be Microsoft, who is well known is these parts as claiming that Open Source will make your baby fat and kill your dog.

    10. Re:It's a bunch of freakin jpg's by dusanv · · Score: 1

      The guy that signed the presentation (Dirk Tombeur) is the BeLux MS .NET manager and judging from Google results gives presentations frequently.

    11. Re:It's a bunch of freakin jpg's by Anonymous Coward · · Score: 0

      I believe the slides to be true, and totally agree with Microsoft's opinion. You GPL folks are nothing but socialists.

    12. Re:It's a bunch of freakin jpg's by MegaFur · · Score: 1

      "... just about as useless as jpegs to Hellen Keller"?

      --
      Furry cows moo and decompress.
  3. Note that Free != freedom by Anonymous Coward · · Score: 1, Troll

    Stop equal Free Software with freedom, you don't really have much more freedom than with closed software, infact, in many cases you have much less.
    Diversity is good, but GPL is the wrong route as it kills diversity.

    Go public domain!

    1. Re:Note that Free != freedom by Dunark · · Score: 3, Insightful

      Diversity is good, but GPL is the wrong route as it kills diversity.

      No, it doesn't kill diversity. It kills MS's "embrace and extend", and *that* kills diversity.

    2. Re:Note that Free != freedom by Col.+Klink+(retired) · · Score: 4, Insightful

      > ...you don't really have much more freedom than with closed software, infact, in many cases you have much less.

      How is this possible? Closed source software never allows you to even see their source code, much less modify or redistribute it. Further, more and more closed source license even limit how you can USE the software. They often don't allow you to even install the program on more than one machine at a time.

      The GPL places NO restrictions on how you can use the program. As long as you don't redistribute, you have complete freedom to make any changes to the program to suit your needs. You can make unlimited personal copies and run on all of own machines.

      Only when you decide to redistribute a GPL'd program does it limit your freedom. Commercial software never allows you to redistribute it.

      So please tell me one instance where a closed source application has even a single freedom that the GPL doesn't already give you.

      --

      -- Don't Tase me, bro!

    3. Re:Note that Free != freedom by Selanit · · Score: 5, Insightful
      Stop equal Free Software with freedom, you don't really have much more freedom than with closed software, infact, in many cases you have much less.

      Okay, maybe I'm dense, but how does your line of reasoning go? The only restrictions I see in the GPL are that 1) You have to make your source available under the GPL if you make a modified version and you choose to distribute that version to the public, and 2) programs that use GPL'ed code fall under the GPL.

      That's it. You can use the program on as many machines as you want, give copies to your friends, all legally. You can even make modifications and keep the source to yourself, so long as you also keep the binaries to yourself. There is nothing in there to prevent you from being selfish. Heck, for most purposes you don't even have to accept the license. You can decline the GPL and still use the program all you want, you just can't legally modify it.

      Compare this to Microsoft's licensing policies. Let's take a specific example: Windows 98 OEM version. That Windows disc that came with your computer can only be used legally on your computer. If you replace, say, the motherboard, it's not the same computer anymore, and you no longer have the right to use that copy of Windows 98 on any computer at all. Similarly, if you sell the computer that the disc came with and build a new one, you cannot use it on the new computer, even if you wiped the old one clean before you sold it. And there are lots of other restrictions, too -- read through a Microsoft EULA some time. If you actually take the time to understand it, you will find that there are about a zillion restrictions on how you can use the program. And of course you are not allowed to modify it, and couldn't if you wanted to, unless you are a wizardly programmer who can read binaries and reconstruct the original source code from them.

      Compare this to the GPL, where there are only those two restrictions, and they only apply to developers. And the GPL is probably the most restrictive open-source license: others, like BSD-style-licenses, or the Zlib license, place effectively no restrictions at all on your use of the program. So, please explain to me: how is it that you have less freedom with open software than with closed?

      I must conclude that this AC is a troll. Dang. Oh, well, I've got karma to burn.

    4. Re:Note that Free != freedom by Chris+Johnson · · Score: 3, Insightful
      That's a peculiar point of view, since the only thing the GPL does (and it does it very thoroughly) is require that the code and ALL DERIVATIONS remain out there and accessible in a practical sense. That is ALL that is being required. It, and anything you do with it, cannot be bottled up. All the things done with it must remain not merely accessible but AVAILABLE.

      By contrast it's child's play to make closed software unavailable, even if it is to some extent accessible. One result can be that the dominant form of software can be completely unavailable and still block out other software from getting serious mindshare.

      Is war peace and freedom slavery, too? I'm sure many people will read your remark about GPL having 'much less' freedom and nod foolishly because that's what they want to believe, but in a practical sense only the GPL is really effective in competing against closed software. And what is wrong with competing against closed software? I thought that was the whole point for the proprietary guys?

    5. Re:Note that Free != freedom by BigBir3d · · Score: 2

      closed source != not free to redistribute

      closed source != commercial

      Please be specific when posting a difference in opinion.

    6. Re:Note that Free != freedom by Col.+Klink+(retired) · · Score: 2

      > closed source != not free to redistribute
      > closed source != commercial

      Fine, but how does this give you more freedoms? You can't make changes since you don't have the source, so it doesn't really help if you can redistribute or if you didn't pay.

      --

      -- Don't Tase me, bro!

    7. Re:Note that Free != freedom by Anonymous Coward · · Score: 0

      Um, I think MS offers more diversity that works then does Linux. I have been a Unix admin for 10 years now and linux/gpl/oss/etc still doesn't offer the same thing as MS. In many ways MS is still better.

    8. Re:Note that Free != freedom by Anonymous Coward · · Score: 0

      Stop equal Free Software with freedom, you don't really have much more freedom than with closed software, infact, in many cases you have much less.

      Okay, that makes no sense. Let's run down the FSF checklist, shall we?

      The freedom to run the program, for any purpose

      GPL software: YES

      BSD software: YES

      PD software: YES

      proprietary software: NO (must accept license before using, license usually restricts things like: running remotely, running multiple instances, running on the wrong # of CPUs, using the product to disparage microsoft, using the program for publishing benchmarks, etc)

      The freedom to study how the program works, and adapt it to your needs. Access to the source code is a precondition for this.

      GPL: YES

      BSD: YES

      PD: YES

      proprietary: NO

      The freedom to redistribute copies so you can help your neighbor

      GPL: YES

      BSD: YES

      PD: YES

      proprietary: NO FUCKING WAY

      The freedom to improve the program, and release your improvements to the public, so that the whole community benefits.

      GPL: MAYBE (see COPYLEFT terms)

      BSD: YES

      PD: YES

      proprietary: NOT EVEN POSSIBLE

      So, tell us about freedom? And how the GPL is worst than proprietary?

      If you have some other freedom in your own list, please let us know about it.

    9. Re:Note that Free != freedom by MacAndrew · · Score: 3, Insightful

      That's a peculiar point of view, since the only thing the GPL does (and it does it very thoroughly) is require that the code and ALL DERIVATIONS remain out there and accessible in a practical sense. That is ALL that is being required. It, and anything you do with it, cannot be bottled up. All the things done with it must remain not merely accessible but AVAILABLE.

      Yes, there's just one basic requirement. Now, a requirement, restriction, licensing term, whatever you want to call it, is why it is not free is the sense of public domain. Free software imposes its own sense of copyright, but it is still copyright, and they will sue you for infringing on it. I only understood this when I realize copyleft is just a politicized synonym for copyright.

      See GNU license. (" To protect your rights, we need to make restrictions that forbid anyone to deny you these rights." -- mild doublespeak, no? To protect your freedom we must limit it by requiring you to acquiesce to this license.) Notice that the document invokes that hoary old term "copyright" more than a dozen times.

      I'm not critizing free software -- really I think it's quite clever, inspired even -- but I believe it is merely a form of licensed software with really liberal "fair use" provisions. The copyright's holder's right to force you to comply persists throughout, so I think the political pitch is slightly misleading. I don't think it's some gross violation of freedom, but then neither is "closed" software -- if you don't like it, write your own "free" or even (gasp) public domain software. :)

    10. Re:Note that Free != freedom by Anonymous Coward · · Score: 0

      Do you know what diversity means??? Unix offering the same thing as MS would be reducing diversity, not increasing it. Like if all the Giraffes in the world became Zebras.

      And GPL software is not just Linux e.g. There are other GPL oses like EROS which are very different to "normal" OSes, and thus I would hazard that GPL stuff is more diverse.

    11. Re:Note that Free != freedom by DGolden · · Score: 1

      Well, I'm pro GPL - but I remember back in the Amiga P.D. days, where closed-source binaries were often released into the true public domain - in those days, one could take a disassembler, and modify them legally, and have a hope of that sort of thing working (helped that the amiga had no memory protection and the SetFunction() call for replacing functions in shared libraries on the fly) - i.e. reverse engineering was easy. Helps that m68k assembler is/was about 1000x prettier that x86 asm yuckiness.

      So, closed-source-public-domain did once give some freedoms.

      Clsoed-source-proprietary is another matter, since nowadays, thanks to successful lobbying, proprietary software makers have managed to retain legally-enforceable copyrights and patents and legally-enforceable prohibition of reverse engineering!

      --
      Choice of masters is not freedom.
    12. Re:Note that Free != freedom by runderwo · · Score: 2
      Hi, just some corrections.
      1) You have to make your source available under the GPL if you make a modified version and you choose to distribute that version to the public
      Not just "to the public"; it applies if you redistribute it outside your organization at all, even in a private transaction.
      You can decline the GPL and still use the program all you want, you just can't legally modify it.
      You _can_ legally modify it; you just can't redistribute it. A GPL-licensed program gives the user freedom to do _anything_ with it in using it. It only applies restrictions when the software is redistributed.

      Just some nits.

    13. Re:Note that Free != freedom by BigBir3d · · Score: 1

      For me freedom is the ability to do what I want with what I want.

      I am not a programmer, and I couldn't care much less about source than I do now.

    14. Re:Note that Free != freedom by Col.+Klink+(retired) · · Score: 3, Insightful

      How does closed source give you any more of "the ability to do what [you] want" than the GPL? I can see BSD or Public Domain letting you do more, but closed source? How?

      Since you don't care about source code, I can only assume you're not making derivative applications. So what freedom is the GPL taking from you?

      --

      -- Don't Tase me, bro!

    15. Re:Note that Free != freedom by BigBir3d · · Score: 2

      I am sorry, did I say that GPL was taking something from me?

      No.

      My point was that all closed source is not bad. To used a tired example:

      Should the programs that run aircraft control towers be GPL?

      If so, give me a specific reason why, that is not tired OSS socialist rhetoric, but is in fact to do with the function of this particular software itself.

    16. Re:Note that Free != freedom by Anonymous Coward · · Score: 0

      In fact you can sell someone the service of running a machine for them that runs a modified binary if you really, really wanted to (although that would be wrong... very, very wrong).

      In fact that's the great thing about the GPL, you don't sell software, you sell the service of running and troubleshooting the software.

    17. Re:Note that Free != freedom by Col.+Klink+(retired) · · Score: 2

      > I am sorry, did I say that GPL was taking something from me? No.

      You'd better go re-read the thread. The original post that I was responding to stated: "...you don't really have much more freedom than with closed software, infact, in many cases you have much less."

      I wanted to know how the GPL gives you less freedom that closed source. You're response was that closed source != commercial. True enough, but not really rebuttal to "closed source gives more freedom than GPL".

      I supposed if I were saying "GPL monotonically better than closed source" you'd have a point. But the topic at hand was freedom, not "which is better".

      --

      -- Don't Tase me, bro!

    18. Re:Note that Free != freedom by Anonymous Coward · · Score: 0

      It kills MS's "embrace and extend"

      Y'know... I've been thinking about this "embrace and extend" phrase that gets bandied about when ppl are MS bashing... Isn't this exactly what the GPL does? I mean, if you modify the source of a GPL product, you must release your product under the GPL too... Isn't this "embracing and extending" in a way too? ie, The GPL "embraces" your product if you try to "extend" a supposedly "free" bit of code... Doesn't sound like real freedom to me...

  4. Re:fp by flapjackboy · · Score: 0, Offtopic

    Not fp, spam.

  5. From Academia to Consumer by very · · Score: 5, Interesting

    A lot of time, softwares are developed by the Academia and heading straight to the consumer. And those software are usually distributed freely for non-commercial use (sometimes they are free for all).

    Apparently the Industry (a.k.a. Micro$oft) want the finding and development to go through the industry first.

    One motive: MONEY

    1. Re:From Academia to Consumer by Evil+Adrian · · Score: 2

      Well, the industry makes money off of computers, that is how they stay in business. There is absolutely nothing wrong with a company wanting to make money, that is the whole POINT of a company being in business in the first place. Companies don't survive if they don't make money. So, a big fat "duh" to you sir.

      Oh, and that "$" instead of an "S" in Microsoft is really mature.

      --
      evil adrian
    2. Re:From Academia to Consumer by Anonymous Coward · · Score: 2, Insightful

      And computing seems to be one of those few areas where academia and amateurs can currently do a better job than companies.

      No, there's nothing wrong with a company wanting to make money - BUT -

      Companies don't have some right to profit - the norm is for them to fail. Very few profit. Why should they be propped up rather than just allowing them to fail? If they can profit then let them - if they're trying to sell ice to eskimos^Winuit, let them, but don't support them when they plan legally-mandated polar-ice-melting so that they can do so!

      To labor the point a little more - don't let them give Einstein a lobotomy so that little timmy can get relatively higher grades.

      P.S. I find the $ in Micro$oft to be a good conversation-starter, which then allows me to lead into why ms is bad for the consumer. I don't care if some teenager thinks it's immature, or some astroturfer says it's immature. It's not. You legitimise someone by using the name they choose for themselves rather than naming them with a derogatory name. I choose, quite deliberately, to insult Microsoft.

      P.P.S. If there was nothing wrong with financial profit at any moral cost, then the $ would be a compliment, not an insult. Clearly, even you feel that there IS something wrong with that, since you're objecting to its use.

      So I hereby declare "inconsistency" on you. Closely followed by "probable shenanigans".

    3. Re:From Academia to Consumer by gotan · · Score: 2

      Sure it's a good thing for a company to make money. But if they do that by taking something away from me (e.g. free software) so they can sell it to me I don't have to agree that this is best for all concerned, do i?

      It's really sickening how people get screwed over by big corporations and then even cheer them on because "it's their godgiven right to make money any way they can". No it isn't they have to play by some rules too, at least if their customers come to their senses and don't buy their products if they are screwed over by their business practices.

      The important part is telling the people how and by who they're screwed, and that they can do something about it. The equation 'making money = good for business' has two sides, if people react appropriately to bad business practice and boycot then it becomes 'bad business practice = bad for business'.

      --
      "By the way if anyone here is in advertising or marketing... kill yourself." -- Bill Hicks
    4. Re:From Academia to Consumer by cookd · · Score: 1

      Huh? No way.

      Microsoft just wants to be sure that Academia doesn't start releasing through GPL, cuz that would screw over any potential commercial use.

      --
      Time flies like an arrow. Fruit flies like a banana.
    5. Re:From Academia to Consumer by istartedi · · Score: 1, Troll

      What software goes straight from Academia to consumer? Nothing I can think of. I don't think I've ever seen (C) University of (whatever) in a retail program, except of course BSD but that's not something that most consumers have even heard of.

      Way too much of the software I've seen from Academia is placed under an "Academic use only and you can negotiate rights if you want" deal. That's even worse than GPL because when you see that "call us" business it usually means they want thousands of dollars just to let you see the code. That's kept a lot of good libraries out of shareware and forced small shops to re-invent the wheel. It would be nice if these universities published some kind of royalty schedule for small developers. If they still want the big corporations to "call them" that's fine. The big corps have the $$$.

      --
      For all intensive purposes, "whom" is no longer a word. That begs the question, "who cares"?
    6. Re:From Academia to Consumer by MegaFur · · Score: 2

      Oh, and that "$" instead of an "S" in Microsoft is really mature.

      It's okay, we're allowed. ESR said so(scroll to the bottom). Yeah I know, I'm pathetic.

      --
      Furry cows moo and decompress.
    7. Re:From Academia to Consumer by gpoul · · Score: 1

      IMHO they just said that it should not be released under the GPL but rather on a BSD-style license. - What's wrong with that?

      They don't take anything away from you. - It's the other way around. If you use the GPL you're taking opportunities away from them, which they, obviously, don't want.

      Using GPL in these cases would clearly harm innovation in IT. - Do we really want that for the sake of the GPL?

    8. Re:From Academia to Consumer by Anonymous Coward · · Score: 0

      The GPL guarantees opportunities for their customers, which only threatens them because of their morally flawed business model that relies on control over users. Incompatibility isn't innovative.

    9. Re:From Academia to Consumer by DunbarTheInept · · Score: 2

      What software goes straight from Academia to consumer?

      Does this phrase look familiar:

      "Copyright (c) Regents of the University of California. All rights reserved."


      That's on a hell of a lot of direct-to-consumer software. Everything that came directly or indirectly from BSD.

      --

      Don't label something "offtopic" unless you know the topic well enough to tell what's on topic.

    10. Re:From Academia to Consumer by istartedi · · Score: 1

      Did you read my post?

      --
      For all intensive purposes, "whom" is no longer a word. That begs the question, "who cares"?
    11. Re:From Academia to Consumer by DunbarTheInept · · Score: 2

      Yes, but somehow I missed the reference to BSD the first time. Sorry about that. Still, you *are* aware that that BSD license is in lots of other stuff to besides unixes, right? The TCP/IP stack of Windows, for example, is directly derived from the BSD TCP/IP stack, and so the University of California license notice appears buried somewhere inside the legal stuff you get with Windows.

      Also, another example is Alladin. It was a filter to convert from postscript to the various proprietary printer codes used by vendors. Until ghostscript became ready, it was the primary print driver used by both FreeBSD and Linux distributions. It was a "Copyright University of Wisconsin" program, and you had to download it directly from the main site. The only restriction on the license was that people could only get a stripped down old version from others and to get the full recent versions you had to visit the Alladin homepage and download from there. I guess that was done so they could have a record of how much it was being used. (This is typically the case with groups funded by grants - the granting agencies want to see how many people are making use of the work done with the grant money - to see if continued funding is justified.)

      --

      Don't label something "offtopic" unless you know the topic well enough to tell what's on topic.

  6. Are slashdotters that gullible? by Anonymous Coward · · Score: 3, Funny

    Yes, you too can believe anything and everything that is posted on the internet! Especially when someone claims it was created by MSFT! Anyone can whip up some slides, take pictures of them, and post them on a random web site.

    1. Re:Are slashdotters that gullible? by Chester+K · · Score: 3, Insightful

      Not to mention... can we find something new to report on? Microsoft doesn't like the GPL. Ok. We got it the last 20 times a story was posted exposing that fact.

      Do we really need another story about it?

      --

      NO CARRIER
    2. Re:Are slashdotters that gullible? by Ytrew+Q.+Uiop · · Score: 1

      Yes, you too can believe anything and everything that is posted on the internet! Especially when someone claims it was created by MSFT! Anyone can whip up some slides, take pictures of them, and post them on a random web site.

      However, it's not legal to knowingly present false statements about a company as if they were fact. If the statements are provably false, Microsoft can sue for libel.

      I am not a lawyer. If I were, this sentence would be too expensive to be worth reading.
      --
      Ytrew

  7. Strange... by Frothy+Walrus · · Score: 1

    Considering ESR's Halloween VIII stressed that decrying the GPL was so ineffective for MS, even their market researches knew it.

  8. 1 comment and already /.ed..... by jludka · · Score: 0, Offtopic

    I think the Visual Studio .net ad that popped up when I opened the comments page explains Microsoft's position well enough....

  9. Nonsense by krog · · Score: 1, Troll

    There was a long period in which Microsoft did not suck. This ended in 1991 or so, at which point they had the money to be total fucking cockbiters to everyone in their path. Shortly thereafter their software quality went waaay down.

    Word 5.1 for Macintosh is the best word processor I've ever used.

    1. Re:Nonsense by weave · · Score: 5, Interesting
      There was a long period in which Microsoft did not suck.

      Read the interview with a former microsoft developer on kuro5hin for an insight into maybe why this is so.

      Executive summary: Microsoft employees are arrogant assholes. (insert sweeping generalization disclaimer here)

      Quote from interview: Microsoft constructed an enabling environment for socially obnoxious behavior: it was welcomed and rationalized into positives. If you were late for meetings it meant you were busy doing important work, if you were extremely confrontational it meant you were passionate about your job, if you required subordinates to work long hours it meant you were committed to the product, if you turned down everyone you interviewed it meant you weren't soft, and so on. ... And some of that behavior trickled out into meetings with customers and partners, where they were correctly seen as negatives and helped foster the anti-Microsoft attitude. But since Microsoft kept hiring and promoting obnoxious people, they kept being obnoxious.

      Now this is just one former employee's opinion. But in sales meetings I have had with Microsoft, (I'm an IT manager for a 13,000 user college), I've seen the same attitudes.

    2. Re:Nonsense by ajp · · Score: 2, Insightful

      I'd disagree. I think Microsoft sucks less now than it did previously.

      Microsoft's worst (alleged or proven, I don't care) dirty trick, IMHO, was Windows telling me that Digital Research DOS was incompatible. That kind of behavior made me a happy OS/2 user for years until I had it pounded in my brain (by IBM, nonetheless) that IBM really is a big, nasty corporation.

      I actually don't see anything wrong with MS's attitude toward OSS or Shared Source. They're afraid of the GPL for the same reason that Apple (all worship Apple, benevolent charity and protector of good!) built OS X on top of BSD. Microsoft--get this--is in it for the money. Just like RedHat is. If RMS could sue Microsoft for having GPL'd code in the NT source base it would really cramp MS's style. That, frankly, is frightening to anyone who doesn't totally subscribe to RMS' goal of eliminating software copyrights wholesale.

      As for the interview with the ex-developer (NB: here I go again with ad hominem arguments) don't you think that it's a little easier to criticize Microsoft after you've worked there 10 years? MS probably made that guy filthy rich. Give me millions of dollars and I'll gladly drive the high moral ground in my brand-new gold plated gas guzzling SUV.

      This is not to say there are no "arrogant assholes" at MS: the interview appears to be written by a prime example. Many sales people (your contacts) also fit that bill. This is merely to point out that MS, as a corporation, has similar goals to those of most corporations. (Similarly, Slashdot, like Usenet in the grand old days, is filled with self-righteous idiots. Oops, ad hominem again! Or is that ad homini?)

    3. Re:Nonsense by marcovje · · Score: 1


      Personally, I don't blame Microsoft, but the US government, and specially the anti trust authoroties.

      Any large and (de-facto or real) monopoly is dangerous.

      The damage is two-fold,

      - the damage caused by the monopoly (killing of innovative companies, specially when they are smaller, and the fact that they can ignore customers)

      - I think if they had put a brake on Microsoft say a few months before Windows 2000, we could now already see the fruits of a the synergy a more cooperative and interoperable Microsoft would bring

    4. Re:nonsense by cookd · · Score: 1

      You can't just take research results out of a paper or journal and use them. There are always IP issues to worry about. So what you are saying is that if a university releases something under GPL, but I don't want to be bound by the GPL restrictions, I can just magically lift the same information from some other source? Nope. First, there isn't always another source. Second, if there is, it probably is missing a lot of important information since that information wasn't worth discussing in the journal (aimed at those who need just the facts, ma'am) but is necessary for a proper implemenation.

      --
      Time flies like an arrow. Fruit flies like a banana.
    5. Re:nonsense by Todd+Knarr · · Score: 2

      Yes you can. This was settled in court back in the IBM vs. Phoenix case.

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

      >But since Microsoft kept hiring and promoting obnoxious >people, they kept being obnoxious.

      Yep. The most obnoxious person in my company right now is a former MS employee.

      I didn't realize that jerkiness was a Microsoft value.

  10. Not about freedom? by e.m.rainey · · Score: 2, Insightful

    And why should they care about your freedom unless there is money to be made in the process? They are, after all, a business, not a charity.
    They want a liscense that protects their freedom to charge for their work!

    --
    The next remark is false. The previous remark is true.
  11. Good slides by Bjarne+Bula · · Score: 4, Insightful

    It seems someone at Microsoft has sat down and thought long and hard about this. I'm certainly not one of MS bigger fans, but I think they pretty much got this one right.

    Naturally, they don't like the fact that they can't take something under the GPL and integrate into their own products, like they have with BSD-licensed code. And, on some level, they have a very good point about products of research that are released under the GPL. The only value they have to any company working on a closed-source product is as an example, while a BSD-style license would have allowed them to take the existing code and adapt it.

    In this aspect, the GPL actually harms interoperability and if the purpose was to give the research results a wide impact, releasing them under the GPL would be counterproductive.

    I live under no illusions that all software will one day be open source, and perhaps it would be a good thing for people to think an extra time about the consequences of their choice of license.

    For standalone programs, the GPL makes a lot of sense, but perhaps BSD-style licenses are more appropriate for prototypes and example implementations. Perhaps also the operating systems themselves, but that's a harder call.

    1. Re:Good slides by Anonymous Coward · · Score: 0

      Taking a different perspective; the goal of the FSF and the free software movement is not really the GPL, but for it to be unessisary to have the GPL since all software would naturally and logically be free. I completely agree the GPL may impose some limitations as you do correctly point out, especially to those seeking to remove freedom from others, and perhaps in the process limits those who might create further works based on the original research. However, I would argue that those restrictions actually do FAR LESS harm than the BSD license, since the latter allows derived works to be permenantly closed off from the public. Once the work is closed off it no longer matters if the original research was free or not because the derived versions people can use are proprietary ones and nobody else is permitted to create or support further interoperability with those closed off implimentations. In the long term, the BSD license will completely KILL OFF further development by others except by an exclusive few, especially if a monopoly situation exists, as it does today.

    2. Re:Good slides by interiot · · Score: 3
      • And, on some level, they have a very good point about products of research that are released under the GPL.

      So there's value for a variety of licenses. Which is good, because we have a lot of 'em.

      Use BSD when the majority of time spent was in coming up with the requirements/design. Use GPL when the majority of time spent was in coming up with the implmentation.

    3. Re:Good slides by Master+Bait · · Score: 2, Insightful
      There is NOTHING that prevents Micros**t from adding their 'embrace & extend' junk to any GPL product and then charging money for it. Nothing. Their only beef is that they can't get free source code, then 'embrace & extend', release it for money and then prevent other people from 'embracing and extending' their stuff.

      Microsoft is lazy, they want free code but they don't want anybody else profiting from it.

      --
      "Only in their dreams can men truly be free 'twas always thus, and always thus will be."
      --Tom Schulman
    4. Re:Good slides by Todd+Knarr · · Score: 5, Insightful

      Actually the GPL doesn't prevent companies from using the covered IP in their products. What it does do is force them to negotiate a suitable license from the original author of the covered IP (if they don't want to give away their own IP, that is). The big advantage to companies of the BSD license is that they can use the covered IP without negotiating with the original author and probably having to pay for the IP they use. That's the heart of MS's position: they want to be able to use everybody else's IP for free while still forcing everyone else to pay to use MS IP.

    5. Re:Good slides by thomasj · · Score: 2, Informative
      That's the heart of MS's position: they want to be able to use everybody else's IP for free while still forcing everyone else to pay to use MS IP.
      Oh please, would you?

      The story of these slides (MS or not), is that software funded by tax money, or are research done "for the general technological advance" should maybe be released under a more relaxed license, rather than a political licence.

      The outstanding phrase of the slides is: "GPL -- good the individual, bad for the industri", saying that: it is good for privately developed software to demand a giveback of co-developers if they add to your software, but projects that has been paid by everybody, including the industry, should be usable in a way that makes sense to more than the OSS crowd.

      You don't loose anything by MS downloading software developed by DoD or NASA or whatnot and put in their own software, since the development is already paid for, and you can download it too.

      I don't mind that people release under GPL and consider it to be reasonable that others should give back if they release derived works, it is fine. I prefer to release software under BSD or the dual Perl AL/GPL, since it makes better sense to me, and that is fine with me that other people "steal" the code since my concern is that my code gets used even by MS. So be it.

      But tax paid code (or industrial funded code) is really a different story.

      --
      :-) = I am happy
      :^) = I am happy with my big nose
      C:\> = I am happy with my OS
    6. Re:Good slides by Anonymous Coward · · Score: 0
      If network effects make the proprietary version dominant (as they tend to in the face of strategic incompatibility), I lose the ability to learn from and improve the tools I use, which is our birthright as thinking beings as well as the source of progress for our civilization. Not to mention any chance of making a living fixing and customizing the software in a competitive market.

      Subsidizing proprietary software (supporting one already-prosperous industry to the detriment of all others) is at least as political as not doing so.

    7. Re:Good slides by Rogerborg · · Score: 3, Insightful

      That's precisely what LGPL is for, but LGPL is also on Microsoft's shit list (c.f. their infamous specification download licensing restrictions). Compare and contrast:

      • BSD: They can take it and use it as long as they don't remove the copyright or license terms from the source. They don't have to tell anyone that you're using it. If we work it out (as we did with the TCP/IP stack) they still don't have to tell anyone that they've modified it, or how they've modified it.
      • LGPL: They can take it and use it as long as they don't remove the copyright or license terms from the source. They have to tell people they're using it and make the source, including their modifications, available.

      Now, how exactly does BSD help interoperability? We had to guess that Microsoft was using the BSD TCP/IP stack, then we had to guess about the changes that they'd made. But it became an open secret that they were using it back in the day (I don't doubt it's been cleanroomed now), so it's not as though it would harm Microsoft to say that they were using it, and to say exactly what version, and with what modifications. We could argue that their improvements (i.e. bug fixes and optimisations rather than protocol changes) are valuable trade secrets, but remember that they got the source free and gratis and that they used it to make a lot of money. They can't afford to give a little back? Even to the extent of just saying "The Microsoft TCP/IP stack is based on the FreeBSD TCP/IP stack version 1.foo, with the following differences..."?

      I believe that the only real reason that they prefer BSD over LGPL is that it allows obfuscation and protocol changing behind the scenes, i.e. to reserve the right to harm interoperability if it becomes convenient for them to do so. Sure, they didn't, but then again, they haven't made the source available, and they haven't cornered the server market yet either. Would you bet your life that there aren't proprietary extensions lurking in there just waiting on the day when they can afford to turn them on and cut off non-Microsoft clients from Microsoft servers? Seriously: bet your life on it?

      All that said, you're de facto correct. The only reason Microsoft chose BSD TCP/IP was because of the license. But that's their irrational childhood trauma issue, and it's up to us to patiently council them until they get over it. There is hope though. Given that they're making noises about shared source now, I wonder how long it will take for them to realise that LGPL, used judiciously, can be used by them as well as against them.

      --
      If you were blocking sigs, you wouldn't have to read this.
    8. Re:Good slides by Todd+Knarr · · Score: 5, Insightful

      Why is it a different story? The taxpayers paid for it, precisely why should a business be allowed to profit from it without paying royalties back in one form or another? What MS is asking is to be allowed to reap the profits while letting the taxpayers foot the bill. Sorry, that's not kosher in my book. And yes, we did lose something when MS used software developed by the DoD and NASA without paying: we lost the funds that went into developing it and that aren't being recouped.

      And it still comes back to, if the stuff was put out under the GPL, the company can go back to the agency that did the work and negotiate a license other than the GPL.

      Personally I think something along the lines of the LGPL, or a modified BSD license which requires that the software being used and any modifications/enhancements to it be made available under the terms the original software was gotten under, would be more appropriate than the GPL. It still boils down to, a private company should not be able to take taxpayer-funded property and use it to make a profit without some of that profit going back to the taxpayers in some way.

    9. Re:Good slides by Anonymous Coward · · Score: 0

      The only reason that the LGPL is on MS's shit list is because of association. If they allowed the coders to use the LGPL, perhaps some would think that they would also be allowed to use just plain GPLed code. It is simpler to say that (and easier to monitor) both the GPL and the LGPL are not allowed than to allow half of the two.

    10. Re:Good slides by jez9999 · · Score: 1

      Someone hass modded this post down as a troll, probably a Microsoft employee, because it's a FUCKING good point. Best post I've seen all day in fact.

    11. Re:Good slides by eer · · Score: 1

      I think I agree with you - MS is certainly willing to pay for IP. And they'd like to use "free" IP when it's good (so would we all). The BSD license lets them/us do that without imposing political economic decisions on us.

      Government sponsored IP should be free, in the BSD sense, and not incumbered in the GPL sense.

    12. Re:Good slides by the+gnat · · Score: 2

      I agreee with you, to a point. Microsoft has taken this position a step further- government should be actively prohibited from working with GPL'd code. This much is evident from their stance on NSA Linux. If the NSA were to write some software from scratch and release it to the public, I would certainly argue that a BSD-style license or simply public domain would be ideal. However, I do not think they should be prevented from working on software with more restrictive licenses- and this includes truly proprietary ones.

      The endpoint of Microsoft's argument would be that taxpayer-funded development could not be done with Microsoft's code under a shared-source agreement. This would prohibit any government agency and many universities from using Microsoft's code, eliminating any usefulness of the Shared Source program, and would probably just drive them further into the Free Software camp (even if they can't use the GPL).

    13. Re:Good slides by cookd · · Score: 1
      Different entities have different business models, with different needs.
      • Individual: Make some software, let it spread. Don't steal it from me -- obey the GPL/BSD/MIT/etc. license. (GPL is appropriate.)
      • Free software created by a company: My company needs to profit from this somehow. Support? Docs? Just so long as nobody else can get an unfair advantage on us, we're ok. We can take IP under GPL, since we're releasing under GPL anyway. (GPL is appropriate -- prevents others from providing significantly better support than the original authors, so the original author can still justify the investment.)
      • Non-free software company: We depend on software sales for our profit, so we can't give OUR IP away to others. When we get IP from others, we have to make sure we have free and clear usage of it. When we share IP with others, we have to make sure that they agree to what they can and can't do with it. My company can't risk tainting the code we write with anything that will open us up to lawsuits.


      All of these business models are perfectly ethical and reasonable. Some software is so challenging to write that decent versions of it would NEVER appear without the more direct profitability of the non-free software company. Other software is less immediately profitable, so it would never appear without the individual who only cares for recognition, if even that much. Some software provides non-sales opportunities for profit (or break-even, which is ok if the company paying for the software also needs the software), opening up a window for the free software market. But why should one of them be singled out as not being allowed to use the IP that the other two can use, if all 3 paid through tax dollars?

      As far as the GPL applying to government sponsored research -- Microsoft wants to be able to use this research just like anybody else. What if TCP/IP (research results, not code) had been released under GPL? The free OSes could use it no problem, but no commercial OS would be able to use it, and there would likely be no TCP/IP in general use today. And even when just TCP/IP code is released under GPL, then the software companies have to clean-room re-engineering of it. This is especially stupid if a great deal of the effort was figuring out how to make the code work in the first place.

      And how do you negotiate a suitable license when something is GPLed? You find any entity that had anything to do with that code and negotiate a separate license with that entity. If it is just the government, and you can do it, then why didn't the government just release it under BSD license to begin with? But otherwise, you CAN'T DO IT! The derivative work, with the new research added is pretty hard to split from the earlier existing work. (You may need to review the GPL if you don't get this -- the point of the GPL is to make it so that derivative works CAN'T be relicensed, yet you say that MS should just get the IP relicensed... Anybody else see the problem here?)

      So Microsoft is claiming with these slides that if everybody (free-software proponents and non-proponents) paid equally through taxes for IP (which is debatable, since MS puts a lot more into the Tax system than any other software company), why should they get the shaft?
      --
      Time flies like an arrow. Fruit flies like a banana.
    14. Re:Good slides by cookd · · Score: 1

      The taxpayers paid for it, precisely why should a business be allowed to profit from it without paying royalties back in one form or another?

      Well, it sounds like in this case those using it under the GPL had better pay royalties, too.

      What MS is asking is to be allowed to reap the profits while letting the taxpayers foot the bill.

      What MS is asking is that ANYBODY, themselves included, be allowed to reap the profits. <OR> put another way, it sounds like YOU want to reap the benefits and let the taxpayers foot the bill, but prevent Microsoft from being able to do so. (And if you are thinking about responding that "the code will now be closed source," you need to think again: only Microsoft's product will be closed source; the research is STILL open.)

      What agency? Microsoft is trying to remind the govt. that if you take a starting point that is under the GPL and apply research to it, the resulting work is under the GPL. It then becomes tricky to separate it back out. I thought people around here actually knew what the GPL was and how it worked! They talk about it all the time. And assuming it is possible, why should one group have to go negotiate a new license while other groups don't? Is the non-free-software community that much less deserving?

      The argument of the last paragraph (using property) again neglects the fact that the "property" is not diminished or taken away when Microsoft or any other company puts it into their product. It is a public good now. The original is still available. Microsoft paid for any modifications/enhancements without taking the original away.

      --
      Time flies like an arrow. Fruit flies like a banana.
    15. Re:Good slides by cookd · · Score: 1

      This isn't subsidizing proprietary software. This is subsidizing any software org that makes use of the contribution. If Microsoft manages to make the dominant tool, so be it. That would be because they added some value to it that made it more usable than the tool of anyone else.

      I'm a bit puzzled about how you obtained this far-reaching birthright. It sounds to me more like something you would like to have. Not everything you would like to have is a birthright.

      --
      Time flies like an arrow. Fruit flies like a banana.
    16. Re:Good slides by cookd · · Score: 1

      How do they prevent other people from profiting from it? The code they "steal" in this hypothetical situation is still there, and you are still welcome to profit from it if you can.

      --
      Time flies like an arrow. Fruit flies like a banana.
    17. Re:Good slides by bnenning · · Score: 2
      And yes, we did lose something when MS used software developed by the DoD and NASA without paying: we lost the funds that went into developing it and that aren't being recouped.


      You didn't lose anything. The DoD and NASA source code is still there for you to use.


      Personally I think something along the lines of the LGPL, or a modified BSD license which requires that the software being used and any modifications/enhancements to it be made available under the terms the original software was gotten under


      Sounds good to me. I don't have a problem with requiring modifications to taxpayer-funded software to be public, but requiring developers to GPL their own code that touches it goes too far.

      --
      How to solve most of our problems: 1.Lots of nuclear plants. 2.Cure aging.
    18. Re:Good slides by Anonymous Coward · · Score: 0

      Here's my rule of thumb:

      If you like the terms of the GPL, use the GPL.

      If you like the terms of BSD, use the BSD license.

      If you don't like any free software license, then your software better come with dancing girls that suck my dick all night long, because otherwise I'll stick with Free software.

    19. Re:Good slides by Anonymous Coward · · Score: 0

      What if TCP/IP (research results, not code) had been released under GPL?

      Don't confuse engineering specs and code. They are completely different things.

    20. Re:Good slides by Anonymous Coward · · Score: 0

      The only reason Microsoft chose BSD TCP/IP was because of the license

      Complete bullshit. Berkeley TCP/IP was the official US Government reference implementation and, at the time, was used in virtually every TCP/IP implementaton. Microsoft had strong compatibility reasons to use it.

    21. Re:Good slides by cookd · · Score: 1

      Umm, I didn't. I recognized that this was not in line with the exact nature of the GPL. Guess why I clarified things right before the statement, and went on to make a more realistic example.

      --
      Time flies like an arrow. Fruit flies like a banana.
    22. Re:Good slides by Todd+Knarr · · Score: 2

      (You may need to review the GPL if you don't get this -- the point of the GPL is to make it so that derivative works CAN'T be relicensed, yet you say that MS should just get the IP relicensed... Anybody else see the problem here?)

      No problem. Remember that the original author of the code isn't bound by the GPL. If I wrote the code and released it under the GPL you can't relicense it, but I can release it under any other licenses I want.

    23. Re:Good slides by sheldon · · Score: 3, Informative

      I have a question.

      If John Smith releases product Foo under the GPL. It becomes successful over a few years and Fred, Bob, Jay and Jake all submit changes.

      Does John Smith still have the right to sell a license to the Bar company for $X? Somehow I don't think he does.

      That's the heart of MS's position: they want to be able to use everybody else's IP for free while still forcing everyone else to pay to use MS IP.

      No, that's really not the heart of MS's position. Most companies realize that there were a variety of acts(look up Dole-Bayh) passed by Congress in the 1980's that encouraged research firms to license their work to corporations, so as to build up a synergy of research and implementation. I'm sure Microsoft would gladly pay a licensing fee to get their hands on innovative research. It wouldn't be the first time they've paid someone for their technology, would it?

      What they don't want is for that research to have been released under the GPL such that the work is now potentially tainted by other people's contributions such that they cannot legally buy rights to it from the research group without putting themselves at risk to turn over the work that they created.

      You don't seem to understand that this debate has nothing at all whatsoever to do with money. Money is a symptom, not the disease.

      They're simply concerned that technologies will be chosen as standards which are not available to everybody on reasonable terms. What's interesting about this is that the Linux Community and Microsoft are both concerned about the same thing.

      People on /. complain endlessly about patents being inserted into open standards. The reasoning is the same, the licensing terms conflict with your chosen business model. Well the GPL conflicts with Microsoft's business model, and there is no denying that... the GPL was designed specifically to conflict.

      You want the same things, just two different sides of the coin. If you'd quit whining about how evil Microsoft is you'd probably realize this and could work together to establish it.

      But as long as you keep fighting Microsoft, they are going to fight back. You try to force source code to be released under the GPL, then Microsoft is going to patent things to prevent you from using them.

    24. Re:Good slides by sheldon · · Score: 2

      The taxpayers paid for it, precisely why should a business be allowed to profit from it without paying royalties back in one form or another?

      Oh please! This has nothing to do with paying royalties.

      IBM is now selling hardware with Linux on it. Do you think they are paying royalties? No... So this argument that the GPL prevents companys from profiting from the software is complete utter nonsense.

      If that was really the question, then rather than the GPL the software would be licensed under something like the BSD license only it would state "for non-commercial use only" in there somewhere. Hmm, weird, where have I seen that before?

      Then this statement would be accurate: "And it still comes back to, if the stuff was put out under the GPL, the company can go back to the agency that did the work and negotiate a license other than the GPL."

      The intent of the GPL is only anti-commercial in that it makes the basic assumption that software developers should have no value attached to their work... all the value is really in the hardware.

      The GPL specifically attacks the business model that Bill Gates created, but it provides completely favorable terms to people who are just trying to sell hardware and want some software to throw on. That's why there is all this confusion about whether the GPL is anti-business or not.

    25. Re:Good slides by sheldon · · Score: 2

      I thought people around here actually knew what the GPL was and how it worked!

      I think they know, but they pretend that these things aren't true so as to not scare anybody away from using it.

      The goal is majority adoption, once they have that and everybody is dependent upon GPLed code... then they pull out the fine print.

      It's the Embrace and Extend model that people keep accusing Microsoft of.

    26. Re:Good slides by Lochin+Rabbar · · Score: 1

      If John Smith releases product Foo under the GPL. It becomes successful over a few years and Fred, Bob, Jay and Jake all submit changes.

      Does John Smith still have the right to sell a license to the Bar company for $X? Somehow I don't think he does.

      John Smith has the absolute right to sell the Bar company a GPL license for Foo, in order to sell it under any other license he needs the permission of the other contributors to the code. There is nothing to stop him from only accepting contibutions to his branch of Foo under the condition that contributors give him a right (license) to sell the code under another license in addition to the GPL. Of course he might have to negotiate a percentage of potential royalties for such an agreement, and many potential contrbutors might not want to be part of a such a deal, but that's business.

      If John Smith wants to sell on the code for without agreement well tough. He should of been open about his intentions in the first place. He still has the right to sell on his own parts of the code under any license he chooses, and he could sell his services to a company that wishes to implement a similar product. It's the code that's copyrighted not the design.

      What they don't want is for that research to have been released under the GPL such that the work is now potentially tainted by other people's contributions such that they cannot legally buy rights to it from the research group without putting themselves at risk to turn over the work that they created.

      It's code that's GPL'd not research, they would still be able to study the technology. Surely you're not saying that Microsoft lack the capabilty to write their own code, though evidence from their attempts to write their own TCP/IP stack might suggest that you're right.

      You don't seem to understand that this debate has nothing at all whatsoever to do with money. Money is a symptom, not the disease.

      No money is the disease, and closed source is the disease. The purpose of closed source is to increase the customer's reliance on a particular vendor so that the vendor can increase their revenue stream. The GPL protects customers, including Microsoft, from being so reliant.

      They're simply concerned that technologies will be chosen as standards which are not available to everybody on reasonable terms.

      Standards and code are not the same thing, just because there is a GPL implementation of a standard it does not mean that someone else can not produce another implementation of that standard and license it how they choose.

      People on /. complain endlessly about patents being inserted into open standards. The reasoning is the same, the licensing terms conflict with your chosen business model.

      You confound the effect of patented technology with the effect of copyrighted code. Copyrighted code does not prevent another implementation of the same technology, patents do precisely that.

      Well the GPL conflicts with Microsoft's business model, and there is no denying that... the GPL was designed specifically to conflict.

      No GPL'd code competes with Microsoft code in the market place, and that is what Microsoft can't stand.

      You want the same things, just two different sides of the coin. If you'd quit whining about how evil Microsoft is you'd probably realize this and could work together to establish it.

      Microsoft want open source freely redistributable code and open standards? Have you been smoking crack?

      But as long as you keep fighting Microsoft, they are going to fight back. You try to force source code to be released under the GPL, then Microsoft is going to patent things to prevent you from using them.

      Microsoft want total domination and they will use patents, lobbying, forced buyouts, lies, and whatever else it takes to achieve that end. They want all competing product to go away, that is why they despise the GPL, because successful GPL'd products tend not to go away.

    27. Re:Good slides by cookd · · Score: 1

      Right, but once there are a lot of contributors (such as if you didn't start from scratch on your project), YOU can't relicense it either. So when the government does research and bases it on GPL stuff, the result it pretty useless to industry.

      --
      Time flies like an arrow. Fruit flies like a banana.
    28. Re:Good slides by cookd · · Score: 1

      Yeah, too bad.

      (I'm sure that anybody that remembers my name in the posts think that I'm avidly pro-Microsoft. I'm not. I've been ticked off by Microsoft every once in a while since 1985, longer than most people on SlashDot have been using computers. I'm just avidly anti-illogical-argument and avidly anti-hypocrisy. And since the most illogical arguments seem to be Microsoft-bashing, that is where I speak up most often.)

      --
      Time flies like an arrow. Fruit flies like a banana.
    29. Re:Good slides by Todd+Knarr · · Score: 2

      Unless they've taken it into account, eg. the way the FSF does with their GPL'd software. And note that you can use the results, it's just the code itself that would be GPL'd. Eg. if a company wanted to use a GPL'd protocol stack without negotiating a different license, they could simply taken the protocol definition and do a clean-room implementation of it.

    30. Re:Good slides by Anonymous Coward · · Score: 0

      If industry insists on decrepit business models that rely on control over their customers, they're pretty useless to civilization.

    31. Re:Good slides by 4r0g · · Score: 1
      "The big advantage to companies of the BSD license is that they can use the covered IP without negotiating with the original author and probably having to pay for the IP they use."

      I have to disagree slightly with you there. If Company X owns IP for Algorithm Y, then Company Z must pay Company X for using Algorithm Y, no matter what the software licence is, BSD or GPL. Of course, the burden of proving that Company Z is using Algorithm Y is on Company X, but that doesn't change the fact who owns the IP and who is commiting an IPR infringement. Proving that someone is using modified/IP'd/licenced software is as difficult with both BSD and GPL, if we're talking about closed source.

      In addition I'd like to comment on the alleged MS FUD; The argument that GPL forces you to give up your IP is not valid. You cannot patent source code, but you can patent a method/algorithm that is implemented in source code. But of course, I don't have to tell you guys that...

      --
      - 4r0g
    32. Re:Good slides by gpoul · · Score: 1

      I have to totally agree!

    33. Re:Good slides by gpoul · · Score: 1

      The real problem is that if many people modify the GPLed code and contribute changes back that you have to negotiate with a lot of people. (Just look at the THANKS files of any GNU program and you get the idea)

      For academic use I think a BSD-style license is just the right thing to do.

    34. Re:Good slides by gpoul · · Score: 1

      I have to totally agree with your statements but it is rather strange that MS and the OSS community seem to be on the same side on the patent issues :)

    35. Re:Good slides by gpoul · · Score: 1

      MS and its employees are also tax payers and IMHO also deserve to use software developed with their money.

    36. Re:Good slides by gpoul · · Score: 1

      A license doesn't attack. The people that use it attack someone or not.

    37. Re:Good slides by gpoul · · Score: 1

      Basically true, but there are normally too many people working on a GPLed software product and you'd have to buy a license from too many people. It's just not worth the effort if you have >x contributors.

    38. Re:Good slides by Daniel+Phillips · · Score: 1

      It's the Embrace and Extend model that people keep accusing Microsoft of.

      You appear to have drunk too much koolaid and damaged your brain. GPL embraces what? GPL extends what? Oh, copyright law perhaps. How downright perverse.

      (I can't believe believe I actually responded to your troll.)

      --
      Have you got your LWN subscription yet?
    39. Re:Good slides by Anonymous Coward · · Score: 0

      When MSFT actually pays taxes I'll worry about whether or not they should or should not be able to use code developed under government contract. MSFT wants to freeload off of other people's work and cries when it cannot. As usual.

    40. Re:Good slides by cookd · · Score: 1

      Clean room sucks rocks. Have you ever been involved? Anybody who thinks it is fair to release something GPL because "they can always just do a clean-room implementation of it" has obviously never been involved in a clean-room operation. A real pain in the neck.

      --
      Time flies like an arrow. Fruit flies like a banana.
  12. first 4 slides: Source Licensing & SoftwareInd by ubiquitin · · Score: 4, Informative
    Let's transcribe this thing! Here are the first four slides, from the first two images (two slides per image). I'd love it if somebody transcribed the whole presentation, as there seems to be a lot to think about in there in terms of Redmond strategy.

    Slide 1: Title of the presentation with Microsoft logo

    Slide 2: The Software Ecosystem
    The flow of shared knowledge goes in a circle.
    Diagram shows customers to government to academia to industry and back to customers.

    Slide 3: The Business of Software
    subtitle: Source Code Licensing
    another diagram showing the interactions between source code - Core IP on the left and business model with usage rights and binaries on the right. Arrows showing development, support, deployment, and audit connect the two.

    Slide 4: The Open Source Software Model:

    complex mix of elements

    has produced some great software

    has both benefits and drawbacks like any model
    Diagram showing "development model" surrounded by "philosophy", "business model" and "licensing"

    Finally, somebody please mirror these images, the bandwidth on that site is getting sucked dry.

    --
    http://tinyurl.com/4ny52
  13. The "anonymous reader" who submitted this one... by JessLeah · · Score: 1, Insightful

    ...sounds an AWFUL lot like Richard Stallman... ;)

  14. Re:Jesus Christ.... by Anonymous Coward · · Score: 0

    what is the correct moderation when a 50% Flamebait comment is 100% Insightful?

  15. you don't get it by SweetAndSourJesus · · Score: 5, Funny

    See, Microsoft is a Big Evil Company. Their interest isn't making money, it's robbing people of their freedom. Withness the Internet Explorer debacle. Microsoft knew that I wasn't going to make them a nickel, but they released it for free so that they could take away our right to someone else's browser. Shit howdy, man, they don't care if they lose every nickel they've got so long as they get to keep robbing us of our rights!

    Don't you see, man? They're eeeeevil. So evil that anyone who alleges that they did something evil is automatically right. So evil that when they release good software we must overlook the fact that the software is good and instead focus on how they are bad.

    Microsoft operates the world's largest kitten and puppy grinding facility! Fact!

    --

    --
    the strongest word is still the word "free"
    1. Re:you don't get it by GigsVT · · Score: 1

      Overheard at a recent LUG meeting:

      LUG Member: You will not believe what you are about to see; that MS could have sunk so low that they can take pleasure to do this to another of Gods creatures. I hope you have a strong stomach senor.

      Linus: Roll the ugliness.

      Linus: Good Lord - I've heard about this - cat juggling! Stop! Stop! Stop it! Stop it! Stop it! Good. Could there be a god that would let this happen?

      --
      I've had enough abrasive sigs. Kittens are cute and fuzzy.
    2. Re:you don't get it by grbyrd · · Score: 1

      Dude, we pay for Internet Explorer everytime we buy a computer, a box of MS software, etc. Internet Explorer was allowed to be downloaded for free as part of the war, but propped up the price of Windows '98 and beyond. Note that new versions of Media Player, also free, only work with the latest OS. They receive funding this way...

    3. Re:you don't get it by Anonymous Coward · · Score: 0

      What made you think making money is incompatible with being evil? Since they already have all the money they can expect to make from arguably willing customers, they now need to find ways to extract money from the remaining unwilling customers (or stop expanding, which investors will not stand for). Licensing is getting worse because users' freedom is a threat to vendors like that.

    4. Re:you don't get it by Zeinfeld · · Score: 2
      Microsoft operates the world's largest kitten and puppy grinding facility! Fact!

      Nah you are confusing them with Bill Frist who has admitted taking cats from shelters in Boston and then using them for vivisection.

      I could not see anything in the presentation that told me anything I did not know already. Microsoft has told everyone that they do not like the viral clauses in the GPL.

      The same information is available on the Microsoft Web site. So forget the cloak and dagger stuff folks, the presentation may well have been made outside Microsoft. Looks to me as if the JPGs are simply scans of a leave behind.

      Microsoft is scared of open source the same way the US is frightened of an imminent invasion by Cuba. Cuba may have embarrassed the US in the past and the US may spend a ridiculous amount of time and effort railing aginst Cuba but that does not mean they are frightened of Cuba. All it really means is that the US is understandably concerned when a bunch of crazys are getting drunk on their self inflated rhetoric.

      On the freedom side I find the discussion frankly appauling. The chopped logic sounds very similar to the propaganda the Communists used to put out. Once people claim the right to define freedom for you you can tell that they are really about ramming some ideologically driven bullshit down your throat.

      --
      Looking for an Information Security student project suggestion?
      Try http://dotcrimeManifesto.com/
  16. FP! by Anonymous Coward · · Score: 0

    For a good time call goatse.

  17. Mirror by infolib · · Score: 4, Informative

    here

    Bandwidth sponsored by danish research funding...

    --
    Any sufficiently advanced libertarian utopia is indistinguishable from government.
  18. Indeed, this is why MS has a long history. . . by kfg · · Score: 3, Insightful

    of refusing to give software away for free in order to drive a competitor out of business, and I, for one, applaud them for taking this courageous stance for capitalistic freedoms.

    Shoe? Meet other foot.

    KFG

  19. Whoops! by joeszilagyi · · Score: 1

    Looks like it's been /.'d...

    --
    Dude, where's my packet?
    1. Re:Whoops! by Anonymous Coward · · Score: 0

      It has been slashdoted... but make sure you come back to http://www.foo.be/ and http://www.ael.be/.

      Especially if you are Belgian/European and you care about: Free Software, Freedom, ... and you don't like EUCD (aka European DMCA) and Software Patent.

  20. Looks Real by Crashmarik · · Score: 1

    The slides look real and consistent with prior microsoft positions. (i.e. Their move to prevent gov't funded software from being GPL'D).
    They do as always play the unasked question game very well.
    1. IF closed source development has driven the economoy what's to say open source won't provide a better driver.
    2. Where is the benefit of shared source except in allowing customers to work to benefit the vendor ?

  21. Re:Jesus Christ.... by unapersson · · Score: 3, Insightful

    > This statement is slashdot idiocy at its finest.
    > GPL'd software isn't "free", it comes with strings
    > attached. What's wrong with pointing that out?

    The GPL is one of the few licences that enforces a user's freedom, rather than the developer's. The BSD licence maintains a developers right to take and use code, the GPL keeps maintains a user's right to look inside the code they are using.

    > Microsoft doesn't really need to any help to
    > make OSS advocates look stupid, the overeager
    > religious zealots do that job just fine.

    Microsoft dislikes the GPL so much because it gives freedom to users rather than developers.

  22. My Thoughts by ffatTony · · Score: 3, Interesting

    We all know MS is bad and they are hard at work on Evil Master Plan v1.0, but where I seriously see Linux going in the next few years is gaining ground on other unix vendors. At my workplace we use AIX and Solaris running Apache and a large number of Java Apps. There is no reason we could not use Linux. I am told making the switch is in the project plan for within the next 5 years.

    I am looking forward for linux to become the definitive unix because at that point we can really start inovating and changing the commands we all know and love. For instance, besides for backwards compatability there is really no reason why no two console tools can't support the same set of regular expressions or command line options that are standard (maybe -V is always version and -D is always debug, etc). I'd also love to see something along the line of perl6's attributes for return codes for commands, e.g. after running cvs update it would be cool if it not only returned 0 for success, but if there was some way to tell if it actually updating any files (I know I can do this by parsing its sysout, but I'm trying to make a point that commands could return more complex structures that we could programatically interrograte).

    I love grep, sed, bourne shells, and the gang but it would be very cool if the typical command line experience was a little more cohesive.

    I've used linux and various unixes for about 5 years now and fee pretty comfortable, but maybe this is where we could really shine.

    I realize there are plenty of efforts to modernize shells and command line tools, but I don't forsee them making much ground as if linux was drastically different from what I used at work, it probably we be a plaything at home, rather than a platform for study and to increase my skills.

    It seems clear to me that the command line is superior to gui in terms of speed and efficiency for knowledgable users. What I'd like to see now is a set of tools (and shell) without such a drastic learning curve and also without loosing the power that unix has.

    And yes, I realize that this is probably an impossible dream as OSS was forged in chaos. But who knows, stranger things have happened.

    1. Re:My Thoughts by qwijibrumm · · Score: 4, Funny
      We all know MS is bad and they are hard at work on Evil Master Plan v1.0
      Are you kidding, they've been artificially inflating their product numbers for years. Seriously how much of an improvement was "Evil Master Plan Me(TM)" over "Evil Master Plan 98SE(TM)"? I think they're working on "Evil Master Plan Zt(TM)" right now.

      Man, I remember when computing was easy and they only had "Hey, I Think Being A Little Evil Can Make Us Money 5.2(TM)"

      I guess it just shows, version numbers don't sell. Year numbers don't sell. But cool letters equal cash!

      --
      I wish there was some there was some way that I could be outside playing basketball, in the rain, and not get wet.
    2. Re:My Thoughts by Evil+Adrian · · Score: 0, Troll

      Prove that they have been inflating their product numbers. Stop talking out of your ass.

      --
      evil adrian
    3. Re:My Thoughts by Teach · · Score: 2

      It seems clear to me that the command line is superior to gui in terms of speed and efficiency for knowledgable users. What I'd like to see now is a set of tools (and shell) without such a drastic learning curve and also without loosing the power that unix has.

      There's a delicate balance here. To change command-line switches or return codes potentially affects thousands of shell scripts which depend on the current behavior. To do so also would probably reduce the productivity of the thousands of unix gurus who already have all command-line options for various tools committed to memory. And that's not to be done lightly. To paraphrase the old quote, "Unix is user-friendly. It's just picky about who its friends are."

      Now admittedly, I'd like it if every command-line util in the world supported "--version". But I wouldn't go so far as to standardize on "-v" or "-V" for the same thing, since that's used for various different things for various tools.

      As an example of this, I'm bummed that someone (RedHat apparently) changed the default sorting order for "ls". Used to, things were sorted by ASCII value, which meant dotfiles were first, then files starting with a capital letter (like Makefile or README), and then finally regular, lowercase file names. In recent releases of RedHat, things are now case-insensitively sorted and include dotfiles in with the regular files (e.g. ".zebra" is now listed between "zartan.tar.bz2" and "zephyr.txt"). This annoys me to no end.

      Eventually I was able to determine that adding -v restores the historic sort order (among other things), and so I made it the default. Nothing in the documentation hints that "sort by version" also does an ASCII sort, whereas normal sorting does not.

      Anyway, mastering the unix command-line is a long road, and you continue to gain power for years and years. It does take a while.

      Maybe a solution would be to make an environment variable called USERLEVEL=novice, which makes the switches more standardized but breaks backwards compatibility. Or a command-line switch called --novice which does the same thing.

      --
      Graham "Teach" Mitchell, computer science teacher, Leander HS
    4. Re:My Thoughts by praetorian_x · · Score: 0

      [quote] We all know MS is bad and they are hard at work on Evil Master Plan v1.0 [/quote]

      One would think they were on at least v4.3 by now...

      cheers,
      prat

    5. Re:My Thoughts by Anonymous Coward · · Score: 0

      Let us know when you finish installing Excel 6.0 on Windows NT 2.0.

  23. probably just an RMSbot by SweetAndSourJesus · · Score: 1

    You know, one of those autonomous drones that runs around looking for any sign that Microsoft is evil or websites by some guy who knows someone who once visited the Peruvian embassy saw this guy who said he ran linux.

    --

    --
    the strongest word is still the word "free"
  24. Imposing the GPL is like imposing free speech by argoff · · Score: 5, Insightful

    I'm glad some people finally understand that the battle isn't about markets or choosing a software license, but freedom. All to often people think that free markets are about markets, and not freedom. But just the opposite is true, when a society has healthy freedoms - the markets tend to take care of themselves.

    There is an old saying, a nation can't be half slave and half free - but only all slave or all free. Unfortunately, alot of people don't understand this about copyright controlls. They think that choosing a software license is like going to the store and choosing between pears and apples or between painting your room yellow or pink - that it's just about preference. Well, it is not, and it is so fusterating to see how people refuse to consider the long term consequences of their own belief systems.

    The simple truth is copyright controlls are untenable without massive free speech restrictions like the DMC0A (and beyond), and information is so easy to manuipulate and change form - that it can't be controlled unless all of it is controlled.

    1. Re:Imposing the GPL is like imposing free speech by Squarewav · · Score: 5, Insightful

      the funny thing about free speech is that people are free to chose how they express them selfs, is linux free as in speech, yes but so is microsoft, microsoft chose to keep thier speech closed and thats thier right. In fact I think it would be unconstitutional to force MS to OSS

      sorry about my spell'n

    2. Re:Imposing the GPL is like imposing free speech by SN74S181 · · Score: 1
      There is an old saying, a nation can't be half slave and half free - but only all slave or all free.


      That sounds clever and all, but you omitted the handwaving and 'proclamations' and faulty logic to back it up.

      All of that 'How can any man be said to be free while....' and whatnot. Which really reduces down into rhetoric and mushes up, rather than clearly defines, the meaning of the term 'freedom.'

      The simple truth is copyright controls are untenable without massive free speech restrictions like the DMCA (and beyond), and information is so easy to manuipulate and change form - that it can't be controlled unless all of it is controlled.


      Similarly, your feet can't achieve 'freedom' in a world where there are snowdrifts, hot black asphalt in the midday sun, and sharp glass out back near the dumpster.

      Print it all up on some leaflets. You can feel good about handing them out. And oh so very righteous afterwards sitting at your computer in your dorm room.
    3. Re:Imposing the GPL is like imposing free speech by inode_buddha · · Score: 2

      Somebody please mod up Squarewav's comment! No kidding, I totally agree, and I'll add to it: Not only are MS and Linux free to choose how to express themselves, their customers and users are, too!

      If you want to see some *really* intense debate on the subject, you should check out the last few day's worth of posts on the kernel mailing list. It's freakin' rare when RMS responds to (perceived) trolling.

      --
      C|N>K
    4. Re:Imposing the GPL is like imposing free speech by Anonymous Coward · · Score: 0


      I agree in that if microsoft wanted to make the code and keep it to themselves they completely have a right to do so - but not to send it all over the universe, and then expect anyone who deals with it to be on their dog leash because of copyright controlls. In fact, the things they have done have directly violated the intent of (american) copyright law - to get innovation out into the public domain. If anything, MS is a classic example of why copyrights are such a failure.

    5. Re:Imposing the GPL is like imposing free speech by Anonvmous+Coward · · Score: 2

      "I'm glad some people finally understand that the battle isn't about markets or choosing a software license, but freedom. All to often people think that free markets are about markets, and not freedom. But just the opposite is true, when a society has healthy freedoms - the markets tend to take care of themselves."

      One of the freedoms we have to accept is that MS is allowed to express their views on GPL.

    6. Re:Imposing the GPL is like imposing free speech by Anonymous Coward · · Score: 0


      half slave and half free...

      That argument was taken from the 1840's where many business people in NYC were very comfortable with the idea that half the nation could be free and half could be slave. That is until the southern states started to demand imposition of massive restrictions on the northern states (and industries) in the name of ensuring that they could contain their slave class. The tension eventually led to a breakoff and a civil war.

      So I'm curious - did the million or so people who died in the civil-war just die for the sake of propaganda as you seem to imply?

    7. Re:Imposing the GPL is like imposing free speech by Oink.NET · · Score: 2
      All to often people think that free markets are about markets, and not freedom. But just the opposite is true, when a society has healthy freedoms - the markets tend to take care of themselves.

      So are we to assume that a license that sidesteps the entire not-free-as-in-beer market system is going to help the markets take care of themselves??? There IS no "market" for that kind of product, except in terms of mindshare versus commercial (aka market system) products.

    8. Re:Imposing the GPL is like imposing free speech by sfraggle · · Score: 2

      You seem to have confused the meaning here. "free as in speech" and "free as in beer" are used to distinguish between the two meanings of the word in the English language (other languages like French have words for these concepts which distinguish them - eg. liberty vs. gratis). The point of Free Software is that the users of software, not the developers, have freedoms.

      --
      were you expecting to see a sig here? perhaps you'd rather see the inside of an ambulance!
    9. Re:Imposing the GPL is like imposing free speech by pjrc · · Score: 3, Funny
      the funny thing about free speech is that governments are free to chose how they express them selfs, is America free as in speech, yes but so is China, China chose to keep thier speech tightly controlled and thats thier right. In fact I think it would be a violation of human rights to force China to allow its people to freely express their own opinions of the goverment.

      your spell's is sorry

    10. Re:Imposing the GPL is like imposing free speech by Darth · · Score: 2

      nobody, except possibly market forces, is forcing microsoft to release their source under an open source license.

      What they are doing is saying "I wrote this. I've opened it's source so that others can use it. However, if you want to do so, you have to play by my rules."

      Microsoft is saying "We wrote this. We keep the source closed and if you want to use it, you have to play by our rules."

      This whole "viral" thing is misleading. Nobody just wakes up with gpl code in their project and goes "damn, now i have to gpl it if i want to distribute it." If you dont want to gpl code you intend to distribute, build your own library or look for one under a license like the bsd license. Just dont cry because the mean programmer wont let you use his code.

      Personally, i find it incredibly hypocritical of Microsoft to complain about gpl not letting them use other people's code while they continually obscure file formats and communication protocols specifically to not allow people to interoperate with their code.

      I guess "it's our code. we can do what we want with it" is only an acceptable answer when it's coming from their lawyers.

      --
      Darth --
      Nil Mortifi, Sine Lucre
    11. Re:Imposing the GPL is like imposing free speech by g4dget · · Score: 2
      We aren't talking about "forcing" anybody to do anything: we are talking about whether customers, including the government, should choose to buy Microsoft's products or conduct research on improving them, given Microsoft's current licenses. To me, the answer is a pretty resounding "no".

      Microsoft can choose whatever licenses they like, but nobody should be under any obligation to buy their stuff.

    12. Re:Imposing the GPL is like imposing free speech by jez9999 · · Score: 1

      You seriously sound like Bill Gates and Steve Ballmer at a computer.

      There may be no 'market' for GPLed software, but who are you to complain? Why does ANYONE, least of all Microsoft, have the right to take someone else's source code for free and profit from it?

    13. Re:Imposing the GPL is like imposing free speech by NineNine · · Score: 1

      Why does ANYONE, least of all Microsoft, have the right to take someone else's source code for free and profit from it?


      I dunno. Ask IBM. They may or may not be profiting from Linux.

    14. Re:Imposing the GPL is like imposing free speech by rlk · · Score: 2

      There absolutely is a market for GPL'ed software. Just ask Red Hat, SuSE, Mandrake, et al. They're very much in the business of selling shrink wrap software.

      We can argue back and forth all day about whether they're really selling "service" (saving you the effort of downloading, or sharing, or integrating, or whatnot), but at the end of the day, they are selling a product. Maybe they're not making as much revenue as Microsoft, but that's not the question at hand. There is a market for GPL software, even if it's less lucrative on the seller side.

    15. Re:Imposing the GPL is like imposing free speech by cookd · · Score: 1

      Yes, it is wonderful that in China, the powerful can control the speech of others. And if we were to force the powerful to stop gagging the others, we would have taken away this wonderful gift of gag.

      --
      Time flies like an arrow. Fruit flies like a banana.
    16. Re:Imposing the GPL is like imposing free speech by cookd · · Score: 1

      No, I think you are putting words into MS's mouth. Microsoft isn't complaining about not being able to use GPLed code.

      First, I think some people actually do wake up and say... For example, the NSA with the secure Linux distro. They realized that they couldn't use it the way they wanted due to the GPL. So in effect, they perhaps are proof that some people don't understand the GPL and perhaps need to understand it better before making decisions. This is probably especially true of management. And this is what MS is trying to do. Obviously, they will explain the GPL from their perspective, but in some cases this might be closer to the perspective of the manager in charge.

      Microsoft is saying: "Yes, GPL or use GPL if you like, but there are consequences you may not like."

      Microsoft is saying: "Warning -- if you use GPLed product B, you will have to release the source to your derivative work before distributing it."

      Microsoft is saying: "Government should be aware that if they GPL the result of their research, the commercial companies are going to have a hard time with it."

      Microsoft is not saying: "We want to be able to steal all GPLed code."

      --
      Time flies like an arrow. Fruit flies like a banana.
    17. Re:Imposing the GPL is like imposing free speech by fatboy · · Score: 2

      First, I think some people actually do wake up and say... For example, the NSA with the secure Linux distro. They realized that they couldn't use it the way they wanted due to the GPL. So in effect, they perhaps are proof that some people don't understand the GPL and perhaps need to understand it better before making decisions. This is probably especially true of management. And this is what MS is trying to do. Obviously, they will explain the GPL from their perspective, but in some cases this might be closer to the perspective of the manager in charge.

      The NSA didn't have to release the source to their distro. As far as I know, they never distributed a binary only version of it. To simply USE OR MODIFY GPL software does not require you to provide source. Somehow I think you knew that all ready, but made the false claim that they HAD to release the source anyway.

      --
      --fatboy
    18. Re:Imposing the GPL is like imposing free speech by yuri+benjamin · · Score: 1

      I refer folks to my earlier post The "GPL is viral" Myth

      --
      You make the mistake of thinking you can educate the fundamental stupidity out of people. You can't.
    19. Re:Imposing the GPL is like imposing free speech by cookd · · Score: 1

      Huh? So now you accuse me of lying. To tell you the truth, I don't remember exactly the reasons why the NSA was upset about the GPL, but they WERE. They had some plans for their secure distro, and they realized that those plans were going to be incompatible with the GPL. I'm not making the story up. So you tell me what they were upset about, and if it doesn't apply here, you have won the argument. But I think it does (from what I do remember), and thus my argument stands.

      Right off, I can think of one situation where they might have been upset by the GPL. If they planned on making a secure distro available to the world, and needed to put some proprietary or sensitive code into it to make it meet their needs, they would be blocked by the "aggregate product" clauses of the GPL.

      --
      Time flies like an arrow. Fruit flies like a banana.
    20. Re:Imposing the GPL is like imposing free speech by greenrd · · Score: 2
      No, I think you are putting words into MS's mouth. Microsoft isn't complaining about not being able to use GPLed code.

      Um, yes they are! They actually go further and claim in these slides that government use of GPL for research software means that "the results of the research can never be commercialised". This is simply untrue.

      One, it can be commercialised by reimplementing and adding value. Algorithms are not covered by copyright - they are only covered by patents which has nothing much to do with the GPL. Two, in the unlikely event that a cross-platform GPL utility were to do a little task perfectly with no possibility for improvement, there would be no point in having a non-free competitor. Commercialisation is only useful when it produces something of value. If it does produce something of value, then what's the problem?

      Answer: nothing. MS are being deliberately misleading here.

      Don't forget, this is coming from the same company that once said "The GPL is like a cancer".

    21. Re:Imposing the GPL is like imposing free speech by greenrd · · Score: 2
      One of the freedoms we have to accept is that MS is allowed to express their views on GPL.

      Express their views, yes. But not lie. They should not be allowed to make false claims such as "the GPL prevents commercialisation of research".

      I don't accept that corporations have the "freedom" to lie about the GPL (or anything else). Corporations are not human beings and should not have human rights. In fact a recent decision by the California Supreme Court - where Nike tried to argue that they had a Free Speech right to lie about sweatshops in advertisements, and the court disagreed - affirms this view. This case may now go all the way to the Supreme Court. Which is interesting, because even the Chief Justice of the S.C. - not a rock-throwing anarchist by any means - has expressed the same kind of view in a dissenting opinion in a previous case.

    22. Re:Imposing the GPL is like imposing free speech by Anonymous Coward · · Score: 0

      Recently, the company I work for decided that a project we were working on would be better off proprietary. Our reasons were thus: We did not want our competition to have access to what we had developed and paid for(I agreed, all of us formed a company after we were royally screwed by our now direct competition). I could not insert provisions into the liscensing to prevent this due to the GPL. I had two choices, rewrite the GPLed portions of code to allow relicsensing, or contact the person who wrote the original code and have them agree that I could restrict ownership of the modified code to certain parties. In this case it was a linked application (to the library), a module, and several patches. The person who wrote the code said no, it must be free to all.

      I actually had to recently rewrite an entire library from scratch due to this. Was I tainted by previously working with the GPLed library? Probably, would there be a case against me that I ripped him off? I don't know. I reworked his C code completely, wrote alot of it with the inline assembler. Several things he had implemented in the best way I could have thought of of implementing them. I used the same. Did I rip him off for my proprietary package? No more so than someone who ignores some stupid US patent.

      I'd rather see the viral nature of the GPL go away, and have companies be able to liscense their patches however they want. Core code stays free, patches may or may not cost.

    23. Re:Imposing the GPL is like imposing free speech by fatboy · · Score: 2

      Huh? So now you accuse me of lying. To tell you the truth, I don't remember exactly the reasons why the NSA was upset about the GPL, but they WERE. They had some plans for their secure distro, and they realized that those plans were going to be incompatible with the GPL. I'm not making the story up. So you tell me what they were upset about, and if it doesn't apply here, you have won the argument. But I think it does (from what I do remember), and thus my argument stands.

      Well, since you didn't look it up yourself, I guess I will do it for you.

      To quote the article, "Despite the intense battle surrounding the open source, the NSA will still fund research on secure operating systems based on Linux as well as work with U.S. companies to create better security in their own operating systems."

      Two camps were primarily pissed off about it.

      1) Microsoft, because the NSA was funding their competitor.

      2) Ultra Nationalist who didn't want the benefits of the GPL to go outside the US.

      The project is still alive and being developed.

      I guess I thought you would have done a little research before blindly posting. Sorry, I was wrong to attribute to malice what can be adequately explained by ignorance.

      --
      --fatboy
    24. Re:Imposing the GPL is like imposing free speech by SN74S181 · · Score: 1

      Read any comprehensive history of the Civil War. It was not a war fought to 'free the slaves' though there's a large body of propaganda out there that claims so.

    25. Re:Imposing the GPL is like imposing free speech by gpoul · · Score: 1

      AFAIK this whole debate is NOT about the DMCA or any other copyright enforcement. It is about choosing the right license for the job at hand and not about enforcing that license by using code. - Your comment makes no sense to me, sorry.

    26. Re:Imposing the GPL is like imposing free speech by gpoul · · Score: 1

      MS is not as misleading here as you think.

      Wouldn't you agree that freedom for everyone would be greater if academic software would be released under BSD-like licenses?

    27. Re:Imposing the GPL is like imposing free speech by gpoul · · Score: 1

      Why is it that nobody wants to see the truth in MS's statement but only picks about the chosen words of a non-US presentation published in english?

      Maybe you're just too used to reading licenses and finding exceptions to what someone wrote. Please be a little bit more open and think about what other people wanted to say and you'll find that sometimes they have valid opinions you should think about.

    28. Re:Imposing the GPL is like imposing free speech by Anonymous Coward · · Score: 0

      Everyone? No. A few developers' freedom would be greater, while all their customers' (including most developers!) would be lost.

    29. Re:Imposing the GPL is like imposing free speech by Anonymous Coward · · Score: 0

      You chose to prevent anyone else from being able to work with your code, and so you lost access to someone else's code you wanted to work with. You suffered for going proprietary to control your customers.

      Good. You deserved to.

    30. Re:Imposing the GPL is like imposing free speech by cookd · · Score: 1

      Good point. I meant that Microsoft wasn't complaining that GPL code in general isn't available for them to steal. I meant that Microsoft is concerned that code that should be available to all (government sponsored research) wouldn't be available for them to use and examine. Which is definitely a legitimate concern. If you think otherwise, you need to study the real meaning of GPL and also study previous lawsuits regarding license infringement of source code. A BSD license allows a coder who will potentially use the results of research to examine the actual sample code when trying to figure out the specs (specs are never complete, in case you didn't know). A GPL license forces a clean-room setup where the specs are provided, and then whenever the programmer has a question, he/she can ask (in writing, recorded for all lawyers who ever might get involved) a "tainted" person to find the answer, and the tainted person can then examine the GPL code, answer the question (and never go beyond directly answering the question) and record the answer. What a major pain! It increases development cost by an order of magnitude or more. Sounds like MS has a real beef.

      When people make comments that "Microsoft wants to steal all that GPLed code," the inferred meaning is that Microsoft wishes it could have the code to Linux, GnuCash, and XBill, which is bogus. However, it is somewhat true that Microsoft does want/need access to certain code, and GPLed code is pretty much out of reach, since it is really incompatible with any business model that is centered on selling software (and by the way, Red Hat doesn't count, since selling software is most definitely not the center of their business mode). Since I am still not convinced that selling software is morally wrong, I think Microsoft has a point.

      --
      Time flies like an arrow. Fruit flies like a banana.
    31. Re:Imposing the GPL is like imposing free speech by cookd · · Score: 1

      Ok, now I'm a bit ticked.

      This (the com.com article you linked) in fact is the article I did read, and while you claim that I am completely "ignorant" and/or lying through my teeth, the article clearly states that the NSA had some trouble with the GPL license, did not understand all of the consequences of the license, and "won't be doing anything like this again" (i.e. working on something GPLed). And MS wasn't the only one to complain.

      --
      Time flies like an arrow. Fruit flies like a banana.
  25. Slides? by Mononoke · · Score: 0, Redundant
    Shouldn't this be a Powerpoint presentation?

    --
    NetInfo connection failed for server 127.0.0.1/local
  26. Slide 9+10 (img_0223r.jpg) by Anonymous Coward · · Score: 2, Informative
    Slide 9:
    Source Licensing Debate (continued)
    • Wider use of Linux has brought more focus to source licensing as a topic
      • Clear benefits to open source model such as community action
    • Result is a healthy examination of source licensing practices by commercial vendors
    • Sustainable rate of innovation has been lef out of discussion for too long
      • Software innovation has been a driving factor of growth across all major industries

    Slide 10:
    Areas of Concern
    Box to the left of text contains 4 boxes saying:
    General Public License (GPL)
    Ecosystem Health
    Commercial Software
    Government Policy

    • Authored by the Free Software Foundation
      • For protecting the individual developer
      • Against ownership or commercialization of software
    • Designed to devalue software and to pull, by force, intellectual property into the commons
    • Known in the OSS community as a "viral" license
    • Terms of license are:
      • Any GPL code can be copied and redistributed at no cost, may charge for cost of distribution
      • If GPL code is distributed in object form you must also include source code
      • Inclusion of GPL code in another work may require you to release entire larger work under GPL termes (e.g., provide source code and allow others to modify and distribute)
    • The GPL is fine for the individual to choose, but bad for the industry
    1. Re:Slide 9+10 (img_0223r.jpg) by Anonymous Coward · · Score: 0

      And of coure, that Slide 10 is WRONG.

      GPL

      For protecting the individual developer

      Actually, more for protecting the end-user, I find.

      Against ownership or commercialization of software

      No it's blatantly not. It REQUIRES ownership of software by copyright for the GPL to be enforceable. One can happily commercialise GPL code - witness redhat.

      Designed to devalue software and to pull, by force, intellectual property into the commons

      No, IP rights are retained by the copyright holder, and certain (but not all) IP rights irrevocably sublicensed to users of the GPL software.

      And also, what an odd statement, presented as if a commons is a bad thing - the GPL software commons is free from scarcity constraints, unlike a physical commons, so none of the normal arguments against a commons stand up.

      Known in the OSS community as a "viral" license

      To some in the OSS community, which is the proverbial "herd of cats"

      Terms of license are:

      Any GPL code can be copied and redistributed at no cost, may charge for cost of distribution

      Yup.

      If GPL code is distributed in object form you must also include source code

      Nope, you only have to provide, upon request, source code to the people you distributed the object code to. In this day and age, though, most people just chuck it on the web.


      Inclusion of GPL code in another work may require you to release entire larger work under GPL termes (e.g., provide source code and allow others to modify and distribute)

      Nope. Only if you redistribute your larger work. Even huge in-company projects (where most of the money is in Software) that use oodles of GPL code don't have to release a single bit back, so long as they're not distributed outside.

      The GPL is fine for the individual to choose, but bad for the industry


      Bad for whose industry? The OSS industry - nope. The software consultancy industry - nope. Microsoft - yep, because they can't use GPL code in a proprietary product without getting the holder of the copyright of the GPL code to license the code to them under an alternate license. And Troll and Alladin, among others, even follow that as a business plan.

      I suspect this is a deliberate leak, to ensure wider penetration of the misinformation in slide 10.

    2. Re:Slide 9+10 (img_0223r.jpg) by cookd · · Score: 1

      No, IP rights are retained by the copyright holder, and certain (but not all) IP rights irrevocably sublicensed to users of the GPL software.

      Somehow, I find this argument to be very lawyer-istic.

      Retained, yet irrevocably sublicensed. Cute.

      Irrevocably sublicensed is pretty much "commons," at least as far as the target audience for this slide goes.

      Bad for the industry...

      You need to go back to English class and learn about the ambiguities of the English language, and then learn about how to properly fill them in.

      There are two alternate interpretations here. One, which as you have explained, makes no sense whatsoever. Which means it is obviously not the correct one (if the second interpretation makes any sense). The second interpretation is that it is bad for the industry to choose. That is the point of the whole slide show. It is not normally a problem for an individual to choose GPL (unless he/she wants to try to make a lot of money from the software). It is often a problem when a company chooses GPL, since the results sometimes come back to haunt them later on.

      Anyway, reading the rest of your complaints, they mostly come down to a difference of ideology between you and the author of the slide (and who is to say that there doesn't exist the same difference in ideology between you and the target audience for the slide? in which case, there is nothing wrong with what MS is saying) and your picking at the tiniest possible misalignment between what the slide says and what your perception of the truth is. Remember -- this is a slide show, where the objective is "get a simple reminder or bullet point onto the slide, then explain verbally in more depth." You assume that what is on the slide is exactly what was meant or all that was said. Very bad assumption.

      --
      Time flies like an arrow. Fruit flies like a banana.
  27. GPL protects YOUR freedom? by Anonymous Coward · · Score: 0

    Don't think so... GPL protects the software's freedom. It makes the software free, but takes away your freedom to modify GPL'd software and release it without the source code for your modifications. The BSD license gives the most freedom to software developers, people are free to do whatever they want with BSD-licensed software.

  28. The GPL, it is all about me ... by codepunk · · Score: 5, Interesting

    First off the number of software companies vs other sectors is really small. I work as a porogrammer / sysadmin at a manufacturing plant. Do we really care if it is bad for microsoft when we use GPL software. No we care about reducing overhead thus lowering the cost of manufacturing thus allowing us to take bigger price cuts on our products while maintaining the same level of profit. Linux makes us competitive in our industry and this is why we use it, religion is not the issue but simple economics is. Furthermore do I want to sit at home each night and write some code for MS so that they might be able to sell it back to me and or overcharge my company for it. No thanks I will choose the GPL!

    --


    Got Code?
    1. Re:The GPL, it is all about me ... by istartedi · · Score: 3, Insightful

      First off the number of software companies vs other sectors is really small

      RMS has used this argument to further the idea that the rights of proprietary developers are unimportant. It's essentially "might makes right" or "Proprietary software company rights aren't important because they are a minority". Placed within a larger political context, this argument not only falls apart--it becomes quite dangerous. Just substitute "black people" for "proprietary developers".

      (self interest argument)

      I have no disagreement with this. I've held my nose and used GPL'd software at times for this very reason, but when several roughly equal alternatives exist, I shun the GPL'd one because I disagree with the long term goals of the Free Software movement.

      Furthermore do I want to sit at home each night and write some code for MS so that they might be able to sell it back to me and or overcharge my company for it. No thanks I will choose the GPL!

      The problem with this argument is that it places undue emphasis on the problem of "exploitation by closing the source" (EBCS) which is really not a problem at all. Why is it not a problem? Because the relicensor can't take anything from you--they can only withhold their own work. If I take BSD and repackage it without making any changes except closing the source, this will be seen for what it is: wholesale appropriation of BSD. It won't sell because it's actually less valuable than the original BSD due to not having source.

      However, if I add something to a BSD distro that makes it more useful, then I can close the source and if the change is valuable enough to offset the loss of source, I will be able to sell my distro at a higher cost based on the value I've added. I could have used the OSS development model too, but it was my choice. Competitors are free to emulate my changes too and make their changes proprietary or open. The original developer loses nothing--they still have the base source.

      So, that argument falls apart because there really is no such thing as EBCS unless your were planning to charge fees for the right to license your GPL'd software under a proprietary license. But then, if you are doing that, you are not really a GPL advocate.

      Let us assume for a moment that EBCS is a problem. Is it the only problem? Of course not. There are many other ways to exploit somebody. The classic definition of slavery is being compelled to work without getting paid. The only thing missing with GPL coders is the compulsion, so it's more like voluntary servitude. It makes no difference whether you enjoy the work, or if the work is Open Sourced or not. The fact of the matter is that you do work, and corporations reap the benefit on all those Linux servers. The GPL doesn't protect anybody from that form of exploitation, which (if we assume that proprietary developers are a minority) is a much larger problem than EBCS. For a more succinct version of my rebuttal to your post, see my .sig.

      --
      For all intensive purposes, "whom" is no longer a word. That begs the question, "who cares"?
    2. Re:The GPL, it is all about me ... by jelle · · Score: 2

      "the long term goals of the Free Software movement."

      AFAIK, there is none. It will go where the tide and waves will take it.

      Where do you get it that there is a goal? It may be heading somewhere, but the best anybody can do is guess whereto it is heading.

      RMS may have a goal, but that's his personal goal, or maybe the goal of his FSF. He does not get to decide where the Free Software community is heading to. No single person does. Not on the long term, not on the short term. RMS did start much of it with the GNU license, his GNU projects, and the FSF, but the community is bigger than that now, and he is not controlling it.

      I'm convinced a lot of Free Software coders think similar to me: When I write code in my own time and then share it, then I dont want somebody to take that and improve it, sell it, and then refuse to give back the result to us. That's not why I'm sharing it. I'm not doing it to let some company sell what I/we made. I'll do that for a paycheck or royalties thank you (I think software companies should not be trying to make software similar to the good commodoty stuff that is available in Open Source form. They should focus on specialized software and custom jobs).

      They're welcome to save money by using the code that I shared internally, but when they want to make money selling a modified version, they have to share the source under the same terms I did. When I write something in my own time, I get the copyright, and I get to decide what happens with it. When I share it, I want it to stay shared, even if/after others (people or companies) modify it. That's where the BSD license falls apart for me, somebody can take it, improve it, sell it for a nice profit, and laugh at me for being suckered in doing their grunt work. I want the users to profit from the shared work, not some company in the middle that adds a neat scrollbar and a gui installer. I don't want the end user to be charged for a modified work, I want them and anybody to have and use it. And I want them to be able to improve it, but then I also want to see the improvements shared back. I'll often choose GNU over BSD for that reason. If you don't like it, too bad. Take it or leave it, but I'm not coding for somebody else to grab and run. They can grab, but not run afterwards.

      A company can take GPL code, improve it, and use it internally. They only have to make the source available outside the company if they also make the binary/object code available outside the company.

      Basically GPL allows companies to save or make money by using GPLed works themselves, and to make money helping (consulting) others to use GPLed works, but they are not allowed to make money by hijacking it.

      --
      --- Hindsight is 20/20, but walking backwards is not the answer.
  29. Re:Lamerz by catman · · Score: 0, Redundant

    Microsoft kix azz all u linucks bitchez!!!

    You don't say? I think it looks like MS is getting its ass kicked ... I've at least kicked their software off my computers. Well, except the Win98 I have to keep on the disk for tax reasons, of all things!

  30. Slide 17 (img_0227r.jpg) by Anonymous Coward · · Score: 1, Informative

    Slide 17 (last):

    Microsoft(R) (logo)

    Dirk Tombeur
    Microsoft Belux
    dirktom@microsoft.com

    http://www.microsoft.com/sharedsource

    Starting work on 15+16 now...

  31. The GPL protects the developer ... by codepunk · · Score: 5, Informative

    No the GPL ensures that some slug is not going to compile in my library and try to sell me back my own code. The GPL is my reward in knowing that I not going to be taken advantage of.

    --


    Got Code?
    1. Re:The GPL protects the developer ... by Anonymous Coward · · Score: 0


      Someone could only sell back to you your own code if:

      i) They value-add to the code enough to make it worth buying. In which case, you're paying for THEIR enhancements, not your code.

      or

      ii) You're a moron.

      The GPL doesn't protect anyone. It does stifle innovation and cause reinvention of the wheel.

    2. Re:The GPL protects the developer ... by Anonymous Coward · · Score: 0

      The GPL protects the freedom of the code. A developer picking up GPL'd code is chained to that license. (by choice, of course, they don't have to use that code)

      BSD-style licenses protect the freedom of the developer. You can do more or less whatever you want with YOUR work, even if it is based off of someone else's.

      the GPL ensures that some slug is not going to compile in my library and try to sell me back my own code.

      See, you wouldn't be buying your own code. That would be stupid, you already have it. You'd be buying their application, which made use of your code.

      Would they be taking advantage of you? Sure, but that's only a problem if it's not what you intended. It's a personal preference I guess.

  32. GPL hurts open source by Anonymous Coward · · Score: 0
    First of all, as it is expected from Slashdot, this news is also biased and wrong. Microsoft is not against open source, or free software at all. They could be against it, but they are also against software which is cheaper than their software. There is nothing so special about open source for Microsoft except GPL.


    Linux community and many open source projects simply use GPL without much thinking, but that prevents people from writing commercial software and using that existing code in their code.


    The author makes up again, as we all know. GPL prevents people from writing commercial software. I think GPL is one of the primary reasons why open source will not be as successfull as it was expected to be. Nobody seems to think about it, but as a software developer, why should I write a commercial software for Linux, rather than Windows. A software developer spends days and nights to build a nice software, but he/she can not release it for Linux, because many projects are GPLed, so he/she can not incorporate that code into his/her own and also some so called open source advocates oppose commercial software. Overall it is better to work for Windows platform. After all of these issues, some people will still accuse Microsoft of using tactics to hurt open source, but the fact is that it is these people who hurt open source.

    1. Re:GPL hurts open source by rking · · Score: 2, Insightful

      Linux community and many open source projects simply use GPL without much thinking, but that prevents people from writing commercial software and using that existing code in their code.

      Microsoft's licences also mostly prevent people from writing commercial software (or any other software) and using Microsoft's existing code in their code. Believe it or not, Word isn't released as public domain.

      GPL gives you a lot more freedoms than Microsoft's licensing does. If you feel it's still not enough then I have sympathy with that, but suggesting that Microsoft have a point about the GPL license being restrictive is absurd.

    2. Re:GPL hurts open source by Anonymous Coward · · Score: 0

      ... and yet more lies from the mouths of slashdotters.

      Deliberate FUD or ignorance? Hard to say.

      You can do a lot with Microsoft's code if you buy their tools. The various OLE/ActiveX/COM controls etc. allow you to do an awful lot of stuff, such as create word-format documents, have a full HTML render engine etc.

      All within Microsoft's own licensing.

      All of which is writing commecial software using Microsoft's own code in your code.

      There's an awful lot of commercial software out there doing just this, and even more custom code that is "in house" only.

  33. Continuing Returns on Public Investments by grendelkhan · · Score: 3, Interesting

    To me, the citizen, GLP'd research/programs/code/technology/whatever ensures that imrpovements in the whatever are kept in the public domain, which benefits those of us that made the investment in the whatever in the first place. As a developer, if I'm going to be contributing to an open source project, I'd rather have it be a GPL or LGPL'd one to make sure that my contributions stay with the project and aren't taken into something that I don't approve of. Now if it's something that I'm writing for myself, I'd rather have the option of dual liscencing the project to allow me to choose the best usage for my project at that time, while still keeping it available for others to see and use, as I allow.

    Different schemes for different purposes, but if it's public financing that helps create something, then the public should have continuing access to that something inperpituity.

    --
    Wu-Tang Name: Half-Cut Skeleton Get your own Wu-Na
    1. Re:Continuing Returns on Public Investments by Anonymous Coward · · Score: 0

      The impression I got from the slides (assuming they are real) is that Microsoft sees this as an "all or nothing" proposition. The only people who should use the GPL are groups of individuals outside of their place of employment, perhaps to do research or enhance the now-classic "foundational bricks of Computer Science" concept. Even Universities should stick to a BSD license so that their work can be commercially exploited, according to the presentation.

      The GPL need not be the only form of software license, and isn't necessarily as restrictive as they believe. Microsoft hasn't accepted the new paradigm (sorry about that) which makes operating systems and applications a general commodity. Instead they suggest that all software innovation will be destroyed (not just their business model), and advocate super-strong protection of Intellectual Property. Personally I don't see how IP protection can get much stronger than it is right now, so plan on seeing a significantly reduced Microsoft by the time you're very old.

    2. Re:Continuing Returns on Public Investments by TheOnlyCoolTim · · Score: 3, Interesting

      "GLP'd research/programs/code/technology/whatever ensures that imrpovements in the whatever are kept in the public domain"

      No, it ensures that GPLed research remains under the GPL.

      The GPL is not public domain.

      Public domain is the real "free software."

      Tim

      --
      Omnia vestra castrorum habetur nobis.
  34. Heh by Anonymous Coward · · Score: 0

    I like the bit about "Open Standards Have Become A Point Of Confusion" ... Isn't that the point of open standards? I mean, you could always cruise around for a while and figure out an open standard is, but for closed standards, I suppose you'd have to just trust what the company that created/supports it says instead of learning about it yourself.

    Yeah yeah, I guess J. Random Consumer isn't gonna want to search Google to find out what the hell IMAP is and how it works, but I rather like that the information, any information is out there somehwere in a clear form for me to read.

  35. Viral license?? by Selanit · · Score: 5, Insightful

    In the sixth slide, it says that the GPL is 'Known in the OSS community as a "viral" license.'

    Totally regardless of whether or not the GPL is viral, isn't this the description that Microsoft came up with?

    I'm confused. Who first described the GPL as viral? MS? RMS? Somebody else?

    1. Re:Viral license?? by SuperDuG · · Score: 2
      I tried taking antibiotics ... but RMS still kept posting bullshit and running FSF ... so obviously since anti-biotics don't work ... it's a virus.

      And I told MS it was viral ... I never knew they'd put it in a leaked presentation.

      --
      Ignore the "p2p is theft" trolls, they're just uninformed
    2. Re:Viral license?? by MisterFancypants · · Score: 3, Interesting
      Who cares who first described the GPL as "viral"? The fact of the matter is it IS viral, and was designed to be viral, regardless of whether or not you think that is a good thing.

      If you use GPL code, your code must also be GPL. That *is* a set up for viral propogation. And that is the way it was intended to work.

    3. Re:Viral license?? by Gerry+Gleason · · Score: 4, Informative

      No, the term viral dates from the earliest GPL debates, long before MS even knew it existed.

    4. Re:Viral license?? by Anonymous Coward · · Score: 0

      So what, all proprietary licenses are also viral, because each copy is under the same terms as the original, and you're not allowed to change the license at any point.

      Try this: take a copy of Office, change the license to the BSD license, and put it up on your web server. See if Microsoft says, aww shucks, he changed the license, we can't arrest him.

    5. Re:Viral license?? by Metrol · · Score: 4, Interesting

      Who cares who first described the GPL as "viral"? The fact of the matter is it IS viral, and was designed to be viral, regardless of whether or not you think that is a good thing.

      I know what you're trying to say, but the metaphor is lacking in a number of key points. First off, the very word "viral" brings to mind illness, disease, and a variety of other unpleasentries. This is why MS decided to describe the GPL in this way. Welcome to marketing 101.

      A virus is some foriegn invader to a system that lives off the host, and thus weakening it. Rarely is a virus invited in, as it's method for propogating is to be hidden in some other form unrecognized by the host.

      Software that exists under the GPL does not hide what it is. It can't find its way into proprietary code unless it is specifically invited into it. It is its own host, not requiring another for its survival. Certainly the code is trapped within the license once placed there, but so is proprietary licensed code. The primary difference is that one is trapped in the public domain, the other in the corporate.

      I don't have a better metaphor to contradict the whole "viral" thing. I do know that the GPL does not in any way exhibit what we would think of as viral though. Just like with proprietary software, if you want to utilize it within your own code there is a cost attached. To use Microsoft software, you'd pay a licensing fee. With the GPL you pay with providing your efforts back to the community you got it from.

      The only purpose behind calling the GPL a "viral license" is to attempt to put a negative spin on it. The term is but one salvo from the MS marketing arsenal designed to attack that which makes us strong. Allowing the term to stick to any OSS license would be suicidal from a public relations standpoint.

      --
      The line must be drawn here. This far. No further.
    6. Re:Viral license?? by Anonymous Coward · · Score: 0

      It probably wasn't the first use, but Microsoft called that in Halloween documents.

      (Then again, the GPL only effects you if you want to be affected, which isn't exactly "viral". To quote, "Software linked with GPLed libraries only inherits the GPL if it forms a single work, not any software with which they are merely distributed." The V-word is just more FUD -- it's less infectuous than, say, a click-wrap license.)

    7. Re:Viral license?? by andrewski · · Score: 2, Informative

      Really? References here, please. I am assuming you are referencing the debates between Stallman and Gilmore (maybe even before this). I would be ever so grateful if you would point me in the direction of some of the debates.

    8. Re:Viral license?? by Anonymous Coward · · Score: 0

      No, if you distribute your code, and your code uses GPL code, then your code must be GPL-licensed to whoever you distributed your code to.

      That's very different - since it allows, for example, in-house use and arbitrary modification of GPL code, without release of that code. Of course, many do release, since it's annoying maintaining your own fork of a codebase. That's why the GPL is often presented as an "increased fork resistance" OSS license.

    9. Re:Viral license?? by Dixie_Flatline · · Score: 2

      While I see where you're coming from, common vernacular has made the word 'viral' mean more than simply being 'from a virus'. Have you ever heard of a 'viral meme'? It's a meme that spreads quickly through a population. It IS infectious, but that's the point. However, there're no ill side effects from having carried and spread a meme around.

      Viral in this instance is meant only to mean contagious and infectious, but without the negative side effects, as odd as that may seem. That something that we want linux and the GPL to be.

    10. Re:Viral license?? by Malcontent · · Score: 2

      All I know is that the guy who got moderated so high yesterday for asking people not to attack MS should take his words back.

      As long as MS is on the attack against open source and GPL it's OK for people to fight back.

      --

      War is necrophilia.

    11. Re:Viral license?? by Metrol · · Score: 2

      Viral in this instance is meant only to mean contagious and infectious, but without the negative side effects, as odd as that may seem. That something that we want linux and the GPL to be.

      I still take issue with this notion. GPL software is not contagious nor is it infectious. Both terms refer to something that is parasitic in nature to a larger host.

      A program released under the GPL is the host. It's the armor that prevents parasitic proprietary code from tearing bits and pieces from it to profit the few by the efforts of the many. More correctly, it could better be described as anti-viral. It's basic nature cannot be altered by infectious influences. Something that protects the host from viral infection is closer to an antibiotic than any virus.

      The point that should be stressed by any and all OSS advocates is that GPL is the cure, where proprietary lock in is the disease that has infected our industry for so long that we've numbed ourselves to the pain.

      Oh boy, diving deep into metaphor land here. I do believe the distinction of wording is critically important, as these words create a visualisation of what a thing is. Like a writer describing a setting, the combination of words and metaphors create a mental picture of a thing or place unseen. We really do not wish to propogate the notion that the GPL is viral. Regardless of who first attributed the metaphor, the image created is far too harmful to the on going public debate.

      Now is not the time to toss a slow pitch across Microsoft's plate.

      --
      The line must be drawn here. This far. No further.
    12. Re:Viral license?? by Ian+Jefferies · · Score: 1
      Have you ever heard of a 'viral meme'? It's a meme that spreads quickly through a population. It IS infectious, but that's the point. However, there're no ill side effects from having carried and spread a meme around.

      Unfortunately much of human history has been about the persecution between memes: restricting propagation, or the conflicts that arise when competing meme populations of a similar size meet and attempt to resolve their differences. Equally, the cooperation between carriers of compatible memes can lead to results that appear to be greater than the sum of the parts.

      For an example that isn't contemporary: think about why the Christians were thrown to the lions in the pre-Christian Roman empire. That particular meme actually won out but, until it did, one possible side effect of spreading the Christian meme was loss of the meme carrier.
      --
      A physicist is an atom's way of thinking about atoms
    13. Re:Viral license?? by cookd · · Score: 1

      Viral != you can't change.
      Viral == spreads.

      Office's license can't spread, since you can't distribute a derivative work from office. GPL allows that, but says that the derivative work must be GPL. Thus, the GPL spreads...

      --
      Time flies like an arrow. Fruit flies like a banana.
    14. Re:Viral license?? by MisterFancypants · · Score: 2
      First off, the very word "viral" brings to mind illness, disease, and a variety of other unpleasentries. This is why MS decided to describe the GPL in this way. Welcome to marketing 101.

      Not always. Marketing people often talk of VIRAL MARKETING (eg. 'word of mouth'), without the 'viral' part meant to indicate a negative. They are simply trying to convey that the message spreads from person to person like a virus.

      I don't have a better metaphor to contradict the whole "viral" thing. I do know that the GPL does not in any way exhibit what we would think of as viral though. Just like with proprietary software, if you want to utilize it within your own code there is a cost attached. To use Microsoft software, you'd pay a licensing fee. With the GPL you pay with providing your efforts back to the community you got it from.

      If you release code based on GPL code, the new code must be GPL. The GPL is replicating itself like a virus, pure and simple. It is viral. You can try to spin it some other way, but I'll keep calling it viral because that's what it is.

    15. Re:Viral license?? by CoughDropAddict · · Score: 2

      If you use GPL code, your code must also be GPL.

      No, your code must be made available under the terms of the GPL. It can also be made available under any other license you choose, including BSD, proprietary, etc.

      Big difference.

    16. Re:Viral license?? by Anonymous Coward · · Score: 0

      Google groups is your friend.

      Here's a iteration of this boring incestous debate from 1993. Yawn!

    17. Re:Viral license?? by Arandir · · Score: 2

      Huh? If I make my GPL derived code available under both the GPL and the MIT license, then I have removed the condition that the GPL must be available to any code derived from mine, because the conditions in the MIT license could be used instead. And that certainly is not the case.

      --
      A Government Is a Body of People, Usually Notably Ungoverned
    18. Re:Viral license?? by Gerry+Gleason · · Score: 2
      Sorry, I don't really have references, its just that I remember all the same debates that we see today. There has always been a lot of resistance to the "viral" aspects of the licenses. This started right from the mid '80s when GPL was first used.

      I'm pretty sure the term was started by opponents to the GPL philosophy, but since then some proponents embrace it as well. It is an intended effect of the license, and I think overall it is positive. I'm not particularly in favor of the strong stand against using LGPL more widely, but that's another debate.

    19. Re:Viral license?? by Tony-A · · Score: 2

      Viral? Yep, in the sense of almost alive and uses its hosts to regenerate itself.
      So is a smile.
      So is yawning at a party.

      Seems like a GPL'd program improves its chances of survival dramatically. As long as someone, anyone, is interested enough it will survive. The question is how long it will take for big business to understand the nature of the beast. I suspect that some higher-ups at IBM already do. Interesting times.

    20. Re:Viral license?? by yuri+benjamin · · Score: 1

      Once again I refer people to The "GPL is Viral" Myth

      --
      You make the mistake of thinking you can educate the fundamental stupidity out of people. You can't.
    21. Re:Viral license?? by Metrol · · Score: 2

      Marketing people often talk of VIRAL MARKETING

      They may just. What they don't do is refer to the product they are trying to sell as being "viral" in nature.

      The GPL is replicating itself like a virus, pure and simple.

      Pure and simply it isn't. Replication is a means by which individual cels manage to grow by simply duplicating themselves.

      Eegads, more metaphors a coming here. Kids, don't try this at home.

      Development of GPL software is more akin to reproduction where multiple hosts come together to create an offspring. The new offspring is not simply a duplicate of the original, but a new living host.

      Aside from the metaphor tossing, the following is the webster definition of a virus. Is this something that you'd want to use to describe a product that you wish to advocate?

      Virus \Vi"rus\, n. [L., a slimy liquid, a poisonous liquid, poison, stench; akin to Gr. ? poison, Skr. visha. Cf. Wizen, v. i.]
      1. (Med.)
      2. Contagious or poisonous matter, as of specific ulcers, the bite of snakes, etc.; -- applied to organic poisons.
      3. The special contagion, inappreciable to the senses and acting in exceedingly minute quantities, by which a disease is introduced into the organism and maintained there.
      Note: The specific virus of diseases is now regarded as a microscopic living vegetable organism which multiplies within the body, and, either by its own action or by the associated development of a chemical poison, causes the phenomena of the special disease. Fig.: Any morbid corrupting quality in intellectual or moral conditions; something that poisons the mind or the soul; as, the virus of obscene books.
      --
      The line must be drawn here. This far. No further.
    22. Re:Viral license?? by Anonymous Coward · · Score: 0

      Easy to find out with only a couple of minutes of research. Here's a really old USENET message describing the GPL as viral (cut, paste, eliminate blanks, etc.). Also try a search for GPV (GP Virus). Google is your friend...

      http://groups.google.com/groups?hl=en&lr=&ie=UTF -8 &oe=UTF-8&threadm=GUMBY.93Apr20075031%40tweedledum b.cygnus.com&rnum=1&prev=/groups%3Fq%3DGPL%2Bviral %26hl%3Den%26lr%3D%26ie%3DUTF-8%26oe%3DUTF-8%26as_ drrb%3Db%26as_mind%3D12%26as_minm%3D5%26as_miny%3D 1981%26as_maxd%3D4%26as_maxm%3D1%26as_maxy%3D1995% 26selm%3DGUMBY.93Apr20075031%2540tweedledumb.cygnu s.com%26rnum%3D1

    23. Re:Viral license?? by Anonymous Coward · · Score: 0


      Except it's not a myth. The GPL *IS* a viral license. It was designed that way.

      A license only matters if you're distributing the code. If code remains in-house, it doesn't matter what license is used.

      Nice attempt at FUD there, btw.

    24. Re:Viral license?? by Anonymous Coward · · Score: 0


      Viral refers to the way the GPL "taints" any code used with existing GPL code.

      In this sense, it IS viral.

      You can scream and kick all you like because you don't like others describing your pet license for what it is, but it doesn't change the facts any.

    25. Re:Viral license?? by Anonymous Coward · · Score: 0


      IBM et al don't give a fig for a program's "survival".

      They care about being able to make money from it.

      The little that IBM does give away is primarily either to help sell other software or for PR reasons.

      Given the amount that a lot of software costs to write, however, I'm of the opinion that it's perfectly reasonable to charge for software. And despite what I've heard repeatedly in the past, the GPL does pretty much kill that method of business.

    26. Re:Viral license?? by Anonymous Coward · · Score: 0


      Take issue all you want.

      The GPL is most definitely viral. It does infect other code that is distrubuted with it.

      BTW, why should any point of yours be stressed by OSS advocates? I'm an OSS advocate. I'm certainly not a GPL advocate. The two are not synonymous.

      The GPL is a license that stifles innovation by anyone who wishes to make money from code directly. It is most harmful to the smaller code shops since it damages their ability to compete. The big shops - say, Microsoft, to pick your enemy - can afford to rewrite code from scratch.

      So, in a sense, such a license helps Microsoft. It keeps away all but the biggest players.

      In fact, I think thus far it's probably helped Microsoft far more than it's hindered them.

      Read Steven Levy's Hackers sometime for the truth behind the GPL. It's doing exactly what it was designed to do.

      And that's not protect your freedom.

  36. Another Mirror. by AltGrendel · · Score: 2
    --
    The simple truth is that interstellar distances will not fit into the human imagination

    - Douglas Adams

  37. GPL kills MS's freedom by Rassleholic · · Score: 0

    Freedom to buy out
    Freedom to monopolize
    Freedom to restrict
    Freedom to blackmail
    Freedom to extort
    Freedom to bribe

    --
    Not noteable, IMO a rubbish article.
    1. Re:GPL kills MS's freedom by Lobo93 · · Score: 1

      And might I add:
      Freedom to induce hairloss among IT-consultants in their 20's.

      Spammers to the rescue!

      --
      "The only clear view is from atop the mountain of our dead selves." - Peter Carroll
  38. What make you think by codepunk · · Score: 2

    What makes you think that I want you to have my code in your closed source project. I could give a rats ass if you like my choice in licensing. It is my code not yours, if I want to use the GPL then by god I will use the GPL.

    --


    Got Code?
    1. Re:What make you think by Anonymous Coward · · Score: 0

      I completely understand that and respect that. Just remember not to cry when Microsoft is the dominant player in the OS market.

  39. Slide 15+16 (img_0226r.jpg) by Anonymous Coward · · Score: 1, Informative
    Slide 15:

    Box to the left of text contains 4 boxes saying:
    General Public License (GPL)
    Ecosystem Health
    Commercial Software
    Government Policy


    Areas of Concern
    • Government policy around source code licensing will have long-term implications
      • Procurement
      • Mandatory preferences for either Open Source or GPL software removes the value of quality

    R&D

    • Government funded research released under the GPL can never be commercialized
    • True public-domain licensing would look more like the FreeBSD license

    Software Industry Growth

    • Strong IP protections provides significant incentive for local software companies to invest in R&D
    • Procurement preferences against commercial software companies will harm local industry
    • Non-commercial software will have artificial advantage over commercial if government funded R&D is covered by the GPL


    Slide 16:

    Choice of Models -
    Choice of Software


    • Individuals and organizations should choose:
      • Development model that works best for them
      • Licensing model that works best for them
      • Software that delivers the most value
    • Governments should:
      • Advocate that the broadest range of choices be available
      • Provide strong IP protection to allow individuals and organizations to benefit from their investments

    That's it from me for now. Somebody else must do the rest.
  40. Re:My Thoughts (or ramblings) by cant_get_a_good_nick · · Score: 2

    At my workplace we ... run[ning] . . . a large number of Java Apps. There is no reason we could not use Linux.
    My understanding is that the Linux threading model (pthreads actually map to processes that share memory space instead of "true" kernel threads) doesn't really work well with Java, since it's easy to generate Java threads, they map to processes, and you swamp the computer. The next Linux (2.6 or 3.0 whatever it's called) I believe has better threads, something more like kernel threads. Please someone corect me if I'm wrong, I'm interested in this too.

    but it would be very cool if the typical command line experience was a little more cohesive.
    I love the command line too, but there are limitations. The data is constrained to be a stream. All data has to be marshalled and unmarshalled to the constraints of the the streams. The only "metadata" organization you can have is whitespace and maybe some headers. These are constrained to be in the same stream and need to be extracted from the normal data. Pretty much the entire reason for awk is parsing the output of commands and rearrange them to be the proper input for other commands. Having all these commands constrained to streams makes for a lot of interoperability but you lose a lot of context. The simplicity of a stream is somewhat countered by the occasional need to use another tool (like awk) within a pipe. I wonder what an XML-aware toolchain would look like. Would having the extra context of XML input/output improve certain tasks (after the learning curve) or would the complexity be too heavy for even power users to use on any consistent basis? Might be an interesting research project for some school.

    The other major limitation of the pipe heavy shell is that the pipe has no knowledge or control of internal program state. You can control initial program state (inputs, command line args) but thats it, everything else is pretty much controlled by the program's internal state machine, and not by you. Again awk helps a little - a pipe friendly program that allows programming looping and conditional constructs, but you're stil limited. AppleEvents are very interesting. They allow you to pass data, structured data, from program to program, and allow the script to interact with the programs internal state while it's running. I'm sure VBA is something like this as well, but I have no experience with it.

    I'm not sure if Linux can ever have this. Too many disparate developers. No one to really "bless" a single scripting language, so there are multiple. Linus has repeatedly said he doesn't really care about the userland, so it won't be from him, maybe RedHat will bless something. But that still doesn't mean developers will use it. Both Apple and MS have certification programs. To get an Apple/MS logo, you have to submit it, and follow some APIs, including AppleEvent or VBA compatibility. Linux doens't have that, won't have it any time soon, and probably never will.

  41. guy with camera at MS remains unquestioned by jdkane · · Score: 3, Interesting
    Yah, that guy who got took those picture was just sitting at the Microsoft meeting and taking pictures of the all presentation transparencies on the wall (presumably because he couldn't acquire the electronic version, or he didn't have a hard copy to scan) and of course nobody questioned him. And he couldn't get an electronic or hard copy so he just sat there and took pictures during the meeting because the most evident action is sometimes the least noticed and questioned. Obviously he got away with it. Oh, just wait a minute ... maybe he was the only guy in the room because he snuck in before or after the meeting because it was ... um ... how about ... a conspiracy theory by Linux enthusiasts -- no, the information isn't good enough for that sort of thing. And maybe the pictures are real!, in which case, well, everybody still can be sure of what they already knew before. Or, maybe somebody just happened across these transparencies that were just lying around (which shows how important they were by the security measures), and the guy could have got in trouble (risked a jail term) to get this information that we already knew.

    And so this article *really* lends credence to the anti-OSS memo. ;)
    Aren't some of these articles and whole lot of fun?

    1. Re:guy with camera at MS remains unquestioned by infolib · · Score: 2

      This looks very much like an MS presentation to a government comittee.

      From the quality of the shots I think it is plausible that they were taken by a concealed camera. If this was a gov't hearing, it's not impossible that other groups were present, perhaps open source advocates.

      The culprit? We may never know...

      --
      Any sufficiently advanced libertarian utopia is indistinguishable from government.
    2. Re:guy with camera at MS remains unquestioned by Anonymous Coward · · Score: 1, Informative

      It was a public meeting...

      http://carolo.net/pipermail/os3b/2002-November/0 00 884.html

      in Belgium & Luxembourg.

    3. Re:guy with camera at MS remains unquestioned by andrewski · · Score: 1

      What, like straddling the border, with one side of the table in Luxembourg and the other half in Belgium?

    4. Re:guy with camera at MS remains unquestioned by Anonymous Coward · · Score: 0

      Yes, exactly like that. That's the way Microsoft organized its Belgium/Luxembourgh operations. That's why it's called "Microsoft Belux". Physically, the meeting was at Systemat, SA, as the message explained. Really, get a grip on European geography.

    5. Re:guy with camera at MS remains unquestioned by vmxeo · · Score: 2, Insightful

      Look very carefully at the pictures. They're not pictures of overhead transparencies, they're pictures of a paper copy (that kind that Powerpoint nicely prints out for you). You can even see some of the text on the next page showing through (for instance, in image 0221 you can see the faint outline of 0222r) . The perpective is not straight on, but rather at an angle. Also, the paper color is slightly green, suggesting he shot it under florescent light.

      My guess is this was the handout at a meeting were the attendee didn't think he was going to get to keep his copy. He covertly pulls out his his camera and shots the handout right on the table in front of him.

    6. Re:guy with camera at MS remains unquestioned by andrewski · · Score: 1

      It was a joke. I know all about where your little countries are at. My point is that you can't have a meeting in Belgium and Luxembourg without somehow being in both countries at once - i.e. at a table with one half in Belgium and one half in Luxembourg.

      I think it's called Microsoft Benelux by the way.

  42. He's right. by Hayzeus · · Score: 1
    I must conclude that this AC is a troll. Dang.

    Why would you conclude this post is a troll? The OP ends with "Go Public Domain!". He's knocking the GPL, not free licensing in general. And he's right -- the GPL is restrictive compared with other licenses (LGPL, BSD, PD) since it places requirements on the derivative work product. Not a big deal for applications, but when applied to a library, the GPL would appear to preclude closed-source application development (or maybe not -- see yesterdays /. article). Whatever you think of CS development, this is a significant restriction which (for CS developers) can be a more onerous restriction than a commercial license (depending on the terms).

    1. Re:He's right. by kien · · Score: 1

      If I understand Free As In Freedom correctly, the GPL exists because the FSF doesn't believe in CS development in the first place. The idea that software can be free and still earn profits for its developers is a hard one to swallow for some, but that is the environment that the GPL was designed for.

      Agree or disagree with the concept of free software, but the fact remains that the GPL was written to promote a world where closed-source software doesn't exist.

      Maybe Linus is right. Maybe CS and OS software can coexist peacefully. Maybe RMS is right. Maybe all software should be free and open-source and there is no middle ground. All of the fretting about the GPL by CS developers makes me wonder which side of the debate is more hardheaded.

      (Not disagreeing with you, Hayzeus; just trying to shed some light on the debate itself.)

      --K.

      --
      Sig: Bad people happen. Try to avoid being one of them.
  43. So? by Anonymous Coward · · Score: 0

    Even if this authentic, so what?

    Microsoft isn't allowed to be opposed to a particular software license?

    I see people on here every damn day saying that they don't like Sun's license for Java, Apple's APSL, BSD, etc. but Microsoft doesn't like the GPL, they are evil.

    I suggest you people take a look in the mirror, and see if you can spot the hypocrite.

  44. Is this a sign? by core+plexus · · Score: 2

    I've been wondering why, and how, ms keeps slipping up and these "unintended discharges", i.e. "Halloween" memos, now this (if it is authentic), etc. Is it a clever marketing ploy? Or is it a sign of rot from within? If or when the so-called mainstream press starts to pick up on these stories, ms will be even more worried, and I predict even more unintended releases.

  45. No! by dubbayu_d_40 · · Score: 1

    It's free markets... not free software. Communism is so passee.

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

      It wasn't a free market once vendors were allowed to use undocumented formats, trade secrets, reverse-engineering prohibitions, patents, and copyrights to prevent meaningful competition from existing. A market is only as free as its customers, who are currently tightly controlled by the maintainers of their proprietary software.

  46. Re:Lamerz by Anonymous Coward · · Score: 0

    Look at the scoreboard, dumbass. 95% versus 5%.

  47. A tad blurry by xihr · · Score: 1

    Would have been nice if the crucial parts of the slides where attempts to rationalize why GPL is bad weren't too blurry to read.

    1. Re:A tad blurry by Metrol · · Score: 2

      ...why GPL is bad weren't too blurry to read.

      That's okay, the logic was just as blurry.

      --
      The line must be drawn here. This far. No further.
  48. Like the Microsoft Switch-Campaign by Devil's+BSD · · Score: 1

    To all those who say that we won't know that someone from microsoft actually made this, I agree. The only way Microsoft will claim that this is theirs is by saying that it was the work of a "rogue employee" or something similar, please note the much-celebrated-on-slashdot Microsoft switch campaign.

    --
    I'm the Devil the Windows users warned you about.
  49. Slides my ass!!! by tyrnight · · Score: 1

    Micro$oft doesnt use Transparencies.. they use DLP projectors. who ever believes this crap ... well uh... Gulable

    but think.. M$ has to much money to send out their team with transparencies..

    --
    Freaky Schitt always happens to me... WHY God WHY!!
  50. If you want to flame the guy who wrote this by Tuxinatorium · · Score: 2

    It's dirktorn@microsoft.com

  51. incensed! by Anonymous Coward · · Score: 0

    What the hell??? Do you work for Microsoft!? It is well known what Microsoft has done in the past. Why NOT believe this time? Even if it's BS, this seems like something MS would do in a second and it's better to be safe than sorry. Based on their past how can anyone now be paranoid and suspect of those pigs at every turn?

  52. The "Go Public Domain!" bit by voodoo1man · · Score: 1

    Obviously identifies him as a troll. Many institutions (and even the FSF) had problems being burned with software being placed in public domain - that's why the current free software licenses require you to copyright your work. The most famous example of this abuse is probably Gosling Emacs. James Gosling originally distributed the source code as public domain, and GNU Emacs used some of that source code. Then Gosling decided to sell the program and source to Unipress, which took objection to this and so all the Gosling Emacs source had to be purged from GNU Emacs. Supposedly, several universities were prevented from distributing their public-domain software after some companies started selling commercial derivatives, although I haven't personally heard of a specific case.

    --

    In the great CONS chain of life, you can either be the CAR or be in the CDR.

    1. Re:The "Go Public Domain!" bit by Hayzeus · · Score: 2
      What? Once something is placed in the public domain (via a notice that the works are "hereby placed in the Public Domain" or similar), my understanding was that it was in the public domain for good -- the PD status can't just be revoked arbitrarily. (I believe this is the way it works in the publishing world, anyway).

      However, I'm not a lawyer (obviously) -- it would be nice to hear from someone a little more versed in this kind of thing...

    2. Re:The "Go Public Domain!" bit by dacarr · · Score: 2

      Public domain is more or less equivalent of abandonware with source.

      --
      This sig no verb.
    3. Re:The "Go Public Domain!" bit by Anonymous Coward · · Score: 0

      I'd say no. Abandonware is a made up term by people who think old games that aren't supported or sold should be able to be distributed for free.

      I kind of agree with them - ever since one of my disks went bad and I couldn't play one of my favorite games because the company no longer exists.

      (Damn them, I put together a 486 box for nothing.)

      IANAL, so I can't say if 'abandonware' distribution is legal or not.

      What I can tell you is that public domain most certainly is not abandonware. Public domain means you can grab software and/or source, and do with it as you please.

      That is, if I grab a public domain work, and use it to make millions, good for me. I don't have to give credit, I don't have to publish source, I don't have to do anything I don't wish to do. Public domain software is free. Absolutely positively no strings attached.

      However, I have no authority to demand people stop using the actual public domain work that's freely availible, though.

      If in fact people have done such, that is, attempting to stop people from using public domain works because they've released a commercial version of said work, then there's something seriously wrong with the legal system.

      Far too often people confuse words such as public domain, shareware, *-ware, open source, GPL, BSD, and the like.

  53. Comment removed by account_deleted · · Score: 2

    Comment removed based on user account deletion

  54. but gpl is not free as in freeom by JDizzy · · Score: 1

    I cannot stand it when people confuse freedom with free (as in price). The GPL isn't 100% *free* as in the definition of the term "freedom". The GPL has a nasty restriction, and even one restriction means it is not free (as in freedom). As we all know the GPL forces you to make any modification availabel to the original writer. In the end, GPL code is only usefull in academic environments, from whence it came at MIT. You can read code, learn from it, and go reimplement it away from the infected GPL code. This is the same reason many unix guru's tend to use oe of the BSD's over one of the Linux distro's, its the BSD license! In BSD you can look at thge code, get ideas, and go copy it. Or you can simply use the existing BSD code, and skip a step in the process.

    There are some good examples of GPL code that is good, and the fact that it is licensed under a restrictive license doesn't take away from the usefullness of the program. I speak of the GCC tool chain, and many more (too many to mention). Many of these tools are so good that its simply not worth the effort to clean room copy the tools.

    So it could be argued that GPL is not suitable for certain things. STuff like protocals, audio/video codex, and device drivers. Where the GPL would be perfect for userland applications. A good example of this argument would be the reasons why the Ogg/Vorbis programes decided to convert the vorbis codex form GPL to BSD license. The GPL was too restrictive, and would prevent chip fabricatin fo the codex for portable players, etc. A Network protocal shoudl be free of restrictions for the same reasons as the audio codex: hardware implementation! Device drivers that exist only as a GPL implementation are no good to other alternative OS users, such as BeOs back in the day didn't ahve as many network drivers as linux, but couldnt' use the existing linux drivers because they would force Be to expose its proprietary code (that it sold).

    We sometimes have to remind ourselves that the entire computer industry would not be where it is today without the openness of computer programers back in the early days. This open spirt existed way before any GNU license existed, and that was good enough for us then, good enought now.

    Companies like microsoft don't nessicarily see our GNU stuff as a threat to them, but a threat to computer programming in general. To clarify, I think Microsoft biggest fear is to be in a world where all code is saturated by a gnu encumberance, and one could not modify any code without being forced to publish the modifications. A world so utterly GPL that it collapses upon itself into stagnation.

    --
    It isn't a lie if you belive it.
    1. Re:but gpl is not free as in freeom by nick+this · · Score: 3, Insightful
      I cannot stand it when people confuse freedom with free (as in price). The GPL isn't 100% *free* as in the definition of the term "freedom". The GPL has a nasty restriction, and even one restriction means it is not free (as in freedom).

      Yeah, I'll give you this, but really the restrictions harm nobody but greedy people. It's the developer's freedoms (greedy developers) that are infringed. That's the whole point. From the point of view of the user or a civic-minded developer, there are as many freedoms as any other licenses, but with more benefits (as in the benefit of being able to use other's modifications). From any perspective aside from that of a greedy business, the GPL is superior.

      So it could be argued that GPL is not suitable for certain things. STuff like protocals, audio/video codex, and device drivers.

      It could be, but I sure won't do it. Perhaps a BSD licensing for core protocols right now is important, because as you say, it is necessary to get commercial interest to get a sufficient "critical mass" to make something like Ogg a standard. Okay. Right now.

      But that's only because right now there aren't enough free software users to be able to call the development shots with our force of numbers. As the free software pool grows, the harder it is to re-write that code base. That means that commercial interests will have to be able to make a *really* impressive application to expect people to pay for it. And that's in the best interests of the users as well.

      As far as poor BeOs not being able to use linux drivers in their OS... huh? Why should they? If they want to use, they have to share. What's wrong with that? And if they can't build a replacement OS that has the broad range of features and compatibilities as linux, or other free Operating Systems, then more the fool them for trying to get into a dying business model. Maybe they should have found a business model that leveraged free software rather than trying to compete with it. Let Be be a lesson to other commercial software companies.

      We sometimes have to remind ourselves that the entire computer industry would not be where it is today without the openness of computer programers back in the early days. This open spirt existed way before any GNU license existed, and that was good enough for us then, good enought now.

      Absolutely! Now you are sounding like a free software convert. Oh. Wait. You mean public domain. Yeah... you are right. In some ways, this would be ideal. In fact, I would imagine that most free software people would rather not have to copyright software and just let it be in the public domain. But the problem with that is that when that used to be case (your "early days" of the computer industry) commercial entities would rape the public domain software by taking the software and modifying it in ways that locked you into a vendors product, be it hardware or software.

      Thus, it became necessary to protect ourselves from greedy and unethical businesses. *That's* why there is a GPL. Yeah, it would be nice to imagine that all software could be free. Really free. Public Domain. But history proves that greedy people can't stop using public domain software to take away users freedoms. So users have to take matters into their own hands.

      To clarify, I think Microsoft biggest fear is to be in a world where all code is saturated by a gnu encumberance, and one could not modify any code without being forced to publish the modifications.

      Absolutely. And they should be, because that's how it's going. They are greedy monopolists locked into a dying business model -- that of extorting their customer base. Good riddance, I say.

      A world so utterly GPL that it collapses upon itself into stagnation.

      I'm not sure this follows. In fact, I'd argue that because of the large base of GPL code from which to build, it allows for people to innovate more easily. The infrastructure is already there, and someone with a great idea sitting in front of a computer in the Congo can implement it. Without a huge company behind them. Then we'll see stuff *really* start happening.

      Don't waste your tears on Microsoft. As they sow, so shall they reap.

    2. Re:but gpl is not free as in freeom by Anonymous Coward · · Score: 0

      The GPL has only one restriction, namely that you cannot add other restrictions. Unless we somehow phase out all the ethically defective people who want to control others, this is as close as we'll ever get to 100% Free.

    3. Re:but gpl is not free as in freeom by JDizzy · · Score: 2

      As far as poor BeOs not being able to use linux drivers in their OS... huh? Why should they? If they want to use, they have to share. What's wrong with that? And if they can't build a replacement OS that has the broad range of features and compatibilities as linux, or other free Operating Systems, then more the fool them for trying to get into a dying business model. Maybe they should have found a business model that leveraged free software rather than trying to compete with it. Let Be be a lesson to other commercial software companies.

      Actually, thsi *did* happento me! I used to work for Be Inc, and I wanted better support for my 3com 3c509 based isa card. BeOS had a driver, but it was in house home brew hack, and I wanted to have it work liek my slack box. So I took Donald Beckards driver, and we developed a wrapper for it so the driver thought it was talking to a Linux kernel (but was really BeOS 4.5). To make a long story short I had to remove the driver from the official Be website, and later from other sites..... as a result of the GPL. So I'm sure you can understand my sentiments about the subject. My supperiors actually were contacted by RMS himself to remove the BeOS wraper based driver. When I caught wind from up above, I sent email myself to RMS, and got a reply. I wish I still had an archive of the email, but let me just say RMS's notorious optinions bleed thru, plus a few attacks at BeOS being inferior due to not being OSS. Technically my wrapper violated the a GPL clause about linked libraries having the notion of being "derivitave", and thus "extending" a GPL'ed work... even though the driver was just linked in... it was linked to the BEOS kernel, and that was *not* available for Beckard to look at.

      I hope this little story was interesting, because it really happened, and to me (and one other guy at Be). Now look at Microsoft, back in the mid 1990's they took code from BSD to implement a native IP-tcp/udp stack. Most people would say that was good for Microsoft. Linux also took lots of code from BSD, and that was percieved good for Linux. So I wonder when writing code as GPL ever was *better* that writing it as BSD style.

      But the problem with that is that when that used to be case (your "early days" of the computer industry) commercial entities would rape the public domain software by taking the software and modifying it in ways that locked you into a vendors product, be it hardware or software.

      I actually think that helped more than hurt the industry, and that the OSS movement would have continued anyways. Vendor lock in can also be called vendor inovation, and many new good things came from the way ATT licensed UNIX to various vendors. Don't forget that this same vendor lock in is also what gave us the broad spectrum of advanced hardware platforms with tailored software. This same advancement in vendor lockin also spured OSS inovation. Just look at NetBSD that is able to boot 31 various platforms.

      In some ways the proprietary sector can benifite by the GPL, like SGI has with XFS. If can let the community have XFS, and eat its cake too since if IMB wanted to fix XFS those changes would go back to SGI. As a greed software company that would be good. In general that is how the GPL works by supporting the greed in society. My father used to tell me that communism would never work just because of the old maxum that: "If every human on Earth had exactly one acre of land to use as they wish, and never any more or less... jsut one acre. There would always be some people who want *two* acre's of land". The GPL works the same way for greed developers/companies. Considering that the above maxum is practically a constant truth, the GPL fundamentally doesn't work. What I'm saying is that since people are greedy: developers want the GPL, and consumers want to rip off the GPL. In fact, for people who want to steal gpl code, there really isn't much stopping them, especially not the GPL. This is like arguing that copyright laws is going to prevent teenagers from tradings mp3's on p2p networks. People are going to do what they want to anyways, and we BSD folks simply don't understand all the fuss about the GPL politics.

      --
      It isn't a lie if you belive it.
    4. Re:but gpl is not free as in freeom by nick+this · · Score: 2
      Actually, thsi *did* happento me! I used to work for Be Inc, and I wanted better support for my 3com 3c509 based isa card. BeOS had a driver, but it was in house home brew hack, and I wanted to have it work liek my slack box. So I took Donald Beckards [sic] driver, and we developed a wrapper for it so the driver thought it was talking to a Linux kernel (but was really BeOS 4.5). To make a long story short I had to remove the driver from the official Be website, and later from other sites..... as a result of the GPL.

      I don't see how you can see this as anything but a *plus* for GPL. If Be used GPL drivers to get a wide compatibility base without giving back improvements or new networking features, that's a bad thing. The GPL prevents that kind of thing. And that's better for users... they would get Be's improvements available in anything that used the GPL drivers. The only people punished here is Be -- because they wanted to have their cake and eat it too.

      And that's the whole GPL thing... it's *user* centric, not business-centric. And as a user, I see that as a plus. In fact, the GPL gives you the ability to do what you did... just not redistribute it. So the GPL protected your right as an individual user to do just what you did. It protected your individual freedom without letting a company profit from stealing without giving back.

      Don't forget that this same vendor lock in is also what gave us the broad spectrum of advanced hardware platforms with tailored software. This same advancement in vendor lockin also spured OSS inovation.

      The vendor lockin didn't spur OSS, it created it. Users don't like being locked in. They like choice, and given none by the vendor, they find ways to create choice. Hence OSS.

      I'll give you that vendor lockin caused the software industry to advance quickly. But the availability of high-quality GPL code make the economics of the situation different now. With such a large base of good-quality GPL code, GPL can advance as fast (or faster) than commercial interests to meet a goal. And as that happens, the added code is in GPL. Which accelerates the pace of the GPL side. Soon, I don't think it will be possible to compete against GPL. I just don't. The manpower necessary to clean-room implement all the stuff that GPL code does won't be worth it. Not for a operating system, certainly. Maybe only for standalone apps and vertical markets. And even then, the vendors will have to move fast to keep from being overtaken by GPL. Note that again, that's in the best interests of users.

      In fact, for people who want to steal gpl code, there really isn't much stopping them, especially not the GPL. This is like arguing that copyright laws is going to prevent teenagers from trading

      But that's not illegal! You can use any GPL code you want for any purpose. Unless you want to redistribute it. If you want to redistribute it, then you'll have to GPL everything. If you've redistributed it for the purpose of getting money, then you have assets and a business infrastructure that can be challenged in court.

      The fact is, the GPL has been very effective in stopping people from using GPL code illegaly. Your example is one. Epson's printer drivers is another. nVidia's use of GPL code is another. The GPL *is* an effective tool to protect users rights.

      I see why you are unhappy with GPL, but you are pointing the finger of blame the wrong way. It's not the GPLs fault that its license isn't compatible with Be. It's *Be's* fault. They made the conscious decision that they could make a better OS without using GPL code. That's fine. That's their right. But if they can't pull it off, it's not the fault of GPL for not letting them save themselves by stealing code. It's their fault for underestimating the size of the task or the cost of accomplishing those goals. Poor business planning, period.

      And I'm even sympathetic, because I liked Be. I wanted it to succeed. But they chose wrong. It happens in business. But it's not the GPL's fault. Maybe its even a good object lession: work with free software, not against it.

    5. Re:but gpl is not free as in freeom by mesocyclone · · Score: 2

      Yeah, I'll give you this, but really the restrictions harm nobody but greedy people

      What's with this greedy people? Why do I assume that you really mean folks like me who actually have to support a family by writing code! And who could not make that money if my code had to be distributed with source, and the source had to be available for free?

      In many areas, all that would mean is that other people would take my code and use it to compete with me with no recompense. An industry built this way would simply fail. Open source relies upon the good will of people to produce useful things. And it sometimes works - there are lots of fine people producing good stuff. But there are also lots of things not being produced in open source - because it isn't "cool" to do so, or it isn't as much fun. And a lot of open source is far less usable than commercial equivalents, because open source people get more plaudits (which is the coin of the realm) for writing code than for writing documentation. And it is more fun to come up with a clever application than it is to produce installation software for it that allows idiots to use it.

      GPL is fine for those who want to freely give of their time. It is a charitable thing. However, as in other areas of human endeavor, charities do not supply everything needed! They are good at what they choose to be good at and in areas where they can attract interest.

      A GPL economy is an imaginary economy. It assumes that everyone who writes code can afford to do it for free, or that if they choose to sell it there is nobody to come along and compete with them with their own code, reducing their income. It is a utopian concept, and like most utopias, it works best at the small scale, and fails entirely when called upon to address the real needs of real people.

      Let me give a real world example. One thing I do is write code for the Health Insurance claims processing industry. How many people are willing to do this for free and GPL the results? I sure am not. If I didn't get paid for it, I wouldn't do it! If I didn't need an income, I would be happy to spend some of my time writing nifty kernel goodies in open source, or doing some other cool thing. But in the real world, somebody needs to write that health insurance software, and that somebody wants to be paid, and that payment won't happen if the code is GPL'd.

      Now... imagine that the government produces some of this software. It would probably be a result of somebody's research. It would probably be ungeneralized, poorly documented and not very friendly to install. It might also have the very best algorithms for some parts of this (there really is some magic in this area).

      If this is GPL'd, that software will probably never be used. Why bother? It would cost a lot to bring it up to commercial standards. And once you did, you would have to release the source for your competitors. People generally don't make investments with the intent of taking a loss! They have to recoup that investment. And they do that in many areas via exclusivity - in software, by protecting their intellectual property.

      Now, in another universe, that software is truely free - it is public domain. Several companies might pick it up and incorporate it into their products. The successful ones would make it more usable, more general, better documented. etc. There might be several that would compete. The result would be a reduction overall in the cost of processing health insurance claims - a positive good. The only objection I can see martialed to this is that somebody is *gasp* making money, with their own efforts, but using somebody else's product(for which that someone else was compensated by the government).

      So what's the problem?

      I think a lot of GPL advocates need to grow up and recognize that it isn't a panacea, but rather one more form of restrictive license - appropriate for certain endeavors and totally unappropriate for others.

      And for those who think that all source code should be freely available... well, I'll bet you still believe in Santa Claus and the Tooth Fairy!

      --

      The only good weather is bad weather.

    6. Re:but gpl is not free as in freeom by Anonymous Coward · · Score: 0

      >In many areas, all that would mean is that other
      >people would take my code and use it to compete with
      >me with no recompense.

      Sure, your competitors can take your code and use it in their products, but with the GPL, you can do the same to them. It doesn't give your competitors everything and you nothing, as you seem to imply; rather, your competitors will be in the same situation you're in, with the same conditions imposed upon them.

    7. Re:but gpl is not free as in freeom by Anonymous Coward · · Score: 0

      You seem to be trying to support a family based on selling copies rather than actually writing the code. Work-for-hire doesn't have this problem. My doctor doesn't need to refuse to explain my diagnosis or treatment, prohibit me from seeing any other doctors, or hold one appointment and try to cash in on it eternally.

    8. Re:but gpl is not free as in freeom by mesocyclone · · Score: 2

      This would be fine if all situations were guaranteed to be symmetric. But that is very unlikely! Much more likely is I spend years (or my customer spends hundreds of thousands of dollars) developing the code, and then someone else simply takes it - perhaps makes a cosmetic mod - and then is in competition with me. However, they have the hundreds of thousands that *they&* didn't spend on sofware available to their marketing and support efforts. This gives them an advantage of me!

      In other words, in general GPL favors the pirate over the originator. GPL only works for *voluntary* effort or in conjunction with other sources of profit (Service Contracts, Training, Hardware).

      I notice that you do not attack IBM for using GPL'd UNIX to increase their *hardware profits (others in this thread have noted this). In fact, on Slashdot there is generally great cheering (which I agree with) when another hardware manufacturer adapts an open source solution.

      Another way of saying this is that GPL results in programmers being paid nothing to enrich hardware makers, or software companies going bankrupt while enriching the hardware makers.

      Selective condemnation is an interesting attribute of the same people who usually favor utopian solutions (for a related discussion, see
      www.tinyvital.com/blog and www.tinyvital.com/PCD.htm).

      GPL *removes* the ability to compete over software features. With GPL everyone can take advantage of the functionality created by anybody. Thus it *ends* competition, leaving the only competition to be in the areas of servicing and marketing. This naturally benefits the large companies over the small, as the large can afford better marketing.

      In such a world, software innovation will die!

      --

      The only good weather is bad weather.

    9. Re:but gpl is not free as in freeom by mesocyclone · · Score: 2

      And is there nothing wrong with supporting a family selling copies? Is code a special kind of beast where it is okay to sell the original but not the copy?

      Work for hire is one mode that programmers may want. But they may also want to be able to invest their *sweat equity* (capital) into their code, and then get a *return on their investment.*

      At one time, I had a business which made small hardware widgets (ham radio repeater controllers with embedded processor). The key proprietary component in this was the software. Anyone could copy the hardware and compete with me, but it took real, rare skills and real cost (which I had already invested via my time) to produce that software. I was not about, and would never, give away that competitive edge for some GPL utopia. In that case, others would simply take my work, dupe my circuit boards, and hit the market with an unfair capital advantage over me - the creator.

      Your argument is inherently anti-capitalist and anti-freedom. The only people who have freedom in this case are those who *chose* to GPL their *own* (not taxpayer supported) and those who take that code under the GPL license.

      Those who take the code may or may not contribute to the GPL process. They may simply take it parasitically (as many of us do when we use Linux but don't contribute to the Linux project). In the case of Linux, that is okay - because it is expressly in the interest of those who contribute to Linux. If it wasn't, they'd be fools to GPL it!

      Your doctor example has nothing to do with software, except in the case of a consultant working for a client. So let's take the latter case... assume I am a consultant producing code for someone (work for hire). I would have no right to withhold it the source from my client (unless that was in the contract, which in fact is not at all unusual). But somebody would have to GPL the software. This simply pushes the capital expenditure burden from me to them, but the economic effect hits me as well as them - if they cannot operate economically in a closed-source, no-piracy mode, then they won't pay me. And for most software, this is a reality.

      Utopianism is a good way to come up with creative ideas, but unfortunately (as in this case) it always results in overapplication and nonutopian results. For some of the consequences of utopianism, see my blog my blog.

      --

      The only good weather is bad weather.

    10. Re:but gpl is not free as in freeom by gpoul · · Score: 1

      If you would've been a user of Be (I haven't been) you wouldn't say that the GPL helped you in that case.

    11. Re:but gpl is not free as in freeom by nick+this · · Score: 2
      What's with this greedy people? Why do I assume that you really mean folks like me who actually have to support a family by writing code! And who could not make that money if my code had to be distributed with source, and the source had to be available for free?

      Wait! That's not what I'm saying! My definition of greedy people is those people that want to use the efforts of other (by taking GPL code) and not returning the favor (contributing back). Those companies that want to use software as leverage to lock you into an upgrade cycle. (read: Microsoft). I'm in the same boat as you. My point is that if you want to use GPL software you have to give back. That's all. If you want to use GPL, you have to share. Period.

      It's not such a white and black situation as you describe. Even in a mostly-GPL world, there will be plenty of non-GPL code. Your vertical market (health) will probably be largely non-GPL. Or in the industry I'm most familiar with (insurance).

      And even in those markets, GPL code is still useable for non-distributed code. If there *were* a good health care app that you wanted to modify for in-house use, you could. Legally. Just not sell it for profit (as a greedy corporation would).

      But in the real world, somebody needs to write that health insurance software, and that somebody wants to be paid, and that payment won't happen if the code is GPL'd.

      And there would still be a market, even in an all-GPL world, for you to be paid to customize a GPL'd health app for your company.

      Now, in another universe, that software is truely free - it is public domain. Several companies might pick it up and incorporate it into their products. The successful ones would make it more usable, more general, better documented. etc. There might be several that would compete. The result would be a reduction overall in the cost of processing health insurance claims - a positive good. The only objection I can see martialed to this is that somebody is *gasp* making money, with their own efforts, but using somebody else's product(for which that someone else was compensated by the government).

      Aha. But can't you see that this situation is *worse* than the GPL one? Imagine there is a mediocre health care claims processing application out there. Then some insurance company picks it up and modifies it. They turn it into a great application, but one that only processes insurance claims for their company. They then turn around and release that software. Now, sure, there is a better claims processing software, but its locked into a particular company.

      Certainly, that's good for the company, but it's bad for the user. In this case, the companies that process those claims. They would rather see the app turned into a good application for processing any claims. But the changes to the app that make it great for the one particular company are hidden. Can't get to them.

      The GPL protects us from that kind of thing, and its better for it. It doesn't restrict your company's right to modify it to do anything you need it to do, but it prevents a greedy company from using that public domain software as a weapon against you.

      Think on it a while, and see if GPL automatically means no software development. I think it doesn't. Most software development is in-house anyway, and GPL doesn't restrict in-house use. I firmly believe that GPL will drive more innovative software because it gives a larger platform to build from.

      It doesn't really matter -- we are arguing in a vacuum. This is going to happen regardless. The economics of it we'll see soon enough.

    12. Re:but gpl is not free as in freeom by mesocyclone · · Score: 2

      Remember I am not arguing against GPL in general, but rather against forcing publicly developed software to be licensed as GPL.

      Aha. But can't you see that this situation is *worse* than the GPL one? Imagine there is a mediocre health care claims processing application out there. Then some insurance company picks it up and modifies it. They turn it into a great application, but one that only processes insurance claims for their company. They then turn around and release that software. Now, sure, there is a better claims processing software, but its locked into a particular company.

      But your argument sets up a straw man. It assumes that only one company can take the free, but mediocre software and improve and sell it. If there is a big enough market to justify investing in the software, then other companies will also come in and either use the free software or write proprietary closed-source software. If there is not a big enough market, then your examples actually shows the good side of non-GPL - it shows that someone will at least provide good claims processing software, but you have to pay for it.

      This is better than just having the mediocre software out there, since it adds choices: the mediocre software is STILL THERE, and now there is a better, but more costly proprietary choice also!

      BTW... I wrote a longer (and more trollish) discussion of this, which addresses your other issues in more detail, and put it on my blog for those who are interested.

      --

      The only good weather is bad weather.

    13. Re:but gpl is not free as in freeom by nick+this · · Score: 2

      The fact of the matter is that I was a Be user. I bought 4.0 and 4.5. And I couldn't get my ISA NIC to work either. I had to buy a PCI one.

      So I was impacted by this same issue. But that has nothing to do with the utility of GPL code.

    14. Re:but gpl is not free as in freeom by gpoul · · Score: 1

      That's nonsense. Sure it does. You were impacted by this. You couldn't get your ISA NIC to work. There was a good driver available as GPL code but Be wasn't able to use it because of the GPL.

      And you still say "that has nothing to do with the utility of GPL code"??

      Sorry, but I can't follow this logic.

    15. Re:but gpl is not free as in freeom by nick+this · · Score: 2

      Its a matter of perspective.

      You see: "GPL license is too restrictive to allow Be to use the code".

      I see: "Be's licensing lacked the freedom to allow it to use the GPL code".

      The problem as I see it, isn't GPL, but Be. Of course, that's a matter of perspective. In the end though, given that whole story, my reaction wasn't "Damn GPL!", it was "Damn Be!".

      And I'm *glad* they couldn't use it. It wouldn't be morally right to take other people's drivers and use it to make money off of. That's why I value GPL. It's a buy-in. When I add s/key support to a program, or I fix a parsing bug and return the patch, I've paid may fee to allow me access to all the GPL stuff out there.

      Really, if you think of it that way, there is a cost associated with GPL -- the cost of contributing improvements. In that way, it really doesn't differ from commercial software.

      Why didn't anyone get pissed off that Be couldn't use Microsoft's drivers for the 3c509? They would have the same rights to steal Microsoft's code as Donald Becker's.

      I guess that just highlights the subject of the very parent post: the GPL isn't free. There is a real cost associated with it. For those that' won't share code. For users, it's better than free.

    16. Re:but gpl is not free as in freeom by Anonymous Coward · · Score: 0

      You were selling radios; you had no reason to care what software ran on them. Customer patches could only make your radios more useful and easier to sell. If you were unable to compete with other radio makers, you were detracting from the economy; you should have sold the software to efficient producers of radios based on the labor that went into it.

      The point of the doctor example is that you're demanding a degree of control over your customers that's not only unethical but unnecessary--well paid professionals have been doing fine without it for millennia.

      Economics is about rationing scarce goods. Software isn't scarce (it can be duplicated indefinitely without cost) but labor is, so labor is what should be sold. The argument is only "anti-capitalist" if you pretend software were capital, and only "anti-freedom" if you demand your freedom include the right to deprive others of their freedom.

    17. Re:but gpl is not free as in freeom by mesocyclone · · Score: 2

      No, I was selling radio control systems. The primary added value was the software, which I wrote. I was the efficient producer of that software - anyone can make the hardware, but I made the software back when it was early in the technology cycle for that environment.

      As far as demanding control over my customers... give me a break! If I sell you a little plastic widget, you can do whatever you want with it. But you have no rights to the injection mold that went into building it. Software source is the injection mold. Binary software is the widget. Please explain why software is different??? Oh year, because you can cheaply duplicate the source - but ONLY if you can get hold of it - which is exactly why people need to keep it proprietary.

      Economics is about the management of goods and labor, and ultimately about capital and more abstract things. You need to understand the concept of capital. Software *source* is indeed capital. It is tangible and very rare. The fact that it can be *stolen* and then duplicated is irrelevant. You argue that software isn't scarce. If you believe that, try duplicating my controller software. Good luck! The reason you will have trouble doing so is that *I* have the source code and you don't, and the binaries are also hard to duplicate because they are burnt into EEPROM's inside of secured microcontrollers.

      As far as freedom, I don't include the right to deprive others of their freedom. They already have their freedoms. When I write software, they don't suddenly acquire *more* freedoms unless I give it to them. YOU are the one who is talking about removing freedom: my freedom to create things and not have someone else reduce its value by copying it. If I *choose* to release it with GPL, that is *my* free choice. It is not your free choice to force me to release it that way!

      Nobody is forced to buy my non-GPL software. That is their freedom. My freedom is my right to release it under whatever license terms I want (within the law).

      --

      The only good weather is bad weather.

  55. GPL is not about freedom by Anonymous Coward · · Score: 0

    It has nothing to due with America and freedom. Someone is needs to stop spiking your coffe. They have a VERY valid point. Government sponsorship of GPL will give an artificial benefit to OSS ( OSS != GPL ). Thereby reducing the competiveness of the companies in America to compete with other countries ( which due provide corporate sponsorship, remember America does not as a practice sponsor business to increase competativeness, why should they due the opposite with a GPL approach. What's wrong with BSD or something like that Apple's approach. Is it even needed ?

  56. Re:first 4 slides: Source Licensing & Software by stinky+wizzleteats · · Score: 2

    Finally, somebody please mirror these images, the bandwidth on that site is getting sucked dry.

    Do a gnutella on Microsoft Slides.

  57. Re:J-E-T-S JETS JETS JETS!! by Anonymous Coward · · Score: 0

    This is news for nerds not news for jocks... nobody give a fuck.

  58. Re:but gpl is not free as in freedom by Anonymous Coward · · Score: 0

    You haven't read the GNU General Public License.

    "without being forced to publish the modifications"

    This is only when there is distribution.

    You can keep secret modification and privacy is respected.

    Equity is the important point of the GNU GPL and some other "copyleft" type license.

  59. ls by Anonymous Coward · · Score: 0

    What you have to do is to touch LC_COLLATE env-var and set it to be C, not en_US as probably RedHat set it (if not set, it inherits from LANG and others). That way you get ASCII sorting back.

    1. Re:ls by Teach · · Score: 1

      What you have to do is to touch LC_COLLATE env-var and set it to be C, not en_US as probably RedHat set it (if not set, it inherits from LANG and others). That way you get ASCII sorting back.

      Holy crap. You, my friend, are much appreciated. You learn something new every day.

      --
      Graham "Teach" Mitchell, computer science teacher, Leander HS
  60. Re:Jesus Christ.... by Anonymous Coward · · Score: 0


    Users don't have a right to look at the code they're using unless the developer of the code grants them that priviledge.

    This is not about "freedom". Source code has nothing to do with freedom.

    You don't even need a computer to be free.

  61. MS wants even more freebies from the gov. by g4dget · · Score: 4, Interesting
    Microsoft seems to be saying that they don't like the GPL used for government sponsored research because they then can't just take that software and re-sell it. Instead, what they want is that government sponsored researchers develop enhancements to Microsoft's products under shared source agreements, enhancements that will be of no commercial value to anybody but Microsoft. Seems to me Microsoft wants an extra-sweet deal from the government.

    I'm quite open to the idea that governments should consider creating software under X11/BSD-style licenses. But I think working with software under Microsoft/Sun-style "shared source licenses" is completely unacceptable because those kinds of licenses favor a single vendor; this should not only be discouraged, it should be made illegal: no government sponsored researcher should be permitted to create software under such agreements. The GPL may not allow commercial use of software developed by researchers, but it is equitable and fair to all commercial competitors.

    1. Re:MS wants even more freebies from the gov. by Radical+Rad · · Score: 2

      It does seem that the main thrust of this presentation is to discourage the government from releasing software under the GPL where Microsoft may not simply cut and paste it. They aren't even advocating having the government contractors place the code they write in the public domain, so the alternative seems to be, as you say, that they will use their influence to have enhancements written for their products and contributed to them under a "shared-source" agreement. I think you hit the nail on the head here.

      While releasing the code to the Public Domain or under BSD style license seems fair at first, I can forsee commercial vendors then using their influence to have government contractors write specific pieces of code, then create products or do MS style innovating based largely off of that code, and colluding with each other and government to make it difficult for others to obtain the source or even to find out about the existence of the source. Even now, who can point me to a web-site filled with government written Public domain code without first doing a search on google? The taxpayers who funded the creation of the code logically should own it and not be forced to pay for it yet again by a corrupt system. For that reason it seems to me that the GPL is the fairest choice for the government to release code under. Any commercial vendor with the desire would be able to study the GPL'd code and write their own copyrightable program using the taxpayers property as a model.

  62. whats wrong with these slides? by stock · · Score: 1
    At a first glance i can't see why these slides would be a bad thing from microsoft. As a matter a fact if SUN Microsystems would be the used banner, no-one would have even blinked their eyes.

    So whats wrong here? IMHO the fact that today microsoft is still a monopoly in software land, and the fact that US law is not abided by the current surpreme court. The sherman act to be more precisely.

    Robert

  63. Strawman by cowbutt · · Score: 2
    The argument over whether the GPL is a "Public Domain" license is a strawman. It isn't, and it was never intended to be. Microsoft are quite correct about that, and that the BSD license is pretty much what a PD license should be.

    Now, I gather in the US, the present legislation means that publicly-funded software development must be placed in the public domain, which would seem to exclude the GPL.

    The question though, is much more fundamental; should publicly-funded software development be "public domain"?

    On one hand, people have paid the taxes that funded the development, so they should get all the benefits. The most efficient way of doing this is to make the software Free and make sure that derivative products stay Free. And, as a bonus, it doesn't even stop proprietary software manufacturers from learning from it.

    On the other hand, proprietary software manufacturers pay taxes too, so they should have the same rights.

    On the other, other hand, most corporations of Microsoft's size actually pay very little in the way of tax, and will employ embrace-and-extend strategies given half the chance. Eventually, this screws over the state and therefore the people as a whole.

    For these reasons, it's my belief that publicly-funded software development should be licensed under GPL-like licenses, unless there's a compelling reason not to do so. And the original developer and a proprietary software manufacturer are always at liberty to agree a mutually agreeable alternative license if the main license doesn't suit the latter party.

    An example of code which should probably be released under a LGPL or weaker license would be software to handle a new file format or a new network protocol. In these cases, it's probably more efficient to license it under a more PD-oriented license such as the LGPL or BSD license so that the code may be re-used and the likelihood of incompatible deviations from the reference implementation greatly reduced. In brief; "use the right license for the job" - even RMS wrote something along these lines, but I can't seem to find it right now...

    --

    1. Re:Strawman by NineNine · · Score: 2

      On the other, other hand, most corporations of Microsoft's size actually pay very little in the way of tax, and will employ embrace-and-extend strategies given half the chance. Eventually, this screws over the state and therefore the people as a whole.



      This is outright wrong, or a complete lie.

      In the quarters ending Nov 30, 2001, Feb 28, 2002, May 31, 2002, and Aug 31, 2002, Microsoft paid $4,423,000,000 in tax. Redhat paid exactly $61,000.

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

      Why is the earlier statement a complete lie? Please explain this. I don't see why comparing Microsoft with Red Hat (i.e. two members of the software industry, albeit differently focused) would support your theory. Maybe $4,423,000,000 isn't that much either for such a large-size company?

    3. Re:Strawman by NineNine · · Score: 1

      He said: "On the other, other hand, most corporations of Microsoft's size actually pay very little in the way of tax,"

      And that's not true. They pay about 4 billion a year in income tax alone, never mind all of the various employment taxes they pay. He was arguing that GPL'ed software helps out the gov't more, and I was pointing out that the largest software company that works with GPL software paid out less tax then many of us do in a year!! So, it's not true that private corporations "pay very little in the way of tax". They actually pay a hell of a lot of tax, even without the comparison to companies like RedHat which pay next to nothing because they have virtually no profit.

    4. Re:Strawman by cowbutt · · Score: 2
      In the quarters ending Nov 30, 2001, Feb 28, 2002, May 31, 2002, and Aug 31, 2002, Microsoft paid $4,423,000,000 in tax.

      Where did you find these figures? I've looked in the most recent 10-Q and 10-K filed with the SEC but my reading doesn't agree with your figures.

      I was going on various articles I've read along the lines of this one.

      If your figures are correct, that would mean they're being taxed at an effective rate of ~56% (annual revenues of ~28 billion US$). I thought the US was the nation of *low* taxation compared with us savages over here in Europe! Even Microsoft's SEC filings only admit an effective taxation rate of ~33%...

      --

    5. Re:Strawman by Anonymous Coward · · Score: 0

      NineNine pulled those stats out of his ass... pretty much where he pulls everything else out of. Including his dog, his kids, his wife and his gerbils. Stupid fuckwit. Go away NineNine. Go the fuck away. Nobody cares about your lies asswipe.

  64. Umm by Anonymous Coward · · Score: 0

    Why not believe this time?

    Simple: We have no information to prove whether or not MSFT created these slides.

    I am not a MSFT shill. I am, however, growing largely irritated by the large percentage of /. visitors who, like yourself, think that anything purported to have come from MSFT must have, that MSFT is the evil empire, that MSFT internally acts and speaks differently than any other company in existence (sorry folks, but Halloween memos read like just about any memo inside just about any technology company), and so on and so forth.

    I saw someone smashing the windows of the community centre across the street a little while back. I couldn't quite make out their face, but since I don't much like you I'll just assume that you did it and run around telling my friends about what you did. Do you think that's fair? Your treatment of MSFT is no different.

  65. The GPL is not the only OS license! by the_germ · · Score: 2, Insightful

    One of the main points in M$'s argumentation is that the GPL hurts the industry, because you cannot write commercial apps based on GPL software, but the GPL is not the only Open Source license and most reasonable OS libraries are licensed under the LGPL or similar licenses that allow developing commercial software.

    Open source developers simply have to choose an appropriate license for their project when they start. And if they find out that they chose wrong there is still the possibility to change the licensing terms. A very prominent example for such a license change is the Wine project that changed it's license from X11-like to LGPL recently.

    If a company finds an OS library useful for their own project, but they cannot use it, 'cause it's GPL, they can still contact the author and ask for different licensing terms. They'll probably have to pay for that then, but they'd have to pay for a commercial product, too. So even GPL'd libraries are not really a hurdle for commercial software development. A good example for such dual licensing is ReiserFS, which is published under the GPL, but sold under different licensing terms to companies that want to use it commercially.

    1. Re:The GPL is not the only OS license! by bruns · · Score: 1

      I think you hit the nail right on the head.

      If the developer(s) don't want to relicense the code for you, then deal with it - either make your code compatible with his, or don't use his source and write your own.

      Sometimes, developers really don't ever want their programs in a commercial situation. That is their right.

      I would use the BSD license for my work more often, its just that companies like M$ leave me no choice but to license my stuff under GPL right off the bat out of concern that it might be horribly borgified if its useful.

      --
      Brielle
  66. Transcription with commentary by pulaski · · Score: 1

    Yes, transcription may be useful but transcription with commentary is more interesting. For example, look at the file "img_223r.jpg" On the lower slide headed "Areas of Concern". The authors display their bias when they paraphrase one of
    the terms of the GPL as:

    "Any GPL code can be copied and redistributed at no cost, may charge for cost of distribution"

    It's my understanding that although the above is true, that's not the whole picture. As I see the GPL, any code can be copied and redistributed at no cost, at the cost of distribution or at any cost a buyer is willing to pay as long as all the other terms of the GPL are honored.

    This thoughtful presentation missed this point among others I'm sure.

    --
    Quid, me anxius sum?
  67. Re:J-E-T-S JETS JETS JETS!! by Anonymous Coward · · Score: 0

    Maybe if you weren't an uncoodinated dork, you wouldn't be having a hissy fit.

  68. TCP/IP Slide by jdeisenberg · · Score: 5, Insightful

    For me, the most interesting slide was the bottom half of img_0224r.jpg, (Areas of Concern) where it says: "Primary research results placed under the GPL are precluded from commercial use: TCP/IP example".

    I'm wondering if this translates to "We are concerned, because we can't charge people royalties for every packet they send." I would have loved to have heard the commentary that went with that slide.

  69. Who cares if it's legit? by Anonymous Coward · · Score: 1, Interesting

    Even if it is legit, that doesn't mean it's true, or even what Microsoft believes is true.

    In other news, Nike is defending their right to lie about shit (as Doc Searls so eloquently put it), and the U.S. Chamber of Commerce, Exxon/Mobil, Monsanto, Microsoft, Pfizer, and Bank of America are supporting them.

    If they win in court, maybe Microsoft can beat Linux once and for all by simply stating that a Linux license costs $100 more than an XP license.

    Is this not a great country?

  70. OK, I say it again. by Anonymous Coward · · Score: 0
    I don't use Microsoft stuff at home because I don't like it; I use Linux, my wife uses OS/2. Hey, we like it, and considering I don't have the time, inclination, or knowledge to build a full operating environment from ground up, I'll use it.

    Accordingly, friends of mine who use Microsoft products don't use Linux; few have tried it (and honestly don't like it), but most are either ignorant of the facts or have partaken of the flavor-ade, as it were, but a few still don't know just what Linux is.

    My point? If you don't like either alternative, build your own operating system or shut up.

    Mod me down if you will, but you know that's where it's at.

  71. The Lost Art by qwijibrumm · · Score: 2

    I think sarcasm is becoming lost in its true intended form. Granted one cannot hear a physical tone of voice in text. But I think my statements were just outlandish enough so no one could ever take them seriously. Silly me.

    --
    I wish there was some there was some way that I could be outside playing basketball, in the rain, and not get wet.
    1. Re:The Lost Art by Evil+Adrian · · Score: 1

      Had no idea... you had me convinced that you were serious. :-)

      You have to hint at the sarcasm somewhere man!

      --
      evil adrian
  72. Re:My Thoughts (or ramblings) by Anonymous Coward · · Score: 0

    Well, two points:

    (i) Linux processes are about as heavyweight as NT threads!

    (ii) Java threading on Linux pre Java-1.4.1 sucked because Solaris threading is different to linux, and the Sun Java was basically a recompile of Solaris's source (admittedly with some non-trivial work by blackdown).

    Linux threading is basically:

    There are processes. Processes can share memory pages. A thread "in" a process is a process with every memory page shared with the other process.

    This is interesting - because, actually, linux processes can allow much finer-grained control than just a thread/process distinction - one can choose from a spectrum in between the two.

    Linux 2.6 will include a new scheduling algorithm which will make large numbers of processes/threads multitask better with less overhead - so making it more suitable for java too.

  73. Why not $un or Net$cape as well? by mgkimsal2 · · Score: 4, Insightful

    I've always HATED the stupid "M$" text that people use when talking about Microsoft. They want to make money - good for them. HOW they go about it has proven problematic/wrong/illegal/whatever, but the motive is the same for all companies - make money.

    No one is suggesting propping up a company at the expense of another - certainly not in this thread.

    Please lose the $, or use it evenly:

    $un
    Net$cape
    $ear$
    $BC
    $pirit
    $am$ Club
    $heraton

    etc

    1. Re:Why not $un or Net$cape as well? by Malcontent · · Score: 2

      "Please lose the $, or use it evenly:"

      Why? All those companies are not evil. They don't make their money unethically, they are not run by morally corrupt people, they don't have a history of stealing, lying or cheating, and finally they don't call me communist or cancerous.

      If and when they act as evil as M$ I will refer to them in an insulting wat. Until then I will respect their the names they have chosen for themselves.

      M$ is an evil company run by evil people which commits acts of evil. Using the $ in their names and not in other comanies names is very consistent if your rule is only insult evil comanies.

      --

      War is necrophilia.

    2. Re:Why not $un or Net$cape as well? by NineNine · · Score: 1

      "Evil"? hahahaha Who's REALLY posting this? George Bush? (ie: "Axis of Evil"). ROTFL

    3. Re:Why not $un or Net$cape as well? by mgkimsal2 · · Score: 3, Interesting

      Why would you take personal umbrage because some people make the perfectly valid observation that the GPL is viral? Cancerous is a somewhat loaded term, but it most certainly is viral. I don't remember anyone referring to the GPL as communist, but I can recall some MS officials stating that it was not in the US taxpayers' interest to have US government funded research be licensed under the GPL (which can be construed as 'GPL is unamerican' certainly).

      But when has Microsoft the company ever called YOU - Malcontent - "communist or cancerous". I dare say never. They may, as a corporate entity, publicly disagree with a license (let's remember, it's GPL licensing they have big problems with, not you personally) which you think is the bee's knees, but they don't personally attack YOU.

      You're suggesting there's no moral corruption at the top of Sears or IBM or WalMart or any of the other dozens of companies much larger than Microsoft? MS is the pinnacle of evil incarnate?

      You're just not as involved in the other industries to see how large companies stomp over small ones all the time, regardless of industry. WalMart certainly has plenty of complaints against it, but they're selling Linux online, so maybe we should be nice to them?

    4. Re:Why not $un or Net$cape as well? by dvdeug · · Score: 4, Insightful

      Cancerous is a somewhat loaded term, but it most certainly is viral.

      Why is viral any less loaded than cancerous? The GPL certainly does not behave as a virus, considering it only comes in when it's invited.

    5. Re:Why not $un or Net$cape as well? by Tony-A · · Score: 2

      With Bill Gates the richest man on earth, or something like that, and planning to get richer still, the M$ seems quite natural.

    6. Re:Why not $un or Net$cape as well? by oliverthered · · Score: 1

      Hmm... I always though M$ was used because when you buy a PC you always pay the Microsoft dollar.

      So, I brought a new PC and payed M$.

      --
      thank God the internet isn't a human right.
    7. Re:Why not $un or Net$cape as well? by CSG_SurferDude · · Score: 2

      Who's REALLY posting this? George Bush? (ie: "Axis of Evil").

      Get with the program dude....

      That's supposed to be typed like this:
      Who'$ REALLY po$ting thi$? George Bu$h? (ie: "Axi$ of Evil").

      (Gee, working that web $ite of your$ mu$t have fried your brain. ;-)

    8. Re:Why not $un or Net$cape as well? by nathanh · · Score: 3, Interesting
      ... the perfectly valid observation that the GPL is viral?

      Because it's genetic, not viral.

      The GPL only affects derivative works. That's genetic, not viral.

      The GPL requires "consensual derivation" before it replicates. That's genetic, not viral.

      The GPL transfers a single "genome" (aka the license) from the parent to the child. That's genetic, not viral.

      A virus is something that infects a host, harms or kills the host, and spreads between hosts without asking either host permission to do so. The GPL does none of these things. The GPL is most definitely not viral.

    9. Re:Why not $un or Net$cape as well? by Gonzoman · · Score: 1

      Let's get past the Microsoft is evil stuff. As a corporation they are unethical and a bad bunch of bastards but how are the worse than most other big businesses? If you don't like them, don't use their products (I don't). Microsoft perceives themself as being under attack, and is striking out in the only way they know.

      I don't care what Microsoft does. They have no way to kill free/open source (take your pick) software. They say that when all you have is a hammer, every problem looks like a nail. Microsoft has a god aweful big hammer, but free software is not anything like a nail. They have no tools to deal with it.

    10. Re:Why not $un or Net$cape as well? by Malcontent · · Score: 3, Interesting

      MS and it's executives have used the word communist and cancer. They chose those words very carefully because they knew it would trigger negative reactions in the public at alrge and the media. It's a calculated effort to demonize open source programmers and users and to fan the flames of hate towards them. They want the US public to hate open source users and developers. So maybe they did not mention me by name but they did not have to they simply publicly smear an entire segment of the population. They are evil but they are smart. They have studied how other people in politics have demonized whole sections of the population throughout history and have applied those lessons to demonize open source developers and users. Using words like virus, cancer, communist, un-american etc are a carefully thought out and well orchastrated effort by the executives of M$ to attack us.

      "You're suggesting there's no moral corruption at the top of Sears or IBM or WalMart or any of the other dozens of companies much larger than Microsoft?

      No just not as much. Wally world is a very evil company (in different ways then M$). Their own employees sued them and won for making them work overtime without pay. This is why I will never walk into a wallmart store as long as I live and there are many people who feel the same way. I have never heard anything bad about sears or IBM. So I am

      "MS is the pinnacle of evil incarnate?"

      Yes pretty much. Worse then wallmart, worse then enron even (that's a close call though) definately up there with qwest, worldcom and the rest of the sleazeballs.

      --

      War is necrophilia.

    11. Re:Why not $un or Net$cape as well? by jelle · · Score: 2
      "Why is viral any less loaded than cancerous?"

      Both are wrong.

      The GPL doesn't start by genetic mutation either.

      For one, Viral infections are often much better treatable than cancer currently is, but both are considered a disease. GPL is a license, not a disease.

      So instead of calling it 'viral' or 'cancerous', which imply a disease, a term like 'infectious' would already be better, because laughter can be infectuous too. But that term does not fit either, especially when used with lawyers in the room (see the dictionary)...

      If an adjective must be used, I suggest using something like 'genuine', or better yet 'free'


      (I get a strange sudden urge to make a script that 'A HREF's all words in a text to dictionary.com).

      --
      --- Hindsight is 20/20, but walking backwards is not the answer.
    12. Re:Why not $un or Net$cape as well? by jelle · · Score: 2

      If you look up how much cash MSFT has and how much other companies keep in cash, and then look up how much of their earnings were paid in dividents by MSFT (none) and the other companies, it should become clearer. The motive for companies is not to make money and stock it in a cash pile like MSFT is doing, but the motive is to use it for growth or if that is not possible to return the profits to the owners.

      That i$ one reason why...

      --
      --- Hindsight is 20/20, but walking backwards is not the answer.
    13. Re:Why not $un or Net$cape as well? by gpoul · · Score: 1

      Yeah. sure. What about this scenario:

      You use library A that is licensed under the GPL. - You write a program B.

      Now you link program B to library A. - What just happened with program B during linking to GPL'd library A?

      Viral anyone?

    14. Re:Why not $un or Net$cape as well? by nathanh · · Score: 2

      You use library A that is licensed under the GPL. - You write a program B.

      Now you link program B to library A. - What just happened with program B during linking to GPL'd library A?

      Viral anyone?

      No. You made a conscious decision to license your program "B" under the GPL. You knew that library "A" was GPLd and you knew that linking library "A" against program "B" would make program "B" a GPLd product also. There was no surprise here. The facts were all laid out in advance and you chose to use the GPLd library, fully aware of the licensing implications. This is nothing like a virus.

      If you are still keen on these negative analogies then I think the closest would be to liken the GPL to a sexually transmitted disease BUT with the provision that the disease carrier tells everybody about it before having sex. If you are so desperate for sex that you choose to ignore the warning then you have waived the right to complain when you get the STD.

    15. Re:Why not $un or Net$cape as well? by gpoul · · Score: 1

      I only partially agree with your analysis. You haven't decided to license program B under the GPL because the GPL made this decision for you.

      That's exactly why it is viral. - To show this I'll use your STD example:

      If you're so desperate to use the GPL library then you have waived your right to complain when you have to license your program B under the GPL.

      Did you get my argument?

      It basically comes down to your viewpoint:

      Fact is that the GPL forces its license onto other programs that just link with the GPLed library. - If you consider this to be "forced" or the "choice" because you had the choice to use another library really depends.

      But whatever way you see it, based on your analogy it is viral.

    16. Re:Why not $un or Net$cape as well? by nathanh · · Score: 2
      I only partially agree with your analysis. You haven't decided to license program B under the GPL because the GPL made this decision for you.

      No, I disagree. You are not forced to use the library therefore you are not forced to license your program under the GPL.

      That's exactly why it is viral. - To show this I'll use your STD example:

      If you're so desperate to use the GPL library then you have waived your right to complain when you have to license your program B under the GPL.

      Did you get my argument?

      Apparently I don't. I don't see anything in that statement that is viral. You willingly used the library and so you willingly chose to license program B under the GPL. There is nothing viral there. It is understood in advance what will happen.

      Fact is that the GPL forces its license onto other programs that just link with the GPLed library. - If you consider this to be "forced" or the "choice" because you had the choice to use another library really depends.

      It's not just a matter of linking. The program has to be written to use the library. This is why it's clearly a CHOICE being made by the author. It's not as if you finish the program and then discover that you're using the library. You had to intentionally choose to use the library before you can even begin coding! It's not as if calls to the GPL'd library magically insert themselves into the code without the author's permission!

      But whatever way you see it, based on your analogy it is viral.

      I disagree. In fact, what you say here is obviously ludicrous because there's no way I would provide an analogy that reinforced your argument instead of my own. Clearly there is confusion here: at least one of us is not understanding the other's argument.

      The closest I can come to understanding your argument is that you are claiming that because the GPL replicates it is therefore a virus. This is clearly nonsense because many things replicate and not all of them are "viral". To say otherwise would be to imply that genes are "viral" because they spread from parents to children, or that rumors are "viral" because they spread from person to person. This is a nonsensical meaning for the word "viral".

    17. Re:Why not $un or Net$cape as well? by gpoul · · Score: 1

      What do you think about this behavior? Is it still not considered "viral" by you?

      You have an exciting research project A released under the GPL. Company X wants to integrate it into their product B because it's a cool new feature and their customers would really like to use it. - Although, because of the GPL they can't, because if they integrate it, they'd have to release their whole product B under the GPL.

      e.g. project A could be TCP/IP and product B an OS.

  74. WRONG by mgkimsal2 · · Score: 2

    Partially - it depends on the product. Certaily the OEM version will have more restrictions because the OEM got a lower price. My storebought Win2k doesn't have the restrictions you're talking about - I can wipe it from a machine, sell the machine, and reinstall the Win2k disc on a new machine. I paid $190 for that version tho, which is probably much more than Compaq paid for a 98 OEM version. Lower price = more restrictions.

    1. Re:WRONG by DA-MAN · · Score: 2

      Try doing this with XP and see what happens when you try to activate it the second time around, or third, etc.

      That is the exact type of behavior M$ doesn't want people to be able to do. Prevents them from cashing in multiple times.

      --
      Can I get an eye poke?
      Dog House Forum
    2. Re:WRONG by clontzman · · Score: 2

      Right... you have to call MS and say, "I got a new computer." They then issue you a new code.

      They're trying to stop wholesale copying of their software, not stopping you from installing it on a machine you have a legal right to install it to.

      Raise your hand if you've made an illegal copy of Windows at some point in the last decade. That's why they're concerned.

  75. Here are my three favorite quotes.... by Sara+Chan · · Score: 2
    Photo #21 (top): Shared source "includes the benefits of open source".
    -> Not mentioning the benefit that (only) open source is free-as-in-beer.

    Photo #22 (bottom): "Open standards have become a point of confusion".
    -> So the correct thing to do is use Microsoft's proprietary standards?

    Photo #24 (bottom): "All software companies must carry significant legal overhead to protect against GPL infection".
    -> Otherwise all companies (not just software ones) must carry significant legal overhead to protect against BSA raids.


    "90% of politicians give the other 10% a bad reputation." --Henry Kissinger

    1. Re:Here are my three favorite quotes.... by cookd · · Score: 1

      Three cheers to taking things out of context! Good job, you get a cookie.

      Photo 21:
      You can't get much text onto a slide and keep it readable. The context can either be supplied by the person doing the presentation, or by informed guessing. You guessed, but it seems that you left the "informed" part out of it. Lets see where context needs to be supplied.

      "includes _________________ the benefits of open source."

      You seem to have placed "all of" in the blank, then ridiculed the result. In reality, you should be red in the face since it is your own addition that you are making fun of. More sensible additions that come to mind (although I have no way to know if they are correct, just they seem more sensible to me) include "some of" and ", as a compromise without all of the commercial disadvantages of open source, some of".

      Photo 22:
      Again, you are making fun of your own [lousy] interpretation of the caption. You jumped to a conclusion for Microsoft, effectively putting extra (stupid) words in MS's mouth, then once again, laughed at their stupidity. Perhaps you forget that MS does a LOT of work with open standards. But they most certainly do produce a lot of confusion, as can be seen by the way the "open" HTML standard has evolved over the years.

      --
      Time flies like an arrow. Fruit flies like a banana.
    2. Re:Here are my three favorite quotes.... by Anonymous Coward · · Score: 0
      "includes _________________ the benefits of open source."

      You seem to have placed "all of" in the blank, then ridiculed the result. In reality, you should be red in the face since it is your own addition that you are making fun of. More sensible additions that come to mind (although I have no way to know if they are correct, just they seem more sensible to me) include "some of" and ", as a compromise without all of the commercial disadvantages of open source, some of".

      In English, "all of" is the (only) correct interpretation.

      Perhaps English is not your native language. I'm hoping it's that and not that you are an MS astro-turfer.

  76. LATS by j_w_d · · Score: 2

    In fact, had many of the doubters looked through the slides they would have found an MS webpage URL on the last one. Checking this URL shows that it is indeed an MS page. Currently it redirects directly to a page on "shared source" and licensing that includes a pointer to a word doc covering MS's analysis of the GPL.

    The slides are a dumbed-down, idiot's version of the longer discussion and look to be developed for marketing presentations - probably directed toward upper management types considering the pros and cons of the issues. The slides present a view that the GPL is probably good for some (individuals, small developers) but bad for business and "innovation."

    One implication is that if code is GPL'd, companies can't grab it (e.g. government produced data and software) and then proceed to profit freely from releasing it through closed licensing schemes protected by the DMCA. Innovation seems in the context to consist of taking ideas and data from tax-dollar funded sources (academia and gov't) and passing it on to the customer, efectively making the user pay twice for the right to use the product. There is nothing revolutionary or self-evidently out character for MS in the slides except perhaps an unusually "liberal" view of OSS, and a blundering failure to appropriately present the "ecology" of innovation

    --
    ------ The only greater hazard to your liberty than n politicians is n+1 politicians.
    1. Re:LATS by gpoul · · Score: 1

      You talk about MS like shit and don't consider if their arguments might be valid but you still spread FUD yourself. pathetic.

    2. Re:LATS by j_w_d · · Score: 2

      Just how is it that I talked about MS like it was fecal material? Did you read what I wrote? I argued that there is nothing inconsistent about what appeared in those slides and MS own arguments, posted on their own pages, administered by their own sysadmins.

      They don't like GPL and go to great lengths to explain why. They are honest enough to delineate a fairly self serving attitude which you would hope for from a succesfull company. You may or may not agree with their argument. Personally, I consider it close to theft to take something paid for through taxes and use it to turn a profit without making the part paid for by public money available freely to the people who paid for it.

      They also state that the GPL has GOOD points for some, such as individuals developing stand alone projects and for some small companies.

      I don't happen to like their reasoning because it really isn't reasoning, just a motivating view point. It pretty much says they want to take work developed with tax dollars and sell it back to those self-same tax payers (you and I that is). Just how is that FUD, or do you even know what those letters stand for?

      --
      ------ The only greater hazard to your liberty than n politicians is n+1 politicians.
    3. Re:LATS by gpoul · · Score: 1

      Please point me to the slide where they stated that they want to be the sole owner of any academic work published in the US.

      AFAIK they just stated clearly and with a complete and reasonable argument why, in their opinion, publishing academic works under the GPL is not desirable.

      Did I miss anything?

  77. Microsoft and Sun are much more "viral" by g4dget · · Score: 5, Insightful
    If you look at Microsoft's and Sun's licenses for their source code, they are much worse than the GPL in terms of "infecting" you.

    You can look at the GPL and write your own proprietary implementation. But a lot of source code from companies like Microsoft and Sun software is licensed under agreements that "contaminate" you; that is, you can't develop a competing implementation because the presumption will be that you copied stuff from their source code. They also contain lots of other clauses that "infect you", like with an indefinite possibility of getting dragged into a law suit between Microsoft or Sun and a third party.

    1. Re:Microsoft and Sun are much more "viral" by eer · · Score: 1

      You're not far wrong - each of those licenses, commercial and GPL, have serious contaminating characteristics.

      It's the choice of the developer to impose those restrictions or not.

      It should be choice of the consumer (either end- or intermediary) whether they accept those restrictions or not.

      That's why Government financed development should be available WITHOUT contamination - via something like the BSD license, with fair attribution for the source of a derivative or integrating use.

    2. Re:Microsoft and Sun are much more "viral" by g4dget · · Score: 2
      That's why Government financed development should be available WITHOUT contamination - via something like the BSD license, with fair attribution for the source of a derivative or integrating use.

      I don't see why that logically follows. For example, just because the tax payer paid for a monument or city park doesn't mean that the government needs to open it for commercial activity. Governments used to pay for lots of non-commercial activities and create lots of non-commercial spaces.

      If we, the people, find it beneficial to our purpose to create BSD-licensed software with government funding, then we should. But there is certainly no obligation to do so. The only issue of fairness is that whatever license we choose should not favor one business over another.

    3. Re:Microsoft and Sun are much more "viral" by nathanh · · Score: 2
      That's why Government financed development should be available WITHOUT contamination - via something like the BSD license, with fair attribution for the source of a derivative or integrating use.

      I disagree. Why should corporations be given the right to profit from the code developed by the government without any obligation to return the favour? The GPL forces the corporations to make their changes public so that EVERYBODY can benefit.

      Remember, the government is supposed to be representatives of the PEOPLE. If the government wants the people to benefit then they should ensure that all government funded code is released under the GPL. Failure to do so means the politicians are not interested in representing the people, but only interested in lining the pockets of their rich buddies.

    4. Re:Microsoft and Sun are much more "viral" by eer · · Score: 1

      I think I'm saying that GPL DOES choose one business over another, whereas BSD does NOT. That's why I think BSD is closer to "the people's" license than GPL, which is more restrictive, and is designed to be antithetical to an economic business model rejected by its authors.

  78. It's a fake or he doesn't know his country's name by Anonymous Coward · · Score: 0

    Notice how the last slide says "Microsoft belux" instead of "Microsoft benelux"

  79. MOD PARENT UP by Anonymous Coward · · Score: 0

    Excellent point.

  80. We don't know this meeting took place at all by Anonymous Coward · · Score: 0

    After alll the announcement is in French.

  81. Re:Jesus Christ.... by Anonymous Coward · · Score: 0

    This statement is slashdot idiocy at its finest. GPL'd software isn't "free", it comes with strings attached. What's wrong with pointing that out?

    Do you ever point this out at the supermarket?

    Sign on the wall: "Buy one get one FREE!"

    You: YOU FOOL! YOU HYPOCREET! That roll of toilet paper isn't FREE! Look at the copyright notice! YOU CAN'T COPY THE PACKAGING OR THE DESIGN! Only BSD TOILET PAPER IS *TRULY* FREE!

    I guess when the person talking (RMS) is an unyielding whiner, everybody who disagrees with him has to turn into one too, even if they only disagree with a tiny little part of what he's saying.

  82. Re:My Thoughts (or ramblings) by bnenning · · Score: 2
    Personally I think something along the lines of the LGPL, or a modified BSD license which requires that the software being used and any modifications/enhancements to it be made available under the terms the original software was gotten under


    Our Linux production servers run heavily threaded Java apps. We end up with tons of processes thereby making top mostly unusable, and we had to write scripts to kill all the "threads" in a "process", but aside from those minor annoyances they work pretty well.

    --
    How to solve most of our problems: 1.Lots of nuclear plants. 2.Cure aging.
  83. A Study of Patterns in Freedom. by hackus · · Score: 3, Insightful

    Computers are cheap enough, and powerful enough for individuals to be thier own research and development shop, bypassing both Academics and Industry and directly publishing.

    THIS IS WHAT I BELIEVE TO BE the issue here with objections to the GPL.

    I don't think the powers that be, namely Microsoft, believe that the individual has the right to create software, manufacture it, and then NOT COMPETE on the same terms as Microsoft does.
    (i.e. freely distribute it.)

    They are trying to convince us that, only Academia, and Industry can be the focus of great ideas, and therefore they should only be the ones that decide how we are to value Intellectual Property legally.

    I think this is VERY similair believe it or not to what the RIAA is trying to fight.

    Think about this:

    A independant band, decides it wants to make music and sell it on the internet, with no distributor. (They build a web site and sell there own music through P2P technology.)

    No Recording studio. (i.e. they hook up a bunch of Mac OS X machines with Cubase and make there own recording studio...)

    Enter the RIAA. They see the internet as a possible tool for making them irrelevant, therefore they lobby and inact laws to make it illegal to use P2P technology to distribute Music over the internet.

    With such technology illegal, they can preserve thier tight hold on distribution, and insure no indepedant bands become to widely popular or compete with thier distribution network.

    ----With a twist

    Independant software developer, Linux Torvalds, builds and designs an Operating System kernel, and publishes it directly on the internet.

    (He decides he will distribute it for free and NOT sell it.)

    He has no research facility, he uses no Academic or Business computing facilities to make the software, instead, he uses and builds his own tools and buys the required hardware himself...(or uses his Dad's computer at home.)

    10 years later, after giving it away...enter Microsoft.

    Microsoft decides this software will destroy its distribution and control over the entire US software industry. They lobby to enact laws including the DMCA, to stop free software.

    They begin Marketing and FUD campaigns with there customers to educate them why it is better to pay for software, and to make illegal not to pay for software, and only software built through IP property sources such as Academia->Industry->User.

    More importantly, they say that this change toward OS will destroy the future economy. The facts in the internet boom do not bear this out by the way.

    I would like to remind people here, that the internet boom was due to ENTIRELY FREE SOFTWARE released under the GPL: (i.e. the orginal CERN HTTP server and Web browser...)

    Did the last 5 years destroy the US software industry? In 1998 for example, did you find it HARD to feed and clothe yourself because this software didn't go through Microsoft's slide presentation of ACADEMIA->INDUSTRY ?

    I am starting to see a pattern, all of it do to the internet. Which, I hope everyone can see here is ACCLERATING the pace of technology through:

    Sharing information for free. Free OS's accelerate the use of software, making it penetrate new markets much more quickly as there is no cost barrier.

    A good example of this is web server/web browser software. They are free, and they created a HUGE demand in hardware, short term anyway, both for servers and of course for workstations to run browsers adequately.

    I believe, information sharing for free generates FAR MORE revenue opportunity than through what Microsoft has proposed in those slides.

    However, that opportunity is now no longer centered strictly around the manufacturer of the software.

    I believe that we are at the tip of the iceberg here. I further believe that eventually, software ALL software will be so easy to produce due to tool advancements, better education that it will, like hardware become a commodity item.

    In the end, these slides represent the fear of the software industry. That is, that software, I mean software that drives the revenues or the control of government, will no longer be ONLY AVAILABLE through research institutions or industry.

    In fact, software will be very prevalent and easy to come by and cheap to come by, through the internet. For free or at very low cost.

    So what will happen 10 years from now?

    Here are my predictions, and I am gearing my company up for this NOW:

    1) Most if not all software, will be sold on a labor basis, not on a shrink wrap basis.

    That is, you hire someone to write your software because all of the software for doing business is basically free. (i.e. you use open source business apps which are standardized and since everyone uses them, it is easier to exchange documents with your vendors over the internet. If they don't have the software they can just download it.)

    2) Shrink wrap software will exist, but it will be for vertical niche's, and highly focused.
    (i.e. Mathematica for example).

    But, in the end, software that has built billion dollar industries, will become free. The reason is the internet allows people to organize, much as what a company does for profit, but at a much lower cost. Which is an interesting thought?

    What will happen to companies if the internet is ultimately allowed to evolve through the free use of information? Perhaps, dare I say, companies will become obsolete? After all, why pay a corporate board to organize people to produce information, like software, when the internet can do it much cheaper!

    Finally, gaming will be one of the last strongholds of mass market shrinkwrap software.

    Even there, you won't actually buy the software you will be provided the software with a monthly subscription which may include a internet connection with the game believe it or not.

    3) Linux WILL BE ON THE DESKTOP. In your server room, and well if it isn't...

    The sheer pricing pressures you will experience in trying to compete with your competitors who don't have those sorts of costs will compell you to load Linux or be pushed out of your own market.

    -Hack

    --
    Got Geometrodynamics? Awe, too hard to figure out? Too bad.
    1. Re:A Study of Patterns in Freedom. by mesocyclone · · Score: 2, Insightful

      Whew...

      I don't think the powers that be, namely Microsoft, believe that the individual has the right to create software, manufacture it, and then NOT COMPETE on the same terms as Microsoft does.
      (i.e. freely distribute it.)


      Nonsense. This is not at all what they are saying. You are totally missing their point.

      Microsoft is simply saying that products of government research should be free as in unrestricted as in all citizens should be able to use it the same way. If the government GPL's it's software, then it is *not free and unrestricted.* Software licenses *restrict* what you can do with software. That is one of their main purposes (the other one being liability disclaimers, etc). GPL is no different. It forces anyone using the software to GPL it.

      To me, having the government GPL'ing software is an abuse of taxpayer money. Why should my government, to which I pay too much in taxes, not permit me (or Microsoft) to improve its software, and make my own choices as to how to sell the added value.

      The GPL argument essentially assumes that either all people are coders, or all consumers are idiots. It assumes that improving software (which may just mean shrink-wrapping it and adding a nice installer) is valueless and that a company should not be able to keep exclusive the very work that that company paid for. It seeks to turn companies into charities... or it seeks to destroy the software business entirely (which, in fact, is what Stallman wants to do!).

      Like many Slashdotters, I make my living writing and selling software. My time is worth money, and if the way to get that money is to sell my software closed source, then that is what I am going to do. You have no right to have my (or Microsoft's) source code - I created it and it is mine! That also applies if my efforts went into creating improvements in internals, functions, packaging or just marketing government funded software!

      In some aspects, the previous poster is right... commodity software in some areas will eventually become free. But the reason is what he misses - the free software will exist because there is no value that can be added that requires paying people for their time. The Open Source movement has been a wonderful thing, for those people with the time and energy to contribute to it, and for the rest of us who use it. But it is not a highly general economic model.

      --

      The only good weather is bad weather.

    2. Re:A Study of Patterns in Freedom. by Chris+Johnson · · Score: 2
      Counterargument: Why should your government, to which you pay too much in taxes, permit anyone ever to take the fruits of this work and close it, taking it away from you? You paid for it, it needs to be under terms that guarantee access for you ALWAYS.

      Hence, GPL. Not even you can close access. After all you are only ONE citizen.

    3. Re:A Study of Patterns in Freedom. by 3am · · Score: 2

      Correct me if I'm wrong, Linus was at college when he decided to start his operating system. He had the resource of the University of Helsinki.

      He based it off of the already free operating system Minix. Which was written by Professor Tannenbaum while he was teaching a class in operating systems at the Free University of Amsterdam. He wrote it using the GNU tools, done by Stallman while he was in the AI group at MIT.

      Also, Mosaic came out of the NCSA, closely affiliated with the University of Illinois. The CERN HTTPd also came out of academia (neither of them is licenced under the GPL, though... I don't know how you got that idea.)

      I'm not really sure why you're choosing to bash academia with Microsoft, but the web and free software were born from and incubated in universities and research institutions. You couldn't have picked a _worse_ example to bash academic institutions.

      --

      A: None. The Universe spins the bulb, and the Zen master merely stays out of the way.
    4. Re:A Study of Patterns in Freedom. by mesocyclone · · Score: 2

      Counterargument: Why should your government, to which you pay too much in taxes, permit anyone ever to take the fruits of this work and close it, taking it away from you?

      This is not a counterargument to the issue of public domain. My government should *not* permit anyone to take the fruits of this work and close it (unless that was in the original contract and resulted in reduced costs to the government).

      But releasing it public domain means it is *not* closed. Nobody can close *it*.

      Sure, someone can take it, re-release it under a closed license, and *claim* they have closed it, but they haven't, because the original work is OBVIOUSLY STILL AVAILABLE FROM THE GOVERNMENT.

      Geez!

      --

      The only good weather is bad weather.

    5. Re:A Study of Patterns in Freedom. by hackus · · Score: 2

      You all have some good points.

      So let me clarify.

      With the current economic system, academic research is quickly becomming and adopting more and more commerical restrictions.

      Go into Barnes and Nobles, and if you want a book on MPI programming, or Software Engineering research, more and more of them have SHRINKWRAP covers on them that have a ton of license restrictions.

      Very very similair to Microsoft's, especially in the areas of practical applications. (Royalties, etc.)

      That is why I knocked academia because it is a VERY VERY troubling trend and because it is fundamentally contrary to what we know makes economic boom times happen in this industry.

      Again, I remind everyone here, the largest economic boom of the century, was caused by FREE INFORMATION with NO RESTRICTIONS. (CERN httpd server, Web Browser) It all happened in the information tech industry.

      Secondly, an individual pointed to the fact that Linus had Minix..etc and access to the Helsinki tech, to develop the Linux kernel in response to the fact I pointed out: People can setup thier own research and development facilties and bypass academic and industry.

      My response to that is Linus more than likely by the time he was 17 and before he got into college, possesed all the tools required to build an OS kernel. Simply by hacking himself and reading because information about computers was freely available. You could go into a book store in 1992-93 and buy books from Sybex on 486 mother board programming and Minix for that matter. The books by the way were not shrink wrapped, and the information inside them had no restrictions.

      I am not so sure from what I have read about Linux/Linus, that he only thought about Linux and only obtained the skills to build a kernel was at Helsinki Tech. However, OBVIOUSLY our learning institutions play apart in disemination of information. I am not saying that our learning institutions are bad, and we shouldn't use them.

      The only way to find out is to ask Linus. :-)

      I am disappointed that most of you don't see the connection though between Open Source and the Economics of free software, however.

      One person pointed out it isn't a general model for economics. I agree, partially. I agree you can't make money in the industry right now, from selling free software. :-)

      My point is though, that free software is redefining what we call a General Economic Model and I was hoping many of you would have picked up on the following:

      1) Free software creates demands in other areas. These demands end up paying for people to write the software in the first place.

      Example: Free web software drives the purchase of more servers and workstations to run free browser software. Many of the companies that make hardware, often employ Linux kernel/hardware programmers.

      2) Free software often creates communities of individuals on the net that make how we form companies right now to pay people, obsolete.

      Example: Mozilla, Linux Kernel.

      Now, obivously some of these people are employed by selling software....read on.

      The relationship is symbiotic. This is the beginning of change for our industry. Symbiotic relationships like the hardware above, and the support of existing companies though, is what I would call, a Transitional Model.

      They allow software to be free, yet, paid for.

      I woudl also like to point out, it is just as viable a model as the one pointed out in the slides, where software isn't free, and source code is hidden.

      Who is right here? Well, obviously, if your company ONLY makes software, or your business is almost 90% wrapped around the concept of closed source systems, your DAYS ARE NUMBERED.

      Why? Simply because you in the symbiotic relationship above, you can create software that drives demand, publish it, and have others expand it, without you paying for it. But in all likely hood, it will create more demand for your products.

      If your Microsoft, you have to do it all yourself, and pay people directly.

      Obviously, in contrast we are seeing hardware manufactures making Video Boards, and not investing any money into the software, just publishing the specs on the hardware and having 3rd party people write the drivers.

      ATI and the Weather channel are a good example of this.

      So, the model of how we pay for software is changing, and I am not in anyway suggesting that we, even now, don't pay for software.

      It is just that software isn't as valuable anymore, and the internet is changing how we pay for it, and how demand is created for more software in the first place.

      This is a threat to Microsoft, who cannot control the distribution or the manufacturing of software anymore, and they IMHO find themselves in the same boat as the RIAA.

      Totally irrelevant in the next 3-4 years if they don't reinvent how they make money.

      --hack

      --
      Got Geometrodynamics? Awe, too hard to figure out? Too bad.
    6. Re:A Study of Patterns in Freedom. by Dirtside · · Score: 2

      The U.S. Government can't hold copyrights on works it creates, so that issue is moot. If government employees themselves write some software as part of their work, the software will, by law, be public domain. Everyone agrees with this.

      But if the government contracts to have software written by a third-party entity (e.g. corporation, university), then that party can still have a copyright on the software, even if only the government is using it. The issue is, should such software be public domain, GPL, proprietary, etc.?

      Now, aside from that, your rant about how the GPL is bad for business is COMPLETELY MISSING THE DAMN POINT. The GPL is not suited for most business plans, because it prevents you from using the historical software business model (write it, keep code secret, sell multiple copies of the software). But there's absolutely no reason why the GPL and proprietary software can't coexist -- in fact, they do, rather nicely. People who demand that all software be free are idiots -- I (and you) have the right to write proprietary software if we feel like it. But people who insist that the GPL will change how the software industry works, and that this is a bad thing, are also idiots. The GPL flourishes because it helps support an alternative "software industry," one not driven by profit and consumer demand. De facto, there is a societal demand for this.

      Your entire rant comes off as, "The GPL scares me because it threatens what I do for a living!" Too fucking bad. History is littered with professions that were obsoleted by new technology and new social structures. Should we have limited computer development, to protect the jobs of telephone operators? Should we have limited automotive development, to protect the horse-and-buggy industry? Should we limit the Internet, to protect the music industry? (Hint: no, no, and hell fucking no). Nobody sane is claiming that they have a right to your code -- but you're an idiot if you think that the GPL can't coexist with closed-source models.

      The original post was saying that Microsoft attacks the GPL (and free software in general) because it's a threat to MS's business. It wasn't saying that all software should be GPL -- it was predicting that, eventually, most software will be GPL (or at least, some form of open source/free software). Don't get your panties in a bunch, you'll be able to stay proprietary for years to come -- but we better not hear you bitching when there's no more jobs for you.

      --
      "Destroy science and religion. Science would re-emerge exactly the same; but not religion." - Penn Jillette, paraphrased
    7. Re:A Study of Patterns in Freedom. by mesocyclone · · Score: 2

      I'm sorry, but YOU are not arguing against my point, you are arguing around it.

      My argument, and Microsoft's, is against those who would *force* the government into using GPL for all of its software. And don't kid yourself, if Congress wanted to, it could indeed make government software into GPL instead of public domain - you won't find anything in the US Constitution that prevents that, and the US isn't the only country in the world. My secondary discussion is an attempt to educate the Free Software utopians in the futility of their ultimate goals.

      If you read my postings more carefully (and I suggest you take a look at my more detailed my recent blog posting), you would see that this is not the simple issue you assert I am arguing.

      As far as "The GPL scares me because it threatens what I do for a living" - thanks for trolling by putting BS words into my mouth (NOT!)! I was simply pointing out (as you in fact do also) that the GPL, if used universally, simply won't work, and that forcing someone to give away their software is wrong. Oh, and I'm really not worried about this, because I expect that there will be proprietary software far into the future, as nobody has yet put forth any credible alternative scenario (short of global catastrophe or true AI). I'm not afraid - you just don't read carefully.

      If I have any fear for my profession, it is that cheap foreign labor will take my job - but as long as that happens through fair competition, there is nothing inherently wrong with that in spite of whatever impact it might have on me. And, of course, it isn't germain to this issue.

      Microsoft attacks GPL on several fronts. The main issue of interest has to do with attacks which actually affect laws - and this is where Microsoft is *defending* our freedoms, for their own private gain, of course. Is that such a hard concept.

      --

      The only good weather is bad weather.

    8. Re:A Study of Patterns in Freedom. by mesocyclone · · Score: 2

      I'm sorry, but YOU are not arguing against my point, you are arguing around it.
      (apologies... I hit submit when I meant to hit preview, and the previous response was incorrectly formatted - so here it is again):

      I'm sorry, but YOU are not arguing against my point, you are arguing around it.

      My argument, and Microsoft's, is against those who would *force* the government into using GPL for all of its software. And don't kid yourself, if Congress wanted to, it could indeed make government software into GPL instead of public domain - you won't find anything in the US Constitution that prevents that, and the US isn't the only country in the world. My secondary discussion is an attempt to educate the Free Software utopians in the futility of their ultimate goals.

      If you read my postings more carefully (and I suggest you take a look at my more detailed my recent blog posting [tinyvital.com]), you would see that this is not the simple issue you assert I am arguing.

      As far as "The GPL scares me because it threatens what I do for a living" - thanks for trolling by putting BS words into my mouth (NOT!)! I was simply pointing out (as you in fact do also) that the GPL, if used universally, simply won't work, and that forcing someone to give away their software is wrong. Oh, and I'm really not worried about this, because I expect that there will be proprietary software far into the future, as nobody has yet put forth any credible alternative scenario (short of global catastrophe or true AI). I'm not afraid - you just don't read carefully.

      If I have any fear for my profession, it is that cheap foreign labor will take my job - but as long as that happens through fair competition, there is nothing inherently wrong with that in spite of whatever impact it might have on me. And, of course, it isn't germain to this issue.

      Microsoft attacks GPL on several fronts. The main issue of interest has to do with attacks which actually affect laws - and this is where Microsoft is *defending* our freedoms, for their own private gain, of course. Is that such a hard concept.

      --

      The only good weather is bad weather.

    9. Re:A Study of Patterns in Freedom. by Chris+Johnson · · Score: 2
      Code rots. Any real programmer can tell you this. That's why the GPL is necessary in this context- it operates within the assumption that code is NOT ever finished, and will continue to adapt to new environments, the old code rotting and becoming useless.

      Quite relevant in an age where we have titanic multinational corporations not merely wishing but conniving with feral intensity hitherto unknown to bit-twiddlers to grab control of anything they can and reduce it to a proprietary yet indispensable status, and quite willing to do 'inefficient' things like code in time-bombs and checks for proprietary hooks in order to get their way, or even lobby governments. If Foo is public domain but Microsoft Foo is not, only works with other Microsoft Foo, and you need to have Microsoft Foo in order to file your Foo Returns with the government, the fact that the original Foo was public domain is of only academic interest since the one you have to actually use is closed as closed can be.

      Hence, the GPL is the only proper license for government work as only it guarantees continued access for ALL citizens, even to the point of bureaucratically cutting off some of your uglier options. :)

    10. Re:A Study of Patterns in Freedom. by mesocyclone · · Score: 2

      GPL does NOT guarantee continued access for all citizens any more than BSD or public domain does. The reason is that under GPL, a lot of code that would have gotten written will not be. It is really that simple.

      Public Domain guarantees continued access for all citizens to the products of the government. The citizens don't have any inherent rights to the products of private individuals, even if those individuals used government effort as a starting point.

      After all, most of our technology ultimately derives from government sponsored research. This is true in biotech, silicontech, spacetech, etc. Why do we want to pick out software as the only technology where we restrict the rights of what citizens can do with it?

      See here for a more detailed discussion.

      Oh, BTW, as a real programmer for over 35 years, I can tell you that *not all code rots.*

      --

      The only good weather is bad weather.

    11. Re:A Study of Patterns in Freedom. by Chris+Johnson · · Score: 2
      "GPL does NOT guarantee continued access for all citizens any more than BSD or public domain does. The reason is that under GPL, a lot of code that would have gotten written will not be. It is really that simple."

      Okay, so the GPL doesn't guarantee access to code for citizens because there might possibly exist code that hasn't been written yet? Or to put it another way, we should sacrifice the code that is in fact written for the sake of other code that doesn't actually exist?

      Too damn simple for me ;)

      And you've got a deft way of assuming all intellectual property must follow the rules of physical property. I don't agree that people have no right to code ideas that stem from other ideas developed on government budgets. I think the ideas need to remain available, and closing them would be harmful, and setting up a situation where government expense goes towards enabling corporations to close ideas is more harmful still. Code is not OBJECTS (well, except OOP ;) ). It is the expression of ideas in functional form and citizens are entitled to continued access to the ideas they pay for.

    12. Re:A Study of Patterns in Freedom. by Dirtside · · Score: 2
      My argument, and Microsoft's, is against those who would *force* the government into using GPL for all of its software. And don't kid yourself, if Congress wanted to, it could indeed make government software into GPL instead of public domain - you won't find anything in the US Constitution that prevents that, and the US isn't the only country in the world. My secondary discussion is an attempt to educate the Free Software utopians in the futility of their ultimate goals.
      And Congress could even pass a Constitutional amendment which would allow the government to retain copyright on works it produces. I think that's pretty unlikely, though; almost nobody has a desire for that. But nobody on /. is suggesting that the government's works should be copyrighted; the discussion is about works the government commissions from private organizations (like corporations or universities). You keep confusing those two issues, which are totally separate. Nobody, not even the "Free Software utopians" like the FSF, want the government's work to be anything but public domain. Some people (I can't speak for the FSF, as I don't know their official position) do, however, want the requirement put into law that any software written for the government by a private corporation, be GPL (or at least, open source, or somewhere else along the continuum between just-barely-free and public domain).
      If you read my postings more carefully (and I suggest you take a look at my more detailed my recent blog posting [tinyvital.com]), you would see that this is not the simple issue you assert I am arguing.
      You made it sound pretty simple in your grandparent post, so I responded to what you said there. Should I have responded to something you wrote elsewhere, that I didn't know about?
      As far as "The GPL scares me because it threatens what I do for a living" - thanks for trolling by putting BS words into my mouth (NOT!)!
      I was pointing out one of the themes of your post, which is why I said "comes off as" rather than "you said". Can't you tell the difference between that and actually claiming you said something you didn't?
      I was simply pointing out (as you in fact do also) that the GPL, if used universally, simply won't work, and that forcing someone to give away their software is wrong.
      No shit, Sherlock. But who was claiming that everything should be GPL, or that any private person should be forced to give away their software?
      Oh, and I'm really not worried about this, because I expect that there will be proprietary software far into the future, as nobody has yet put forth any credible alternative scenario (short of global catastrophe or true AI). I'm not afraid - you just don't read carefully.
      I too believe that there will be proprietary software far into the future; I should have said "ifwill disappear, which I don't. (I think it should disappear, but that's another story.)

      And I do read carefully; I just understand your motivations better than you do, it seems.

      If I have any fear for my profession, it is that cheap foreign labor will take my job - but as long as that happens through fair competition, there is nothing inherently wrong with that in spite of whatever impact it might have on me. And, of course, it isn't germain to this issue.
      Then it's a good thing you brought it up. :)
      Microsoft attacks GPL on several fronts. The main issue of interest has to do with attacks which actually affect laws - and this is where Microsoft is *defending* our freedoms, for their own private gain, of course. Is that such a hard concept.
      I understand the situation better than you do, since you can't separate the two issues of:
      1. Works produced by government employees are automatically in the public domain;
      2. Works produced under government contract by private corporations should either:
        1. Be entirely public domain
        2. Be licensed under the GPL
        3. Have the source available for public perusal, but only the corporation can sell/distribute the software
        4. Have the source available for review by certain government employees only
        5. Be entirely proprietary (the way it is now)
      This has nothing to do with Microsoft trying to defend our freedoms; it has to do with MS not wanting to share its source under terms which might not be to its ultimate benefit. Nobody (except a small, insane minority) is trying to force you to give away your software; so why do you keep acting like they are?
      --
      "Destroy science and religion. Science would re-emerge exactly the same; but not religion." - Penn Jillette, paraphrased
    13. Re:A Study of Patterns in Freedom. by mesocyclone · · Score: 2

      No, you don't sacrifice the code that is in fact written, because THAT CODE IS ALREADY FREE TO EVERYONE! It really is that damn simple!

      I do not assume that intellectual property must follow the rules of physical property. Rather, I reason that it must have some property value (and in the US the Constitution enshrines that principle - which is why it calls for the establishment of Patents and Copyrights - so don't argue with me - amend the constitution).

      Code, for the most part, is not ideas. It is a tedious collection of detailed insructions to a machine. In that sense, it is not a mathematical idea (the concept of which prevented code patents for many years) but rather an expression of an algorithm - which is most similar to music or writing.

      And again, you seem to be assuming the allowing public domain software to be used in proprietary, closed source system, to cause that public domain software to vanish. That is UTTER NONSENSE. You, yourself, have the right to take very piece of public domain software ever written and to be written to be released under a GPL issued by you, if that would make you feel better!

      Admit it! Your real objection is that you don't like not having access to source code (neither do I). The rest of your argument (where it isn't just totally contrary to the *facts*) is mostly a rationalization for that view.

      --

      The only good weather is bad weather.

    14. Re:A Study of Patterns in Freedom. by mesocyclone · · Score: 2

      And Congress could even pass a Constitutional amendment which would allow the government to retain copyright on works it produces

      Not true. Congress does not have the power to amend the Constitution.

      Actually, I don't know how you speak for all of Slashdot or FSF about the difference between government produced and government commissioned software. Some proof would be interesting.

      But what is the theoretical difference of whether the software came from a government employee, or someone or some organization that produced it on behalf of the government? As far as I can tell, the only difference is that the government can negotiate a reduced cost in return for changes in the intellectual property value of the software (I once worked on a program where exactly that happened).

      So do you disapprove of the government saving taxpayer money if it results in less free software? If so, why?

      Your #2 point is the very first time that this issue has been raised in this thread. So please stop attacking me for arguing against a wider issue. Now that *you* have made clear the narrow range of your issue, I have responded (above) to that. So can we discuss that personally and stop psychoanalyzing my motices?

      --

      The only good weather is bad weather.

    15. Re:A Study of Patterns in Freedom. by Dirtside · · Score: 2
      Not true. Congress does not have the power to amend the Constitution.
      I was condensing the following, although I suppose I should have chosen a better word than "pass":
      The Congress, whenever two thirds of both Houses shall deem it necessary, shall propose Amendments to this Constitution, or, on the Application of the Legislatures of two thirds of the several States, shall call a Convention for proposing Amendments, which, in either Case, shall be valid to all Intents and Purposes, as part of this Constitution, when ratified by the Legislatures of three fourths of the several States, or by Conventions in three fourths thereof, as the one or the other Mode of Ratification may be proposed by the Congress; Provided that no Amendment which may be made prior to the Year One thousand eight hundred and eight shall in any Manner affect the first and fourth Clauses in the Ninth Section of the first Article; and that no State, without its Consent, shall be deprived of its equal Suffrage in the Senate.

      U.S. Constitution, Article V

      Nonetheless, I'm fully aware of how Constitutional amendments get proposed and passed.
      Actually, I don't know how you speak for all of Slashdot or FSF about the difference between government produced and government commissioned software. Some proof would be interesting.
      What? That makes no sense. The difference between government-produced software and software produced under goverment contract is obvious; it has nothing to do with what /. or the FSF think, or you, or me for that matter.

      Software produced by the government means software that is written by actual employees of the federal government, during work hours, as part of their job. Such software cannot be copyrighted; it is public domain.

      Software produced under contract to the government is software that is written by people who are not federal goverment employees, but are rather (for example) Microsoft or IBM employees. Such software is subject to normal copyright law, at least as the laws currently stand. It's possible that the contract could specify that the software in question be released as GPL or public domain, but there's no laws requiring that that be the case.

      /. and the FSF's position on the latter issue have no bearing on the actual material difference between the issues. Now it seems possible that this isn't what you meant, in which case you phrased the above-quoted very poorly.

      But what is the theoretical difference of whether the software came from a government employee, or someone or some organization that produced it on behalf of the government? As far as I can tell, the only difference is that the government can negotiate a reduced cost in return for changes in the intellectual property value of the software (I once worked on a program where exactly that happened).
      Already explained above.
      So do you disapprove of the government saving taxpayer money if it results in less free software? If so, why?
      It would be nice if it were that simple of an issue, weren't it? A convenient balance scale with free software on one side, and money on the other. But, unfortunately, it isn't that easy.

      When it comes to commissioned software (software written by a third party, under contract to the government), there are three main factors to take into account when deciding whether some particular software is a good choice for the government to use:

      1. Monetary costs (including up-front cost, ongoing maintenance and support costs, etc.);
      2. The license the software is provided under (public domain, BSD, GPL, proprietary, etc.);
      3. The quality of the software (i.e. how good it is at doing what it's supposed to do).
      #1 and #3 are obvious; if it costs a trillion dollars, it's probably not worth buying (even if it's of unparalleled quality). If it sucks, it's probably not worth buying (even if it's dirt-cheap). But the license is important, as well. If the source code is not provided to the government, then how is the government (and those it serves -- i.e., the people) supposed to know that it's properly doing what it's supposed to be doing? Thus, some people argue that such software should at the very least have its source available for inspection, either by government employees who would not be allowed to divulge the contents of the source they read, or by members of the public, or whatever. I'm not going into that issue; I'm just bringing it up because it's the only real issue that's even similar to the one you keep claiming you're arguing about.
      So please stop attacking me for arguing against a wider issue.
      What you're arguing against isn't an issue. Nobody's demanding that all software be GPL, or that you should be forced to give your software away for free. (Nobody modded 3+, anyway.) So why do you keep demanding that you have a right to your software, when nobody's saying that you don't?
      --
      "Destroy science and religion. Science would re-emerge exactly the same; but not religion." - Penn Jillette, paraphrased
    16. Re:A Study of Patterns in Freedom. by mesocyclone · · Score: 2

      I'm only going to beat a small amount of this dead horse.

      LOTS of people on slashdot have argued that all software should be GPL'ed, and that is indeed the ideology of a lot of the Free Software movement. I normally read Slashdot with a filter of 4, and I see that point of view every time anything close to the issue comes up! If this thread doesn't have any (and I'm not gonna bother to look), it is because they all went beddy-bye early.

      Software produced by the government means software that is written by actual employees of the federal government, during work hours, as part of their job. Such software cannot be copyrighted; it is public domain. [cornell.edu]


      Your quote actually establishes my point precisely. You are quoting US Code, which indeed is frequently modified by Congress (in fact, that is what we mean by passing a law!). Thus such software could very easily be released GPL (or proprietary or anything else) if Congress were pressured to do so.

      And as far as Congress amending the constitution, again, THEY CANNOT DO SO. They can propose an amendment (your quote again). Beyond that, it is another process (thank goodness!).

      Thus, some people argue that such software should at the very least have its source available for inspection, either by government employees who would not be allowed to divulge the contents of the source they read, or by members of the public, or whatever. I'm not going into that issue;

      Yes, now that we are getting into a tiny little piece of the idea space under discussion, you are right that some people think that the government should divulge all source that they commission. Those people are *seriously* misguided.(Do they really think that all NSA classified code is coded by government employees? How about the guidance code for the Patriot PAC-3 missile. Most highly secret code used by the government is produced by contractors - a couple of whom I worked for in the distant past - and obviously that code shouldn't be released to the public domain! Security through obscurity in fact is very important in these sorts of cases. If you don't know the exact algorithms used in weapons system, it is much harder to spoof or jam them, for example.

      So we have moved into an even tinier piece... contracted code (not written by government employees) who are not writing classified stuff. Do you really think that all the posts on Slashdot about this issue relate only to that?

      Even in that area, I will only argue that the source should be public domain, not GPL. In other words, most of the arguments of mine that you took such offense too do not relate to the subset of the tiny subset of discussion space in this thread!

      Puleez

      --

      The only good weather is bad weather.

    17. Re:A Study of Patterns in Freedom. by Dirtside · · Score: 2
      LOTS of people on slashdot have argued that all software should be GPL'ed and that is indeed the ideology of a lot of the Free Software movement. I normally read Slashdot with a filter of 4, and I see that point of view every time anything close to the issue comes up!
      References, please. I've been reading /. for 3.5 years and have seen almost no evidence of this. Maybe their posts just don't get modded to 3, which is where I read. The arguments I have seen that are similar to this, usually say that the world would be better if all software was GPL, but they rarely, if ever, insist that all existing or future software should be forcibly made GPL.
      Your quote actually establishes my point precisely. You are quoting US Code, which indeed is frequently modified by Congress (in fact, that is what we mean by passing a law!). Thus such software could very easily be released GPL (or proprietary or anything else) if Congress were pressured to do so.
      Once again, I am familiar with how Congress passes laws. I know what the U.S. Code is and how Congress goes about modifying it. Yes, you're right, Congress could pass a law changing 17 USC 106, but it seems rather unlikely.
      And as far as Congress amending the constitution, again, THEY CANNOT DO SO. They can propose an amendment (your quote again). Beyond that, it is another process (thank goodness!).
      I addressed this directly in the grandparent; it was a poor choice of words, nothing more. Why do you keep harping on it?
      Yes, now that we are getting into a tiny little piece of the idea space under discussion, you are right that some people think that the government should divulge all source that they commission. Those people are *seriously* misguided.(Do they really think that all NSA classified code is coded by government employees? How about the guidance code for the Patriot PAC-3 missile. Most highly secret code used by the government is produced by contractors - a couple of whom I worked for in the distant past - and obviously that code shouldn't be released to the public domain! Security through obscurity in fact is very important in these sorts of cases. If you don't know the exact algorithms used in weapons system, it is much harder to spoof or jam them, for example.
      No, obviously the circumstances will dictate who should be allowed access to the code. Nobody sane claims that all contracted software should be available to the public; but to claim that this is a tiny area of discussion is ludicrous. Unclassified software use by government agencies absolutely dwarfs the amount used by classified agencies. Think about every payroll system, social services management software, database management software, etc. the government uses. Now multiply it by 50, for all the state goverments. And then multiply by another 100, for all the county and city governments. Those don't need to be classified. Even still, I was pointing out a range of possibilities for how the source could be available; I never said that any one of them should be used in particular, or in every instance.

      Don't be dense. Do you REALLY think I want military secrets declassified for any random Joe to read? Of course not! Only a tiny number of select, authorized government agents would ever have access to military software source produced by a contract corporation (e.g. Lockheed). But someone in the government has to have access to it -- otherwise, how are they to know that it actually does what it says?

      So we have moved into an even tinier piece... contracted code (not written by government employees) who are not writing classified stuff. Do you really think that all the posts on Slashdot about this issue relate only to that?
      Did I ever claim they do? No. The issue came up, and we're discussing it, except that you think it's unimportant, and I'm forcefully and repeatedly whacking you with a clue-by-four.
      Even in that area, I will only argue that the source should be public domain, not GPL. In other words, most of the arguments of mine that you took such offense too do not relate to the subset of the tiny subset of discussion space in this thread!
      I took offense to your entire original post. Anyway, you're the one who spends the bulk of your posts claiming that this isn't an important issue, and ignoring most of my other points. Naturally, I respond to what you argue with. What should I do, argue about the things we agree on?
      --
      "Destroy science and religion. Science would re-emerge exactly the same; but not religion." - Penn Jillette, paraphrased
    18. Re:A Study of Patterns in Freedom. by mesocyclone · · Score: 2

      Well, I do like the phrase "clue-by-four."

      Other than that... this is a waste of time.

      --

      The only good weather is bad weather.

  84. They Make a Point by cslarson · · Score: 1

    I agree. Let's not kid ourselves into thinking that the GPL equates to public domain. Maybe we aren't, but the slides make the point that our government should not be making developing products under the GPL. I like the GPL though. I think it's great that programmers would say, "if you think what i have done has value enough to use it, and you mod it, then damn it, let me see what you did." It's not only fair, but sensible, it seems to me.

    Now that I think about it though, good debates could be had over whether the government should really be using the GPL. Its not really public domain in nature, but does it better benefit society as a whole. I mean look at what has happenned with linux/oss and the community. it's a thing of beauty. i can't wait to see what happens when this becomes a bigger issue (which i think it will in a short while when desktop/linux becomes just a little easier - let's not go there again).

    On the other hand it is crazy to say that the government shouldn't develop ontop of the GPL...isn't it...it is, right?

  85. MOD PARENT UP!! by Anonymous Coward · · Score: 0

    He/she makes some good points!

    1. Re:MOD PARENT UP!! by Anonymous Coward · · Score: 0

      He/she makes some good points!

      A she in /.? Keep dreaming dude :)

  86. Re:More M$ Sh**t by jumbie · · Score: 0

    why do you bother? you've posted 4 times in 6 months and frankly IMNSHO all your comments are bland and pointless

    don't worry only you will ever see this message (probably in 3 months when you next log in) no need to feel shame

  87. nonsense by martin-boundary · · Score: 1
    Research results are *already* freely available to all. What you do is read the published research reports and papers. They are designed to disclose in human readable format exactly those parts of the design which are out of the ordinary and worth discussing, and skip the boring details. It's more cost effective and efficient to read the papers than to scour the cryptic pages of program code.

    So if you're a company and you want to use a research result, get a knowledgeable employee to read the papers and write your own version in-house. No licensing problems (except maybe for patents, that's another kettle of fish). Repackaging existing research code by slapping a company logo on it and selling it to the public *is* stealing from taxpayers.

  88. it's a strawman by martin-boundary · · Score: 1
    Primary research results like TCP/IP are always freely available. Just read the research reports, published papers, RFCs. Whether those things are implemented by the researchers as GPL or not is irrelevant. Microsoft and the "software industry" is welcome to use the products of research like everybody else: by reading the papers and building their own with no strings attached.

    However, if they want to take the test code the researchers built based on the papers they wrote, and slap a company logo on it and resell it to consumers, who are also taxpayers, then that *is* stealing. Why should consumers pay twice for the research they funded.

    Let Microsoft have an employee read the research papers and build their own code. Then I have no problem if they want to sell it. Or else, if they do use code I and others funded, they can't sell it back to me piecemeal. Give me the source, which is as much mine as theirs to begin with.

    1. Re:it's a strawman by mesocyclone · · Score: 2

      However, if they want to take the test code the researchers built based on the papers they wrote, and slap a company logo on it and resell it to consumers, who are also taxpayers, then that *is* stealing.

      No, it is not stealing. You also can take the test code and use it for free... or you can put it into a product. If you pay Microsoft for it, it is because you are too lazy (or more likely, too smart) to spend your time adapting the research code for your own use.

      Microsoft in this case would add value. If they didn't, NOBODY WOULD PAY FOR THE SOFTWARE!

      Stealing would be taking the code and hiding it so nobody else could use it!

      --

      The only good weather is bad weather.

    2. Re:it's a strawman by spitzak · · Score: 2

      The problem is that MicroSoft might "add value" by doing what everybody here calls "embrace and extend". I personally feel this is done accidentally more often than it is done for sinister purposes, but the end result is the same.

    3. Re:it's a strawman by mesocyclone · · Score: 3, Insightful

      I argue that this is itself a strawman argument. It matters not what Microsoft does with the government funded software - what counts is what *everyone* is allowed to do with that software.

      The fact that Microsoft is a monopoly is the only reason that they can play a lot of their predatory games. One could argue that Microsoft in particular should be denied the use of taxpayer funded software as a penalty for monopolistic abuses, or one could argument that whatever use they do make of it should be monitored for monopoly abuses. But this applies only to a monopoly, which Microsoft happens to be.

      In fact, it is unfortunate that Microsoft's name is used in this argument. The licensing of government software affects anyone who may want to use it, not just one company. Anti-Microsoft arguments, however valid, really add nothing to the debate over what is the best license to use for government subsidized software.

      --

      The only good weather is bad weather.

    4. Re:it's a strawman by spitzak · · Score: 2
      Pretty true. MicroSoft's monopoly is really why "extend" works to control the market. If there were a bunch of companies that took the government-generated code and made slightly different versions that were incompatable, I expect these incompatabilities would be treated as bugs and fixed over time, and most users would say "don't rely on that, it does not match the standard" and not use these bugs. In the cases where the "bug" is really a useful feature the original company has an incentive to release some form of code because other companies would copy the idea anyway and possibly do it slightly differently and incompatable, the version where the code is available would always end up being the standard in the end, not necessarily the best or first version.

      However with MicroSoft it usually means that their "bugs" *become* the standard, making the original free code useless because it no longer is the standard.

      I however have some problems with making rules that only apply to MicroSoft, or only apply to a "convicted monopoly". The next monopoly could easily use the same techniques until they get convicted. Also the monopoly is easily powerful enough to make shell companies or otherwise evade the rules. I would prefer global rules that are fair, allow competition, but prevent MicroSoft style lock in. It is hard to figure out such rules. One idea I like is that a requirement be made for all government purchases that all communication protocols and storage formats used by the purchased product must include sample public-domain source code provided to read/write/communicate with the product. Companies can still do clever things inside their products, or even have different (ie better & faster) secret implementations of the interface code, but this would avoid the lock-in problem. Notice that I think public domain is better than GPL in this case. It may be that even Linux will need a few parts changed to public domain for this, but it would all be for the best in the end.

    5. Re:it's a strawman by mesocyclone · · Score: 2

      All excellent points. When you can devise rules (as you did) to achieve anti-monopolistic results in a pro-active manner, you have done well!

      However, in the case of Microsoft, that didn't happen. In fact, I have often argued that Microsoft owns a natural monopoly (using the economic sense of the term) and thus a desktop operating system monopoly would have originated with or without Microsoft. However, once such a monopoly has arisen, one needs to take measures to minimize the damage that may result as the company uses monopoly rents to unfairly compete in other markets.

      BTW... I wrote a longer (and more trollish) discussion of the Free Software movement and put it on my blog for those who are interested.

      --

      The only good weather is bad weather.

    6. Re:it's a strawman by spitzak · · Score: 2

      I agree that there would almost certainly be some software monopoly even if MicroSoft had not succeeded. Despite all the bitching about him, I suspect we are pretty lucky we got Bill Gates. Some other people (Steve Jobs, perhaps Scott McNealy of Sun) may have been much worse. Other ones that seemed likely were IBM or ATT (they may have been stopped by the previous monopoly convictions), Lotus, Digital Research (makers of CP/M), Borland (which once controlled the compilers). I also think the Unix market was sabotaged by other vendors that were fearful of Sun becoming the monopoly, and they did not realize the growing threat from MicroSoft.

  89. there is a difference... by bani · · Score: 2

    m$ willingly and knowingly violated federal law, violated court orders, and lied under oath.

    netscape and sun didn't.

    that's why m$ deservingly gets the label, while other companies (who haven't violated the law) dont'.

  90. They only show one side. by miffo.swe · · Score: 2

    Why does people always miss out half of the equation when talking about the GPL in comercial surroundings? The GPL doesnt help people selling the same product multiple times or to take somebody elses work and make money of it. It doesnt help someone to take a project, twist it and screw the initial developers (think kerberos etc.). The GPL dont ease up the software companies ongoing efforts to screw people up with endless upgrades and "almost good, next version will work, i promise" kind of software.

    The GPL is constucted to benefit users and not the vendors that want to sell you the same product with a new clownsuit ten times. All people and companies and governments use software, thats a pretty much established fact. They dont do software and they dont benefit from paying more for things than necessary.

    As i see it software buisiness as it looks today is like the spinneries in england in the 1800. It is going to be raplaced sooner or later anyway. Todays constant upgrades and paid servicepacks is an artificial market not based on realworld logic.

    Software companies like IBM, RedHat, Sun etc who provide services and really do something for what you pay is the future. Software compenies like Microsoft just sell the same things as many times possible and preferably without even having developed it themselves. They are moving themselves into a corner where they dont research and invent things but is merely a proxy for other peoples ideas that they "borrow". Now they even want government funded code for free to be able to sell it to the people who paid for it, the taxpayers. The GPL fosters interopability and adherence to standards because you cant hide alterations in code you have to show openly. The BSD license and others lets you screw the authors royally up the poopchute.

    Overall the GPL license the license that benefit users of software the most. As a nice side effect it fosters adherance to standards witch in turn lets more people into the race even if they dont use or make GPL code themselves.

    The only looser of the GPL is those who work once and want to sell the product over and over.

    --
    HTTP/1.1 400
  91. moron marketeering gaffes buy liesense peddlers by Anonymous Coward · · Score: 0

    a few massturds of deception action figure "slides" we found. talk about fooling some of the people......

    perhaps ucann see why the payper liesense, stock markup, hostage ransom scam FUDgePeddlers of the ill eagle kingdumb, MuSt delete the non-compliaNT hobbyists, buy nitefall.

  92. Right on, my friend. by TheOnlyCoolTim · · Score: 2

    You are going to and have taken so much shit in response to this post, but you are right.

    Both RMS-zealot "Free Software" (free as in communism?) and Microsoft's restrictive EULAs are against freedoms. The whole idea of licenses in general is rather rotten, I think, but there's still tons of licenses that are more free than the GPL.

    Tim

    --
    Omnia vestra castrorum habetur nobis.
  93. Re:Jesus Christ.... by TheOnlyCoolTim · · Score: 2

    There is a damn good reason for them to dislike the GPL, because it would destroy their entire business model and radically change, if not destroy, their entire business model.

    Most of the ideas in that presentation were rather sound.

    Tim

    --
    Omnia vestra castrorum habetur nobis.
  94. of course you can use it by martin-boundary · · Score: 1
    If it's published in a journal, or officially published on some university's tech report server, then you can do as you please with the information you learn reading these documents.

    Now sometimes, there are patents associated with some of those results, which is the prerogative of the University to apply for if they want. Nothing new here. If it's patented, follow the usual licensing channels. Should it be patented? Personally, if it's taxpayer funded research, I think it shouldn't. But that's another topic.

    But to suggest that what you learn from reading research papers is IP encumbered is false. The paper has author copyright, but that applies only to the wording, ie as a literary work, not the concepts discussed.

    The only valid criticism is that it may actually take a while to duplicate the code in-house for a company, but that's nothing compared to duplicating the full research that went into the idea. It's a production cost like any other.

    1. Re:of course you can use it by cookd · · Score: 1

      Yeah, but what I'm saying is that the journals can never have enough detail to be worth anything when it comes to computer science stuff (small advances, nifty algorithms - yes, but important new technologies such as TCP/IP - no). So Academia(TM) releases some sample code. If Academia GPLs the code, then companies are going to have to clean-room their implementation to avoid the possibility of lawsuits. If Academia puts a BSD license on it, then the companies can look at the code freely to understand the algorithms involved, even if they choose not to use the code directly.

      (By the way, everybody keeps talking about BSD code in NT. First, that is unsubstantiated. Second, if true, it is in no way wrong. Third, according to my contacts, my understanding is that "if that was ever true, it is certainly not true in currently shipping code.")

      --
      Time flies like an arrow. Fruit flies like a banana.
  95. Another interesting slide by gmhowell · · Score: 1

    Personally, I liked slide 223:

    "The GPL is fine for the individual to choose, but bad for the industry."

    So, IOW, Microsoft admits that the GPL is good for everyone but Microsoft. Imagine that.

    --
    Jesus was all right but his disciples were thick and ordinary. -John Lennon
  96. Thanks for proving my point. by Anonymous Coward · · Score: 0

    While I appreciate your more thought-out comments regarding the actual issue of open vs. closed source, your first paragraph simply proves my point. Anyone can link to a page and somewhat summarize its comments. Don't get me wrong - I'm certainly not saying that MSFT didn't create these slides, I'm just knocking those people who simply assume MSFT created them because it allows them to begin an attack against the so-called Evil Empire.

  97. Well now by Anonymous Coward · · Score: 0

    Niggers be niggers, no matter what they choose to dress-up as. Mickeysoft can only suck SO hard, then they blow!

  98. Microsoft Misses the Point - Again by iCEBaLM · · Score: 2

    Slide "0223r" states the GPL is "For protecting the individual programmer" and "Against ownership or commercialization of software".

    The GPL is in place to PROTECT THE END USER so that, as the fable goes, he can get working printer drivers, etc. It's not to protect the programmer at all but the user!

    Also, if the GPL is so much against commercialization of software why are so many companies using linux and/or GPL'd software like Apple (GCC), TiVo (Linux), etc?

    -- iCEBaLM

  99. Clipart by TheCrimsonUnbeliever · · Score: 1

    If the slides are Microsoft then that means PowerPoint - And if you tell someone to use PowerPoint - That leads to the use of ClipArt

  100. What about not attacking OSS? by asobala · · Score: 1

    In Halloween VII, assuming it's genuine, MS decided not to attach the OSS process but rather make economic arguments for Windows. Um.

    1. Re:What about not attacking OSS? by kcb93x · · Score: 1

      And they realized they'd lose, so they did this. They went and attacked the GPL anyway. Because they know they can't confuse most of America into thinking that buying something is cheaper than getting something for free. (Support costs notwithstanding)

      --
      There are 4 boxes to use in the defense of liberty: soap, ballot, jury, ammo. Use in that order. Starting now.
  101. Re:Jesus Christ.... by mlyle · · Score: 1

    I also thought it might destroy their business model; or perhaps completely destroy their business model.

  102. The "GPL is viral" myth by yuri+benjamin · · Score: 2, Informative

    Myth - If you use and modify GPL code inhouse, you have to give away all your code.

    Truth - If you use and modify GPL code inhouse, you are free to keep it inhouse.
    GPL only comes into effect if you want to distribute your GPL based code outside your organisation.

    --
    You make the mistake of thinking you can educate the fundamental stupidity out of people. You can't.
    1. Re:The "GPL is viral" myth by phel666 · · Score: 1

      I think what is meant by viral is that if it is distributed, then it remains "free".

      --
      -- f00!
    2. Re:The "GPL is viral" myth by gpoul · · Score: 1

      True, but IMHO this whole discussion is about academic software and this is basically written to be distributed, isn't it?

    3. Re:The "GPL is viral" myth by yuri+benjamin · · Score: 1

      Yes, the academic community who write the software do so to distribute it. But not every company that uses it is into re-distribution.

      If a company does want to re-distribute, under GPL they can do so gratis if they also share their own mods, or they can negotiate a fee with the research institute if they want to distribute binary only products.

      I.e. if you get it gratis, you gotta share. If you don't want to share, you can still negotiate non-GPL terms with the tax-funded organisation that did the ground work for you.

      The way I see it, if Foo-Corp wants to use gratis-ware and make money from it, they should pay the developers instead of letting the tax-payer pay the developers.

      GPL does not preclude to original developer from offering different licence terms as an alternative.

      --
      You make the mistake of thinking you can educate the fundamental stupidity out of people. You can't.
    4. Re:The "GPL is viral" myth by gpoul · · Score: 0, Troll

      Because the GPL is "viral" it is just the wrong license to publish academic works under because of the following characteristic:

      - You can't integrate it with a commercial product to further advance innovation. (In fact you can't even look at the source and write your own implementation because you might be subject to the GPL's "viral" effects then)

      I think it's one thing to share your modifications and derivative works at will, but it is IMHO not okay to force someone to release a whole product into which you integrated it.

      btw: As surprising as it may be, Microsoft also pays taxes and therefore funds academic projects.

  103. Bogus examples by Animats · · Score: 2
    The two examples, "TCP/IP" and "NSA Secure Linux" are bogus. TCP/IP is an open specification, not a code base. Even in the earliest days, there were multiple implementations. Some commercial systems did copy the Berkeley stack, because its licensing allowed that. Others copied the K9AQ stack, developed by a radio ham. The licensing issues were complex; Berkeley UNIX was a modification to AT&T UNIX, and you had to be licensed by AT&T. (FreeBSD came much later.) But none of the early stuff was GPL.

    As for NSA Secure Linux, which is GPL, it's a set of relatively minor mods to Linux. There's no new technology that you can't use if you reimplement it, and the code is useless outside the Linux context anyway. The whole purpose of NSA Secure Linux is to give people something to try that implements a mandatory security model, so that they can find out what it's like and figure out how to live with a tight security system. (There's no "root". What does that mean to the sysadmin?) It's the same technology NSA has been trying to get adopted for twenty years. Yet Microsoft has lobbied heavily to stop NSA from doing further work in this area. That could be construed as weakening America's defenses in time of war.

  104. FUCK by TheOnlyCoolTim · · Score: 2

    I meant "completely destroy their industry" or something like that.

    Shit and perdition!

    Tim

    --
    Omnia vestra castrorum habetur nobis.
  105. makes money off of computers? by oliverthered · · Score: 2

    I always though that most computer companies,
    IBM, Solaris &co made most money from support, not software of hardware sales.

    Few companies are and where in the pure software game.

    Install[piece of crap] shield is a good example.
    You more-or-less have to go on a training course to use it, coes the documentations crap, it's a freek piece of software etc...
    (I'm not sure why people ever used install shield to start with)

    --
    thank God the internet isn't a human right.
  106. This is laughable! by Eric+Damron · · Score: 1, Troll

    I don't know if this shit came from Microsoft or not but one of the statements:

    "Primary research results placed under the GPL are precluded from commercial use *TCP/IP example ..."

    I didn't realize that TCP/IP was GPL'd but the laughable part is that this suggests that we would all be better off if the TCP/IP protocol were proprietary. Can you imagine if Microsoft controlled this protocol?!

    --
    The race isn't always to the swift... but that's the way to bet!
  107. Re:Jesus Christ.... by Anonymous Coward · · Score: 0

    GPL'd software isn't "free", it comes with strings attached.

    It most certainly is "free". Wether it has "strings attached" or not is irrelevant.

    If you're on a bus, and someone walks up to another person and asks if the seat beside them is free, would you call them an "idiot" and lash into a tirade about how the seat isn't "free" because it's part of the bus, and that they can't take it and put it in their basement?

    Open your mind a little bit.

    Even though there are "strings attached", it's still "free".

  108. it's hard to get presentations like that. by twitter · · Score: 2
    These jpgs were obviously taken at great risk in some kind of M$ presentation. We are lucky that they did not perrish with one or two of those risk taker's jobs.

    Seriously, this demonstrates a larger trust issue. No one inside of M$ will take credit for that kind of thing and no one will believe anyone outside of M$ when they pubish that sort of thing. Why is this true? Because Microsoft is dishonest, that's why. How simple.

    --

    Friends don't help friends install M$ junk.

    1. Re:it's hard to get presentations like that. by jbolden · · Score: 3, Insightful

      I've read Microsoft's on the record comments and these don't look any different. Craig Mundie frequently spoke of "Sustainable Innovation" ( for example ) and the references to viral are common and Microsoft is no exception.

      Frankly I didn't find anything in those slides that is any different from what they openly state as their company's position towards GPL. Which means if it is a fake its a fake which accurately represents Microsoft's public position. I don't see why they have any reason to deny it if those slides were their's.

  109. Re:Jesus Christ.... by Anonymous Coward · · Score: 0

    Their business model doesn't have a divine right to succeed. I wouldn't stick up for the scribes that were put out of business by the printing press, or the pony trap manufacturers eliminated by that newfangled autocar.

    May MS stock tank, and collapse the American economy with it. Then Europa will rule the world.

  110. Open standards a source of confusion? by SiMac · · Score: 1

    Since when have open standards been a source of confusion, besides when Microsoft doesn't comply with them? Microsoft is the only company with enough market power to confuse people about open standards and they have.

  111. hee, hee. by twitter · · Score: 2
    I like that, Inode:

    Not only are MS and Linux free to choose how to express themselves, their customers and users are, too!

    and I'll add to it: Customer freedom leaves M$ two choices, adopt free licenses or fail under an obsolete business model. Freedom is the ability to do what you want, fiscal reward for your activities is not a given.

    Microsoft thinks that they are entitled to income based on their "correct" business model. Most of the presentation was about software philosopy and why the GPL is wrong. It's funny how M$ overlooks their own strident propaganda while spending billions to promote it.

    The only way for M$ to remain relative and profitable is for them to free their source code NOW. The longer they wait, the more pollished their "competitor's" free code becomes, the less credit anyone will give them when they see the light. Only swift and positive action will resotore faith in anything M$.

    --

    Friends don't help friends install M$ junk.

  112. Visionary notion about IP by eniu!uine · · Score: 1

    It is irrelevant to argue the authenticity of the slides in this article. It is obvious that Microsoft has held these views for a long time. The debate here is about a philosophy of intellectual property that extends from the desktop to the CD player, and to technologies we have yet to explore.
    Software as an industry has only a tenuous existence because it is unnatural to sell something as ethereal as information. Most things bought and sold have a solid physical presence, and therefore build in copy protection. The only way we can keep the value of intellectual property is by placing limits on what we can do with it. If I want to protect a bicycle from being copied I need only manufacture it in a way that would make duplicating it more costly than buying it. To copy protect a software product I have to threaten potential copiers with jail time and somehow monitor their behavior to make sure they aren't doing it. True copy protection requires a virtual digital police state.
    Software makers as well as the recording industry lack vision as to what the future will hold. They struggle to maintain what they have now, when they should be worrying about how to adapt to the new order of things. Right now I run SuSe linux, which is nice and green. I use MPlayer(which is better than windows media player IMO) to play movies, and if I want to go through the trouble to learn a bit more I can get Quake working, or Neverwinter nights. All the software I could need for word processing, web browsing etc is already installed. This is an operating system that has practically no market share for desktops, but it is this functional. If microsoft doesn't come out with any major breakthroughs, it's easy to see where the desktop is headed. In the future people will choose the system that is great, allows total freedom, and costs nothing. Software companies need to focus on how they can market their proprietary products in an open source atmosphere.

  113. Here are the slides... by Shads · · Score: 2, Funny

    ...

    Slide1: Embrace
    Slide2: Extend
    Slide3: ???
    Slide4: Profit

    It definetly has worked in the past for ms products.

    --
    Shadus
  114. apropos value by martin-boundary · · Score: 1
    Microsoft in this case would add value. If they didn't, NOBODY WOULD PAY FOR THE SOFTWARE!
    Right, that's the crux of the argument (and all similar ones): how much value is added by the company. This is of course an intractable problem, which is why licenses like the GPL matter.

    My example assumed little to no reworking of the code. Since most customers are lazy/don't know any better, they would fork over cash for no added benefit and pay for the research twice. If this code is bundled "freely" with some other product, but can't be "unbundled" and increases the price of the product, then things become interesting for lawyers.

    Unlike the BSD license, the GPL-like license prevents this sort of thing from happening. However, if there is significant reworking of the code (where "significant" is the debatable point), then obviously the taxpayer/customer isn't paying twice for the same thing.

    Lastly, looking back on what I just wrote, you're right that my original example isn't stealing the code. It's really just an example of wilful misrepresentation and stealing the taxpayer/customer's money.

    1. Re:apropos value by mesocyclone · · Score: 2

      But why not allow the consumers to fork over cash for no added benefit? Are you their keeper? I asserted earlier that the GPL license assumes that consumers are dumb. This seems to prove the case.

      If it is bundled with some other product, so what? What is wrong with this?

      As far as wilful misrepresentation, it only works if the customer is dumb, or if the issue is of insufficient importance to matter.
      Or it may be that the consumer is unaware of the free software. In that case, the added value produced by the company is the advertising that resulted in the purchase of the software.

      So again, I do not see anything wrong being done with the government produced software. It is *still* available to anyone that wants it. For those who don't go to the trouble of finding it or applying it, a commercialized closed-source version of it works.

      For that matter, with public domain software, there is *nothing* preventing an open source group from *also* picking up the software and immediately GPL'ing what they have, and then developing from there.

      In other words, taxpayer produced software should be free. Really free. And that means public domain - license with no strings at all.

      --

      The only good weather is bad weather.

    2. Re:apropos value by martin-boundary · · Score: 1
      Ehh, not all customers are dumb because they overpay. We are only now seeing the first steps towards being able to buy computers without a mandatory Windows OS, after years of abuse of this practice. Who is to say how many millions were spent on "free" Windows licenses for computers, by customers who weren't dumb at all, but were forced to buy licenses for OS "x.xx", even though they needed OS "y.yy". Since the courts were required to step in after years of this, it's obvoius that the market itself can't always self-adjust against this scenario. It is quite possible for people to be aware of a misrepresentation, but be unable to simply vote with their wallets in the way you suggest.

      But I'm digressing... with regard to the issue, do you own a car? Please send me your address and the make and registration number, because I've decided to sell it to one of my neighbours. If it's ok with you, I'll drive by next weekend and take pictures of it for my sales pitch.

      Anyway, I'll let you have the last word on this, but remember, we're only discussing the special case where the company adds no substantial value to the software ;-)

    3. Re:apropos value by mesocyclone · · Score: 2

      There are lots of choices that are made for consumers by manufacturers. A hardware vendor may choose to preload an OS if that is their strategy.

      However, you are really addressing Microsoft, which as I have said is a special case. It is simply not relevant to the issue of whether the government should restrict its citizens from using government developed software in a private product.

      Your car question puzzles me. It is *my* argument, so why do you assert it?

      --

      The only good weather is bad weather.

    4. Re:apropos value by martin-boundary · · Score: 1
      Darn, I was going to leave it at that, but then you ended with a question...

      I certainly was addressing Microsoft, but only as an example of a typical situation, not in an exceptional, once in a blue moon sort of way. From your earlier response, it seems to me that you subscribe to the standard invisible hand free market argument. In particular, a free market quickly settles into equilibrium, because people act rationally.

      Now it is known that the free market doesn't work in the limiting case of a monopoly (which is the Microsoft example), and in fact the invisible hand theory usually supposes that there is no friction either: that agents are free to act in their best interest, and always do, immediately. It also assumes that agents have full information at all times.

      Obviously, this is an idealization which is far from true in the real world. In fact, real markets can exhibit several local equilibria, both stable and unstable. At that point, since the market can't make optimal decisions, I think it is the job of governments to step in and force the market into a desirable equilibrium when the current one isn't in the best interest of the citizenship. Monopolies are one such example, but others include using tarriffs and preventing dumping, to protect local industries for example. It happens all the time.

      For free software, there is no doubt that people can and are duped into sidestepping their own preferred responses. For example, if a medium-sized company takes free software and simply rebrands it, spending millions on an advertizing campaign, the majority of people will be unaware of the free and functionally identical alternative, even though they would prefer using it if they knew. When this free software is distributed without the source, it is not even possible to verify the fact, nor is it usually possible to force a decision on the issue through the courts, since the company can stonewall practically indefinitely.

      So this is an example where the true market equilibrium is different from the theoretical invisible hand "best" equilibrium, which you invoked previously. In that equilibrium, the price of the software would go to zero regardless of the company's actions, simply because the free alternative would spread very quickly and unstoppably. But in fact people don't have all the information they need in this case, and therefore prefer the branded version.

      The car example was sort of on the same lines, since it depends on my prospective customers not having full information.

      Anyway, I had a quick look at the link you provided, and if you've read this far, you might as well keep reading a couple more paragraphs.

      The article on communism misses the point of the GPL. I would argue that in fact the GPL is an extremely capitalistic license, quite unlike the BSD license. Here's why: in the real world, property belongs to you because you can prove that is so, through paperwork backed by the legal system. Why do you own your house/car/etc? Because you can show relevant papers.

      In the current software world, there is no such thing as proof that you own a piece of code. Change the compiler and your binary looks slightly different. If you keep your source code secret, then others must take your word for it that you're selling them something you own (again, like the car example). So this is a proto-propery system based on people trusting you, rather than an independent third party.

      The GPL and open source licenses in general are more advanced. People don't need to trust you, they can see for themselves by looking at the code. Just like in the real world, people don't trust you but trust the pieces of paper you carry.

      If you want to have capitalism, you need a solid foundation for property ownership, which only open source can offer. The current alternative, trusting a vendor because they say so (closed source), is a no-go. You'd need to create a whole external trust and certification system, which is one of the functions of the government.

      So GPL like licenses are strong capitalism because everywhere the source goes, it carries proof that it is yours. The fact that most open sourcers like to give the code away freely (as in zero dollars) is just a sideshow. You can charge anything you want for your software, and if it carries proof that it is yours, people will know they should come to you for support/extensions/whatever first.

      Closed source is weak capitalism, because anyone can wrap a closed source application inside a different shell and sell that. Yes it's illegal, but who's going to check? Especially if it's a company with lots of lawyers. Because the source is closed, it's too hard normally to check the provenance, so one has to trust the vendor.

      BSD licenses are the closest to communism, because the property foundations are elided. If you're told a program "uses some BSD code", you don't know if it's just a little, a lot, or all of it. You're back in the closed source scenario where you have to trust the vendor's word. However, the difference with closed source is that you've asserted ownership of the code, unlike in the GPL case. Here's how: your customer bought the sotware and reads the BSD copyright. Does he conclude that the best person for upgrades/changes is going to be you or the original BSD author? Probably you, since there is no way of knowing how many changes you've done. The code is now your property, as well as the original BSD author. This is communism, where property belongs to everyone.

      Well, I've gone on long enough about this.

    5. Re:apropos value by mesocyclone · · Score: 2

      You certainly raise a more interesting and valid argument for open source than I have seen so far in this discussion, so I will comment on that.

      First, a comment. I do not assume a perfect free market. Markets are in general the best known economic decision mechanism, but they aren't perfect. Microsoft is a good example - it has a monopoly. Many free market people (including far too many of my ideological comrades in conservatives) seem to have almost a religious belief in the power of the market to always produce the right result, and thus make ignorant arguments about the Microsoft case (fortunately Judge Bork is much smarter in his arguments).

      I have another essay in that blog about the failure of the free market in health insurance... and how conservatives are wrong in most of their arguments. So no, my arguments make no utopian free market assumption. In cases given, the assumption is valid. In other cases, it may not be.

      What I do dislike is government interaction where it is not totally necessary. Government can only operate through the implied use of deadly force (at the extreme) and thus has vast powers that should be used very rarely. Furthermore, government mandates are usually worse than the market - government tends to be stupid, slow moving, extremely bureaucratic, and often corrupt (I suspect that you in particular would enjoy my quasi-humorous essay on the subject of bureaucracies).

      Now to address your point about open source proving code ownership, and that being pro-capitalist. I believe that in balance, this point fails. The reason is that while open source allows one to prove code genesis, the only value of this is to prevent criminal theft of trade secrets. But it the process it decapitalizes the code as an asset, which I think is an even worse outcome. There are other (admittedly imperfect) remedies for trade secret theft, but any forced decapitalization of code is disastrous.

      In the case of privately developed software, the owners of that software can *choose* whether to let open source or closed source protect their interest in the software, and I think that is a maximal freedom approach. IOW, if you believe that *your* commercial or personal interests are best served by GPL'ing your code... go for it! I have no problem with that. If you don't, don't. You may want to BSD it. More likely, you will keep it as a trade secret.

      Since government produced (or commissioned) software is the main subject of this discussion in Slashdot, I have *no objection* to anyone taking *that* software, putting a different name and a flashy package on it, and selling it for a zillion dollars. Or, more accurately, I don't like people doing that but I don't think it appropriate to sacrifice anybody's freedoms to stop them. Their behavior may be immoral but that's their problem, not ours.

      Thus I think government produced software should, in general, be released to the *public domain*, not GPL or BSD or any other non-public domain license. The government's interest in the software ends at that point. Then, whatever happens to that software is up to whatever any person or group (including corporations) wants to do with *their copy* of it. Nothing in public domain release prevents the software from remaining open source, or from GPL or BSD or other trees being derived from it. Only modified versions of the software can be closed source, because the original source is freely available from the government or archives.

      I also believe the government should be allowed, with suitable oversight (this is a whole discussion in itself - how to do that with minimal corruption), to contract for closed source or even proprietary software.

      Several decades ago I worked for a military consulting house and we were paid by the government to develop closed source software for them. They got the benefit of cheaper software and our expertise, and we got an asset that kept our tiny consulting company alive.

      I don't thing my example should be the rule, but I do think it should be totally prohibited (perhaps, again, with suitable oversight).

      --

      The only good weather is bad weather.

  115. I can just imagine how they got those pictures by TummyX · · Score: 2

    Some evil smelly hippy must have managed to slip into the presentation and take pictures of the secret Microsoft manifesto using SOVIET RUSSIA era spy equipment.

    The only photo they didn't manage to take was the one of the map of Western Europe.... :P

  116. MSFT is anti-GPL not anti-copyleft by Anonymous Coward · · Score: 0

    Not to nitpick, but MSFT is _not_ anti-copyleft. For example MSFT supports the BSD-style licence which is a copyleft.

    MSFT is fervently anti-GPL. In particular the viral nature of the GPL fuels hatred by MSFT. If software written under the GPL was self-contained and was guaranteed to not apply to non-standard core or extension system API's. What is non-standard? Is anything non-POSIX also non-standard? The answer has to be no because otherwise to bypass the GPL a vendor would simply have to package its propietary code as an unpublished API that is used by a GPL program shell. I'm quite certain that the FSF holds such actions to be in violation of the GPL. See the GCC/NeXT debacle.

    Without this issue, MSFT would probably be less driven. Since GPL is untested legally, MSFT lawyers may correctly read the GPL to require API's used by GPL software to fall under the GPL. MSFT is unwilling to risk their software library by endorsing the use of the GPL. End of story.

    1. Re:MSFT is anti-GPL not anti-copyleft by Anonymous Coward · · Score: 0
      Copyleft is a general method for making a program free software and requiring all modified and extended version of the program to be free software as well.

      That's what the FSF says "copyleft" means, and they coined the term. BSDL doesn't even try to be a copyright license, though it is a free software license (only appropriate to use if you're willing to leave some users of derived works twisting in the wind).

  117. virus vs. cancer by MegaFur · · Score: 2

    Why is viral any less loaded than cancerous?

    Because on very rare occasions, one hears a phrase like "virus used for good." Cancer, by contrast, is always bad. Haven't you heard about any of those projects where they plan to employ a virus in a positive way? (Either figuratively or literally.)

    See since a virus (in the real world) is this little clump of DNA that reprograms cells, it's conceivable (though difficult) that you could make a virus that reprogrammed (only some of) someone's cells to do something good (like if they weren't working right). Or much easier would be make a virus that only attacks a specific organsim that you want to kill.

    Cancer refers to a condition where some of your cells are broke and they're copying without bounds, theoretically consuming all your body's resources eventually, and making lumps where there should be no lumps. It's bad. It's always bad. There's no good there.

    The main difference is that "virus" refers to a little programmable clump of DNA whereas "cancer" refers to a (always bad) condition.

    --
    Furry cows moo and decompress.
  118. There's Still Time by IHateEverybody · · Score: 2


    We all know MS is bad and they are hard at work on Evil Master Plan v1.0

    This actually comes as something of a relief. We know it always takes Microsoft until at least version 3.0 to get everything to work.

    --
    Does this .sig make my butt look big?
  119. The use of slides may be on purpose... by Anonymous Coward · · Score: 0

    A presenter brings a message with everything he or she does, body language, clothing, words; this also including use of presentation means.

    I sometimes deliberately bring slides for smaller groups, believing this (among other means) to create a more informal and friendly atmosphere, when this is what I want.

    If this MS guy talked to a smaller group, he could be doing the same thing.

    s.y.,
    AC in the consultancy business

  120. MS wants you to not /use/ GPL s/w by doug363 · · Score: 2
    This is really more of the same stuff that's been discussed before. However, I'd like to point out a few issues that irk me about Microsoft's anti-GPL arguments.

    1. Indirectly, they suggest that merely using GPL software could cause "viral" licensing problems for commercial companies. It doesn't. Of course, one only has to look at what Microsoft's business aim is: to sell software. If they can associate "GPL" with "bad", then their software will have an edge over GPL software where there is competition (in MS's biggest markets).
    2. Their suggestion that Microsoft's licensing and "shared source" programs provide all of the freedoms with none of the downsides of GPL-like licenses. Of course, this is patently false: you're never allowed to just copy Microsoft shared source code and plonk it into your own product, which is the only time that the GPL kicks in. But virtually any other license has more freedoms than Microsoft's, including: the right to refuse automatic software updates; the right to transfer all copies of the software and the licence more than once; (in the case of a compiler) the right to license compiled programs under any licence of your choosing that doesn't require the library source code to be distributed; and the right to create competing implementations after seeing the source code. Of course, free software comes with more freedoms that just those listed above. They make a token statement that they've re-thought their licensing in response to the GPL, but mostly it's just gotten more restrictive, and attempted to shut out Windows GPL programs as much as possible. (Have a look at the Windows Media SDK licensing terms. Very very restrictive.)
    3. Their suggestion that the GPL stifles innovation and creativity. Microsoft is using many of the ideas that were developed in the Linux kernel in recent years, which is fine, but then they suggest that the GPL stifles creativity, when in fact GPL-licenced code has inspired some of their ideas. Some of the most bleeding-edge stuff is developed as free software. Examples: ReiserFS, many other kernel projects, Mozilla, and KDE/Gnome.
    4. The idea that publishing sample code for a standard under a GPL license is bad. Microsoft are free to read the source code and get ideas from it, but they aren't allowed to copy it if they don't want to distribute source code with their product. So it's a reference implementation that they can't copy and distribute under conditions of their chosing, so what? They suggest that TCP/IP wouldn't have gotten the widespread adoption that it did had the code been GPL licensed. Microsoft were late on the bandwagon with TCP/IP, and they don't use the BSD implementation in NT anyway, contrary to popular myth. They didn't copy the BSD implementation, so they wouldn't have had problems if the canonical implementation was GPL licensed either.

    The bottom line is this: There are certainly reasons why businesses or individuals would not want to release their software under the GPL, but Microsoft wants to convince you of more than this. They want you to avoid using GPL software even if it's appropriate, they want governements to discourage (or prevent!) its use in acedemia even if it's appropriate, and they want to stamp out any and all development under the GPL on Windows.

  121. GPL does suck by Anonymous Coward · · Score: 0

    These guys are right about one thing: the GPL does really suck.

    While the GPL's communism provide an interesting counterbalance to the typical shrink wrap license's fascism, GPL'd software is no more free than proprietary software -- it just happens to be on the opposite end of the encumbrance spectrum.

    Proprietary: The IP owner has all the rights. The public has no rights.

    GPL: The software (as if it's a person) has all the rights. The public has no rights.

    If you want a piece of software to be TRULY FREE, contribute it to the public domain. This enables anybody on earth to do anything they want with it, without any encumbrances. Public domain is the only mode of release than anybody can accurately claim to be free.

    The open source community is a land of a thousand licenses and no genuine freedom.

  122. Rip Them Down. by Anonymous Coward · · Score: 0

    Yeah. It's about time everybody woke up to themselves. Socioeconomic models are the same; capitalism is as bad as communism. Fascism smells bad too. So what's the alternative??

  123. well, i don't know much about the gpl debate.... by teknophobe · · Score: 1

    ..but nobody exactly spent a lot of time incorporating any design features into those slides. doesn't anybody at MS know how to use those cool colors, backgrounds and animations available in PowerPoint.??

  124. legal overhead? by p00ya · · Score: 1
    All software companies must carry significant legal overhead to protect against GPL "infection" - 0224r

    Not if they're happy to embrace the GPL and release under it. I'd say there's just as much legal overhead consumed by making sure that all use of M$ software complies with its EULA (not to mention the horror of shared source !).

  125. Interesting read... by Chexsum · · Score: 0

    The stuff about the GPL is true *ie you cant sell the software as easilly*. Why dont they just quote the FSF Manifest though - hehe *at least then the reader can read the intentions surrounding the GPL*. :)

    I dont like licensing and its fun to see this terms and conditions battle. */me checks FSF.org for a retaliation*

    The GPL is the best software license! *IANAL but who GAF*

    --
    Pixels keep you awake!
  126. GPL is better for the industry by clenhart · · Score: 1

    I believe freedom is not the advantage of the GPL, but competition is.

    One of the slides said that "The GPL is fine for the individual to choose, buy bad for the industry.". This is not true. Sure, the GPL is not as profitable for companies as closed source, but the GPL is good for customers, because it makes for a much more competitive industry. A more competitive industry benefits the customer.

    Smart sellers will choose monopolies. Smart buyers will choose competition. It will be interresting to see who wins, proprietary source or open source!

  127. late post by Anonymous Coward · · Score: 0

    In other new, Bookmans organizes protest march on public library "They're stealing our profits" film at 11

  128. Is the GPL really free as in free speech? by gpoul · · Score: 1

    Who coined that term?

    Is it really true?

    What's with the BSD-license? Isn't that more free? And doesn't every license provide and take away your freedoms?

  129. Re:More M$ Sh**t by larry2k · · Score: 0
    It's the same question to you:
    why do you bother? if i'm a guy that posts every 1 1/2 month, logs in once in a while, writes bland and pointless comments and is not as elocuent as you, why?
    Anyway, thank you for your comment.

    larry

    --

    The package said "Windows XP or better. Pentium Class Processor or better"... So I got a Mac with OS X

  130. Microsoft's GPL FAQ by gpoul · · Score: 1

    To get a glimpse of what Microsoft thinks of the GPL you can read the document at
    http://www.microsoft.com/licensing/downloads/Gpl-f aq.doc.

    This document is actually really good and should be a must read for every SMB or OSS developer.

  131. Not just Microsoft by Felinoid · · Score: 2

    In the free software world it's the pirates who try to use commertal software as if it were free (as in beer) and reverse engenear it (free as in speach) and patch it (free as in sidewalk.. )
    But it is theft.

    In commertal software it's legal to do exactly the same thing to free programs.

    The short and simple.
    Jack writes commertal code
    Zeek writes free software.

    Zeek makes a game Jack makes some changes and sells it Zeek pirates those changes.
    Jacks the theaf but Zeek gose to jail.

    This is becouse Jack os getting paid for Zeeks hard work and Zeek dosen't get to benifit from it. Jack's getting ALL the benifits and NONE of the labor.

    That said I do release some of my code in public domain becouse sometimes I do benifit from Jack using my work.

    --
    I don't actually exist.
  132. Counter argument by Felinoid · · Score: 2

    It's sick that I can counter myself.
    So here we go.
    Yes I can benifit from somebody using my code in a commertal product.
    Let's say I'm a gammer and I make a game that has a huge number of sweet graphic and sound hacks. But maybe the game sucks.
    Then Jack makes a great game out of my code now I get a great game with sweet hacks. Even if I'm paying for if had I not done the work I'd never have such effects.
    I benifit. Now let's say I run Linux and the commertal gamed using my hacks won't run on my box even under wine. Now I can't benifit unless I get the code and port it to Linux myself.
    Or I'm a commertal software develuper now I won't get paod becouse anybody can use my hard work for free.

    Maybe I'll get extra traffic to my website. Maybe I don't need it.
    Maybe I'll get recognised as a great programmer. Maybe I'm already recognised. Maybe I'm in a diffrent profession and don't need the recognition. Maybe my code sucks.

    It's up to me. It's my code after all.

    --
    I don't actually exist.
  133. Re:My Thoughts (or ramblings) by cant_get_a_good_nick · · Score: 2

    Our Linux production servers run heavily threaded Java apps.

    Does the "thread really is a seperate process" mess with things like signals as well?

  134. Commercial vs Open source. by DunbarTheInept · · Score: 2

    The second slide already showed how broken their perception of open source is. Their second slide was a comparasin of "commercial" source vs "open" source as if they were mutually exclusive groups when they are not. Take a Linux distro company like Redhat for example. They are commercial. They make money reselling stuff that's open source. Whether something is Commercial or not is not really a property of the code itself, but of how people obtain it. Redhat's SRPM of the linux kernel that lives on the install CD is commercial. A downloaded tarball from www.kernel.org is not, even if it's exactly the same version number, with the same verbatim GPL boilerplate licenses all over the source code, and 'diffs' show it to be identical code to what's in the Redhat SRPM. Whether it's commercial or not is a property of the distribution technique by which you obtained the product, not a property of the end product itself.

    --

    Don't label something "offtopic" unless you know the topic well enough to tell what's on topic.

  135. My Favorite Quote by asscroft · · Score: 1

    "Government funded projects released under the GPL would remain public resources and have no commercial value. Like FreeBSD"

    Isn't that the point. I'm tired of paying lots of taxes (& Tuition) to fund projects that get private companies rich and do little to give back to the community or the schools.

    Oh know, GPL limits corporate welfare. Very fuckin well then, spend the money on Art/Music/PE and teachers in K-12, and let MS create thier own software.

    --
    because I have been enjoined by this Holy Office to abandon the false opinion which maintains that the Sun is the centre
  136. Re:More M$ Sh**t by jumbie · · Score: 0

    thanks for taking the time to rise to a blatent troll

  137. Last Post! by alpg · · Score: 0

    Those parts of the system that you can hit with a hammer (not advised)
    are called hardware; those program instructions that you can only curse
    at are called software.
    -- Levitating Trains and Kamikaze Genes: Technological
    Literacy for the 1990's.

    - this post brought to you by the Automated Last Post Generator...