Slashdot Mirror


Businessweek Recommends License Switch for Linux

MadFarmAnimalz writes "BusinessWeek has an article about the perceived threat of patents to linux, citing the SCO case, the opening of OSRM, and the Munich situation as evidence for the veracity of their conclusion that Linux isn't safe. Their solution? Relicense to the BSD license or the Mozilla license. On a positive note, the article's author does link to RMS' article Why Software Should Not Have Owners; good to see Stallman being quoted and linked to in a publication Like BusinessWeek."

52 of 548 comments (clear)

  1. No protection by msgmonkey · · Score: 5, Insightful

    I can't see how switching licenses will help.

    The licenses mentioned (patent clauses in GPL acknoweldged) deal with copyright and not patents which although people easily confuse are completely different legal areas.

    1. Re:No protection by product+byproduct · · Score: 5, Funny

      It's businessweek. Business people like to force a useless migration to something different every once in a while.

    2. Re:No protection by smootc-m · · Score: 5, Insightful

      Switching to a BSD license will just encourage code forking which is bad. We will just end up in another "Unix Wars" scenario with proprietary versions of GNU/Linux popping up with their own incompatible extensions.

      The real beauty of the GPL is that it encourages collaboration and sharing with the side effect that forking is discouraged. GNU/Linux is becoming the commodity OS precisely because of the GPL.

    3. Re:No protection by Bruce+Perens · · Score: 5, Insightful
      He's a tech reporter who hasn't investigated the situation much and wrote the first thing that occurred to him. He did a pretty big disservice.

      Switching from the GPL to BSD or another license would actually reduce the protection. It doesn't provide any incentive to license the patents for all users. Who do you think is going to develop all of this software if only big companies are able to distribute it legally? We'd be back to proprietary software and proprietary licensing.

      Bruce

    4. Re:No protection by Jeremiah+Cornelius · · Score: 5, Insightful
      If MBA's had been involved in Linux from the beginning, there'd be nothing to discuss.
      There'd be no Linux at all.

      Same old story... Come late to the party, then know all about how it's done.

      --
      "Flyin' in just a sweet place,
      Never been known to fail..."
    5. Re:No protection by eric76 · · Score: 5, Insightful

      I don't see that the GPL does anything at all to prevent code forking.

      Say you wanted a different version of Linux that did something differently. So you make the changes, however much they are and you donate them back to Linux.

      But the Linus doesn't have to accept those changes. Or he can pick and choose which portions he thinks are good.

      But since you donated your modifications back, you are free to use those modifications to release your own version.

      In a manner of speaking, there already is a fork of Linux. Except it's a fork that is built into the current release instead of a completely separate fork. I'm talking, of course, about SELinux from the NSA.

      What switching to the BSD license would really encourage is everyone else, for example, Microsoft, to be free to use the code for their own commercial purposes.

      By switching to the BSD license, Microsoft could release their own closed and proprietary version of Linux. For example, they could use the Linux code to enhance Windows and make it able to run any and all Linux programs available.

    6. Re:No protection by grumbel · · Score: 5, Insightful

      The GPL doesn't prevent forking, it just makes sure that code can be merged back and forth between the forks at all times, so that stuff like the WineX vs Wine scenario can never happen with the GPL.

    7. Re:No protection by aquabat · · Score: 5, Insightful
      I think the point the article is trying to make (although not explicitly) is that a BSD style license would allow big software companies to hide their use of open source software in their products.

      Assuming the company is distributing its open source derived software, the GPL requires public disclosure of the original open source software and any derivations, which would give patent holders evidence of infringement.

      The BSD license, however, lets the company distribute their product without acknowledging any open source content. They can keep all their code secret. This places a greater burden on the patent holder to prove that a patent is being infringed at all.

      I think this is the "protection" the article refers to.

      --
      A republic cannot succeed till it contains a certain body of men imbued with the principles of justice and honour.
    8. Re:No protection by Ralph+Yarro · · Score: 5, Funny

      Business people also like open source programmers to release their work under a BSD license rather than GPL.

      As a business man I can confirm this and would like to add that we would also like it if you would mail us your life savings at the same time.

      Thanks

      Ralphie

      --

      The real Ralph Yarro posts as Anonymous Coward. Anyone else is an impostor.
    9. Re:No protection by ArbitraryConstant · · Score: 4, Insightful

      Switching to a BSD license will just encourage code forking which is bad.

      As opposed to what, picking a development model that forces distributions to fork? 2.6 is the active development kernel, and distributions are now responsible for putting together a stable kernel.

      This will cause more situations similar to what Red Hat has done with their heavily customized 2.4 kernel. Distributions will have their own heavily patched kernels that can no longer be easily migrated to the current vanilla versions. There are several distributions with the resources to do this by themselves, and the smaller ones will probably band together to do it as well. If that's not a fork, it's the closest thing to it and will probably lead to a fork in the future.

      It's not the BSD license that encourages forks. There were (are) two factors:

      -Commerical forks can get specs on hardware that open source ones can't. Since they can't give the code of the driver back to the community, they must fork.

      -The BSDs (not the license, but the OSes) are designed as complete operating systems, with a userspace and a kernel in one package. This encourages forking because it's less modular than Linux.

      It's not the licenses that do it, it's the unique position the BSDs are in. There are BSD licensed projects which do not fork, such as Python, which uses a license similar to BSD. By similar, I mean it explicitly says you can fork, keep the code secret, and sell the results. Python hasn't forked because there's no motivation for people to do it.

      --
      I rarely criticize things I don't care about.
    10. Re:No protection by Ruie · · Score: 5, Insightful
      GPL does help with code forking - it gives you the freedom to do with the fork as you please.

      As opposed to buying forked software (say Mac OS X) and then having to wait for the developer to fix bugs in the portions of code that are binary only.

      In other words, the help is not in prevention of forks, but rather in making it easy to merge them back.

    11. Re:No protection by oolon · · Score: 5, Insightful

      The point they miss (because they are looking back) is many corportate donors of software source in linux would never have done it if it was not GPL. As the GPL maintains a level playing field, if a competitor takes the code and uses it they have to give back (or rather forward). If Linux had been BSD all the donations could have just been torn out of linux and used in other things. I believe resulting in the donations not being made in the first place, do you think IBM would have dontated its filesystem if it thought Veritas could just take the good bits of the code?

      James

    12. Re:No protection by Tony-A · · Score: 4, Funny

      SOP for a new CEO.
      If it was centralized then decentralize it.
      If it was decentralized then centralize it.

    13. Re:No protection by TheRaven64 · · Score: 4, Informative

      I think you are confusing BSD and MIT licenses. The BSD license specifically states that you must acknowledge the use of BSD code even if you only ship binaries (see the IE about box, for example). The MIT license only requires you to include the copyright in the source code (which you do not have to distribute).

      --
      I am TheRaven on Soylent News
    14. Re:No protection by Tony-A · · Score: 4, Interesting

      BSD has a few forks.
      Linux has many forks.
      Main-line linux, as on kernel.org
      Red Hat Linux, with a modified (forked) kernel.
      Various patch sets that haven't (yet) made it into the main line.
      By applying different combinations of patch sets, you can have more different possible kernels, this is before you start configuring, than there are places to put those kernels.

      The critical difference is that Red Hat 2.6 is a fork from the main-line 2.6 not a 2.6 fork of Red Hat 2.4. Forks that aren't worth keeping up with just wither and die. Linux gives the outward appearance of not forking, because there is about as much merging as there is forking.

    15. Re:No protection by eric76 · · Score: 4, Informative

      Let me clarify that point.

      What I meant was that if Linux switched to the BSD license, Microsoft could release their own proprietary version of Linux. Under the BSD license, such a release would not have to be open at all.

      They already did that with the TCP stack from what I understand. They incorporated the BSD stack in their code and their use of it is not open at all.

    16. Re:No protection by schon · · Score: 5, Insightful

      I still don't see a problem.

      Then you have blinders on.

      The problem isn't that the original code is free, or isn't free, or that MS's version is or isn't free. The problem is that THERE IS A FORK THAT WILL NEVER BE ALLOWED TO MERGE BACK.

      A major point of Free software is to reduce the amount of wheel reinvention. Everybody gets to see and use everybody else's code. BSD-to-commercial forks provide a major impediment to that.

      So what damage accrued to BSD or TCP users as a consequence?

      MS TCP-users were not able to take advantage of the advances to the BSD stack, and are now stuck with a crippled version. This is the whole point.

  2. In other news.... by rokzy · · Score: 5, Insightful

    Women should give up their personal rights to make it easier on people who want to rape them.

  3. Less incentive to develop by dukerobinson · · Score: 5, Insightful

    if this were to happen, which I find highly unlikely, for one thing there would be a fork straight away. It would be just like the Xorg and Xfree split. Also, under the bsd license commercial proprietary software can integrate the open-source work, so why would anyone slave away at developing linux, only to have their work immediately integrated into commercial applications, the original developers not to see a dime. There is all kinds of bsd code in windows, for example.

    1. Re:Less incentive to develop by rokzy · · Score: 5, Insightful

      no it doesn't. that's like saying being able to kill people increases your freedoms.

      it may be true for a minority of people who want to kill, but it means that EVERYONE loses the "freedom" to feel secure against random deadly attack.

      taking it further, the most free society is one with no laws whatsoever, but in such a society freedoms can be easily lost.

      the GPL is like "Civilisation for Software" - it may mean you lose some freedoms, but in return the freedoms it gives are protected.

    2. Re:Less incentive to develop by jsebrech · · Score: 4, Informative

      A real life example: the linux kernel is BSD-relicensed, DistroInc turns it into a closed source kernel on which a closed source linux distro is based. DistroInc has gained freedoms by the relicensing, but everyone else has lost them, because if the kernel were not relicensed, DistroInc would have to have made their improvements public, thereby benefiting everyone in the community, giving them higher freedom to use DistroInc's advancements.

    3. Re:Less incentive to develop by Trelane · · Score: 5, Insightful

      This isn't about Microsoft, although it could well be (they can't use GPLed code like they use BSD'ed code in Windows).

      It's actually a very different, very critical point: if there were no GPL, Red Hat, Novell, and others could very well release their own binary-only kernels/utilities and the Linux world would fragment like the Unix world. It's the GPL that's holding the Linux community together.

      For instance, say that SuSE gets 90% of the Linux "marketshare." They then start introducing changes in the kernel and standard software stack which other vendors (hardware/software) rely on, due to their market dominance (sound familiar?). However, we note that, in order to be Linux and use the Linux kernel/software stack, they must release the changes back to the world under the GPL. Thus, Red Hat, Gentoo, Debian, and others all can stay 100% compatible with SuSE despite SuSE setting the de facto Standard. If SuSE comes up with Licensing 6.0 and tries to coerce their users into it, the users have much less of a barrier to switching away to other Linux distros because of this compatibility! Thus SuSE's power is checked despite monopoly position.

      Now, there is fragmentation in the Linux community due to different distros relying on different software, and having slightly different systems and configurations. This can be mitigated, however, by following the Linux Standard Base, and we must encourage our distros to follow the standard and work to develop the standard to prevent this fragmentation. It should be a fairly easy problem to fix, of a much different order than the problem with the binary unix compatibility fragmentation.

      --

      --
      Given enough personal experience, all stereotypes are shallow.
    4. Re:Less incentive to develop by kanly · · Score: 5, Insightful

      This whole thread seems based on the premise that you actually could, in some way, relicense Linux under the BSD license. This isn't as easy as you might think.

      Relicensing checklist:

      1. Go to Linus, and get him to release the portions of Linux that he owns under the new license.
      2. Armed with his blessing, go to each person who's ever contributed code, and get them to sign on. Last time I looked, this was at least a few tens of thousands of coders. Some are deceased, so you will have to get permission from their heirs.
      3. Ask the FSF to release glibc under the new license. Wear body armor.
      4. Go through every userspace program you want. If it is GPL'd, either get the author to relicense, write a replacement, or do without. Good luck trying to even find all the authors, let alone get them on board.

      It's widely considered that even Linus Himself could not push through a license change. No need to worry about a corporation doing it.

      If you want something under the BSD license, you might want to use BSD.

  4. Leave me alone by Anonymous Coward · · Score: 5, Informative

    I have written code for Linux and I decided to put it under the GPL. Get over it. I won't change it. I feel that the GPL gives me the kind of protection I want to have. BSD license would mean that scum like SCO can abuse my code. I am sure they would love that but it won't happen. So you stupid reporters and lawyers can as well stop argueing about license switches BECAUSE IT WILL NOT HAPPEN. Go away.

    1. Re:Leave me alone by Rakshasa+Taisab · · Score: 5, Insightful

      Exactly, i think most serious open source coders are well aware of what the license they choose means. I specifically choose GPL instead of LGPL for a library i'm writting because that's what i wanted.

      I'm sorry if our licenses arn't corporate friendly.

      --
      - These characters were randomly selected.
  5. All your software are belong to us! by bap · · Score: 5, Insightful

    That's an article? People who want money for nothing demand a gift with no string attached? Their message to the authors of Linux: "All your software are belong to us!"

    1. Re:All your software are belong to us! by Bastian · · Score: 5, Insightful

      What the author is really asking for is for Linux to transition from this bizarro-world that many businesses are afraid of and can't understand to the nice simple regimented money-based world they are used to.

      In this world, if you get something for free (as in beer), you should be able to do anything you want with it. They can't understand the idea of nonmonetary compensation. The idea of, "You can use it, but if you try to do anything else with it you have to let us use your version, too." comes across as some sort of wacky bait-and-switch. The whole thing gets broken into two parts:
      1. It's yours. Take it.
      2. No, wait, WE WANT YOUR SOUL! SOUUUULLLS! RARRRRRRRRR!
      (Of courrse, it doesn't help that MySQL AB really does try to do the above.)

      I'm sure it's frightening for lots of business folks. They don't like it when they can't pretend to understand what's going on.

  6. Not even an article by Anonymous Coward · · Score: 5, Insightful

    It's a commentary, AKA an opinion piece. Look, I can write an opinion piece, too.

    Microsoft should switch to the GPL.

    Hey, someone submit this to Slashdot. Here's an idea for the text. "Slashdot has an article suggesting Microsoft should switch to the GPL."

  7. Why don't they mention FreeBSD, OpenBSD, etc? by Anonymous Coward · · Score: 5, Insightful

    Are there any practical reasons they can't use FreeBSD/OpenBSD/NetBSD instead of Linux in situations where a BSD-style license is preferred over GPL?

    Or is it simply because they've never heard of it due to lack of marketing?

  8. Not going to happen. by BJH · · Score: 5, Interesting

    Even if this were a good idea (which it's not - it's roughly on a par with somebody who is being attacked by rabid hyenas deciding that they'd be safer if they distracted the hyenas by attaching large chunks of fresh meat all over their body), it would require that either:
    a) Anybody with significant (as in more than 20-30 lines or so) contributions to the kernel give their approval for the switch, and it ain't gonna happen because even if Linus went for it, Alan Cox is very much pro-GPL and has large chunks of code all over the kernel

    or:
    b) Somebody strip out or rewrite all parts of the kernel copyrighted by people who objected to the license change, which in the end would probably amount to an effective rewrite of the whole thing.

  9. No can do! by tomhudson · · Score: 5, Insightful
    If it's GPL'd, then everything up to the license chance would still be GPL'd, and it would immediately fork into GPL'd and non-GPL'd.

    Of course, then the BSD licensed stuff would be copied back into the GPL'd fork, as is allowed.

    Result - A full-featured GPL'd version, and a non-GPL'd version without all the features that it can't include as it would be a violation of the GPL.

    In other words, why bother? It ain't broke - don't try to "fix" it.

  10. Logistics by keiferb · · Score: 4, Insightful

    The logistics of a license switch are staggering, especially when you consider a project the size of the Linux kernel. IANAL, but wouldn't every contributor to a given project, no matter how far back as long as their code's still there, have to sign off and approve of the license change?

    Sounds like a headache and a half to me.

  11. License Change by EinarH · · Score: 5, Informative

    Groklaw had an article about this some days ago, there are tons of discussion there why a license change;
    1. Would be stupid.
    2. Won't happen.

    --

    Melius mori in libertate quam vivere in servitute.

  12. Re:So let me get this straight... by oolon · · Score: 4, Insightful

    But this is what people just don't get. Linux like all other GPL source is copyrighted, If the GPL licence agreement is proved to be invalid that does not mean suddenly linux and all other GPL code is now public domain. Linux would still be copyright and everyone who was not the copyright owner would not have a valid license to use it. Until issued with a new agreement from the copyright owner. This is one of the strenghs of the GPL, if your defeat it you can no longer play with the toys rather than being able to steal them.

    James

  13. Lamest.... article.... ever.... by gsfprez · · Score: 5, Insightful

    in light of IBM's use of the GPL to shutdown a major copyright infringer, SCO...

    and in light that this author decided to publish an outdated article - he continues to talk about how IBM is being sued for copyright infringement, while the hunter is now the hunted in the SCO vs IBM case with IBM arguing (very well) for partial summary judgement that IBM is 100% in the clear on Linux while its SCO who is now clearly in violation of copyright law...

    but mostly because his very first premise is utterly false - "How does software owned by everyone and by no one survive in a world where copyrights and patents shape the legal landscape?"..

    this article is lame...

    Dear Mr. Wildstrom.

    The GPL has NOTHING to do with your precious IP or ownership of software. The GPL is ONLY about two simple things - distribution and use. Just like EVERY SINGLE OTHER software license.

    It is obvious you do not understand this. I suggest you read the two latest court documents from IBM, who are doing two things you claim the GPL does not allow...

    1. claiming ownership of their GPL licensed software and
    2. are asking the courts to prevent a copyright infringer from reditributing their software without their permission.


    The easiest way to understand how the GPL works and why it works is to read those court documents - because its heart is exactly what the GPL is about - controlled distribution of owned software by the copyright holder.

    As my history teacher was fond of saying to the kids that wrote their papers the night before as they watched The A-Team - "please grasp the concept, then rewrite your paper".

    --
    guns kill people like spoons make Rosie O'Donnell fat.
  14. Re:hail by imroy · · Score: 5, Funny

    I belive in spell-checkers!

  15. MOD PARENT UP by glMatrixMode · · Score: 4, Informative

    mod parent up

    besides, this has already been discussed at Groklaw :
    http://www.groklaw.net/article.php?story=200408140 64859996

    --
    War doesn't prove who's right, just who's left.
  16. Asking the wrong questions by irexe · · Score: 4, Informative

    From the article:

    How does software owned by everyone and by no one survive in a world where copyrights and patents shape the legal landscape?

    Shouldn't that be:

    how can copyrights and patents survive in a world where software is owned by everyone and by no one?

  17. Simple BSD allows rape by SmallFurryCreature · · Score: 4, Insightful
    Business doesn't want to be restricted, no minimum wages, maximum working hours, safety rules, GNU style licenses.

    The BSD license allows you to use the code without ever having to give back. Exactly the way business uses it.

    The only thing you need to know about BSD is that Microsoft favours it.

    --

    MMO Quests are like orgasms:

    You may solo them, I prefer them in a group.

    1. Re:Simple BSD allows rape by MsGeek · · Score: 4, Insightful

      Which is precisely why Microsoft has been pushing BSD licenses instead of the "viral" GPL. This Businessweek article is basically a truckload of astroturf on MS's behalf.

      --
      Knowledge is power. Knowledge shared is power multiplied.
    2. Re:Simple BSD allows rape by eviltypeguy · · Score: 5, Insightful

      "rape"...

      I write just about everything under a 3-clause BSD license. Do you know why? Because when I write something and give it away, it's really free to do whatever you want with (except of course claim it's your own).

      While some people think it's "rape", there are many of us who write code, that picked a BSD license because we want anybody to be able to use our code without restrictions other than claiming it's their own. So software can be a true gift without any "strings" attached. So it isn't "rape".

      Just the opinion of a programmer who writes BSD-licensed software...

  18. Slashdot Recommends License Switch for MSOffice by originalhack · · Score: 4, Funny

    Well, as long as the people that don't hold the copyrights are suggesting that those who do change their licenses, I think Slashdot should suggest that Microsoft switch the license for Office to (GPL or) BSD.

  19. Re:GPL affects patents issues by Bruce+Perens · · Score: 4, Insightful
    however, patents only affect commercial software.

    Sorry, but this is not the case. In the U.S., patents even effect use. Use is clearly given by the law as one of the acts for which the patent holder can bring suit. You are liable for patent infringement by software that you write and use privately in your own home.

    Yes, it's a broken system. We have to fix the law.

    Bruce

  20. Privatization wet dream by Lulu+of+the+Lotus-Ea · · Score: 4, Insightful

    I don't think the reporter's poor investigation has much to do with this piece. I'm not saying the "research" was any good--Bruce is probably right about the ignorance of Businessweek. But the knowledge part is kinda irrelevant.

    Instead, Businessweek, being what they are, is in the business of fantasizing about free giveaways to large companies. Sort of the Enron model of capitalism. What could Businessweek readers like more than a massive donation of free programming efforts into the private coffers of big business? Well, I suppose they like massive corporate welfare even more (the Haliburton model); but they'd certainly be happy to accept the free money of "privatized" Free Software.

    The patent issue is OF COURSE completely irrelevant here. Or maybe BSD-licensed software would be slightly more vulnerable to patent suits. But the difference is small, in any case. The main patent danger is big companies spending a lot more on lawyers than Free Software developers possibly can--and quite independent of the "merits" of patent claims, getting injunctions against Free Software.

    1. Re:Privatization wet dream by killjoe · · Score: 4, Insightful

      The funny thing is that the GPL only comes into play if you are modifying the source code AND redistributing it to third parties. What percent of corporate america does that? Maybe 1%?. For the 99 percent of corporations the GPL does not even apply. You don't have to agree with the GPL in order to USE software.

      --
      evil is as evil does
  21. Flawed assumption by Our+Man+In+Redmond · · Score: 4, Interesting

    This article stems from a flawed assumption, namely, that the Linux development team really cares whether businesses switch to Linux or not. Linux was written by people who wanted "software that doesn't suck," not people who thought "Hey, let's write a bunch of neat-o code and put it out there and maybe a bunch of businesses will be interested."

    In fact the article has it 100% backwards. Rather than Linux switching licenses to appeal more to the business crowd (which of course ain't gonna happen), business should start thinking of software in terms of software as a service -- not a web service, but a service like electricity or plumbing. Once that happens and businesscritters start realizing that you can use Linux in your enterprise without scaring off your employees or having to release all your internal software into the public domain, the arguments over lower TCO will start to take hold.

    --
    Someone you trust is one of us.
  22. I wrote to BW, and said this. by Markus+Registrada · · Score: 5, Interesting
    I'm afraid your columnist, Mr. Wildstrom (in "Big Fly", 8/13), has been taken in by some who envy the success of Linux and GNU Project software. Every success is dogged by advice to abandon the wellspring of that success. For Linux, that wellspring is the GNU General Public License. IBM could (and can) as easily adopt a BSD-based OS, just as Apple did. With the best legal advice available on the planet, IBM chose the GPL.

    The GPL has rarely been to court precisely because its implications are clear. Violators settle quickly because the alternative is to stop shipping product. Grumblings about "murky" license terms amount to nothing more than sour grapes.

    In any case, changing Linux's license is a practical impossibility. Hundreds of people and companies own bits of it, and all would have to agree to a change. Linux is condemned to retain the source of its success indefinitely.

  23. My favorite line by sean.peters · · Score: 4, Insightful
    Unfortunately, the GPL is hardly a model of clarity

    Hardly a model of clarity? It's one of the few license agreements that IANAL can understand without legal help!

    Here's another precious quote:

    "Some people argue that the GPL as a whole isn't even enforceable.... "

    Where "some people" == "Darl McBride", apparently.

    Sean

  24. I wrote a rebuttal to this on a mailing list by mav[LAG] · · Score: 4, Insightful

    Comments and clarifications welcome:

    Linux is burdened with too much intellectual-property uncertainty for
    many companies to embrace and develop it further


    This entire column is complete bollocks as I will now explain. (FLOSS = Free Libre and Open Source Software - remember folks, brush and FLOSS
    daily!)


    The open-source movement has had a remarkable run of success that has seen software such as the Linux operating system and the Apache Web server emerge as major challenges to Microsoft (MSFT ). However, the movement is now facing a crisis. At its heart is a question that has been around from the very beginning: How does software owned by
    everyone and by no one survive in a world where copyrights and patents shape the legal landscape?


    The same way it's always done - by being more reliable, more agile, better maintained and better supported. I'm also not sure how the author thinks that open source is not copyrighted - all of it is by definition.

    then owned by AT&T. Intellectual-property questions about Linux came to the forefront after the SCO Group (SCOX ), which acquired the Unix
    trademarks, launched a series of lawsuits against alleged infringers of its rights.


    Incorrect - SCO does NOT own the trademarks to Unix.

    POTENTIAL INFRINGEMENTS. The central case, a 2003 suit against IBM (IBM ), an important corporate promoter of Linux, has degenerated into
    a messy contract dispute with no intellectual-property issues left on the table. SCO's threats to sue companies that use Linux have almost entirely evaporated.


    Because they were and are lies. But the author is mistaken. There are "intellectual property" issues aplenty left on the table. IP - which is a lazy and meaningless term that conglomerates at least three kinds of entirely different sets of laws on intangible rights - is going to bite SCO severely because IBM is now suing it for distributing Linux without a license.

    But now another problem has surfaced. Open Source Risk Management, a new outfit that indemnifies its customers against infringement claims, found in a review of Linux code that the operating system potentially infringes on 283 patents. Although IBM declared it would make no
    effort to enforce its 60 patents involved, some are held by Linux foes, including 27 by Microsoft.


    Patents granted in its infinite stupidity by the US patent office. Maths should not be patented.

    The potential patent infringements pose no immediate threat to Linux. Such disputes typically take years to resolve, and courts rarely issue
    injunctions against alleged infringers. But the uncertainty is taking a toll. In the most significant response to date, the city government
    in Munich, Germany, has suspended a massive transition of desktop computers from Microsoft Windows to Linux, pending clarification of
    the patent situation (see BW Online, 8/9/04, "Will Legal Fears Freeze the Penguin?").


    Munich is going ahead.

    But open-source proponents also have to get their own intellectual-property house in order.

    Again - what is meant by intellectual property here? Does he mean copyrights? All FLOSS is copyrighted. Does he mean trademarked? The
    brands that matter are trademarked. Does he mean patented? Sorry but the vast majority of FLOSS developers don't really care whether the US
    allows the patenting of maths or not. If he's talking about "ownership" then he's wrong. As the SCO episode demonstrated, every single line of Linux can be accounted for - unlike many closed-source vendors.

    The development of open-source software is increasingly dominated by corporate interests that, one way or another, want to use Linux,
    Apache, and other open-source products to make money.


    No - it's the other way around. Businesses have to decide why and how they are going to use open source software to survive. Plenty already have decided to use it to make money and give b

    --
    --- Hot Shot City is particularly good.
  25. Re:And of course... by oolon · · Score: 5, Insightful

    I was just saying the GPL rather a good method for attracting contributions, not that it was the only way. Companies (who are the copyright owner) can even use it to showcase the code and allow commerical licencing to companies if required (trolltech for example). If trolltech offered a BSD version they would have never sold anything. XFree86 which was BSD had alot of problems attracting manufactures to contribute driver code, evenually having to go down the binary route as a result. GPL seems a better half way house to me... but thats me I like GPL alot more than BSD licence.

    James

  26. The irony here, of course... by Estanislao+Mart�nez · · Score: 5, Funny
    Switching to a BSD license will just encourage code forking which is bad.

    Which is exactly why there are like 50something different forked BSD systems, each of them unpredictably different from the next. Oh, wait, no.

  27. Re:And of course... by oolon · · Score: 5, Interesting

    Yes I see your point it was badly worded by me, there is no way to prove that the donations came cos of the GPL or just because it large. As clearly small projects are likely to attract less donations. However I do believe the GPL has helped attract contributions (both personal and corporate), as I believe the GPL offers better protection from the abuse of a gift of code. It is also interesting that BSD which was more advanced (some would claim still is) when Linux started yet failed to catch on. Perhaps that was more because of the development model rather than the license? As you point out, we can't know the answers.

    James