Brian Aker Responds To RMS On Dual Licensing
krow (Brian Aker, long-time MySQL developer) writes "Richard Stallman's comments on the Oracle Acquisition of Sun left me scratching my head over his continued support of closed-source licensing around open source software. Having spent more than a decade in the MySQL community, I feel that his understanding of the dual-license model is limited, and is at odds with his advocacy of free software. For this reason, I believe his recent statements concerning it need to be addressed. By pushing for the right to turn GPL-licensed software into the heart of a proprietary business model, he is squandering an opportunity for advocacy of open source within the European Union."
Did someone just accuse RMS of supporting commercial licenses anywhere near Free Software?
Isn't there already an open source fork of MySQL? Is anybody actually paying for Sun's?
Ghostview used to have (and may still have) a dual-licensing setup -- the most up-to-date version of Ghostview was under a non-free license that could be purchased by companies that wanted Acrobat support on platforms Adobe wasn't interested in supporting, and the older versions of Ghostview were released under the GPL. I remember RMS commenting on this at the time, and his comment was "I'd rather it be all GPL, but if that's what the creator needs to do in order to support his work so be it."
Perhaps I misunderstand the article, but I don't see this as a new position or a deviation on RMS' part. I also personally disagree that it's "anti Open Source" -- first, on a pedantic level, RMS would say that the issue had nothing to do with "Open Source," rather it was about "Free Software." ;-) Second, and probably a lot more relevant, if software is licensed under the GPL, then it's licensed under the GPL. You're free to hack on it, distribute it, improve it, modify it, as much as you wish under that license, and any new work you add to that software under that license stays under that license as well. So what exactly are you losing?
Eviscerati.Org: All Hail the Eviscerati
Groklaw has an interesting take on this, full of conspiracy theories.
See, for example, this comment, where PJ is talking about Monty, and says:
I have come to suspect he's a double agent. And I believe the beneficiary will be Microsoft.
Wow
RMS could not care less about open source. He only cares about free software. There's a difference and he will go to great pains to point out the difference if you engage him using the term "open source." If you are going to respond to him, the least you can do is use the terminology correctly. Otherwise he'll interpret what you say differently than what you probably meant.
Cory Doctorow talking about cloud computing makes as much sense as George W Bush talking about electrical engineering.
what's the point of saying something i.e. "Let's not pretend that GPL software is any different" that's obviously false?
To call Stallman a kook and crackpot would be overly flattering. He isn't concerned with "freedom", he is only interested in pushing a personal agenda. That's what the GPL is really all about. If you truly believe in software freedom then you absolutely reject the entire notion of software licensing.
Have you ever bought a book? Furniture? Clothing? A toaster, microwave or television? Did you have to agree to a license before you could use any of these items? NO. If you want software freedom, then there is only one license -- no license at all. Here's the software, you are free do do what you want.
The makers of proprietary software force you to agree to a massive, complicated license before you can use their products because they want to control and restrict what you can do. Let's not pretend that GPL software is any different.
Ah yes, the WTFPL.
Your trollish demeanor aside, the GPL is nothing like a standard EULA.
In fact, using GPL software is much like reading a book. The issues of copyright never come into play until you get it in your head that you wish to redistribute the work in question. Copyright says "no you can't, go talk to the copyright holder" while the GPL says "yes, under these terms. If you don't like them, Copyright says no you can't, go talk to the copyright holder."
Whereas proprietary software requires you read and accept a license before using it. Completely unlike a book.
Hopefully you will understand Stallman and the GPL better now, or I will have to apologize for feeding a troll.
The GPL is not an EULA. In your book example, you can buy, read, resell, etc, the book in question. Exactly what you can do with any software, barring (possibly) an EULA.
You can certainly do all that with GPL software without ever reading or agreeing to the GPL. Agreement is not required for use.
Other actions, such as making and distributing copies, are restricted by copyright law, and apply to books as well as software regardless of license. The GPL happens to be a license which allows copying and redistribution, actions which are otherwise forbidden by copyright. You only must agree to GPL when you take action that bumps against copyright law.
You are conflating a "usage" license with a "distribution" license. I agree that the former is completely inane. But the latter is a necessary extension of the concept of copyright, and the basis of the GPLv2.
"I assumed blithely that there were no elves out there in the darkness"
While I agree that RMS is an ideologue of the worst kind, you're completely off base here:
Have you ever bought a book? Furniture? Clothing? A toaster, microwave or television? Did you have to agree to a license before you could use any of these items?
No. But guess what? The GPL doesn't require that, either.
The GPL, like all copyright licenses, is a *redistribution* license. ie, when you *redistribute* the software, at *that* point you are bound by the terms of the GPL, as it is under those terms that you are granted the right to redistribution.
What you're talking about is a EULA, and I don't believe it's clear that those are even enforceable (and whether or not they are almost certainly depends on the state/province/country you live in). And certainly EULAs have absolutely no grounding in copyright law (which, as I say, is concerned with redistribution).
Did you have to agree to a license before you could use any of these items? NO.
Are you serious? Maybe you should read the GPL before passing public judgment on it.
Activities other than copying, distribution and modification are not covered by this License; they are outside its scope. The act of running the Program is not restricted, and the output from the Program is covered only if its contents constitute a work based on the Program (independent of having been made by running the Program).
-- GPLv2
"When I first heard Daydream Nation it quite frankly scared the living shit out of me." -- Matthew Stearns
The letter from Stallman and the others discussed two ways in which forking MySQL would be hard. One was because it is under GPLv2 without the "or later" option, so cannot mix with GPLv3 code. That a pretty irrelevant point, though, because the problem lies entirely with GPLv3's lack of compatibility wity other free licenses, such as GPLv2.
The other problem the letter mentions, though, has nothing to do with GPLv3 vs GPLv2. Here is how they describe the problem. I'll include the GPLv3 argument for completeness:
Defenders of the Oracle acquisition of its competitor naively say Oracle cannot harm MySQL, because a free version of the software is available to anyone under GNU GPL version 2.0, and if Oracle is not a good host for the GPL version of the code, future development will be taken up by other businesses and individual programmers, who could freely and easily "fork" the GPL'd code into a new platform. This defense fails for the reasons that follow.
MySQL uses the parallel licensing approach to generate revenue to continue the FLOSS development of the software. If Oracle acquired MySQL, it would then be the only entity able to release the code other than under the GPL. Oracle would not be obligated to diligently sell or reasonably price the MySQL commercial licenses. More importantly, Oracle is under no obligation to use the revenues from these licenses to advance MySQL. In making decisions in these matters, Oracle is facing an obvious conflict of interest – the continued development of a powerful, feature rich free alternative to its core product.
As only the original rights holder can sell commercial licenses, no new forked version of the code will have the ability to practice the parallel licensing approach, and will not easily generate the resources to support continued development of the MySQL platform.
The acquisition of MySQL by Oracle will be a major setback to the development of a FLOSS database platform, potentially alienating and dispersing MySQL's core community of developers. It could take several years before another database platform could rival the progress and opportunities now available to MySQL, because it will take time before any of them attract and cultivate a large enough team of developers and achieve a similar customer base.
Yet another way in which Oracle will have the ability to determine the forking of MySQL relates to the evolution of the GNU GPL license. GPL version 2.0 (GPLv2) and GPL version 3.0 (GPLv3) are different licenses and each requires that any modified program carry the same license as the original. There are fundamental and unavoidable legal obstacles to combining code from programs licensed under the different GPL versions. Today MySQL is only available to the public under GPLv2.
Many other FLOSS software projects are expected to move to GPLv3, often automatically due to the common use of the "any later version" clause. Because the current MySQL license lacks that clause, it will remain GPLv2 only and it will not be possible to combine its code with the code of many GPLv3- covered projects in the future. Given that forking of the MySQL code base will be particularly dependent on FLOSS community contributions - more so than on in-company development - the lack of a more flexible license for MySQL will present considerable barriers to a new forked development path for MySQL.
I'm assuming that hell has frozen over, because the first argument is that forking won't work because the GPL does not let the forker use the dual licensing model to make money, and that letter is signed by Stallman.
Some of us would like to be able to support our development of Free Software directly through the software. Many of us support ourselves in other ways and don't care about this. But for those who want to get the support from the software, dual-licensing is a good way to do it.
It satisfies the folks who don't like the GPL, because it gives them a different set of rights in exchange for some cash. Both the contributions by other developers who follow the GPL and cash are ways of providing a quid-pro-quo for the original developer.
What it doesn't satisfy is the folks who want a free ride instead of Free Software, because you have to pay for a commercial license. And IMO that strikes a good balance.
Even RMS sees this. I think Brian's accusing him of being too moderate. :-)
Bruce
Bruce Perens.
Idiot. GPL software restrictions are on redistribution, not usage. That's a massive different to the license shit you mentioned.
Things don't work the way you think. The book you bought had a license, you simply did not have to agree to it. You're bound to it anyway.
Bruce Perens.
Er, have you actually read the GPL? From section 9 (GPLv3):
Erm, the GPL is a distribution license. You are free to run, modify, print and use as toilet paper, or do whatever as long as you do not distribute. If you wish to distribute the code, you need to follow the license and include your changes with it. I think even the biggest FLOSS zealots understand this. Why can't you?
As for this:
Have you ever bought a book? Furniture? Clothing? A toaster, microwave or television? Did you have to agree to a license before you could use any of these items? NO.
You don't have to with GPL code either. If you were to copy the book, or make knock-off furniture or clothing and then sold or distributed, you could likely be sued for it. If you sell or distribute GPL code, you just have to follow the license.
Said, "It's just like dice but it's got more sides And it tells me who lives and who dies"
I don't read here that Stallman advocates dual licensing. He is merely stating the historical situation of the mysql licensing model. Acutally, you can read between the lines of his letter to EU. His argument is that the dual license of mysql is going to kill mysql development. He says that only Oracle can hold a commercial license for mysql, and due to Oracle's conflct of interest, mysql will languish.
So, between the lines, I see a warning from Stallman to those who use dual licensing. You may get the benefit from developers contributing for free to the product, but in the end, you will be screwed if someone with big bucks becomes the one and only holder of commerical license.
Fixed that for you.
To call Stallman a kook and crackpot would be overly flattering. He isn't concerned with "freedom", he is only interested in pushing a personal agenda.
Huh? By that definition the same thing could be said about Thomas Jefferson, Karl Marx, or any person involved in politics that was considered "radical" where they really don't even believe in their own ideas.
I mean seriously... Say what you will about RMS ideas and disagree with them if you don't like them, but to say he only does the FSF and GPL for the ladies and money is retarded at best.
I mean if he's got an agenda what is is for? To get attention from forum nerds? The lulz?
"I am the king of the Romans, and am superior to rules of grammar!"
-Sigismund, Holy Roman Emperor (1368-1437)
The GPL places restrictions on distribution of derivatives of the work. It does not restrict in any way shape or form what users can do with the software, or even derivative works, so long as those never leave their hard drives.
Further, FOSS licenses grant you ownership rights over the work.
Proprietary software licenses on the other hand (I assume you're talking about EULAs and such) place restrictions on usage and distribution, and they only grant you licensee (not ownership) rights, which can be revoked at any point for any reason by the company you're getting the software from.
I might not be a big fan of Stallman and his philosophies, but if you're going to make a point like this about him, at least get the basic legalese right.
Web2.0: I love when people Flickr my cuil and digg my boingboing until my google is reddit and I start to yahoo
> If you want software freedom, then there is only one license -- no license at all.
Nope. You could license under the WTFPL, which is a recognized Open Source license, fully compatible with the GPL.
> Let's not pretend that GPL software is any different.
It is. There are absolutely no conditions imposed in order to use GPL licensed software, as long as you don't distribute it in any way. However, as you correctly point out, the average proprietary software's EULA has gobs of conditions which you have to fulfill to be allowed to even use the software as it was meant to be used. Probably one of the reasons why no one is actually sure if EULAs are enforceable.
I met with Monty a few months ago and could not convince him that he could carry out his business although the MySQL server was under the GPL. He appears to be locked into some GPL FUD that MySQL got from a lawyer in service of selling the commercial license even though - IMO - you've never needed one to run the server, just a few of the client libraries.
So, Monty is now attempting to rebel against the GPL unnecessarily because of this false conclusion.
Or perhaps his real strategy is to kill the Sun/Oracle MySQL business, leaving him and his company in an advantageous position.
What makes this doubly strange is that Monty has been paid. Something around USD $100 Million for about 10 years work - a pretty good rate, IMO. Whatever he put into MySQL, he got compensated for. And thus I don't see that he has much moral standing on this issue.
Bruce
Bruce Perens.
Sorry, but I just really don't get what the problem is either... ?
You don't agree to the GPL license to use or modify a GPL product. It is only concerned with redistribution, which would be blatantly illegal without the GPL.
Everyone is permitted to copy and distribute verbatim or modified copies of this license document, and changing it is allowed as long as the name is changed.
That last part is the deal breaker. I was looking for a truly free license, but this still doesn't quite cut it.
Another MS fanboi gets schooled. LOL.
If I'm the author of a GPLed piece of software I still own the software I wrote so I can decide to make a closed source fork. Did I get it wrong? If I got it right, dual licensing is a pretty normal consequence of my ownership of the code. The only way to prevent it would be to surrender the ownership of the code, but if I don't own it, how can I license it? Without an owner the code would be in the public domain where anybody can take it and use it for closed source projects. So what's the way out? Maybe a license that binds me to use the code only under its terms?
You're confusing EULAs with distribution licenses. Consider:
EULA: Microsoft produces Office. Before I can use it I have to agree to certain conditions of use. Copyright law restricts me from re-distributing (or creating new works from) it without permission getting permission from MS.
GPL: Sun produces Java. They give it to me and I can use it without agreeing to any conditions limiting my use of the software*. Copyright law would restrict me from re-distributing (or creating new works from) it, but Sun has already given me permission to do this through the GPL.
Doesn't Stallman claim to want freedom for "recipients" of software to be able to use it and modify it, and not a free-for-all for developers and distributors? If those are his goals, then whether you agree with them or not presumably people who produce and distribute software under the GPL either agree with them, or don't understand the point of the license.
* I'll acknowledge that plenty of software presents a copy of the GPL and asks you to acknowledge it before installing the software. This doesn't change the fact that the GPL does not take any rights away from you, it only grants you certain rights (with regards to redistribution and modification) that you would not have otherwise. In fact the GPL itself says that "You are not required to accept this License in order to receive or run a copy of the Program"
So, I'm an unethical evil person because I make money writing proprietary software. However, it's a requirement that MySQL be sold to a different big evil corporation that doesn't already have a database offering and that can make money off it, else they might not support it.
Sorry, my brain isn't big enough to hold the cognitive dissonance that is Stallman -- he gives me a headache.
WTF? You're bound by copyright law when you buy a book. Nothing more, nothing less. What is this license you speak of? Where do I find it? What makes it binding? How do I violate it?
I don't care about religious wars.
I get that since the companies want to do business in Europe, they have to follow the regulations and be approved and such.
However, they are US companies. Not EU companies.
So what can the EU actually do? If the US OK's it, surely the resulting company can be barred from doing business in the EU or whatever..., but even that more than likely would not hold.
I understand the practicalities, but I just wonder what actual power the EU has to stop US companies from joining.
If you ignore ACs because they are anonymous - you're an idiot.
Mod parent UP as informative
Mod GP DOWN as worng
$ make available
By pushing for the right to turn GPL-licensed software into the heart of a proprietary business model, he is squandering an opportunity for advocacy of open source within the European Union.
umm...RMS doesn't advocate Open Source. RMS advocates Free Software
...and that is all I have to say about that.
http://jessta.id.au
i think you should need a license to post such blatently wrong uninformed toss on slashdot, but there we go ...
I just posted this Brian Krow's blog, but it's caught in moderation:
I agree with a lot of your perspective here. I somewhat have to given your own contributions to the code ecosystem. But I don't see how this is incompatible with what KEI is arguing. Their letter is about a specific event with a specific company, whereas you are discussing general notions of what is better.
I don't see how RMS et al suffered from a lack of imagination. They are making a very credible case about the likely outcome of what is going to happen here and how that might impact end users, i.e. the general public, i.e. EU citizens. I'm not as close to the issue as you might be, but their case sounds right to me. And I hope the EU takes this into consideration. KEI is arguing that what was once MySQL AB can continue as an entity - whether a subsidiary or independent company - just not fairly under ownership by Oracle.
While their letter doesn't pass judgement on the MySQL project's choice of license, I read their case as a warning for people like you and I who care about software freedom: taking out the "and future versions" clause while offering the code under another licence will inhibit future contributions from the community at large. As others have noted, many were vaguely reluctant to trust MySQL's model from the beginning.
But, that's where the project now is, and that's where the company now is, and the decision to be made isn't about whether this is a cathedral or a bazaar - it's over whether Oracle should own that company and its assets (i.e. code copyright).
To which I would add: KEI's letter says nothing about a copyright holder's right to re-issue code under multiple business licenses, nor about any interpretation of a license's suitability for any business or community organizing model.
----
Not to be confused with Col.
Everyone is permitted to copy and distribute verbatim or modified copies of this license document, and changing it is allowed as long as the name is changed.
That last part is the deal breaker. I was looking for a truly free license, but this still doesn't quite cut it.
The quoted text does not pertain to works licenced under the WTFPL, but rather restricts what you can do with the license document.
In other words, the WTFPL is so free that works licensed under it are freer than the WTFPL itself!
Actually, pointing out why Open Source misses the point of Free Software isn't pedantic or irrelevant, these differences are real and they explain why RMS takes the position you just pointed out.
RMS, as you rightly point out, understands that non-free software which eventually becomes free software is significantly better than non-free software that stays non-free forever because the former leads to eventually respecting our software freedom while the other can lead to our loss of software freedom. The open source movement is interested in a development methodology aimed primarily at businesses, not framing issues in terms of user's software freedom. Open source proponents aren't taught to think in terms of user's software freedom. This too can lead to the loss of software freedom. So whenever someone licenses a non-free program, open source advocates have little reason to object despite how that chips away at our freedom (from the aforementioned essay, "This attitude will reward schemes that take away our freedom, leading to its loss."). Free software activists, on the other hand, lament the disrespect for user's freedom which motivates them to support a project to develop a free replacement so that everyone can do that job whilst retaining their software freedom. Finally, as for the GPL: RMS wrote the GPL with user's freedoms in mind. The reason we enjoy the freedoms you champion at the end of your post is precisely because RMS pays attention to all computer user's software freedom. Had he taken an interest in mere development methodology instead, proprietary derivatives might be far more common than they are.
Digital Citizen
RMS could not care less about open source. He only cares about free software. There's a difference and he will go to great pains to point out the difference if you engage him using the term "open source." If you are going to respond to him, the least you can do is use the terminology correctly. Otherwise he'll interpret what you say differently than what you probably meant.
That's right. Keep bringing this up. Keep treating it as important. The corporations that you're so paranoid about, love it when you do...because it means that while you're busy arguing about this, you're not providing them with any consistent form of opposition instead.
But then again, what am I saying? If you were one of the people who were actually helping Linux get somewhere, you wouldn't be on Slashdot.
Oops, I forgot to use the term, "GNU/Linux," as well. You'd better remind me not to do that next time, as well. After all, we know how critically important it is.
"Woe to you teachers of the law and Pharisees, you hypocrites! You give a tenth of your spices -- mint, dill and cummin. But you have neglected the more important matters of the law -- justice, mercy and faithfulness. You should have practiced the latter, without neglecting the former. You blind guides! You strain out a gnat but swallow a camel."
-- Matthew 23:23,24
That's the different between Open Source Software and Free Open Source Software
I don't know what dictionary you're getting your definition of open source from; but I take it you're not using http://www.opensource.org/docs/osd. It says
The license must allow modifications and derived works, and must allow them to be distributed under the same terms as the license of the original software.
See my other post: http://news.slashdot.org/comments.pl?sid=1414861&cid=29842015
From http://www.opensource.org/docs/osd:
The license must allow modifications and derived works, and must allow them to be distributed under the same terms as the license of the original software.
Also
The license shall not restrict any party from selling or giving away the software as a component of an aggregate software distribution containing programs from several different sources. The license shall not require a royalty or other fee for such sale.
I don't think the licenses you talk about are Open Source by what we might want to call the official definition.
The specification of "any later version" isn't part of the GPLv2, it's part of the authors text describing which licence(s) the code is released under.
Boffoonery - downloadable Comedy Benefit for Bletchley Park
The open source movement is interested in a development methodology aimed primarily at businesses, not framing issues in terms of user's software freedom. Open source proponents aren't taught to think in terms of user's software freedom.
Umm, no. The supposed "Free" software proponents like to try to make this distinction, but unfortunately it's bogus. You think some coder has business in mind as he contributes to Apache projects or zlib/MIT/BSD licensed projects? Haha, right... He has the users of his software in mind (which probably includes himself), and that's not any different than someone who is contributing to GPL software.
If you want to make a distinction, it's that so-called "open source proponents" realize that businesses may also be users, and they don't have a problem with that or forcing users to meet certain obligations with respect to modifications and distribution. That's all. As someone who agrees with the ideals of "copyleft" and the GPL, it might stroke your ego to think that your kind are the only ones who have the user's freedoms in mind ("think of the users!"), but perhaps its good if a little truth helps deflate some of that for you.
This too can lead to the loss of software freedom.
Software licensed under Free licenses such as MIT, zlib, and BSD can become less free no easier than can GPL software. I know this may fly in the face of the dogma you've always thought concerning how the GPL is supposed to be more protective of users' freedoms. In reality, if a company cannot meet the requirements of the GPL, we are no better or worse (in terms of the amount of public code) even if said company finds some BSD-licensed code to build off of and keeps their changes proprietary. Their alternative would be to build everything in-house, and it will still be proprietary anyway. On the other hand, many companies (that are legally able) do contribute their changes back to Apache, MIT, zlib, BSD-licensed projects every day (even if they have no legal obligation), as they do GPL projects. These two facts combined with the realization that code which has been licensed freely cannot then be retracted (there will always be a public fork) should be enough to make obvious to you that the popular assumption that the GPL is legally or morally better for users' freedoms resides on shaky ground.
The GPL is a decent license, although considerably more complicated than most people and projects need. It does have one notably interesting feature, although ironically (and arguably) it is related to user freedom in a negative way, which is what this article is about: the GPL can be used alongside a proprietary one. That's not something that is easily accomplished with other Free software licenses, but I don't consider it a bad thing. It's the one unique feature that really makes the GPL worthwhile in my estimation.
This author takes full ownership and responsibility for the unpopular opinions outlined above.
The open source movement is interested in a development methodology aimed primarily at businesses, not framing issues in terms of user's software freedom. Open source proponents aren't taught to think in terms of user's software freedom. This too can lead to the loss of software freedom.
Right on.
The "Open Source Movement" AKA the "Linux Movement" advocates free software by shoveling purist ideology down people's throats whether they want it or not. :\
The whole "If we port it to Windows [or FOO], we will hurt Linux" concept is straight from Open Source land. "Open Source" is like a parasite, slowly strangling free software
Message to open source advocates:
People shouldn't be pressured to use one thing or another becauses of your beliefs. Lets keep this in the scope of software development where it belongs...
Posts that speculate about their moderation fate induce nausea. Moderation is vicissitudinous. That's the deal. Enough with the existential shirt rending, even if I agree with you.
What I'd like to see the adoption statistics of Postgres vs MySQL after subtracting out everyone who has expressed even the vaguest warm and fuzzy business sentiment about "monetizing eyeballs". Most people I know divide by some large number whenever this term comes up, except when quoting MySQL's enormous install base. I don't get it.
MySQL's original strength was rapidly generating page views containing data that was either 1) not very important, or 2) securely stored somewhere else, or 3) not worth thinking about in the frenetic pursuit of a profitable quarter. The big bang for open source database adoption was the second half of the 1990s, when monetizing eyeballs was cliff-jumping delusion of choice. It's clear nevertheless that MySQL won class presidency by a landslide. Isn't it?
One company out there that seems to be doing quite well lately is Atlassian. They strongly support the use of Postgres in conjunction with their Tomcat application suite. They are presently offering six tools on a heavy discount for small teams: issue tracker, wiki, source code inspection tool, agile PM, continuous integration server, and an OpenID server. I can speak well of JIRA at this point, not much experience yet with the others, but I'm doing the full-on Postgres installation tour of all six.
These are applications where the customer consumes their own data, so integrity of the data outweighs page view performance. Not that there's so much difference at this point due to convergent evolution. What irks me though is that MySQL gained its initial reputation on an inflated resume. I'm just saying that MySQL's storied success on prom night should be taken with a grain of salt. Ms Nortel 1999 is now a 30-year-old crack-ho.
My investigation of the Atlassian tool suite is an exploration of the uncomfortable boundary between pure open source and commercial software with attractive low-end adoption clauses. Atlassian seems to be 100% in the Java development camp, but with no special love for Oracle. I'm sure that will cause Larry some heartache. Is freedom from the hairy arms of Bugzilla worth the risk of being BitKeepered? I don't mind using Bugzilla, but I'm loath to administrate it. Time will tell whether I've sold my soul for a bad price.
is a quote directly addressing the proprietary software businesses. (Read the question.)
Since, for at least part of my life, I was a sole proprietor delivering proprietary software solutions, then, according to Stallman, I was acting unethically.
I also believe that he said I was evil. I will grant you that, in parsing English grammar properly, he might have said the software was acting evilly, and not me, but at the same time, I will have to assert that IMHO you are, deliberately or not, being obtuse about what he really meant.
I mean, it's pretty fucking obvious to me that he called me evil and unethical. YMMV.
While I agree that RMS is an ideologue of the worst kind
Of the "best" kind, for sure.
Stallman is considered by some to be a pure saint. People think he lives his life without compromises. Yet, he simultaneously holds the position that proprietary software is evil, and that people who write GPLed software won't do so unless they are incented by the ability to sell non-GPLed copies of that software to evil people who are going to merge it with their proprietary software and sell it for a profit.
If I believed that someone was evil, I wouldn't have anything to do with them, and if I merely thought they were misguided, I wouldn't use that term -- it is very heavily loaded. I would almost go so far as to say Stallman is evil for using it. (See how that works?) Personally, I believe that Stallman has done some good things, but also has some stuff to answer for, and calling me evil is one of those things he will eventually have to answer for. He and his followers are not yet as single-mindedly obsessed as the Taliban or the anti-abortionists, but they are getting there.
-1, troll.
If you don't understand the purpose of the GNU GPL, and the significance of "embrace, extend, and extinguish", you should keep your ill-informed opinions to yourself.
You got that right. If only all ideologues were as charitable as RMS.
Also you can modify GPL software yourself, and not release the changes so long as you don't release the software. It is legal to modify copyrighted works you own. You can draw on a painting, write on a book, etc. So a company could very well take GPL software, modify it for internal use, and never release either the changes or the finished product.
The GPL only comes in to play if you wish to redistribute GPL'd software. In that case, you have to distribute source as well as binaries. However that doesn't apply if it is something you just use yourself.
Props up again.
The EU does not have any power to stop US companies from merging. But they do have the power to forbid you to do business in Europe if a US company does not comply with its regulations.
Since the EU is a major economic player in the world and Oracle and Sun both have large stakes there, this becomes an issue.
It's not a matter of the EU taking over US companies, but rather the fact that US companies need to play their game when doing business outside the US.
Don't quote me on this.
Tell that to the Wine developers.
Now Stallman himself turns out to be a traitor too! Traitor! Traitor!
And developers of closed source software are very well aware of this (as is anybody else really, including users of any kind of software: I have the code, I have more power; I don't have any code, I am powerless).
You may not be an evil person, but certainly the situation of complete dependency in which you put your clients could be aptly described as evil (the path to hell is paved with good intentions they say).
It is always though when somebody finds something unethical about the way you earn a living (there are many cases of this situation), but the rational answer is not pretend nothing is happening, since clearly a lot of people think they are being short changed by closed source software providers.
IANAL but write like a drunk one.
You are really stretching it there.
There is not such a legal thing in existence.
IANAL but write like a drunk one.
And we will have nothing but what Sun wanted to give. If anything.
Remind us, what is Apple giving away as a thank you for the BSD base of OSX?
IANAL but write like a drunk one.
It is legal to modify copyrighted works you own.
Unless you're doing it to circumvent a copyright protection system of course...
It's official. Most of you are morons.
The makers of proprietary software force you to agree to a massive, complicated license before you can use their products because they want to control and restrict what you can do. Let's not pretend that GPL software is any different.
Last time I checked I didn't have to agree to ANY license agreement to use GPL software.
Browse at -1 to keep an eye out for abuses.
Every time rms is brought up, someone hauls out this phrase "extremely narrow definition of free"
Really? Narrow? *Extremely narrow?!?? How many licenses are considered free?
http://www.gnu.org/philosophy/license-list.html
Software is free if it respects the four freedoms. They're clear and, in my opinion, not the slightest bit narrow.
Nine times out of ten this comes from someone who prefers "permissive" licenses to copyleft ones. But these *are considered free by the FSF.
Are you just tweaked that rms and others *prefer that copyleft licenses be used? That's nothing to do with how "narrow" their definition of free is. It's a pragmatic argument about which intelligent people can disagree.
But this "extremely narrow" business serves no purpose vis-a-vis intelligent disagreement. It's a rhetorical whack meant to associate principled advocates of free software with limitations,restrictions & unfreedom.
My turnips listen for the soft cry of your love
Of all the Big Names (TM) in FLOSS (yes, I know), why is it that Bruce always comes across as the most calm and logical? Maybe it's just the way my mind works, but I have always found Bruce to be clear and easy to understand.
Thank you, Bruce. Go get them, tiger.
Books (and software code) fall under copyright. So it's different than a license... You can't as well copy parts out of a book and call it your own without giving due credit to the original author. That kind of attribution is what the GPL helps sort out, though.
If you want a more truly free license, than go with one of the BSD'ish ones, that allow companies to take the code and roll it into their own proprietary black box. I think philosophically the BSD license only seeks to maintain copyright so that same company can't greedily claim copyright for themselves and start suing everyone else for using the same BSD code they stole. So you see why at least /some/ licensing terms are necessary. As a contribution to society, BSD only wants to make sure that the code used by all these proprietary products has a solid foundation. Just think... if it wasn't for the BSD network stack, Microsoft OS's would probably be completely pwned off the internets by now...
GPL does take licensing quite a bit farther to make their contribution to society... it is a vendetta against proprietary lock-in (and all those poor SOBs that had to attempt to deal with bugs in proprietary code with binary fiddling and patching... I figure RMS was particularly scarred by something like this in his younger years, and fully understand how he could have gone off the deep end as a result.) Proprietary lock-in is a form of extortion, which I think most people will agree is quite unethical.
On the other hand, I think a lot of people and businesses have the misconception that the GPL automatically means "public domain"... nowhere in the GPL does it state that the GPL'd code that you modify and give to someone else also automatically has to be released back upstream too. It can stay completely private between you and your customer. It only stipulates that you have to give your customer the power to fix your code, and also that the customer can go on and give the code to the rest of the public (and all of their competition) too if they want, or they could also take it to another programmer (your competition) if they want. That's the viral freedom-as-in-libre. It's not necessarily free-as-in-gratuit / beer (though a lot of OSS code is in addition to being GPL'd).
We're transitioning from a manufacturing economy to almost a completely imaginary intellectual property economy. The ones with all the money and power will be the ones with all the licenses - also imaginary. Think about that.