From: Gary Thomas <gary@mlbassoc.com>
To: Jonathan Larmour <jifl@eCosCentric.com>
Cc: eCos Maintainers <ecos-maintainers@sources.redhat.com>
Subject: Re: Copyright resolution
Date: Fri, 21 Mar 2003 18:56:00 -0000 [thread overview]
Message-ID: <1048273005.4073.1061.camel@hermes.chez-thomas.org> (raw)
In-Reply-To: <3E7A9442.8000607@eCosCentric.com>
On Thu, 2003-03-20 at 21:25, Jonathan Larmour wrote:
> The time has come to bring this to a conclusion. The beta is now out, and
> we want this to be resolved for 2.0 final.
>
> I gave Red Hat repeated reminders and finally a deadline of last week to
> give a response to the mail I had sent (which you've all seen). But there
> was no answer.
>
> At FOSDEM I talked to Martin Michlmayer about SPI and copyright
> assignments and stuff, and from that I found out that despite my very
> explicit statements in almost all my mails, it is almost certain they
> unfortunately didn't quite understand our proposal with licensing
> opt-outs. Martin's view from knowing the individuals on the SPI board (he
> doesn't speak for SPI so this *isn't* a definitive SPI response though) is
> that many of them would be deeply against such license opt-outs.
>
> Add to that that SPI are only now even _considering_ how to deal with
> copyright assignments (although admittedly we were only proposing before
> them delegating the paperwork to us), and that their approach in general,
> while well-intentioned, is unfortunately.... er... amateurish, I don't
> believe any chance of license deals between Red Hat and SPI is plausible.
>
> So as I see it, and from what y'all have already indicated preferences
> for, there are essentially two conclusions:
>
> a) Create our own "eCos Foundation" whether not-for-profit or otherwise,
> and possibly then try to do a deal with Red Hat.;
I'm in favor of this, but it must be seen as vendor neutral, i.e. not
favoring any commercial participant (eCosCentric or MLB or Mind or ...)
> or
> b) Drop the copyright assignment requirement for patches entirely.
>
I see this as a last resort because it basically can turn things into
a free-for-all.
<snip>
> I would like to hear from every maintainer in this thread. Unless we get
> complete consensus, I would suggest thrashing things out here a little,
> and then setting up a phone conference to reach the conclusion.
>
> I won't say what my favoured personal preference is until tomorrow as I
> want to prevent this post appearing biased :-P.
>
By "tomorrow", I assume that you mean Friday, March 21?
I'm ready to discuss this at length whenever y'all are. I note that
it's been 15 hours since Jonathan sent this, and AFAICT this is the
only response so far.
> What I would say is that if Red Hat presented the option of assigning all
> their copyright to a _single_ not-for-profit entity on a plate, I'd go for
> that. But that's safe to say since it isn't an option :-) :-(.
Yup, pretty safe.
--
------------------------------------------------------------
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
------------------------------------------------------------
next prev parent reply other threads:[~2003-03-21 18:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-21 4:27 Jonathan Larmour
2003-03-21 18:56 ` Gary Thomas [this message]
2003-03-21 20:45 ` Jonathan Larmour
2003-03-21 22:28 ` Bart Veer
2003-03-26 15:15 ` Jonathan Larmour
2003-03-28 18:07 ` Nick Garnett
2003-03-25 16:37 ` John Dallaway
2003-03-25 16:41 ` Gary Thomas
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=1048273005.4073.1061.camel@hermes.chez-thomas.org \
--to=gary@mlbassoc.com \
--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).