Legal Group Releases Guide To GPL Compliance 141
An anonymous reader brings news that the Software Freedom Law Center has published a guide for compliance with the GNU General Public License. The purpose of the guide is to prevent "common mistakes" the SFLC has encountered during its various GPL violation investigations. Their suggestions include close scrutiny of software acquisitions, more precise tracking of changes and updates, and avoiding "build gurus." They also provide tips for dealing with a violation. The full guide is available at the SFLC's website.
All in all, a good thing. (Score:4, Insightful)
Any kind of legalese could do with such a guide.
Good fun to make up your own license (Score:1, Informative)
but yes this does rather highlight all the obligations of the GPL, which is a good thing because a lot of companies don't realise what it actually entails.
When making a software product from open source software, one of the tasks is to find out about all the licenses and to be quite honest it is to avoid a lot of software that is GPL, which thankfully most isn't as far as the building blocks go.
GPL software is nice when you want to include a tool that the end user can use but is not central to your software
Build Guru (Score:1, Informative)
Re:Build Guru (Score:5, Informative)
I don't think that the term is a standard one in the broader sense; but it is clear enough for the purposes of their discussion. Relying on one person's personal knowledge for a vital step in your process is never ideal, especially if you have a legal obligation to provide your customers with some of that knowledge, if they ask for it. Simple enough, really.
Re: (Score:3, Interesting)
Re: (Score:2)
Re: (Score:2)
I never heard that term, either, but I'm guessing it's someone who knows the entire build process from start to finish. Possibly even wrote the scripts for it. For embedded Linux firmware this would involve shell scripts, custom tools written in C/C++, a ton of Makefiles, maybe a little Buildroot, and how to script the source code control system. Just figuring out how the various SCCS tools do "branching and merging" takes a guru all by itself.
Re: (Score:2)
There is no official term, and your interpretation makes sense, but a thorough reading of the article and the actual guide to which it refers, shows that they mean something different. It is, in effect, a facetious term in the content in which they use it. In this case the articles author actually used quotes correctly - [stops to gasp]
If some
From the document... (Score:5, Funny)
GPL compliance need not be an onerous process.
They say at the end of a 15 page document.
Re:From the document... (Score:4, Insightful)
To be fair, 15 pages is nothing to most lawyers.
Re:From the document... (Score:5, Insightful)
Exactly. It kind of makes you think the BSD folk might have a point in insisting on simple, permissive licences (though even those can be open to misinterpretation - see ipfilter in OpenBSD).
Still, this 15 page document is only needed for legal-corporate types, anxious to know the letter of the law and the exact boundaries of what's permitted. For ordinary programmers, RMS has tended to say that the letter of the GPL is less important than its spirit, which is to share your code and give all users the same rights you have. If you stick to that principle you can be pretty sure you are within the letter of the licence as well.
Re:From the document... (Score:4, Insightful)
Making sure that your licence is as short as possible, without compromising your goals, is always good; but compromising your goals just to make your licence simpler is perverse at best.
Legalese not complexity is the issue. (Score:3, Insightful)
GPL arguably has more complex goals than BSD, so it really isn't realistic to expect the GPL to be simpler than, or even as simple as, the BSD licence. Making sure that your licence is as short as possible, without compromising your goals, is always good; but compromising your goals just to make your licence simpler is perverse at best.
Complexity isn't the issue with the GPL: it's the legalese. And because of the legalese, I am not confident to use it or any software using that license for commercial use without legal advice; which increases the cost of using GPL software on a commercial level. This extra cost is factored in when evaluating and comparing against software under other licenses.
Deceptive simplicity is unwise. (Score:4, Informative)
Large corporations (which probably do way more business than you or whomever you're speaking for) don't have that problem. Reasonable business operators recognize that you should not be "confident to use" any software without complete understanding of the terms of the relevant licenses. This goes for any software license. In this way the new BSD license is deceptively simple and framing this issue as though it only affected the GPL is unfair.
Re: (Score:2)
Large corporations are also inclined to want possession of the software. Unless they are tailoring to a specific niche or hold a number of advocated in it, GPL's opensource software doesn't have much of a change. Therefore, I think the license should fit the smaller corp like the GP was talking of. This also stops open source software from getting the name a hacker OS or hobbyist software which further discourages larger corporation usages.
Re: (Score:1)
I agree totally; hence the need for legal advice.
So what if it gets patented? (Score:3, Informative)
What if someone takes your code and patents a part of it? BSD then says you cannot claim the patent or protect yourself from it.
And patent law says you can't use your BSD code.
It therefore doesn't matter if you feel confident in obeying the BSD. Your feelings will not make a hill of beans difference. And you will be disallowed.
Re: (Score:2, Insightful)
What if someone takes your code and patents a part of it? BSD then says you cannot claim the patent or protect yourself from it.
The BSD license does not mention patents. There is nothing in the BSD license preventing you having patents based on BSD code, nor protecting yourself from others patent claims.
Re: (Score:2)
Nothing protects you from someone else patenting your idea, except fighting the patent application in court.
The license under which you release your code is irrelevant with regards to patent law.
Re: (Score:2)
The license under which you release your code is irrelevant with regards to patent law.
The difference is that the company holding the patent can't distribute the code under the GPL. Consider the case where you write code; someone else patents part of the basis for your code; now they redistribute the code that you wrote and charge their patent rent. With GPLed code, they couldn't redistribute your code (they'd have to write their own).
Re: (Score:2)
How are you going to know if they distributed your code? It would at that point likely be a binary blob or something with a little shifted to change the checksums. In other words, someone can patent something in the GPL code, claim their offering isn't GPLed code anymore and not have to worry about it until someone figures out the difference and takes them to court. we are now back to square one where you still have to goto court to defend your rights. And it does have to be the person who owns the copyrigh
Re: (Score:2)
This is incorrect. The word "patent" or derivatives do not appear in the BSD license. You can read it here [opensource.org]
Patent law says you must license legally patented methods to include them in a product. It does not interact with the concept of software licensing.
Re: (Score:2)
Re: (Score:2)
But at least once you've got legal advice on the GPL once, you can freely follow that advice for any of the many software packages that are licensed under it.
This compares rather favourably to the situation in the closed-source world, where every single EULA is different, and they are all many, many times longer
Re: (Score:2)
Complexity isn't the issue with the GPL: it's the legalese. And because of the legalese, I am not confident to use it or any software using that license for commercial use without legal advice; which increases the cost of using GPL software on a commercial level. This extra cost is factored in when evaluating and comparing against software under other licenses.
I dread to think how long it takes your organisation to install a typical proprietary program... the legalese in any EULA is at least two orders of magnitude worse than the GPL (and those are expected to be understood by children, teenagers, and people with no IT nor legal knoweledge...
e.g. take iTunes. Required to use an ipod. How many people know that you've signed a contract with someone other than Apple, and given that company permission to modify the contract at any time without them even having to
Re: (Score:2)
So, as a lawyer, I don't consider the GPL to be written in "legalese." It's just not written very well, especially v2.
When drafting a document, a lawyer tries to make sure that it can only be read one way--his. Often lawyers drop into the habit of "legalese" to do this. And, as a result, that document may be difficult for non-lawyers to understand. But, that "legalese" is rarely required.
So, here's an example of the GPLv2 poor drafting:
Re: (Score:2)
Complying with the GPL is simple: when you ship binaries based on GPL code, provide the source you used to build them. It's only when people think they can get away with not providing the source because they're not technically linking to GPL'd code or otherwise violate the spirit of the agreement that it gets complex. Do you disagree, that shipping source is a sufficient action to comply with the GPL?
Re: (Score:2)
Re: (Score:2, Informative)
Dear Fermion:
If you trust a salesperson to spell out legal limitations, you are a fool.
More than likely, you aren't a fool, but are just working a little weekend overtime at Microsoft.
Am I right?
Re: (Score:1, Troll)
Exactly. The result is that I have been advising my employer to remove dependencies on GPL and LGPL software from all of our products. Either take a commercial license, find an alternative that has a more permissive licence or roll your own.
Re:From the document... (Score:5, Informative)
You don't mean a "commercial" license. The GPL is a commercial license. Commerce is done with software licensed under the GPL. You mean something else, perhaps "proprietary".
In any event you haven't explained what is so bad about the GPL or that you understand the licenses you deal with (any of them) to warrant such trust in these other more permissive licenses or licenses you erroneously referred to as "commercial".
Re: (Score:1, Insightful)
Trolls don't have to explain their reasoning. All they have to do is take what (might) be a minor inconvenience in a license such as the GPL, and expand it into a FUD-storm, listing, and not explaining, dubious alternatives.
Re: (Score:1, Troll)
You want to know what is so bad about the GPL? Anything that takes 15 pages to explain how to be compliant and contains recommendations that you change your software development process as part of it is a significant problem. And did you notice those terms that copyright owners might impose? They could cripple a small company (and most software development companies are small).
And that is just GPLv2. GPLv3 and the patent bar makes it even worse. Companies often have to defend themselves from patent infringe
Re: (Score:2)
There's nothing dangerous about the GPL if you comply with the license terms. If you don't want to comply with the license terms, the libraries simply aren't available to you. I don't see what the problem is.
Re: (Score:2)
Obviously I am not getting through to the GPL fanbois here. Maybe shouting will help.
THE MAIN PROBLEM IS THE GPL LICENSE TERMS ARE TOO COMPLEX AND IMPACT THE ENTIRE SOFTWARE DEVELOPMENT PROCESS. A 15 PAGE DOCUMENT LIKE THE ONE THE ARTICLE REFERS TO IS *NOT* REALISTIC. ASSURING COMPLIANCE IS DIFFICULT AND OVER A MULTI-YEAR SDLC WITHIN A SIGNIFICANTLY SIZED ORGANIZATION LIKELY IMPOSSIBLE.
A lot of companies cannot realistically use 3rd party software under these conditions. Licenses like artistic, apache, BSD
Re: (Score:2)
It's absolutely true that the GPL has a higher cost of compliance than a "BSD style" license.
The cost of compliance is still trivial compared to the benefit of using pre-existing code in a scenario where releasing source for a module is compatible with your business goals. This 15 page document basically says "you really have to release the source for your modified GPL modules", and explains that it's easier to do that if your build process isn't messed up.
Conclusion: No software has a $0 acquisition cost
Re: (Score:1)
I agree. Sadly most of the people here assumes that every company has the moral duty to release its code, so GPL is not dangerous but "ethical promoting". I will not judge about that, but GPL fans have to understand that a lot of people (yet) considers "close code" their best fit, so GPL (like any "pirated" comercial/propietary software) is potentially dangerous.
Re: (Score:2)
It's no less "ethical promoting" to distribute proprietary software and claim that that is necessary. It's totally appropriate to judge whether proprietary software is ethical.
Re: (Score:1)
Agreed. I thing nobody will believe that it is estrictly necessary to distribute software in "propietary/obscure/commercial" terms (except, maybe, in some security domains) from a technical point of view; saying that would be a plain lie. From a business perspective, IMHO I think most owners yet prefer that way, and I just do recognize the right of a lot of people/companies to do so for whatever reason they choose. Call it "freedom to hide", despite not being of my personal taste... and apparently to their
Re: (Score:2)
Re: (Score:2)
I seem to recall most of the books in the ... for Dummies series being more than 15 pages. Reading " See Spot Run " also requires you to wade through more than 15 pages IIRC ;-)
(I mean the original children's book, not this one [imdb.com]. That's not a book, and the screenplay is more than 15 pages also, unless I miss my guess.)
Guide to GPL compliance (Score:3, Insightful)
Share and share alike.
Re: (Score:1)
Re: (Score:1)
Context people, context. (Score:5, Insightful)
The broad concept of the GPL isn't hard; but a quick guide to a few of the unintuitive points is a useful thing. The details of the source distribution requirements are a matter of considerable confusion in some quarters, as are the terms under which one can regain the licence after violation.
Those minutiae aside, though, I am very surprised by how much apparent confusion the GPL and other copyleft type licences inspire. There seem to be two main camps of misinterpretation. The copyleft=no copyright group seems to believe that anybody who doesn't do copyright the exact same way they do doesn't do copyright at all. Hence this group's lack of respect for the terms of the GPL and similar. The other extreme has a fear amounting to mania of the GPL, believing that the GPL is unknowably complicated, and will inevitably lead to having all the code you've ever written forcibly expropriated by armed communist penguins.
I don't understand the confusion because the GPL is a perfectly ordinary licence, from the legal perspective. Its purpose, socially, is quite interesting, and rather unusual; but the form "Copyright law says that you can't copy this without our permission, which we grant if you do foo and bar." is absolutely standard. People seem to go in expecting the legal side to be horribly mysterious, just because the social purpose is unusual. It is rather weird, really.
Re: (Score:2, Interesting)
The folks who should be concerned with the GPL are technical folks; not lawyers.
Re: (Score:1, Interesting)
I've not read the guide yet as I'm somewhat busy this afternoon.
Does it include any clarification of the requirement to provide source code? That one has always seemed ambiguous/fuzzy. Whenever it comes up in discussion here on /. there is always argument over who the source code must be provided to.
Having seen the arguing over this requirement so often I feel it is one that certainly could use some clarification.
Re: (Score:3, Informative)
Re:Context people, context. (Score:4, Informative)
If software was written in English instead of programming languages, I think there would be less confusion.
The folks who should be concerned with software are ordinary folks; not programmers.
But of course, in reality, both of these matters are too complex to accurately express in standard English.
The GPL is a hack of the legal system with the goal of turning copyright upside down. That hack only works because it's written in legalese.
Re:Context people, context. (Score:5, Informative)
I agree that licences(and law in general) ought always to strive for clarity; but(as I'm sure you know from explaining tech stuff to non techies) real clarity often demands a certain amount of jargon. Concepts, whether they be "JIT Compiler", "Special Relativity", or "Derivative Work", can be glossed in English; but they cannot be fully described without reference to the technical terminology of their fields.
The GPL does pretty well, comparatively speaking, in being precise without being incomprehensible. Unfortunately, it has been forced to become more complex(the difference between version 2 and version 3 is striking) by factors outside of its control, mostly related to software patents, DRM/Tivoization, and technological advances that make the aggregation/derivative work boundary fuzzier.
Re: (Score:2)
Maybe you can explain what the purpose is of the UPPERCASE PARAGRAPHS IN EULAS? Uppercase text is harder to read than lowercase text, so if the purpose is to emphasize the important bits, it doesn't do it very well. And why emphasize paragraphs? Is lowercase text less legally binding than uppercase
Re: (Score:2)
There are certain provisions in contracts that are disfavored at law. This usually includes limitations on liability, disclaimers of implied warranties, and the like - essentially, items that take away rights that the purchaser (usually) would have absent the contractual language. Such provisions are usually construed strictly against the beneficiary. One of the legal arguments available to someone trying, for example, to sue in the face of a liability waiver is that it fails to give "clear notice" of the n
Re: (Score:1)
Confusion? (Score:4, Insightful)
I have to wonder if people who complain about the GPL (or, for that matter, most software licenses I've dealt with) being confusing have ever actually read it. I read and understood the GPL when I was in 9th grade. Sure it took me a few reads, but any legal document, or for that matter most any book is like that.
Can you give a specific example of language you find confusing in the GPL?
I think, perhaps, people simply are daunted by the idea of "so much" language that all has meaning to be understood, not the actual quality of that language.
Re: (Score:2)
I think you got something there. "Natural language" is far less dense than specialised languages. Legalese, or technical language above a certain level, you cannot skip a single word, or sometimes, even a single comma. Most people I know read about 50% of the words on a page, then make up an opinion of what is meant. That's why legalese is scary. It's not that it's hard to understand, it's that the natural process these people use makes it 95% likely to get the meaning wrong. When they say complicated,
Re: (Score:2)
If somebody can't understand the GPL, either version, I don't want them working on any software I have to deal with in any way. The licenses are a lot more readable than the sort of code I work with daily.
Re: (Score:2)
If the GPL was written in English instead of legalese, I think there would be less confusion.
The folks who should be concerned with the GPL are technical folks; not lawyers.
Compared to most EULAs I've read (and yes I do read them, part of my job is to ensure my employer complies with licensing requirements), the GPL is a shining beacon of clarity. Version 3 is rather less clear than 2, but nevertheless both are quite readable.
I suspect the confusion comes from two places:
1. People who don't know anything about software development and think it all sounds terribly awkward to follow.
2. People who have never read any sort of EULA in their lives, GPL included, and go purely on
Re: (Score:2)
#2 seems more likely, but I'd phrase it: "People who've used Linux, but never actually read the GPL or informed their clients of their obligations, figuring they could just wing it."
Re: (Score:2)
Yeah. I was just talking to a colleague at the school where I teach who is the author of a textbook. We were discussing ways of keeping costs down for students, and he said it ought to be easy these days to get figures from Wikipedia, so the publisher wouldn't have to pay per-copy royalties to
Re: (Score:2)
hose minutiae aside, though, I am very surprised by how much apparent confusion the GPL and other copyleft type licences inspire.
I'm not. That's because I don't think most of those entities are confused at all. Having heard a lot of them, I'm of the opinion that they understand the GPL and how to comply with it perfectly well, but they've got their own agendas which would be harmed by having to comply with the GPL so they feign ignorance and confusion to try to get out of doing what they know full well th
Request: (Score:3, Interesting)
Dude - send a copy to the Utah State Attorney General's Office.
No, they did nothing wrong, but in 1999 when I was trying to explain that I wanted to put the GPL to use in my former classroom (all non public-domain copyrights are jointly held by a teacher and the State of Utah), most of the Dept'y Att'y General's responses consisted of "...I don't understand". I even pointed him to the GNU website), but he called back later and was still lost. Nice guy, sounded like a good lawyer, but he just couldn't wrap his brain around the concept.
Now that was nine years ago (!? Cripes I'm old),, and things may have changed, but pushing a copy of this new guide to all 50 US State Att'y General offices would, IMHO, not be a bad idea at all.
Build Gurus (Score:4, Informative)
The GPL requires you to include the scripts used to control compilation and installation of the executable. It does not require you to provide the knowledge needed to use those scripts, if it's all in someone's head. So having "build gurus" doesn't necessarily put you out of compliance, though it might make it hard to demonstrate you are in compliance.
Re: (Score:2)
Re: (Score:2)
Too many software projects rely on only one or a very few team members who know how to build and assemble the final released product. Such knowledge centralization not only creates engineering redundancy issues, but it also endangers GPL compliance, which requires you to provide build scripts.
On a literal, hair-splitting note, I'm sure build scripts do not have to be provided if the build guru in question has not actually scripted the build. After all, if no build scripts exist, there is simply no grounds to claim that they must be distributed. Copyright/the GPL do not cover things that do not exist, as far as I can tell.
Re: (Score:2)
On a literal, hair-splitting note, I'm sure build scripts do not have to be provided if the build guru in question has not actually scripted the build.
I guess you'll just have to supply your guru to anyone who obtains the binary code then ;)
(just kidding, I know GPL explicitly lists the types of files which are considered 'corresponding source')
Re: (Score:2)
Re: (Score:2)
Interesting. I guess the FSF's point of view is that such documentation is part of the "work" that constitutes a piece of software. I'm not sure I agree, but life's like that. Sure, it's nice to write build scripts (and you should release them if they are already written), but I think it's merritless to say that my knowledge is part of the derived work.
For geeks by geeks (Score:2)
GPL'ed software is notoriously by geeks for geeks. The original GPL was clear enough, as this document indicates things are getting confusing.
Re: (Score:2)
Some common things I see with GPL violations (Score:3, Interesting)
1.Companies who release software (usually embedded into a hardware device) and then claim "we are working on releasing the source code but its going to take time"
2.Build systems where one "master makefile" builds the entire project (usually with a "master config file" that selects which model you are building for, what features are turned off and on etc)
3.Companies who use a version of GCC and/or binutils that isn't publicly available and then dont release source code or binaries for that version, thus making it harder to recreate the binaries they are shipping (I wonder if creating a CPU with a new or altered instruction set, porting Linux to this CPU and then releasing kernel source but not GCC or binutils would be a GPL violation or not...)
4.Companies who release source code for one firmware revision and then dont release source code for other firmware revisions (*cough*Motorola Z6*cough*)
and 5.Companies who claim a need to "sanitize" GPL code before its released (this most likely includes removing any comments that reference internal intranet email addresses, web URLs, machine names, internal processes etc but may also include removal of pieces that are used only by or removal of comments/changing of code of pieces related to proprietary hardware so as not to release any more hardware details than they have to. Will likely also include removing anything embarrassing such as swear words)
7.1 covers an often-overlooked part of LGPL (Score:3, Interesting)
Section 7.1 of the article covers an often-overlooked part of the LGPL. If you include LGPL libraries as part of your application, the EULA must permit reverse engineering to debug the application if the end user modifies the library and uses the modified version, instead of the version that came with the software.
I suspect that there is a lot of software out there that includes LGPL libraries, but has a blanket "no reverse engineering" clause in the license agreement.
Re: (Score:2)
I joke, of course, but your point is very insightful, IMHO.
Re: (Score:3, Informative)
Copyleft licences are quite explicit about using copyright to achieve their aims, just as ordinary copyright licences are. Now, it is true that people who use and advocate copyleft licences are frequently, though not universally, likely to advocate significant copyright reform of o
Re: (Score:2)
Actually no. Copyright reform is NOT needed. Copyright laws were just fine until some twats messed it it up by extending the copyright.
Patent reform is needed, not copyright reform.
I use GPL, LGPL, BSD and similar software and abide by the terms of these licenses. And I do not pirate anything. Days where you've had an excuse that you needed something but can't afford it are *gone*. Can't afford Windows and Office? Use Linux/BSD/Solaris and OpenOffice. Want to hack code but can't afford a compiler - there is
Re:Question (Score:4, Informative)
Re: (Score:2)
Secondly, if you were releasing your software, it would have to be GPL only if it is part of a derivative work made from GPLed software. Merely being distributed with, or running on, or interacting with
Re: (Score:2)
No.
No more than you'd be required to release the source code of a program you'd compiled with GCC.
Re: (Score:2)
No -- the GPL is not a usage license (Moglen) (Score:4, Informative)
> [as a user] would I be under any obligation to release the source code to the software I wrote?
No, as a user of GPL software, as opposed to a (re)developer or distributor, you do not engage any of the relevant conditions of the GPL with respect to provision of the source code.
As the ex-FSF's Eben Moglen has said on many occasions (paraphrased but close), "The GPL is not a usage license, but a distribution license". That's a very clearcut distinction, and Eben has written the book in this area.
There is a small corner case to watch out for, however, and that's static linking with GPL libraries --- a few people call this "derivation" despite the fact that you're only an end user and are only aggregating the GPL library functions statically with your code, so the issue is slightly grey. However, most linkage with GPL libraries is dynamic, and even Richard Stallman has conceded that legally, dynamic linking cannot ever be derivation but only mere usage. No doubt Eben put him straight on that. "Aggregation is not derivation" appears in the FSF's own explanatory materials.
On the whole then, the answer is "No, you're safe", unless you go out of your way to use static linking, which would open you up to the possibility of occasional arguments within the community, although probably not legal ones.
Source, please? (Score:3, Insightful)
Where would I find Richard Stallman saying this? Where would I find Eben Moglen talking about this? In other words, what's your source?
Re: (Score:2)
It would help us to better understand the claims in this thread if we had specific quotes for both Stallman and Moglen's alleged statements rather than vague recollections and broad generalizations. We don't know what you have read.
Re: (Score:1)
even Richard Stallman has conceded that legally, dynamic linking cannot ever be derivation but only mere usage
Wow. It was hard to take him seriously when he was making extreme statements like that. If this trend keeps up, he may be reasonable in a few hundred years :)
Re: (Score:2)
Re: (Score:3, Informative)
I'm still very skeptical with regards to what you're saying, because if true, that would open the doors to reuse of GPL code in proprietary closed-source applications on an unprecedented scale. Most certainly that sort of thing would be picked as news of the day by more than one of websites, portals and blogs associated with Linux and OSS - Slashdot, Groklaw etc. Yet I do not recall seeing anything like that. Unless you're implying that FSF is deliberately trying to ke
Re: (Score:2)
As for your theory as a whole - can you point us to any specific closed-source product that knowingly uses GPLed (not LGPLed) libraries by dynamically linking to them, and claiming that it is GPL compliant?
Re: (Score:2)
Re: (Score:1)
Re: (Score:3, Interesting)
The original phrase was "Copyleft: All rights reversed" [gnu.org]. The "reversed" means that the rights of the end user are protected more so than the rights of the developer (the more natural beneficiary of copyright) - to wit, the end user is preserved the rights to run the program for any reason, share the program, examine and learn from the source code, and build and distribute derivatives.
Berkeley et. al. focus on protecting the rights of the developer more than the end user - to wit, the developer can create
Re: (Score:3, Insightful)
The problem is that copyright itself is contrary to libertarian principles.
BSDL and similar licenses take minimal advantage of copyright themselves, but allow downstream developers to apply as strict a copyright policy as they wish to any derivative works.
The GPL relies more on copyright for enforcement, but is designed to limit the ways in which downstream developers can apply more restrictive copyright and patent policies to GPL-derived works.
Whether you prefer the BSDL or GPL mostly comes down to whether
Re: (Score:2)
I'd mod you +1 interesting if I could. :-) Thanks for the insight into libertarian principles. However...
I don't follow this. The late, great wireless driver controversy [opensourcehypocrisy.org] was specifically about a BSD-licensed driver being changed to GPL, and the consensus seems (I believe) to be that this is not permitted - only the copyright holder can change the license once under BSD.
Or am I missing yo
Re: (Score:2)
I'm not sure I agree with that consensus entirely, and I'm not a lawyer of any sort (which should be assumed -- this is the Internet after all), but there is at least one important distinction to be made: the driver wasn't significantly altered
Re: (Score:2)
I believe his point is that you can modify BSD licensed works, and license your changes under the more restrictive GPL. The BSD disclaimer still holds, and the additional one does as well. What you cannot generally do is remove the BSD disclaimer or copyright notice. The original author still holds copyright over the parts you didn't change!
The wireless controversy was a great deal trickier than a mere Slashdot summary can contain: some places in the source code suggested it was available under BSD or GPL,
Re: (Score:2)
The problem is that copyright itself is contrary to libertarian principles.
And this is why libertarians (such as myself) should be for the copyleft licenses.
More permissible licenses like BSD do NOTHING to change the current status of copyright laws.
Copyleft licenses, such as GPL, provide the real impetus for changing the current state of copyright in two ways:
1) they restore, partially, what you would have without copyright (for the licensed work itself, this is no different than BSD);
2) they (at least when it becomes widespread enough) give motivation to commercial entities to s
Re: (Score:2)
As I said, it comes down to the end justifying the means. Yours is one common view, but there is just as much support for the view that claiming copyright (as one must do to utilize "copyleft" licenses) is wrong regardless of the motivation, or that doing so undermines your ultimate goal.
In my opinion, if one fails to stick to one's principles throughout the entire effort one runs a strong risk of becoming the enemy, and simply replacing one tyranny with another. I have seen this already where some have arg
Re: (Score:2)
As I said, it comes down to the end justifying the means. Yours is one common view, but there is just as much support for the view that claiming copyright (as one must do to utilize "copyleft" licenses) is wrong regardless of the motivation, or that doing so undermines your ultimate goal.
I am guessing we (or, the two opposing camps) actually have different "ultimate goals".
The way I see it, the ultimate goal for a libertarian has to be the abolition of copyright system itself (and thanks to international agreements, this is going to have to be a global thing). Releasing one's works into the public domain does very little to achieve this ultimate goal, since other participants and powerful players in the system do not have a motivation to ditch copyright in this case. Poisoning the copyright
Re: (Score:2)
That's not going to happen. No matter how many GPL libraries you write the proprietary software companies will just continue to write their own code in-house, or employ third-party libraries under
Re: (Score:2)
Jawohl! Sieg!
Re: (Score:2)
I dunno? I'm not a huge fan of the GPL and I read the entire thing.
Re: (Score:2)
Re: (Score:1)
Ah yes, the GNU Cult Members can't handle accurate criticisms so they censor my comments by moderating the parent comment down. Typical communist control. That's another indication of how you really don't value freedom!
To be a true freedom fighter *YOU MUST* allow others who disagree with you to voice their opinions in the public space *without moderating* them down. Have the guts to hear contrary opinions!