From: Greg Troxel <gdt@ir.bbn.com>
To: Daniele Nicolodi <daniele@grinta.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: Org-mode exporters licensing
Date: Mon, 27 Jul 2015 08:42:03 -0400 [thread overview]
Message-ID: <rmiio953h7o.fsf@fnord.ir.bbn.com> (raw)
In-Reply-To: <55B62153.4070904@grinta.net> (Daniele Nicolodi's message of "Mon, 27 Jul 2015 14:17:23 +0200")
[-- Attachment #1: Type: text/plain, Size: 1423 bytes --]
Daniele Nicolodi <daniele@grinta.net> writes:
> On 27/07/15 13:52, Marcin Borkowski wrote:
>> I disagree. Licensing a tutorial with GPL is a stupid thing to do.
>> A tutorial may contain code which people naturally mimic (or even
>> copy). Such things should definitely be in PD.
[many excellent comments. As a nit, to reuse another's work under the
GPL under a BSD license, you need more than them not to object; you
need their affirmative permission. And if much of org is assigned to
the FSF, as I believe it is, that means the FSF's permission. That's a
use of resources about something that doesn't really matter much.]
Indeed. A major point of which Marcin seems unaware is that licensing
in a project in is more than a legal matter. The license terms are a
declaration of intent for how the code will be shared, and people
contirbute under an expectation that those norms will be followed.
In particular, the GPL is designed to allow sharing only when the
recipients receive rights to further share (and more). In other words,
not only is the code Free Software, but any derived works (that are
distributed) will also be Free Software. With a BSD-style license, or
PD, derived works may or may not be Free.
Regardless of licensing, you can't make a derived work from copyrighted
code and have it be PD. And as Daniele points out, new works being PD
only works in some jurisdictions (hence CC0).
[-- Attachment #2: Type: application/pgp-signature, Size: 180 bytes --]
next prev parent reply other threads:[~2015-07-27 12:42 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-27 8:06 Org-mode exporters licensing Marcin Borkowski
2015-07-27 8:16 ` Rasmus
2015-07-27 8:26 ` Marcin Borkowski
2015-07-27 8:35 ` Rasmus
2015-07-27 9:05 ` Marcin Borkowski
2015-07-27 9:46 ` Eric S Fraga
2015-07-27 11:50 ` Marcin Borkowski
2015-07-27 8:42 ` Eric S Fraga
2015-07-27 8:59 ` Marcin Borkowski
2015-07-27 9:31 ` Eric S Fraga
2015-07-27 11:52 ` Marcin Borkowski
2015-07-27 12:17 ` Daniele Nicolodi
2015-07-27 12:42 ` Greg Troxel [this message]
2015-07-27 12:52 ` Daniele Nicolodi
2015-07-27 17:45 ` Marcin Borkowski
2015-08-02 16:54 ` Nicolas Goaziou
2015-07-27 17:44 ` Marcin Borkowski
2015-07-27 17:42 ` Marcin Borkowski
2015-07-27 18:02 ` Daniele Nicolodi
2015-07-27 18:20 ` Marcin Borkowski
2015-07-27 18:30 ` Daniele Nicolodi
2015-07-27 18:49 ` Marcin Borkowski
2015-07-28 7:05 ` Robert Klein
2015-07-27 12:06 ` Oleh Krehel
2015-07-27 12:27 ` Rasmus
2015-07-27 12:25 ` Oleh Krehel
2015-07-27 12:50 ` Daniele Nicolodi
2015-07-27 17:47 ` Marcin Borkowski
2015-07-27 17:10 ` Achim Gratz
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
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=rmiio953h7o.fsf@fnord.ir.bbn.com \
--to=gdt@ir.bbn.com \
--cc=daniele@grinta.net \
--cc=emacs-orgmode@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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).