emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Daniele Nicolodi <daniele@grinta.net>
To: emacs-orgmode@gnu.org
Subject: Re: Org-mode exporters licensing
Date: Mon, 27 Jul 2015 14:17:23 +0200	[thread overview]
Message-ID: <55B62153.4070904@grinta.net> (raw)
In-Reply-To: <87r3ntvmuq.fsf@mbork.pl>

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.

As yourself pointed out in one of your emails, in many legal
ordinations, there is no such concept as public domain: you cannot
renounce to the copyright on your intellectual production.

Therefore licensing something as public domain is not quite possible. If
you want to grant the users of your code the most freedom (but do not
care about this freedom being carried over to others) the 3-Clause BSD
license http://opensource.org/licenses/BSD-3-Clause, the 2-Clause BSD
license http://opensource.org/licenses/BSD-2-Clause, or the MIT license
http://opensource.org/licenses/mit-license.html are good candidate
licenses formulated in the framework of copyright law as accepted
internationally.

However, you cannot derive your work from some other work distributed
under GPL and license it with a more permissive license (as the ones
suggested above). What constituted a derived work is however not
scientifically defined (and you have been rather terse in describing how
your work build upon code released under the GPLv3). In one place you
explicitly mention running a query-replace on the source code:
mechanical transformations of the source code are considered derived
works, even if the end result does not resemble at all the original.

I would suggest you to do derive your work from the GPL code and then
consult with the authors about its licensing. If you are only using the
GPL code as a skeleton, I think they would not have objections (but you
could also easily re-implement it from scratch).

Other than this I would recommend you to refrain from harsh comments on
a matter on which you hold strong ideas but weak knowledge (as most of
this thread demonstrates). Especially if your positions seem detrimental
of the Copyleft model, and you are asking for help in a mailing-list
devoted to a very successful Copyleft program.

Cheers,
Daniele

  reply	other threads:[~2015-07-27 12:17 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 [this message]
2015-07-27 12:42           ` Greg Troxel
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=55B62153.4070904@grinta.net \
    --to=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).