Slashdot Mirror
FSF Releases Fourth and Final Draft of GPLv3
An anonymous reader writes "The most notable changes found in this latest draft include making GPLv3 compatible with version 2.0 of the Apache license, ensuring that distributors who make discriminatory patent deals after March 28 may not convey software under GPLv3, adding terms to clarify how users can contract for private modification of free software or for a data center to run it for them, and replacing the previous reference to a U.S. consumer protection statute with explicit criteria for greater clarity outside the United States.
The draft also does not prohibit Novell from distributing software under GPLv3 'because the patent protection they arranged with Microsoft last November can be turned against Microsoft to the community's benefit,' FSF executive director Peter Brown said."
GPLv3 is a key event in Microsoft's war to divide and conquer the Free Software / Open Source community. Most of the Linux industry seems to be betting on GPLv3 to put an end to Microsoft's patent claims. My question is simply: is Microsoft sitting around scratching its head, or has it already started on the next level of play...? Are we going to see those 235 patents handed over to the community, or are we instead going to see "IP Bridges" as the next great Product to come out of Redmond?
My blog
Is the GPL going to play catch-up with all the [il]legal deals that the big bad companies make? I hope not.
Ok, so it's not worded specifically towards the MS-Novell deal, but the date is in there to exempt that deal because it can be turned against Microsoft if it is allowed. That's bad. The GPLv3 is going to be with us for decades. It doesn't feel right to have that one-off thinking in there.
I am not clear what they are talking about, being able to turn these protections around to the FOSS movement's advantage? Frankly, so long as OpenOffice is at risk, I would say there is still quite a bit of risk, since most end users are more concerned with being able to use office/e-mail then about network backends (such as Novell netware).
Can anyone give some clarification?
More politics.. Who really need it? Really don't people have anything better to to? Like, ACTUALLY writtig software?
It's time to realise that Abble's products are the biggest abomination these days. Just say NO to the dumb iAbble way!!
People want guarantees that their software is not closed up by someone else; in other words, that it stays open and that all descendant software stays open too. For that people need a certain amount of regulation. Some people choose to call that politics, but regardless of its name, it's a necessity nonetheless. A bit like the way it's impossible to maintain a free society without some form of government. Everyone hates it, but nonetheless agrees we need it.
The patent thing is going to backfire big time. It's going to scare away businesses who would either stand to lose huge amounts of money or because they're unsure about whether it would invalidate patents they already have (what if the software is designed specifically to perform a piece of CAM in a way that's patented? Would that patent become invalid because of this licence? Would patented business practices that use OSS be threatened? Why risk losing millions in licence fees when you could spend a few hundred thousand and fit your systems with software you know doesn't rob you these rights?
For a licence that was supposed to be simple and easy to understand, section 11 makes for a hard read, even for geeks and I imagine lawyers will love the the potential vague nature of those terms. God knows what a layperson would think when reading it.
It's good that RMS is now telling everyone what are morally acceptable uses of software. I thought the idea of freedom was the freedom to do whatever you wanted with the software, so long as you shared the work. Apparently freedom doesn't matter quite so much when you have a chance to take shots at "ideologically impure" groups and start a pissing war with Microsoft.
This is all really, really sad.
Which, like that of Stevens, cost a lot without exactly going anywhere useful, no doubt.
Get thee glass eyes, and, like a scurvy politician, seem to see things thou dost not.--King Lear
the GPL3 fiasco should serve as a wake up call to companies which are trying to shift to GPL software either for development or use. The fact is you can't make a business model based around the current GPL version because once you switch to GPL software you become the bitch of the FSF. What is to say the FSF will not add other restrictions on the software you use? It is entirely usage clause will be added that limits what you can do with GPL software. In addition when there is a licence change like this eveyone needs to get legal involvd again to make sure GPL software is still usable. The parts where GPL infects patent deals is really disturbing. As each day goes by it really does seem like MS might have a point about the GPL being a viral licence. In this case it has mutated to infect unrelated areas of business after entering the host.
This has got me seriously looking at BSD instead of GPL stuff. At least BSD will not change on you like this. We will probably shift to Macs at work. I see the release of GPL3 as the beginning of the end.
The war with islam is a war on the beast
The war on terror is a war for peace
There is non-copyleft, like BSD: it's free, you might make it non-free or copyleft or keep it like it is.
There is copyleft: It's free and you may not make it non-free.
And there is anti-copyleft: It is free but you are allowed to make it non-free (by imposing the condistions of the Affero GPL for example) but you may not restrict the possibility to make it non-free.
You keep using that word. I do not think it means what you think it means.
I heard Microsoft is looking for someone to sort out their patent archive... 235 are missing, you see...
Free beer is never free as in speech. Free speech is always free as in beer.
I had a look. The controversial anti-DRM clause seems to be in part #3 of the license:
No covered work shall be deemed part of an effective technological measure under any applicable law fulfilling obligations under article 11 of the WIPO copyright treaty adopted on 20 December 1996, or similar laws prohibiting or restricting circumvention of such measures.
When you convey a covered work, you waive any legal power to forbid circumvention of technical measures to the extent such circumvention is effected by exercising rights under this License with respect to the covered work, and you disclaim any intention to limit operation or modification of the work as a means of enforcing, against the work's users, your or third parties' legal rights to forbid circumvention of technical measures.
The definition of "convey":
To "convey" a work means any kind of propagation that enables other parties to make or receive copies, excluding sublicensing. Mere interaction with a user through a computer network, with no transfer of a copy, is not conveying.
As for the FSF getting stuff done, I am happy to use corutils and all the other tools that have been written and maintaned by the FSF. If you are trying to make the argument that the FSF hasn't actually contributed any significant code to the community, you are going to have to try a little harder.
One practical issue: it will be nice if somebody (Debian?) could write a script that makes it easy to scan source hierarchies for GPLv2 comments so they can be replaced consistently with GPLv3. The last time the FSF changed its address, it was a pain to check and change all the boilerplates.
The goal of the GPL, the GNU project, and the FSF has always been software freedom, first and foremost. If a business finds no value in making changes to the way they do things to reap the benefits that Free Software brings, then they are free to not use any GPL'ed software. It's as simple as that.
That said, most of the big businesses currently interested in Free Software, including some which have HUGE patent stores, like IBM have actually participated in the drafting of the GPLv3.
You're obviously trolling but I'll bite. The FSF is now more relevant than ever. Version 3 of the GPL is just trying to close loopholes. If you don't like it, don't use it.
8 of 13 people found this answer helpful. Did you?
No.
The BSD is nice and simple, but it's only of use if you're happy to basically work for free for some random corporation.
Look at NetBSD for example. It's stagnated to the point of irrelevance, while Linux keeps getting more and more polished and more and more popular.
If anything, the BSD will the one that will die, when people realize that corporations have no concept of playing nice or gratitude.
The trouble is, you need business to be on board. There's no way a group of separated individuals working in their own time would be able to produce a large project that rivals something produced by dedicated teams from Microsoft, Adobe or any other large corporation. At some point all the large major OSS applications have had the input and time from a big business to improve on them, particularly in the case of simple user interfaces which are all too often a stumbling block for OSS.
I choose neither. BSD anyone?
But don't the anti-patent provisions in GPLv3 only prevent war WITHIN the open source community? In effect, they will stop the Trojan Horse of patented open source code being used to extort money.
What they DON'T stop is someone without ties to GPLv3 code taking patents and launching an attack. I always thought that IF such an attack would come (at least on a large scale), it would be far more likely to come from someone like Microsoft who would be untouched by any GPLv3 conditions. Small scale bullying might (and in some cases apparently has already) take place, but a large scale "destroy the free software ecosystem" attack I always thought was more likely from someone who had no financial incentive to see free software exist. After all, even patent trolls need someone to attack, and if they kill the free software world there will be nothing left for them to prey on except people who can afford lawyers to fight back. Admittedly they would survive, but I doubt they would be institutionally committed to the destruction of free software.
I admit it might make a repeat of the SCO fiasco with patent claims instead of contract and copyright laws somewhat less likely, and that's beyond question a good thing, but it doesn't reduce the large scale threat in any important way I can see. It's still a patent version of the MAD directive that's holding things in check, and (like the real Cold War) if anyone starts shooting the whole works (commercial AND open source) could go down the drain (in the US at least, and I am regrettably certain at least a few large corporate interests and US lawmakers will do their best to make the consequences felt elsewhere, if only to avoid competition getting an edge by not having to fork over for lawyers to fight patent issues.
What we REALLY need is software patent DISARMAMENT. Reform. What have you. I don't doubt ingenious folk in the commercial world will look for some other way to achieve the same end (as some insightful person said - "the only thing necessary for evil to triumph is for good men to do nothing") but at least this particular gambit will be over.
The ideal case from our side would be to have protection for software that is given away at no cost (with source code) to the benefit of society. Of course the whole "limited monopoly to promote innovation that is publicly disclosed" bit would need to be debated, but at least we would be HAVING the debate. Software patents are just a manifestation of one view of how society should function. There are other views, and I would much prefer to see the debate take place on a societal level in a serious way than to drain the industry's resources fighting legal skirmishes. Life is too short for that, and there's too much code to write.
"I object to doing things that computers can do." -- Olin Shivers, lispers.org
Or they could, you know, use a BSD.
Would it have killed them to link to the actual draft and documents? Here are the links:
Please help publicise swpat.org - the software patents wiki
Kids remember to look for the Free brand label. Free brand software it's the selfrighteousiest! There is no free but Free. Oh wait, that's right a lot of the open source GPL using world won't be going to GPLv3, because a lot of those projects don't require divestiture of copyright. And probably even some of the projects managed by FSF won't be able to go to it, because they maintain a lot of projects that were started by other people and don't neccesarily have copyright providence over all the code they inherited. Oops.
Turning the patent protection agreement into a benefit for the community is nice and all, but I was really hoping for a big "GTFO Novell". Oh well...
business *is* on board. IBM, Nokia, Sun, and many others participated in the drafting of the GPLv3. They probably don't care much about the whole "freedom" aspect, but they find that Free Software is great for their bottom line.
My point is that the authors of the license care more about end-user freedom than about whether XYZ inc. will like the license or not. And that is as it should be.
BSD isn't using any GNU tools these days?
If you mind working for free, why are you writing free software in the first place? The BSD license doesn't just help one corporation - it is just as easy for everyone to incorporate and thus increases competition. Increasing competition helps everyone. Monopolies are the real evil and if it weren't for BSD licensed code there wouldn't be any competition to Microsoft at all - and Microsoft's own code probably still wouldn't work.
I don't see the justification for that sort of pessimism. Of course they'll fight back as we continue to eat their lunch. That doesn't mean we haven't eaten anything or that we should stop eating now.
Please help publicise swpat.org - the software patents wiki
That can work sometimes, but not always.
If we have an application with round buttons and they turn out to be patented, we just make ours square. That's ok because having round buttons is not the purpose of the application. But if we have an application whose purpose is to read and edit MS Word documents, and a patent says we are not allowed to do that, then that application is kaput.
Here are some good explanations of how the patent problem plays out and what we can and can't do about it: http://fsfe.org/transcripts#patents.
Please help publicise swpat.org - the software patents wiki
I can't see any other reading of this. Which raises the question: what were Novell smoking when they signed the deal? If Microsoft predicted this kind of clause in GPLv3 (which you can be fairly sure they did), they essentially tricked Novell into signing a contract saying "We're going to stop distributing the very software which is core to our business" and Novell went on record saying how great this contract is.
I have a lot of trouble believing that. In which case, exactly what patent protection does this contract provide?
Only when doing so it necessary in order for the GPL to do it's job.
Please help publicise swpat.org - the software patents wiki
No, you're wrong. We're free to use and create proprietary software and GPL 2, BSD, etc., etc. We're even free to create our own open source software licenses if we want. You're the one with the all or nothing mentality that borders on following a cult.
Open Source represents both a social revolution and a mutation of capitalism. It's not going to be a vehicle towards RMS's Socialist revolution (note the difference between social revolution and Socialist revolution). If anything, open source represents the anarchist form of socialist revolution; RMS seeks to impose control over that revolution. He wants centralized control over it. GPL 3 moves us towards a collectivized proprietary license, which brings to mind "in with the new boss, same as the old boss".
So, go ahead and limit your choices and allow RMS to protect you by limiting those choices. There are plenty of other licenses for the rest of us. We'll be enjoying interoperability while you languish in your walled garden.
It's not offtopic, dumbass. It's orthogonal.
This argument is funny. What it translates to is: "I want to write 'free' software, but I don't want anyone else to make money off my work" -- Or more directly, "I want to be greedy but not appear to be"
The BSD license will be around for a long time, since there are plenty of people that code for fun, or to do something they needed done, and don't give a damn about being paid for it, regardless of what others do with their code. As for NetBSD - I'd venture to guess its stagnated for the same reason most large projects do: Bad or NO leadership, combined with other projects doing similar things (FreeBSD, OpenBSD).
Likewise, the GPL will be around for a long time, as it fills the need for others who want some sort of control over their software.
I guess I don't see why one license has to "win" over the other. Use what you like. Just don't bash other stuff.
If anything, the BSD will the one that will die . . . Where have I heard that before? Oh yeah. I've seen it before: It is official; Netcraft now confirms: *BSD is dying
One more crippling bombshell hit the already beleaguered *BSD community when IDC confirmed that *BSD market share has dropped yet again, now down to less than a fraction of 1 percent of all servers. Coming close on the heels of a recent Netcraft survey which plainly states that *BSD has lost more market share, this news serves to reinforce what we've known all along. *BSD is collapsing in complete disarray, as fittingly exemplified by failing dead last in the recent Sys Admin comprehensive networking test.
You don't need to be a Kreskin to predict *BSD's future. The hand writing is on the wall: *BSD faces a bleak future. In fact there won't be any future at all for *BSD because *BSD is dying. Things are looking very bad for *BSD. As many of us are already aware, *BSD continues to lose market share. Red ink flows like a river of blood.
FreeBSD is the most endangered of them all, having lost 93% of its core developers. The sudden and unpleasant departures of long time FreeBSD developers Jordan Hubbard and Mike Smith only serve to underscore the point more clearly. There can no longer be any doubt: FreeBSD is dying.
Let's keep to the facts and look at the numbers.
OpenBSD leader Theo states that there are 7000 users of OpenBSD. How many users of NetBSD are there? Let's see. The number of OpenBSD versus NetBSD posts on Usenet is roughly in ratio of 5 to 1. Therefore there are about 7000/5 = 1400 NetBSD users. BSD/OS posts on Usenet are about half of the volume of NetBSD posts. Therefore there are about 700 users of BSD/OS. A recent article put FreeBSD at about 80 percent of the *BSD market. Therefore there are (7000+1400+700)*4 = 36400 FreeBSD users. This is consistent with the number of FreeBSD Usenet posts.
Due to the troubles of Walnut Creek, abysmal sales and so on, FreeBSD went out of business and was taken over by BSDI who sell another troubled OS. Now BSDI is also dead, its corpse turned over to yet another charnel house.
All major surveys show that *BSD has steadily declined in market share. *BSD is very sick and its long term survival prospects are very dim. If *BSD is to survive at all it will be among OS dilettante dabblers. *BSD continues to decay. Nothing short of a cockeyed miracle could save *BSD from its fate at this point in time. For all practical purposes, *BSD is dead.
Fact: *BSD is dying
It's not offtopic, dumbass. It's orthogonal.
I'm curious whether all this back-and-forth went on when the GPL v2 was written. Is there anyone here who remembers that process?
It boils down to all software being BSD-like in its distribution restrictions (i.e: No restrictions). However the situation will be much closer to a GPL world one, because the incentive to create closed software that you cannot sell will approximate nil. Closed-source's single advantage over opensource - its ability to raise disproportionate funds for its development will disappear and opensource software will simply outachieve it.
If I had point, I'd mod you up.
It's important for people to realize that the GPL3 wasn't drafted in isolation. It was open and had a wide variety of participants, several with immense legal resources that helped guide the drafting.
*sigh* back to work...
Absolutely not. I'm fine with them making money off it. I'm not fine with them taking it and not giving back. I absolutely hate the idea of that something I write might one day end up in a Tivo-like device, where nobody can improve it further.
For instance, IBM benefits from contributions to the Linux kernel. This is fine, IBM returns the favor by then releasing their own code. If I write say, a driver, then IBM finds a bug and fixes it, they'll have to release the source if they plan to distribute. This is how I like it.
On the other hand, I don't ever plan to contribute anything substantial to a BSD licensed project, unless I'm being paid for it. Did BSD ever see any improvements to the code used by MS? I bet they haven't.
Incidentally, one of the reasons of NetBSD's stagnation was exactly that, the license. If you don't believe it, there was an article on slashdot about it. Wasabi Systems, one company that uses NetBSD, hired NetBSD developers. Of course since under the BSD they have no obligation to open anything, from then on that developer started working on Wasabi's proprietary branch, and NetBSD never saw any of it. That sort of thing happening for long enough can easily drain a project of good developers.
Now look at Linux, does that happen there? Hell, no. There are plenty paid kernel developers, and their contributions still get into the main branch.
First off... The GPLv3 license's primary goal is to make it more compatable with other licenses.
Second off... the FSF/GNU folks are usually pretty easy-going when it comes to relicensing software for other people to use, if they have a good reason to. There are a number of projects that have given out GPL'd code under a different license for compatability reasons.
Ever try to get somebody from Apache project to relicense code for you? IT'S NOT GOING TO HAPPEN. They are much more hardcore, beuracratic, and nasty about this then the GNU folks.
It's like your seeing the world inside-out or something.
Your taking a person like RMS whose primary purpose in life, something he has devoted pretty much every minute of his waking life, is for the freedom of software users everywere. And you act like it's HIM that wants to control YOU.
It's so much bullshit that it makes me want to puke, get your head out of your ass.
Not everybody wants to devote their lives to making software that you can turn around and use to extract fees from the clueless masses. The GPL is about liberation, moving away from restrictive software licenses, not about making other people rich.
How can it be a "Final Draft"? Doesn't "Draft" imply that changes could still be made to it?
Coder's Stone: The programming language quick ref for iPad
The reason that Novell can distribute GPLv3 software in spite of their Microsoft deal is simple - the patent restriction in question does not apply to agreements made before 28 March 2007 (see the end of section 11). The reason that the FSF decided to write the clause in that manner is because they felt that Novell could possibly turn this deal around to do good if they chose to do so, and therefore are giving them a pass this time.
OK, I have hated $X for years but I am unable to use reason against $X, so I act like some new thing about $X has pushed me over the edge, even though I was pushed long ago. I will then slip in $Y, which otherwise is passed over in favor of $X.
The new thing about $X should serve as a wakeup call about...fire....brimstone...hell breaking loose...illuminati starting new world government...
This has got me seriously looking at $Y instead of $X. (Like I had not already made up my mind about this years ago.)
We will probably shift to blahblah which uses $Y. (As if blahblah has no other qualities which would explain it.)
I see the new thing about $X as the beginning of the end. (Like I have not been proclaiming $X's demise for years.)
I cannot help but wonder, is there a term for this kind of troll?
If businesses would be scared away by a license, then they'd also be scared of Windows' EULA.
"open source represents the anarchist form of socialist revolution .. go ahead and limit your choices and allow RMS to protect you by limiting those choices"
.. :)
..
The GPL actually acts to prevent others from limiting my choice in what I do with the software. The only proviso being I must also pass on such freedoms to others.
Your comments regarding anarchist reminds me of the writing of Dr. Nikolai Bezroukov. You aren't him by any chance
key words:
cult, social revolution, mutation, Socialist, anarchist, collectivized
Re:Don't like GPLv3? Run MSFT software
davecb5620@gmail.com
The people who don't like it are probably not software developers, or at least not software developers who are currently using the GPL.
Most independent software developers who use the GPL are smart enough to have chosen it for a reason, usually because they agree with the philosophy behind it. Most of those developers, I imagine, will be switching to GPLv3 because the philosophy is the same. It's really just closing loopholes and adding protection from patent lawsuits. It's a great thing for independent Free Software developers.
Emphasis mine.
That's was the basic idea has always been and will always be.
The problem is, corporations are finding creative way to appear to be sharing that work, without actually giving the freedoms to do whatever you wanted to the next in line - the user. In fact, they don't effectively share the work.
The initial GPL was written, because RMS always wanted that the End-user receives in turn the freedom to do whatever he wants. Back when GPLv1 was created, the main reason RMS saw was that company refuse to share the work by give the code, so GPLv1 makes mandatory to give the code too (or make it available), whenever you copy a GPL program.
The problem is that corporation found way to remove the possibility to do whatever you want, while still providing a copy of the code. Thus not effectively sharing the work.
The whole GPLv3 idea originated in finding way to plug those holes so that, no matter what the corporation will try, it will BE FORCED TO SHARE THE DAMN WORK !!!
It's not pissing contest against Microsoft, it's pulgging holes in the current GPL.
The main ideas :
- The SIGNING KEYS restriction (TIVOisation) :
TiVo says : "We do support open source and we follow GPL : you can find everything for download on our website. We do share the work".
Facts : To use that work one needs signing keys to load the code back into the TiVo. But those keys are kept über-secret.
Results : TiVo did share the work *in a way*, but found a way to actually remove the end users freedom to do whatever they want, thanks to signing keys.
GPLv3 : asks that users have a way to obtain keys to actually do whatever they want with given software.
- The PATENT mine field :
Random corporation say : "We do support open source and we follow GPL : you can find everything for download on our website. We do share the work".
Facts : The technology underneath is heavily patented. You can't do anything with the code, even if received it as per GPL, because otherwise you'll be violating enough patent to immediately find a horde of lawyers knocking at your door with Cease-And-Dessit letters.
Results : Source is published but you still can't do anything with the code because patents restrict you freedom.
CPLv3 : asks that no patent should stop the end users' freedom to do whatever they want - Either the code should be patent-free or license should be granted to GPL-compliant usage.
- REMOTE access.
Company says : "We aren't distributing copies of our software, people are running it remotely on our servers. We don't need to share the work"
Fact : Users are running an application (remotely) but have all their freedoms to thinker with it stripped.
This is especially more frequent with Web2.0, where websites are full almost desktop-grade AJAX applications, but are pulled from the server. But this can also be considered for applications that are ran over a remote interactive session like terminals (Telnet, SSH) or whatever similar.
Result : Is you give it to users so they use it, you must give them the right to analyse / modify and/or make copies of it. But those company found a way to give only access without code.
GPLv3 : Counts giving remote access to a program as a form of distribution.
The GPLv3 is only about founding way to still grant the end-user freedom to thinker, whatever the corporation may do in attempt to stop that freedom transmission.
It's not some ideological religious war against freedom-hating-microsoft or against other ideologically impure infidels.
It's just that RMS has a special character which tends to ruin such work by speaking using extremists words.
"Sufficiently advanced satire is indistinguishable from reality." - [Tips: 1DrYakQDKCQ6y52z6QbnkxHXAocMZJE61o ]
>well, it seems the slashbot group think only sees GPL and MS. Lets ignore Macs and the BSDs. Even though i explicitly mention that as my other choice.
A choice that you had already made years ago, an "inconvenient" that fact you conceal in order to dramatize your "GPL3 fiasco" fiction into some kind of revelation. I am considering updating the Wikipedia entry on trolling. Would you mind parting with any more techniques? Of course, whatever identities and examples that I might use, I will just make up, just like you did with your "surprise revelation".
This argument is funny. What it translates to is: "I want to write 'free' software, but I don't want anyone else to make money off my work" -- Or more directly, "I want to be greedy but not appear to be"
:)
I see absolutely nothing wrong with "I want to write free software, but I'm also willing to license that code for reasonable compensation."
That's certainly no more greedy than "I see free code out there that I'd like to use, but I don't want to pay for it."
I guess I don't see why one license has to "win" over the other. Use what you like. Just don't bash other stuff.
We agree completely.
The best way to reply to this might be 'right on paper turns out wrong in practice'.
It is best to think of the Committee and Community input as being advisory only, ultimately Stallman/the FSF makes all the decisions and cannot be overturned.
You would think this would mean a tougher license, but what we got instead is one that focuses on punishing enemies and rewarding friends, not "car[ing] more about end-user freedom than about whether XYZ inc. will like the license or not."
You can see that in some of the (careful) cut outs for companies like Cisco (note that section 6 only covers consumer items, not, say a Cisco enterprise router); IBM/Intel's embedded chip business (an exception is made for Linux burned to ROM where there is no opportunity to change); Google (the ineffectual Affero provision. In Eben's defense, he has spoken out about Google's failure to live up to the spirit of the GPL). Probably most significantly, the patent provisions have a cut out so that only "contributed code" is covered, not everything in a distribution. This is a big win for IBM - never forget that IBM is the single biggest patenter, NOT Microsoft!
I fully support the right of the FSF to do this. It truly is their license. But the cut outs and oddly twisted language tells me that this license is about something other than _just_ Freedom.
The developer community will have to make a choice to stick with v2 and move projects forward in that manner, or switch to v3 with its friends and enemies list.
Reminiscent of "Animal Farm", one has to wonder how the rules will be changed on the barnyard door next time!
A sig?!? I don't think so.....
See http://www.freebsd.org/cgi/cvsweb.cgi/src/gnu/
MidnightBSD: The BSD for Everyone
You make good points... Perhaps "friends and enemies" is part of it. I still think the GPLv3 is moving in the "more free" rather than "less free" direction though. Dismantling the enemies methods of causing trouble will in the end make the Free Software movement more powerful, and although your Animal Farm analogy is accurate perhaps, I still trust the FSF, GNU, the SFLC and RMS more than any other big entity in the software arena.
The moment the FSF does something that hurts the users of Free Software, I'll give 'em hell.
"Final Draft" is the language used outside of software for the rough equivalent of a "Release Candidate" in software, the "Final" is a statement of intent, not fact.
I was also hoping for some punishment for Novell. However if this prevents any future corporate retardation from occurring then I'm ok with it. As much as I hate Novell for being the trader it is I would rather focus on the greater good and I feel that this is what is happening. Being an SA for a large company all I can do is use whatever sway I do have to move away from companies like Novell. In the end I would like to see Microsoft focus on writing better software to compete with OSS. I have watched them for 20 years and I don't think they will change until their grip is broken.
Telecommuting! What about socialization?
I'm not Bezroukov, but thanks for that link. Interesting thoughts.
It's not offtopic, dumbass. It's orthogonal.
It is a Microsoft-World war. In case you haven't noticed over the last 20 years or so MS has attacked anyone that they felt would take even .01% of what they consider to be revenue that belongs to them.
They don't believe in competition of any kind. The GPL is the only challenge to the MS monopoly that has a snowballs
chance in hell to make a dent in it.
Over the years I may have met one or two Unix bigots that were trying to eliminate any MS software running in the company
but I have met dozens of MS cult drones that reject anything that does not have the MS stamp of approval on it.
Most of these drones have zero understanding of architecture and infrastructure and why MS is not always one size fits all.
Freedom is divine. Its what is best for everyone.
and yes I do have ADD. You couldn't tell from my posts?
Telecommuting! What about socialization?
It's better to be the foot on the boot than the face on the pavement. ~~ tkx Kadin2048
>GPL 3 does limit what you do with the software, regardless of your passing on the same freedom to others, by placing limits on the hardware you are allowed to use.
I don't understand how the GPL3 limits the hardware you are allowed to use. OTOH, If you are distributing (or "conveying") the software via hardware, well then, that's a little different, isn't it?
The distributor can inflict Tivoization upon you, passing on to you only part of Freedom 0 that he was granted via the GPL. I believe the latest draft allows this within organizations and businesses so that its members have reduced freedoms. So what are you asking for, that Freedom 0 be even less protected than it already is in the latest draft? This degrading Freedom 0 for the sake of Tivoization goes against the ideals that FSF began with. Why would any free software person support this?
NetBSD's "stagnation" was Charles Hannum trying to fuck the project over and engage in a massive sympathy ploy before he got shitcanned for doing stupid things to the CVS tree.
Jesus is coming -- look busy!
It seems somewhat problematic to put phrases in the license that the license creators admit are there to hurt MS. This is something they really shouldn't be saying publicly, as it could hurt them down the road legally.
Of course, MS has never played fair, so maybe we shouldn't complain too much if the FSF doesn't play fair either.
Some businesses see it, and some don't. The ones that don't see it are monopolies, and try to convince people that this stuff is anti-business when it's actually only anti-monopoly.
Intellectual Property is a monopolistic, selfish, and defective concept. It is "tyranny over the mind of man"
The compatibility matrix does not include the GFDL.
o n_License
http://gplv3.fsf.org/dd3-faq
So is the GPLv3 still incompatible with the GNU Free Documentation License (GFDL)?
http://en.wikipedia.org/wiki/GNU_Free_Documentati
It makes using the text of, say, Wikipedia articles completely off-limits in a GPL'd program.
Why the FSF would promote licenses incompatible with the GPL is beyond me. And totally unnecessary IMHO.
Very shortsighted to promote artificial distinctions between code and data -- the kind of shortsightendess one would not expect from a Lisp hacker like RMS.
A 21st century issue: the irony of technologies of abundance in the hands of those still thinking in terms of scarcity.
"I'm not Bezroukov, but thanks for that link. Interesting thoughts"
:)
You shouldn't be surprised if you get a bit of a reaction when you call Open Source people an anarchist cult now should you
davecb5620@gmail.com
The GPLv3 isn't written by a fulminating, roaring and foaming RMS that screams "Thou shall not put online a single line of PHP that you didn't make available".
The GPLv3 went through several revision before reaching draft 4.
The whole limitation of remote access is optional.
As are all the additional added stuff making it mutually compatible with various license.
Notice also how already almost any web stuff features a small almost unnoticeable plug "powered by x.y.z" be it a GPL PHP app or some proprietary app.
"Sufficiently advanced satire is indistinguishable from reality." - [Tips: 1DrYakQDKCQ6y52z6QbnkxHXAocMZJE61o ]
will be Microsoft Linux.
Novell showed the way with SCO. Use Novell and you don't have to worry about SCO IP infringement lawsuits. When Novell announced that they would effectively protect any company who used Novell and was sued for it by SCO, they became very attractive to companies that wanted to use Linux but were afraid of Lawsuits. The funny thing is that Microsoft may hold patent threats, but it could easily use that to push it's own Linux distribution.
Headline: Microsoft releases Linux version with software you cannot get from any other Linux distro. Why? Imagine the impact on the sales of RedHat if you could get the same thing (CentOS, Oracle) with Microsoft software and support on top of it. Certainly much of the FOSS community would freak out, but businesses wishing to support both MS and Linux systems would jump at the chance. For those businesses wishing to support Linux, it would give them a transition system that would never need to transition, keeping the lock-in that makes Office so popular. Businesses could hire developers who have experience programming for Apache and PHP to work along side people using .NET, VB and IIS. Instead of having to choose a candidate based on experience with the one system they have, they could hire whoever seems most qualified in any.
Instantly MS could say that it is "fostering" cross-platform development and at the same time edge out the players who release OSS. There is nothing that says you cannot run closed source software on Linux, or even distribute the same, as long as you don't mix the source. If anybody could pull it off, Microsoft could and if they do, it will be a major blow to the other Linux vendors which in turn decreases their revenue, and essentially squeezes down the amount of contribution that RedHat and SUSE are able to afford.
When? Well I'd expect the announcement shortly before the end of the current agreements with SUSE expire, so that MS can make a clean break, retain SUSE users and take a big bite out of RedHat revenue. RedHat would be in quite a pickle as any legal action they pursue against MS is already questionable and MS has the patents to make the lawsuit ugly.
If someone at MS were really smart they were talking over beers with SCO people with this in mind all along, make the lawsuits scary and you will make money -wink- -wink- ... and thinking at the same time that if SCO gets hammered out of existence then take the assimilation approach.
I don't know if I'd be able to resist running exchange on a Linux system, the temptation of the dark side is very strong.
B) Eliminate all the stupid users. This is frowned upon by society.
MS can't make you distributor of other people's software just by them sying you are one.
MS promises not to sue you would be completely independent of the rights granted to you by the GPLv3.
MS is very powerful, but event ehm are not that powerful.
IANAL but write like a drunk one.
You are failing miserably to explain how MS will kill GPL.
I just read your rambling and it lack any coherence.
If that is MS's plan then I frankly think we don;t have too much to worry about.
IANAL but write like a drunk one.