public inbox for kawa@sourceware.org
 help / color / mirror / Atom feed
From: spellcard199 <spellcard199@protonmail.com>
To: "kawa@sourceware.org" <kawa@sourceware.org>
Subject: Most Kawa-compatible licensing scheme for a new project?
Date: Fri, 31 Jan 2020 14:44:00 -0000	[thread overview]
Message-ID: <YZJvSTucmuzvr_iN5spjvK5kN_PXyHGqRDy2M_uGcPCAe8OokwHuaylYMcL5iEuQGKiwXgyMP3BXKmgfkUCcwElvSrnGua2ieL_zhW6iBFc=@protonmail.com> (raw)

Hello. I'm writing to ask an advice about the licensing scheme for a
new project in which I may include code copied from Kawa and then
modified by me.

I can only imagine 2 scenarios, but I don't know :
- if my understanding about the 2 scenarios is correct
- if there are other choices besides them

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

Scenario 2:
1. I distribute my project under the GPL license
2. Since I have choosen the GPL, I can include in my project
   code that I have taken and modified from Kawa
3. Let's say that someone in the Kawa team at that point wants to
   copy->paste->modify some code from my project into Kawa: since Kawa
   is also MIT licensed, would the fact I used the GPL forbid this?

I'm asking because I'm trying to write a java project to support
interactive development in Kawa (porting my own `geiser-kawa'
from scheme to java atm) and, in the remote case it's decent,
some functions may happen to be reusable in the Kawa Language Server.

So my question is: what's the most Kawa-compatible licensing scheme
that allows both of the following?
- Code from Kawa to be copied->pasted->modified into my project
- Code from my project to be copied->pasted->modified into Kawa

Thank you in advance for the attention.

             reply	other threads:[~2020-01-31 14:44 UTC|newest]

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

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='YZJvSTucmuzvr_iN5spjvK5kN_PXyHGqRDy2M_uGcPCAe8OokwHuaylYMcL5iEuQGKiwXgyMP3BXKmgfkUCcwElvSrnGua2ieL_zhW6iBFc=@protonmail.com' \
    --to=spellcard199@protonmail.com \
    --cc=kawa@sourceware.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).