From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 35546 invoked by alias); 1 Nov 2019 12:55:19 -0000 Mailing-List: contact libc-alpha-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: libc-alpha-owner@sourceware.org Received: (qmail 35537 invoked by uid 89); 1 Nov 2019 12:55:19 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-6.9 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS,SPF_PASS autolearn=ham version=3.3.1 spammy=HX-Languages-Length:1784, employee, signs, zhang X-HELO: mx1.redhat.com Subject: Re: [PATCH v2 2/2] aarch64: Optimized memcpy and memmove for Kunpeng processor To: Yikun Jiang Cc: "Zhangxuelei (Derek)" , Siddhesh Poyarekar , Szabolcs Nagy , Florian Weimer , DJ Delorie , Wilco Dijkstra , "libc-alpha@sourceware.org" , jiangyikun References: <8DC571DDDE171B4094D3D33E9685917BD9DF9D@DGGEMI529-MBX.china.huawei.com> <5948ff2c-6a65-43ef-f2bd-0ceaa31a9432@redhat.com> From: Carlos O'Donell Message-ID: <94a9fae3-3f89-09c4-7e35-f3ceb0ef791e@redhat.com> Date: Fri, 01 Nov 2019 12:55:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-SW-Source: 2019-11/txt/msg00008.txt.bz2 On 10/30/19 2:42 AM, Yikun Jiang wrote: > Hi, Carlos or someone can reply, : ) Sorry to bother you guys in here. > > And @Craig mentioned the corporate copyright assignment from > copyright-clerk@fsf.org, but no more detail information in follow up. > > Looks like we have two choice: > a. employer disclaimer + individual assignment > b. corporate assignment > > We are employees of Huawei, and we have achieved the company's > approval to contribute the code in GNU Glibc. > > and we have already signed the individual assignment with FSF. (Yikun > Jiang(1435635), Xuelei Zhang(1436346)). Having individual assignments with the FSF is very good. > Could you tell us which the copyright assignment should we use? What > should we do for the next step? You have a choice. The choice you choose depends on what Huawei, as a company, wishes to do. a. Employer disclaimer - The employer signs an agreement with the FSF saying they disclaim the ownership of the work you are doing on glibc. b. corporate assignment - The employer signs an assignment to assign copyright of employee work to the FSF for work done on glibc. They are legally distinct processes, and this decision should be taken, usually, to Huawei's legal representative to decide which is best for the company. You should ask the FSF for copies of both of these documents that need to be signed by your employer, such that you can take them into any kind of meeting you will have internally. Next steps: - Get documents from the FSF. - Have an internal meeting at Huawei with company legal representatives and explain the choices, and get support for one. - Work with the FSF to complete one of the two documents. -- Cheers, Carlos.