Legal Summits to Tackle Linux
An anonymous reader writes "BuilderAU has the story that the Linux Foundation, custodians of the Linux trademark, have announced that they will host two summits to deal with legal issues surrounding Linux and open-source software. Attendance at the first summit will be restricted to members of the Linux Foundation and their legal counsel. The second summit — an open meeting — will be held in Autumn 2008 where legal experts from any background will be able to attend."
...the spirit of the GPL was to keep software free so that the source code can't be made proprietary (such as what happened with Microsoft swallowing pieces of BSD like you stated). Linus very much supports that clause, and has always spoken in favor of the GPLv2. I'm curious why you suggest he is against the spirit of the GPLv2. The only anti-GPL statements I've seen him make are in regards to GPLv3, in that he doesn't think a software license should govern or have anything to do with hardware.
http://blindscribblings.com - Tasty pop-culture in conceptual fashion.
How exactly did MS swallow "the BSD"? Last time I checked, BSD projects and communities were as strong as ever.
How dd they swallow BSD? Simple:
1.First they drank the BSD licensed code, like Kerberos from MIT and the BSD TCP-IP stack.
2. As it descended down their oesophagus, they added proprietary extensions to it, and bundled it with their inferior monopoly Windows OS.
3. The corporate types were then fed with choice quotes and reviews, and Active (Craptive) Directory got deployed.
4. The market leading authentication mechanism is now incompatible with the original BSD Kerberos; thus it has been effectively swallowed.
Clear?
If you keep throwing chairs, one day you'll break windows....
You seem to be trolling a bit but no, there is an alternative; keep the kernel GPLv2 and fork the GNU userland just before they go to GPLv3. That isn't such a herculean task as it at first might seem: much of the GNU stuff is at an end, so to speak; textutils, binutils, the shells and compilers are all pretty much finished works. Even Linus said that there may not be a Linux v3, because it's 'done'. Much of the applications that otherwise play on top of Linux are either windowed (which is a whole story onto itself - the quality of Gnome is debatable to put it friendlily) or services (most of those aren't made by the FSF at all). And there exist good alternatives for the GNU userland, as well - shells, compilers, you name it. The FSF may think they're holding Linux by the ears, but they're not.
Religion is what happens when nature strikes and groupthink goes wrong.
The OP was suggesting that BSD licensing is bad because it allows embrace-and-extend. My point was that this is not something that can be solved by licensing, and that actually with BSD licensed code there are better chances of compatible implementations (as shown by the TCP/IP example) than with the GPL for example. In fact, even RMS agreed that a less restrictive license (compared to the GPL) is suitable for reference implementation of a standard to gain wider adoptation. Thus the OGG Vorbis reference implementation library was licensed BSD.
It's worth noting that a lot of contributors offer their code under different licenses. Some files are MIT or BSD licensed. Some are public domain. Some are GPLv2 or later. Linus uses GPLv2-only, but it is not the only license used. I'd be interested to see how much of the kernel code is under the GPLv2-only license.
I am TheRaven on Soylent News