The Reuters story quotes Eben Moglen, general counsel for the Free Software Foundation, as saying, "The community of people wants to do anything they can to interfere with this deal and all deals like it. They have every reason to be deeply concerned that this is the beginning of a significant patent aggression by Microsoft."
Finkle goes on to say, "Novell angered members of the open-source community that develops Linux and other free software programs in November when it entered a wide-ranging business deal with Microsoft."
An observation: conflating the open source and Free Software communities -- as Finkle has done -- shows about as much familiarity with the subject matter as I have with quantum physics. My guess is that open source folks, a group that leaves Stallman and Moglen largely unimpressed, are pretty much OK with the Microsoft/Novell deal. But not so the FSF, which has been considering as yet unpublished changes to the draft of GPLv3 to effectively block such deals in the future.
As an illustration of how far and how quickly misinformation can spread on the Internet, Geek.com published a story this morning entitled "Novell may lose access to new Linux versions."
According to Brian Osborne, the author of the Geek.com piece, "The Free Software Foundation may ban Novell from selling new versions of the Linux operating system due to concerns over the close partnership with Microsoft."
In the face of such towering ignorance, it may be worthwhile to note:
1. The FSF has absolutely no control over Novell's distribution of Linux. None at all. Zero. It doesn't matter a whit how much Stallman hates the Microsoft/Novell deal. It's legal. It's legit. It's in full compliance with the GPL.
2. GPLv3 is still on the drawing board. Jumping to conclusions about the consequences of its impact on Novell is insanely irresponsible. Any changes to the current draft version of GPLv3 will go through the same public debate and discussion as have the previous drafts.
3. The odds of the Linux kernel ever moving to GPLv3 -- so long as its current anti-DRM and other restrictive clauses remain in place -- is about the same as mine being crowned Miss America. And I don't even know Donald Trump.
This story -- the meme about Novell not being allowed to sell Linux -- is too stupid to even be considered FUD. Both Novell and Eben Moglen have declined our invitation to comment on it.
Note: Comments are owned by the poster. We are not responsible for their content.
This is more of the same thing. What's worse, is that it was blindly sort of propagated by the FOSS community. I don't particularly like Novell making deals with MS, I think Novell will regret it but it's their company and they do make a very good Linux.
Novell has to look out for itself and if your customer is wanting interoperability, you give it to them. So you are a little miffed about red carpet. So it's not "open source" anymore (or is it that you can get the source, but not the resources they offerd.) Understand that the new package system, ZMD, is based on the old red carpet technology. So gripe away. You can hate them all you want, but they have brought alot more than you are willing to admit to the table.
You purist and zealots are really entertaining with the way you have to froth over this. Where is the talk over Red Hat and JBoss? Where is the venom over Oracle "Forking" Red Hat?
You should be thankful that Novell is in the game. There answers to SCO over Linux along with IBM will put that whole matter to rest. Think of the patent concerns that alone is putting to rest.
A patent agreement that is essentially a non-aggression pact is not a bad thing. Sure it could back fire. But be realistic. How can Novell indemnify EVERY linux user. Their previous indemnification program was limited to THEIR products, not all of the Linux world. How can they indemnify on behalf of Red Hat, Mandriva, Ubuntu or the other million distributions out there? THEY CAN'T
Sure there are a lot of implications that can impede Linux, but Linux will survive, and in actuallity, if you understood the business world you would know that. This entire matter is the software equvalent to what happened with IBM when their enginieers left and started the Clone market. Look at where that has brought us today. So put a cork in it an understand that the world/linux is bigger than Novell and MS. You alarmist attitude will only give you an ulcer and cause me to fall out of my chair from rolling my eyes too much...
However, remember also that there are a lot of BSD-licensed equivalents to the GNU tools. Novell could switch to those.
This brings an interesting scenario: a Linux distribution with a BSD userland. AFAIK nothing of this kind exists (sounds strange to me, given that there is the opposite: GNU/kFreeBSD), but maybe the reason is condensed in this post: <a href="http://lists.freebsd.org/pipermail/freebsd-questions/2004-December/067723.html" title="freebsd.org">http://lists.freebsd.org/pipermail/freebsd-questi<nobr>o<wbr></nobr> ns/2004-December/067723.html</a freebsd.org>.
At this point, Novell should be happier restarting from DesktopBSD, PCBSD or something similar. The main problem would be driver support. If Novell is bold enough, it could add driver support to FreeBSD and this would strenghten BSD. Interesting.
If the desktops go GPLv3, this would be serious trouble for them. Although they could comply by kludges like installing them from the network instead of physically redistributing them (sort of what Ubuntu does with restricted formats).
Have a taste of freedom. It is sometimes a bitter pill. To me though, this is the sweetness of the GPL
Hey, I fully agree. I generally like the GPL.<nobr> <wbr></nobr>:)
If the FSF decides that they are moving gcc under a new more restrictive license, they cannot put the genie back in the bottle. All versions up until today are available under GPL2 to any and everyone and nothing can stop them from further distributing and developing that version. GPL3 cannot cage software that is already free!
IANAL, but are we sure the argument would apply when the copyright owner is a single owner (like in this case, because ALL contributors to these projects assign copyright to the FSF)?
That means that, for example, all versions of GCC are in fact owned by the FSF. If the FSF comes in and says "We have been possessed by the Devil himself and we send all rights for every GCC version to Microsoft", I am not sure of the consequences. The GCC is *their*: they agree to distribute it under the GPL, but maybe they can revoke it anytime now. The problem wouldn't exist in the case of a multi-copyrighted project
That's the reason they can unilaterally decide to change all the licenses of their projects to GPL3. For Linux this has been deemed impossible, because they would have to ask to every contributor -which is often impossible.
Note that I personally like the GPL, but I don't know if it protects from such a risk.
Probably it's me being dense but...
You can't, by the way, "send all rights for every version of the GCC to Microsoft" - rights are not retroactive. GPLv2 will continue to be in force for every utility released by the FSF under that version. They can't even re-release existing tools under GPLv3 and thus revoke the ones under GPLv2 because the versions - even if identical - under GPLv2 would STILL be under GPLv2 as marked in their source code.
This quite surprises me. It seems to me your statement is analogous to: "I cannot change the license of something I released and of which I own all copyrights". Is this really true? The fact that rights are not retroactive, as I understood it, means I can't do anything previous uses of GCC under the GPL -at that time this was the license, and they were perfectly right to comply with that license. So if I am the FSF and I change the licence of all GCC versions tomorrow, I can't sue anyone for having distributed it under the GPL today. But I can't understand why I can't have the freedom to change my mind on the license of something I 100% own and then enforce the new license from now onward.
Anyway yes, forking would be a great damage anyway to Novell. Even if Novell lawyers can cover their rear-end, I think development costs etc. would rise a lot (who would like to contribute OSS work to a Novell-specific fork? Except of course the Novell fork becomes somehow more interesting than the official fork...hmm, interesting times ahead.)
If you have complied with the license, Microsoft cannot suddenly change its mind and sue you for redistributing its software.
Do you see how that would be unfair?
Actually Microsoft can and does do things like that, but they are able to because there is a clause in the license that says "we reserve the right to change the terms of this license at any time." Since that type of phrasing is absent in the GPL, it's not an issue for Novell.
I'm sure it would be unfair, I just wondered if it was possible. I also did a little research on the Internet and it seems you are right. Hmm, I have to think better when I assign licences to my projects<nobr> <wbr></nobr>:)
...but your comment about the Linux kernel not moving to GPLv3 is irrelevant. The Linux kernel is the least visible part of Gnu/Linux to most users. If Novell happened to find themselves in a position where they could only distribute the kernel, they wouldn't have a Linux business.
By the way, the people who are most vocal in rejecting the name "Gnu/Linux" in favor of "Linux" are mostly the same people who wouldn't be able to tell the difference if you ripped out Linux (the kernel) and replaced it with a BSD variant, or even with Sun Solaris.
I agree, but...
Posted by: Anonymous Coward on February 06, 2007 09:57 AMHowever, it may be that a confrontation between these two organizations will take place down the road, let's say after GPLv3 is rolled out and the GNU projects (gcc, gmake, binutils, bash, and standard Unix command line utilities) adopt the new license going forward. It could be that Novell will have to fork these projects to in order to distribute new versions of their Linux distro (we should expect that the kernel will not upgrade its license due to heavy opposition by Torvalds and other kernel developers).
The FSF and Novell represent opposing poles of the umbrella of interests involved in free software. The FSF has its philosophy; Novell represents the ultra-pragmatic corporate interests that can and will change course on a dime to meet quarterly earnings estimates. Without the FSF, there is no "free software", only open source and various kinds of encumbered "shared source" licenses; but without Novell and other large corporations willing to supply R&D funding and marketing muscle, free software is in danger of being relegated to the academic and hobbyist communities.
A large-scale fork would be a major problem not only for Novell, but the entire community. A fork of these tools over licensing helps nobody except for Microsoft. Maintenance and security patch hassles would double overnight. It would give companies substantial reason to pause before using or adopting free software, if they do any software development themselves, because of fear of legal entanglement with the FSF.
Therefore this article is slightly worthwhile in that it offers people the chance to anticipate the consequences of the GPLv3 blowing the Novell-Microsoft agreement out of the water. Joe points out that GPLv3 hasn't even been finalized yet. Correct, but the FSF has given every indication they want to prevent two party patent covenants such as Novell-Microsoft, and are not willing to overlook this agreement under a grandfather clause. Further, they want the new license to enforce their philosophy on DRM.
#