From: Antoni Boucher <bouanto@zoho.com>
To: gcc@gcc.gnu.org, assign@gnu.org
Subject: Question regarding copyright assignment
Date: Thu, 06 Oct 2022 20:57:23 -0400 [thread overview]
Message-ID: <ce069a2f01d39868b7d0510550de53f2ebd07dca.camel@zoho.com> (raw)
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?
Thanks.
next reply other threads:[~2022-10-07 0:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-07 0:57 Antoni Boucher [this message]
2022-10-07 15:00 ` David Edelsohn
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=ce069a2f01d39868b7d0510550de53f2ebd07dca.camel@zoho.com \
--to=bouanto@zoho.com \
--cc=assign@gnu.org \
--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).