From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754042AbdKILTK (ORCPT ); Thu, 9 Nov 2017 06:19:10 -0500 Received: from mail-lf0-f67.google.com ([209.85.215.67]:54371 "EHLO mail-lf0-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753839AbdKILTJ (ORCPT ); Thu, 9 Nov 2017 06:19:09 -0500 X-Google-Smtp-Source: ABhQp+QTHzlE3kz1nddvXTFQJCvNVsUrwfn6l03jFyjaLThyjTa+3ScoGwlg3OwqR1j7RHJWxyUosA== Subject: Re: Legal question: Author, Sign-off, Company Copyright and gmail To: Greg Kroah-Hartman Cc: Linus Torvalds , Linux Kernel Mailing List References: <084f9151-523e-a212-bf27-d4a4c23878e4@linaro.org> <20171109104403.GA21222@kroah.com> From: Daniel Lezcano Message-ID: <9c8b7edb-5bd6-99d3-bc8f-148fc26f7bae@linaro.org> Date: Thu, 9 Nov 2017 12:19:04 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 MIME-Version: 1.0 In-Reply-To: <20171109104403.GA21222@kroah.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 09/11/2017 11:44, Greg Kroah-Hartman wrote: > On Thu, Nov 09, 2017 at 10:45:27AM +0100, Daniel Lezcano wrote: >> >> Hi all, >> >> I noticed a practice when the patches are submitted where I'm a bit >> confused about how it fits with the DCO. >> >> People are creating gmail accounts to send patches on behalf of their >> company because the company's email configuration does not allow to send >> patches or adds extra infos, or whatever... >> >> That ends up with patches submitted by a gmail account with no history >> and verifiable origin and new files containing a company copyright [1]. > > If there is a question, just ask. > >> At the first glance I would say, it is not allowed, and if a company is >> willing to do opensource, it should provide the tools to its employees >> to do so. But I don't want block patch submission if this practice is >> tolerated. > > Fixing the use of a company's email server is outside of almost all > Linux kernel divisions. As one such example, Red Hat has a system that > messes with patches :) > > I only know of one company that uses Exchange that has "fixed it" enough > to allow their developers to send patches out that are not corrupted > (and no, it's not Microsoft). Preventing all of those companies, or > those that use Lotus Notes, or any other horrid email system, from > contributing to kernel development is not a good idea. > >> What is the policy in this case ? > > I just ask all new contributors who they work for, and so we then know, > it's not that big of a deal. Thanks for your quick answer and clarification. -- Danie -- Linaro.org │ Open source software for ARM SoCs Follow Linaro: Facebook | Twitter | Blog