public inbox for ecos-maintainers@sourceware.org
 help / color / mirror / Atom feed
From: "Frank Ch. Eigler" <fche@redhat.com>
To: Jonathan Larmour <jifl@eCosCentric.com>
Cc: ecos-maintainers@sources.redhat.com
Subject: Re: Future code ownership
Date: Thu, 02 Jan 2003 16:21:00 -0000	[thread overview]
Message-ID: <20030102112140.B3571@redhat.com> (raw)
In-Reply-To: <3E145A86.5050601@eCosCentric.com>; from jifl@eCosCentric.com on Thu, Jan 02, 2003 at 03:28:06PM +0000

[-- Attachment #1: Type: text/plain, Size: 1275 bytes --]

Hi -


jifl wrote:

> > I'm still being misunderstood.  My point is that you might find a way
> > to go *without* formal copyright assignments to a central organization,
> > and still be relatively safe from corporate copyrights.
> 
> "relatively"? It's the "relatively" that's the problem. I agree that 99% 
> of the time there's no problem. It's the magnitude of the problems that 
> the 1% cause that give us reason to hesitate.

Right.


> > Yes, whatever [the FSF has] makes sense to them for their assignment-based
> > scheme, and there has been little "competition" to discourage excessive
> > barriers to contribution.
> 
> But it's their legal advisors that say it's not excessive to use an 
> assignment-based scheme! It's the only way to be legally sure about
> ownership. [...]

But that begs the question.  Just because the FSF uses such relatively
bulletproof documentation requirements (company officers' signatures
for assignments) does not mean that this is the only way.  (Even the
FSF has a slightly different copyright-disclaim mechanism.)  Anyway,
Another lawyer may give advice more in line with my intuition, and
that would render FSF's approach excessive.  IOW, You might want to
get your own legal opinion.


- FChE

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

       reply	other threads:[~2003-01-02 16:21 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3E145A86.5050601@eCosCentric.com>
2003-01-02 16:21 ` Frank Ch. Eigler [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
  -- 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=20030102112140.B3571@redhat.com \
    --to=fche@redhat.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).