Slashdot Mirror

← Back to Stories (view on slashdot.org)

Debian GNU/Linux to Declare GNU GFDL non-Free?

Posted by CmdrTaco on from the read-those-licenses dept.

Syntaxis writes "There's some considerable argy-bargy in progress over whether or not GNU's own GFDL is a Free documentation license at all. At issue are "invariant sections" which cannot be removed from derivative works. Check out the thread culminating in the proposed motion to take action. The current consensus on Debian-legal does indeed appear to be that one of the FSF's own licenses is non-Free under the terms of the Debian Free Software Guidelines! Well, documentation for GPLed projects countermanding the very freedoms embodied in the GPL certainly seems insane to me."

6 of 454 comments (clear)

  1. Lack of pragmatism by Eloquence · · Score: 4, Informative
    People who choose the FDL usually know little about its specifics -- they just want their documentation to be available under a copyleft license. Thus, virtually all FDL documents are free of invariant sections. Instead of condemning the license outright, a pragmatic approach would therefore be to define a threshold of invariant content (say, 20%), after which a document is no longer considered free. The FDL is the standard license for free, open content (see also Wikipedia, perhaps the largest open content project), and ostracizing it entirely will get us nowhere.

    Upon reading the post, however, what I see is a bean counter mentality that can really be dangerous to open source projects as a whole. I shudder at the thought of hundreds of package maintainers being contacted to deal with this "license issue", which is really a non-issue to anyone with some common sense. This time would better be spent working on real problems -- it's not like Debian has none of those ...

  2. Re:Debian has some weird licencing rules. by Mendax+Veritas · · Score: 5, Informative

    You obviously don't understand what the Debian project is all about. It isn't just a Linux distro; it is specifically a free software distro. They don't want anything that isn't free-as-in-liberty. That's why they have the licensing rules that they do.

  3. Re:If you want true open source on anything by BJH · · Score: 5, Informative

    In case you didn't realise, any works completely of your creation can be used in any way you like, as you're the sole copyright holder.

    So the only case where you wouldn't be able to take a work you've released under GPL and include it in a closed source application is where you've either (a) originally taken source that was under GPL or similar and added to it or (b) applied patches from people where those patches were supplied in the understanding that the resulting app would be released under GPL or similar license.

    In other words, your comment about releasing your own works into the public domain because it gives you more freedom are wrong.

  4. Re:Same with GPL by Mendax+Veritas · · Score: 5, Informative

    Either you're trolling, or you don't understand the issue. Of course you can't change the license; that would make no sense. The issue has to do with the fact that the GFDL allows portions of the licensed document to be marked "invariant", meaning you can't change those parts. This is logically equivalent to what you would have if the GPL allowed authors to mark parts of their source code as unmodifiable. It essentially means that the document is not entirely free, but only mostly free. The debate within Debian has been about whether "mostly free" is good enough.

  5. Re:how? by demi · · Score: 4, Informative

    You'll see that the FSF is concerned with free documentation as well. The problem here is that some people are misunderstanding the invariant section provision of the FDL. As stated in that link, not every piece of writing is the same thing as software. The FDL insists that all the technical instructions be freely modifiable so that someone who creates a derivative piece of software can also modify the manual to keep it accurate.

    However, some parts of a manual might be literary or express an author's opinion. This might be a political opinion ("software should be free") or it could be a technical opinion ("monolithic kernels suck"). But whatever it is it doesn't make sense for the creator of a derivative manual to change those opinions--that would be lying about the original author's intent.

    The FDL recognizes that an author may have the need to guard these sections (remember, they can't have anything to do with the instructions to use the program). It doesn't make the manual any less free.

    --
    demi
  6. I've used the FDL for code restrictive purposes by azzy · · Score: 4, Informative

    When I finished my MSc last year, I had to publish my thesis, and sourcecode. The university instructued us that the thesis had to claim them as the copyright owners, as they had a claim over our code and report. The lecturers were aware that we would maybe want to contest this, and noted that we'd probably have a fair point as we had never signed away our IP rights.. yet in order to be accepted our reports MUST contain the copyright info as stated, unless a alternative was agreed. I got my course director to accept the FDL as a license on my work in which I claimed the copyright, and I published my source code as an invariant section. As no other license/copyright info appeared on my sourcecode either printed or on disk, I essentially made them unable to claim ownership of it and make modifications.

    Now I don't have any objections to the GPL or freedom over sourcecode in principle, I just didn't want them to claim ownership and rights over it.

    So I was thankful that the invariant clause of the FDL allowed me to restrict the published sourcecode.

    My take on this may be wrong, IANAL, but seemed to be the case, hence why I did it.