This is the mail archive of the
ecos-discuss@sourceware.org
mailing list for the eCos project.
eCos license documentation in final products
- From: John K <johnk_dev at yahoo dot com>
- To: ECos Discussion <ecos-discuss at sourceware dot org>
- Date: Tue, 21 Jul 2015 09:50:16 -0700
- Subject: eCos license documentation in final products
- Authentication-results: sourceware.org; auth=none
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!
John
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss