From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/9720 Path: news.gmane.org!not-for-mail From: Christopher Lane Newsgroups: gmane.linux.lib.musl.general Subject: Re: musl licensing Date: Mon, 21 Mar 2016 15:46:18 -0700 Message-ID: References: <20160316234656.GQ9349@brightrain.aerifal.cx> <20160317081748.GF13856@example.net> <20160317160131.GE21636@brightrain.aerifal.cx> <20160318042158.GN21636@brightrain.aerifal.cx> <20160318191209.GQ21636@brightrain.aerifal.cx> <20160319043547.GS21636@brightrain.aerifal.cx> Reply-To: musl@lists.openwall.com NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=001a113ec52275aa99052e96ddd8 X-Trace: ger.gmane.org 1458600394 31437 80.91.229.3 (21 Mar 2016 22:46:34 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 21 Mar 2016 22:46:34 +0000 (UTC) To: musl@lists.openwall.com Original-X-From: musl-return-9733-gllmg-musl=m.gmane.org@lists.openwall.com Mon Mar 21 23:46:34 2016 Return-path: Envelope-to: gllmg-musl@m.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by plane.gmane.org with smtp (Exim 4.69) (envelope-from ) id 1ai8ao-0005fT-3a for gllmg-musl@m.gmane.org; Mon, 21 Mar 2016 23:46:34 +0100 Original-Received: (qmail 17796 invoked by uid 550); 21 Mar 2016 22:46:31 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-ID: Original-Received: (qmail 17778 invoked from network); 21 Mar 2016 22:46:30 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to; bh=u1LTDhn0q9XpPHohCsGE2FOPYOYKNjC+eex+ParrWX4=; b=HtuoTFGdh1phC9CUbCg4xTMdRFlOwW0/8KDpkNGpNcxTiyk0A/o5pKXNENnRJSCbkm yi7gYNqRGYg5E84jec4cR24iU7qAcBcLRV2bpnkWlwugjeqhHbk/g9UsYrfwb6qWcpd5 NuL/Vr3l9eXAjEJxK4sKxbenb+vG+Q1cqhmlMixX28eMspjqhE9likskkPcvlvqeKeQr Fs3Lt1HlCWm5jZaJwlQtronUpziXLS0BsSqPIF0A277O5bH093MYmup32HrrvQ4QksJ2 JLNTQXX42hCDpGRY00rxgF17TrkzvsMf82f0pPeZT9Ty8qcNRyvrqJCr5QMRGUOxewsf 0oug== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to; bh=u1LTDhn0q9XpPHohCsGE2FOPYOYKNjC+eex+ParrWX4=; b=cUQqnbVvC9fSMQlJUpau6d9fZ9pOamyC++NWrYGgpxWacjbHFUmtMXg2p8IaMR5at0 WxnojFUpmxtam+OfVl8cMo0t90qOfnqkHSxstHcWGVMNk+o6/oVwm62a294ZILEeqs94 EWbA8nGxg1YGp87LVyiB3w+pb/UlaGh2ziIRT3kNRnLLmMC5z7LU7WMM38DUcm8Y+Ldk iIRj9X/o0ZUoaZfcTvczJD0WOcpXH8nTER7Iw05nhpKJaUh9+/2lQ8Vza2fwC45bkrjd txV0TifnN9PhUO4q4HerKcYmrysivPAlCNoTPfnF+ltIfpgDhEps7jGTm4M2PImCSZP9 T/Zw== X-Gm-Message-State: AD7BkJKUg91A1uE6xTlmAqhagQrGV22DvYVSR39WUp0pH8jehdE3BBJnXq3Ip32liPMGdeGRhVC7QoVIorzLPQ== X-Received: by 10.107.137.38 with SMTP id l38mr34239887iod.133.1458600378997; Mon, 21 Mar 2016 15:46:18 -0700 (PDT) In-Reply-To: <20160319043547.GS21636@brightrain.aerifal.cx> Xref: news.gmane.org gmane.linux.lib.musl.general:9720 Archived-At: --001a113ec52275aa99052e96ddd8 Content-Type: text/plain; charset=UTF-8 On Fri, Mar 18, 2016 at 9:35 PM, Rich Felker wrote: > On Fri, Mar 18, 2016 at 07:47:21PM +0000, George Kulakowski wrote: > > I wanted to mention another small thing, which is simply to update the > > names of some files specifically mentioned in COPYRIGHT. I've attached a > > diff. > > Thanks. Applied. > > Rich > Some comments on the proposed COPYRIGHT text... """ The implementation of blowfish crypt (src/misc/crypt_blowfish.c) was originally written by Solar Designer and placed into the public domain. The code also comes with a fallback permissive license for use in jurisdictions that may not recognize the public domain. """ """ The x86_64 port was written by Nicholas J. Kain. Several files (crt) were released into the public domain; others are licensed under the standard MIT license terms at the top of this file. See individual files for their copyright status. """ Those paragraphs still reference public domain. We can't use the things mentioned there. WRT the blowfish impl, there are other implementations we can pull if we want / need that - though I'm not sure we even do want that. The x86_64 crt files can be cleanroom'ed here (and we'd release those BSD0 when we're done). If you want to fix in musl, that works for us too, of course. If it's not feasible to fix upstream, it might be good to even more explicitly note which files exactly are meant to be covered by PD -- in the event they have to be surgically removed, that would help. If the per-file headers are up-to-date, that might be fine. The new text is almost OK. The biggest problem is, you shouldn't comment or speculate on the copyrightability of work inside the license file. Doing so could unintentionally alter or restrict the scope of the license you're attempting to apply. Comments should go in the readme file or another separate file. In the words of one of the lawyers here, "the license file should say X is MIT, Y is BSD, Z is BSD-2, goodbye." Apparently license files are like code written in English (or other human languages) where the compiler is some future, undetermined group of people. It takes the concept of undefined behavior to a new level... --001a113ec52275aa99052e96ddd8 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On F= ri, Mar 18, 2016 at 9:35 PM, Rich Felker <dalias@libc.org> wro= te:
On Fri, Mar 18, 2016 at 07:47:21PM= +0000, George Kulakowski wrote:
> I wanted to mention another small thing, which is simply to update the=
> names of some files specifically mentioned in COPYRIGHT. I've atta= ched a
> diff.

Thanks. Applied.

Rich

Some = comments on the proposed COPYRIGHT text...

"""
The implementatio= n of blowfish crypt (src/misc/crypt_blowfish.c) was
originally written by Solar = Designer and placed into the public
domain. The code also comes with a fallback = permissive license for use
in jurisdictions that may not recognize the public do= main.
"""

"= ""
The x86_64 port was written by Nicholas J. Kain. Several files (crt)
were relea= sed into the public domain; others are licensed under the
standard MIT license= terms at the top of this file. See individual
files for their copyright status.=
"""

=
Those paragraph= s still reference public domain.=C2=A0 We can't use the things mentione= d there.=C2=A0 WRT the blowfish impl, there are other implementations we ca= n pull if we want / need that - though I'm not sure we even do want tha= t.=C2=A0 The x86_64 crt files can be cleanroom'ed here (and we'd re= lease those BSD0 when we're done).=C2=A0 If you want to fix in musl, th= at works for us too, of course.=C2=A0 If it's not feasible to fix upstr= eam, it might be good to even more explicitly note which files exactly are = meant to be covered by PD -- in the event they have to be surgically remove= d, that would help.=C2=A0 If the per-file headers are up-to-date, that migh= t be fine.

The new text is almost = OK.=C2=A0 The biggest problem is, you shouldn't comment or speculate on= the copyrightability of work inside the license file.=C2=A0 Doing so could= unintentionally alter or restrict the scope of the license you're atte= mpting to apply.=C2=A0 Comments should go in the readme file or another sep= arate file.=C2=A0 In the words of one of the lawyers here, "the licens= e file should say X is MIT, Y is BSD, Z is BSD-2, goodbye."

Appar= ently license files are like code written in English (or other human langua= ges) where the compiler is some future, undetermined group of people.=C2=A0= It takes the concept of undefined behavior to a new level...
--001a113ec52275aa99052e96ddd8--