There is no RationalWiki without you. We are a small non-profit with no staff — we are hundreds of volunteers who document pseudoscience and crankery around the world every day. We will never allow ads because we must remain independent. We cannot rely on big donors with corresponding big agendas. We are not the largest website around, but we believe we play an important role in defending truth and objectivity.
If everyone seeing this today donates $5, we will meet our goal for 2018.
| Fighting pseudoscience isn't free.|
We are 100% user-supported! Help and donate $5, $20 or whatever you can today with !
GNU Free Documentation License
| You betrayed the|
| Someone is wrong on|
It is unremittingly awful and grossly unsuitable for anything other than software manuals written on paper, and often not even those.
It is a cautionary tale in the dangers of excess restraint in the name of freedom.
No one understands how to reuse GFDL content safely, including the FSF. In the context of mirroring a widely-edited wiki or a page thereof, its terms are difficult to follow, legally unclear and may be technically impossible to comply with in a comparable degree of safety to the GPL or CC BY-SA. And don't even talk about images. Before Wikimedia went Creative Commons, tedious nerds would frequently claim that any given reuser of Wikipedia content was technically violating the GFDL no matter what shrubberies they obtained (thus putting off quite a lot of reusers). The Debian project classes it as a "non-free" license because its terms are unclear and onerous in practice.
The only reason it is not a minor footnote in the "miserable failures" section of free licensing history is that it was used for Nupedia (because the Creative Commons (CC BY-SA) hadn't started then), which evolved into Wikipedia, which also used it, and quickly became the largest repository of GFDL content by far. With many years' effort, the Wikimedia Foundation convinced the FSF and Stallman in 2008 to allow relicensing GFDL content on wikis as CC BY-SA, so that text could be sanely edited on a wiki, let alone shared with the entire rest of the free-content world, who had gone for a license easily obeyed by mere humans.
There were those who vociferously objected to Wikimedia changing from GFDL to CC BY-SA, because they considered the difficulty of reusing content in any practical manner to be a feature rather than a problem. They may have rather missed the point.
Appallingly, the FSF is still pushing the thing. Even though they themselves say at the tricky bits "better get a lawyer, son." Because freedom only for those with copyright lawyers on retainer is still technically freedom, right? Unless you have a spectacularly good reason, ignore them and just use CC BY-SA, CC BY or public domain, like everyone else does.
The GFDL is not to be confused with the GNU Public License (GPL), a far better license intended specifically for software.
The good points
- The escape clause (section 11).
- Providing thought experiments for bored copyright nerds.
- Um ...
- That's it.
In fairness it was one of the first copyleft licenses for data (though the Design Science License may pre-date it), so it's understandable that significant mistakes were made. That it managed to fit so many mistakes into one license at least provided a warning for those who were to follow.
- Abbreviated as FDL by the FSF, but as GFDL by Wikimedia and many others.
- The FLOSS Manuals Foundation eschewed it in favor of the GPL, the FSF's greatest hit ... with which the GFDL is incompatible. Nice one.
- One RationalWikian sent a query about how it applies to aggregates; three months later, the FSF cut-and-pasted their "we have no idea either" response, suggesting you read the license text and consult your attorney. Given Wikimedia's attorney at the time was Mike Godwin and it made his head hurt too, this strongly suggests no one left at the FSF wants to think about this thing. They finally clarified the issue in GFDL 1.3.
- Every copy must have the full 23 kilobytes of license text attached, about seven pages of single-spaced 12 point. This is not so good for single articles or photographs, and Internet video is likely impossible to reproduce under the GFDL in legal safety. This is, of course, the easiest term of the GFDL to obey. CC BY-SA allows the license to be named by reference.
- General Resolution: Why the GNU Free Documentation License is not suitable for Debian main. The Debian Free Software Guidelines threat model is: if an innocent reuser follows the terms, can an insane copyright holder sue them anyway and have it not thrown out immediately? The GFDL failed in several regards. Some GFDL variants are allowed as technically DFSG-free, but Debian still recommends against it as it's incompatible with everything else on Earth.
- Wikipedia/CC news: FSF releases FDL 1.3
- An open response to Chris Frey regarding GFDL 1.3 (Richard Stallman, FSF licensing blog)
- And still bitch about it, evidently not understanding the term "or later" that was there every damn time they clicked "Submit."
- For example, the video problem can be addressed by including the license text and other stuff required as a fold-out on the Betamax box. Video on the internet may present more of a problem.
- Betamax? Would VHS tapes just be too relevant for the license to handle?
- DESIGN SCIENCE LICENSE: TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION