public inbox for
 help / color / mirror / Atom feed
From: Jonathan Larmour <>
To: Andrew Lunn <>
Cc: eCos Maintainers <>
Subject: Re: FSF status
Date: Fri, 08 Sep 2006 18:51:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Andrew Lunn wrote:
>>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.
> Are there any other FSF projects which have a commercial company
> associated?  Like Wine/crossover office?

I've looked up that one, and WINE is not assigned to the FSF. I'll try to 
think of some other companies where the main project is assigned to the 
FSF but other bits wouldn't be. I know that Red Hat and Novell/SuSE do 
have a blanket assignment anyway, so not them.

> Could you could find such a
> setup which have already been through this process and use there
> assignemt. Ask the company for a copy of what they used. You would
> then have a strong position to argue from that the FSF accepted this
> exact wording before, so there is no need for the legal people to be
> really involved.....

I've already asked this of the FSF directly in prior correspondence and 
they claimed no-one's ever raised this before.

eCosCentric    The eCos and RedBoot experts
------["The best things in life aren't things."]------      Opinions==mine

  reply	other threads:[~2006-09-08 18:51 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
2006-09-08 17:13   ` Andrew Lunn
2006-09-08 18:51     ` Jonathan Larmour [this message]
  -- 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).