From: Daniel Jacobowitz <drow@false.org>
To: gdb@sourceware.org
Subject: Wiki content license
Date: Wed, 05 Mar 2008 16:23:00 -0000 [thread overview]
Message-ID: <20080305161440.GA25369@caradoc.them.org> (raw)
I have added a license notice to the GDB Wiki, based on a discussion
between Micah Cowan (wget maintainer) and Brett Smith (FSF license
compliance). It's appended below. The short version is that it lets
us use future text from the wiki in the manual directly, although for
large sections the FSF still recommends we get a copyright assignment.
Code will still need assignment.
Of course, because I added this to an existing Wiki, the "all content"
statement is not strictly true - you can't retroactively apply a
notice that way. I'm not sure what to do about that. The only
significant content that applies to are the plotting and STL macro
packages, which are code rather than data anyway, so I don't see a
big problem. If the owners of those packages object to the license
notice / assignment please let me know.
====
All content (C) 2008 Free Software Foundation. For terms of use,
redistribution, and modification, please see the WikiLicense page.
License for GDB Wiki content
The Free Software Foundation holds the copyright for all GDB code and
documentation. If you make significant contributions to the wiki that
might be useful in the official GDB documentation or source code,
please leave your contact information so we can arrange that if we
want to use your work in GDB.
Permission is granted to copy, distribute and/or modify this content
under the terms of the GNU Free Documentation License, Version 1.2 or
any later version published by the Free Software Foundation; with no
Invariant Sections, no Front-Cover Texts and no Back-Cover Texts.
Copyright Assignment for Wiki Changes
By contributing to any page on this wiki, you agree to assign
copyright for your contribution to the Free Software Foundation. The
Free Software Foundation promises to always use either a verbatim
copying license or a free documentation license when publishing your
contribution.
We grant you back all your rights under copyright, including the
rights to copy, modify, and redistribute your contributions.
====
--
Daniel Jacobowitz
CodeSourcery
next reply other threads:[~2008-03-05 16:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-05 16:23 Daniel Jacobowitz [this message]
2008-03-05 16:24 ` Robert Dewar
2008-03-05 16:32 ` Daniel Jacobowitz
2008-03-05 16:30 ` Thiago Jung Bauermann
2008-03-05 16:36 ` Daniel Jacobowitz
2008-03-05 16:31 ` Robert Dewar
2008-03-05 17:15 ` Daniel Jacobowitz
2008-03-06 16:31 ` Robert Dewar
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=20080305161440.GA25369@caradoc.them.org \
--to=drow@false.org \
--cc=gdb@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