Re: [PATCH v2 2/2] aarch64: Optimized memcpy and memmove for Kunpeng processor

[Carlos O'Donell <carlos@redhat.com>]

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.