Slashdot Mirror


Delicious Details of Open Source Court Victory

jammag writes "Open source advocate Bruce Perens tells the inside story of the recently concluded Jacobsen v. Katzer court case, in which an open source developer was awarded $100,000. Perens, an expert witness in the case, details the blow by blow, including how developers need to make sure they're using the correct open source license for legal protection. The actual court ruling is almost like some kind of Hollywood movie ending for Open Source, with the judge unequivocally siding with the underfunded open source developer."

58 of 202 comments (clear)

  1. Good Guys by arizwebfoot · · Score: 4, Interesting

    Sometimes the good guy doesn't finish last.

    --
    Beer is proof that God loves us and wants us to be happy.
    1. Re:Good Guys by bbbaldie · · Score: 2, Interesting

      This is why "Blammer" just Blamms on about Linux infractions of MS patents, but doesn't actually file suit: If it ever went to court, FOSS might in fact win many millions.

  2. Believe It or Not by eldavojohn · · Score: 4, Interesting

    There were a few people that smart at Pixar when I worked there, but there seem to be tons of them in the Open Source world.

    Believe it or not, your two categories are not mutually exclusive. I discover more and more that the brilliant people I am paid to work with have made improvements to open source projects. Both through work and in their free time.

    I think something the open source community could use is an adjustment of this attitude that you're either gainfully employed or working for free ... when I can attest that both are possible at once. Just be mindful of what you signed when you were hired by your employer. Some companies have terrible "everything you do even outside of work is ours" clauses. Wish the employers would realize that it's a benefit for you to experience contributing and learning from open source.

    --
    My work here is dung.
    1. Re:Believe It or Not by Bruce+Perens · · Score: 4, Informative

      I am gainfully employed in consulting companies, mostly, that are trying to cope with Open Source but still have the old mindset. That's what they have me there to fix. Of course lots of people who are gainfully employed get paid to work on Open Source today. But it's interesting, when I visit these companies, that I already know their hottest programmers - through Open Source.

    2. Re:Believe It or Not by Anonymous Coward · · Score: 5, Interesting

      Bruce, do you also explain to these companies that not all open source software is created equal?

      I've had to deal with several large companies who see "open source" as meaning basically nothing but Linux, MySQL, PHP and Apache HTTPd. The moment I suggest using a better technology, often with a much less restrictive license, they get all uneasy.

      They can't seem to understand that OpenBSD is more secure than almost any other OS. They can't understand that PostgreSQL is better at handling large data sets and heavier workloads than MySQL is. They can't understand that Ruby allows for faster and more reliable web application development than PHP does. They can't understand that nginx offers better performance and reliability than Apache HTTPd does.

      Keep in mind that they are just considering the use of open source software in their operations, without actually planning on contributing back any changes. So I don't think it's a licensing problem. Nor is finding support a problem. I always provide them with a lengthy list of consultants and specialists, both individuals and companies, who I've personally worked with before and know to do top-notch work.

      It's probably just a hype and marketing problem. They've only heard marketing yells of "Linux!", "MySQL!", "PHP!" and "Apache!" thrown out by various vendors and industry rags. They're ignorant of anything else.

    3. Re:Believe It or Not by Bruce+Perens · · Score: 3, Informative

      Most of my customers are in embedded systems. Sometimes, it concerns Android, and I have told them that Android does not represent the quality that should be expected out of an Open Source project. But their customers are asking for Android. So, we don't really get to make that decision.

    4. Re:Believe It or Not by trapnest · · Score: 2, Insightful

      What do you mean exactly? Android (cyanogen specifically) seems higher quality then most other open source projects.

    5. Re:Believe It or Not by vivaoporto · · Score: 3, Insightful

      Most companies doesn't care about the best technical solution for a problem. They also take in account availability of workforce to use that particular solution, suppliers interested in working and giving support and a some other factors, like cost. Take the example you mention, the LAMP stack. PHP programmers with knowledge of MySQL are a dime a dozen, and you can filter through them to pick and choose the real competent ones. Most hosting providers already have an already optimized and time tested stack that supports these technologies, so companies can filter through them to choose the cheaper and more reliable. It gets the job done so other potential better solutions gets overlooked. Technical merit is not the only factor when choosing the right tool for the job.

    6. Re:Believe It or Not by A+nonymous+Coward · · Score: 2, Informative

      The kernel code from Android is crap and very unlikely to be merged as part of the mainstream kernel tree. Google seems to not care, and they wrote it in such a manner that no one else is interested in doing their dirty work for them.

    7. Re:Believe It or Not by Bruce+Perens · · Score: 2, Informative

      Not just the kernel. The utility code is crap too, hard-coded in places where it shouldn't be, etc. And some people don't like the fact that they dropped LIBC and put in their own version. They'll fix it eventually.

    8. Re:Believe It or Not by Bruce+Perens · · Score: 2, Informative

      I am not running the Android kernel project. If I get to run any embedded manufacturer's project, I will try very hard to get the code into the kernel, and I know how to make the technical and economic case for that.

      Most cell phones have two processors. The radio modem is in the smaller one, and is awake much of the time, and the PDA in the larger one, and is not awake nearly as often. That's how stand-by can work for so long on such a little battery. The radio uses a real-time OS and the PDA of course has Linux. Often their communication is over the Hayes modem protocol, believe it or not. So, when you want to call 911, Linux sends "+++ATDT911" or something similar.

      I have a hard time believing that the Linux kernel is a fundamental problem regarding anything about the call, given the above architecture. I am sure that there are design flaws.

    9. Re:Believe It or Not by IamTheRealMike · · Score: 2, Interesting

      Come on Bruce. Your argument for why Android low quality is that the kernel has patches and the "utility code is crap"?

      Has it escaped your notice that unlike on the (presumably?) high quality desktop Linux distributions, the following things actually work in Android:

      • Sound mixing
      • Real-time software updates
      • Anti-malware sandboxing
      • Hardware acclerated video decoding

      Android is selling by the truckload, it's doing far better than any other consumer open source OS ever has. Your customers want it because they know that the quality of an OS is not determined by how "hard coded" its "utility code" is - they can use it for themselves, they can see how well it's doing in the market place.

      And as for the kernel arguments, wasn't that whole hooha debunked already? I mean, you know what the kernel "team" are like (I use the word team loosely). There's no clarity around who is responsible for approving or denying most changes. No decision can be made quickly. Everything you do will be flamed by someone and if you do get code merged, it'll quickly be rewritten or obsoleted by somebody else who may or may not have produced something usefully better. It's largely due to these high quality practices that desktop Linux remains a joke, to this day.

      Android is what your customers demand because it works. If that's what low quality means, give me lower quality open source!

    10. Re:Believe It or Not by GasparGMSwordsman · · Score: 2, Insightful

      There are a lot of weaknesses in your statement, but I will concentrate on one point. It appears that you are not taking into consideration the amount of time, effort and money it costs to change platforms, tech or language. Such change-over costs can be prohibitive.

      First consider who would need to learn the new tech/system/language. How long would that take to bring that person up to the same level of competence compared with the old tech/system/language. In the best case scenario you are looking at a full month per employee spent doing practically nothing useful. Alternatively you could send them to take classes, usually an expensive prospect. Do you need to hire additional personnel or fire existing personal to meet the new needs?

      Next consider the added complexity of using two sets of tech/system/language. Do you have two separate teams, one to work on the first combination and a second to work on the new combination? Do you cross train everyone? What support systems are in place for the old system that will need to be updated or created for the new system? What policies or procedures will need to be updated or created?

      Third we have security concerns. No tech/system/language is entirely secure. In any environment where there will be a large financial liability to a security breach, it is essential that every step is taken to ensure your over all systems are secure. You have to stay on top of newly found security issues to avoid dangerous vulnerabilities. With each added tech/system/language you add more ground to cover, more possibilities for breach.

      Fourth we have the issue of updating old/existing systems to use a new tech/system/language. How many scripts/modules/configuration files/documentation files/source code files/test cases must be updated or altered for the new solution to work. Not only this but testing must be done to ensure that each change has not introduced a bug and works correctly. For a large 'business solution' testing alone can consume thousands of man hours to completely ensure that the new solution preforms the same as the old solution.

      All of these factors must be considered before such a change is feasible (in addition to several not mentioned). Many times the change-over costs are less than the benefit. Others the benefits of change are much lower than the cost. I can not gainsay the situations you were in or what *I* would have recommended. But to say a change is better without considering all the factors is foolish at best.

    11. Re:Believe It or Not by SanityInAnarchy · · Score: 4, Interesting

      the following things actually work in Android

      You didn't list a single thing that doesn't work on Desktop Linux.

      the quality of an OS is not determined by how "hard coded" its "utility code" is

      If you were a programmer, you'd understand that hardcoding generally does determine the quality of an OS -- if not its current capabilities, then its future capabilities. By avoiding things like that, we get flexibility -- and the flexibility of the Linux kernel is why something like Android could be written in the first place.

      --
      Don't thank God, thank a doctor!
    12. Re:Believe It or Not by Bruce+Perens · · Score: 2, Interesting

      Well, I know how to write bit-slice microcode, which is lower-level than assembler. I wrote it for image processing at Pixar. It can get a lot more performance out of the hardware. But so many people insist on programming in those pesky high-level instruction sets that popular CPUs don't even come with the facility to accept user microcode any longer.

  3. A few corrections to the preface here at Slashdot by Bruce+Perens · · Score: 5, Informative

    It's actually the appeals court that was sympathetic. Twice. The lower court seems to have had less understanding of the Open Source developer's plight.

    Using "the right one": means the right Open Source license. A real key here is getting one that had competent legal help in its drafting. There are a few real duds on the OSI list, including a font license that I swear allows you to convert the font to the public domain. Only the programmers who wrote it don't see it that way.

    Sorry about the lack of paragraph breaks. I tend to write too many of them and the editor responded by using too few of them. He might have fixed that and the web cache hasn't been flushed yet.

  4. A victory with a high cost... by ndykman · · Score: 5, Interesting

    At the start, the open source developer got hit with a large SLAPP fine (urgh), and finally got the judgement reversed and was awarded damages, but the article notes that: "This doesn't fully compensate Jacobsen for all of his time and expense over 5 years, but it was the best he could get." So, by not using the right OSI license, the developer opened himself to years of legal hassles and woes.

    Also, one wonders if by proactively suing, he ended up being worse off than by not waiting and then countersuing. Finally, it is noteworthy that since the DMCA was used on behalf of the open source developer, this may not be seen by opponents of that law as a victory at all, as it provides validation (if weak) of it's existence.

    If this is victory for the little guy, I'd really hate to see what defeat is like.

    1. Re:A victory with a high cost... by Bruce+Perens · · Score: 5, Insightful

      It's more of a victory for you and me, because we have the benefit of Bob's court precedents. Katzer had previously intimidated at least one other person with patent threats, and Bob felt that the team could not go on with their project with this hanging over their heads. But I agree that the Open Source developer really paid, paid big, to get this. I've taken tons of s**t for what I attempt to do for the community too. You'd better believe in what you're doing, because there isn't always a thank-you.

      If you read the second appeal, I don't think DMCA is a big deal in it. But if we're going to have dumb law, let's at least make it work for us. IMO worse than DMCA is the entire concept that cases like this can bankrupt someone before they have a chance to win. How can there be justice if that's the case?

    2. Re:A victory with a high cost... by raddan · · Score: 3, Interesting

      Bruce, I wonder-- did Katzer know that the Artistic License was weak, and did that motivate some of his behavior? I'm wondering if the choice of a different license would have actually deterred this guy.

    3. Re:A victory with a high cost... by Bruce+Perens · · Score: 3, Informative

      The court said that Katzer deliberately misappropriated and obfuscated. My guess is that he would have done so to anyone he thought he could beat. The failure of the license took what should have been a short case and made it longer. Of all the terms in Open Source licenses, I never saw myself having to fight a case over the right to be attributed properly. We had just a little thin thread to fight with, IMO.

    4. Re:A victory with a high cost... by Bruce+Perens · · Score: 2, Insightful

      BSD, MIT, etc. are simple, but they don't give you any protection from patent aggressors. And so I am wary of using them, because it's patent suits that are the largest problem.

      GPLv3, LGPLv3, AGPLv3 are the strongest within the constraints that RMS set. License not contract, no rights that you already had are restricted, etc. About 40 lawyers involved in drafting and review. Larry Rosen thinks his licenses are better for the absence of RMS. Look at both sets and make your own decision.

    5. Re:A victory with a high cost... by Bruce+Perens · · Score: 2, Informative

      I like BSD licenses because they allow me to close my own source, not the source others contributed but mine.

      Everybody wants to receive the BSD license. Of course. Everybody loves a gift, and that's what the BSD license is. But it doesn't always make sense for someone to give it. And since the person giving the license is doing the work, it's their choice.

      Sure there are rights being restricted. If you use GPL code you can not close your own code and still distribute it.

      I'm afraid you sound a bit confused about this. If you apply the GPL to your own code, you certainly do have the right to close it and distribute it. All copyright holders have that right.

      Perhaps you mean if you mix your code with someone else's GPL code. In that case, you still have the right to distribute your own code privately, as long as you remove that other person's GPL code from the project.

      The person giving you the GPL code is only giving you rights, not taking any away at all, because before they gave you the code you had no rights regarding that code. The problem from your perspective is that they aren't giving you all rights.

      Nobody owes you a gift.

  5. Victory? by Kjella · · Score: 3, Insightful

    Over 5 years, Bob Jacobsen put in thousands of hours of work on this case. He was threatened with loss of his employment, and with all of the money and property that he had. The $100,000 he eventually received doesn't compensate him for this. But I'm sure that the feeling of achievement does.

    If you count being tied up in court for five years, getting lots and lots of pro bono lawyer time and still not breaking even. I call this "How to snuff out a potential upstart for $100,000" even though he probably wasn't competition in the first place.

    --
    Live today, because you never know what tomorrow brings
    1. Re:Victory? by Bruce+Perens · · Score: 4, Insightful

      If you look at how many presentations, etc., Bob did at the recent NMRA (National Model Railroading Association) conference, he hardly got snuffed. It almost looks as if people were going to the conference just to see him.

      Katzer spent a lot of money, has no product he can legally sell today (his web site currently only points to a list of articles) and his reputation is in the pits over this with anyone who might have otherwise been a customer.

      But yes, anyone less tenacious than Bob would have lost, and it wouldn't have been terribly expensive for the patent holder. The patent system is so tuned to incent the bad guy that it really stinks.

  6. Re:A few corrections to the preface here at Slashd by Just+Some+Guy · · Score: 3, Insightful

    including a font license that I swear allows you to convert the font to the public domain.

    Which one is that? IANAL, but I wanna play "spot the contract bug", too.

    --
    Dewey, what part of this looks like authorities should be involved?
  7. Long, Long Road for an Open and Shut Case by twmcneil · · Score: 4, Insightful

    When I heard about this ruling last week, I was shocked that this apparently open and shut case had taken so long to conclude. If I recall the details I read about years ago when this all started, it seems that Jacobsen was really being taken advantage of badly. IANAL or a judge but I would have thought this case would have taken all of 45 minutes to decide, not years.

    There's something really wrong when someone like Katzer (or SCO) can so completely snow a court. The crux of both cases come down to code ownership/authorship. Is that something that just goes "Whoosh" to all judges?

    --
    "The ferrets, they're every where I tell you!"
    1. Re:Long, Long Road for an Open and Shut Case by b4dc0d3r · · Score: 2, Insightful

      If I photocopied a famous author's work and printed it with my name in the author's spot, I'd lose in a heartbeat. That's because there is an existing legal tool called "copyright" that the judges *do* understand, with an entire set of procedures and precedents.

      As a judge, having no exposure to the idea of open source, creative commons, or other such issues, the only thing a judge can fall back on is the legislature and case precedence. In a simplistic sort of way, it's very easy to conclude that everyone is playing according to copyright law, because that's the only law that applies (DMCA being related to copyright).

      The problem is that the normal copyright law is almost never superseded by a contract. Usually the contract stipulates who owns the copyright, not any specific terms of copyright, because copyright is made up of laws. And you can't have a legally binding contract that contains clauses which are contrary to the law. Open source licenses are basically legislation created by individuals, which a judge should regard with suspicion. They are *not* obviously entering into a contract, since no one signs or agrees to anything. It's about as enforceable as a pop-up EULA, but someone using open-source code never had to take an action to agree to an EULA in order to use the code. It's entirely possible to download source code, make changes, and never read or even notice the license file. (EULAs have been ruled enforceable, as long as they are reasonable, so I'm not suggesting open source licenses can be disregarded like people think EULAs can be).

      So in the judge's head, people give things away for free and then invent arbitrary legislation to go along with it, and the end user never has to agree to follow those rules. Since citizens can't create enforceable legislation, open source developers are giving stuff away, and the most sensible conclusion is that "Open Source license was tantamount to a dedication to the public domain." Once the "bad guys" made this argument, it clicked and the gavel came down.

      It was a smart argument. What the judge missed is that there was a copyright notice attached to the code (either in the header or in the code package). The whole point of copyright is that the copyright holder retains the right to copy, regardless of how it is distributed. I can have a free screening of a movie, but that doesn't mean people can film it. I can give away 20 copies of a book, but that doesn't mean I intend to give away my rights, just 20 copies as promotional value.

      If you're going to ignore the citizen-created license, you have to fall back on the law, and the law says it's copyrighted unless otherwise declared.

      The obvious counter-argument is a web site. CNN pays for web servers and an internet connection, basically paying money to give away content - but they aren't giving away the rights to the content, just the content. The business model is to get advertising revenue by giving away content for free, just like the TV channel. Open source doesn't have anything like that to establish it as a legitimate business model, so it's not obvious what open source exists for.

      And that is the fundamental flaw the judge made, in my opinion. "... Tantamount to putting something in the public domain" assumes that since you aren't losing money, you aren't being harmed. Copyright isn't there to protect a business or business model, it's there to encourage people to create things and let them be seen - without fear that someone will take advantage of its availability. The judge's ruling, and the appellate court agreeing, suggests that business interests are seen as more important than individual rights. Maybe I'm misreading, but that's not a good sign. Good thing this guy fought the law.

    2. Re:Long, Long Road for an Open and Shut Case by Jah-Wren+Ryel · · Score: 2, Insightful

      Would "Businessman" vs. "Hobbyist" be less objectionable?

      Of course not. That a "businessman" - or anyone else - has any more default legal standing is odious because it welcomes abuse.

      And to NORMAL PEOPLE, it seems unbelievable that...

      Judges aren't normal people. I'm not saying they need to have expertise in every field, but what they should have is an extremely well developed set of critical thinking skills. Because if they do not have such skills, then we might as well just decide matters of law by doing sidewalk polls of "normal people."

      --
      When information is power, privacy is freedom.
  8. Re:A few corrections to the preface here at Slashd by Bruce+Perens · · Score: 4, Informative

    It's the SIL font license. This is the problem paragraph:

    5) The Font Software, modified or unmodified, in part or in whole, must be distributed entirely under this license, and must not be distributed under any other license. The requirement for fonts to remain under this license does not apply to any document created using the Font Software.

    The problem is, if you embed the font, it explicitly says the license doesn't apply any longer. If you then extract the font, the authors of this license assume that the license magically applies once more. I am far from sure that is the case.

  9. Re:"the correct one"? by nacturation · · Score: 2, Insightful

    Yes... from the summary:

    Perens, an expert witness in the case, details the blow by blow, including how developers need to make sure they're using the correct one for legal protection.

    Make sure you're using the correct expert witness.

    --
    Want to improve your Karma? Instead of "Post Anonymously", try the "Post Humously" option.
  10. Re:A few corrections to the preface here at Slashd by Bruce+Perens · · Score: 2, Interesting

    No, they told me that they meant that if you embed the font in a document, you can distribute the document under any license that you desire to use. But you can't sell the font separately, or convert it to another license.

    That's what they meant, anyway. What it says, however, can be parsed about four different ways. So, we have to get a judge and let him/her pick one.

    Good license writers make them clear enough that there aren't ambiguities in the license itself to litigate.

  11. Re:Delicious? by raddan · · Score: 2, Insightful

    We don't need the extra precision unless our software is stealing from the boss, thanks.

  12. Re:"the correct one"? by Bruce+Perens · · Score: 3, Informative

    Jammag just wrote this submission in a hurry. It means use the right Open Source license.

  13. Re:The lesson? The Perl Man slips by Bruce+Perens · · Score: 2, Informative

    That should probably be: use the version 3 ones. There are a lot of lessons from experience in the v3 series.

  14. These guys deserve support by starseeker · · Score: 4, Informative

    Here's the link to their donations page:

    http://jmri.sourceforge.net/donations.shtml

    I have to admire what these guys are doing and the good it will do for the open source community as a whole (at least in the US). I've seen this case pop up off and on over the years, and it always struck me as a scary plight for an open source developer to be in.

    (Not affiliated with the project in any way and nobody asked me to post the link - I just think a slashdot effect is in order here given what they're doing and what he's been up against.)

    --
    "I object to doing things that computers can do." -- Olin Shivers, lispers.org
  15. Re:Programmers writing licenses by nomadic · · Score: 2, Funny

    Interesting to note that two of the slashdot stories for today are programmers giving legal analyses of cases...

  16. Re:A few corrections to the preface here at Slashd by oldhack · · Score: 2, Insightful

    Nice writeup.

    While it may be a win of sort for Jacobsen, I don't find it an encouraging precedent for OS people.

    Threats and harrassment, five years of hassle, outright fraud (copyright infringement), all that resulted in measley 100k settlement over 18 months (minus 30k Jacobsen had to fork out previously?) after several trips up and down the appeal lanes, all with probono attorney service and even some prominent OS advocates' help.

    --
    Fuck systemd. Fuck Redhat. Fuck Soylent, too. Wait, scratch the last one.
  17. Anoyiing at best. by LWATCDR · · Score: 5, Insightful

    Why the heck is Bruce Perens' name all over this and in the summary TWICE while Bob Jacobsen's name is only listed in the summary in case name?
    It was Bob Jacobsen that paid for this case, risked his job, and wrote the software while Bruce Perens' did even go on the stand!
    Here is a much better summery.

    "Open source programmer Bob Jacobsen wins an historic case establishing the legal validity of Open Source Licenses ,
    The court awarded Mr. Jacobsen $100,000 after years of appeals and many thousands of dollors of personal expenses.
    The actual court ruling is almost like some kind of Hollywood movie ending for Open Source, with the judge so unequivocally siding with the underfunded open source developer.
    Here is a link to Mr. Jacobsen's project JMRI http://jmri.sourceforge.net/ where you can read about his software and contribute to his project to show your support and gratitude for the legal fight Mr. Jacobsen fought for all of our benefit."

    "

    --
    See my blog http://ilovecookes.blogspot.com/ for light hearted technical information.
    1. Re:Anoyiing at best. by Bruce+Perens · · Score: 4, Informative

      If you read the story, rather than the summary, you will find that Jacobsen is of course all over it. The summary is written by an editor who wishes you to read the story based on the credibility of a writer whom you already know, yours truly. And I am, to some extent, telling the story from the perspective of my own involvement.

      I am also taking the opportunity to advertise my work as an expert witness, which I get damn little chance to do because every other case I've participated in has sealed and thus I can't show anyone my writing samples!

      Sorry if that annoyed you. All of the work on the case was done for free. I get a little money from Datamation, but far from enough to live on.

    2. Re:Anoyiing at best. by LWATCDR · · Score: 2, Informative

      I did read the article. I wasn't criticizing your article in anyway just the summary.
      In fact most of my summary came from your article. Including the name of the FOSS author, name of his FOSS project, and the fact that he paid for most of the lawsuit himself.

      If you take a look at the front page that summary is the only summary that in anyway reference the author of the original article at all. I thought your article was just fine.
      The summary which you didn't write was terrible IMHO. I feel it did you a disservice by making you out to be terrible nihilistic while really dismissing the acts of Jacobsen.
      But you didn't write the summary at all so my criticism has nothing to do with your writing.

      --
      See my blog http://ilovecookes.blogspot.com/ for light hearted technical information.
  18. Re:"the correct one"? by Chyeld · · Score: 2, Insightful

    I think both interpretations are correct.

  19. I'm an Androind luser.... by rickb928 · · Score: 2, Interesting

    ...and I can tell ya, it is not yet up to the standard of excellent OSS.

    However, Cyanogen is barely part of the android community. He's clever, aggressive, and actually willing to work within the constraints, but he's also a bee in Google's bonnet. He does what they won't do, cause he caters to a smaller population of smarter users. To implement much of Cyanogen's stuff in OTA relases would require more testing, and of course trusting users like me with root. Some of us would be fine. Others would be calling their carrier and complaining about something they deleted. Well, they probably do that anyways, but for modded ROM users, we pretty much talk amongst ourselves and take the arrows.

    Android is moving so fast it will take a while to settle down and get excellent. And then something else will come and take its place on the bleeding edge.

    --
    deleting the extra space after periods so i can stay relevant, yeah.
  20. Re:Bad news for Open Source by mqduck · · Score: 3, Funny

    Aww, such a cute little troll. Yes you are. Yes you are! Does my little Trolly need attention?

    --
    Property is theft.
  21. Re:Precedents? by Bruce+Perens · · Score: 5, Informative

    It went to appeals court twice and the appeals court ruled both times, then handed the case back to the lower court. The main precedents come from the appeals court.

    That's the way it always is. Lower court precedents aren't terribly useful because only that court has to follow them. Appeals court precedents are more valuable, and the appeals courts are more respected as expert jurists so that other courts follow them even if they don't have to.

    The precedents are that Open Source licenses can be enforced, and with all of the mechanisms that have been put in place to enforce proprietary licenses, including summary judgement. To get that, we had to show that the Open Source developer has an economic interest in his work even though he isn't paid by legitimate licensed users of the work, and is harmed by an infringer even though he isn't paid.

    To you and me it seems odd that anyone had a problem with that idea. But we're inside the revolution.

  22. Re:A few corrections to the preface here at Slashd by Cornelius+the+Great · · Score: 2, Insightful

    The win here is that the case remains public so that it can be used as a precedent in the future. A sealed case would be all for naught for the OSS community.

    --
    Sigs are for losers
  23. Re:A few corrections to the preface here at Slashd by Bruce+Perens · · Score: 2, Insightful

    "Understood by everyone in the industry" is my job. I tell the judge if that's the case or not. As does an expert on the other side. Obviously, we often contradict each other. And then the judge has to decide which of us he trusts. So, what the industry understands is only unreliably communicated to the courts.

  24. Re:Yay! by mike260 · · Score: 2, Funny

    Yeeeesssss...I'm seeing Matt Damon as the earnest geek who refuses to back down, James Gandolfini as the litigious scumbag, and Brent Spiner as Bruce Perens.

  25. Re:It rather sounds as a defeat to FOSS by Bruce+Perens · · Score: 3, Insightful

    Well, it says a number of things to FOSS developers. One is that your license choice matters. This case was much longer than it should have been, and was almost lost, because of the license. Second, it says the patent system still sucks and we're not fighting hard enough. And we still need tort reform.

    But it has some significant value in deterrence, for the subclass of sane aggressors. Nothing deters the other ones, the only thing you can do is to make sure your own legal execution (your license, how you accept contributions, how you identify your developers) in order so that the court doesn't make things worse.

  26. Re:Crap, read that article *too* quickly ... by lbalbalba · · Score: 2, Interesting

    Thanks, that kind reply really means a lot to me. But my guess is that it's not really the subject matter per se that is complicated for me here ; rather, I believe it's my poor grasp of the English language that is the problem. Stating that " ... The case was not sealed like so many settled cases ... " at the top of your article falsely led me to believe that this case was also settled - just not sealed.

  27. "someone ... can so completely snow a court" by jeko · · Score: 5, Interesting

    (I'd like to deeply, deeply apologize to Perens, Jacobsen and all the other People of Virtue who worked on this case for the wet blanket I'm about to throw. God knows you all deserve better.

    I'm sorry, I'm so sorry, and here goes...)

    You should never attribute to malice what can adequately be explained by stupidity.

    But no Court is this stupid. At some point you have to concede the problem is corruption.

    Katzer's outright theft is painfully obvious. It took $30,000 up front and five years of legal wrangling. WORLD CLASS MINDS had to engage on the side of the good guys. Look at the outcome.

    $100,000 over 18 months and future disputes are sent to arbitration.

    $100,000 does not even begin to cover the legal costs of the angels here. If the good guy attorneys hadn't been working pro bono, our Hero would still be in ruinous debt. If not for the amazing charity in this case, Jacobsen's victory would be declaring bankruptcy. $100,000 probably doesn't even put a chip in the profits Katzer made by his theft. $100,000 isn't even $100,000 since it's being paid over time, which means the real net present value is less.

    Worse, "Both parties have agreed to ... arbitration." Do some googling on modern arbitration. It's so blatantly rigged you can't even properly call it a fraud. Corporate interest prevail over the little guys in something like 98% of all cases, and the remaining two percent get such token amounts you can't legitimately call it a "win." Katzer is free to pull some heinous new stunt tomorrow -- like filing entirely new patents claiming ownership of Jacobsen's work -- and he can remain comfortable in the knowledge that he has a 98% chance of getting away with it.

    "Aw, shut the Hell up, man. We got the precedent and that's what really counts."

    Really? A precedent that costs $30,000 up front to try to use?

    "Dude, seriously, STFU. We're making incremental progress towards a larger victory here. FOSS is gaining legitimacy in the legal world, and that's what really matters."

    I know. I've been hearing that for 20 years now. After twenty years of gaining legitimacy, it still only takes five years, two appeals and a team of pro bono attorneys to recover a token amount of somewhat less than $100K and a decision that all future disputes will be resolved in the favor of the bad guys. We're making wonderful progress. A few more such victories and we'll be lost.

    "Frackin' Hell, man, what the frack is your problem?!"

    My problem is that I want everyone else to come to the same excruciating conclusion I have. The System has a horrible bias in favor of the rich and powerful. The System will go out of its way to screw the weak and defenseless. That by Bruce's own admission, the System will take a tool like SLAPP, expressly designed to level the playing field, and use it to deny justice to those not rich enough to afford it. If Jacobsen hadn't had an extra $30,000 laying around, this case would have been over before it began.

    Justice is no longer blindly weighing merits, but is instead whoring herself out to the highest bidder. I want to change that, and we can change that when enough of my fellow citizens begin to understand just how corrupt things have become.

    But wearing rose-colored lenses and seeing this as a "victory" doesn't help us. Jacobsen and company had to wage a heroic, epic battle for a very. very tepid victory. The real costs of his case weren't covered, he hasn't been made whole for the time he lost, Katzer kept his profits and is still out there free to start stealing again tomorrow.

    We shouldn't be celebrating this outcome. It doesn't vindicate the Courts.

    It indicts them.

    (And again, my sincerest apologies and deepest thanks to the wonderful people who fought this fight.)

    --
    He put his boots up on the table and made a face. "The sig," he smirked. "You can waste your life in search of the sig."
    1. Re:"someone ... can so completely snow a court" by rahvin112 · · Score: 3, Informative

      FYI, the $100,000 doesn't include legal fees, the agreement specifically includes that Katzer will pay the "reasonable" legal fees of Jacobsen. What this means is that if Katzer thinks the legal fees are too high he can complain to the judge and the judge will review but otherwise Katzer is going to pay the legal fee's separately from the $100,000 he's paying Jacobsen.

  28. Re:what has this got to do with open source? by Anonymous Coward · · Score: 2, Interesting

    I tend to agree with you. The only relevancy to Open Source I found in the entire article is that the court ruled that an Open Source license was not the same as public domain (a ridiculous argument the patent holder tried to make). The rest of the article is just more David vs Goliath, with the Open Source angle being completely irrelevant.

  29. Re:A few corrections to the preface here at Slashd by Toonol · · Score: 2, Funny

    "This code is free to redistribute, so long as no mention of the author is made. Leaving the credits attached will revoke the license."

  30. Re:Must be something wrong with me by Bruce+Perens · · Score: 3, Insightful

    When someone engages is these sorts of activities, there should be more than civil penalties. There should be criminal penalties as well. It is simply unbelievable.

    Lying on your patent application is perjury. It hasn't been prosecuted since 1974, when USPTO discontinued their enforcement division.

    I have so far had little success in evangelizing that it should be prosecuted again. If you know an organization that would like to sponsor work on that, I could use some help. I rarely can put food on the table through evangelism, and thus can't do it as much as I'd like.

  31. Model Railroading as an "Open" Hobby by Katyrnyn · · Score: 5, Informative

    The outcome of this case is beneficial both for Open Source Software community and the Model Railroading hobby.

    In general model railroading is a very open and diverse hobby. Some are better with structural engineering and carpentry, others with electronics, model building, methods of railroad operation, et cetera. As a community we work together to share and improve our techniques, both to improve ourselves as modelers and to increase our satisfaction from the hobby. There are many well established venues for sharing our knowledge, from regular conventions (NMRA National, Regionals, and plenty of Special Interest Groups), a large number of printed an online periodicals, online communities, and just general "how did you..." questions at any old time.

    Unfortunately our openness attracts thieves and greedy sorts who are more interested in making a quick buck than improving the hobby, and manufacturers and other entities attacking hobbyists is nothing new. I imagine this greedy nature is present in all hobbies and walks of life, but it seems to be more common now than when I entered the hobby 20 years ago.

    Hopefully the outcome of this case will make others that prey on innocent hobbyists think twice.

    Thanks, Bruce, for your well-written summary of the case. I'd mod your article up +1: Insightful if the Internet gave out mod points.

    --
    I dti'r na ndall is ri' fear na leathshu'ile.
  32. what are you going to do about it? by jeko · · Score: 4, Interesting

    With respect, I'm not a cynical college kid who just discovered nihilism, Bruce. I have children, so I fear for the future. I speak. I write. I vote. I'm up for anything short of flying a plane into a building. You got a hill you wanna take, General Perens, I'll be there.

    I began my life as a homeless kid. I've had a miraculous outcome, built a life against all reasonable expectation; college, wife, kids. But as good as my life is -- and it is good -- I am embattled on all sides. I am fighting the good fight -- and I will proudly go down fighting the good fight -- but I can see the battlefield.

    I paid for my own education. I went into a lucrative, practical, growing field. I have watched salaries and opportunities plummet. I know that chances are good I'll be declared too old to hire before my hair even goes grey. Looking back, I would have been better off skipping college and becoming a plumber.

    There is a medical issue that has wiped out my family's finances. I have insurance. Insurance has been worse than useless. There are databases filled with other families in the exact same trap. We make a lot of noise, but we're not making much progress.

    I'm lucky. My kids' school is filled with idealistic teachers doing all they can. The problem is they're doing all they can with the proceeds of a can recycling drive. They're gonna go down fighting the good fight too, and gallows humor pervades the place.

    For the first time ever last year, I saw a financial analysis that argued college was not worth it, especially if you had to pay for it yourself. Worse still, I couldn't refute it. What path do I offer my children when even education is a losing proposition?

    I've traveled. I've seen the Third World. I know where we're heading. I'm desperately hoping my fellow citizens can quit hitting the Fox News crack pipe long enough to notice our city bus just went off a cliff.

    What am I doing about it, Bruce? I'm standing on the walls of the Alamo, firing steady and sharpening my Bowie knife. I'm hoping in the future fat tourists in cotton shorts come to gawk at my heroic remains. I'm hoping my stand here gives General Houston time to run. Gregory Bloody Peck better play me in the movie.

    But I'm pretty sure I know how this chapter's gonna end. And like I said, I'm a man with kids. So I'm OK with that.
     

    --
    He put his boots up on the table and made a face. "The sig," he smirked. "You can waste your life in search of the sig."
  33. Re:So Slashdot is in favor of copyright today? by vadim_t · · Score: 3, Insightful

    The copyright laws are a tool that can be used to different ends.

    Think a hammer. When you use it to build a house, that's good. When you use it to bash somebody's head in, that's bad.

    Similarly with copyright. When you use it to help spread knowledge, it's good. When you use it to stiffle expression, that's bad.

    Hope this helps.

  34. Re:A few corrections to the preface here at Slashd by RogerWilco · · Score: 2, Insightful

    Mr. Bruce Perens,

    I just want to say that I think it's very much appreciated that you spend time to not only be an expert witness in these cases pro bono, but also to discuss this at length here and elsewhere and pointing out such things as flaws in certain licences.

    I'm not sure if you will read this, but I've learned that especially in the more technical professions, we do not often enough give compliments when they are appropriate.

    --
    RogerWilco the Adventurous Janitor