emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Paul Rudin <paul-sqPYmOVXOov10XsdtD+oqA@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: How to make a non-GPL Org-mode exporter?
Date: Tue, 28 Jul 2015 13:33:32 +0100	[thread overview]
Message-ID: <86lhe0jwbn.fsf@rudin.co.uk> (raw)
In-Reply-To: 87bnex4wzf.fsf@gmail.com

Oleh Krehel <ohwoeowho-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:

> Marcin Borkowski <mbork-yQ6rpnL/fpw@public.gmane.org> writes:
>
>> Hi all,
>>
>> after a short discussion in a recent thread, I have a serious technical
>> question.
>>
>> Assume that (for some reason) I want to write an Org-mode exporter which
>> won't be GPL'd.  (Use-case: having written a few custom exporters, I'm
>> writing a tutorial on them, and I consider publishing a *tutorial* with
>> GPL'd code a Bad Thing™.  (The idea of a programming tutorial is that
>> other people can or even should reuse the code in the tutorial, right?
>> And I see no reason to impose GPL on them.))
>>
>> How do I do that?  Is that even possible?  Also, is it possible to get
>> an actual answer to this question without spending money on lawyers?
>
> Like I said in an earlier message just a few minutes ago, you can do it,
> but you can't use org.el or Elisp at all, unless you implement your own
> Elisp engine that you call.

AIUI, in the UK at least this isn't correct. There is no infringement of
copyright by writing and distributing your own elisp (or any other
language) code.

Whether or not somebody else chooses to use a particular elisp
implementation to run that code is up to them. But you don't have any
liability simply by using the language.

  parent reply	other threads:[~2015-07-28 12:33 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-27 12:10 How to make a non-GPL Org-mode exporter? Marcin Borkowski
2015-07-27 12:16 ` Oleh Krehel
2015-07-27 13:02   ` Rainer M Krug
2015-07-27 13:09     ` Greg Troxel
2015-07-27 13:13       ` Andreas Hilboll
2015-07-27 13:30         ` Rainer M Krug
2015-07-27 14:05       ` Marcin Borkowski
2015-07-27 14:03   ` Marcin Borkowski
2015-07-28 12:33   ` Paul Rudin [this message]
2015-07-27 12:39 ` Daniele Nicolodi
2015-07-27 16:59   ` Marcin Borkowski
2015-07-27 18:02     ` Nick Dokos
2015-07-27 18:12       ` Marcin Borkowski
2015-07-27 18:45     ` Daniele Nicolodi
2015-07-28  7:55     ` Oleh Krehel
2015-07-29 14:54       ` Aaron Ecay
2015-07-30 10:08         ` Oleh Krehel
2015-07-27 13:05 ` Greg Troxel
2015-07-27 14:32   ` Marcin Borkowski
2015-07-27 13:58 ` Scott Randby
2015-07-27 16:32   ` Marcin Borkowski
2015-07-27 15:13 ` Eric S Fraga
2015-07-27 16:01   ` Marcin Borkowski
2015-07-27 16:12     ` Oleh Krehel
2015-07-27 17:12       ` Marcin Borkowski
2015-07-27 17:13       ` Thomas S. Dye
2015-07-27 16:54     ` Eric S Fraga
2015-07-27 17:04       ` Marcin Borkowski
2015-07-27 18:38         ` Eric S Fraga
2015-07-28  8:07           ` Oleh Krehel
2015-07-28  9:00             ` Eric S Fraga
2015-07-28  9:00               ` Oleh Krehel
2015-07-28 10:38                 ` Eric S Fraga
2015-07-28  9:20               ` Andreas Hilboll
2015-07-28  9:30                 ` Oleh Krehel
2015-07-28 10:14                   ` Andreas Hilboll
2015-07-28 10:29                     ` Oleh Krehel
2015-07-27 18:32 ` Richard Lawrence
2015-08-04 15:04 ` Phillip Lord

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=86lhe0jwbn.fsf@rudin.co.uk \
    --to=paul-sqpymovxoov10xsdtd+oqa@public.gmane.org \
    --cc=emacs-orgmode-mXXj517/zsQ@public.gmane.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).