From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31124 invoked by alias); 26 Aug 2004 18:52:47 -0000 Mailing-List: contact ecos-maintainers-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Post: List-Help: , Sender: ecos-maintainers-owner@sources.redhat.com Received: (qmail 31085 invoked from network); 26 Aug 2004 18:52:44 -0000 Message-ID: <412E3176.8020209@eCosCentric.com> Date: Thu, 26 Aug 2004 18:52:00 -0000 From: Jonathan Larmour User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-GB; rv:1.4) Gecko/20030703 X-Accept-Language: en-gb, en, en-us MIME-Version: 1.0 To: sebastien.couret@elios-informatique.fr Cc: ecos-maintainers@ecos.sourceware.org Subject: Re: Contribution of a DHCP server =?ISO-8859-1?Q?=28=B5DHCP=29po?= =?ISO-8859-1?Q?rt_to_eCOS?= References: <412D010D.60603@eCosCentric.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-SW-Source: 2004-08/txt/msg00035.txt.bz2 sebastien Couret wrote: > Hello Jonathan,(and maintainers) > > I'm sorry but i'm not a lawyer and licencing issues are a bit tricky. None of us are, but the maintainers have to be aware of these things (unfortunately!). > As U say "the eCos license, which is GPL plus a special > exception." . if I had well understood this exception is that you can link > your own code with an eCOS library and your own code will stay under your > property. (With GPL, your code also becomes GPL ...) Is that it ? Yes in general with your own code. But with the GPL, there are extra requirements to be fulfilled, and one of those is compatible with the BSD "advertising clause" which I mentioned before. > I have tried to obtain a written agreement of all contributors of µDHCP to > cahnge GPL to the eCOS licence but many emails are now broken and one of them > had strictly refused. > So I think the best thing I could do is to release it under GPL. I think we can expect to have to deal with this type of thing - the important thing is that we don't allow any situation where eCos users use (full) GPL code without realising it. There are some hurdles to overcome to achieve this, which are now being discussed as a result of your situation :-). > I was also unaware of the FreeBSD licensing clause, If I had understood you > have a solution if U can convinced Mr Niels Provos of changing his terms. > Am I right ? That's a definite obstacle. There are a few other files which might be able to be worked around easily, but some might be difficult. Most difficult of all is the time required as net stacks are tricky things :-|. > Could you send me templates of what u call a "copyrigth assignement" and > "copyright disclaimer" ? Sorry, I was probably a little obtuse in my previous mail, but you can read all about copyright assignments, including links to the relevant forms at . The forms themselves are at > I'm the only contributor for the changes needed by the port so I will fill > them in. That's super, and will also cover any future contributions you choose to make (at least until we complete the transfer to the FSF anyway). > Thanks for all your good work. eCos is a community project and contributions drive it. Thanks for your good work too :-). Jifl -- eCosCentric http://www.eCosCentric.com/ The eCos and RedBoot experts --["No sense being pessimistic, it wouldn't work anyway"]-- Opinions==mine