public inbox for ecos-maintainers@sourceware.org
 help / color / mirror / Atom feed
From: sebastien Couret <sebastien.couret@elios-informatique.fr>
To: Jonathan Larmour <jifl@eCosCentric.com>
Cc: ecos-maintainers@ecos.sourceware.org
Subject: Re: Contribution of a DHCP server (µDHCP)port to eCOS
Date: Thu, 26 Aug 2004 14:40:00 -0000	[thread overview]
Message-ID: <MELELIOSTzmKYTgetZ3000000fb@melelios.dmz.elios-informatique.fr> (raw)
In-Reply-To: <412D010D.60603@eCosCentric.com>

Hello Jonathan,(and maintainers)

I'm sorry but i'm not a lawyer and licencing issues are a bit tricky.

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 ?

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 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 ?

Could you send me templates of what u call a "copyrigth assignement" and 
"copyright disclaimer"  ?
I'm the only contributor for the changes needed by the port so I will fill 
them in. 

Thanks for all your good work.

  parent reply	other threads:[~2004-08-26 14:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-25 13:20 Contribution of a DHCP server (µDHCP) port " sebastien Couret
2004-08-25 21:13 ` Jonathan Larmour
2004-08-25 22:23   ` Bart Veer
2004-08-26  0:20     ` Jonathan Larmour
2004-08-26 13:47       ` Bart Veer
2004-08-30  7:58     ` Andrew Lunn
2004-08-31 15:38     ` John Dallaway
2004-08-26 14:40   ` sebastien Couret [this message]
2004-08-26 18:52     ` Contribution of a DHCP server (µDHCP)port " Jonathan Larmour

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=MELELIOSTzmKYTgetZ3000000fb@melelios.dmz.elios-informatique.fr \
    --to=sebastien.couret@elios-informatique.fr \
    --cc=ecos-maintainers@ecos.sourceware.org \
    --cc=jifl@eCosCentric.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).