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

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 
<http://ecos.sourceware.org/patches-assignment.html>. The forms themselves 
are at <http://ecos.sourceware.org/assign.html>

> 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

      reply	other threads:[~2004-08-26 18:52 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   ` Contribution of a DHCP server (µDHCP)port " sebastien Couret
2004-08-26 18:52     ` Jonathan Larmour [this message]

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=412E3176.8020209@eCosCentric.com \
    --to=jifl@ecoscentric.com \
    --cc=ecos-maintainers@ecos.sourceware.org \
    --cc=sebastien.couret@elios-informatique.fr \
    /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).