public inbox for kawa@sourceware.org
 help / color / mirror / Atom feed
From: spellcard199 <spellcard199@protonmail.com>
To: Per Bothner <per@bothner.com>
Cc: "kawa@sourceware.org" <kawa@sourceware.org>
Subject: Re: Most Kawa-compatible licensing scheme for a new project?
Date: Fri, 31 Jan 2020 16:48:00 -0000	[thread overview]
Message-ID: <VVGUgTz9hUC5vj_DkH5fPYgS38aVlICUHKgpWmpjh4Qzo14tHEMp4KYinVugFIa38HST63HPW5_dqA7pV_1Mm1weXwEfV78-CpdUrjR1zoE=@protonmail.com> (raw)
In-Reply-To: <3df35751-5f1f-c18a-67ec-b1fd1d17f6d0@bothner.com>

Sorry, my bad. I should have read
https://www.gnu.org/software/kawa/Software-License.html
before sending the mail.

Some days ago I read some comment online I can't find anymore which
said Kawa had this double MIT/GPL license where you could pick the MIT
one only if you didn't make any changes to the code and I took it for
good without checking. Now I see those modules are not part of the
standard distribution anymore.

Thank you.

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Friday, January 31, 2020 4:17 PM, Per Bothner <per@bothner.com> wrote:

> On 1/31/20 6:44 AM, spellcard199 wrote:
>
> > Scenario 1:
> >
> > 1.  I distribute my project under the MIT - Expat license
> > 2.  Since I've choosen the MIT license, I can't include code
> >     that I have modified after having copied it from Kawa
> >
>
> Why not?
>
> -----------
>
>     --Per Bothner
>
>
> per@bothner.com http://per.bothner.com/


      reply	other threads:[~2020-01-31 16:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-31 14:44 spellcard199
2020-01-31 15:20 ` Per Bothner
2020-01-31 16:48   ` spellcard199 [this message]

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='VVGUgTz9hUC5vj_DkH5fPYgS38aVlICUHKgpWmpjh4Qzo14tHEMp4KYinVugFIa38HST63HPW5_dqA7pV_1Mm1weXwEfV78-CpdUrjR1zoE=@protonmail.com' \
    --to=spellcard199@protonmail.com \
    --cc=kawa@sourceware.org \
    --cc=per@bothner.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.
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).