public inbox for ecos-maintainers@sourceware.org
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: Jonathan Larmour <jifl@eCosCentric.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 20:00:00 -0000	[thread overview]
Message-ID: <1040183990.32279.2394.camel@hermes.chez-thomas.org> (raw)
In-Reply-To: <3DFFF152.7030107@eCosCentric.com>

On Tue, 2002-12-17 at 20:53, Jonathan Larmour wrote:
> Andrew Lunn wrote:
> >>3) A commercial entity interested in picking up the eCos "banner", such as 
> >>eCosCentric.
> > 
> > Does this mean eCosCentric is actually willing to do this?
> 
> Only willing if that's what the maintainers want. I'm wearing a very 
> different hat in eCosCentric and as a maintainer. I want to do what's best 
> for eCos, even if it conflicts with what eCosCentric wants. To be honest, 
> I don't think it's very likely we'll choose this option - I just threw it 
> in there for completeness, but tell me if I'm wrong!
> 
> > Has Mind been approached? What is their opinion on this. 
> 
> Dunno. Gary might have the best take on that if they don't speak up 
> themselves.

I can only talk loosely - I don't speak for Mind, but I know
their feelings.

Mind would prefer that copyright ownership be as non-commercial
as possible.  Since eCosCentric (as well as Red Hat) are competitors
of Mind, having the copyright be in eCosCentric's name could be
considered counter to such a goal.  A central body, such as SPI,
would be ideal.

-- 
------------------------------------------------------------
Gary Thomas                 |
MLB Associates              |  Consulting for the
+1 (970) 229-1963           |    Embedded world
http://www.mlbassoc.com/    |
email: <gary@mlbassoc.com>  |
gpg: http://www.chez-thomas.org/gary/gpg_key.asc
------------------------------------------------------------

  reply	other threads:[~2002-12-18  4: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 [this message]
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
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=1040183990.32279.2394.camel@hermes.chez-thomas.org \
    --to=gary@mlbassoc.com \
    --cc=andrew.lunn@ascom.ch \
    --cc=ecos-maintainers@sources.redhat.com \
    --cc=jifl@eCosCentric.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).