public inbox for ecos-maintainers@sourceware.org
 help / color / mirror / Atom feed
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 15:40:00 -0000	[thread overview]
Message-ID: <40757276.5050305@eCosCentric.com> (raw)
In-Reply-To: <407566E2.3010608@ecoscentric.com>

Alex Schuilenburg wrote:
> Jonathan Larmour wrote:
> 
> [...]
> 
>>> 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.
> 
> 
> Hmmm, this is of concern. I thought all of eCos could be attributed to 
> either Red Hat, eCosCentric or one of the maintainers.  Are you saying 
> that there are files that are not copyright one of the above?

No, I mean there are files which don't explicitly have a banner saying who 
owns the copyright, so it makes it difficult to use the copyright banners 
as a method of determining fully which files Red Hat needs to assign.

> If there are files that do not have a copyright banner from their owner 
> (Red Hat or otherwise), then would you also not have to get consent from 
> the owners also on the assignment to the FSF.

Maybe, but it becomes silly if the sole point of the exercise is that it 
all ends up as Copyright FSF and nothing else. Since we know that all the 
copyright is held by RH, eCosCentric and the maintainers it's naff if 
things have to be held up to work out some bureaucratic list; hence my 
suggested possibly viable alternatives.

>> 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!
> 
> 
> IMHO this is not going to happen unless somebody outside Red Hat drives 
> this.  I suggest getting a draft together for all maintainers, Red Hat 
> and eCosCentric representatives to sign that simply states that they 
> assign copyright to all the files for which they may hold copyright in 
> the ecos CVS repository to the FSF.

As soon as the FSF starts replying to my mails! There's still the issue of 
the publically stated "guarantee" we wanted from them not to immediately 
strip away the GPL exception. It looked like we were very close to agreeing 
this - it just all went very silent that's all. Right now I know that the 
FSF is not accepting assignments for eCos. Any agreement will have to be 
reviewed by either or both of the RH and FSF legal counsels I'm sure, and 
probably constructed by one of them.

> Come to think of it, my previous suggestion of listing the files is not 
> a good idea as there is no guarantee that the list will not change while 
> we are waiting for signature.  You will have to freeze contribs while 
> waiting for signatures which will be could be forever in the case of Red 
> Hat.
> 
> We could approach Red Hat with a formal written offer to do this so that 
> the assignment to the FSF which they announced can actually take place. 
>  If you want help from me, let me know.

It's more a question of getting a dialogue with anyone. I'm sure whatever 
the issues are we can work them out; but if we can't even start discussing 
them we're no further on.

I wonder, in all seriousness, if we (or some of us) chipped in to a 
donation to the FSF so we can say "Talk to us and we'll give you a 
donation.". I wouldn't have thought it would be too difficult to rustle up 
$150 or so given the current exchange rate. Maybe eCosCentric would like to 
chip in too :). I'm willing to contribute personally anyway, just to give 
myself some peace from this palaver!

Jifl
-- 
eCosCentric    http://www.eCosCentric.com/    The eCos and RedBoot experts
--["No sense being pessimistic, it wouldn't work anyway"]-- Opinions==mine

  reply	other threads:[~2004-04-08 15:40 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
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 [this message]
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=40757276.5050305@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).