From: tycho garen <firstname.lastname@example.org>
To: Bastien <email@example.com>
Subject: Re: What license for Worg?
Date: Sun, 8 Aug 2010 17:10:43 -0400 [thread overview]
Message-ID: <20100808211042.GA27500@deleuze.linlan> (raw)
On Wed, Aug 04, 2010 at 06:36:45AM +0200, Bastien wrote:
> Here is what I read at the bottom of every emacswiki.org page:
> This work is licensed to you under version 2 of the GNU General Public
> License. [..]
> So this is GPLv2. Any idea why this isn't GPLv3?
No clue. I must confess that I'm writing this email without the
benefit of a net connection, so I can't check if emacs itself has
moved to GPLv3. If it hasn't I can imagine wanting to keep emacs wiki
compatible with emacs itself.
> Also, I find the formulation a bit confusing. Is it the standard
> formulation when multi-licensing? Where can I found an example of a
> clear multi-licensing statement?
I'm not a lawyer or even particularly interested in the technicalities
of such, but I do think that the emacs-wiki statement errs on the side
of being human intelligible at the expense of concision.
> I've not made up my mind yet, but I would go for something like that:
> The content of the Worg website is licensed under the CC BY-SA 3.0 and
> the GPLv3 and the GFDL 1.3. You can choose to receive the content of
> Worg under any of these three licenses.
I'd include "or later" statements, so that Worg can optionally take
advantage of any updates to these licenses if they are revised to fix
issues that arise (which is, again, the same as emacs itself.) More
than anything, the "or later" statements, reduce potential future
headache. Perhaps something like
The content of the Worg website is licensed under the CC BY-SA 3.0
(or later) and the GNU GPLv3 (or later) and the GNU FDL 1.3 (or
later). You can choose to receive the content of Worg under any of
these three licenses.
Again, just a thought.
"don't get it right, get it written" -- james thurber
next prev parent reply other threads:[~2010-08-08 21:11 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-02 12:33 What license for Worg? Bastien
2010-08-02 16:59 ` David Maus
2010-08-02 18:50 ` Bernt Hansen
2010-08-03 9:34 ` Ian Barton
2010-08-04 4:26 ` Bastien
2010-08-13 23:32 ` Eric S Fraga
2010-08-03 12:53 ` tycho garen
2010-08-04 4:36 ` Bastien
2010-08-08 21:10 ` tycho garen [this message]
2010-08-09 19:36 ` David Maus
2010-08-10 1:35 ` Memnon Anon
2010-08-10 15:41 ` Bastien
2010-08-04 5:36 ` Bastien
2010-08-04 7:14 ` Ian Barton
2010-08-06 8:31 ` Bastien
2010-08-06 9:25 ` Andreas Röhler
2010-08-04 12:33 ` Sebastian Rose
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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.
Code repositories for project(s) associated with this public inbox
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).