From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id BE42442870; Thu, 30 Mar 2023 15:14:34 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 9C9DA410D3; Thu, 30 Mar 2023 15:14:34 +0200 (CEST) Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) by mails.dpdk.org (Postfix) with ESMTP id C5C3E40E25 for ; Thu, 30 Mar 2023 15:14:33 +0200 (CEST) Received: from compute2.internal (compute2.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 6F94C5C0067; Thu, 30 Mar 2023 09:14:30 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute2.internal (MEProxy); Thu, 30 Mar 2023 09:14:30 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:cc:content-transfer-encoding:content-type:content-type:date :date:from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:sender:subject:subject:to:to; s=fm2; t= 1680182070; x=1680268470; bh=K/MSGqfCb6cwBDBn1kQZwcdHY1vZv0Sx2IA ejbTr+1c=; b=x4QlfeMcY0/u+yrKS6uEpn0dBFYXsTK0k2qfOIuMBPr6g4UvJ/L j4rwC/GUvQKVQXrk3k6tBELbsgfPAsrBY0Dr+/jhoOljUE0HyaKpWZiEPiB1QKAk dp6qW412FiSywZHmG13RXANT2CF39OKGbq/gnOVzrf23dJuxuKnqR4pQRn8QMyYu MlWl3cd+YctxHm2w50yfy2LBTaq4dE5acyWSJbnCWunAdZvkMC6qH7fdjlLwxDi6 dbPtDjwZiAItCIc9BGhlFzKsksa+NS84ycaXVW06xD+aWtNcB1mQ0687s4H+1A4z 8/m/a29KrCbXgjuFWpVqOIlnz8qzmtAOr1Q== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:content-type:date:date:feedback-id:feedback-id :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:sender:subject:subject:to:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; t= 1680182070; x=1680268470; bh=K/MSGqfCb6cwBDBn1kQZwcdHY1vZv0Sx2IA ejbTr+1c=; b=ph8956xhnzNBmErzTpCTws2i4xfzXdeRk72lgEutpEH5kFt7l8V eoYSMngvLtCLyBH6K/w+TLJP0lOxdYf1epO5GEZv02xbxc2OCSrDf6o4umSsvXiY gAwwwP+ppLJed0wyrxR5NhLe/OkOedhRw6WRHzRqvW6XMUpeSIuLmGDO3XMLYtUO VqcnPU9fYhJONhWDTiPUBDtK1vlPSzdenMf0dxOLvhpjzxSEcNDBwyKOrWQfrIpV bMqy3gZ5/IZF9KOHTSIEJg99+TvbzbbkDvM+PFTXLMrL8bWrffw0tcDq4zWohzAt 1D+lSuuBvrVJ+VyVX5POpOB/9velWl0ud5A== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrvdehkedgiedtucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephffvvefufffkjghfggfgtgesthfuredttddtvdenucfhrhhomhepvfhhohhm rghsucfoohhnjhgrlhhonhcuoehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtqeenuc ggtffrrghtthgvrhhnpedtjeeiieefhedtfffgvdelteeufeefheeujefgueetfedttdei kefgkeduhedtgfenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfh hrohhmpehthhhomhgrshesmhhonhhjrghlohhnrdhnvght X-ME-Proxy: Feedback-ID: i47234305:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Thu, 30 Mar 2023 09:14:28 -0400 (EDT) From: Thomas Monjalon To: Ferruh Yigit , "Zhang, Qi Z" , "Wu, Jingjing" , "Xing, Beilei" , Rushil Gupta , "Guo, Junfeng" Cc: "dev@dpdk.org" , Joshua Washington , Jeroen de Borst Subject: Re: [PATCH 2/2] net/gve: update copyright holders Date: Thu, 30 Mar 2023 15:14:27 +0200 Message-ID: <9576586.lOV4Wx5bFT@thomas> In-Reply-To: References: <20230328020826.1269570-1-junfeng.guo@intel.com> <2436497.uoxibFcf9D@thomas> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org 30/03/2023 09:20, Guo, Junfeng: > From: Thomas Monjalon > > 28/03/2023 11:35, Guo, Junfeng: > > > The background is that, in the past (DPDK 22.11) we didn't get the > > approval > > > of license from Google, thus chose the MIT License for the base code, > > and > > > BSD-3 License for GVE common code (without the files in /base folder). > > > We also left the copyright holder of base code just to Google Inc, and > > made > > > Intel as the copyright holder of GVE common code (without /base > > folder). > > > > > > Today we are working together for GVE dev and maintaining. And we > > got > > > the approval of BSD-3 License from Google for the base code. > > > Thus we dicided to 1) switch the License of GVE base code from MIT to > > BSD-3; > > > 2) add Google LLC as one of the copyright holders for GVE common > > code. > > > > Do you realize we had lenghty discussions in the Technical Board, > > the Governing Board, and with lawyers, just for this unneeded exception? > > > > Now looking at the patches, there seem to be some big mistakes like > > removing some copyright. I don't understand how it can be taken so > > lightly. > > > > I regret how fast we were, next time we will surely operate differently. > > If you want to improve the reputation of this driver, > > please ask other copyright holders to be more active and responsive. > > > > Really sorry for causing such severe trouble. > > Yes, we did take lots of efforts in the Technical Board and the Governing > Board about this MIT exception. We really appreciate that. > > About this patch set, it is my severe mistake to switch the MIT License > directly for the upstream-ed code in community, in the wrong way. > In the past we upstream-ed this driver with MIT License followed from > the kernel community's gve driver base code. And now we want to > use the code with BSD-3 License (approved by Google). > So I suppose that the correct way may be 1) first remove all these code > under MIT License and 2) then add the new files under BSD-3 License. The code under BSD is different of the MIT code? If it is the same with a new approved license, you can just change the license. > Please correct me if there are still misunderstanding in my statement. > Thanks Thomas for pointing out my mistake. I'll be careful to fix this. > > Copyright holder for the gve base code will stay unchanged. Google LLC > will be added as one of the copyright holders for the gve common code. > @Rushil Gupta Please also be more active and responsive for the code > review and contribution in the community. Thanks!