Open Definition 2.0
Open Definition 2.0
Posted Oct 8, 2014 18:56 UTC (Wed) by donbarry (guest, #10485)In reply to: Open Definition 2.0 by josh
Parent article: Open Definition 2.0
It is somewhat disconcerting, however, that they do not mention the FSF and GNU project at all -- after all, they are the philosophical parent of these movements.
It raises the question: why do we need yet another such "certifying" body?
The wealth and connections of this group is disconcerting. Their 35 employees dwarf the FSF. They are clearly an appendage of Canonical, and the board members are, largely, the generic bunch of Financial Titan Aspirants who are Hedging their Bets. They do not enjoy my trust as proven guardians of a free code/culture/data movement -- which raises the question: who asked them to? And the answer is -- Canonical -- not any democratic mass movement.
They have much to prove, and much distrust to overcome in the process.
Posted Oct 8, 2014 19:19 UTC (Wed)
by josh (subscriber, #17465)
[Link] (1 responses)
I would certainly be happier if this was proposed or backed by some existing body, sure. As for why a new definition, there's a shockingly large number of people who seem to believe that data, writings, art, and many other forms of work are somehow different from software and don't actually need to be Free or Open. While I agree that there's an odd collection of folks backing this, the results taken in isolation do seem to have turned out well.
Do you see anything obviously broken about the definition itself, as opposed to the backing body behind it?
Posted Oct 11, 2014 14:18 UTC (Sat)
by coriordan (guest, #7544)
[Link]
The DFSG was a formal description of what FSF had been promoting for the previous 14 years. Perens even ran it by RMS (who approved) before publishing it.
Posted Oct 8, 2014 19:19 UTC (Wed)
by josh (subscriber, #17465)
[Link]
Posted Oct 8, 2014 20:17 UTC (Wed)
by landley (guest, #6789)
[Link] (20 responses)
No, they're really not. They're just very good at self-promotion and fuzzing (our outright lying about) history. Just one random example, Project Gutenberg predates the FSF by many years, as covered multiple times here on lwn: http://lwn.net/Articles/177602/
I know Stallman tries to claim credit for Wikipedia, Linux, earth having an Oxygen atmosphere, and the canadian sport of Curling, but it's just not true. Wikipedia explicitly voted _against_ using their licenses back in 2009 https://lwn.net/Articles/328412/ and Linux spun off of minix, its first three releases were under a home-spun license Linus came up with (no commercial use), and it coexisted with the early 386 BSD releases.
And yes, Stallman has tried to claim credit for FreeBSD. To my face, when I drove up to Boston to interview him for my computer history research in 2001. And yet here's Kirk McKusick's essay about the first 20 years of BSD history, spot any mention of Stallman or the FSF or GNU?
http://oreilly.com/openbook/opensources/book/kirkmck.html
It takes about 3 years to clone unix. Andrew Tanenbaum did it with Minix, the Mark Williams company did it with Coherent, and Linux took that long to get out a 1.0 release. (And no, compilers aren't special: Minix and Coherent had their own compilers, and Fabrice Bellard went from tinycc's prototype winning the 2002 Obfuscated C code contest (really!) to booting the linux kernel FROM SOURCE CODE http://www.bellard.org/tcc/tccboot.html in October 2004. "But text editor!" Busybox has a vi implementation, Linus Torvalds maintains his own fork of microemacs (which is to emacs what busybox vi is to vim) at https://git.kernel.org/cgit/editors/uemacs/uemacs.git it's really not special.)
The GNU project started in 1983. Linus's 1991 Linux announcement made fun of it because even then it was already the Duke Nukem Forever of OS releases: even if it did eventually ship it simply wouldn't _matter_ anymore.
The thing to realize is that until the Apple vs Franklin decision in 1983 extended copyright to cover binary software, there essentially _was_ no closed source software. Binaries were "just a number", not subject to copyright. By that point, Unix was around 15 years old. Stallman's 1983 GNU announcement is a mirror image of IBM's "object code only" announcement (http://landley.net/history/mirror/ibm/oco.html), _everybody_ reacted to it. AT&T let itself be broken up in part to enter the computer business with unix, and tanenbaum started writing Minix in response to that, and Linux wrote Linux in response to Minix. (As he documented in his own biography "just for fun".)
I gave an entire talk about this at Ohio LinuxFest in 2013:
https://archive.org/download/OhioLinuxfest2013/24-Rob_Lan...
And that talk doesn't even touch on things like the CP/M user groups circa 1981 http://landley.net/history/mirror/cpm/cpmug.html or Bill Gates' widely mocked "letter to hobbyists" in 1976:
http://en.wikipedia.org/wiki/Open_Letter_to_Hobbyists
And yes, Gates was complaining about copyright infringement 7 years before copyright actually covered the software he was talking about, here's an audio interview he gave in 1980 talking about how he was lobbying congress to change the law to match his wishes and how congress wasn't listening to him and it was so unfair, stupid congress:
audio: http://landley.net/history/mirror/ms/gates.mp3
I.E. Gates whined and issued manifestos and lobbied congress ineffectively for years, Steve Jobs went through the courts and got the law changed as soon as it started bothering him:
http://en.wikipedia.org/wiki/Apple_Computer,_Inc._v._Fran....
Stallman's big "GNU/Linux" push happened when Linux famously grew 212% in 1998 because the flood of Java developers switched over to Linux (netscape had united the "anything but microsoft" crowd had behind java, then opened its source while simultaneously elevating Linux to a tier 1 platform). The existing Linux community didn't have the bandwidth to enculturate all the new arrivals and wasn't particularly _interested_ anyway, (Linus' stance was always "shut up and show me the code"). The FSF siezed the opportunity and fed the flood of newbies a stream of inaccurate self-aggrandizing propoganda claiming credit for everything that ever happened ever.
But it wasn't true. History didn't "forget" Stallman: he simply wasn't very important. At MIT he was overshadowed by a dude named "Richard Greenblat", if you can believe it. His own authorized biography said he fantasized about commiting suicide by blowing up the building where that dude worked: http://landley.net/history/mirror/faif/ch07.html. Steven Levy's book "hackers" said he duct taped casette recorders under the table at restaurants to spy on their Lisp development so he could copy it, because Stallman's technical vision totally thought Lisp was the future. (Probably in the epilogue, only part that really mentions him I think? My copy is buried in a box...)
Stallman's main skill is self-promotion. Always has been. He had nothing to do with Linux (and was against it for most of its first decade), nothing to do with Netscape releasing its source code (that was the usenix paper the cathedral and the bazaar in which "the cathedral" was the FSF and "the bazaar" was Linux development), nothing to do with Red Hat's IPO, nothing to do with IBM's $1 billion/year investment starting in 2000 (and their defense against SCO starting in 2003), nothing to do with x.org forking off from xfree86, nothing to do with Android...
So yes, not mentioning him here is correct.
Rob
(Sorry for the rant. Stallman annoys computer historians the way Dan Brown annoys religious historians. Very popular, nested layers of wrong.)
Posted Oct 8, 2014 21:13 UTC (Wed)
by Zack (guest, #37335)
[Link] (10 responses)
Posted Oct 8, 2014 21:47 UTC (Wed)
by bronson (subscriber, #4806)
[Link] (6 responses)
Posted Oct 8, 2014 22:16 UTC (Wed)
by Zack (guest, #37335)
[Link] (5 responses)
In ours we would have to start by actually citing evidence for any allegations made, and take it from there.
In theirs you apparently can simply state personal opinion, then post a wall of citations that are neither here nor there, all to construe a case that has the flimsiest of bearings on the actual inquiry, for no other reason than to hold a personal diatribe against a particular person.
It could be their Universe has found a way to substitute oil with strawmen. Hence, "fascinating."
Posted Oct 8, 2014 22:35 UTC (Wed)
by josh (subscriber, #17465)
[Link] (4 responses)
It's the equivalent of getting a patch into the Linux kernel because it compiles and follows the proper submission conventions, without asking "wait, *should* we actually do this?".
Posted Oct 8, 2014 23:07 UTC (Wed)
by dlang (guest, #313)
[Link] (3 responses)
Posted Oct 9, 2014 10:53 UTC (Thu)
by Zack (guest, #37335)
[Link] (2 responses)
No. It's to question the assertions made. What is "it" here?
"It" seems to be the claim here that, to paraphrase, "the FSF claims to have invented sharing source code for mutual benefit."
"I know Stallman tries to claim credit for Wikipedia"
"I know Stallman tries to claim credit for Linux"
"Stallman has tried to claim credit for FreeBSD."
, etc.
In other words, a large amount of citations that serve to refute claims that, as far as a reasonable reader can conclude, _have never been actually made_.
Furthermore, even *if* the argumentation was taken at face value, what the whole argument comes down to is akin to: "It has been shown Vikings landed on the North American continent way before Columbus. Therefore it can be concluded that Columbus' discovery had no bearing whatsoever on the development of the continent."
I have no opinion of whether the FSF should be credited in the "Open Definition 2.0", but the claim here seems to be that they had no bearing on on the landscape computing whatsoever because everything they did had been done before.
There is in no logical argument constructed here, and the whole piece is rife with conjecture and personal attacks, only to arrive at a questionable conclusion that is widely outside of the scope of the initial argument. It's absurdity dressed up like logic, and no amount of contradicting source citations will change that.
Posted Oct 9, 2014 15:29 UTC (Thu)
by raven667 (subscriber, #5198)
[Link] (1 responses)
Or maybe it's more accurate to say that a historian who's spent a lot of time with primary sources has seen claims made that those of us playing the home game are entirely unfamiliar with.
Posted Oct 9, 2014 22:53 UTC (Thu)
by sjj (guest, #2020)
[Link]
Posted Oct 8, 2014 21:50 UTC (Wed)
by vonbrand (subscriber, #4458)
[Link] (2 responses)
Just one nit: Linux development started under Minix, but is in no way an inheritor of it. More a reaction to it's closed development model (no distribution of patched sources allowed, official source had to stay minimal and strictly 8088-compatible; lots of incompatible unofficial patches, including for 80386, floating around).
Posted Oct 8, 2014 22:34 UTC (Wed)
by landley (guest, #6789)
[Link] (1 responses)
Linus's introduction to Unix was Andrew Tanenbaum's book, and the early announcements/discussions of it were posted to comp.os.minix (leading to the Tanenbaum/Torvalds debate where Tanenbaum basically said "off my lawn" and Linus got his own mailing list, amidst some very nice technical discussion of monolithic vs microkernel architecture and only moderate name calling):
http://oreilly.com/catalog/opensources/book/appa.html
He didn't use Minix code in Linux, but he read the entire minix source, read a book about it, had a course on it at his university, installed it, ran it, and extensively modified it before starting Linux, which he developed under it. (And he only booted Linux from a floppy until he accidentally left autodial running on /dev/hda instead of /dev/tta (or whatever device it was back then) and it overwrote a good chunk of his minix partition's filesystem metadata with hayes modem commands and copies of the modem pool's phone number before he noticed. Considering it took him over a month to install minix and the stack of external patches to make it a vaguely usable 32 bit os the _first_ time, and his linux partition had survived... Dogfooding was the easy path at that point.)
Note: this doesn't make Linux a derivative work of minix. AT&T sent Dennis Ritchie to the Mark Williams company to read the Coherent source to see if any AT&T copyrights had been violated. The verdict was they've clearly read official unix source, but then they wrote a new one from scratch:
http://randalljhoward.com/2012/01/01/dennis-ritchie-memor...
A few years later the BSD guys won their lawsuit against AT&T, that having seen someone else's code didn't automatically make your own implementation a copyright violation...
In addition, Tanenbaum chewed Linus out for using a completely different design the academic didn't approve of (because it onoly works well in practice, notin theory). That was the meat of the aforementioned tanenbaum-torvalds debate (linked above).
But the big reason linux jumped from "toy" to 0.95 release so quickly is the existing Minix community had a giant stack of patches (porting minix 8086 code to 386 protected mode, adding virtual terminals, making the filesystem performance not utterly suck, etc) that Tanenbaum wouldn't incorporate because he wanted a simple teaching tool, not a usable system. (The reason Linus used gcc instead of the minix compiler is gcc could produce 32 bit output while the minix compiler was only 16 bit.)
When Linus posted his OS, a couple of those developers ported their patches over to apply to his thing, and when Linus took them a FLOOD of patches went his way and almost the entire existing Minix community switched over to Linux. He _accepted_patches_. The years of existing patch pressure grounded out through his project and pushed it well ahead of where he would have gotten it on his own.
So what Linux did take from Minix was its entire hobbyist developer base. Swallowed it whole. Because Tanenbaum didn't take patches, and the patch pressure grounded itself out through either a fork or a rewrite. (Fork examples: xfree86->x.org, gcc->egcs. More current rewrite example: gcc->llvm, because enough people responded to GPLv3 with "hell no" to sustain quite an active project.)
I talked about this a bit in my presentation at ohio linuxfest. If you like primary sources (other than "Just For Fun"), I haven't gone through comp.os.minix but I have scrubbed the first year and change of the new list for interesting posts, collected here:
http://landley.net/history/mirror/linux/1991.html
And here are two posts Linus himself made about the early history, back in 1992:
http://www.kclug.org/old_archives/linux-activists/1992/ju...
That said, part of what attracted Linus to minix _was_ that it was already part of a larger unix tradition. (That's why Stallman glommed onto it too, after ITS died and he was _forced_ to retrench.) In "just for fun" Linus described reading the Sun Microsystems manuals in his university library to get lists of system calls he added to his terminal program when trying to get it to run bash (so he didn't have to reboot into minix to call mkdir /mv/rm when uploading and downloading files from the university microvax connected to usenet. He wrote his term program that booted from a floppy and ran on the bare metal because minix's microkernel architecture couldn't keep up with a 2400 bps modem's serial interrupts without dropping characters. If minix _had_ merged enough of the "suck less" patches, he'd still be using it.)
The Sun manuals are probably why Linux started with more system v influence than BSD. Of course what Sun influence there was probably came to a screeching halt with:
http://cryptnet.net/mirrors/texts/kissedagirl.html
So yeah, reality is complicated. :)
Rob
Posted Oct 8, 2014 22:50 UTC (Wed)
by josh (subscriber, #17465)
[Link]
The push for LLVM has much less to do with GPLv3 (at least, directly), and much more to do with two factors: Apple pushing hard to get away from *any* GPL code (v2 *or* v3), and GCC not being usable for plugins/libraries/embeddable things. Now, you can most certainly blame the latter on the FSF, for being so concerned about proprietary GCC extensions that they pushed back hard against providing any kind of stable internals for GCC. But that has little to do with GPLv3.
I think it's rather unfortunate that the latter momentum combined with Apple's fear of copyleft drove people to an all-permissive project, and I think we're going to regret that in the future. There's a very real tendency for people doing a rewrite of a project for unrelated reasons to also switch to an all-permissive license to use it in proprietary projects, because it gets them a quick boost in momentum.
Posted Oct 8, 2014 22:23 UTC (Wed)
by josh (subscriber, #17465)
[Link] (2 responses)
Apart from that, even if they did nothing else, huge credit to GNU and the FSF for the GPL and LGPL, and the concept of copyleft, which they rather clearly originated. Without that, it seems highly likely that Linux would be a predominantly all-permissive and far more proprietary ecosystem.
I'm not going to argue that this new proposed Open Foo Definition necessarily needs to mention them, but at the same time, it's ridiculous to claim that the world would look almost entirely the same in the absence of the GNU project.
As for the FSF's emphasis on philosophy, I find it impressive how often the FSF has successfully predicted future problems with technology and policy. (Whether they've been the best positioned to deal with them in all cases is another matter.)
Posted Oct 8, 2014 23:48 UTC (Wed)
by landley (guest, #6789)
[Link] (1 responses)
A) don't you think it's long enough already?
B) I covered some of that in the Ohio Linuxfest talk.
I can talk about how Sun's marketing guy Ed Zander's decision to unbundle sun's compiler and sell it as an optional ad-on that cost extra was responsible for gcc reaching a critical mass of developers. How the real killer app the FSF had was its FTP site back before the NSF AUP changed to allow for-profit use of the internet (giving us "the september that never ended" in 1993 and geocities in 1995), which is why Larry Wall signed the copyright on his "patch" program over to the FSF back in the 80's, but happily supported perl on windows in the 90's. He never cared about idealism, he didn't have any other easy way to get distribution. (sunsite/ibiblio eroded it a bit, but it was really the home isp, geocities, and sourceforge that made the FSF's copyright assignment requirement too much of a hurdle for most developers to ever bother with).
But the thing is: you're not citing _any_ of the points you're making. You're not even referring to specific historic events. You're repeating assertions that some guy told you, and what that guy is telling you is that he's a really important guy who was inexplicably cut out of history and that he must regain his rightful place by telling everybody in the world about his greatness.
While this does tend to happen to people like Rosalind Franklin? It doesn't happen _that_ much to white male college graduates from boston. His big contributions are what, emacs? Even granting the importance of his version of eclipse (posix standardizes vi, but not emacs), even there he was not the first, was part of a very large team, and was working on one of a zillion forks: http://www.jwz.org/doc/emacs-timeline.html
The start of this thread was "why didn't you mention X"? The answer is "because most things that happen do not involve this specific guy, even though he tries to take credit for magnetism and sunlight because of his raging ego and ".
Honestly, I've hung out with Peter Salus in three different states (and at his apartment when he lived here in Austin), he was executive director of usenix and vice president of the FSF, you probably don't know him as the author of "A quarter century of unix": he said richard was nuts. I spent a summer staying with Eric Raymond (they had a falling out but he and Richard were friends in the 80's hanging out at science fiction conventions, and Eric maintained the EMACS Lisp library once upon a time: _he_ said richard was nuts. (Maybe there's a "takes one to know one" there, but at least it's a different kind of nuts.) My friend Stu Green (founded the Austin Linux User Group) was the only guy to work for _both_ of the Lisp startups that spun out of MIT (the ones RMS was so pissed about), he says he was on _suicide_watch_ with the guy after a bad breakup with a girlfriend, long ago. In 2001 I drove to Boston to interview Stallman himself in _his_ office. (He borrowed my car to run an errand, and left it unlocked.) He told me the BSD guys fighting back against AT&T legally was his idea. (Because obviously, they wouldn't have thought of that.)
I've made some minimal attempt to figure out what did actually go on. I talked to more than one person, often traveling to other states to interview them. I tracked down primary sources where possible.
The basic story is that the gnu project failed. It was 8 years old when linux happened, and had not produced a usable system. Coherent took three, minix took three, BSD rewrote and replaced all of AT&T's old code in less than three, and even more have come and gone that nobody pays attention to.
I grew up in an open source community that had never heard of unix. We didn't even have the patch program.
http://landley.net/history/wwiv/
> As for the FSF's emphasis on philosophy, I find it impressive how often
Stallman didn't invent open source. It was ubiquitous before the apple vs franklin decision. The FSF was not visionary, it was a conservative reactionary movement to changes in the industry, and its goal was to recapture the glorious past of the 1970's. (Keep in mind the year before announcing GNU he was cloning the output of the two Lisp companies in boston because he was sure that was going to be big.)
Unix was so obviously big that Paul Allen (the techie co-founder of microsoft, Gates was the lawyer/marketer, it's like Steve Jobs and Steve Wozniak) licensed Unix when he found out that IBM was doing a PC, and hired a two man garage operation called the Santa Cruz Operation to port it to the 8086 and 68000 (because he didn't know which IBM would use) and called it "Xenix" to indicate they would port it anywhere IBM needed.
Then when IBM did come to them (to license basic) and the hardware specs said "16-64k ram" he saw they were doing a CP/M clone (marvelous page about that mirrored here: http://landley.net/history/mirror/cpm/history.html ), and so they bought the 16 bit CP/M clone Tim Paterson had done (they knew him because he'd previously made Microsoft's first hardware product for them, an Apple II expansion board that let you stick an 8080 processor into an Apple so it could run Microsoft basic instead of woz's version).
But Allen didn't give up on Unix, he shoehorned unix features into their CP/M clone (which is why Dos 2.0 went from file control blocks to filehandles, and grew subdirectory support) with the goal of gradually converging with unix until he could just ship Xenix as DOS 4 or 5. (The DOS 2 manual has an appendix about this.)
And then Paul came down with Hodgkins Lymphoma in 1983, initially wrote it off as overwork getting DOS 3.0 out (a driver upgrade for the IBM AT, now with hard drives), heard Gates and Ballmer in the next room scheming about how to get his stock back if he died, left for medical treatment and never returned to the company. His technical agenda left with him.
Microsoft continued to use xenix to run its internal email system until 1990, but when Gates found out that Unix System III had sucked in Xenix code with attribution stripped (the same practice that came back to bite them in the BSD lawsuit, they did it to everybody), he _flipped_out_. Rather than fight much bigger AT&T, he unloaded xenix on the porting house SCO and washed his hands of it. But that's how close we came to having Unix from microsoft in the 80's: one cancer cell away.
So thinking the gnu project was visionary? Cloning a 15 year old widely deployed operating system that had already _been_ cloned (coherent shipped its first version in 1980)? No, it really wasn't. That was the same year Sun Microsystems was founded. Go read "where wizards stay up late" (it's a history of the arpanet/internet), Bolt Beraneck and Newmann replaced all the original honeywell IMPs with VAXes running BSD Unix in 1980. It was in every university with an internet connection, running the show.
Oh here, I mirrored the start of a good book about it (and Bill Joy's role in it, back before he went crazy):
http://landley.net/history/mirror/books/andrewlenard/part...
(That's the sort of thing I find fascinating. I am weird.)
Stallman talks about reacting to Xerox closing its driver software in response to Apple vs Franklin. AT&T similarly closing its code led Andrew Tanenbaum (who was using unix as a teaching tool) to write a new clone version from scratch so he could _continue_ teaching OS design based around Linux. (No, he wasn't the only professor doing that, google for the Lyons book. But Tanenbaum responded by writing code. Unlike Stallman, he actually finished and shipped something, because he had a class to teach. Linus learned "ship early, ship often" from the comp.os.minix community.)
Linux is a clone of Minix, with input from printed Sun workstation manuals in the university library (because posix cost too much). It is not a product of the FSF, they were working on GNU, with the hurd (after alix), which failed. The FSF trying to take credit for Linux (as they try to take credit for BSD standing up to AT&T) is factually untrue.
And yes, I asked Kirk McKusick about that one when I saw him at Ohio LinuxFest in 2013. I also asked Doug McIlroy some questions when I had dinner with him at a previous LinuxFest (2010?) but as far as I remember he hadn't ever met Stallman.
We live in a time when primary sources for this stuff are still alive (some of them, anyway). before he died, I got to email Dennis Ritchie to ask what "inode" stood for. Turns out, even he didn't know, but he could at least definitively guess:
https://lkml.org/lkml/2002/7/20/86
(And I spoke to him on the phone briefly once, he answered the "office" phone number on his web page so I invited him to Penguicon as a GoH. He declined politely, wasn't traveling much. I've received email from Ken Thompson but it was about the 8 chapters he reviewed of The Art of Unix Programming, I didn't get to ask any of my own questions...)
But if you really want to ask Linus Torvalds a question, and are willing to drive to his hometown at a time of his choosing and buy him an expensive beer, you can probably get an answer. (Or arrange to meet up with him at a conference he's attending, through the conference organizers.) Same for any computer science luminary you care to name, they're generally not movie star level famous...
> Apart from that, even if they did nothing else, huge credit to GNU and
I covered that in the talk too. Copyleft only works as a category killer. There's no such thing as "The GPL" anymore. Samba and the Linux kernel can't share code even though they implement two ends of the same protocol and are both GPL. By introducing GPLv3, the FSF fragmented the GPL the way AT&T fragmented proprietary unix back in the 80's.
(No, "just ship GPLv2 or later" doesn't help, then you can't accept code from either one. The GPL was a terminal node in a directed graph of license convertibility providing a universal receiver. Developers only faced a single binary decision, "is this GPL or not", with no care for how licenses _interacted_ beyond that one question.
In the absence of a universal receiver, people like unlicense.org are switching up to universal donor. That's the public domain, but since the public domain has been so hugely FUDded for years (here's a lawyer comparing placing code into the public domain with abandoning trash by the side of the highway, and for some reason Linux Journal saw fit to publish him in 2002: http://www.linuxjournal.com/article/6225 ) people are afriad of it so the either have long elaborate legalese that equals public domain (creative commons zero for example) or they go with one of the BSDs. But the various number of clause BSDs and MIT and LSC and Apache and so on are equivalent to public domain EXCEPT they require you to copy specific license boilerplate into derived works, so if you combine a bunch of them together in one product... guess why the kindle paperwhite's about->license page is over 300 pages long. Ok, kindle pages, but still. You think that's verbosity is ever going to be _useful_?)
Sigh. I care deeply about this topic, but lwn.net comments is not an ideal venue to discuss it.
Rob
Posted Oct 9, 2014 9:52 UTC (Thu)
by mpr22 (subscriber, #60784)
[Link]
Posted Oct 8, 2014 22:27 UTC (Wed)
by DOT (subscriber, #58786)
[Link]
In your talk, you said that 5 years ago you were happy to use "The GPL". 5 years ago, you could have expected the entire FOSS world to gravitate to one license. A universal receiver, as you called it.
I see your point about recent developments hurting that grand vision. It's a huge disappointment that the GPLv3 was too controversial to gain universal acceptance, causing all kinds of troubling incompatibilities. But that doesn't mean that Stallman and the FSF deserve no mention of being a part of the push towards a FOSS world. If anything, their failures should be studied and remembered.
Posted Oct 9, 2014 1:08 UTC (Thu)
by BrucePerens (guest, #2510)
[Link] (4 responses)
Posted Oct 11, 2014 12:40 UTC (Sat)
by Wol (subscriber, #4433)
[Link] (3 responses)
Sorry, I don't mean to impugn your lawyer friends, but I'm very interested in medicine. I've done secondary research (ie read primary papers and drawn my own conclusions) both into modern medicine, and historic medicine. And it's left me EXTREMELY cynical about the public view of medicine, including a lot of what is apparently peddled by doctors themselves.
Just because someone's a lawyer doesn't mean they know jack about law ... :-) and especially doesn't mean they know anything about particular "historical" events. If they've got first-hand knowledge I will bow to their knowledge. But I get the impression Rob makes a point of trying to get to primary sources, to hear or read first-hand accounts. You've made no attempt to claim your lawyer friends are in the same league ... Sorry.
Cheers,
Posted Oct 15, 2014 17:09 UTC (Wed)
by nix (subscriber, #2304)
[Link] (2 responses)
Posted Oct 16, 2014 17:42 UTC (Thu)
by dlang (guest, #313)
[Link] (1 responses)
As for the links he provides, if he didn't provide links, people would respond with "citation needed"
Posted Oct 16, 2014 18:11 UTC (Thu)
by rahulsundaram (subscriber, #21946)
[Link]
Open Definition 2.0
DFSG derived from FSF's concept
> This definition isn't derived from the FSF/GNU
Open Definition 2.0
Open Definition 2.0
> the FSF and GNU project at all -- after all, they are the
> philosophical parent of these movements.
transcript: http://features.slashdot.org/story/00/01/20/1316236/b-gat...
context: http://maltedmedia.com/books/papers/sf-gates.html
Open Definition 2.0
Open Definition 2.0
Open Definition 2.0
Open Definition 2.0
Open Definition 2.0
Open Definition 2.0
Which the Gutenberg, Apple vs Franklin, and Bill gates quotations seem to pertain to. But how about a quotation where the FSF actually *makes* that claim? As such, [citation needed]
[citation needed]
[citation needed], with the sidenote that any "computer historian" would know *damn* well, that any time RMS would refer to Linux, he would mean the "Linux kernel", which means facts are being deliberately skewed here.
[citation needed]
Open Definition 2.0
Open Definition 2.0
Open Definition 2.0
Open Definition 2.0
http://www.zdnet.com/blog/murphy/comparing-code-bases/379
http://landley.net/history/mirror/linux/1992.html
http://www.kclug.org/old_archives/linux-activists/1992/ma...
Open Definition 2.0
Open Definition 2.0
Open Definition 2.0
> You're ignoring, for instance, quite a lot of the pre-Linux history of
> GNU, as a project that supplied Free Software replacements for
> UNIX/POSIX utilities, widely used on proprietary UNIX systems.
So the decline in influence of the FSF in the 90's was a natural result of the spread of the internet (remember, their primary fundraising was printed manuals and the sale of software on magnetic tape well into the 90's). They declined due to changes Linux took advantage of. They blamed Linux, and tried to _claim_ Linux, but neither was so...
> the FSF has successfully predicted future problems with technology and
> policy. (Whether they've been the best positioned to deal with them in
> all cases is another matter.)
> the FSF for the GPL and LGPL, and the concept of copyleft, which they
> rather clearly originated. Without that, it seems highly likely that
> Linux would be a predominantly all-permissive and far more proprietary
> ecosystem.
CC0 and the BSD/MIT/X licences have an important property that "this work is released into the public domain" does not: they are legally efficacious in (for example) France, which does not recognize in law any right of an author to relinquish their rights to a work.
Open Definition 2.0
Open Definition 2.0
Rob specializes in writing long analyses of why people shouldn't get credit for what they've done. He wrote one about me a while ago that real lawyers say is wrong.
'nother one
'nother one
Wol
'nother one
'nother one
'nother one