From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received-SPF: None (no SPF record) identity=mailfrom; client-ip=83.163.83.176; helo=sibelius.xs4all.nl; envelope-from=mark.kettenis@sibelius.xs4all.nl; receiver=edk2-devel@lists.01.org Received: from sibelius.xs4all.nl (sibelius.xs4all.nl [83.163.83.176]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id 54746211944A4 for ; Fri, 7 Dec 2018 02:51:46 -0800 (PST) Received: from localhost (bloch.sibelius.xs4all.nl [local]) by bloch.sibelius.xs4all.nl (OpenSMTPD) with ESMTPA id 5b3b73e8; Fri, 7 Dec 2018 11:51:44 +0100 (CET) Date: Fri, 7 Dec 2018 11:51:44 +0100 (CET) From: Mark Kettenis To: "Kinney\, Michael D" CC: edk2-devel@lists.01.org, michael.d.kinney@intel.com In-reply-to: (michael.d.kinney@intel.com) References: Message-ID: <9e5ccf6ec56240c2@bloch.sibelius.xs4all.nl> Subject: Re: [RFC] Change EDK II to an Apache 2.0 License X-BeenThere: edk2-devel@lists.01.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: EDK II Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Dec 2018 10:51:47 -0000 > From: "Kinney, Michael D" > Date: Thu, 29 Nov 2018 18:39:28 +0000 As an OpenBSD developer I feel I have to point out that the OpenBSD project considers Apache 2.0 to be a *restrictive* license. http://www.openbsd.org/policy.html We (currently) don't include EDK II code in the OpenBSD OS itself, but do support ARM boards that boot using EDK II-based firmware that has to be included on the same boot media as the OS. So to license change would restrict us (the OpenBSD prject) and potentially others from distributing working boot media for such boards under a "no strings attached" license. Personally, I also think clause 4b of the Apache 2.0 license is too problematic for truly open source software. Adding the required notice for every change that is made is obviously unworkable as I've never seen such notices in modified Apache 2.0 codebases... All-in-all, from my point of view replacing a simple, easy to understand, permissive license with a more complicated legal document that imposes additional restrictions would be a step backwards. No doubt Intel's lawyers have a different opinion. Cheers, Mark Kettenis > Hello, > > This RFC follows up on the proposal from Mark Doran to change the > EDK II Project to an Apache 2.0 License. > > https://lists.01.org/pipermail/edk2-devel/2018-October/030385.html > > > ** Please provide feedback on the proposal by Friday 12/7/18. ** > > I will be following up with pointers to public GitHub branches that > contain the initial set of changes in steps (1) and (2) below for > review. > > The proposal is to perform this change to edk2/master in the steps listed > below. The license change will not be applied to any of the other existing > branches in the edk2 repository. > > 1) Change all files with a BSD 2-Clause license and only a single > copyright statement by Intel Corporation to an Apache 2.0 license > and add an SPDX-License-Identifier statement. > > ====================================================================== > SPDX-License-Identifier: Apache-2.0 > > Licensed under the Apache License, Version 2.0 (the "License"); > you may not use this file except in compliance with the License. > You may obtain a copy of the License at > > http://www.apache.org/licenses/LICENSE-2.0 > > Unless required by applicable law or agreed to in writing, software > distributed under the License is distributed on an "AS IS" BASIS, > WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. > See the License for the specific language governing permissions and > limitations under the License. > ====================================================================== > > 2) Update Readme.md and License.txt in the root of the edk2 repository to > state that content is covered by a mix of BSD 2-Clause and Apache 2.0 > licenses. > > 3) Update all documentation to state that content submitted under the > Apache 2.0 license no longer requires the Tianocore Contribution > Agreement which means the following line is not required in commit > messages for changes to files that are covered by an Apache 2.0 License. > > Contributed-under: TianoCore Contribution Agreement 1.1 > > 4) Create Wiki page(s) that provide the details of the Apache 2.0 License > change and provide the status of the license change for each package > in the edk2 repository. Also provide a list of the additional copyright > holders that need to be contacted to accept the change to an Apache 2.0 > License along with the status of that acceptance. > > 5) After all copyright holders have accepted the change to an Apache 2.0 > License, change the remaining files from BSD 2-Clause to Apache 2.0. > > 6) Update Readme.md and License.txt in the edk2 repository to state that > Apache 2.0 is the preferred license for the EDK II project. > > Best regards, > > Mike > _______________________________________________ > edk2-devel mailing list > edk2-devel@lists.01.org > https://lists.01.org/mailman/listinfo/edk2-devel >