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

On Tue, 2002-12-17 at 02:26, Andrew Lunn wrote:
> > 6) Software in the Public Interest, Inc. is a US not-for-profit 
> > organisation. <http://www.spi-inc.org/> Its goals are to advance open 
> > source. They are well known already as the copyright holders of many well 
> > known projects like Debian Linux, GNOME, LSB as well as owners of the Open 
> > Source marque, and so on. They are trusted.  We have already taken the 
> > step of asking them in principle if they could accept eCos as a project, 
> > even with our funky licensing proposal outlined above. And as you can see 
> > from 
> > <http://www.spi-inc.org/corporate/resolutions/resolution-2002-10-08.mgs> 
> > this was accepted.
> > 
> > Personally I favour this option. I think it is best for eCos as an Open 
> > Source project, and I would like to hope even Red Hat would be able to 
> > support it, as it would be in the long-term best interests of eCos. 
> > Besides if the licensing proposal does pay off, they would profit!
> 
> Has the opinion of RH been sought on this? 
> 
> To me, this does seem like the best option.
> 

Frankly, Red Hat's opinion should not matter.  They're the ones
that caused all this ruckus in the first place.

As for me, I think this is the best solution.  My main reason
for putting my copyright in files I touch (which I believe matches 
those who followed me) was to preclude Red Hat from simply taking
work that I and others had done and selling it to the highest
bidder.  [n.b. of course the can still try to do this, but I'm
sure that some lawyer somewhere will stop them]  I would have
no problem assigning any new work I contribute to a third party
since this would have the same effect.

As Andrew has asked, how would we actually make such a change?
We can't change Red Hat's copyright notices without their consent.
Or can we get away with just assigning any new work to the SPI?

-- 
------------------------------------------------------------
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-17 13:47 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 [this message]
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=1040132847.22212.1460.camel@hermes.chez-thomas.org \
    --to=gary@mlbassoc.com \
    --cc=andrew.lunn@ascom.ch \
    --cc=ecos-maintainers@sources.redhat.com \
    --cc=jifl@jifvik.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).