public inbox for ecos-devel@sourceware.org
 help / color / mirror / Atom feed
From: Ilija Kocho <ilijak@siva.com.mk>
To: John Dallaway <john@dallaway.org.uk>
Cc: Uwe Kindler <uwe_kindler@web.de>,
	 eCos development list <ecos-devel@sourceware.org>
Subject: Re: eCos Driver for open source CANopen stack CanFestival
Date: Fri, 31 May 2013 08:06:00 -0000	[thread overview]
Message-ID: <51A859DE.9090108@siva.com.mk> (raw)
In-Reply-To: <51A8547A.3010907@dallaway.org.uk>

On 31.05.2013 09:42, John Dallaway wrote:
> Hi Uwe
>
> On 23/05/13 08:23, Uwe Kindler wrote:
>
>> we are currently in the process of creating an eCos driver for the open
>> source CANopen stack CanFestival.
>>
>> http://www.canfestival.org/
>> http://dev.automforge.net/CanFestival-3/
>>
>> This driver is based on the eCos CAN framework of the public eCos
>> repositories.
>> We thought about integrating CanFestival as an eCos package like lwIP or
>> uSTL but we are not shure if the license of the CanFestival stack
>> (LGPLv2) is suitable for this plan. What is your opinion? Or should we
>> contact the CanFestival maintainers and ask if they would accept an
>> additional license (the eCos license).
> A port pf CanFestival to eCos would be great, but the eCos maintainers
> would prefer to avoid LGPL in the eCos repository.
>
> I took a brief look at the CanFestival sources. Copyright appears to be
> held by three individuals at present. Perhaps you could ask them if they
> would accept an additional license. The eCos license would be ideal, but
> we can also accept BSD-licensed code from "certain trusted sources". If
> an additional license is not possible, please get back to us and we can
> think again.

LGPL and eCos Licence are practically same regarding modification of
contributed source and derivative works, but there's an essential
difference with regard to proprietary code.
Having in mind sameness of LGPL and eCos licences regarding the
contributed source, I hope that eCos licence will be accepted by
CanFestival authors.
Regarding proprietary code, in most cases embedded system application,
LGPL requires  availability of object code that, I'm afraid, would not
be acceptable for most of producers of embedded systems. I wouldn't put
LGPL code in eCos repository, there are other options such as eCos modules.

Ilija

      reply	other threads:[~2013-05-31  8:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-23  7:24 Uwe Kindler
2013-05-31  7:43 ` John Dallaway
2013-05-31  8:06   ` Ilija Kocho [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=51A859DE.9090108@siva.com.mk \
    --to=ilijak@siva.com.mk \
    --cc=ecos-devel@sourceware.org \
    --cc=john@dallaway.org.uk \
    --cc=uwe_kindler@web.de \
    /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).