public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Shahid Khan <shahidk@qti.qualcomm.com>
To: Jim Wilson <jimw@sifive.com>, "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Cc: "siddhesh@linaro.org" <siddhesh@linaro.org>
Subject: RE: Copyright assignment form
Date: Tue, 16 Jan 2018 19:55:00 -0000	[thread overview]
Message-ID: <5734863e0bdb4c4391b4668b258db25f@NALASEXR01G.na.qualcomm.com> (raw)
In-Reply-To: <8c3ce9c8-6228-2ed2-9552-08d04c3e1932@sifive.com>

Thanks for the info, Jim. 

Siddhesh,

Is there a separate copyright assignment for glibc or the same form works for both?

-Shahid 

-----Original Message-----
From: Jim Wilson [mailto:jimw@sifive.com] 
Sent: Tuesday, January 16, 2018 1:01 PM
To: Shahid Khan <shahidk@qti.qualcomm.com>; gcc@gcc.gnu.org
Cc: siddhesh@linaro.org
Subject: Re: Copyright assignment form

On 01/15/2018 03:11 PM, Shahid Khan wrote:
> Our team at Qualcomm Datacenter Technologies, Inc. is interested in contributing patches to the upstream GCC compiler project. To get the process started, we'd like to request a copyright assignment form as per contribution guidelines outlined at https://gcc.gnu.org/contribute.html.
> 
> Please let me know if there are additional steps we need to take to become an effective contributor to the GCC community.

You should contact assign@gnu.org directly.  The standard forms contain language about patents that Qualcomm lawyers are unlikely to be comfortable with, and may require negotiating a non-standard agreement. 
As best as I can tell, the FSF has never received a copyright assignment or disclaimer from Qualcomm.  If this is the first time Qualcomm lawyers are talking to the FSF, this will take a while.  I would not be surprised if this takes a year or two.  You will also need a VP level signature for the forms once you get approval from Qualcomm lawyers.

You may want to consider getting a disclaimer from your employer, and then filing personal assignments.  It is probably easier to get a disclaimer from Qualcomm than an assignment, but this requires more paperwork, since each individual contributing then needs their own personal assignment.  The disclaimers also have language about patents that the Qualcomm lawyers may not like, so while this should be easier, it is still likely a difficult process.

Siddhesh can help you with this as the rules for gcc are the same as for glibc.

Jim

  reply	other threads:[~2018-01-16 19:55 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-15 23:11 Shahid Khan
2018-01-16 18:01 ` Jim Wilson
2018-01-16 19:55   ` Shahid Khan [this message]
     [not found]     ` <CAFZeh08oKhZbH=rTs_NG7Cq463PUvj21TOcR692OUBfmqqKJJg@mail.gmail.com>
2018-01-16 20:01       ` Siddhesh Poyarekar
2018-01-16 20:32         ` Jim Wilson
2018-01-16 20:35           ` Siddhesh Poyarekar
2018-01-17 12:22             ` Nathan Sidwell
2018-01-17 12:50               ` Siddhesh Poyarekar
2018-01-16 20:49           ` Joseph Myers
2018-01-16 20:46   ` Joseph Myers
  -- strict thread matches above, loose matches on Subject: below --
2021-04-09 12:32 Copyright Assignment Form Ruihan Li
2021-04-09 15:06 ` David Edelsohn
2021-04-10  2:31   ` Liu Hao
2021-04-10  7:22     ` Jonathan Wakely
2021-04-10 12:04       ` Liu Hao
2021-02-18  4:25 Akshat Agarwal
2021-02-18 14:51 ` David Edelsohn
2020-10-03 13:06 Copyright assignment form Antoni Boucher
2019-05-18  9:42 copyright " David Čepelík
2019-05-20 11:22 ` Martin Jambor
2018-06-01 15:36 Copyright " Andrew Benson
2017-03-04 12:32 Decius Caecilius Metellus
2006-09-02 17:39 Rask Ingemann Lambertsen
2006-08-15 15:58 copyright " Jack Howarth
2001-02-15  8:07 Copyright " Gerald Pfeifer
2001-02-15  7:24 Mike Yang

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=5734863e0bdb4c4391b4668b258db25f@NALASEXR01G.na.qualcomm.com \
    --to=shahidk@qti.qualcomm.com \
    --cc=gcc@gcc.gnu.org \
    --cc=jimw@sifive.com \
    --cc=siddhesh@linaro.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).