From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1124 invoked by alias); 7 Sep 2013 13:40:03 -0000 Mailing-List: contact ecos-maintainers-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: ecos-maintainers-owner@ecos.sourceware.org Received: (qmail 1107 invoked by uid 89); 7 Sep 2013 13:40:02 -0000 Received: from p02c12o142.mxlogic.net (HELO p02c12o142.mxlogic.net) (208.65.145.75) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-SHA encrypted) ESMTPS; Sat, 07 Sep 2013 13:40:02 +0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.3 required=5.0 tests=AWL,BAYES_50,KHOP_THREADED,RDNS_NONE autolearn=no version=3.3.2 X-HELO: p02c12o142.mxlogic.net Received: from unknown [12.218.215.72] (EHLO smtpauth1.linear.com) by p02c12o142.mxlogic.net(mxl_mta-7.1.0-4) with ESMTP id fac2b225.0.49783.00-345.92627.p02c12o142.mxlogic.net (envelope-from ); Sat, 07 Sep 2013 07:40:01 -0600 (MDT) X-MXL-Hash: 522b2cb17efd7c4b-66723d985407124a3ded6cd89f3fddcc9d998da3 Received: from [192.168.0.221] (174-24-1-174.clsp.qwest.net [174.24.1.174]) by smtpauth1.linear.com (Postfix) with ESMTPSA id 58F62740A3; Sat, 7 Sep 2013 06:39:58 -0700 (PDT) Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\)) Subject: Re: Copyright and maintainability question for new ARM Cortex A9 HAL From: Michael Jones In-Reply-To: <522A97B3.4060607@eCosCentric.com> Date: Sat, 07 Sep 2013 13:40:00 -0000 Cc: ecos-maintainers@ecos.sourceware.org Content-Transfer-Encoding: quoted-printable Message-Id: References: <77A01081-8A89-4D60-B7B1-78D774946EC6@linear.com> <522A97B3.4060607@eCosCentric.com> To: Jonathan Larmour X-AnalysisOut: [v=2.0 cv=S/xuNvQP c=1 sm=1 a=glloKNylpeYNumXQcclYyA==:17 a] X-AnalysisOut: [=ZxzQOBPtP98A:10 a=D2_GN2MmYMYA:10 a=BLceEmwcHowA:10 a=8nJ] X-AnalysisOut: [EP1OIZ-IA:10 a=MqDINYqSAAAA:8 a=L753ub2bAIUA:10 a=4ifyanK4] X-AnalysisOut: [AAAA:8 a=mDV3o1hIAAAA:8 a=iOsiBahpst8OAzLjHVkA:9 a=wPNLvfG] X-AnalysisOut: [TeEIA:10 a=HSwB7ZUirYEA:10 a=DNQHCi6i0jEA:10 a=jDjqO0XcD2V] X-AnalysisOut: [1Z7bK:21 a=z6nTMFpQYh7SDrd5:21] X-Spam: [F=0.2000000000; CM=0.500; S=0.200(2010122901)] X-MAIL-FROM: X-SW-Source: 2013-09/txt/msg00002.txt.bz2 Jonathan, The files have the following copyright. They do not refer to any license. I find the second redistribution clause a nuisance. It means if you make an= app or library and distribute, you have to reproduce the copyright notice.= Just how do you do that with an end application? Mike /* * Copyright (c) 2013, Freescale Semiconductor, Inc. * All rights reserved. * * Redistribution and use in source and binary forms, with or without modif= ication, * are permitted provided that the following conditions are met: * * o Redistributions of source code must retain the above copyright notice,= this list * of conditions and the following disclaimer. * * o Redistributions in binary form must reproduce the above copyright noti= ce, this * list of conditions and the following disclaimer in the documentation a= nd/or * other materials provided with the distribution. * * o Neither the name of Freescale Semiconductor, Inc. nor the names of its * contributors may be used to endorse or promote products derived from t= his * software without specific prior written permission. * * THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS = IS" AND * ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IM= PLIED * WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE * DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LI= ABLE FOR * ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL D= AMAGES * (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVI= CES; * LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED = AND ON * ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT * (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF= THIS * SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. */ On Sep 6, 2013, at 9:04 PM, Jonathan Larmour wrote: > On 05/09/13 04:52, Michael Jones wrote: >>=20 >> The status is: >>=20 >> - Project not registered yet >=20 > That's not an issue. Projects don't need to be registered. >=20 >> - Uses Freescale SDK macros >> - Uses Freescale SDK code for MMU, GIC, etc >=20 > Okay, the most important thing we need to know is the license for that > Freescale SDK. Is it Free (with a capital F) - in other words, it can be > distributed and redistributed freely by anyone in a way acceptable to the= Free > Software Foundation (FSF)? That means really, is it one of the licenses h= ere: > http://www.gnu.org/licenses/license-list.html#GPLCompatibleLicenses >=20 > If it is one of those licenses, that will probably mean it's okay (unless= the > GPL exception clause in the eCos license causes some conflict). Furthermo= re, > we can directly incorporate any files you use directly into the port, avo= iding > any problems with users having to build with an SDK which lives elsewhere. >=20 >=20 >> Before I register, I want to have a strategy in place to deal with >> Freescale code. Do I replace all the Freescale code line by line until >> nothing is left, >=20 > Assuming it needs to be replaced... >=20 > Replacing it line by line is risky. Copyright is about ideas, not just who > typed it in. If you use the same, or a sufficiently similar, API or desig= n to > theirs, it risks infringing the copyright. Not only must it not be the AP= I, it > must not be able to be considered to have been derived from the API. >=20 > In some cases, people have gone to the extent of "clean room" implementat= ions > to avoid this sort of thing, but I don't think that's likely to be needed= . But > really what's wanted is to effectively do what you would have done if the > Freescale SDK APIs hadn't been there. For some stuff, it can't really be = done > any other way *anyway*, which is fine. For example, an interrupt controll= er > mask macro - there's probably only one particular way to do it. Although = if, > for example, you named the function, and any local variables, exactly the= same > way, that might be a problem. Hopefully replacement isn't relevant though. >=20 >> or see if Freescale will assign copyright? >=20 > That would certainly be easiest, however I don't think they're going to w= ant > to assign copyright for their whole SDK! There can only be one owner of t= he > code, and it would mean it was no longer Freescale. So that really won't = fly. > However, I think in this case we can have confidence that Freescale are t= he > owners of the code, and have the rights to redistribute; that's something= we > have to be more cautious about with other contributors. >=20 > Jifl >=20 > --=20 > eCosCentric Limited http://www.eCosCentric.com/ The eCos experts > Barnwell House, Barnwell Drive, Cambridge, UK. Tel: +44 1223 245571 > Registered in England and Wales: Reg No 4422071. > ------["Si fractum non sit, noli id reficere"]------ Opinions=3D=3D= mine