From: Dmitry Alexandrov <dag@gnui.org>
To: Giovanni Biscuolo <g@xelera.eu>, tylercstrouth@gmail.com
Cc: help-gnu-emacs@gnu.org
Subject: Re: Using Emacs for commercial purposes
Date: Thu, 16 Jul 2020 15:11:35 +0300 [thread overview]
Message-ID: <zh7zoe14.dag@gnui.org> (raw)
In-Reply-To: <87v9io29bu.fsf@roquette.i-did-not-set--mail-host-address--so-tickle-me> (Giovanni Biscuolo's message of "Wed, 15 Jul 2020 15:31:49 +0200")
[-- Attachment #1: Type: text/plain, Size: 874 bytes --]
Giovanni Biscuolo <g@xelera.eu> wrote:
> If you modify Emacs (or any Emacs package) you must comply to the terms of the licence.
> modify
Or distribute.
> See https://en.wikipedia.org/wiki/GNU_General_Public_License#Use_of_licensed_software for general information about freedom of use of GNU GPL licnsed free software
Actually, one might find reading the legal text itself [1] more benefiting than reading many various texts about the text (thankfully, FSF have always tried to keep its licences in English than legalese ;-)
In particular, many simplifications as well as detailed explanations of GNU GPL fail to state prominently the only point one might be really interested in:
| You are not required to accept [the terms of] this License [agreement] in order to receive or run a copy of the Program.
[1] <f1> C-c
or https://www.gnu.org/licenses/gpl-3.0.html
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]
next prev parent reply other threads:[~2020-07-16 12:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-15 11:09 Using Emacs for commercial purposes tylercstrouth
2020-07-15 13:28 ` phillip.lord
2020-07-15 13:31 ` Giovanni Biscuolo
2020-07-16 12:11 ` Dmitry Alexandrov [this message]
2020-07-16 14:37 ` Giovanni Biscuolo
2020-09-24 13:53 ` Jean Louis
2020-07-15 19:08 ` Emanuel Berg via Users list for the GNU Emacs text editor
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=zh7zoe14.dag@gnui.org \
--to=dag@gnui.org \
--cc=g@xelera.eu \
--cc=help-gnu-emacs@gnu.org \
--cc=tylercstrouth@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.