public inbox for ecos-maintainers@sourceware.org
 help / color / mirror / Atom feed
From: "Frank Ch. Eigler" <fche@redhat.com>
To: ecos-maintainers@sources.redhat.com
Subject: Re: Future code ownership
Date: Thu, 19 Dec 2002 11:52:00 -0000	[thread overview]
Message-ID: <20021219145229.A15709@redhat.com> (raw)

Hi -


Speaking merely as an interested individual sympathetic outsider, I
wonder if jifl correctly understands SPI's relationship to other
projects it is associated with:

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

A quick cursory browse of a bunch of pieces of the gnome distribution
shows copyright notices from all sorts of players, FSF, Red Hat, and
many individuals.  I didn't actually see any SPI copyright notices.

There were a few listed drawbacks of a mixed-copyright future for
eCos.  Maybe they are not too serious:

The problem of lack of single copyright enforcement agent would not be
diminished if some of the new code was assigned to SPI or somesuch,
for there would still be Red Hat (C) code in there.  (Or is one of the
ideas to get Red Hat to reassign to SPI too?)

The problem of uncertainty about the trustworthiness of contributors to
submit code unimpeded by corporate copyright is not going to go away in
any case.  You might try requiring submitters to specify the appropriate
copyright notice for the new code, in effect making it their onus to
determine/state corporate impact.  You could then take it at face value.

The problem of shipping relicensed (non-GPL) eCos derivatives is probably
moot unless Red Hat Officials Of Great Highness see it fit to come to
an agreement with you guys.  (I clearly have no clue about this.)  If
no such agreement occurs, then license revenue matters become moot.
(... or you could rewrite all that existing code! :-)


- FChE

             reply	other threads:[~2002-12-19 19:52 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-19 11:52 Frank Ch. Eigler [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
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

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=20021219145229.A15709@redhat.com \
    --to=fche@redhat.com \
    --cc=ecos-maintainers@sources.redhat.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).