Slashdot Mirror
Open Source Licensing
This has been a particular headache for embedded systems manufacturers. If the engineers take advantage of the openness of Linux and make some tweaks to the part that is officially Linux, the company must to distribute their changes too. If they merely create software that works like a regular program, then there's no need to distribute anything. (Notice the ASP in the URL!) I know at least one very sharp businessman who explained to me how he carefully made sure the proprietary code in his system would only be dynamically linked to the GPL-protected code. If he left things statically linked, he would be legally bound to release all of his code and his investors wouldn't allow that.
"You had to work with developers. We had to create a build process that very carefully keeps things separate. If we weren't able to do that, we wouldn't have been acquired," he told me.
Rosen's book is a guide for anyone who's trying to walk that line. It dissects the major (GPL, BSD, Netscape, Apache, etc.) as a lawyer would: this kind of legal writing is always eye opening for me ,because the courts often make decisions differently from programmers. They value abstract issues like damages and pay attention to the often nebulous concept of who "owns" a piece of code. Thanks to the hard work of the lawyers at SCO, the distinctions will continue to be important to everyone experimenting with open source.
There are a surprisingly large number of distinctions, both big and small, between the different licenses. For most of us, the differences don't matter. But it's fascinating to watch a lawyer take them apart and compare and contrast them. The BSD license and the Apache license aren't the same, even though they're close cousins. Who would have known?
This book is a wonderful start on the topic. But by the end, it's clear that it's only just the beginning. There are deep philosophical questions awaiting the movement. The distinction between statically and dynamically linked code was easier to define in the past, long before modern languages like Java and the emergence of the Internet. Are web services specified by a hard-coded WSDL file, an example of dynamic or static linking? Can the DNS service change a static IP address into a dynamic link? Enquiring minds want to know. Rosen's book is a great way to begin the exploration of these topics.
You can purchase Open Source Licensing: Software Freedom and Intellectual Property Law from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.
His Trademark law article and his explanation of fair use seem particularly useful.
In soviet russia, You ask not what country do for you, but what you do for country!
Oh wait...
I disagree. Developers, more and more, need to be conscious of licensing, patent, copyright and IP issues. It sucks, because it takes time away from writing code, but I see it getting worse before it gets better.
Did you take your Free Software licensing quiz today?
Thank you for discussing this book. I will be sure to check it out.
p 2004/tc20040922_8372_tc024.htm With that, we can expect to see more and more proprietary software vendors who are feeling the heat of open source competition to stretch the very limits of any contract or license agreement.
I think that in the not-too-distant future, this kind of legal knowledge will be a bit of a prerequisite. This is especially true as awareness of the value of open source continues to spread, and more and more companies and people turn to open source as a cost effective tool. Check out "No More Stock" at this page: http://www.businessweek.com/technology/content/se
Knowing the legal limits *as a court would interpret them* will be crucial for open source developers world wide.
Get some.
<paraphrase>But I'm more than a little frustrated that a book like $foo For Dummies is necessary. It speaks volumes about the current state of computing. The reason computers are complex is that big corporations who have no interest in their users' needs and programmers are too lazy and inconsiderate to create simple, flexible interfaces that Aunt Tillie can pick up in five seconds flat.</paraphrase>
Seriously, exactly how does the fact that non-lawyers need a book on the application of the law to open source issues lead to the conclusion that the law is unnecessarily complex? By the same reasoning, physics is unnecessarily complex because you need an engineering degree to get a good understanding of how Newton's laws govern the behaviour of real-world systems.
Law is like mathematics: you have a set of basic principles that are fairly simple on their own, but which need to be developed into quite complex structures in order to be useful in a large number of situations. In this example, the basic principle is: the person who creates the code has the right to say how it's used. The complexity comes simply from the fact that lots of people are involved and the law gives them all a say in how their work should be used.
Simplicity is a fine thing, but over-simplification should be considered harmful.
With the way things are going in the lawsuit department lately, it seems this is kinda needed. Tho it has always been hard to explain to the buisiness world the concept of gpl style license agreements.
Tho, i do disagree 100% with the idea that developers do not need to be concerned with the legal side of this argument (from above posts), more and more do we find ourselves as developers in the spotlight when something is not 100% up to snuff. More knowledge isnt really a bad thing.
Just because something's properly GPL'd doesn't mean it's sue-proof, and there's a lot more to litigation than just the substantive law at issue.
/*insert bad thing happening here*/, not the terms you released it under.
Well, it will help protect you by helping you become more sue-proof for licensing reasons than you would be by not reading the book. Of course it may not be as effective in a theoretical loss-of-life situation (in a country where someone can successfully sue for spilling hot coffee on their own lap, anything can happen). But in those types of situations, your choice of license is moot; the actual product is being held responsible for
You're right, though, nothing is a substitute for a good lawyer for some things.
--- Journals are boring; Go to my web page instead
Seems that OS may have other ramifications!5 0,39131082,00.htm
From http://www.builderau.com.au/program/work/0,390246
"solicitor, Nick Abrahams today revealed he was in pre-court negotiations to defend a legal case in which a large IT company was attempting to use provisions of the open source General Public License to force his client to reveal its proprietary code."
I've submitted this as news (twice) yet it doesn't appear to be getting posted.......
Law is man made and is arbitrarily complex. It could be simple, but for some reason, even though it is defined by man, it isn't. On the other hand, physics is defined by observable natural phenomenon. There is no known way to make it simpler. There's a huge difference.
Slashdot is proof that Sturgeon's Law applies to mankind.
...businesses trying to honor the rules...
These words don't make any sense together.
As soon as you use that phrase, you are assuming a specific interpretation of the 3 legal constructs. Those of us who reject that particular interpretation are automatically locked out of the discussion, which I suspect is the purpose of the phrase.
What Copyright, Patents, and Trademarks do is impose a 'temporary monopoly' onto something intellectual that otherwise would not have limits. The nature of the monopoly may be different (Is it for an exact 'copyable' work of art such as an audio/visual work, or writing....is is a process where the words/diagrams used to describe the process are not critical, but the process is ... or is it part of a virtual identity), and
the time limits may be different, but the phrase "temporary monopoly" is
the essence of these legal structures.
If we can't start from that basis, then there is no way to have the discussion without quickly breaking down. The metaphor of property just does not make sense outside of physical objects as ideas are infinitely copyable, and can be spontaneously created ("thought of") in different places and time in isolation from each other. With physical objects there is a natural monopoly: the land, animal, person, object or whatever physical object can only exist in one place at any given time, and in the world outside of science fiction and magic do not just "appear out of thin air".
Creating an arbitrary legal limit on how something can be copied is clearly government intervention in the natural world to create a monopoly. Who benefits from that monopoly, and what the costs are, and how these things have changed over time can be brought up to interpretation and debate, but the basic concept behind the government granted temporary monopoly cannot be debated.
AdsJunction.com Ad Network
You need the book, because you are wrong. You have stumbled onto a point of major issue with teh GPL, which simply isn't 100% answered yet.
When a peice of code, lets say, libfoo, is under the GPL, that means the structures in memory that libfoo defines, the method signatures, etc, are all peices of libfoo. They are copyrighted works released under the GPL.
Now, lets say you want to write a peice of software to USE libfoo. To write this software, it's required to import some of libfoo's headers. These headers are copyrighted. When you compile your software, even though it links dynamically at runtime, it still retains this copyrighted memory structure information in the final binary image. You're compiled program has just included GPLd code. In fact, if you simply call methods, you're program could arguably be including copyrighted material.
This is a major peice of contention... and I would say this IS how the GPL works, even though most people ignore it. WHy would I say that? Because of the LGPL, which was designed SPECIFICALLY to address the issue by putting in writing that it was OKAY to use LGPL libraries in a non-LGPLed program. Because the FSF found the need to create the LGPL, one can only assume that that GPL really does work th is way. Somebody suing you for using their GPL'd code would most likely bring this up in court, and they'd likely win.
According to a strict interpretation of hte GPL, this is the way it is. It disturbs me greatly that some people have never read the thing, or are willing to ASSUME anything in the face of copyright. That's bogus to me. Don't rewrite the GPL to suit how you wish it was, interpret it as it is and go from there, otherwise you are opening yourself up a can of worms.
I know at least one very sharp businessman who explained to me how he carefully made sure the proprietary code in his system would only be dynamically linked to the GPL-protected code. If he left things statically linked, he would be legally bound to release all of his code and his investors wouldn't allow that.
Hmmm, according to my reading of the GPL FAQ, even dynamically linking creates a derivative work, and thus all of the code would need to be under the GPL. No?
"For most open source software users, there are few things as easy to understand or follow as an open source license.
/..
When I read this, I laughed so hard I nearly fell out of my chair. Just consider, if you will, how many completely misguided and contradictory views of the GPL you've seen/heard recently, even right here on
Most open source users have no friggin' clue what the exact rights and restrictions are under the GPL or other popular OSI-listed licences (the BSD/MIT variants being a possible exception, since they contain almost no restrictions to begin with). That doesn't keep them from having an opinion and loudly expressing it, of course...
Rosen disagrees with FSF on many points -- specifically, whether dynamically linking creates a derivative work. And since FSF's lawyer is a law professor and Rosen is a two-bit hack, you should think twice about listening to Rosen. Incidentally, MySQL's lawyers also disagree with Rosen -- and have gone to court to defend the GPL.
Read the full story at my web page, http://www.feyrer.de/g4u/g4l.html.
- Hubert