public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Jordan Justen <jordan.l.justen@intel.com>
To: "Kinney, Michael D" <michael.d.kinney@intel.com>,
	Leif Lindholm <leif.lindholm@linaro.org>
Cc: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: PATCH] Change EDK II to BSD+Patent License
Date: Tue, 19 Mar 2019 12:57:01 -0700	[thread overview]
Message-ID: <155302542161.7938.10539816377419987642@jljusten-skl> (raw)
In-Reply-To: <E92EE9817A31E24EB0585FDF735412F5B9C6CE6D@ORSMSX112.amr.corp.intel.com>

On 2019-03-19 12:09:41, Kinney, Michael D wrote:
> Leif and Jordan,
> 
> Would you mind putting together a specific proposal

I would propose adding the exact text from that site into a
DeveloperCertificate.txt in the root of the tree. Then reference when
documenting how to contribute a patch, near the Signed-off-by part.

Optionally, the https://developercertificate.org/ site could be
referenced to show where the text came from.

> and perhaps some links to other projects that use
> the same approach?

* linux kernel [1] (where DCO started)

* eclipse [2]

-Jordan

[1]: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v5.1-rc1#n431

[2]: https://www.eclipse.org/legal/DCO.php


  reply	other threads:[~2019-03-19 19:57 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-13 17:54 PATCH] Change EDK II to BSD+Patent License Kinney, Michael D
2019-03-14 10:55 ` Laszlo Ersek
2019-03-14 19:06   ` Julien Grall
     [not found]     ` <8F40F2BF-B40F-4338-A832-70AE84B26408@citrix.com>
2019-03-15  9:35       ` Julien Grall
     [not found]         ` <6FBC013D-4BC9-454C-9D4D-87C96F435704@citrix.com>
2019-03-15 17:18           ` Julien Grall
     [not found]             ` <C2A0176C-8197-421A-9CA9-2B416DF17EAB@citrix.com>
2019-03-20 12:09               ` Laszlo Ersek
2019-03-23  0:44                 ` Kinney, Michael D
2019-03-25 10:04                   ` Laszlo Ersek
     [not found]               ` <720E0EE9-2AED-4110-827D-B87DE5F52862@citrix.com>
2019-03-20 18:25                 ` Laszlo Ersek
2019-03-20 18:42                   ` Julien Grall
2019-03-20 20:03                     ` Laszlo Ersek
     [not found]                   ` <8A1C7ED9-000A-4EBB-A196-10CE5B9B522F@citrix.com>
2019-03-21 17:41                     ` Laszlo Ersek
2019-03-18 18:17   ` Kinney, Michael D
2019-03-14 18:03 ` Jordan Justen
2019-03-18 18:25   ` Kinney, Michael D
2019-03-18 19:42     ` Jordan Justen
2019-03-19 17:58     ` Leif Lindholm
2019-03-19 19:09       ` Kinney, Michael D
2019-03-19 19:57         ` Jordan Justen [this message]
2019-03-19 20:06         ` Leif Lindholm

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=155302542161.7938.10539816377419987642@jljusten-skl \
    --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