From: Aspasia Beneti <aspra@dyne.org>
To: libreplanet-discuss@libreplanet.org
Cc: j@jxself.org
Subject: Re: Can we licence our Clojure (Eclipse Public License 1.0) project with the GNU AFFERO GENERAL PUBLIC LICENSE?
Date: Sun, 28 May 2017 17:03:47 +0200 [thread overview]
Message-ID: <3095D54A-0532-4F03-914D-0648B4351F14@dyne.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 988 bytes --]
Aspasia Beneti said:
> Not sure who you mean I should contact.
It was a two-fold suggestion.
The first was to participate in the discussion of the next version of the
EPL so as to raise GPL compatibility as a thing that should be addressed in
that new version. There is a mailing list linked to from [0] for the
purposes of discussing the next version of the EPL.
The second was to contact the FSF's Licensing & Compliance Lab via
address@hidden for help in seeing if an exception would be appropriate
and to see if they could help draft one.
Hopefully between these two it'd help solve not just your particular
problem but also everyone else's by trying to get a newer version of the
EPL that's GPL-compatible.
[0] https://mmilinkov.wordpress.com/2013/05/31/community-review-of-the-
eclipse-public-license/
>> Thanks for the advice, I have done both and waiting for more information. I will keep this thread updated when I have some news.
[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next reply other threads:[~2017-05-28 15:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-28 15:03 Aspasia Beneti [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-05-24 14:54 Can we licence our Clojure (Eclipse Public License 1.0) project with the GNU AFFERO GENERAL PUBLIC LICENSE? Aspasia Beneti
2017-05-24 16:55 ` Jason Self
2017-05-23 14:49 Aspasia Beneti
2017-05-24 3:28 ` Jason Self
2017-05-24 7:05 ` Nico Rikken
2017-05-24 13:46 ` Adonay Felipe Nogueira
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=3095D54A-0532-4F03-914D-0648B4351F14@dyne.org \
--to=aspra@dyne.org \
--cc=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).