Slashdot Mirror


The Biggest Legal Danger For Open Source?

itwbennett writes "Brian Proffitt is blogging about the undercurrent of legal issues troubling the open source world these days and offers up this question: Are patents or copyright a bigger threat to the open source community? Patents are the obvious choice, with inflicting fear being the 'obvious intention of those who have instigated the various legal troubles on open source practitioners.' But the issue of copyright and copyright assignments is no less troublesome, argues Proffitt. And copyright assignment can be confusingly Machievllian, even in open source land."

161 comments

  1. Patents by afidel · · Score: 5, Insightful

    Because copyright can only cover a specific implementation but patents can now cover an idea in such a way that there is no alternative way to implement it. Not only that but all copyleft open source licenses actually rely on copyrights in order to make the mandates of the license enforceable.

    --
    There are 4 boxes to use in the defense of liberty: soap, ballot, jury, ammo. Use in that order. Starting now.
    1. Re:Patents by SilverHatHacker · · Score: 2

      That's it, end of discussion. No more comments are needed.

      --
      Funny may not give karma, but +5 Informative never made anyone snort coffee out their nose.
    2. Re:Patents by Firehed · · Score: 3, Insightful

      Exactly - copyleft is simply a (rather oddly named) type of license for copyrighted material. If you want to go all the way with open source by relinquishing copyright and releasing it to the public domain, you're giving up all rights on setting terms on how your code should be used.

      Copyrights are not bad things. Companies lobbying for infinite copyright length *cough*disney*cough* so that they can sit around and profit from decades-old content and not innovate or even produce new material are bad things. Never mind the whole cultural contribution aspect of copyright expiration.

      At least patents expire - although in software years they might as well go on forever. That's my biggest beef with (non-obvious) software patents in particular - the length of a patent term does not correspond with the useful lifetime of the product or its industry.

      --
      How are sites slashdotted when nobody reads TFAs?
    3. Re:Patents by afidel · · Score: 1

      Well, the LZW patent did expire just before GIF's became fairly outmoded so it IS possible for a patent to expire while the idea is still useful, it's just rare =)

      --
      There are 4 boxes to use in the defense of liberty: soap, ballot, jury, ammo. Use in that order. Starting now.
    4. Re:Patents by QuantumG · · Score: 1

      Patents that are actually developed into something useful in their enforcement lifetime.. sure.. but there's plenty of patents that are simply uneconomical to implement so long as you have to include legal costs into the budget. When the patent expires the cheap operators are free to investigate how to make actual products from it.

      Of course, for many industries the cheap operators are in China, and they don't tend to take much notice of patents either way. (god bless em).

      --
      How we know is more important than what we know.
    5. Re:Patents by larry+bagina · · Score: 1

      GIF's are still relevant for animation.

      --
      Do you even lift?

      These aren't the 'roids you're looking for.

    6. Re:Patents by Sarten-X · · Score: 1

      Patents do not cover "an idea". They cover a specific solution, which for software is a specific algorithm. Find a different algorithm to produce the same (or similar enough) results, and the patent isn't an issue. Yes, that's a problem when you want to exactly duplicate some function (like with a compression codec), but for the vast majority of applications, the algorithms used are well-known and not patented. Once in a great while, some brilliant algorithm will be discovered for doing something that isn't specialized, but in the vast majority of such cases, those algorithms come after years of research work and refinement. Why shouldn't the thinker have some control over their thoughts?

      Copyright is indeed what protects open-source software, but the other details are where trouble lies. Contributors to open-source projects must declare that the copyright on their work belongs to the project. That means it can't be itself copied from somewhere else without license (including tutorials, sample code, etc.). If that assignment isn't made, then any change in the project's licensing requires the approval of all the submitters!

      --
      You do not have a moral or legal right to do absolutely anything you want.
    7. Re:Patents by CastrTroy · · Score: 1

      To be fair to Disney, although they do push for longer copyrights, they certainly haven't stopped creating new content, nor have they stopped contributing to culture. While, yes, they are profitting from decades old creations, by reselling the same movie in a new format ever 10 years, they probably are one of the more creative companies out there today.

      --

      Anthropic principle: We see the universe the way it is because if it were different we would not be here to see it.
    8. Re:Patents by Anonymous Coward · · Score: 0

      Yes, that's how it should work. But it doesn't. And how come "for the vast majority of applications, the algorithms used are well-known and not patented"? That is surely going to change soon.

    9. Re:Patents by airfoobar · · Score: 1

      Patents do not cover "an idea". They cover a specific solution, which for software is a specific algorithm.

      Alas, only in theory. Broad or trivial patents are a real problem and a real danger. Software patents can cover anything from a GUI (see: Microsoft vs everyone using Android) to an "algorithm" to blink a cursor (see: Amiga).

    10. Re:Patents by c0lo · · Score: 1

      Contributors to open-source projects must declare that the copyright on their work belongs to the project. That means it can't be itself copied from somewhere else without license (including tutorials, sample code, etc.). If that assignment isn't made, then any change in the project's licensing requires the approval of all the submitters!

      Must? Why? The alternative of "or the change in project's licensing must require the approval of all accepted submitters" seems fine with me. See, as a hypothetical submitter, I might dislike not being consulted would the licensing be changed. On the other side, being required to assign the copyright to the project just from the start is just a fair request: given that I know the condition from the start, I can decide whether or not I want to contribute.

      In this regard, my point is: this is a non-story - I don't see how the land-scape of open-source is threatened by Canonical's request for copyright attribution: it is playing by a fair set of rules and Canonical will live-or-die by this rule - if too many contributors wouldn't like it, Shuttleworth would be facing sustaining the effort all by himself (by hiring developers).
      In other words, since the "copyright assignment" doesn't make the Open Source less open than it is right now (the contributor still has the freedom to accept or reject it), just where is the threat?

      --
      Questions raise, answers kill. Raise questions to stay alive.
    11. Re:Patents by davester666 · · Score: 1

      But Hitler demands further comment!

      --
      Sleep your way to a whiter smile...date a dentist!
    12. Re:Patents by ozmanjusri · · Score: 4, Insightful

      end of discussion. No more comments are needed.

      Not quite.

      Malevolent organisations which don't respect community commons are the threat. Patents are just one of their tools.

      Until those organisations are reigned in, they will continue inventing ways to diminish the value of projects which threaten their income.

      --
      "I've got more toys than Teruhisa Kitahara."
    13. Re:Patents by angloquebecer · · Score: 1

      Patents do not cover "an idea". They cover a specific solution, which for software is a specific algorithm.

      Except we see increasingly generic software patents being approved all the time.

      Find a different algorithm to produce the same (or similar enough) results, and the patent isn't an issue.

      Except this isn't true in the real world. Patent lawsuits can be filed before any source code is subpoenaed. As long as the end product (read running binary) appears to infringe upon a patent, then the actual underlying algorithms don't mean anything.

      Once in a great while, some brilliant algorithm will be discovered for doing something that isn't specialized, but in the vast majority of such cases, those algorithms come after years of research work and refinement. Why shouldn't the thinker have some control over their thoughts?

      Because algorithms themselves are nothing more than math. Trade secrets and copyright on the original source code should be the only protection warranted on original algorithms.

    14. Re:Patents by Master+Moose · · Score: 3, Interesting

      nor have they stopped contributing to culture.

      Me thinks you have never seen an episode of Hannah Montana.

      --
      . . .gone when the morning comes
    15. Re:Patents by rolfwind · · Score: 1

      GIFs are still overused for animation.

      FTFY.

    16. Re:Patents by geminidomino · · Score: 4, Informative

      Patents do not cover "an idea". They cover a specific solution, which for software is a specific algorithm

      Reality doesn't mesh with your statement.

      One-click, anyone?

    17. Re:Patents by eh2o · · Score: 2

      Find a different algorithm to produce the same (or similar enough) results, and the patent isn't an issue.

      This is only true if the output product of an algorithm is itself not patentable (e.g. it is obvious, not novel, etc), in which case someone is just wasting time and money on the patent process anyways.

      Otherwise, according to the doctrine of equivalence an alternative algorithm will still be infringing if it produces identical results. For example its not possible to patent "a compression algorithm" but if someone had a patent on an algorithm for producing a specific kind of compressed data structure (e.g. MP3), it would be infringing to use an alternative algorithm that produced identical (or substantially similar) output. That alternative algorithm might actually be useful and is in fact patentable, for example if it was faster, more reliable, etc., but the patent holder would still have to license the original algorithm first to practice the invention (as it is deemed an improvement over a prior art so it is dependent on that). A patent does not necessarily grant the right to practice the invention.

      Note there may be significant differences in the interpretation of the doctrine of equivalents depending on jurisdiction (see Wikipedia).

    18. Re:Patents by nitehawk214 · · Score: 5, Funny

      nor have they stopped contributing to culture.

      Me thinks you have never seen an episode of Hannah Montana.

      Contributing to the demise, is still contributing.

      --
      I'm a good cook. I'm a fantastic eater. - Steven Brust
    19. Re:Patents by westlake · · Score: 1, Interesting

      Companies lobbying for infinite copyright length *cough*disney*cough* so that they can sit around and profit from decades-old content and not innovate or even produce new material are bad things.

      I wonder.

      The Disney archives are essentially intact -

      down to the fragile matte paintings on glass used in films like Bambi.

      Amazon.com lists over 3,600 live action and animated titles distributed by Walt Disney Studios Home Entertainment. Most are quite reasonably priced.

      Print quality is uniformly excellent and restoration is not dependent on scratching and clawing out funds from a dozen foundation grants.

      Preservation does not happen unless there is there is the will and the money to make it happen.

    20. Re:Patents by Anonymous Coward · · Score: 0

      Why shouldn't the thinker have some control over their thoughts?

      Why shouldn't the thinker have some control over your thoughts?

      FTFY

    21. Re:Patents by burnin1965 · · Score: 1

      In TFA he doesn't actually state what the risk is with copyrights but I assume the risk is that developers who contribute code to a project may be angered by the choice of licensing used by the project and will no longer contribute to the project. The only example provided in the article mentions some vagueness in the Ubuntu project licensing terms that suggest Canonical may license contributed resources under a license of their choice.

      It doesn't seem like much of a risk, it's not as if Ubuntu is the only game in town for open source contributors.

      The other issue, software patents, are a risk for all businesses whether they develop or just use closed source or open source software.

    22. Re:Patents by Anonymous Coward · · Score: 0

      Sorry, but copyrights are bad things.

      Can you give a coherent justification for copyright law, other than as a concession to the publishing industry to get your laws affecting them passed? (Because that's how it all got started...)

    23. Re:Patents by Anonymous Coward · · Score: 0

      Javascript and png's are much better.

    24. Re:Patents by cmburns69 · · Score: 3, Funny

      I read that as:

      But Hitler demands furher comment!

      (it would have been a delightfully painful pun)

      --
      Online Starcraft RPG? At
      Dietary fiber is like asynchronous IO-- Non-blocking!
    25. Re:Patents by Nursie · · Score: 1

      "Contributors to open-source projects must declare that the copyright on their work belongs to the project. That means it can't be itself copied from somewhere else without license (including tutorials, sample code, etc.). If that assignment isn't made, then any change in the project's licensing requires the approval of all the submitters!"

      Wait, you see this as a bug?

      I see it as a feature. If I contribute to a project then I don't want some arbitrary group of people on a committee at a later point in time to be able to decide that it's in the project's best interests to close the source, or (for instance) switch GPL to MIT license, or whatever else, without my say so or removing my code.

    26. Re:Patents by Anonymous Coward · · Score: 1

      All I'm getting from this is that the biggest threat to Open Source projects is the Free Market.

    27. Re:Patents by darkwing_bmf · · Score: 1

      Honestly, copyleft is just as bad as any other kind of copyright. You're basically ensuring other software writers can't make a profit on improving the program itself.

      Here's how it should be done... and this can work without any kind of copyright protection whatsoever. You write a program and sell as many copies as people will buy. Keep the source code a trade secret. When sales drop and you no longer feel like supporting it you release the code base to the public domain. Someone else comes along and improves that and makes a better program, sells it without releasing source right away, makes money and then, once they feel they've gotten what they can out of it, releases *that* source to the public domain so the next person or group can take over. Right now, most commercial software firms and even individuals won't touch copyleft because there's no way to make money from the software itself if you give away the source that can be distributed freely (exceptions are support contracts, specialized hardware and single customer... but those are very narrow niche cases).

    28. Re:Patents by rtb61 · · Score: 2

      Nah, the biggest threat to open source has always be FUD 'fear, uncertainty, doubt', also known as scary bullshit, spread by closed source proprietary software companies who have achieved data lock in, all looking to protect their inflated profit margins.

      Open source sofftware has been around for a long time now, been tested under fire from M$ 'it's a cancer', 'terrorists use it', 'software hackers prefer it' (that was a big fail ie it was more secure), 'it is communist', 'it is like a virus infecting everything it touches','it is too hard to use','it costs to much'(TCO B$) and, of course patent and copyright B$ up the wazoo.

      In fact this kind of FUD has been pretty rare with regard to open source for quite some time, some big software supply contracts must be up for renewal and they are hoping mass media will run with the latest ohh scary open source software caimpagn.

      --
      Chaos - everything, everywhere, everywhen
    29. Re:Patents by Anonymous Coward · · Score: 1
      Naturally.

      You're a Microsoft shill. You're paid to denigrate open source.

    30. Re:Patents by dryeo · · Score: 1

      Can't they just get a new copyright on the restored print? With a short copyright term this would motivate them to restore and rerelease. And their archives are theirs whether they are copyrighted or not as they are physical possessions.

      --
      https://en.wikipedia.org/wiki/Inverted_totalitarianism
    31. Re:Patents by dryeo · · Score: 1

      Be OK if the source was actually released to the public domain but I'd guess that peoples pack-rat habits would kick in and they'd keep the source secret just in-case a use materializes.

      --
      https://en.wikipedia.org/wiki/Inverted_totalitarianism
    32. Re:Patents by Pentium100 · · Score: 1

      So, which forum allows me to embed Javascript in my posts and then run it?

    33. Re:Patents by Jaxoreth · · Score: 1

      To be fair to Disney, although they do push for longer copyrights, they certainly haven't stopped creating new content, nor have they stopped contributing to culture. While, yes, they are profitting from decades old creations, by reselling the same movie in a new format ever 10 years, they probably are one of the more creative companies out there today.

      Case in point: The story following this one is about Tron: Legacy, a Disney film.

      --
      In general, it is safe and legal to kill your children. -- POSIX Programmer's Guide
    34. Re:Patents by silanea · · Score: 1

      Copyright is indeed what protects open-source software, but the other details are where trouble lies. Contributors to open-source projects must declare that the copyright on their work belongs to the project. That means it can't be itself copied from somewhere else without license (including tutorials, sample code, etc.). If that assignment isn't made, then any change in the project's licensing requires the approval of all the submitters!

      You do realise that this is not a "problem" or a bug in the way copyleft is handled but an intended feature? People who contribute to a FOSS project do so under agreed-upon terms. If the terms change, the agreement has to be renewed.

      Besides, many projects successfully went from GPLv2 to v3, OpenStreetMap is in the middle of a license change, Wikipedia is phasing out GFDL in favour of a CC license. It is doable, though it certainly adds complexity for large projects. But again: That is not a bug, it is a feature.

      --
      Rudolf Hess edited Mein Kampf. He was the very first grammar nazi.
    35. Re:Patents by squizzar · · Score: 1

      Many of their biggest successes as films (or at least the underlying ideas for them) are based on fairy tales and folk stories that are out of copyright. The hypocrisy of them fighting so that no work they 'create' can ever be used in the same way is astonishing.

    36. Re:Patents by gerddie · · Score: 2

      Care to explain how patents make a "Free Market"? Oh you're an AC, nevermind ...

    37. Re:Patents by Sarten-X · · Score: 1

      How I see it depends entirely on what hat I'm wearing at the time.

      As a submitter myself, I see it as a boon. As a manager of a project, I see it as a headache. As an advocate of open-source software, I see it as yet more FUD I have to waste my time explaining to some company who's concerned about wasting resources without profit.

      --
      You do not have a moral or legal right to do absolutely anything you want.
    38. Re:Patents by DarwinSurvivor · · Score: 1

      I guess you don't live in one of the many countries that don't recognize software patents in the first place. Then again, I like having copyrights on software. It means that big companies can't steal a smaller company (or invididual)'s work and profit from it. Copyrights are also VERY different in that if you can show that you developed your software with no prior knowledge of someone else's software implementation, then you are in no way infringing on their copyright. Patents on the other hand can get you sued even if you had no idea that patent even existed.

    39. Re:Patents by Chrisq · · Score: 2

      All I'm getting from this is that the biggest threat to Open Source projects is the Free Market.

      A really free market wouldn't have patents or copyright.

    40. Re:Patents by smacinn · · Score: 1

      but he provided a solution for that as well in his signature: There are 4 boxes to use in the defense of liberty: soap, ballot, jury, ammo. Use in that order. Starting now.

    41. Re:Patents by mangu · · Score: 1

      If "Tron: Legacy" is new content then why cannot I make a "Steamboat Willie: Legacy" film?

    42. Re:Patents by Grismar · · Score: 1, Interesting

      You're effectively arguing: "Patents don't kill open source, people do".

      This statement is true in the same way as the guns-related one, and it detracts from the discussion at hand in the same way the guns-related one does.

      A decent illustration of how this is irrelevant and counterproductive here http://www.huppi.com/kangaroo/L-gunskill.htm and I'm sure the /. readership has no problems translating this example to the open source domain.

    43. Re:Patents by jonamous++ · · Score: 1

      What are you talking about? With most open source licenses, I can sell it as-is as long as I make the source code available. I can modify it to my heart's content and sell that modified version. If everyone followed your model, things like GNU/Linux would never exist. We have companies like Red Hat raking in $900m+, certainly making a profit, using software that isn't theirs (copyleft software).

    44. Re:Patents by Anonymous Coward · · Score: 0

      I counter with Phineas and Ferb.

    45. Re:Patents by JasterBobaMereel · · Score: 1

      Like :

      Winnie the Pooh - Bought the rights for a pitance, and copyrighted thier version ...so the original cannot complete
      Aladdin/Little Mermaid/etc .etc ... - Used very well known ancient story, and copyrighted thier version and sue anything remotely like it

      Most disney TV is cable TV filler and not worth watching....not exactly creative genius

      --
      Puteulanus fenestra mortis
    46. Re:Patents by jellomizer · · Score: 2

      So if you disagree with an idea then you are Malevolent?
      I work for a company that writes closed source software. It it was Open Source I wouldn't have this job. We copyright and patent our work primarily so a competing company who is bigger then us wont steel our work. The fact that it is preventing Open Source software is not a consideration, it is just a side effect. However our company does actively respect Open Source. We use their tools, and give back to their community for the tools we find useful. As well we are quite careful not to mix licences that are incompatible with ours.
      We respect Open Source however we will not let it get in away of our business model. And as someone with a family to feed I am glad of that. the OSS model reduces the number of ways you can profit off of your work.

      --
      If something is so important that you feel the need to post it on the internet... It probably isn't that important.
    47. Re:Patents by w_dragon · · Score: 1

      And you're free to go make a movie based on the same folk stories and fairy tales. In many cases you can even use the same title as they did since the title is just the name of the fairy tale and can't be copyrighted. There are several non-Disney Cinderella movies. You can't use their artwork or their modifications to the stories, but you can certainly use the same source material for the story.

    48. Re:Patents by w_dragon · · Score: 1

      Selling is kind of pointless if part of the license you agree to is to allow your users to redistribute so long as they also provide the source.

    49. Re:Patents by Anonymous Coward · · Score: 0

      The Lion King is plagiarism of a Japanese Classic still in copyright. Oh, and they also threw lemmings of a cliff in order to make a documentary. Someone remind me what did Disney ever do that wasn't completely evil?

    50. Re:Patents by Anonymous Coward · · Score: 0

      I guess you've got me there. No more obnoxious postage stamp sized dancing cats and women't boobs bouncing up and down. Tragic.

    51. Re:Patents by Raumkraut · · Score: 2

      Trademark law.

    52. Re:Patents by TheVelvetFlamebait · · Score: 1

      Companies lobbying for infinite copyright length *cough*disney*cough* so that they can sit around and profit from decades-old content and not innovate or even produce new material are bad things.

      I agree with you, without a shadow of a doubt, that these companies are "bad things", but I don't think that lack of innovation or the risk of not creating new material. Disney will always produce new material, because children will always want new material (perhaps production might slow slightly, but that would be about it). I don't think indefinite copyright would change that (has changed that?). Disney will similarly not innovate, because children don't need them/don't want them to innovate. Besides, I don't see how limited copyright terms would change any of that either.

      No, the reason, as far as I'm concerned that these companies are "bad things" (aside, of course, from their creepy influence on the government), is that the culture is not theirs, but ours. We grew up on their material, and it's a part of our lives and our pasts. We have sat patiently on our hands while companies wring every last piece of financial value from these works, on the condition that it becomes ours after a reasonable amount of time. While it's new and most profitable, sure, they deserve the first couple of slices for helping facilitate its existence. But when the public's cash has moved on to the next latest thing, it should become completely our own, for us to share and use as we see fit. Or, if the public's cash doesn't move on, then it's pretty clear that the work in question is already an important part of our culture, and should be liberated.

      We can all win; the companies, the artists, and the public. It is possible. Companies and artists can make a mint of popular works, and we can have eventual ownership over our culture. I wish that people would realise this, because then politicians might pay attention. For a politician, fear for their job trumps lobbying every time. After all, how can they be lobbied if they have no power?

      --
      You know, there is a difference between trolling and pointing out the flaws in your reasoning. Just saying.
    53. Re:Patents by Anonymous Coward · · Score: 0

      Reined in, not reigned.

        A king reigns over his people, the big bully. But when a horse runs out of control, you take the reins, and you rein him in.

      There's a g in the one about (g)overnment.

    54. Re:Patents by darkwing_bmf · · Score: 1

      Red Hat makes its money from support contracts. I already said that was a niche market exception. If you were a software developer would you sell software you spent years to create to a person for $30 if that person could turn around and legally give copies away to the rest of the world for free?

    55. Re:Patents by jonamous++ · · Score: 1

      Please go to red hat's web site and download a copy of RHEL for free; just tell them you don't want support. Won't that work? No? How are they still in business with companies like Oracle taking their software, rebranding it, and selling it? The point is, it can be done. Does that mean it is a great business model? No. I work for a software company and our business would fail if we licensed our software under GPL (mainly because our competitors would be able to take code that was difficult to develop in order to comply with government regulations).However, even under a "public domain after you've squeezed the money out" model, we would never release our software because we are continually building on it. It's the core of our business.

    56. Re:Patents by darkwing_bmf · · Score: 1

      Would you use open source software if it meant you'd have to make your own source open? Of course not. That's the problem I alluded to in my original reply.

    57. Re:Patents by cdrguru · · Score: 1

      You can bet that the budget assigned to new work is figured on the basis of not only how much it will bring in the first week but also how much they will be able to continue to bring in over five or ten years.

      Widespread, pervasive piracy hasn't really hit Disney yet. When we get 30-something mothers downloading (and seeding) torrents for Disney videos so their children can watch them the revenue stream will dry up and they will only be able to spend a far, far less amount producing movies.

      This is beginning to be felt in Hollywood already and will only get worse. There is no point in spending 100 million on a movie that in 1990 would have brought in 150 million in theater sales and another 100 million in DVD sales when they get 60 million in theater sales and $8 in DVD sales - sell one and it is immediately pirated and available planet-wide.

      It isn't that there is no more revenue, it is that the pie shrinks and the duration is vastly shortened.

    58. Re:Patents by cdrguru · · Score: 1

      But just think of the revenue in making an animated XXX feature staring Mickey Mouse! I know you want to see what Minny has under that skirt.

      I have a deep suspicion that there are still Disney executives that have been having nightmares about "Deep Throat Minny" since around 1974.

    59. Re:Patents by Jaxoreth · · Score: 1

      If "Tron: Legacy" is new content then why cannot I make a "Steamboat Willie: Legacy" film?

      You're assuming that the original Tron was not also a Disney film. It was.

      --
      In general, it is safe and legal to kill your children. -- POSIX Programmer's Guide
    60. Re:Patents by Aldenissin · · Score: 1

      Apparently the Slashdhot readership aren't happy to do your job of making your point, because they agree that people kill people and that guns are just a tool. Nothing more. Proprietary software and ideologies are a tool as well. But it doesn't have good purposes, like hunting or defense, and that is where the analogy you made breaks down.

      --
      Like a city whose walls are broken down is a man who lacks self-control.
    61. Re:Patents by WorBlux · · Score: 1

      Not having slaves reduces the number of ways you can make a profit from cotton farming.

      A utilitarian argument here misses the point. Malevolence often though not always has a material benefit to the evil-doer, and also incidental niche benifits for others.

      Even then as a utilitarian argument it fails because it addressees only the seen and easily recognizable, and not the unseen and hidden. The cost of litigating and defending patents increases the cost of everything in the computer industry by about 10%. This isn't even adding in the costs and burdens upon the general public from the monopoly rents that result.

      It's not the disagreement that's malevolent, or even not releasing your source code. It's reliance on political pull and privileged to stop competition, quash innovation, and extract two decade of monopoly rents based on broad and vague claims in an area of endeavor which is extremely precise and accurate.

    62. Re:Patents by WorBlux · · Score: 1

      . Once in a great while, some brilliant algorithm will be discovered for doing something that isn't specialized, but in the vast majority of such cases, those algorithms come after years of research work and refinement. Why shouldn't the thinker have some control over their thoughts?

      Because algorithms are math.

      Also here you are conflating the specific with the general.

      A thinker does and should have control other their own thoughts. However once you publish it (make public) and I have my own specific thought and it is mine. That it follows the same general form of your thought is irrelevant.

    63. Re:Patents by psxndc · · Score: 1

      The cost of litigating and defending patents increases the cost of everything in the computer industry by about 10%. This isn't even adding in the costs and burdens upon the general public from the monopoly rents that result.

      Cite please.

      --

      The emacs religion: to be saved, control excess.

    64. Re:Patents by psxndc · · Score: 1

      How specific do you expect a claim to be? Seriously. Below is claim 1 of the one-click patent. What do you want to see there: "on a Unix-based system?" "Wherein the component is coded in Java"? Everything is identified in the specification, so there is a finite number of what things like an "identifier" can be (or an equivalent). So please, tell me what else there needs to be according to you to convert this from being an idea to specific solution.

      1. A method of placing an order for an item comprising:
      under control of a client system, displaying information identifying the item; and in response to only a single action being performed, sending a request to order the item along with an identifier of a purchaser of the item to a server system;

      under control of a single-action ordering component of the server system, receiving the request;

      retrieving additional information previously stored for the purchaser identified by the identifier in the received request; and

      generating an order to purchase the requested item for the purchaser identified by the identifier in the received request using the retrieved additional information; and
      fulfilling the generated order to complete purchase of the item whereby the item is ordered without using a shopping cart ordering model.

      --

      The emacs religion: to be saved, control excess.

    65. Re:Patents by jellomizer · · Score: 1

      Not really. You Analogy is wrong.
      The removal of slavery doesn't stop the sale of cotton, or the way that people sell cotton. It only changes the process that cotton was made. Open Source is more like you must give away your cotton for free however you may charge for shipping and other value add services, however anyone can go to your farm and pick up their own bails of cotton for free.

      So if your business was based on just picking cotton and storing where someone else bought it from you and picked it up themselfs you are screwed. The abolishment of slavery could possible added an additional cost to production, but that will just cause the cost of the product to rise.

      --
      If something is so important that you feel the need to post it on the internet... It probably isn't that important.
    66. Re:Patents by WorBlux · · Score: 1

      To start, 16 billion in litigation costs. http://papers.ssrn.com/sol3/papers.cfm?abstract_id=983736 And in cost of legal work in filing, royalties. Plus costs that aren't easily quantified, the R+D needed to invent around a patent. A greater emphasis on applied rather than pure science, and the cost of monopoly rents on the consumer.

    67. Re:Patents by WorBlux · · Score: 1

      No, my analogy isn't wrong, you've just missed the point of it. The point is that a utilitarian argument doesn't settle the question of malevolence, neutrality, or beneficence, especially a utilitarian argument which fails to be catholic in it's analysis.

      Also the issue is patents, not open source. Even if there were no patents, or even no copyrights, there is still no reason why you couldn't keep your source secret.

    68. Re:Patents by geminidomino · · Score: 1

      I don't have to. My assertion is already backed up by the fact that someone else implemented it differently (Barnes and Noble, maybe? Not sure) and was enjoined/sued by Amazon based on said patent.

      Again, reality says you're mistaken.

    69. Re:Patents by psxndc · · Score: 1

      Ah the old "I don't have to back up my position because I can vaguely allude to some anecdote" defense that Aristotle and Plato often used. Well played sir, well played.

      --

      The emacs religion: to be saved, control excess.

    70. Re:Patents by psxndc · · Score: 1

      I'm still working my way through the paper you cited, but complaining about the R&D costs needed to invent around a patent?! That's the whole point! They cause further research. That's how they "promote the Progress of Science and useful Arts."

      --

      The emacs religion: to be saved, control excess.

    71. Re:Patents by syockit · · Score: 1

      Yeah, I suppose humanity needed to find out many other ways to invent the wheel.

      --
      Democracy is for the people; you only vote once per season and we'll do the rest of the work for you don't have to.
    72. Re:Patents by geminidomino · · Score: 1

      Uh. I did back up my position. With facts.

      Your opinion is that the one-click patent was not overbroad and covered only a specific implementation. I provided a reference to a real, actual, legal decision that said you were wrong. How is that not backing up my position?

      Troll.

    73. Re:Patents by psxndc · · Score: 1

      Today's wheel - spokes, rims, inflatable - is very different than the first wheel made of stone.

      --

      The emacs religion: to be saved, control excess.

    74. Re:Patents by psxndc · · Score: 1

      First of all, I'm not trolling. I asked you what the claim needed to cover a specific implementation under your definition. You didn't respond to that at all.

      Instead, you made a vague reference to some case - that you're not even sure of the defendant - where the company was accused of infringement. And even IF they were found to infringe, you still provided NO analysis or commentary as to how similar or dissimilar the defendants system was compared against what was described in the patent. Based on the "facts" you've provided so far, Barnes and Noble (?) could have copied the source code verbatim from Amazon. But - under your premise - because they are different company, if Amazon's patent covered them, then it must be overbroad and is just covering an idea.

      Lastly, saying "someone-question mark was enjoined" is not citing to a real, actual, legal decision.

      ProCD, Inc. v. Zeidenberg, 86 F. 3d 1447 (7th Cir. 1996) (holding that click through EULAs are enforceable).

      THAT's citing a real, actual, legal decision.

      --

      The emacs religion: to be saved, control excess.

    75. Re:Patents by Anonymous Coward · · Score: 0

      I'm still working my way through the paper you cited, but complaining about the R&D costs needed to invent around a patent?! That's the whole point! They cause further research. That's how they "promote the Progress of Science and useful Arts."

      And if that kid just kept breaking windows all over town, the economy would be booming!

      http://en.wikipedia.org/wiki/Parable_of_the_broken_window

    76. Re:Patents by WorBlux · · Score: 1

      Doing exactly the same thing in a roundabout way isn't exactly innovation. Rube Goldberg machines are cool in all, but nobody really wants to use one every morning to fry an egg. To really innovate you should implement the best known technology in a better way. Take the example or Watt's engine and patents. The engine didn't particularly improve or gain a widespread use until after the patents had expired. R&D to get around a patent is R&D that could have been dedicated to improving the best known practice rather than trying to come up with a good-enough practice.

  2. Patents. by RyuuzakiTetsuya · · Score: 1

    Copyrights are a big threat, but, ultimately unless the open source project is funded by some pretty well off corporate backers, patents represent a far greater threat. Copyright issues can be avoided with the proper licensing agreements. Whether it be the LGPL, GPLv2, v3, BSD, etc.

    Patents on the other hand can stop a project cold.

    --
    Non impediti ratione cogitationus.
  3. I only have 2 things to say to Brian Proffitt by syousef · · Score: 0

    Proffitt? Dude, SAY it don't SPRAY it.

    And anyway you forgot. 1. and 2. Only when you get to 3. can you Proffitt!

    --
    These posts express my own personal views, not those of my employer
    1. Re:I only have 2 things to say to Brian Proffitt by Samantha+Wright · · Score: 4, Funny

      Here's a better joke using the same material.

      Threats to open source:

      1. Patents
      2. Copyrights
      3. ???
      4. Proffitt!
      5. Other bloggers.

      --
      Bio questions? Ask me to start a Q&A journal. Computer analogies available for most topics!
    2. Re:I only have 2 things to say to Brian Proffitt by AstrumPreliator · · Score: 1

      I think I've been hanging around /. for far too long. The first thing I thought about doing after reading that guys last name was making a list like you did...

    3. Re:I only have 2 things to say to Brian Proffitt by syousef · · Score: 1

      I wasn't aiming for high brow humour. I don't think that was any funnier than what I said. And you completely missed out "say it don't spray it' (which was my original joke...the 1. 2. 3. thing was just tacked on). Frankly. I think your post got the rating more due to reverse sexism than anything else...*shrug*

      --
      These posts express my own personal views, not those of my employer
    4. Re:I only have 2 things to say to Brian Proffitt by Samantha+Wright · · Score: 2

      Who knows! Personally I'd like to think it was the base appeal to memes, and perhaps my half-hearted attempt at acting like I had some kind of textbook answer.

      --
      Bio questions? Ask me to start a Q&A journal. Computer analogies available for most topics!
    5. Re:I only have 2 things to say to Brian Proffitt by Aldenissin · · Score: 1, Funny

      Mod her, I mean *cough* "parent" up! Oh, and by the way, will you marry me?

      --
      Like a city whose walls are broken down is a man who lacks self-control.
    6. Re:I only have 2 things to say to Brian Proffitt by CrashandDie · · Score: 1

      So first you call her mommy, then ask her to marry you?

      Kinky. I like it.

  4. Its all about money by Wolfling1 · · Score: 1

    Open Source generally doesn't have a bankroll funding it. It has a community. Communities of like-minded individuals don't usually have the finances or the will to defend (or instigate) legal battles.

    As they say, "You will never know who was really right. But you will know who had more money."

    1. Re:Its all about money by c0lo · · Score: 1

      Open Source generally doesn't have a bankroll funding it. It has a community. Communities of like-minded individuals don't usually have the finances or the will to defend (or instigate) legal battles.
      As they say, "You will never know who was really right. But you will know who had more money."

      Don't bet on it: communities of like-minded individuals may have enough money to sustain a "legal arm" to protect them - e.g. EFF

      EFF is a donor-funded nonprofit and depends on your support to continue successfully defending your digital rights. Litigation is particularly expensive; because two-thirds of our budget comes from individual donors, every contribution is critical to helping EFF fight — and win — more cases

      --
      Questions raise, answers kill. Raise questions to stay alive.
    2. Re:Its all about money by M.+Baranczak · · Score: 1

      If this was true, Open Source would have been dead years ago.

      1: There are, in fact, large companies bankrolling it. Ever heard of IBM? RedHat? Novell? Canonical? Sun... OK, forget that last one.

      2: See the other response, regarding the EFF. There are now a lot of individuals and businesses that depend on Open Source to make a living. If someone threatens that, there's a good chance they'll fight back.

    3. Re:Its all about money by Chrisq · · Score: 1

      Sun... OK, forget that last one..

      Which illustrates how fragile this support is. If someone doesn't like an open source area they can just buy the company behind it, and the FUD will scare people away from the project

  5. Proffitt's oppinnionns...... by MrEricSir · · Score: 2

    ......maayy suufferr frromm aa sttuuckk kkeyyboaardd annd//orr mminddssett.

    --
    There's no -1 for "I don't get it."
  6. Backwards. by Anonymous Coward · · Score: 0

    I would argue that open source is a danger to patents and copyright, not the other way around.

  7. What about THE BSA who may count by system by Joe+The+Dragon · · Score: 1

    What about THE BSA who may count by system even when windows is not on them.

    1. Re:What about THE BSA who may count by system by Anonymous Coward · · Score: 0

      lolwut?

    2. Re:What about THE BSA who may count by system by Anonymous Coward · · Score: 0

      lolidiot

  8. Step 3 by Anonymous Coward · · Score: 1

    1 - Make blog with ads
    2 - Get slashdotted
    3 - Proffitt

  9. Who the hell is Brian Proffitt? by Anonymous Coward · · Score: 0

    Who the fuck is Brian Proffitt? What are his credentials? Has he done anything of note?

    1. Re:Who the hell is Brian Proffitt? by Samantha+Wright · · Score: 2

      Yes! His resume is here. Major career highlights include getting mentioned in Slashdot summaries, and getting mentioned in Slashdot summaries.

      --
      Bio questions? Ask me to start a Q&A journal. Computer analogies available for most topics!
    2. Re:Who the hell is Brian Proffitt? by fostware · · Score: 1

      1. Keep getting mentioned in Slashdot summaries
      2. ?????
      3. Proffitt!!!!

      --
      "We know what happens to people who stay in the middle of the road. They get run over." - Aneurin Bevan
  10. logo: prior art exists by Anonymous Coward · · Score: 0

    you can't trademark that green sorta-circle, because that is the pattern made by "magic eye" tubes from the 1930s with no grid voltage.

  11. Renegging on the GPL by QuantumG · · Score: 1, Interesting

    Ok, patents are the biggest threat, but here's another.

    Suppose Larry decides he's not happy with just changing the license on one of the dozens of open source products he's acquired and decides to actually start demanding payment for use of earlier versions of the software.. Does a copyright owner have the legal right to retract an issued license? Does that right apply to the GPL? This is a massive blindspot in copyright law.

    --
    How we know is more important than what we know.
    1. Re:Renegging on the GPL by Anonymous Coward · · Score: 1

      No. No. No it isn't.

    2. Re:Renegging on the GPL by afidel · · Score: 2

      A) Unless they are the sole copyright holders (not feasible for any decent scale project unless you ask for assignment of copyright like the FSF does) then they can't change the license.

      B) It's generally understood that the GPL is non-revocable for that existing codebase and any forks but AFAIK that assumption has never been tested in court because sole rights holders are so rare for anything that matters.

      --
      There are 4 boxes to use in the defense of liberty: soap, ballot, jury, ammo. Use in that order. Starting now.
    3. Re:Renegging on the GPL by Anonymous Coward · · Score: 0

      The answer is "no". The GPL was written to prevent this.

    4. Re:Renegging on the GPL by Anonymous Coward · · Score: 0

      No it isn't a problem. See forks: http://en.wikipedia.org/wiki/Fork_(software_development)

    5. Re:Renegging on the GPL by c0lo · · Score: 2

      Suppose Larry decides

      Larry who?

      Suppose Larry decides he's not happy with just changing the license on one of the dozens of open source products he's acquired and decides to actually start demanding payment for use of earlier versions of the software.

      Since me, as a licensee, acquired the rights under certain conditions (a set of mutual obligations between parts, obligations protected by the copyright laws [1]), the other part of the contract cannot unilaterally modify the contract in her/his benefit. Which, if happens, would creates another agreement between us.

      [1] GPLv2 point 5: You are not required to accept this License, since you have not signed it. However, nothing else grants you permission to modify or distribute the Program or its derivative works. These actions are prohibited by law if you do not accept this License.

      Does a copyright owner have the legal right to retract an issued license?

      No, unless the original license specifies this is possible and the two parts (licensor/licensee) agree with it before engaging in the contract. E.g. a "variable mortgage rate" - yes, the rate can change in the future, but this is specifically stated in the loan contract before signing it.

      Does that right apply to the GPL?

      No, it doesn't, because this right does not exist!

      Don't make a confusion with releasing a software under two or more different licenses though. If-and-only-if you have the full ownership of the copyrighted work, you are allowed to release the work under a non-GPL license as well. Potentially, you can stop releasing future versions under GPL, but you cannot change the licensing conditions of whatever release that was distributed under GPL.

      --
      Questions raise, answers kill. Raise questions to stay alive.
    6. Re:Renegging on the GPL by Anonymous Coward · · Score: 0

      RE: "Larry who?"

      Larry Wall?

    7. Re:Renegging on the GPL by Anonymous Coward · · Score: 0

      Larry Page.

    8. Re:Renegging on the GPL by QuantumG · · Score: 2

      Larry who?

      Get off my lawn.

      --
      How we know is more important than what we know.
    9. Re:Renegging on the GPL by jbolden · · Score: 2

      Does a copyright owner have the legal right to retract an issued license?

      First off you are going to get a lot of "no" below. That's not true, the actual answer is sort of. For example there is a notion of "fundamental breach" which would allow them to get rid of the license. For example if you were issued a license under the GPL and you proceded to not honor it by distributing a binary without source they could declare you in fundamental breach and revoke the entire license.

      Alternately you could get software under the GPL and the author could declare "anticipatory repudiation" which requires you to take mitigating actions. For example if they came to believe their software was covered under a valid patent and they notify you of that, arguably you can't blindly redistribute under the GPL.

      This is a massive blindspot in copyright law.

      How so?

    10. Re:Renegging on the GPL by Alex+Belits · · Score: 1

      It was also never tested in court that you are not a fuckheaded moron.

      --
      Contrary to the popular belief, there indeed is no God.
    11. Re:Renegging on the GPL by countertrolling · · Score: 1

      I think it's one of those ispo-fatso things.. after the fact?

      --
      For justice, we must go to Don Corleone
    12. Re:Renegging on the GPL by QuantumG · · Score: 1

      Well, seeing as you're the only serious reply, I guess we should have a conversation.

      For normal (proprietary) licenses it's already been established that a copyright owner can revoke the license at any time simply by giving notice to the licensee. (Wood v Leadbitter).

      They can legally do a bait and switch, handing out permissive licenses, waiting a few years, then revoking all the licenses and demanding payment from anyone who continues to copy or modify the software. This is established law in Australia (Computermate Products v Ozi-Soft), and the only law prohibiting it in the US is UCITA, which thankfully never much made it (as it has much worse effects, namely clickwrap licensing).

      Ultimately it would take someone with deep pockets to do this.. and they'd have to be outright malicious towards Free Software (thus, Larry). They'd preferably want a product that was dual licensed in the first place, never really had much of a development community, and had a strict copyright assignment policy for contributors (the two tend to go hand in hand).. that way they can simply declare "the only license available for this software is now [the proprietary license]", and because there was no doubt that they are the sole copyright owner it would be sufficiently ambiguous whether or not they were referring to all versions of the software or just the future versions.

      Their sales team would be instructed to inform customers that no, there is no GPL version of the software anymore, and yes, you do have to buy a license to install the software. At that point they're a proprietary software company and they will start treating their customers like proprietary software customers - that is, they'll start showing up at the doorstep to do software audits. That's when they start putting the hard word on customers to "upgrade" to the proprietary licensed software.. if the customers resist *on the grounds that they don't need to pay for old versions*, then the legal fangs come out and we find out if this whole GPL thing has been built on a foundation of sand.

      --
      How we know is more important than what we know.
    13. Re:Renegging on the GPL by Anonymous Coward · · Score: 0

      For example if you were issued a license under the GPL and you proceded to not honor it by distributing a binary without source they could declare you in fundamental breach and revoke the entire license.

      Considering that the GPL says so, that's not really retracting the license. That's using the part of the license that specifies that action.

    14. Re:Renegging on the GPL by Kjella · · Score: 1

      For normal (proprietary) licenses it's already been established that a copyright owner can revoke the license at any time simply by giving notice to the licensee. (Wood v Leadbitter).

      Your quotes are wildly misleading. A proprietary licence is a permission to enter land and may be express, implied or contractual. Like say, I can invite you into my home and if I ask you to leave you must leave. Implied permission is much the same, it ends the moment you end it.

      Contractual obligations are different, they're binding agreements to both sides. You have no right to terminate a land lease just by saying it, that's breach of contract. I can take you to court, and one of the things I can do is demand fulfillment - that I'm can continue to use the land as per the contract. The GPL is a form of contract, you can't terminate my right to use the software. Since that fundamental assumption is wrong, the rest of your post makes no sense.

      --
      Live today, because you never know what tomorrow brings
    15. Re:Renegging on the GPL by QuantumG · · Score: 1

      There's no consideration for a free software license.. therefore it isn't a contract.. in any court. Please, you really should talk to a lawyer sometime as getting your legal advice from the Free Software Foundation is a great way to be steered down the garden path (trust me, I've been misled for about a decade).

      As for licenses that do have consideration, the copyright owner is still permitted to terminate them. If you suffer damages you can sue the copyright owner for those damages. That's how civil law works.

      --
      How we know is more important than what we know.
    16. Re:Renegging on the GPL by Anonymous Coward · · Score: 0

      It's not completely clear-cut; if we're lucky, the doctrine of estoppel would stop such revocation of licenses (because the GPL effectively encourages us to rely on the fact they wouldn't relicense). And OzEmail looks bad.. but hopefully the fact the license didn't actually detail redistribution will help. But, yes, none of this is solid, it's more 'glimmer of hope'.

      http://www.ilaw.com.au/public/licencearticle.html

    17. Re:Renegging on the GPL by jbolden · · Score: 1

      I don't know Australia law, so I have no opinion one way or the other. The Journal of the National Society for Computers, September 2002 Issue 49 specifically addressed this case for Australia and felt that the bare permission was so unambiguous in the case of the GPL that it wouldn't apply. In the US you have to declare a breach, and that's going to require preponderance of the evidence.

      Now of course there is nothing to prevent intimidation using the threat of a suit. SCO was somewhat successful in getting people to pay for Linux when migrating from SCO. So it has been proven that a vendor could extort money but SCO did lose when they actually tried suing one of their clients.

    18. Re:Renegging on the GPL by jbolden · · Score: 1

      The GPL is a form of contract,

      I agree with you on this, most lawyers agree that the GPL goes beyond copyright and asserts a contract. So far the FSF's position is that it is asserting rights under copyright law and not creating a contract. The reason being is that contract law, is more complex in terms of damage and breach while copyright law is simply; you can't copy unless you are licensed. So you can't just assume that point that there is a contract in place while at the same time using the FSF's reasoning as far as simplicity.

    19. Re:Renegging on the GPL by jbolden · · Score: 1

      Right but if you downloaded another copy you could argue that's a new license.... That's why revocation is important.

    20. Re:Renegging on the GPL by jbolden · · Score: 1

      I suggest you do a web search on whether the GPL is a contract. Open Source Business Conference, San Francisco, March 17, 2004; had a panal on this matter and opinions were heavily divided. The vast majority of lawyers believe that redistribution is a consideration since licenses have value generally under the law.

  12. for-or-non by Anonymous Coward · · Score: 0

    OK, in light of this. If a company were to use Open-source software, would that make them a for-Proffitt or a non-Proffitt organization.... Now I'm really confused...

    1. Re:for-or-non by petteyg359 · · Score: 0

      Four Anon Organizations For Non-Profit Organizations 'Fore Proffitt?

  13. If you don't know the dude's name... by Anonymous Coward · · Score: 0

    Perhaps you shouldn't reference Machiavelli if you don't even know how to spell his name.

    1. Re:If you don't know the dude's name... by jedidiah · · Score: 1

      How to spell the guy's name isn't the important bit of information...

      --
      A Pirate and a Puritan look the same on a balance sheet.
    2. Re:If you don't know the dude's name... by Anonymous Coward · · Score: 0

      Right.....

      By that logic getting the function/method name "almost right" in an API call is OK too?

      If you're going to quote someone - getting their name right seems a small enough courtesy

  14. ... can be confusingly Machievllian... by Anonymous Coward · · Score: 0

    Nice try, but I know who you really are... it's no use trying to disguise your name like that.

    Thought you could fool us, huh? Well, tough luck!

    Oh, Machiavelli... you're so... machiavellian!

  15. The real biggest threat is by Master+Moose · · Score: 1

    Lawyers and companies who compete by legislation over innovation

    --
    . . .gone when the morning comes
  16. kindergarten analogy by Anonymous Coward · · Score: 1

    Imagine a bunch of small kids making sand castles on a beach.

    Copyright abuse would be analogous for one kid to say, "I own this castle and I don't care if you guys helped build it. Get out of here and go make your own." That would be harsh, but the beach is pretty big, right? Besides, who wants to play with such an obnoxious kid anyway. Let him play with himself, and be more careful with whom you work with in the future.

    Patent abuse would be like if one kid said, "You can't build a sand castle anywhere on the beach because I thought of doing that first." If he could enforce that, that would be bad news. Because another kid would have thought of bodysurfing first, another lying on a towel reading a book, another running parallel to the shore with a dog, etc. Pretty soon it would be hard to figure out what you're allowed to do, legally. Patent abuse is much more intrusive and restrictive.

  17. Brain Profit by LongearedBat · · Score: 1

    A clever pseodonym given the topic.

  18. *DRM* and patents, not copyright and patents by ciaran_o_riordan · · Score: 5, Insightful

    DRM and signed hardware is the biggest legal threat beside patents.

    If we liberate the PC, only to find that people are doing their computing on handheld computers (such as phones) and games consoles which won't boot if the software's not approved, then we'll be shafted.

    The answer is (as it always was) that we have to educate people about what sovereignty/liberty/independence means for computing, and that having freedom is valuable. That takes years (ask RMS), but it's the only way to win successive battles. There's no point in defeating some current problem if the same attack will succeed later under a different guise.

    After DRM and patents, the big problem is centralised social networking, where people do their computing on remote servers which they have no control over.

    1. Re:*DRM* and patents, not copyright and patents by Anonymous Coward · · Score: 0

      People use Facebook because their friends use Facebook. There's an enormous amount of peer pressure to use it - if RMS denounced it as evil, people would just say "oh the fat hairy man is just jealous nobody friended him" and put it out of their minds. People don't understand what a website IS, let alone how they can be harmful.

    2. Re:*DRM* and patents, not copyright and patents by Anonymous Coward · · Score: 0

      DRM and signed hardware is the biggest legal threat beside patents.

      If we liberate the PC, only to find that people are doing their computing on handheld computers (such as phones) and games consoles which won't boot if the software's not approved, then we'll be shafted.

      The answer is (as it always was) that we have to educate people about what sovereignty/liberty/independence means for computing, and that having freedom is valuable. That takes years (ask RMS), but it's the only way to win successive battles. There's no point in defeating some current problem if the same attack will succeed later under a different guise.

      After DRM and patents, the big problem is centralised social networking, where people do their computing on remote servers which they have no control over.

      Why do you care what OTHER PEOPLE are doing with their computers, and further, wherever they move their computing to?

      If everyone else started computing on their toaster, you'd have to start attacking those? You really need to stop and think about who this "battle" is with.

  19. Copyrights are not as big a deal as patents. by bmo · · Score: 3, Insightful

    With copyrights, you can write around the infringing part et voila, you no longer infringe. You can do this a lot easier than writing around a patented algorithm which may lay at the core of your software.

    SCO brought up many busted hypotheses why Linux infringed on SCO IP, up to and including "negative knowledge" - i.e., "don't do it that way". None of it stuck. "Similarity" is not enough. Header files are not enough. Some evidence of word-for-word copying in the source code must be there for the accusation of copyright infringement to stick at all. And even then, it's proportional to the amount of infringement. And *even then* courts want you to hammer it out privately before ever going to trial. Courts frown upon plaintiffs going to court without letting the defendant try to mitigate what might be wrong.

    And to this day, they have still not shown any copied code from Unix in Linux, on their path to their "utter destruction" as Darl McBride so succinctly put it. And Linux has come out only stronger because of the ordeal while SCO's entire market cap is 2.1 million on the pink sheets.

    http://www.smallcapdirectory.com/Listing.aspx?CompanyId=21987&Mode=Profile

    Apple sued Microsoft over UI for "copyright" and lost - just because it looks similar doesn't mean it's the *same*.

    Patents are more difficult to defend against. Because these days, patents cover ideas and general mock-ups (design patents) with no regard for prior art or obviousness in the eyes of someone skilled in the art. That last bit has especially been removed from the "obviousness" test. It seems like patent examiners lowered the bar to "Dumb and Dumberer" for obviousness.

    --
    BMO

    1. Re:Copyrights are not as big a deal as patents. by dbIII · · Score: 1

      SCO was a two man scam where Darl deliberately ran his company into the wall that is IBM and took it to his brothers legal practice so they could funnel out millions. Ever notice those big legal names they shouted about in the press were not the ones in court? It was just extra window dressing for the scam.
      Linux really had nothing to do with it. Anything the layman finds complicated would have worked.

    2. Re:Copyrights are not as big a deal as patents. by bmo · · Score: 1

      Darl was just a stooge hired by Ralph Yarro.

      Smart enough to follow through with a plan. Too dumb to question the plan - same for Kevin.

      --
      BMO

  20. so fuddles could be wearing the fedora, tomorrow? by Anonymous Coward · · Score: 0

    just #s. no good deed, unbridled greed.... never looked good on the penguin anyway?

  21. OFFTOPIC by Anonymous Coward · · Score: 0
  22. This article has FUD written over all of it by hweimer · · Score: 1

    This article is so lopsided that given the long time free software licenses have been around, one must assert malicious intent instead of plain incompetence. Yeah, Canonical and even the FSF require copyright assignments that allow them to release the code under non-free licenses. And yes, even the FSF may turn rogue one day and work against the interests of the community (some claim the invariant sections of the GFDL are already a step in this direction). But why should I really care about this? I can always take the last release that was published under an acceptable license and fork it. The ability to fork is the only thing that really protects software freedom. Anything else is just secondary.

    --
    OS Reviews: Free and Open Source Software
    1. Re:This article has FUD written over all of it by Raumkraut · · Score: 1

      1. IIRC the FSF's bylaws are written with the "replicant" issue in mind. That is; if every member of the FSF board was replaced by replicants (from Microsoft, for example), they _still_ couldn't turn the FSF totally evil.
      2. AFAIK, the GFDL's invariant sections are like astronauts drawing a giant penis on the moon. Embarrassing and regretted the morning after, but it's there in the historical record, and you can't do much about it now but apologise. Creative Commons seems to have replaced the use case for the GFDL anyway.
      3. Yes indeed.

  23. None of the above by Aighearach · · Score: 1

    There is no significant threat to open source, legal or otherwise.

    Know that we are.

    Know that we are well.

    Fear not, for as we are we will be.

  24. biggest problem? by Anonymous Coward · · Score: 1

    The biggest legal problem open source has is fear mongering from the likes of "old industry" rags like IT World and corporate executives. This puts a financial burden on everyone that shouldn't have to be there.

    Failing that, there's always copyright being all but null and void in its applicability to the common man. I suspect corporations would like that; they're pushing for it as it stands today.

  25. Value of SCO by Michael+Woodhams · · Score: 1

    Someone/some people believe SCO is worth $2.1M? Wow. It might have been, when they declared bankruptcy, but they've spent rather more than that on the bankruptcy since then*, and if I recall correctly are trying to sell off everything they have left which might be of value for $0.6M, but are in legal difficulties because Novell says the sale (of licenses from Novell) can't go through without their approval.

    * No, this doesn't make any sense to me either.

    (Note: everything I know about SCO I got by reading Groklaw.)

    --
    Quattuor res in hoc mundo sanctae sunt: libri, liberi, libertas et liberalitas.
    1. Re:Value of SCO by bmo · · Score: 1

      2 million for a market cap is a pittance.

      The market cap is the share price times the number of outstanding shares. The share price is just over 3 cents.

      And if you buy anything on the pink sheets, your official name is "Bag Holder."

      As for knowing all there is to know about SCO from Groklaw, there are other places on the net to get information. One of them is the SCOX.PQ group on Investor Village (formerly of the Yahoo board), who PJ always steers people away from because she's paranoid. She has a particular dislike for one of our members, because he bought some shares (Al Petrofsky) just so he could participate in the quarterly conference calls, and raise hell about the expense reports, 10Ks and 8Ks. He bought 100 shares when it dropped below 3 bux, I believe. For shits and giggles and to have a printed and framed stock certificate.

      Half of the group are lawyers and retired lawyers, and the other half are computer professionals and random geeks like me. Some of us post informative stuff on Groklaw as anonymous. I'm anonymous there but I always sign as the same I do here. For instance someone (I forget who it was) exposed the Skyline Cowboy as Darl himself.

      More like Skyline Hat if you ask me, all hat and no cattle.

      Darl used to make appearances on IV, and his wife (alias=Snowshoes) would show up to defend him, and Jeff Merkey of "lol, my kids smashed this hard disk, not me" fame.

      I hope PJ writes her book. It should be interesting.

      --
      BMO

  26. test case by MarkvW · · Score: 1

    Make something that violates a software patent, then file a declaratory judgment action seeking to determine the invalidity of the patent--after you've built up a big war chest. Come at the opponent (MS, IBM, Oracle, etc.) Straight On.

    Why not? The corporations always avoid the showdown out of self-interest.

    1. Re:test case by psxndc · · Score: 1

      If there is no apprehension of being sued by the patent owner, your DJ action will fail. You can let them know you infringe and they can choose to do nothing about it. The patent itself isn't affected by ignoring you; only their potential claim against you suffers.

      --

      The emacs religion: to be saved, control excess.

  27. Eh? by naich · · Score: 1

    What a strange article. Lots of words, but no clear meaning comes through to me. He seems to be taking one sentence from a Canonical license and saying that it proves there's lots of problems for open source because copyrights fwibble a gwabbit. Well, if he's making up stuff I might as well start making up stuff too. Copyrights are what keep open source open - i.e. you can't ignore the license and stop other people using the open source code you distribute without breaking copyright law yourself.

    I really don't see the problem. Contributed code where copyright is assigned to the company can be distributed under a license specified by the company it was contributed to. How is this different from any other company that takes in code? Code that is already under the GPL stays under the GPL - you can't hijack it for your own license, thanks to the copyright laws. If Canonical start being bastards and distributing copyright-assigned contributed code under a non-free license then people will stop contributing. The stuff they have already distributed under a free license remains free forever and they can't revoke it.

    1. Re:Eh? by salesgeek · · Score: 1

      proves there's lots of problems for open source because copyrights fwibble a gwabbit

      I believe you've hit the nail on the head.

      The problem is that some people want an orange and others want a potato. Unfortunately, being human beings, people who want oranges want potato people to buy their oranges and potato lovers want to impost their spudtastic diet on orange lovers. Governments are created, wars are fought, dynasties fall, and then someone discovers the strawberry and another person the tomato.

      Now, what were we talking about?

      --
      -- $G
  28. Copyright by Yvanhoe · · Score: 1

    Because software patents are not legal where I live (you insensitive clod!) and because the last time I read the French legislation, I got this strange feeling that a source code is not a copyrightable entity in France.

    --
    The Wise adapts himself to the world. The Fool adapts the world to himself. Therefore, all progress depends on the Fool.
  29. We don't need IP by jprupp · · Score: 1

    IP is hampering innovation by promoting laziness among IP owners. It creates a government-enforced monopoly on certain ideas, so companies do some R&D, find one idea, and stop doing R&D to profit from the only single idea that they came up with.

    Maximization of profit stem from innovation rate, not government enforcement of ideas and information scarcity. It's the fucking dark ages elitism. Old stuff is new again.

  30. I think that is overstated by dbIII · · Score: 1

    ask RMS

    ... and while you are at it ask RMS what he thinks about passwords being used to lock people out of systems. You may find he's looking at this from a very different mindset to your own.
    Stuff that is locked down to stupid levels is not going to sell to the point where it obliterates things that are sold with the convenience of no DRM as a selling point.
    Software, business method and other insane patents covering wide areas of similarity on the other hand are a very stupid obstruction. It's a case of "don't even think about doing X" where X can be something that has never been implemented as a product and may even be so tangentially related that the filers of the patent never thought of it. It's almost a case of destroying innovation and a large chunk of the economy for the temporary gain of a tiny bit of extra government revenue.
    While there are no laws to impose DRM it is not much more than an annoyance avoidable by using different products that still exist. Software patents on the other hand prohibit things and reduce your choices far more than DRM with no legal teeth can do.
    We saw it with DVD players - most made in China for a global market with the DRM available to be turned on for the US market but entirely usable without it. It's a social thing and not a technological thing so you can expect each generation of DRM to fall to those that can get around it with no consequences - which really is going to be the majority of the population of the world.

  31. The bigger legal threat to open source is not the actual legal threats, it's the fear of misunderstood potential legal threats.

  32. That's kinda' ironic by jonaskoelker · · Score: 1

    I can understand why the title talks about Open Source---it would look weird for a "Mr. Proffitt" to talk about "Free" software.

    [For the uninitiated: the FSF, fsf.org and gnu.org, is about software freedom and software that's free as in free speech. It tends to have a price of zero, but that's a consequence rather than a definitional requirement.]

  33. Fragmentation by Anonymous Coward · · Score: 0

    If they combined their efforts into one or two distros, it--
    Oh wait, you said "legal", my bad, carry on.

  34. there is not threat by Anonymous Coward · · Score: 0

    If the US (and by that I mean its industrial/political complex) continue to suppress open source, file sharing, whatever - then thats up to them.

    The rest of the world will carry on, and with a competitive advantage.

    Anyone who remembers what Soviet era cars and computers looked like will know what happens when an entire society decides it doesn't need openness any more and relies instead on the "innovations" of an elite whose status is based on who they know and not what they know..

  35. What about Google & other 800lb gorillas? by mschaffer · · Score: 1

    Google has meddled in open-source projects (i.e. Android) in ways that are surprising:
    1. Closed source 3.0 (at least for now)
    2. Google has filed cease and desist against CyanogenMod

    Either it's open or it isn't. If 800lb gorillas can just walk over open source projects at will, aren't they all at risk?

  36. liability by roju · · Score: 1

    I worry about liability. While the GPL and other licenses can disclaim liability all they like, a litigious user could still file a lawsuit, forcing the developer to spend money defending themselves. I have a Firefox extension that I've avoided releasing for exactly that reason.

  37. Mom taught me to share ... by applematt84 · · Score: 1

    I believe acknowledgement is due where its' due, but what ever happened to sharing?
    I think what it all really boils down to is greed.
    If I take something that someone built and build off of it, I'm fine with saying, "Hey ... this dude wrote this and I'm using it to leverage what I'm writing." I would appreciate if someone would show the same respect.
    Is it really too much to ask? Guess so.

  38. M$ is biggest threat by Anonymous Coward · · Score: 0

    With proposed law such as these:

    http://www.groklaw.net/article.php?story=2011032316585825

    Which protects only M$ and the other big ones, and the legislation purposely leave FOSS alone if you read carefully.

    China still has a favorable IP laws and nobody should get punish for it. Buy "Made in China"!

  39. A contributor must assign copyright to Canonical? by wdef · · Score: 1

    "Canonical will ordinarily make the Assigned Contributions available to the public under a 'Free Software Licence,' according to the definition of that term published by the Free Software Foundation from time to time. Canonical may also, in its discretion, make the Assigned Contributions available to the public under other license terms." Need to see the full agreement. So a contributor must basically assign copyright for the contribution to Canonical? I would assume so since, in the case of GPL'd code, only the copyright holders can license the same code out under another license - at least I believe so. That is what is happening with X264 - there is the open source X264 code under the GPL and there is also non-GPL'd X264 library code licensed out by the same authors which is not copyleft so programs that link to the latter do not have to be GPL'd also. But in the case of BSD-style permissive licenses, Canonical can do what they want and distribute the contribution under a different license regardless provided the copyright notice is distributed with the binaries.