From: David Edelsohn <dje.gcc@gmail.com>
To: Antoni Boucher <bouanto@zoho.com>
Cc: gcc@gcc.gnu.org, assign@gnu.org
Subject: Re: Question regarding copyright assignment
Date: Fri, 7 Oct 2022 11:00:25 -0400 [thread overview]
Message-ID: <CAGWvny=uuHVK4JhVQp0HPfq-8CJ4N0HB-C11rz933Hio9iy_jA@mail.gmail.com> (raw)
In-Reply-To: <ce069a2f01d39868b7d0510550de53f2ebd07dca.camel@zoho.com>
[-- Attachment #1: Type: text/plain, Size: 1216 bytes --]
On Thu, Oct 6, 2022 at 8:58 PM Antoni Boucher via Gcc <gcc@gcc.gnu.org>
wrote:
> Hi.
> I contribute to gcc outside of work, but I'm about to sign a new work
> contract which contains a work ownership clause saying that I give the
> ownership to the company of any work not listed in some appendix.
>
> What exactly should I list to make sure my contributions to GCC are not
> affected by this?
> Do I need to do something more than this to make sure there are no
> issues with the FSF copyright assignment?
>
>
We cannot provide legal advice, employment advice or labor advice.
One option is for you to contribute through a copyright assignment by your
company or DCO authorized by your company. Another option is to enumerate
FOSS projects in your employment agreement, if your company and hiring
manager will permit that. The term GCC (GNU Compiler Collection) is
interpreted to include the compiler and all components, including runtime
libraries. You also might consider listing GLIBC, GDB and BINUTILS for
completeness and potential overlap. Those four components are the terms
used for Free Software Foundation copyright assignment forms and in the FSF
file listing copyright assignments.
Thanks, David
next prev parent reply other threads:[~2022-10-07 15:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-07 0:57 Antoni Boucher
2022-10-07 15:00 ` David Edelsohn [this message]
2022-10-07 15:47 ` Craig Topham
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='CAGWvny=uuHVK4JhVQp0HPfq-8CJ4N0HB-C11rz933Hio9iy_jA@mail.gmail.com' \
--to=dje.gcc@gmail.com \
--cc=assign@gnu.org \
--cc=bouanto@zoho.com \
--cc=gcc@gcc.gnu.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).