From: "Jason Self" <j@jxself.org>
To: libreplanet-discuss@libreplanet.org
Subject: Re: Can we licence our Clojure (Eclipse Public License 1.0) project with the GNU AFFERO GENERAL PUBLIC LICENSE?
Date: Tue, 23 May 2017 20:28:24 -0700 (PDT) [thread overview]
Message-ID: <1495596504.4586@jxself.org> (raw)
In-Reply-To: <11FB4C65-FB77-47F2-80D4-6A14A43C6121@dyne.org>
Aspasia Beneti <aspra@dyne.org> wrote ..
> and will be secured from been used for commercial purposes
I'm not entirely certain what you mean by this but I wanted to point
out a part from the Free Software Definition [0]:
"'Free software' does not mean 'noncommercial'. A free program must be
available for commercial use, commercial development, and commercial
distribution. Commercial development of free software is no longer
unusual; such free commercial software is very important. You may have
paid money to get copies of free software, or you may have obtained
copies at no charge. But regardless of how you got your copies, you
always have the freedom to copy and change the software, even to sell
copies."
I recommend reading the entire Free Software Definition along with
Selling Free Software [1].
Depending on what exactly you mean by the programing being "secured"
from commercial use, it may mean that it doesn't qualify as free
software to begin with.
On the other hand, if you mean 'commercial' as a synonym for
'non-free' or 'proprietary' then I'd like to point you to [2].
> However it was brought to our attention that GPL and EPL are
> incompatible (are they?)
Yes, the FSF has it in its list of GPL-Incompatible Free Software
Licenses [3]. Plus, there's also [4].
> Do you have any advice on what is the best way to go in our case?
There was a discussion on a new version of the EPL [5] but it seems to
have stalled. Regardless it would be good to help raise GPL
compatibility as something to be addressed in the next version of the EPL.
Until/less that happens perhaps some sort of exception is appropriate?
It may be best to contact licensing@fsf.org for help with such a thing
because it can be hard to get them "just right."
[0] https://www.gnu.org/philosophy/free-sw.html
[1] https://www.gnu.org/philosophy/selling.html
[2] https://www.gnu.org/philosophy/words-to-avoid.en.html#Commercial
[3] https://www.gnu.org/licenses/license-list.html#EPL
[4] https://eclipse.org/legal/eplfaq.php#GPLCOMPATIBLE
[5]
https://mmilinkov.wordpress.com/2013/05/31/community-review-of-the-eclipse-public-license/
next prev parent reply other threads:[~2017-05-24 3:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-23 14:49 Can we licence our Clojure (Eclipse Public License 1.0) project with the GNU AFFERO GENERAL PUBLIC LICENSE? Aspasia Beneti
2017-05-24 3:28 ` Jason Self [this message]
2017-05-24 7:05 ` Nico Rikken
2017-05-24 13:46 ` Adonay Felipe Nogueira
-- strict thread matches above, loose matches on Subject: below --
2017-05-24 14:54 Aspasia Beneti
2017-05-24 16:55 ` Jason Self
2017-05-28 15:03 Aspasia Beneti
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://lists.gnu.org/mailman/listinfo/libreplanet-discuss
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1495596504.4586@jxself.org \
--to=j@jxself.org \
--cc=libreplanet-discuss@libreplanet.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.
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).