Re: License for Slime

--000000000000473363056e765383
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Oops, meant to reply all.

On Tue, Jun 12, 2018, 8:55 AM Red Daly <[email protected]> wrote:

> I got approval to contribute if the new code is in a separate file
> released under MIT (and other OSI-approved licenses). Thanks for the
> suggestion and willingness to do this.
>
> Aside from edits to Makefiles, I am not able to modify files that have
> been released into the public domain. It also sounds problematic or
> impossible to apply a license to code previously released into the public
> domain, so my original post to this thread was naive - apologies.
>
>
> On Mon, May 14, 2018, 8:25 PM Red Daly <[email protected]> wrote:
>
>> 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=C3=ADs Oliveira" <[email protected]> wrote:
>>
>> On Mon, May 14, 2018 at 3:23 PM Stelian Ionescu <[email protected]>
>> wrote:
>> > Maybe you don't necessarily need to change the licence of existing cod=
e.
>> > 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 gues=
s
>> this
>> > should be ok to appease lawyers.
>>
>> I wouldn't have a problem with that. Would it help, Red?
>>
>>
>> --
>> Lu=C3=ADs Oliveira
>> http://kerno.org/~luis/
>>
>>
>>

--000000000000473363056e765383
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Oops, meant to reply all.<br><br><div class=3D"gmail_quote"><div dir=3D"ltr=
">On Tue, Jun 12, 2018, 8:55 AM Red Daly &lt;<a href=3D"mailto:reddaly@gmai=
l.com">[email protected]</a>&gt; wrote:<br></div><blockquote class=3D"gmail=
_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:=
1ex"><div dir=3D"ltr"><div dir=3D"auto"><div>I got approval to contribute i=
f the new code is in a separate file released under MIT (and other OSI-appr=
oved licenses). Thanks for the suggestion and willingness to do this.</div>=
<div dir=3D"auto"><br></div><div dir=3D"auto">Aside from edits to Makefiles=
, I am not able to modify files that have been released into the public dom=
ain. It also sounds problematic or impossible to apply a license to code pr=
eviously released into the public domain, so my original post to this threa=
d was naive - apologies.</div></div></div><div dir=3D"ltr"><div dir=3D"auto=
"><div dir=3D"auto"><br></div><div dir=3D"auto"><br><div class=3D"gmail_quo=
te" dir=3D"auto"><div dir=3D"ltr">On Mon, May 14, 2018, 8:25 PM Red Daly &l=
t;<a href=3D"mailto:[email protected]" rel=3D"noreferrer" target=3D"_blank"=
>[email protected]</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote=
" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><=
div dir=3D"auto"><div>Thanks for the replies. The idea of using a license f=
or new code might indeed help. I now have some questions out to the open so=
urce team here, and I will reply when they get back to me.</div><div dir=3D=
"auto"><br></div><div dir=3D"auto">For some background reading on public do=
main software from OSI, I found this page informative:=C2=A0<a href=3D"http=
s://opensource.org/faq#public-domain" rel=3D"noreferrer noreferrer" target=
=3D"_blank">https://opensource.org/faq#public-domain</a></div><div dir=3D"a=
uto"><div class=3D"gmail_extra" dir=3D"auto"><br><div class=3D"gmail_quote"=
>On May 14, 2018 8:23 AM, &quot;Lu=C3=ADs Oliveira&quot; &lt;<a href=3D"mai=
lto:[email protected]" rel=3D"noreferrer noreferrer noreferrer" target=3D"_=
blank">[email protected]</a>&gt; wrote:<br type=3D"attribution"><blockquote=
 class=3D"m_2090255710715080729m_665633995356474563m_6164925017838189445m_4=
37861944007976639m_-6163266060122283540quote" style=3D"margin:0 0 0 .8ex;bo=
rder-left:1px #ccc solid;padding-left:1ex"><div class=3D"m_2090255710715080=
729m_665633995356474563m_6164925017838189445m_437861944007976639m_-61632660=
60122283540quoted-text">On Mon, May 14, 2018 at 3:23 PM Stelian Ionescu &lt=
;<a href=3D"mailto:[email protected]" rel=3D"noreferrer noreferrer noreferr=
er noreferrer" target=3D"_blank">[email protected]</a>&gt; wrote:<br>
&gt; Maybe you don&#39;t necessarily need to change the licence of existing=
 code.<br>
&gt; Just like with the legacy code from Spice Lisp and CMUCL which was pub=
lic<br>
&gt; domain, it should be enough to state that the licence for new code is =
MIT<br>
and<br>
&gt; over time the code base would become a mixture, just like SBCL. I gues=
s<br>
this<br>
&gt; should be ok to appease lawyers.<br>
<br></div>
I wouldn&#39;t have a problem with that. Would it help, Red?<div class=3D"m=
_2090255710715080729m_665633995356474563m_6164925017838189445m_437861944007=
976639m_-6163266060122283540elided-text"><br>
<br>
-- <br>
Lu=C3=ADs Oliveira<br>
<a href=3D"http://kerno.org/~luis/" rel=3D"noreferrer noreferrer noreferrer=
 noreferrer noreferrer" target=3D"_blank">http://kerno.org/~luis/</a><br>
<br>
</div></blockquote></div><br></div></div></div></blockquote></div></div></d=
iv></div>
</blockquote></div>

--000000000000473363056e765383--