From: Marcin Borkowski <mbork@mbork.pl>
To: Org-Mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: How to make a non-GPL Org-mode exporter?
Date: Mon, 27 Jul 2015 18:01:51 +0200 [thread overview]
Message-ID: <87k2tlvbbk.fsf@mbork.pl> (raw)
In-Reply-To: <87wpxlocpz.fsf@ucl.ac.uk>
On 2015-07-27, at 17:13, Eric S Fraga <e.fraga@ucl.ac.uk> wrote:
> On Monday, 27 Jul 2015 at 14:10, Marcin Borkowski wrote:
>
> [...]
>
>> And I see no reason to impose GPL on them.))
>
> [...]
>
>> And please understand that if I'm sounding a bit angry in this email,
>> it's because I'm *very* angry about this whole lawyer mafia
>> restricting my freedom (again). (Note: I'm all for restricting
>> people's freedom when there are important reasons for that. I just
>> consider this situation not to be one of these.)
>
> Interestingly enough, the whole premise of FSF and GPL is that
> restrictions imposed by hiding code and/or not allowing redistribution
> are restricting our freedom!
As I wrote in other posts (today and also some time ago, on other
FSF-hosted list), I used to consider FSF your typical 3-letter
organization. Though I revised my standpoint on that a bit, I still am
not a huge fan of FSF and GPL. Also, I don't consider distributing
non-(free-as-in-FSF) software as morally evil, so I see no reason to
force anyone to use GPL.
> You'll find some (many?) of us on this list will disagree fundamentally
> with you: for me, GPL is about freedom and ensuring that freedom is
> not restricted. Imposing GPL, as you put it, is about ensuring that
> those that want to make use of our code or text pass on the same rights
> they made use of in using this code or text.
Grown from the TeX community, and knowing how TeX's license works,
I find GPL to be rather restrictive.
And what if I explicitly want people to be able to use my code in
a proprietary software? Or if I just want to use the "Unlicense"? Or
if I don't want to use GPL on principle? (And if I still consider Emacs
to be technically superior to most other software, and do not want to
stop using it and writing Elisp?) In all these cases, GPL actually
restricts me.
> Note that all of the above is for people writing code that they
> subsequently wish to distribute. If they keep it to themselves, the
> licence used is a non-issue...
That I already learned from this discussion. It's good that FSF does
not try to deny me at least this minimal amount of freedom... ;-P
> Of course, nobody is forced to use any code I write so I am not stopping
> anybody from doing whatever they want with *their* code. Although my
> contributions to org are infinitesimally small, I expect the GPL to be
> observed in any derivation of org.
With that I do agree (and it has nothing to do with the question whether
I like GPL or not, it's just basic ethics). Now the main (and
recurring) question: is an exporter a "derivation" of Org? My common
sense says it's probably not. Is an exporter built by copying an
existing one and replacing all the code relevant to one particular
format with the code generating other format, leaving the skeleton
(which is more or less identical in most if not all official exporters,
and it's difficult to even conceive one radically different!) intact,
a "derivation" of the existing exporter? My common sense is unsure, and
hence my question and this discussion. Is any Elisp package
a "derivation" of Emacs? My common sense says definitely not.
> YMMV, of course :-)
Well, it seems it does. :-)
BTW, while I do not consider myself a "hacker" (in a sense used by RMS)
- I'm probably too inexperienced to deserve to be called that - I find
it ironic in the context of this exchange to recall this excerpt from
RMS's "On hacking":
,----
| Hackers typically had little respect for the silly rules that
| administrators like to impose, so they looked for ways around.
`----
Best,
--
Marcin Borkowski
http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski
Faculty of Mathematics and Computer Science
Adam Mickiewicz University
next prev parent reply other threads:[~2015-07-27 16:02 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
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 [this message]
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=87k2tlvbbk.fsf@mbork.pl \
--to=mbork@mbork.pl \
--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).