Kernel contributions from organisations and individual privacy

[riel@surriel.com (Rik van Riel)]

On 06/11/2015 01:10 AM, Chris Packham wrote:
> It's not a concern for the _employer_ (unless we say something
> particularly inflammatory), in fact the organisation sees the benefit
> of the company name getting out there in technical circles.
> 
> It's more a case of the _employee_ not wanting their name to show up
> in mailing list archives, similar to people that don't want a phone
> book listing or twitter/facebook/google+. One option is for someone
> (like me) to do the submission and work with upstream to get the
> change accepted, I don't have a problem with this but it does mean
> that if/when I move on I take the kudos (as well as the criticism)
> with me and the company loses out.

One thing the employees who want to stay anonymous can do
is grant the company copyright on the code (if their
employment agreement doesn't do that already).

Then another employee, who does not mind participating
upstream, can submit the code, with the company name as
copyright on new files added, and their own name in the
Signed-off-by: line of the patches.

At least, I believe this should work...

-- 
All rights reversed.