From: "Sherman Boyd" <meekrob@mitosys.com>
To: <gentoo-dev@gentoo.org>
Subject: [gentoo-dev] How should Gentoo docs be licensed?
Date: Mon, 8 Apr 2002 07:04:26 -0700 [thread overview]
Message-ID: <MAECLFPHPNOHNHHJHBGPAEENCDAA.meekrob@mitosys.com> (raw)
How should Gentoo docs be licensed? I know of two documentation licenses, the GFDL and the OPL. Anyone know of any alternatives?
http://www.fsf.org/licenses/fdl.html
http://opencontent.org/openpub/
I think it's important that Gentoo choose or create ONE (as opposed to letting the author decide) license for it's official documentation. Having one documentation license simplifies things, and lowers our chances of breaking a license (or copyright) when we distribute our documentation.
Both licenses are seem good to me, but I am not a copyright lawyer. The GFDL is definitely longer, and more specific. The OPL is short and clean, easily understood by a layperson.
sherman (meekrob)
next reply other threads:[~2002-04-09 1:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-08 14:04 Sherman Boyd [this message]
2002-05-02 20:15 ` [gentoo-dev] How should Gentoo docs be licensed? Bjarke Sørensen
2002-05-03 20:57 ` Jean-Michel Smith
2002-05-03 21:39 ` Bjarke Sørensen
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=MAECLFPHPNOHNHHJHBGPAEENCDAA.meekrob@mitosys.com \
--to=meekrob@mitosys.com \
--cc=gentoo-dev@gentoo.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