From: Jonathan Larmour <jifl@eCosCentric.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: eCos Maintainers <ecos-maintainers@ecos.sourceware.org>
Subject: Re: FSF status
Date: Fri, 08 Sep 2006 17:03:00 -0000 [thread overview]
Message-ID: <4501A25C.8010704@eCosCentric.com> (raw)
In-Reply-To: <20060908091947.GE25338@lunn.ch>
Andrew Lunn wrote:
> Hi Jifl
>
> Hows it going with FSF?
>
> Are you still trying to get the eCosCentric copyright assignment
> sorted out?
Yes it is still waiting on them, allegedly their legal department. The
"copyright clerk" Jonas Jacobson replied to me not that long ago seeming
to forget much of the thousands of words I have already written to him
(much at his own request) and almost bringing things back to square one.
He says there are "issues" but then doesn't say what they are. I'm not
convinced FSF legal have looked at this at all yet. In my view, I have a
clear and minor change suggested to their standard copyright assignment
wording, and there has not been any problem mentioned with it, other than
the fact it isn't the boiler plate copyright assignment.
All in all, I'm moving past "disappointed" to "irritated" in how they're
dealing with this. Were it not for eCosCentric's public undertaking to get
this stuff assigned, I'd have thrown in the towel on this ages ago.
The only reason we can't use their standard assignment template is that it
assigns all code in "eCos" which is something eCosCentric cannot be
expected to do as eCosCentric develops extensions to eCos which are not to
be assigned. You would have thought this would be a simple concept, and
one the FSF would have already had to deal with, but it appears not.
I reckon there would be some surprised people out there if they found out
that if you assign to the FSF, you assign all code you ever write
associated with that project, even code you didn't intend to contribute
and haven't even told them about.
Given that this issue is straightforward and there's nothing secret about
it, I don't mind forwarding my past correspondence to any maintainer who
wants it, but I wouldn't want to bore (or irritate) anyone with it unless
you do.
Anyway, I have been back and forward, and my last missive to them was
2006-08-25, to which I am still awaiting a response.
Jifl
--
eCosCentric http://www.eCosCentric.com/ The eCos and RedBoot experts
------["The best things in life aren't things."]------ Opinions==mine
next prev parent reply other threads:[~2006-09-08 17:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-08 9:19 Andrew Lunn
2006-09-08 17:03 ` Jonathan Larmour [this message]
2006-09-08 17:13 ` Andrew Lunn
2006-09-08 18:51 ` Jonathan Larmour
-- strict thread matches above, loose matches on Subject: below --
2005-05-04 14:38 Gary Thomas
2005-05-04 15:03 ` Jonathan Larmour
2005-05-06 12:33 ` Mark Salter
2003-10-15 13:37 Gary Thomas
2003-10-15 14:01 ` Jonathan Larmour
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=4501A25C.8010704@eCosCentric.com \
--to=jifl@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).