Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sourceware.org
Subject: Re: OT: copyright issues (was: Re: D Symbol Demangling)
Date: Thu, 20 Apr 2006 17:05:00 -0000	[thread overview]
Message-ID: <20060420170450.GJ11710@nevyn.them.org> (raw)
In-Reply-To: <20060420163934.GB20059@radix50.net>

On Thu, Apr 20, 2006 at 06:39:34PM +0200, Baurzhan Ismagulov wrote:
> Great! Just to clarify: A and B are employed by a Company and the
> employer has all rights on code they produce. A has an assignment and
> contributes code to FSF. This code is also included in a closed-source
> product, distributed by the Company in binary-only form. B makes a patch
> to the code and wants to propagate it into the FSF copy. B doesn't have
> an assignment. IIUC, the above says this patch can't be accepted (I
> understand "authorship" as personal, not corporate), even though it's
> the Company who had donated code. Does this mean that, in order to have
> the patch included, B (and only B, not anyone else from the Company) has
> to sign a copyright assignment?

We're now a bit off topic for gdb-patches; you're in a whole different
kettle of fish here, once corporate assignments are involved.  It
depends on the nature of the company's copyright assignment.  If the
company has filed disclaimers for an individual's work, then (A) they'd
need to have disclaimers for both individuals, and (B) both individuals
would need copyright assignment.  If the company has a corporate
blanket assignment, different rules apply.  You should really talk to
assign@gnu.org if you have any concerns.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2006-04-20 17:05 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-19 11:18 D Symbol Demangling Thomas Kuehne
2006-04-20 13:20 ` Daniel Jacobowitz
2006-04-20 15:20   ` OT: copyright issues (was: Re: D Symbol Demangling) Baurzhan Ismagulov
2006-04-20 15:40     ` DJ Delorie
2006-04-20 15:46       ` Daniel Jacobowitz
2006-04-20 16:39         ` Baurzhan Ismagulov
2006-04-20 17:05           ` Daniel Jacobowitz [this message]
2006-04-20 17:11             ` Baurzhan Ismagulov
2006-04-21 21:25   ` D Symbol Demangling Thomas Kühne
2006-04-22 22:52     ` Thomas Kühne
2006-04-24 17:21       ` Jim Blandy
2006-04-24 20:53         ` Daniel Jacobowitz
2006-04-25  3:35           ` Eli Zaretskii
2006-04-25 14:13             ` DJ Delorie
2006-04-29  7:23               ` Thomas Kühne
2006-04-29 16:47                 ` DJ Delorie

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=20060420170450.GJ11710@nevyn.them.org \
    --to=drow@false.org \
    --cc=gdb-patches@sourceware.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