From: Nathanael Nerode <neroden@twcny.rr.com>
To: gcc@gcc.gnu.org
Subject: doxygen, GPL incompatibility of FDL, and the horror
Date: Sun, 25 May 2003 02:55:00 -0000 [thread overview]
Message-ID: <20030525023000.GA2105@doctormoo> (raw)
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.
Gah!
[I hate the FDL more and more...]
--Nathanael
next reply other threads:[~2003-05-25 2:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-25 2:55 Nathanael Nerode [this message]
2003-05-25 8:18 ` Gerald Pfeifer
2003-05-27 19:36 ` Mike Stump
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=20030525023000.GA2105@doctormoo \
--to=neroden@twcny.rr.com \
--cc=gcc@gcc.gnu.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).