From: Jonathan Larmour <jifl@eCosCentric.com>
To: Andrew Lunn <andrew.lunn@ascom.ch>
Cc: eCos Maintainers <ecos-maintainers@sources.redhat.com>
Subject: Re: Future code ownership
Date: Tue, 17 Dec 2002 19:57:00 -0000 [thread overview]
Message-ID: <3DFFF206.5040606@eCosCentric.com> (raw)
In-Reply-To: <20021217084251.GI350@biferten.ma.tech.ascom.ch>
Andrew Lunn wrote:
>>Note: I have no intention of forcing people with an existing Red Hat
>>assignment to change. That's up to them, and I don't think it makes
>>significant difference since Red Hat's copyright on a lot of the code is
>>here to stay. However, I think it is in the best interests of the Open
>>Source project for any significant contributions to be "moved" to the new
>>system, and certainly this would become the requirement for new assignments.
>
>
> How does this 'move' work in practice? Do we change the copywrite
> headers on the source or does it keep the modified GPL?
We change the assignment proforma and tell people to use the new
assignment forms. We maintainers would probably switch to the new
assignment immediately (probably by informing Red Hat the previous
assignment is now cancelled), but as I said, I don't want to force anyone
with an existing Red Hat assignment to sign a new one if they don't want
to. Anyone with an existing RH assignment can and should be allowed to
continue contributing on that basis if they want, with their code then
becoming (C) Red Hat.
> Can existing code, which i contributed in the past, like say the DNS &
> FTP client etc, be moved?
Only if it wasn't already assigned to Red Hat. So in those specific cases, no.
Jifl
--
eCosCentric http://www.eCosCentric.com/ <info@eCosCentric.com>
--[ "You can complain because roses have thorns, or you ]--
--[ can rejoice because thorns have roses." -Lincoln ]-- Opinions==mine
next prev parent reply other threads:[~2002-12-18 3:57 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 [this message]
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
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=3DFFF206.5040606@eCosCentric.com \
--to=jifl@ecoscentric.com \
--cc=andrew.lunn@ascom.ch \
--cc=ecos-maintainers@sources.redhat.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).