public inbox for ecos-maintainers@sourceware.org
 help / color / mirror / Atom feed
From: Jonathan Larmour <jifl@eCosCentric.com>
To: Gary Thomas <gary@mlbassoc.com>
Cc: Andrew Lunn <andrew.lunn@ascom.ch>,
	eCos Maintainers <ecos-maintainers@sources.redhat.com>
Subject: Re: Future code ownership
Date: Tue, 17 Dec 2002 12:00:00 -0000	[thread overview]
Message-ID: <3DFF8251.4030606@eCosCentric.com> (raw)
In-Reply-To: <1040144188.22212.1692.camel@hermes.chez-thomas.org>

Gary Thomas wrote:
> On Tue, 2002-12-17 at 09:42, Andrew Lunn wrote:
> 
>>>5) A new not-for-profit organisation, e.g. "the eCos foundation". There is 
>>>considerable difficulty for non-USers to set this up, and the process can 
>>>take upwards of 6 months I believe. There may also be tedious obligations 
>>>and overhead like accounts, board meetings, blah blah. Plus without any 
>>>experience we may need lawyers, and therefore fees, etc. as well as any 
>>>other charges for setting it up.
>>
>>What about the English equivalent? I guess that means getting Charity
>>status. Have you look at this option? I guess it still needs lawyers
>>etc.
> 
> Yes, Jonathan looked into this at length.  It did not seem to be
> a very workable (hardly possible) solution.

Indeed, the summary was that it was a) very unlikely that an open source 
project could be considered a sufficiently good work for the purposes of 
being designated a charity, and b) out of the question for any money from 
licence revenue to be used in the way we'd want it.

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

  reply	other threads:[~2002-12-17 20:00 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
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 [this message]
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=3DFF8251.4030606@eCosCentric.com \
    --to=jifl@ecoscentric.com \
    --cc=andrew.lunn@ascom.ch \
    --cc=ecos-maintainers@sources.redhat.com \
    --cc=gary@mlbassoc.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).