Slashdot Mirror
Open Source License Comparison
rbb writes "Bryce Wilcox-O'Hearn, aka Zooko, has put together a simple chart that in just a few lines displays the characteristics of each of the most popular Open Source licenses. The table, which is currently in version 0.8.3, makes it easy to see in a glance how the licenses compare to one another." Easily digestible information - good for PHB [?] s.
Apparently the only way to be safe against the accusation of having given "legal advice" is to write with such ambiguity and obfuscation that nobody can learn anything from what you've written
:P
Well from my experience the more complicated it looks, the more like legal advice it becomes!
And judging from the wars on this site, most of us write like this anyway
Kudos to Zooko for producing this, but I have to point out that if you didn't already know this stuff, you're not going to learn much of anything useful here because there's not enough basic introduction, and if you did already know it, you're not going to learn much of anything useful here, because there's not enough detail.
And what on earth is the point in posting your opinion on legal issues, then disclaiming that opinion as being worthless? Again, no disrespect to Zooko, but his opinion isn't worth any more than mine or yours.
Let's keep pressing for IAAL advice, or better yet, get some of these licenses tested in court, proactively and preemptively if necessary. I'd happily help fund a FSF case to have a declaratory decision made on the validity and limitations of the GPL.
If you were blocking sigs, you wouldn't have to read this.
You seem to have a strong opinion in favor of the GPL and, from what I can determine, it looks like a fantastic concept that is applicable to more than just computer code. However, I am somewhat inexperienced with open licenses and have a few questions as I consider publishing software that I am currently developing. Short story is as follows, the program I'm working on is being coded in Python (latest GPL OK version). It is designed for accessing damage and/or fatigue life for aging commercial aircraft. The math engine is developed by myself and I'd like to make it available to other experts in the field so that it can grow. I would also like input from experienced programmers since I am self taught (this is in fact my first Python program). On the other hand, I need to keep that math model under tight control. I am concerned that someone who is a good programmer but not experienced in aircraft fatigue my modify the math engine in such a way as to make it unsafe for use. Can the GPL protect from this scenario?
A goal is a dream with a deadline