From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: Marcin Borkowski <mbork@mbork.pl>
Cc: Org-Mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: Org-mode exporters licensing
Date: Mon, 27 Jul 2015 09:42:19 +0100 [thread overview]
Message-ID: <87a8uigff8.fsf@ucl.ac.uk> (raw)
In-Reply-To: <87io962fdz.fsf@mbork.pl> (Marcin Borkowski's message of "Mon, 27 Jul 2015 10:06:48 +0200")
On Monday, 27 Jul 2015 at 10:06, Marcin Borkowski wrote:
> Hi all,
>
> 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. 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 you reuse GPL code, you have to distribute your code under GPL as
well basically. From the COPYING file in the org distribution:
[...]
For example, if you distribute copies of such a program, whether
gratis or for a fee, you must pass on to the recipients the same
freedoms that you received. You must make sure that they, too,
receive or can get the source code. And you must show them these
terms so they know their rights.
Developers that use the GNU GPL protect your rights with two steps:
(1) assert copyright on the software, and (2) offer you this License
giving you legal permission to copy, distribute and/or modify it.
[...]
Oh, and it's FSF lawyers you should worry about, not EFF! Two different
organisations albeit with some overlap in goals.
HTH,
eric
--
: Eric S Fraga (0xFFFCF67D), Emacs 25.0.50.1, Org release_8.3beta-1293-g985420
next prev parent reply other threads:[~2015-07-27 8: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 [this message]
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
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=87a8uigff8.fsf@ucl.ac.uk \
--to=e.fraga@ucl.ac.uk \
--cc=emacs-orgmode@gnu.org \
--cc=mbork@mbork.pl \
/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).