From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wr0-x22c.google.com (mail-wr0-x22c.google.com [IPv6:2a00:1450:400c:c0c::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id 9B5E721A143C1 for ; Fri, 21 Jul 2017 15:12:15 -0700 (PDT) Received: by mail-wr0-x22c.google.com with SMTP id v105so56869515wrb.0 for ; Fri, 21 Jul 2017 15:14:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=s4ga6/w+6hs1a3R1Ib0p9b2Y6ZJ5X/VkzTR7WKQ0Pco=; b=N9+QLGa01KRE/2GkGca/qXdzlG92n6v1cqbMtr0MRpilQ5r3FHgp7CahKK5FK24NGc qPQIu6mITEIvQD1WKiMVng3iwkHj0NEmMSJeGHlGTjc+AZWNfLwB701U6qjHMKAxzTjW F7slSN3TpzRhHz/sOfidJeLvVqdsQfRj6z+k4= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=s4ga6/w+6hs1a3R1Ib0p9b2Y6ZJ5X/VkzTR7WKQ0Pco=; b=rB6w/iFm10y7OC55YYMtbrXUwkFVTq9s+UPGF5mPGFUlKE6fJiXig3lk6luFwRBcjT 2Ci1FPZW9QNf0MMpMp2DYXC/EHGTiKHyID9iW8PGrMM1UyAxmQK+SIKo+SUFoYcucPta P+apgNl32fOe6g5G6xeIRx2vK7yYcOObc21A+1Hdlgg5dS/gc+pS1IGnCJi3mPL8EWD0 G9d5fW1QMGpm9LY9sKh3GO/oBJpAyfi4sRt2BVwqbGNfNJW55UqU98SdTiGpeo6htjAJ pVrNtH1h3RA648Fk+4H2wL6uujGzvMkqc98Hq2UVuiP4DQiZ8cpI9nhPzVjmOB2j2jcU ph6g== X-Gm-Message-State: AIVw111p7+YSdOoU4UPjwt9xvD7/Ly+yOwilLrhwb19jxhYJL+FMmP2F 3why3iJhwmJFOFSI X-Received: by 10.223.128.209 with SMTP id 75mr9902219wrl.99.1500675251504; Fri, 21 Jul 2017 15:14:11 -0700 (PDT) Received: from bivouac.eciton.net (bivouac.eciton.net. [2a00:1098:0:86:1000:23:0:2]) by smtp.gmail.com with ESMTPSA id b23sm4724665wrd.40.2017.07.21.15.14.10 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 21 Jul 2017 15:14:10 -0700 (PDT) Date: Fri, 21 Jul 2017 23:14:09 +0100 From: Leif Lindholm To: Jordan Justen Cc: Michael D Kinney , edk2-devel@lists.01.org, Andrew Fish Message-ID: <20170721221409.GF1501@bivouac.eciton.net> References: <20170720054411.18928-1-michael.d.kinney@intel.com> <20170720054411.18928-4-michael.d.kinney@intel.com> <150067181439.20068.8395013529501693336@jljusten-skl> MIME-Version: 1.0 In-Reply-To: <150067181439.20068.8395013529501693336@jljusten-skl> User-Agent: Mutt/1.5.23 (2014-03-12) Subject: Re: [Patch V3 3/8] edk2: Remove commit message details from Contributions.txt X-BeenThere: edk2-devel@lists.01.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: EDK II Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Jul 2017 22:12:16 -0000 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Fri, Jul 21, 2017 at 02:16:54PM -0700, Jordan Justen wrote: > On 2017-07-19 22:44:06, Michael D Kinney wrote: > > https://bugzilla.tianocore.org/show_bug.cgi?id=629 > > > > Remove the change description, commit message, and > > patch email section from Contributions.txt. This > > section is not part of the TianoCore Contribution > > Agreement. > > Neither are the ~35 remaining lines before this content, which you are > not removing. > > > The information is very important and is > > provided on the TianoCore web site and wiki and will > > be added to Readme.md in the root of the edk2 > > repository. > > Yes. It is important for making contributions, as is the ~35 lines > before the agreement that you didn't remove. So, why don't we just > keep them in Contributions.txt since they document how to make a > contribution? > > If you want a single file that only has the contribution agreement > text, then how about moving it to a ContributionAgreement.txt file, > and making Contributions.txt refer to it? I'm not sure why this would > be needed though. I think separating the mechanics of what a developer is supposed to do in order to contribute code from legalese of more interest to their legal department is a useful thing. This was why I was suggesting a SubmittingPatches.txt. Renaming Contributions.txt ContributionAgreement.txt would however indicate it contained only the contribution agreement, which (as you allude to) is not currently the case. The list of acceptable licenses would also need to move into the "howto" in this case. Regards, Leif > -Jordan > > > > > Cc: Leif Lindholm > > Cc: Andrew Fish > > Cc: Jordan Justen > > Contributed-under: TianoCore Contribution Agreement 1.1 > > Signed-off-by: Michael D Kinney > > --- > > Contributions.txt | 49 ------------------------------------------------- > > 1 file changed, 49 deletions(-) > > > > diff --git a/Contributions.txt b/Contributions.txt > > index f87cbd73c6..06c60d8e17 100644 > > --- a/Contributions.txt > > +++ b/Contributions.txt > > @@ -34,55 +34,6 @@ To make a contribution to a TianoCore project, follow these steps. > > Contributions using other licenses might be accepted, but further > > review will be required. > > > > -===================================================== > > -= Change Description / Commit Message / Patch Email = > > -===================================================== > > - > > -Your change description should use the standard format for a > > -commit message, and must include your "Signed-off-by" signature > > -and the "Contributed-under" message. > > - > > -== Sample Change Description / Commit Message = > > - > > -=== Start of sample patch email message === > > - > > -From: Contributor Name > > -Subject: [PATCH] CodeModule: Brief-single-line-summary > > - > > -Full-commit-message > > - > > -Contributed-under: TianoCore Contribution Agreement 1.0 > > -Signed-off-by: Contributor Name > > ---- > > - > > -An extra message for the patch email which will not be considered part > > -of the commit message can be added here. > > - > > -Patch content inline or attached > > - > > -=== End of sample patch email message === > > - > > -=== Notes for sample patch email === > > - > > -* The first line of commit message is taken from the email's subject > > - line following [PATCH]. The remaining portion of the commit message > > - is the email's content until the '---' line. > > -* git format-patch is one way to create this format > > - > > -=== Definitions for sample patch email === > > - > > -* "CodeModule" is a short idenfier for the affected code. For > > - example MdePkg, or MdeModulePkg UsbBusDxe. > > -* "Brief-single-line-summary" is a short summary of the change. > > -* The entire first line should be less than ~70 characters. > > -* "Full-commit-message" a verbose multiple line comment describing > > - the change. Each line should be less than ~70 characters. > > -* "Contributed-under" explicitely states that the contribution is > > - made under the terms of the contribtion agreement. This > > - agreement is included below in this document. > > -* "Signed-off-by" is the contributor's signature identifying them > > - by their real/legal name and their email address. > > - > > ======================================== > > = TianoCore Contribution Agreement 1.0 = > > ======================================== > > -- > > 2.13.1.windows.2 > > > > _______________________________________________ > > edk2-devel mailing list > > edk2-devel@lists.01.org > > https://lists.01.org/mailman/listinfo/edk2-devel