From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [216.205.24.124]) by sourceware.org (Postfix) with ESMTP id 732923892454 for ; Thu, 11 Mar 2021 14:29:13 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 732923892454 Received: from mail-qk1-f199.google.com (mail-qk1-f199.google.com [209.85.222.199]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-383-Pa6ZOPQlNFKwhU-K1Hsqcw-1; Thu, 11 Mar 2021 09:29:09 -0500 X-MC-Unique: Pa6ZOPQlNFKwhU-K1Hsqcw-1 Received: by mail-qk1-f199.google.com with SMTP id m68so15622900qkd.5 for ; Thu, 11 Mar 2021 06:29:09 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-language:content-transfer-encoding; bh=hreyANgDTEqUlU7NblLudO6EWTRx+z909wlanpKbS2g=; b=IKFbLVBDDMJl9gh0OlnzaRwJjzGIVtJj5/SVQWPV79flJNzG0lg/sMCs6GvWMchbDw elF5gQUk2GFWwoiyT+JgFpMeS/qCep0k40mdin0ceAJO1EW2r7AB7wlLmXD13BUW/5hz KaBY/mr4kgqFm+LbS4Vlaqx7EV0aPYaaY/BLNfwdRu/1jrXugAM9Ep/QbClEKzlgEOsH BnHta/xSqqvZM9SOc+IMNDDUVDVv1tou47UDDcHe/W6T4qIAiSdsvmb/biWy4dMpmZUz ghQsagK2hua7Ycz2N1apHcohhWGyMlECMsXxj6errtC37zAFOel5i/52P3SoHiLH9i/A rTlA== X-Gm-Message-State: AOAM532X5Y/CCSIOwg0uR6PlCZQGhDmVB2aFZdETrUOU3hUP64o581SB ma+Jm/8fQ23P/soRNdq7E+galCG82aNnw0JZsYiUZ6Jro5eQHmcPjcJU/XQ7PJrNVtaUBq/+qrQ nk0mZMFL7/7ImUemIkTRR3fssk9TtFthrZ0upR1If1peKzJv2bZ8w6p5AbrOvf9TmGdPX X-Received: by 2002:aed:2983:: with SMTP id o3mr5569907qtd.149.1615472948512; Thu, 11 Mar 2021 06:29:08 -0800 (PST) X-Google-Smtp-Source: ABdhPJw1V3i5W1k8rv1v0q+VQo6TFddp5Rlk9rEVzNlyFdzFw4BjWJSg1XdsWq1qmILecgIbXgemvw== X-Received: by 2002:aed:2983:: with SMTP id o3mr5569891qtd.149.1615472948280; Thu, 11 Mar 2021 06:29:08 -0800 (PST) Received: from [192.168.1.16] (198-84-214-74.cpe.teksavvy.com. [198.84.214.74]) by smtp.gmail.com with ESMTPSA id a19sm2043060qkl.126.2021.03.11.06.29.07 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 11 Mar 2021 06:29:07 -0800 (PST) Subject: Re: Need personal copyrigt assignment to contribute glibc? To: Florian Weimer , yunqiang.su@cipunited.com Cc: libc-help@sourceware.org References: <003901d71620$6d2eff00$478cfd00$@cipunited.com> <87tupinkch.fsf@oldenburg.str.redhat.com> From: Carlos O'Donell Organization: Red Hat Message-ID: <53ce54a6-2606-9bd7-e1ea-1c9463ccb477@redhat.com> Date: Thu, 11 Mar 2021 09:29:06 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0 MIME-Version: 1.0 In-Reply-To: <87tupinkch.fsf@oldenburg.str.redhat.com> X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-5.6 required=5.0 tests=BAYES_00, DKIMWL_WL_HIGH, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, KAM_SHORT, NICE_REPLY_A, RCVD_IN_DNSWL_LOW, RCVD_IN_MSPIKE_H3, RCVD_IN_MSPIKE_WL, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: libc-help@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Libc-help mailing list List-Unsubscribe: , List-Archive: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Mar 2021 14:29:14 -0000 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. > > > > 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.