public inbox for ecos-maintainers@sourceware.org
 help / color / mirror / Atom feed
From: Jonathan Larmour <jifl@eCosCentric.com>
To: eCos Maintainers <ecos-maintainers@ecos.sourceware.org>
Subject: Documentation License
Date: Tue, 11 May 2004 21:52:00 -0000	[thread overview]
Message-ID: <40A14B02.3010006@eCosCentric.com> (raw)

The time is coming up (I hope!) when we'll need to make some choices about 
our documentation license. The FSF have already said that our existing Open 
Publication License (with the license options) is not acceptable to them. 
However, I don't know if people are aware, but not everyone is happy about 
the FSF's own Free Documentation License. There's a long page about it at 
http://home.twcny.rr.com/nerode/neroden/fdl.html but the summary is that 
surprisingly enough the license is not Free.

Personally I would not be happy with the FDL either, but of course that's 
just me :-). I am prepared to argue with the FSF about that. But 
http://www.gnu.org/licenses/licenses.html does helpfully say: "occasionally 
we use other free documentation licenses" so that's encouraging.

That web page suggests some alternatives:
- For GPL'ed programs, licence the manual under the GPL (mutatis mutandis)
- If you don't mind people making proprietary versions of your manual, use 
a permissive, non-copyleft license such as the X11 license. (The X11 
license explicitly mentions documentation.)
- If you have to use the GFDL for some reason, dual-licence your 
documentation under the program license.

But there are other options, the best resource for which being 
http://www.gnu.org/licenses/license-list.html#FreeDocumentationLicenses 
especially since that list is officially acceptable with the FSF.

To save searching since the link is broken, the FreeBSD doc license is:

-=-=-=-=-
Redistribution and use in source (SGML DocBook) and 'compiled' forms (SGML, 
HTML, PDF, PostScript, RTF and so forth) with or without modification, are 
permitted provided that the following conditions are met:

    1. Redistributions of source code (SGML DocBook) must retain the above 
copyright notice, this list of conditions and the following disclaimer as 
the first lines of this file unmodified.
    2. Redistributions in compiled form (transformed to other DTDs, 
converted to PDF, PostScript, RTF and other formats) must reproduce the 
above copyright notice, this list of conditions and the following 
disclaimer in the documentation and/or other materials provided with the 
distribution.

Important: THIS DOCUMENTATION IS PROVIDED BY THE FREEBSD DOCUMENTATION 
PROJECT "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A 
PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FREEBSD 
DOCUMENTATION PROJECT BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED 
TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR 
PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF 
LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING 
NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS 
DOCUMENTATION, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
-=-=--=-=-

The apple license could also not be read as the server was down. So here's 
Google's cache: 
http://66.102.9.104/search?q=cache:d_swFDmNzqIJ:www.opensource.apple.com/cdl/

Personally I'm inclined to think the FreeBSD Documentation License is 
adequate (the Apple license just more legalese stuff and verbose, but 
equivalent as far as I can see), as I'm not too enamoured about making the 
documentation "Free" (as in FSF "Free") primarily because the point of eCos 
is the code, and the documentation is there to help, not an asset to be 
controlled.

Other thoughts/options/opinions?

Jifl
-- 
eCosCentric    http://www.eCosCentric.com/    The eCos and RedBoot experts
--["No sense being pessimistic, it wouldn't work anyway"]-- Opinions==mine

             reply	other threads:[~2004-05-11 21:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-11 21:52 Jonathan Larmour [this message]
2004-05-13 13:09 ` Andrew Lunn
2004-05-13 13:23   ` Jonathan Larmour
  -- strict thread matches above, loose matches on Subject: below --
2002-09-12 12:07 documentation license Bart Veer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=40A14B02.3010006@eCosCentric.com \
    --to=jifl@ecoscentric.com \
    --cc=ecos-maintainers@ecos.sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).