public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Mike Stump <mrs@apple.com>
To: Nathanael Nerode <neroden@twcny.rr.com>
Cc: gcc@gcc.gnu.org
Subject: Re: doxygen, GPL incompatibility of FDL, and the horror
Date: Tue, 27 May 2003 19:36:00 -0000	[thread overview]
Message-ID: <6E4E85F2-9079-11D7-8138-003065A77310@apple.com> (raw)
In-Reply-To: <20030525023000.GA2105@doctormoo>

On Saturday, May 24, 2003, at 07:30 PM, Nathanael Nerode wrote:
> Just realized that the doxygen docs in libstdc++-v3 are under the FDL.
> The files they take information out of are under the GPL.  This is
> legitimate only because the FSF owns the copyrights and can release 
> them
> under any damn copyright it likes. :-/
>
> This appears to make the following scenario illegal for anyone who
> hasn't assigned all their copyrights to the FSF (or indeed someone who
> has, but doesn't have the FSF's permission to modify copyrights)
> * I modify the doxygen comments.
> * I rerun doxygen.
> * I distribute the resulting documentation.
>
> Gah!
>
> On the more immediate note, anyone who contributed any doxygenated text
> to libstdc++-v3 is a contributor to the manual, and according to RMS, 
> if
> they don't have a post-January 2000 copyright statement, we shouldn't
> use their work, which means we can't rerun doxygen.

If I understand this correctly...

Docs are generated from GPL source.  We want the generated docs to be 
covered by some other copyright.

Solution, have the FSF officially bless this and then document it as a 
blessed transformation.

Essentially what the FSF blesses is the idea that certain bits of the 
GPL source are also under another license (FDL), and that one is 
permitted to so convert these bits into stand alone content (a set of 
html pages for example), and that content is FDL covered.

Informally, I think that this really is a non-issue, but, because it 
touches legal things, it does really need to be discussed with the FSF 
and proposed and accepted and documented for all to understand.  Thanks 
for bringing it up.

  parent reply	other threads:[~2003-05-27 19:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-25  2:55 Nathanael Nerode
2003-05-25  8:18 ` Gerald Pfeifer
2003-05-27 19:36 ` Mike Stump [this message]
2003-05-27 19:40   ` Joe Buck
2003-05-27 19:48   ` Joseph S. Myers

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=6E4E85F2-9079-11D7-8138-003065A77310@apple.com \
    --to=mrs@apple.com \
    --cc=gcc@gcc.gnu.org \
    --cc=neroden@twcny.rr.com \
    /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).