public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Leif Lindholm <leif.lindholm@linaro.org>
To: Jordan Justen <jordan.l.justen@intel.com>
Cc: Michael D Kinney <michael.d.kinney@intel.com>,
	edk2-devel@lists.01.org, Andrew Fish <afish@apple.com>
Subject: Re: [Patch V3 3/8] edk2: Remove commit message details from Contributions.txt
Date: Fri, 21 Jul 2017 23:14:09 +0100	[thread overview]
Message-ID: <20170721221409.GF1501@bivouac.eciton.net> (raw)
In-Reply-To: <150067181439.20068.8395013529501693336@jljusten-skl>

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 <leif.lindholm@linaro.org>
> > Cc: Andrew Fish <afish@apple.com>
> > Cc: Jordan Justen <jordan.l.justen@intel.com>
> > Contributed-under: TianoCore Contribution Agreement 1.1
> > Signed-off-by: Michael D Kinney <michael.d.kinney@intel.com>
> > ---
> >  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 <contributor@example.com>
> > -Subject: [PATCH] CodeModule: Brief-single-line-summary
> > -
> > -Full-commit-message
> > -
> > -Contributed-under: TianoCore Contribution Agreement 1.0
> > -Signed-off-by: Contributor Name <contributor@example.com>
> > ----
> > -
> > -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


  reply	other threads:[~2017-07-21 22:12 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-20  5:44 [Patch V3 0/8] Update to Tiano Contribution Agreement 1.1 Michael D Kinney
2017-07-20  5:44 ` [Patch V3 1/8] BaseTools/PatchCheck: Support " Michael D Kinney
2017-07-20 22:57   ` Jordan Justen
2017-07-20  5:44 ` [Patch V3 2/8] edk2: Move TianoCore Contribution Agreement to root Michael D Kinney
2017-07-20  5:44 ` [Patch V3 3/8] edk2: Remove commit message details from Contributions.txt Michael D Kinney
2017-07-21 21:16   ` Jordan Justen
2017-07-21 22:14     ` Leif Lindholm [this message]
2017-07-24 18:13       ` Kinney, Michael D
2017-07-24 19:33         ` Jordan Justen
2017-07-24 20:01           ` Kinney, Michael D
2017-07-24 20:46             ` Jordan Justen
2017-07-20  5:44 ` [Patch V3 4/8] edk2: Update to TianoCore Contribution Agreement 1.1 Michael D Kinney
2017-07-20  5:44 ` [Patch V3 5/8] edk2: Reformat " Michael D Kinney
2017-07-20  5:44 ` [Patch V3 6/8] edk2/OvmfPkg: Add MIT license files Michael D Kinney
2017-07-20  5:44 ` [Patch V3 7/8] edk2: Move License.txt file to root Michael D Kinney
2017-07-20  6:35   ` Jordan Justen
2017-07-20 15:09     ` Kinney, Michael D
2017-07-20 22:53       ` Jordan Justen
2017-07-20 23:39         ` Kinney, Michael D
2017-07-25 10:06           ` Laszlo Ersek
2017-07-20  5:44 ` [Patch V3 8/8] edk2: Add Readme.md to root of edk2 repository Michael D Kinney

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-list from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170721221409.GF1501@bivouac.eciton.net \
    --to=devel@edk2.groups.io \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox