The XFree86 Project modified their license (fully effective as of the upcoming 4.4.0 release). The updated license change applies to the base XFree86 license, and to source files that explicitly carry a copyright notice in the name of The XFree86 Project, Inc. Copyrights and licenses in the names of others will not be affected by this change, however some fear that these changes might be GPL-incompatible.
XFree86 Changes License; Fear of Being GPL-Incompatible
About The Author
Eugenia Loli
Ex-programmer, ex-editor in chief at OSAlert.com, now a visual artist/filmmaker.
Follow me on Twitter @EugeniaLoli
The German article that is linked to explains that there might or will be problems with the new license because it has an advertisement clause like the “classic” BSD-license. It might be incompatible with the GPL because of that, just like the “classic” BSD-license was.
Sorry, didn’t want to discriminate the people that don’t speak neither English natively nor German at all.
GPL-incompatibility is not a valid argument against this license, in this case. If this were a library or kernel module, then GPL-based operating systems could have a problem with it.
What _is_ problematic about this license is the advertising clause. As has been said many times in discussions about the original BSD license: lots of contributors include copyright notices, each requiring that different names be mentioned in advertising the product. This means that advertising the product becomes really awkward up to virtually impossible, which is a great pity, and ultimately harms the project itself.
This is exactly the reason why the University of California decided to drop the advertising clause. Unfortunately, many individual copyright holders of BSD-licensed software have not. It is sad to see that XFree86 is repeating the same mistakes…
—
> Those who do not study history are doomed to repeat it
Yes, and those who do study history are doomed to watch in frustration as it is unwittingly repeated by those who do not
— jonadab on Slashdot
You want to include Xfree86 code in your GPL’d program? You can’t anymore. That is because this licence is placing these advertising restrictions on the use of the code.
huh
both the original version and the new version have the same advertising clause what are you people going on about?
If you compare them though, the old one only prohibited use of their name in advertising without their permission. The new one actually requires that this acknowledgement be included with every single redistrobution of their code: “This product includes software developed by The XFree86 Project, Inc (http://www.xfree86.org/) and its contributors”.
Excuse me for trolling, but… if the people behing XFree86 decide to change the license of their product in a way that collides with the (oh-so-holy) GPL, it’s their decision, isn’t it?
That’s what’s bugging me big time with the GPL: It’s stepping up to the plate and desires to be the one-and-only license around, and everybody who’s not complying is “a social problem” (quoting Mr. Stallman, and several people flaming me for not placing my projects under the one true license).
I can see where this change in license results in pains for other developers. But neither Linux, POSIX, Unix, Open Source, or XFree86 is equivalent to the GPL. Cope, it’s their damn right to change the license.
And I might add, are you aware that the GPL *explicitly* reserves the right for the FSF to change it, and having all your GPL’ed software fall under a license you had no saying in?
Both licenses are on the same page. If you review them carefully you will notice that the new license is nothing more than detailed clarification of the original. The only addition is clause 3;
<snip>
The end-user documentation included with the redistribution, if any, must include the following acknowledgment: “This product includes software developed by The XFree86 Project, Inc (http://www.xfree86.org/) and its contributors”, in the same place and form as other third-party acknowledgments. Alternately, this acknowledgment may appear in the software itself, in the same form and location as other such third-party acknowledgments.
</snip>
Which requests that the distributer of the binary or source provide reference to the origin of the code. This is a documentation requirement, but unlike the ‘invariant’ problems with the GFDL the user is allowed to place the reference in whatever location is appropriate. AFAICT the license is simply more clear from a legal standpoint. This makes the license more defensible in a court.
..ang honeymoon for Packard’s project
“Cope, it’s their damn right to change the license.”
I don’t think anyone claimed otherwise.
“are you aware that the GPL *explicitly* reserves the right for the FSF to change it, and having all your GPL’ed software fall under a license you had no saying in?”
Why do people keep dredging this point up? Anyone who is *not* aware of this simply hasn’t read the license carefully enough. This is nobody’s fault but their own.
Thankfully, though, there’s a simple solution for those developers that actually bother to read a license before releasing their source code under it.
Simply snip the appropriate clause from the license before applying it to your code. The Linux kernel, for example, is explicitly licensed under only the GPL version 2, with the “or any later version” clause removed. Problem solved.
well, that was the first thought when I read this comment. hehe, next time I want to upgrade, it will say “removed xfree86*” packages
XFree86 is closed because there is no information about it. It’s a closed project even under the GPL.
And I might add, are you aware that the GPL *explicitly* reserves the right for the FSF to change it, and having all your GPL’ed software fall under a license you had no saying in?
Yes… And its might right to change to another licence at that point. At least, for future versions.
The GPL has been somewhat exposed as the controlling entity in the open source world, but it only goes to show that the GPL provides the mechanism to understand the system through the source code. If we do not take advantage of the source code to differentiate and create choices, than the GPL does not protect the community, it only slows down the loss of knowledge.
Its not that bbe a pain in the ass really. Even if 50 different organizations contriubte to it thatks 50 more lines so thats what an extra 1k when you download the isos or require one extra roll of the mouse-wheel to get to the bottom of the webpage? Really I’m a fan of the GPL and all but I –unlike others— don’t feel the need to lit incense and give burnt offerings to it. Theres more to OSS than the GPL, and we should be greatful for xfree86 despite this hassle.
What _is_ problematic about this license is the advertising clause. As has been said many times in discussions about the original BSD license: lots of contributors include copyright notices, each requiring that different names be mentioned in advertising the product. This means that advertising the product becomes really awkward up to virtually impossible, which is a great pity, and ultimately harms the project itself.
Not necessarily problematic. SunOS was based on early BSD implementation and they’re more than happy to acknowledge their BSD roots. Most companies are quite happy to include a little bit in their about box or version information. So for most people, it will be a none issue.
that’s not true, Debian will have 2 choices:
– Xouvert from http://www.xouvert.org
and
– XServer from fd.o
> “are you aware that the GPL *explicitly* reserves the
> right for the FSF to change it, and having all your
> GPL’ed software fall under a license you had no saying
> in?”
>
> Why do people keep dredging this point up? Anyone who
> is *not* aware of this simply hasn’t read the license
> carefully enough. This is nobody’s fault but their own.
Judging from my experience over the last couple of years, far to few people realize the real impact of the GPL. More than once I had some really excited GPL evangelist hopping up and down in front of me (virtually speaking) telling me that nothing would keep me from earning money with GPL’ed code, how forking a project is always beneficial because it offers the user a choice, how the GPL gives you total freedom and other unreflected stuff like that.
Sorry for the venting off steam.
That being said, about 90% of the developers I know place their stuff under GPL because they don’t want to think about licenses… I remember a time when that “default license” was the Public Domain, which actually made it much easier to learn from code because you could actually use the code for learning.
Today, I’m writing a Public Domain C library, and I don’t dare looking into the glibc for tutoring, in fear that my code could turn out to be too closely resembling it.
Brave new world. The GPL scares me just as much as TCPA does.
Unless someone can convince me otherwise, I have no problem with the new XFree86 license.
It simply asks for recognition of the fact that XFree86 is being used (in whole or in part). If somebody uses software, in whole or in part, that I wrote, I want recognition of the fact.
GPL on the other hand does not require recognition, but it does require you to open your source – which is much more problematic for me. I don’t mind someone creating copycat version of my code, but I am not necessarily keen on releasing my IP.
For me, the ideal license would be summarized as follows:
(1) you have free use of the code, in whole or in part, but you must credit the original and you must make the original source available
(2) if you have modified, extended, or used my code, you may not restrict me from modifying or extending my code or creating new code that duplicates your code.
Personally, it is not important for me to be able to see other peoples source code. It is only important to me that I can develop wihtout you trying to impede me.
I guess you could say I prefer a black box open source model (interfaces and functionality) rather than a white box open source model (actual source code).
John
…not even mentioning the real point: It’s 2004, damnit, and I have to write up a damned C library because all the existing ones plaster me with legalese about what I am allowed to do with it or not.
The first C standard was published 1989, that’s fifteen years for crying out loud! And still basic stuff like that is kept under licensing – by Microsoft et al. in fear for losing their “competitive advantage”, and by the GNU people in fear for losing their competitive advantage – or their chance at liberating the world of the evils of non-GPL licenses.
Pshaw. As if it would hurt anyone – or benefit Microsoft – if all of GNU/Linux suddenly went Public Domain over night. I doubt Microsoft could use much of the stuff, locked into their own platform as they are. The only ones who would benefit are the small struggling projects and companies, let’s say OpenBeOS, Amiga Inc. or AtheOS.
But all this FSF/GPL speak it’s not really about choice for the user, now is it? I realized that when reading http://www.gnu.org/philosophy/udi.html. Note how “free software” is set equivalent to “GNU/Linux” in there… never a word about other competitors in the OS marketplace that might benefit.
Control freaks on both sides. Nah, thank you.
Maybe you and some others should start “Free Sourcecode Foundation” which expresses what the word Free is truly about as it has been misused by the Free Software Foundation for so long.
I wish schools could explain the word better as so many in the world of coding have misinterpreted it badly…
I also agree that GPL and TCPA = The worst 2 with none worse than the other…
The source code of free(dom) systems should be open and accessible because the direction of progress is through building differentation and choice and a competition to improve the technology, rather than to sell a product.
If you hate the license so much then don’t use it. Its as simple as that. I’ve found no license I like so instead I’ve developed my own one, comically called, “I Don’t Give A Shit License”, in a nutshell, I don’t care what you use it for, I don’t care if you copy it, clone it, extend it.
The problem I have with LGPL and other opensource projects is what happens if someone makes a compatible implementation using the GPL version as a reference? its not a line by line copy, yet, it is based on the same concept. How does one ensure that another does steal their concepts? thats the iffy part of opensource hence I’ve always tended to lean towards the liberal licenses like BSD for the sake of practicality.
Also, the problem I have with alot of GNU people is that they spend more time debating the license than actually coding. How many out there have honestly seen projects move no more than “planning stage” because there is a split between the coders over which license to use.
“And I might add, are you aware that the GPL *explicitly* reserves the right for the FSF to change it, and having all your GPL’ed software fall under a license you had no saying in?”
This is just ridiculous. “*explicitely*”??? It’s a license! Everything it says is supposed to be explicit. You write this like it makes it worse or something. In any case, for clarification, the FSF site notes this as an option wherever it is mentioned (that I could find). They also take time to explain exactly what it means:
“Each version [of the GPL] is given a distinguishing version number. If the Program specifies a version number of this License which applies to it and “any later version”, you have the option of following the terms and conditions either of that version or of any later version published by the Free Software Foundation. If the Program does not specify a version number of this License, you may choose any version ever published by the Free Software Foundation.”
An important note is that even if you do decide to include the allowance, your program is still perpetually under the license under which it was received. It’s just that users also have an option to follow the provisions of the new GPL as well. And why wouldn’t we want that? We trust the FSF, just like I trust Debian and several other open source entities. If there is a new GPL (and there are improvements to be made, I won’t argue!) this clause will be a godsend during the transition period.
Some people here need to Fscking read the GPL. Understand something. YOU DO NOT LOSE YOUR IP UNDER THE GPL. It stays your under your copyright for etirnity. You are encouraged to transfer your copyrights to the FSF but are nto required to. DO you think IBM gave up their copyright to JFS when they made an open source GPL verison of it. NO they didn’t.
Why can’t you use the GPL of Glibc for learning. The only thing that the GPL states is that if you DISTRBUTE a new version based off the GPL version you MUST supply the source. If you are using it for learning then you are going to DISTRUBUTE the SOURCE anyway.
I hope you idiots actually learned something today. I know you stopped learning how to think in college, but lets see if we can try something new.
…When I wrote to a message board the other time when people were talking about the GNOME Foundation elections. I agree that most people use the GPL because they don’t really care for the consequences, and its partly selfish, so that people may not copy my code and PROFIT. While the GPL is a good license for things like the kernel, and other central bits, I think there are certain things that Linus anticipated when he made modifications to the GPL and specifically limited the kernel to one version of the GPL.
The terms of the GPL make the FSF a de facto owner of your code, because they can change their rights, and your, to the code and its derivatives. Whilst we all beleive they have godo intentions, what is to stop them from saying they alone (the FSF) have the right to take code and rerelease it under some other license in a future license. I know there are tradeoffs involved in this, there might be a need for smeone to be able to change the license conditions for GPL’d software, but its worrying nonetheless.
However, this could be the proverbial final straw that breaks the camel’s back, because there oculd be a backlash at XFree86. People could just decide its not worth it, those who fund it just drop the funding. I think its fd.o’s chance to shine. Just get us an XServer right now, and XFree86 will be history.
Couldn’t you use the libc from a BSD? I’d hardly call the BSD license a burden – all you have to include is the license itself and a copyright notice.
It is very poor linking style not to mention if the link is in a different language. Please do so in future.
When it comes down to it GPL is almost as restrictive as a private license when it comes to technology transfer.
Since when was XFree86 GPL ? So why fear to not be GPL conform if they never had a GPL like license before ?
The GPL only slows down the loss of knowledge and the loss of control of the technology. A knowledge base is a more permanent foundation because without one, it is difficult to learn just from the code, without any context and background knowledge about the system and it’s requirements. It should be easy to design your own library, not a severe burden. In addition there should be tools that help you to ensure quality and security, and even do most of the work. These tools are largely unknown to this day.
There is nothing stopping you today from thowing yourself to the complete mercy of a vendor solution and product line strategy. However, in a world were everyone has the same code base, there will be security problems or else severe punishments and restrictions to freedom. The technology will not be based on quality or competition through differentation, but the goal of vendor software is too keep developers under their control by taking research out of their hands, to focus on and give imporatance to trivial issues and to force upon the developers a subscription of forced upgrades.
So let me get this right.
He is angry that the GPL is “too strict” in that it does not allow other people to take the code and re-license it under their own extremely restrictive license, that would in turn, not allow anyone else to re-license that code..
Nice logic there bud.
It stays your under your copyright for etirnity.
Eternity is the spelling. Or if you’re excentric like me and a few people I know, aeternity/aeternity. However, either way, Eternity isn’t right. Copyright is typically for a limited time; the US constiution explicitly says that, even if there’s a popular interpretation under which it can effectively be permanent (I’m sure in 10 years time, Congre$$ will have no problems with extending copyright for a further 20 years)…
Oh, and as for freedom and stuff, the FSF is after free software. In an ideal world, sure, they could release the source code and be guaranteed it’d never be hidden against their wishes, but this isn’t the case. They feel that free software is more important than the freedom of people to do whatever they want with the software, and this is their call. They just want the source code to always be accessible to everyone, and have no limits on the redistribution beyond ensuring the source code is always accessible to everyone. When you criticise them, criticise their goals, not their implimentation, if you disagree with their goals.
The source code will not always be open and accessible even under the GPL. In a world of software differentation, quality software has been realized, and a new genre of personal software development is organically brought to life through artificial means.
> that would in turn, not allow anyone else
> to re-license that code..
With a BSD license, anyone can re-license the original code. Solar is right. The GPL is indeed “too strict”.
I write code “A” under GPL, so A is “free”. You can’t make what you want with my code.
I write code “B” under GPL, so B is “free”. You can make what you want with my code.
Nice logic, imho.
I write code “B” under BSD, so B is “free”. You can make what you want with my code.
Solar,
You are sadly, seriously and deliriously mistaken. If you release your software as GPL 2.0, that is the license under which the software is released, unless *you* the author decide to release it subsequently under a new license.
Stop spreading disinformation about the GPL to promote your own personal agenda.
Thats not the only thing wrong w/ your arguments… You forgot to mention what you consider the term “Make what you want” means. Literally, you can make whatever you want from GPL’d source code. The licence does not cover the use of the software.
Maynard,
Stop inventing monsters that only live in your head. There is not one shred of truth in anything you have said. The FSF cannot claim copyright over your work if you did not assign it ot them and they cannot change the license of your software if you specify that you want GPL v.1.0. Period. End of Story.
You are wrong, sorry.
You have the *option* to license *your* code under, e.g., “GPL 2.0 or later version”, giving the FSF *some* control over *one* of the actual licenses your code is available under.
My Code -> GPL2.0 -> FSF gives GPL 2.1 –> no effect
My Code -> GPL2.0orLater -> FSF gives GPL 2.1 –> someone DERIVING FROM MY CODE can license the DERIVED code under GPL 2.0, 2.0orLater, 2.1, 2.1orLater. MY CODE is still available under GPL2.0 if someone who doesn’t like 2.1 needs it.
Got it?
If I read “Make what you want”, I understand “Make what you want”.
If you choose the GPL for your code, I can’t make a derivative work and license it under the BSD. Point.
I think everyone should take a look at http://www.gnu.org/licenses/gpl.html . Not to mention under the Heading Terms and Conditions look at number 9 and you will see that Solar is correct.
The FSF doesn’t appear to paint the ‘big picture’. It is the impression of some parties that read the GPL that code licensed under it is contrained in certain ways, especially the rule that you have to give away your IP under this license.
This extreme measure has an effect on software development strategy as well as the general software industry. It is likely to change the way that developers percieve software development and how to make profit, however this change is tempered by a gradual rather than rapid uptake of open source development.
The approach to open source development is system implementation. The systems are the most important pieces of software and for the first time ever, they are open and accessible. The systems software is substantial and they bear upon the underlying hardware mechanisms. New system design can even demand that those hardware mechanisms change. That demand can be met by hardware vendors.
The systems come first, before any of the libraries, before any programming languages, or any tools, in fact all of these things are reinvented to serve system implmentation. New and different systems in the hands of individual creators are powerful because the creator has all of the control and all of the knowledge. Nobody else in the world has that knowledge and control.
Each version is given a distinguishing version number. If the Program specifies a version number of this License which applies to it and “any later version”, you have the option of following the terms and conditions either of that version or of any later version published by the Free Software Foundation. If the Program does not specify a version number of this License, you may choose any version ever ublished by the Free Software Foundation.
The point is it defaults to applying to any new version of t he GPL unless otherwise explicitly stated Which is what Linus had to do with the kernel.
Oh, and as for freedom and stuff, the FSF is after free software.
Can you please please please stop misusing the word “free”???
FSF is after sourcecode which is FORCED to remain open, which therefor has nothing to do with the word Free. They use their name for branding but their name should be “Open Software Foundation” because they definitely have nothing to do with Free as in any free…
Again, again, again:
if you specify GPL 2.0 or later, it’s … GPL 2.0 or later
if you specify GPL 2.0 it’s GPL 2.0 AND ONLY 2.0
if you specify GPL, it’s *any* version of the GPL.
YOU CHOOSE. You choose when you write and GPL code, and you choose when you write GPL-derived code; only, in the latter case, you have to choose between the possible options **respecting the upstream copyrights**.
what is the problem? if I specify “old BSD”, advertising clause is there; if I specify “new BSD”, it isn’t.
BSD licenses works the same way. only they say oh, and you can even make this code part of your proprietary and closed product, **as long as you keep the attribution of copyrights in your source code**.
We’ve been over this before. FSF is using the word “free” in the same sense the Constitution uses the word “free.” The GPL is about individuals giving up certain rights to ensure the freedom of everyone else. Both BSD and GPL are free licenses, but in different senses of the word.
XBe: Can you please please please stop misusing the word “free”???
FSF is after sourcecode which is FORCED to remain open, which therefor has nothing to do with the word Free.
Stop with the FUD. the sourcecode is not forced to remain open. YOU are forced not to take away it’s freedom. Thats the bargain. Think of it like a public park with no rules. You are free to use the park, modify it, add to it, etc. But you are not free to put a big fence around it and say no one else can use it. And if you add a house to the park, it doesnt mean that you own the land under the house… it just means the house is now part of the park.
You are the one misunderstanding the word free. You seem to think free = “something i can pick up and then own for no cost” and thus think you own the code and can do as you like. The real usage of “Free” in this situation is “something you can use anyway you like for no charge – but you do not own it, much like air.”
So get a better grip on language, and the need to route around its weaker areas, and stop spouting your ignorance.
To expand on your comparison:
– You license A under GPL, I can’t do whatever I want with the code.
– You license B under BSD, I can do almost whatever I want with the code.
However:
A company comes along and improves A and B:
– They license A under GPL, I can still do lots of things with the code.
– They don’t release code for B at all, I can’t do anything with the code.
BSD is about freedom for developers. GPL is about freedom of the code itself, and freedom for users. If you like the ideals of the former, than license your code under BSD. If you like the ideals of the latter, license your code under the GPL.
I write four programs: MyPropriatryProgram, MyOldBSDProgram, MyGPLProgram and MyPublicDomainProgram. Each gets licenced under the licence you would expect by the names (in the case of the MyPropProgram, you’re forbidden from redistributing it, etc. etc. as you’d expect with Microsoft software). Each program deals with files in their own obfuscated and poorly documented file formats. I release the source code to none of them (as I wrote the code in the first place, this is perfectly ligitimate, even in the case of the GPL, but please don’t do this; it’s against the spirit!).
Similarities: In no case will you be able to easily write another program to deal with files, nor will the programs be able to continue development if I decide to stop.
Differences:
In MyPropProgram, if you send a document in the file format to your friend, and they don’t have MyPropProgram, they’re stuffed or they have to break the law if you’re willing to. In the other three cases, you can freely distribute the programs.
Say you choose to create a software package that includes (the binaries of) one of the above programs. You also would like to have some small advertisements, but you don’t have much money, so you’d be having small ads you pay for per word or per line. You wish to say it can open files from one of the programs. In the case of MyOldBSDProgram, you have to include a dozen or so words, which could amount to two or three lines. In the case of the MyGPLProgram or MyPublicDomainProgram, no such limitation exists. You’re obviously proscribed from including MyPropProgram.
If you decompile MyGPLProgram, modify it, and release it, you’re required to distribute the source code upon request. No such requirement exists for MyOldBSDProgram or MyPublicDomainProgram. You’re obviously proscribed from decompiling MyPropProgram. ‘Digital’ amendments to copyright law on your area may also forbid you from doing this to MyOldBSDProgram.
I’m really not sure that the advertising-clause-enhanced BSD licence is any ‘freer’ than the GPL. The GPL just stops you from selfishly stealing what isn’t yours.
Wrong. It seems to me that you never read the GNU site. So I’ll spell it out for you:
Free means Freedom. Freedom of ANY user to become an user, distributor, developer, integrator, WITHOUT having to pay MORE for it.
with BSD-style license, you give this freedom PLUS the freedom to derive the work in a non-free fashion. why? maybe because you are really giving what you want to give. maybe because you fear hardware makers won’t make drivers to your software (think nvidia).
with copyleft, you give only this freedom. and you say, you want to use my code? ok. just IF you derive from it AND IF you distribute the derived code, THEN YOU MUST maintain the pace and keep it open. just that. no more.
HTH,
The GPL is about individuals giving up certain rights to ensure the freedom of everyone else.
I respect you and all that Rayiner in fact most stuff you write are brilliant, but this is plain wrong.
Did anyone stop and bother to QUESTION the metaphor with free speach? I find the comparison plain stupid. Considering the amount of things RMS writes and what he writes, do you actually mean the only thing he got right was the GPL comparison with free speach? Think again, the comparison is just idiotic.
Free speach is about saying whatever you want and the connection to software is idiotic
I’d like to quote the following that RMS declares as what makes it free as in free speach according to the 4th rule
“The freedom to improve the program, and release your improvements to the public, so that the whole community benefits (freedom 3). Access to the source code is a precondition for this.”
Freedom to release your software I agree on, but freedom to close the software is inclded in free speach as in, if you ehar someone say something you reflect on it, build your own opinion and CHOOSE NOT TO EXPRESS IT, it’s still free as in free speach… the GPL does NOOOOT comply to this and therefor the comparison is WRONG!
They write the code, they have the right to choose whatever license they want. If their new license requires that whenever you use their code, you have to list their credits – fine with me. I don’t see anything wrong with that.
OK, so it is not compatible with the GPL. So? I think compatibility (to anyting) is an unnecessary burden that has more importance than it deserves. If compatibility with existing software were crucial, then we shouldn’t have started with alternative operating systems in the first place and just stick to some ancient common denominator (how about MS-DOS? Let’s all be compatible to MS-DOS).
I think the free speech comparison is wrong too. I really don’t think that software freedom is anywhere up there with Constitutional freedoms. My point was not that, however. My point was that when the FSF uses the word free, they use it to mean that certain people (developers) give up certain freedoms (making non-free code forks) to ensure that other people (users) always have certain other freedoms (being able to modify the code of their programs).
To use a metaphor: BSD is like an Anarchy. It is more free than GPL in absolute terms, but it could possible lead to a non-free society — if everyone can do what they want, the strong can rule over the weak. GPL is like having a government and a Bill of Rights. *Any* form of government is less free (in a sense) than no government at all, but such a government can lead to more free society overall.
Thus, the word “free” doesn’t just have a single definition. Over time, people have ascribed to it different meanings. The FSF is simply using one of those meanings.
You are right… except that, in your metaphor, if you build your own opinion and choose not to express it, you would not be “distributing” your opinion (“derived work”). the GPL says if you build your opinion on other’s (or my) speech AND shares your new, “derived” opinion with others, you pass along the right to these others to build their own (“derived”) opinions, and pass along, freely. the BSD says you can break the NEXT level to form, and pass along, their opinions.
“Freedom to release your software I agree on, but freedom to close the software is inclded in free speach as in, if you ehar someone say something you reflect on it, build your own opinion and CHOOSE NOT TO EXPRESS IT, it’s still free as in free speach… the GPL does NOOOOT comply to this and therefor the comparison is WRONG!”
Under the GPL you have have the right close any software you want (-: You just don’t have the right to redistribute that if all the other authors don’t agree that you can. If you are the only author, seeing as how you still own the copyright, you can close it. You just can’t “Take back” what you have already put out there as GPL’d.
<2 cents>
GPL means freedom to study and learn source code for mutual benefits and making sure that no one can steal your source code, make additions and hide those additions from you. Think about it, how bad will you feel if you wrote 10000 lines of source code under BSD, some company came along, took your source, added 1000 more lines, and started selling it in market, without showing you those new 1000 lines.
BSD is more like a charitable license for everyone to benefit in the way they want to benefit. It has a good side that it gives commercial software to florish using others work but has a bad side that companies can steal your hardwork and make money. Its basically how you look at it.
I personally won’t ever like that my hardwork is sold in market without my benefit or without giving source code to the whole community, so i put my work under GPL 2.0 ONLY. I don’t add any later version, because that will give FSF control of my work, if they tomorrow release GPL 2.1 same as BSD or any other license.
</2 cents>
Thanks
Wolf
The problem, if there is one, is described in the following scenario:
I come up with some VERY GOOD nvidia accelerated drivers for XFree. NVidia corp. DID NOT HELP me writing the drivers in any way, so why should I give them the right to distribute a binary “nv.o driver build 8999” based on my work and with some improvements I could use too? So, I want to license my work under the GPL. if they decide to improve and distribute a derived driver, they must distribute the source.
If XFree goes for a GPL-incompatible license, this would not be possible, because e.g., Debian would be forbidden to distribute my driver at all.
“Free speach is about saying whatever you want”
This simply isn’t true. It’s all relative – I can’t think of anywhere that freedom of speech is as absolute as you seem to believe it should be.
Here in Europe there are various laws against e.g. publicly promoting Nazism. In the US you don’t have the right to spout off on private property (this includes e.g. cinemas and shopping malls) and even on so-called public property you can be stopped on grounds of creating a disturbance, causing an obstruction, inciting to violence…
“if you ehar someone say something you reflect on it, build your own opinion and CHOOSE NOT TO EXPRESS IT”
This is a ridiculous comparison that you make. Choosing not to express your opinion is choosing not to exercise your right to free speech at all.
The closest analogy I can think of in the software world is choosing not to distribute your derived work at all, and in fact the GPL does allow this – you only have to comply with the license when you *distribute*, because that’s all it covers. It says nothing about *use*.
Can you please please please stop misusing the word “free”???
FSF is after sourcecode which is FORCED to remain open, which therefor has nothing to do with the word Free. They use their name for branding but their name should be “Open Software Foundation” because they definitely have nothing to do with Free as in any free…
No. The FSF is after source code which is forced to remain free. Many Westerners claim they live in a free country; but are they allowed to take another person and claim them to be theirs? Of course not! The proposition is absurd and if it were allowed is tantamount to having no freedom at all! The FSF promotes free software, hence the name, and not free developers (though I’m sure they’d prefer that developers are not enslaved, but they rather have some limitations on them).
Furthermore, if something is open, that doesn’t mean you can change it. When my Uni has an open day, I don’t take that to mean I can rock up, build a new building, re-arrange classrooms to make it better; nor when a shop is opened am I allowed to touch anything and everything I please! If I had an open wound, I wouldn’t want J. Random Person to start poking at it and trying to learn about the inner workings of human physiology! Yet I’m given these particular freedoms with free software. In fact, the only real limitation on free software is that you aren’t allowed to close it, to strip it of its freedoms!
Free software, and much ‘open source software’, is a lot more than simply open.
(But don’t feel so bad. I’m on record as arguing against the GPL. This was before I realised the advantages it has, and I quietly converted a few months ago.)
Under the GPL you have have the right close any software you want (-: You just don’t have the right to redistribute that if all the other authors don’t agree that you can. If you are the only author, seeing as how you still own the copyright, you can close it. You just can’t “Take back” what you have already put out there as GPL’d.
Point is, in free speach you don’t have to give back the way to how you formed an opinion and distribute it without saying anything about inspiration etc. So the redistribution rule simply doesn’t apply to free speach but it sure does to GPL. However, BSD would more match the criterias as if you provide the whole concept behind it (as in sourcecode) you have to acknowledge the author of it…
Voila, BSD matches it better not GPL
Here in Europe there are various laws against e.g. publicly promoting Nazism. In the US you don’t have the right to spout off on private property (this includes e.g. cinemas and shopping malls) and even on so-called public property you can be stopped on grounds of creating a disturbance, causing an obstruction, inciting to violence…
Problem here (as in europe) with free speach is that because of people not being able to EXPRESS what they feel and discuss it properly, lots of underground groups appear and we get problems from it… which is also why the nazi movement are growing again in huge numbers all over europe. Now THIS is a problem and this is exactly what happens once restrictions is put on things…
When we describe GPLed software being ‘free as in freespeech, not as in free beer’, it’s an analogy. Like all analogies, it does not mean that it’s exactly equivalent. The message it is getting across is that of freedom, rather than pricelessness. I don’t think anyone would suggest that GPL free and freespeech free were exactly equivalent.
GPL means freedom to study and learn source code for mutual benefits and making sure that no one can steal your source code, make additions and hide those additions from you. Think about it, how bad will you feel if you wrote 10000 lines of source code under BSD, some company came along, took your source, added 1000 more lines, and started selling it in market, without showing you those new 1000 lines.
As in free speach, if I write 100 000 lines of an essay about animal rights, someone reads it, thinks about it, decides to build their own opinion, *DISTRIBUTE* their opinion without giving mine as a source I would NOT have any problem with it…
As in free speach, if I write 100 000 lines of an essay about animal rights, someone reads it, thinks about it, decides to build their own opinion, *DISTRIBUTE* their opinion without giving mine as a source I would NOT have any problem with it…
See my most recent other post; but also, Um… you realise that the GPL doesn’t demand you distribute the original, unmodified source, but rather your modifications to that source? The only possible similarities you could have in this case would be if you distributed a GPLed document in something like LaTeX, and then someone modified it and distributed it only as PDFs…
When we describe GPLed software being ‘free as in freespeech, not as in free beer’, it’s an analogy. Like all analogies, it does not mean that it’s exactly equivalent. The message it is getting across is that of freedom, rather than pricelessness. I don’t think anyone would suggest that GPL free and freespeech free were exactly equivalent.
You could also do a propagandha thing and say NAzigermany as in free germany. IT wouldn’t exactly match, but it could mean that to others…
I would say that is misusing the word free, just as the analogy in GPL is wrong just as the above.
Run “dict free” in your browser and see what it means… if you justify free as in free speach as in analogy GPL = Free.
Then you might as well justify a lot of evil thigns being called free….
“Point is, in free speach you don’t have to give back the way to how you formed an opinion and distribute it without saying anything about inspiration etc. So the redistribution rule simply doesn’t apply to free speach but it sure does to GPL.”
The GPL says nothing about having to explain your inspiration or methods. You just to give the program in a human readable way (source code). The same way in spoken language(the human readable form being the written word), you have to give the words you speak by the very act of speaking them.
Yes, The GPL is more artifical, but thats just it’s emulation of free speech.
The only real “free” license is the Public Domain. All other licenses, GPL/BSD/etc, place restrictions. Restrictions like always having to include names of authors in the code (BSD), or restrictions telling you what you HAVE to do with the code (ie always distribute source code etc). I think the GPL ppl should stop calling the license “free”, because in reality it isn’t so. Yes, the GPL has many good things about it, such as the license being designed to preserve code in the open, etc. But it is not free, only Public Domain is really free.
“which is also why the nazi movement are growing again in huge numbers all over europe”
Actually, in the vast majority of cases the far-right parties gain support through playing on the xenophobia of the general populace, which is in turn caused by insufficient integration of immigrants into the local community. Immigration and integration are the two key issues.
Your argument (paraphrased) “Nazism is becoming popular because of the fact people aren’t allowed to promote Nazism” seems rather circular to me.
Besides, nothing prevents these groups from meeting in private or conferencing over the ‘Net. I’m not personally a fan of the laws in question, but I have my doubts as to their effectiveness in stifling discussion on “forbidden” subjects anyway.
“Now THIS is a problem and this is exactly what happens once restrictions is put on things…”
No, I really don’t think that the GPL is contributing to the growth of the nazi movement… but perhaps that’s just me.
You could also do a propagandha thing and say NAzigermany as in free germany. IT wouldn’t exactly match, but it could mean that to others…
I really don’t understand that. You’re being delibarately obtuse. You aren’t contributing to the world by trying to express a differing opinion. You aren’t even trolling! You’re just being difficult.
My opinion on licenses is the same as Linus
he who writes the code gets to choose the license, people who complain about what license something is under are just whiners.
You can’t shout fire in a crowded theater. Do you still have free speech?
You simply needs to understand that GPL makes sure that no one can misuse other’s hardwork and sell it under their name. They force you to share your work derived from others hardwork so that they can also benefit like you benefitted.
I understand that its more like dictatorship, but with too many selfish out there, this is the only way to make sure that rights of the weak are defended.
You should understand that GPL gives people like us who don’t want to share our code due to the fear of it being misused by corportate, a confidence, to share it without fear. And thats why it rocks.
I don’t say BSD is bad or GPL is bad, both are different licenses. If tomorrow i right something, which i think can be best used in a commercial product, i will give it under public domain, so that someone can derive from it and sell it, but frankly it ain’t gonna happen, unless they pay me for my hard work. I am not a charitable trust after all.
– Wolf
sometime you need to force things to ensure freedom. Think about it, today you are free to sit in your homes and do what you want, because police and government is protecting you. You feel safe in their presence. Would you feel so free and safe, if there was no police?
If I am physically not a very big guy and if there was no police to protect me, someone will come and steal my money and i will sit their helplessly. GPL acts as a police to protect our freedom, our freedom to write code and share it, without the fear of it getting stolen.
How and Why you think its bad?
In many other languages it wouldn’t be an issue. In Spanish, for instance, people would talk about software being libre (unrestricted) or gratis (no charge). The whole “free as in speech” metaphor only exists because in English the word “free” includes two very different meanings. You can (and probably will) argue all day about just how free various licenses are, but the analogy to free speech isn’t about the code being speech, but about the language used to describe the license.
I understand that its more like dictatorship, but with too many selfish out there, this is the only way to make sure that rights of the weak are defended.
Yes, and the selfish people are those who use the GPL “so others can’t profit”. Think about it. If some company adds 1000, 10, or even 0 lines of code to your program and manages to sell it, then you could have done the same. If those 1000 lines of code are so important that the program without them is not worth anything, then maybe the company deserves to make money off their addition.
Since the code *you* wrote is released to the public, no one can ‘steal it’ anymore. That specific code is always avaliable. The GPL is basically like releasing products that “can’t be used by liberals” (or some other distict group).
All these analogies are really really wrong (with maybe the exception of Rayniers later argument). For instance, the park analogy is wrong because if you fence off the park, you are taking it away from the public. But code is not a park, it can be *copied* and the original is left untouched. It’s more like me cloning the park into my huge yard, putting a fountain in it, fencing it off and charging people to enter my park. The orignal park is still there for free, so if people are paying me for my park, maybe they are really just paying to see the fountain.
And as for GPL being used for learning, *it can’t be*. If you see GPL code you could be infuenced by it so that *your* code looks a whole like like it. With proprietary code this is a well known danger and often leads to employment clauses that prevent you working for companies developing similar products for x number of years after you quit. The same applies to GPL code. Those of us who *don’t* release our projects under the GPL have to treat GPL code as equivalent to proprietary code: stay away from it.
As for the new X license? I’d prefer it any day to a GPL license and therefore I’m almost glad it’s incompatible with the GPL. I still have the freedom to do *almost* anything I want with the code, so long as I include the proper credit.
The discussion is veering off the topic (at least it appears that way to me regarding the philosophical discussion on free and intent of the GPL).
But I would like to address what peragrin earlier “Some people here need to Fscking read the GPL. Understand something. YOU DO NOT LOSE YOUR IP UNDER THE GPL. It stays your under your copyright for etirnity”
But first I will babble about the licensing nature of GPL, in which I agree with those commenters who say the FSF is interested in forcing source code to remain open.
I have read the GPL license and it (version 2.0) says in clause 2b:
“You must cause any work that you distribute or publish, that in whole or in part contains or is derived from the Program or any part thereof, to be licensed as a whole at no charge to all third parties under the terms of this License. “
This is no doubt the reason MS labeled FSF software as viral. This clause clearly requires you to distribute your code under GPL if you use any GPL code.
Fortunately, many libraries provided a proviso that did not require the GPL being applied to binary distributions (see below):
/* As a special exception, if you include this header file into source files compiled by GCC, this header file does not by itself cause the resulting executable to be covered by the GNU General Public License. This exception does not however invalidate any other reasons why the executable file might be covered by the GNU General Public License. */
— As a special exception, if other files instantiate generics from this unit, or you link this unit with other files to produce an executable, this unit does not by itself cause the resulting executable to be covered by the GNU General Public License. This exception does not however invalidate any other reasons why the executable file might be covered by the GNU Public License. —
The introduction of the LGPL (or GPL 2.1) introduced in 1999, does away with the need for these special exceptions. Without this modification in the GPL, I doubt very much IBM would be supporting Linux the way it does today.
However, to say that you retain the rights to your software when you GPL it, is wrong. By GPLing your code, you are handing it over to the FSF. They in turn, let you license it. You may remain the author, but you no longer remain the owner.
From the GPL (GPL 2.0 omits the ‘we’ in ‘we copyright’, GPL 2.1 does not):
“We protect your rights with two steps: (1) we copyright the software, and (2) offer you this license which gives you legal permission to copy, distribute and/or modify the software.”
John
> The only real “free” license is the Public Domain
Take a look at http://www.gnu.org/philosophy/category.jpg
According to the FSF, “Free Software” and “Open Software” are the same. Pubic Domain is Free.
As for the definition of “FREE SOFTWARE”, it is very clear :
– The freedom to run the program
– The freedom to modify the program
– The freedom to distribute copy (original or modified)
The copyleft effect is another story, which is about the big question “The Answer to Life, the Universe, and Everything”
My answer is : “the ultimate free softawre is Domain Public”
> A company comes along and improves A and B:
>
> – They license A under GPL, I can still do
> lots of things with the code.
>
> – They don’t release code for B at all,
> I can’t do anything with the code.
You still have the original B program, which is “free”.
You can improve it, as the company did. They wrote the code, they choose the license
Sorry for the poor english. I am a stupid french programmer
This is no doubt the reason MS labeled FSF software as viral. This clause clearly requires you to distribute your code under GPL if you use any GPL code.
—
Duh. That’s the whole point of the GPL. If you want to benefit from the GPL, you in turn have to contribute back to the community.
The introduction of the LGPL (or GPL 2.1) introduced in 1999, does away with the need for these special exceptions.
—
The GPL and these exceptions are completely different. The exception in the header file is there to allow you to include the header in your programs without that counting as using GPL’ed code. The LGPL is something else entirely. If the header was under LGPL alone, without exceptions, you could *not* include the header in your program without L/GPL’ing your program. The LGPL exists for the following reason: Linking code with other code is the same, at the technical level, as including the sources directly into your source tree. This means that any code linking to a GPL’ed library must be under a GPL-compatible license. The LGPL exists to make an exception for linking, and allows applications under any license to link to LGPL’ed code. However
Without this modification in the GPL
—
It is not a modification to the GPL, but a seperate license entirely.
I doubt very much IBM would be supporting Linux the way it does today.
—
Since Linux is GPL’ed, the provisions of the LGPL do not matter. IBM has donated a great deal of code to Linux under open source licenses like GPL and LGPL. In fact, GPL is pretty popular among commercial companies because it lets them distribute the code without allowing their competitors to incorporate it into proprietory products. This is the reason that JFS and XFS were released under GPL rather than, say, BSD.
However, to say that you retain the rights to your software when you GPL it, is wrong. By GPLing your code, you are handing it over to the FSF. They in turn, let you license it. You may remain the author, but you no longer remain the owner.
—
The bit you are quoting is from the Preamble:
“We protect your rights with two steps: (1) copyright the software, and (2) offer you this license which gives you legal permission to copy, distribute and/or modify the software. ”
The problem is that you read it wrong. The “You” refers to the licensee:
“Each licensee is addressed as ‘you’.” (Clause 0 GPL)
The GPL is written from the point of view of the FSF. The developer is referred to as “the author.” The FSF is referred to as “We.” The licensee is referred to as “you.”
So I repeat: Unless you assign your copyright over to the FSF, you own it completely!
“so others can’t profit”
No, it’s “so others can’t profit while removing freedom”.
dumbass
No, it’s “so others can’t profit while removing freedom”.
If you read my post, you’d see that in no way are any *freedoms* being *remove*. The released code will be always as it was. The derived code has value added, and so restrictions might be placed on the added portions… but that doesn’t effect the original released code in the slightest.
* Any deratives of non XFree86 4.4.0 (earlier versions than that one) can still be used.
* The earlier beta’s don’t count neither.
* This includes the innovative fd.o
* The code and changelogs can still be watched and seen as how they fix bugs thus allowing others to fix these bugs theirselves.
* This while the development of earlier beta’s was still under the old license.
* Discussion seems still open.
No disaster *yet*, move along.
Anyone that argues “Free” and “free” are 2 different words needs to go back to school.
Good job parroting the FSF. Although, that’s not *my* definition of free software. The FSF can try laying claim to the term “free software” all they want. It has no relevance on our current discussion.
I could just as easily *clearly define* a term like so:
Definition: “free software”
Source code and software compiled from it that can be relicensed under any other license.
Weee. We are having fun now eh?
Dpi: You don’t believe you are a Jedi. You will forget what you saw here today.
By GPLing your code, you are handing it over to the FSF. They in turn, let you license it. You may remain the author, but you no longer remain the owner.
This is completely false. You don’t have to assign your copyright to the FSF if you release code under the GPL. Some people do, but the great majority don’t, and remain the owner of their software. They can even relicense it if they want.
That the word free and GPL is not friends…
Whether GPL is good or bad now that’s a completely different story and as some suggested, we’d all be better off with a dictator, I don’t agree. Even though I respect the opinion that someone thinks that a dictator or GPL would be the better choice for how to run things.
Indeed the author chooses whatever license to publish something under, but that’s not the problem. A Developer is a developer, not a lawman. Understanding a complex license like GPL which even lawmen has a hard time understanding is really difficult. However, many don’t know the differences and get printed in their face “GPL is free” etc which is just wrong. Don’t confuse what it’s about.
How does this affect the general user and why would he/she have a say about this?
Since GPL has a viral effect (I do hope a debate about that won’t start off) it’s also a question about how GPL affects R&D and what effects that has for humanity as well as software evolution. I could have a long run explaining that R&D and GPL don’t match eachother (which I actually think at least 70% of us would agree on) but I believe, as a user, GPL affects me badly in the long run… therefor I’ve dedicated parts of my time to work against it, just like I spend some time working against communism/dictatorship.
I’ll accept your point that the LGPL covers only binary linking, but does not cover the more general use of source code which gets compiled into binary.
And I will accept your assertion that GPL does sign over your copyright. From paragraph 10:
“If you wish to incorporate parts of the Program into other free programs whose distribution conditions are different, write to the author to ask for permission.”
But I still do not like the “viral” nature of the GPL.
Which is why I like the new XFree86 license because it only requires you to recognise the original source.
John
Sorry for the Anonymous, I’m now at home and forgot to fill the field.
I’m not “parroting”, I don’t like the FSF and their philosophy.
> Source code and software compiled from it
> that can be relicensed under any other license.
>
> Weee. We are having fun now eh?
http://www.opensource.org/docs/definition.php
An Open Source software is a free software. A free software is an Open Source software. You seem to think that a free sowtware is a copyleft software. It’s not.
Understanding a complex license like GPL which even lawmen has a hard time understanding is really difficult.
The GPL really isn’t that complex – it’s actually quite simple to understand.
Opponents to the GPL usually want to have the right to use the code for free, modify it, and then make a profit from it by releasing the resulting code under a proprietary license. In other words, they want a free ride (the irony is that some anti-Linux trolls will say they prefer the BSD license and then say that “nothing in life is free” – in other words, “do as I say, not as I do”).
If you want to make profit from selling software under a proprietary license, just write the code from scratch, use BSD code or buy some proprietary code under a license. But don’t complain that the GPL isn’t free just because it won’t give you a free ride.
Oh, and the comparison to a “dictatorship” (and the subsequent amalgamation of “dictatorship” and “communism”) are completely groundless. The GPL is an extension of Copyright, it grants more right than a simple copyright, and yet I don’t hear anyone saying that the copyright system is a dictatorship.
Off-topic: for the record, some of the most notorious dictatorships of the 20th century weren’t communist (and in fact were completely opposed to communism): Nazi Germany, Fascist Italy, Franco’s Spain, Chile under Pinochet (and in fact most South American dictatorships).
Authoritarianism/Liberalism is a distinct political axis than the traditional Left/Right axis. I suggest you check out this link to better understand the distinction (and learn something about your own political inclinations as well):
http://www.politicalcompass.org/
Reading all the way down to the bottom of the license (which is really, really tedious) I see that I was wrong in my assertion that GPL requires handover of the copyright.
However, one only clearly sees that in section 10. The preamble, certainly implied to me that you handed your rights over.
Sorry for any confusion.
It would be helpful for those who disagree to provide evidence of their disagreement.
John
It really wouldn’t make sense for a license statement to address the licensor, since licenses are written from the point of view of the licensor addressing the licensee. These sections of the GPL are not unclear in the least.
Actually, I’d argue, by my definition of free, that copyleft is *not* free, contrary to what the FSF thinks. My point was that it’s futile to worry about definitions since anyone can define what “free software” is to them.
GPL is GPL software. Simple. It’s free for end use, restricted for source use. The term “free software” is nonsense just leads to more flame wars. It’s only used by the FSF so that they can seem “holier than thou”.
…a discussion of the GPL turns into an onslaught of armchair lawyering.
Doesn’t it seem to anyone else as if the GPL is too vague and ambiguous for comfort?
“Umm, try comming up with coherent thoughts.
How is something with strings attached free.”
Tell me about ONE human activity that does not
come with strings attached.
Speaking? We (as in humans) have social rules for speech. (no
loud jokes on a funeral, no shouting in the cinema, no
telling da boss to go buy a donkey and get fscked by it).
Fine, you won’t go to jail, but you will:
a) Get the crap beaten out of you
b) Lose your job
c) run out of friends.
Sh*tting? pissing? You cannot do that in the middle of the street.
Walking around naked? Nope. See above.
Property? You have to pay for most things in order to own
them.
Taking up space in the world? breathing? anything at all?
Well, you HAVE to do something with your life. Get a job.
Work for some cause (even if it’s not your cause). breed.
If you get 100% anal about freedom, then you have to come
to the conclusion that NOTHING is free. Leave the GPL alone
if you don’t like it.
> Stop spreading disinformation about the GPL to promote
> your own personal agenda.
Ah, I expected this to happen. Everyone who speaks up against the GPL has “a personal agenda”.
Perhaps I just have an opinion, and excercise my right of free speech? (Ah, the irony…)
Why not ask yourself three things:
One – as maintainer of a piece of GPL’ed software, if you ever accept a bugfix by someone else, what happens to your IP, your right to release another copy of your code under a different license?
Two – how many GPL’ed pieces of software do you know that actually state a specific version of the GPL? And how many state “X.Y or later”, or omit any reference to the version?
There’s more, but I think if you really think about these two points, that’s already something.
> Tell me about ONE human activity that does not
> come with strings attached.
Writing code that other people could need, either to build a larger product or to educate themselves, and release it into the Public Domain so they can do so.
Releasing Linux as GPL was OK with me. Releasing gcc as GPL was OK with me.
But why must a C library be GPL, or a graphics cards driver, or “more”? What is the sense of discouraging the use of a cross-platform, cross-OS driver infrastructure for fear that Windows could benefit? (Last time I looked, they had all the drivers they need.)
You’ve stated that it would be better to put it as public domain, but this isn’t possible in every country.
ahaha, you’re one of those “fscked” people huh.
I bet you use “micro$oft” too..
As much as you seem to feel an uncontrollable urge to come to the defense of the GPL that still dosn’t make it free.
Something that has to redefine a word to exist is a bit suspect.
> Opponents to the GPL usually want to have the right to
> use the code for free, modify it, and then make a profit
> from it by releasing the resulting code under a
> proprietary license.
Scrap “profit”, say “revenue”, and you hit it.
I want to create a new, better operating system.
Should I actually make it happen, I would like to have the money to advertise it, to produce shrink-wrapped distros that people can buy for a cost-covering fee at their local convenience stores (without user #1 putting it online for free download and getting away with it), and I don’t want to go broke on paying the development / download server.
Now, I could do it the GNU way: Make the stuff so damn hard to understand that I can reap a fortune on manuals, consulting services, and user help desks.
But tell you what, I’d prefer to spend my time coding a system that’s so damn easy to use that no-one could sell a single copy of “How To Use XYZ”.
And since Mr. Stallman thinks I am “a social problem”, and even “educated” people like OSAlert readers think I’m spreading FUD and have “a personal agenda”, well, I have to write my own C library.
And because I think this sucks big time, and that no one should have to go through such basic a task about three decades after the invention of the language but rather spend his/her time designing better software for the people, I’ll release that lib it into PD where it belongs.
Some evil dictator am I…