From: Carlos O'Donell <carlos@redhat.com>
To: Florian Weimer <fweimer@redhat.com>, yunqiang.su@cipunited.com
Cc: libc-help@sourceware.org
Subject: Re: Need personal copyrigt assignment to contribute glibc?
Date: Thu, 11 Mar 2021 09:29:06 -0500 [thread overview]
Message-ID: <53ce54a6-2606-9bd7-e1ea-1c9463ccb477@redhat.com> (raw)
In-Reply-To: <87tupinkch.fsf@oldenburg.str.redhat.com>
On 3/11/21 3:52 AM, Florian Weimer via Libc-help wrote:
> * yunqiang su:
>
>> https://sourceware.org/glibc/wiki/Contribution%20checklist
>>
>> The Free Software Foundation (holder of the glibc copyrights) requires
>> copyright assignment for all legally significant changes by a particular
>> author (read not a company). This webpage describes the copyright assignment
>> requirements.
>>
>> So, does it mean that I need to sign a personal copyright assignment even my
>> employer has one for all FSF projects?
>
> The glibc project does not require dual assignments. Assignment from
> the actual copyright holder is sufficient for our purposes. FSF policy
> might differ from that, but you'll have to talk to the FSF to figure
> out. The GNU project says this:
>
> | If the employer does claim the work was part of the person’s job, and
> | there is no clear basis to say that claim is invalid, then we have to
> | consider it valid. Then the person cannot assign copyright, but the
> | employer can. Many companies have done this. Please ask the
> | appropriate managers to contact assign@gnu.org.
>
> <https://www.gnu.org/prep/maintain/html_node/Copyright-Papers.html>
>
> I don't think this requires dual assignment, either. In fact, it even
> argues against it.
>
>> If I want to continue to contribute glibc, which one should I chose?
>> request-disclaim.changes, request-assign.changes, request-assign.future.
>
> request-assign.future is what we recommend.
>
> (I should point out that I'm not an glibc steward/GNU maintainer.)
Florian's answers are correct, and I am a GNU Maintainer for glibc.
Please see the contribution checklist:
https://sourceware.org/glibc/wiki/Contribution%20checklist
If you have any questions please don't hesitate to reach out to me.
--
Cheers,
Carlos.
prev parent reply other threads:[~2021-03-11 14:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-11 2:44 yunqiang.su
2021-03-11 8:52 ` Florian Weimer
2021-03-11 14:29 ` Carlos O'Donell [this message]
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=53ce54a6-2606-9bd7-e1ea-1c9463ccb477@redhat.com \
--to=carlos@redhat.com \
--cc=fweimer@redhat.com \
--cc=libc-help@sourceware.org \
--cc=yunqiang.su@cipunited.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).