From: Jonathan Larmour <jifl@eCosCentric.com>
To: Jiri Gaisler <jiri@gaisler.com>
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] Are copyright assignments detrimental to eCos?
Date: Sat, 05 Apr 2008 00:44:00 -0000 [thread overview]
Message-ID: <47F6C3C7.5000301@eCosCentric.com> (raw)
In-Reply-To: <200804041650.m34Goakc019397@mail175c2.megamailservers.com>
Jiri Gaisler wrote:
> Alex Schuilenburg wrote:
>
>> 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.
>
>
> What I am saying is that I want everyone to benefit from our contribution,
> *and* from potential derivate work in form of bug fixes. Just like the
> linux kernel.
In this respect it's no different from the linux kernel. Someone can take
the linux kernel, make changes and bug fixes and distribute it. And by
virtue of the GPL the people who get any kernel binaries can get the
source code that goes with it and all is as it should be. That doesn't
mean they have to be posted on the linux-kernel list, nor provided to
Linus for inclusion in the source base, and indeed many are not.
What difference do you think there is?
> Everyone sees the same kernel code, while applications and
> drivers can be proprietary if desired.
And that's what happens with eCosPro - all the source code is supplied,
and the only bits that can't be redistributed freely are some portions we
have written solely ourselves (not derived from public eCos sources) as
extensions and add-ons.
For example we have an entirely new MultiMedia Filesystem. That's an
extension we wrote ourselves, and is no different conceptually from people
writing their own userspace filesystem on Linux (such as with FUSE). Just
like with a FUSE filesystem an extension should be able to be
proprietary[1]. The fact that eCos, unlike Linux, links into a single
kernel image without such a clear kernel boundary isn't important for the
principle of thing - that's the reason for the exception clause with the
GPL which we have.
> It seems to me that insisting on
> FSF copyright transfer blocks this in some way. We are still maintaining
> our own ecos fork (superset), but I would rather see everything merged
> to anoncvs. But I respect the policy of the anoncvs maintainers and
> eCoscentric, so we will keep it as is for them time being.
Obviously you don't have to contribute changes either :-). But I don't
think you need have the worry you seem to have. Anything contributed to
eCos gets owned by the FSF, and put under the eCos GPL+exception license
de facto forever[2]. No-one can change that (except the FSF, and as the
creators of free software they never would). And anyone who makes fixes to
those source files has to keep it with that license and distribute them
under the GPL terms. Just like the Linux kernel.
Does that clear things up?
Jifl (eCosCentric hat)
[1]
<http://fuse.sourceforge.net/wiki/index.php/FAQ#Under_what_conditions_may_I_distribute_a_filesystem_which_uses_libfusex3f.>
[2] Or equivalently anyway - because of single ownership in the FSF, we
can change the license wording if there is a legal need. We couldn't do
that with multiple owners - we'd need everyone's permission.
--
eCosCentric Limited http://www.eCosCentric.com/ The eCos experts
Barnwell House, Barnwell Drive, Cambridge, UK. Tel: +44 1223 245571
Registered in England and Wales: Reg No 4422071.
------["The best things in life aren't things."]------ Opinions==mine
--
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-05 0:14 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] ` <47F642D0.7000907@xylanta.com>
2008-04-04 15:17 ` Andrew Lunn
[not found] ` <47F6450C.4090302@gaisler.com>
2008-04-04 15:17 ` Jiri Gaisler
2008-04-04 16:06 ` Alex Schuilenburg
[not found] ` <47F65C78.5050005@gaisler.com>
2008-04-04 23:18 ` Jiri Gaisler
2008-04-05 0:44 ` Jonathan Larmour [this message]
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
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=47F6C3C7.5000301@eCosCentric.com \
--to=jifl@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).