From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/9613 Path: news.gmane.org!not-for-mail From: Petr Hosek Newsgroups: gmane.linux.lib.musl.general Subject: musl licensing Date: Tue, 15 Mar 2016 14:59:24 -0700 Message-ID: Reply-To: musl@lists.openwall.com NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 X-Trace: ger.gmane.org 1458079223 8288 80.91.229.3 (15 Mar 2016 22:00:23 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 15 Mar 2016 22:00:23 +0000 (UTC) Cc: kulakowski@chromium.org To: musl@lists.openwall.com Original-X-From: musl-return-9626-gllmg-musl=m.gmane.org@lists.openwall.com Tue Mar 15 23:00:22 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 1afx0n-00021A-Ah for gllmg-musl@m.gmane.org; Tue, 15 Mar 2016 23:00:21 +0100 Original-Received: (qmail 26384 invoked by uid 550); 15 Mar 2016 22:00:17 -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 26259 invoked from network); 15 Mar 2016 21:59:36 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:sender:date:message-id:subject:from:to:cc; bh=pUtIdDRtvr4HZTElC8a3aQ6rqfNZIxCkBV/p9SBBLlE=; b=YONglRDol6kyoUrIb3Ad4n1Y9v/w3pB2v4hAL//lq+wr9f9psOZd71F33CQwFNZ0Fh kXXKgX7zjg+ae7Yk3gxxgoIhJmomukorxeoNktt2mo2qj0IrebRvRd/CmVQ49K0J3Mtm AoidkZgkE/Ghq0zTwGOXpPtjBwSKkLmYIAc2uNROYRzRCvlUj7RmlAENsBvEOpagtV8v eAk8gACcx3lQNO/fYv5gXuciH42bi/zEpI44nVTpIOxFpuralStDlqprKKFOJ+toyc60 f3Y5ah7gCMrGNe4KoJKTnJfWlH3ChzY97oAJpLdIBMlRlz6Oq7TuJELTmcRhWG+OPI4E RvFg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=mime-version:sender:date:message-id:subject:from:to:cc; bh=pUtIdDRtvr4HZTElC8a3aQ6rqfNZIxCkBV/p9SBBLlE=; b=ZU7/TriaLGYfZAc1VTqW7Eie975KJ3ATLFWWWftR69YZYoVCwexTetOUcw1luKGVZW owz0vSBtgHddjRrvpgBUB/4JhaC9FwxYKxsbM5ATteS0nTa6WHPepGxfn3JnHYoSa2fr cTmocbqZ3BlfkUtTnmbYR/UQ/3FBMy2IPDbkA= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:date:message-id:subject:from :to:cc; bh=pUtIdDRtvr4HZTElC8a3aQ6rqfNZIxCkBV/p9SBBLlE=; b=DC+ASFsHuV7a+j9QXs5vu13sJVH38bZDPxlQKQeEaGzYcVLzEl3jqKQS5YhEsJZToz tQ98MfParIeZy8+lVTZ0YYH6FFL0S2YqxIskUMNx8V9lNwXR6qJIlS0tEmpppr3S0yJE vqTqsDlI5HoI5AjzoSyTvNZYi5JP8KslzJcyxSTAeq2uZOiHwXmpGT8q/qZ5UZ+zoLqE khWH+U2pVsB/d2PPqUn7COE8yvRUjxxeuZZEVV1/75RyjUJ5q5YxMIYUUO9dySajS8bB 6VFirEl33nvvNN8os+Lw5YYWqMpJR13J3y57DUVcu9Qjh6wL8ANfGhPEPdtmwIJLJaNj IuSQ== X-Gm-Message-State: AD7BkJKo967ZsgWjL4wKVBnuDULh7/3SMZkigRcu6Z9b0UGZvwtKEIo8PFRcMZTgGIbEmldYl9F6j6+VOdFb6+9y X-Received: by 10.55.212.130 with SMTP id s2mr523563qks.74.1458079164984; Tue, 15 Mar 2016 14:59:24 -0700 (PDT) Original-Sender: phosek@google.com X-Google-Sender-Auth: OSV_Xj1UHgiA2d6d7BZkbJ7Z3IM Xref: news.gmane.org gmane.linux.lib.musl.general:9613 Archived-At: We work on Chromium project at Google. Our team, as well as several other teams here at Google, would like to start using musl in various open-source projects. This includes shipping musl as a part of SDKs and toolchains. However, after performing a standard license review, our open-source lawyers told us that there are two obstacles to us being able to use musl. The first issue is the lack of clarity around per-file licensing and copyright attribution. The other issue is the claim that some files (in particular, the public headers and C runtime) are in the public domain. While this might be technically correct, it's not legally sound and we would be legally unable to use these files without them being placed under copyright and an open source license. The most appropriate way of addressing both issues would be to include a copyright notice in individual source and header files. Rather than working around these issues by reimplementing parts of musl, we would like to work with the musl community to directly address these issues. We believe that our company's interpretation of the copyright and authorship is the same across the entire industry and resolving these issues would benefit both musl as well as projects which already do or plan to use musl. To address both issues, authors of all files in musl that are "public domain" or any other non-license will have to agree with relicensing their work under the MIT license (or any other compatible open-source license). Furthermore, all past and future contributors will have to to sign the Contributor License Agreement (CLA). Since the majority of musl authors are present in this forum, we're reaching out to you to ask whether this is something you would agree with and also to start the discussion within the wider musl community.