License for Slime

Red Daly reddaly at gmail.com
Tue May 15 00:25:14 UTC 2018


Thanks for the replies. The idea of using a license for new code might
indeed help. I now have some questions out to the open source team here,
and I will reply when they get back to me.

For some background reading on public domain software from OSI, I found
this page informative: https://opensource.org/faq#public-domain

On May 14, 2018 8:23 AM, "Luís Oliveira" <luismbo at gmail.com> wrote:

On Mon, May 14, 2018 at 3:23 PM Stelian Ionescu <sionescu at cddr.org> wrote:
> Maybe you don't necessarily need to change the licence of existing code.
> Just like with the legacy code from Spice Lisp and CMUCL which was public
> domain, it should be enough to state that the licence for new code is MIT
and
> over time the code base would become a mixture, just like SBCL. I guess
this
> should be ok to appease lawyers.

I wouldn't have a problem with that. Would it help, Red?


-- 
Luís Oliveira
http://kerno.org/~luis/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.common-lisp.net/pipermail/slime-devel/attachments/20180514/837d68e2/attachment.html>


More information about the slime-devel mailing list