From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2584 invoked by alias); 3 Sep 2015 13:50:34 -0000 Mailing-List: contact ecos-discuss-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: ecos-discuss-owner@ecos.sourceware.org Received: (qmail 2561 invoked by uid 89); 3 Sep 2015 13:50:33 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-0.4 required=5.0 tests=AWL,BAYES_50,SPF_PASS,T_RP_MATCHES_RCVD autolearn=ham version=3.3.2 X-HELO: mail.ecoscentric.com Received: from albus.ecoscentric.com (HELO mail.ecoscentric.com) (212.13.207.200) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-GCM-SHA384 encrypted) ESMTPS; Thu, 03 Sep 2015 13:50:31 +0000 Received: from localhost (localhost [127.0.0.1]) by mail.ecoscentric.com (Postfix) with ESMTP id 6A450A8ACF1 for ; Thu, 3 Sep 2015 14:50:28 +0100 (BST) Received: from mail.ecoscentric.com ([127.0.0.1]) by localhost (albus.ecoscentric.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id E1C8R3gJBOpv; Thu, 3 Sep 2015 14:50:12 +0100 (BST) DKIM-Filter: OpenDKIM Filter v2.10.3 mail.ecoscentric.com 29323A8AC7B To: ecos-discuss@ecos.sourceware.org References: <1437497416.88153.YahooMailBasic@web141604.mail.bf1.yahoo.com> From: Alex Schuilenburg Message-ID: <55E85012.9080406@ecoscentric.com> Date: Thu, 03 Sep 2015 13:50:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0 MIME-Version: 1.0 In-Reply-To: <1437497416.88153.YahooMailBasic@web141604.mail.bf1.yahoo.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Subject: Re: [ECOS] eCos license documentation in final products X-SW-Source: 2015-09/txt/msg00001.txt.bz2 On 21/07/15 17:50, John K wrote: > Greetings, > > I've been spending the better part of this morning reading about the eCos license and GPL trying to figure out what I need to mention in the documentation for my final product. > > For example, suppose I'm making a consumer grade coffee pot that runs eCos. What text do I need to include in the documentation mentioning the use of eCos? Obviously a customer of a coffee pot could care less about what operating system is making their coffee. > > Second example, suppose I make a WiFi module that runs eCos. Think of it as a wireless NIC that can be embedded in an IOT device. Then a company who makes window blinds buys my module so their customers can wirelessly control the window blinds. What do I need to provide to the company who is buying my module? Note that they are using my module as a finished "product" - they have no idea or no concern about the OS it's using. Similarly, what would they have to provide to their customers? Note that the end customer is essentially 2 steps removed from the OS - they could care less about which wireless module is embedded in the blinds let alone the OS. > > Thanks in advance for the clarification! Since I have not seen a response on the list from any of the maintainers, we have a section on our website which includes a license compliance guide for eCos. See http://www.ecoscentric.com/licensing/license-compliance-guide.shtml HTH -- Alex -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss