From: Andrew Lunn <andrew.lunn@ascom.ch>
To: Jonathan Larmour <jifl@jifvik.org>
Cc: eCos Maintainers <ecos-maintainers@sources.redhat.com>
Subject: Re: Future code ownership
Date: Tue, 17 Dec 2002 08:38:00 -0000 [thread overview]
Message-ID: <20021217163838.GB1044@biferten.ma.tech.ascom.ch> (raw)
In-Reply-To: <3DFDF6B7.8090008@jifvik.org>
> 1) No copyright assignments at all. This is like the Linux kernel. The
> admin overhead is reduced, as well as the hassle factor for contributors.
> However the ownership of the code is called into question, and there is a
> risk that code that is contributed may not be the copyright owners - think
> of the corporate disclaimer thing we have. Certainly the FSF are against
> it for these types of reasons, and they are the acknowledged experts in
> this field. Once this decision is made it can never be revoked. Definitely
> no potential licence revenue.
I don't think assignments are that much of a burden on the
contributer, but i would try to ensure its a case of sign it once, it
lasts indefinatly. Having to redo the assignment everytime was APITA.
We know RH had the infrastucture in place to handle these
assignments. What about the other options. Does SPI Inc already have
this infrastructure? Do any of its other projects require such
assignments? How quickly are they processed?
Andrew
next prev parent reply other threads:[~2002-12-17 16:38 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-16 7:52 Jonathan Larmour
2002-12-17 0:44 ` Andrew Lunn
2002-12-17 19:57 ` Jonathan Larmour
2002-12-17 1:09 ` Andrew Lunn
2002-12-17 15:24 ` Bart Veer
2002-12-18 0:40 ` Andrew Lunn
2002-12-19 5:09 ` Jonathan Larmour
2002-12-17 19:54 ` Jonathan Larmour
2002-12-17 20:00 ` Gary Thomas
2002-12-17 1:27 ` Andrew Lunn
2002-12-17 5:47 ` Gary Thomas
2002-12-17 9:16 ` Andrew Lunn
2002-12-17 8:52 ` Gary Thomas
2002-12-17 12:29 ` Jonathan Larmour
2002-12-17 8:29 ` Andrew Lunn
2002-12-17 12:23 ` Jonathan Larmour
2002-12-17 8:38 ` Andrew Lunn [this message]
2002-12-17 12:18 ` Jonathan Larmour
2002-12-17 8:42 ` Andrew Lunn
2002-12-17 8:56 ` Gary Thomas
2002-12-17 12:00 ` Jonathan Larmour
2002-12-19 11:52 Frank Ch. Eigler
2002-12-19 14:39 ` Bart Veer
2002-12-20 14:21 ` Frank Ch. Eigler
2002-12-22 15:21 ` Bart Veer
2002-12-23 7:53 ` Frank Ch. Eigler
2003-01-02 14:55 ` Jonathan Larmour
2003-01-12 2:42 ` Jonathan Larmour
2003-01-22 2:22 ` Jonathan Larmour
[not found] <3E145A86.5050601@eCosCentric.com>
2003-01-02 16:21 ` Frank Ch. Eigler
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=20021217163838.GB1044@biferten.ma.tech.ascom.ch \
--to=andrew.lunn@ascom.ch \
--cc=ecos-maintainers@sources.redhat.com \
--cc=jifl@jifvik.org \
/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).