emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Achim Gratz <Stromeko@nexgo.de>
To: emacs-orgmode@gnu.org
Subject: Re: Org-mode exporters licensing
Date: Mon, 27 Jul 2015 19:10:42 +0200	[thread overview]
Message-ID: <87h9op34rx.fsf@Rainer.invalid> (raw)
In-Reply-To: 87io962fdz.fsf@mbork.pl

Marcin Borkowski writes:
> I'm preparing a tutorial on writing Org-mode exporters.  To this end,
> I'm writing a (simplistic) Oddmuse/WikiCreole exporter.  Rather
> obviously, I'm modeling it on existing exporters (mainly ox-latex),
> which seem to share a lot of structure (function names and docstrings in
> particular).  I'd like to put my code in public domain.

I'm pretty sure that you cannot do that, for the simple reason that you
cannot unilaterally waive all creators' rights (of which copyright is
one part) in the EU to the best of my knowledge.  There is also no such
thing as "putting something into the public domain" in most
jurisdictions anyway, since PD is defined as the absence of any
applicable statutory rights.  This also makes PD a very shaky ground to
stand on, since something that is in the PD in one jurisdiction doesn't
necessarily stay that way in another.  You can license your publication
in a way that effectively makes it indistinguishable from PD, though.

> However, I reuse parts of GPL'd code (as I mentioned, quite generic
> ones, but still).  Is it fine, or should I expect a visit from EFF
> lawyers or something?

If the reuse is substantial enough (from your description I'd say yes),
then you have to license the result as GPL also.  That is just for the
code, not the tutorial, however.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Wavetables for the Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#BlofeldUserWavetables

      parent reply	other threads:[~2015-07-27 17:11 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
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 [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

  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=87h9op34rx.fsf@Rainer.invalid \
    --to=stromeko@nexgo.de \
    --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).