From: Alex Schuilenburg <alexs@ecoscentric.com>
To: Jiri Gaisler <jiri@gaisler.com>
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] Are copyright assignments detrimental to eCos?
Date: Fri, 04 Apr 2008 16:06:00 -0000 [thread overview]
Message-ID: <47F64F89.9080809@ecoscentric.com> (raw)
In-Reply-To: <200804041510.m34FAdfE025938@mail175c2.megamailservers.com>
Jiri Gaisler wrote on 2008-04-04 16:11:
>
>
> Andrew Lunn wrote:
>
>>>>> I have looked at the files in eCos Pro, and majority of it has
>>>>> the GPL license with the linking exception. Is there anything that
>>>>> would prevent me from merging updated files from eCos Pro back
>>>>> to the open CVS version?
>>>> AFAICS, no, given that you legally received your copy of eCos Pro.
>>> eCoscentric provides a free eCos Pro kit for the Nios processor,
>>> which anyone can download. This would mean that all GPL files in
>>> the kit are free to be merged with the open CVS. Or is there some
>>> other catch ...?
>>
>> The catch is that in order for it to be included into anoncvs, the
>> owner of the code has to agree and transfer the copyright to FSF. So i
>> cannot just pick up eCosCentric code and commit it. eCosCentric have
>> to agree to it as copyright owner.
>
> So if I contribute code to the anoncvs, I assign the copyright to FSF.
> If eCoscentric includes the code into eCos Pro, it will still bear the
> FSF copyright. If they then make a bug fix, any licensee of eCos Pro
> should be able to submit the fix into anoncvs, since the copyright
> is still with FSF and the code is still GPL. Have I got this right?
> Or do I need to assign the copyright to eCoscentric before it is
> included in the eCos Pro distribution?
No. You would need to assign the code to the FSF. We (eCosCentric) are
no longer accepting contributions. The FSF are now the keepers of the
eCos copyright and to whom we assign any of our eCos contributions, just
like the rest of the eCos community.
As for submitting fixes from eCosPro to anoncvs, copyrightable fixes can
only be submitted by the copyright holder, which we do from time to time.
>
>
> What I am trying to avoid is a fork of a potential contribution,
> with one version in anoncvs and some other version in eCos Pro.
As Andrew says, anyone can fork the code. It is GPL code after all. The
only condition is they have to adhere to the license.
Anyway, forking is not in our interest, never mind the community's. We
want the benefits that contributions to eCos bring, as does everyone
else. eCosPro is not a fork, it is a superset of eCos. See
http://www.ecoscentric.com/ecos/ecospro.shtml
What you seem to be suggesting is that you want everyone else *but*
eCosCentric to benefit from your potential contribution.
>
> Jiri.
>
-- Alex Schuilenburg
Managing Director/CEO eCosCentric Limited
Tel: +44 1223 245571 Barnwell House, Barnwell Drive
Fax: +44 1223 248712 Cambridge, CB5 8UU, UK
www.ecoscentric.com Reg in England and Wales, Reg No 4422071
** Visit us at ESC Silicon Valley <http://www.embedded.com/esc/sv> **
** April 15-17 2008, Booth 3012, San Jose Convention Center **
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next prev parent reply other threads:[~2008-04-04 15:56 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-28 2:59 Øyvind Harboe
2008-04-02 19:01 ` Jonathan Larmour
2008-04-03 9:38 ` Markus Schaber
[not found] ` <47F4A57F.1080501@gaisler.com>
2008-04-03 11:14 ` Jiri Gaisler
2008-04-03 18:49 ` Alexander Neundorf
[not found] ` <47F55A47.7070602@gaisler.com>
2008-04-03 22:40 ` Jiri Gaisler
2008-04-04 4:11 ` Alexander Neundorf
2008-04-04 9:02 ` Markus Schaber
[not found] ` <47F5F130.2030800@gaisler.com>
2008-04-04 9:36 ` Jiri Gaisler
[not found] ` <20080404114231.7efcf59a@kingfisher.sec.intern.logix-tt.com>
[not found] ` <47F5FC4A.2080401@gaisler.com>
2008-04-04 10:50 ` Jiri Gaisler
2008-04-04 15:33 ` Alex Schuilenburg
2008-04-04 16:09 ` Markus Schaber
2008-04-04 16:13 ` Markus Schaber
2008-04-04 16:25 ` Andrew Lunn
2008-04-04 16:26 ` Markus Schaber
2008-04-04 14:58 ` Andrew Lunn
[not found] ` <47F6450C.4090302@gaisler.com>
2008-04-04 15:17 ` Jiri Gaisler
2008-04-04 16:06 ` Alex Schuilenburg [this message]
[not found] ` <47F65C78.5050005@gaisler.com>
2008-04-04 23:18 ` Jiri Gaisler
2008-04-05 0:44 ` Jonathan Larmour
2008-04-07 12:18 ` Alex Schuilenburg
[not found] ` <47FA1CE4.8090708@gaisler.com>
2008-04-07 13:17 ` Jiri Gaisler
2008-04-07 13:28 ` Gary Thomas
[not found] ` <47FA2438.4090904@gaisler.com>
2008-04-07 13:44 ` Jiri Gaisler
2008-04-07 15:51 ` Gregg Levine
2008-04-04 15:45 ` Andrew Lunn
[not found] ` <47F642D0.7000907@xylanta.com>
2008-04-04 15:17 ` Andrew Lunn
2008-04-04 15:20 ` Andy Jackson
2008-04-04 16:47 ` Markus Schaber
2008-04-07 8:00 ` Gary Thomas
2008-04-04 10:00 ` Chris Zimman
2008-04-04 15:09 ` Andrew Lunn
2008-04-04 15:46 ` Chris Zimman
2008-04-03 18:46 ` Bart Veer
2008-04-03 19:01 ` Alexander Neundorf
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=47F64F89.9080809@ecoscentric.com \
--to=alexs@ecoscentric.com \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=jiri@gaisler.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).