From: Joshua Saddler <nightmorph@gentoo.org>
To: gentoo-doc@lists.gentoo.org
Subject: Re: [gentoo-doc] Supporting CC-BY-SA 3.0 and later versions
Date: Tue, 29 Nov 2011 13:00:09 -0800 [thread overview]
Message-ID: <20111129130009.7b3971d3@angelstorm> (raw)
In-Reply-To: <20111127174137.GC18017@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1782 bytes --]
On Sun, 27 Nov 2011 17:41:37 +0000
Sven Vermeulen <swift@gentoo.org> wrote:
> Hi
> guys,
> With http://wiki.gentoo.org having their documents as CC-BY-SA 3.0,
> I thought it might be a good idea to work this out for our
> documents as well. That would allow us to "tech-write" stuff that
> is on the wiki properly, but also use the newer (and recommended)
> version.
> Of course, that won't be done by just making <license /> refer to
> the 3.0 as that will break our documents (legally, that is).
> Instead, I was considering to add @version support to the license
> entity (in dtd and xsl), update the supporting documents (xml-guide
> and the like) so that this can be done less
> intrusively.
> In other words, support "<license version='3.0' />" for documents
> that need to be CC-BY-SA 3.0, or for new
> documents.
> What's your take on
> this?
i should weigh in on this:
sure, go ahead and add the version attribute. only issue i can see is
that we'll have a ton of different licenses in play over time, which
will lead to the same problem we have now between the wiki and /doc/,
except that the potential conflicts will all be in /doc/, between our
own documents.
as long as future docs are copyrighted to the gentoo foundation or
something, relicensing to use the latest version of CC shouldn't be
much of a problem. though i really hate the idea of blanket
relicensing in general, having seen all the issues that's caused for
gentoo-wiki.com over the years.
we might want to think about something like the "or later" clause in
recent GPL versions, just to be able to keep up with the changes in
Creative Commons. although "or later" doesn't cover switching to a
completely different license, should that become necessary.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2011-11-29 21:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-27 17:41 [gentoo-doc] Supporting CC-BY-SA 3.0 and later versions Sven Vermeulen
2011-11-28 3:11 ` Mr. Aaron W. Swenson
2011-11-28 18:05 ` Sven Vermeulen
2011-11-28 20:21 ` Chema Alonso
2011-11-29 1:11 ` [gentoo-doc] " Duncan
2011-11-29 13:01 ` Sven Vermeulen
2011-11-29 15:19 ` wireless
2011-11-29 15:39 ` Sven Vermeulen
2011-11-30 2:19 ` Duncan
2011-11-29 21:00 ` Joshua Saddler [this message]
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=20111129130009.7b3971d3@angelstorm \
--to=nightmorph@gentoo.org \
--cc=gentoo-doc@lists.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