From: Jonathan Larmour <jifl@eCosCentric.com>
To: Alex Schuilenburg <alexs@ecoscentric.com>
Cc: Andrew Lunn <andrew@lunn.ch>,
eCos Maintainers <ecos-maintainers@ecos.sourceware.org>
Subject: Re: [ECOS] Re: eCosCentric copyright hold in headers
Date: Thu, 08 Apr 2004 14:02:00 -0000 [thread overview]
Message-ID: <40755B58.30905@eCosCentric.com> (raw)
In-Reply-To: <407556D4.8080407@ecoscentric.com>
[ Moved to maintainers list ]
Alex Schuilenburg wrote:
> Andrew Lunn wrote:
>
> [...]
>
>>> Yep. It should all get blasted away when the FSF assignment happens
>>> (don't ask).
>>
>>
>> Which is my i asked. We should keep track of this just in case...
>
>
> and for the benefit of all...
>
> When I asked them face-to-face last week at ESCW, Red Hat were unable to
> provide a date when the actual assignment to the FSF would happen.
> Apparently everything has passed through legal and it is now a matter of
> waiting for their engineer to become available to actually make the
> assignment and header changes.
>
> We could offer to do the changes for them but would need legal-sign off
> from someone in Red Hat for all the files that would have their
> copyright changed. If we are going to help make this happen, I suggest
> we provide Red Hat with a list of all the eCos files for which they hold
> copyright and have them approve the list (in writing). We can then make
> the copyright changes and assignments to the FSF (including eCosCentric
> and other maintainer held copyrights) in one go, which would make a lot
> of sense.
I'd have hoped we wouldn't have to be responsible for that. While we could
search for the copyright banner in files, I can't guarantee every file
contains a Red Hat copyright that should have (even from the days when
we^H^HRed Hat were working on eCos). And for the files without a Red Hat
copyright banner, it would need careful identification to work out whether
they are Red Hat's or someone elses (or indeed are mostly someone elses but
may contain portions of RH code thus making it a derived work). The
consequences of us making a mistake with the identification is painful; but
if Red Hat makes the mistake it's nowhere near as bad and I believe intent
does matter a lot in these circumstances.
It would be much much nicer if Red Hat could arrange some sort of blanket
assignment, perhaps just by reference to the contents of the entire eCos
CVS repository at ecos.sourceware.org. Or perhaps just list every
repository file, irrespective of copyright and finetune the wording of the
assignment so that it assigns any right and title that _may_ belong to Red
Hat in the listed files. I'm no lawyer though. I'd be more than willing to
talk to them about ways it could be done though..... if they'll talk to me!
Jifl
--
eCosCentric http://www.eCosCentric.com/ The eCos and RedBoot experts
--["No sense being pessimistic, it wouldn't work anyway"]-- Opinions==mine
next parent reply other threads:[~2004-04-08 14:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040408101602.GJ29940@lunn.ch>
[not found] ` <4075305D.8020101@eCosCentric.com>
[not found] ` <20040408111939.GK29940@lunn.ch>
[not found] ` <407556D4.8080407@ecoscentric.com>
2004-04-08 14:02 ` Jonathan Larmour [this message]
2004-04-08 14:20 ` Andrew Lunn
2004-04-08 14:54 ` Jonathan Larmour
2004-04-08 15:21 ` Andrew Lunn
2004-04-08 15:27 ` Jonathan Larmour
2004-04-08 14:49 ` Alex Schuilenburg
2004-04-08 15:40 ` Jonathan Larmour
2004-04-08 16:31 ` Alex Schuilenburg
2004-05-07 17:11 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=40755B58.30905@eCosCentric.com \
--to=jifl@ecoscentric.com \
--cc=alexs@ecoscentric.com \
--cc=andrew@lunn.ch \
--cc=ecos-maintainers@ecos.sourceware.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).