From: Thomas S. Dye <tsd@tsdye.com>
To: Oleh Krehel <ohwoeowho@gmail.com>
Cc: Org-Mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: How to make a non-GPL Org-mode exporter?
Date: Mon, 27 Jul 2015 07:13:12 -1000 [thread overview]
Message-ID: <m2lhe1mslz.fsf@tsdye.com> (raw)
In-Reply-To: <874mkp37hq.fsf@gmail.com>
Oleh Krehel <ohwoeowho@gmail.com> writes:
> Marcin Borkowski <mbork@mbork.pl> writes:
>
>> And what if I explicitly want people to be able to use my code in
>> a proprietary software?
>
> Then you're out of luck. Just like thousands (millions) of programmers
> are out of luck when they want to examine the code of a closed source
> proprietary software.
>
> If I asked someone for Microsoft Word source code, because I want to
> understand why my macro doesn't work, they would laugh in my face. And
> then bring up that situation as a joke for years. A credit to FSF
> people: no one is laughing at you. Myself included, I tried to explain
> the benefits of GPL, but if you don't want to listen that's fine.
>
> --Oleh
Amen. History over the last 500 years is littered with defunct social
organizations based on rights of person (claims that members can't be
excluded from the use or enjoyment of some social product, like the
GPL). Over and over, the introduction into them of property rights
(claims that individuals can exclude members from the use or enjoyment
of some social product), often against violent protest, eventually
destroyed both the social organizations and the rights of person they
tried to perpetuate.
All the best,
Tom
--
Thomas S. Dye
http://www.tsdye.com
next prev parent reply other threads:[~2015-07-27 18:35 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
2015-07-27 16:12 ` Oleh Krehel
2015-07-27 17:12 ` Marcin Borkowski
2015-07-27 17:13 ` Thomas S. Dye [this message]
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=m2lhe1mslz.fsf@tsdye.com \
--to=tsd@tsdye.com \
--cc=emacs-orgmode@gnu.org \
--cc=ohwoeowho@gmail.com \
/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).