public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Kinney, Michael D" <michael.d.kinney@intel.com>
To: "Justen, Jordan L" <jordan.l.justen@intel.com>,
	"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>,
	"Kinney, Michael D" <michael.d.kinney@intel.com>
Cc: Leif Lindholm <leif.lindholm@linaro.org>, Andrew Fish <afish@apple.com>
Subject: Re: [Patch 5/6] edk2: Update to TianoCore Contribution Agreement 1.1
Date: Wed, 19 Jul 2017 17:35:50 +0000	[thread overview]
Message-ID: <E92EE9817A31E24EB0585FDF735412F5A7D5D453@ORSMSX113.amr.corp.intel.com> (raw)
In-Reply-To: <150042183834.7417.17999724057527326477@jljusten-skl>

Hi Jordan,

I will change format to a bullet list in next version of the
patch series.

The only documents donated so far use the Free BSD Documentation 
license.  If a community member requests to donate a document under
a different license, we can review that request when that happens.

Thanks,

Mike

> -----Original Message-----
> From: Justen, Jordan L
> Sent: Tuesday, July 18, 2017 4:51 PM
> To: Kinney, Michael D <michael.d.kinney@intel.com>; edk2-
> devel@lists.01.org
> Cc: Leif Lindholm <leif.lindholm@linaro.org>; Andrew Fish
> <afish@apple.com>
> Subject: Re: [Patch 5/6] edk2: Update to TianoCore Contribution
> Agreement 1.1
> 
> On 2017-07-18 14:17:00, Michael D Kinney wrote:
> > https://bugzilla.tianocore.org/show_bug.cgi?id=629
> >
> > Update the TianoCore Contribution Agreement from Version 1.0
> > to Version 1.1 to cover open source documentation associated
> > with the TianoCore project.
> >
> > Version 1.0 covers source code files.  Version 1.1 is a
> > backwards compatible extension that add support for document
> > files in both source form and compiled form.
> >
> > The edk2 repository is updated so the same contribution
> > agreement is used by developers that work on TianoCore
> > related source code or TianoCore related documents.
> >
> > Links to RFC and Wiki on the GitBook documentation process
> > * https://lists.01.org/pipermail/edk2-devel/2017-
> March/008654.html
> > * https://github.com/tianocore-docs/edk2-
> TemplateSpecification/wiki
> >
> > 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 | 16 +++++++++++-----
> >  1 file changed, 11 insertions(+), 5 deletions(-)
> >
> > diff --git a/Contributions.txt b/Contributions.txt
> > index 06c60d8e17..e2e3437981 100644
> > --- a/Contributions.txt
> > +++ b/Contributions.txt
> > @@ -1,4 +1,3 @@
> > -
> >  ======================
> >  = Code Contributions =
> >  ======================
> > @@ -27,6 +26,7 @@ To make a contribution to a TianoCore
> project, follow these steps.
> >     * MIT: http://opensource.org/licenses/MIT
> >     * Python-2.0: http://opensource.org/licenses/Python-2.0
> >     * Zlib: http://opensource.org/licenses/Zlib
> > +   For documentation:
> https://www.freebsd.org/copyright/freebsd-doc-license.html
> 
> As I noted before I think this would look more consistent:
> 
> """
> 5. It is preferred that contributions are submitted using the
> same
>    copyright license as the base project. When that is not
> possible,
>    then contributions using the following licenses can be
> accepted:
>    * BSD (2-clause): http://opensource.org/licenses/BSD-2-Clause
>    * BSD (3-clause): http://opensource.org/licenses/BSD-3-Clause
>    * MIT: http://opensource.org/licenses/MIT
>    * Python-2.0: http://opensource.org/licenses/Python-2.0
>    * Zlib: http://opensource.org/licenses/Zlib
> 
>    For documentation:
>    * FreeBSD Documentation License
>      https://www.freebsd.org/copyright/freebsd-doc-license.html
> """
> 
> I also asked if other documentation licenses were evaluated, such
> as
> the 'good' licenses that Red Hat noted for Fedora:
> 
> https://fedoraproject.org/wiki/Licensing:Main?rd=Licensing#Docume
> ntation_Licenses
> 
> Anyway, the bullet format would lend itself to expanding the list
> in
> the future.
> 
> -Jordan
> 
> >
> >     Contributions of code put into the public domain can also
> be
> >     accepted.
> > @@ -35,10 +35,10 @@ To make a contribution to a TianoCore
> project, follow these steps.
> >     review will be required.
> >
> >  ========================================
> > -= TianoCore Contribution Agreement 1.0 =
> > += TianoCore Contribution Agreement 1.1 =
> >  ========================================
> >
> > -INTEL CORPORATION ("INTEL") MAKES AVAILABLE SOFTWARE,
> DOCUMENTATION,
> > +INTEL CORPORATION ("INTEL") MAKES AVAILABLE SOFTWARE,
> DOCUMENTATION ("DOCUMENTATION"),
> >  INFORMATION AND/OR OTHER MATERIALS FOR USE IN THE TIANOCORE
> OPEN SOURCE
> >  PROJECT (COLLECTIVELY "CONTENT"). USE OF THE CONTENT IS
> GOVERNED BY THE
> >  TERMS AND CONDITIONS OF THIS AGREEMENT BETWEEN YOU AND INTEL
> AND/OR THE
> > @@ -51,14 +51,20 @@ AGREEMENT AND THE TERMS AND CONDITIONS OF
> ANY APPLICABLE LICENSE
> >  AGREEMENTS OR NOTICES INDICATED OR REFERENCED BELOW, THEN YOU
> MAY NOT
> >  USE THE CONTENT.
> >
> > -Unless otherwise indicated, all Content made available on the
> TianoCore
> > +Unless otherwise indicated, all Content (except Documentation)
> made available on the TianoCore
> >  site is provided to you under the terms and conditions of the
> BSD
> >  License ("BSD"). A copy of the BSD License is available at
> >  http://opensource.org/licenses/bsd-license.php
> >  or when applicable, in the associated License.txt file.
> >
> > +Unless otherwise indicated, all Documentation made available
> on the
> > +TianoCore site is provided to you under the terms and
> conditions of the
> > +FreeBSD Documentation License ("FreeBSD"). A copy of the BSD
> License is
> > +available at https://www.freebsd.org/copyright/freebsd-doc-
> license.html or,
> > +when applicable, in the associated License.txt file.
> > +
> >  Certain other content may be made available under other
> licenses as
> > -indicated in or with such Content. (For example, in a
> License.txt file.)
> > +indicated in or with such Content (for example, in a
> License.txt file).
> >
> >  You accept and agree to the following terms and conditions for
> Your
> >  present and future Contributions submitted to TianoCore site.
> Except
> > --
> > 2.13.1.windows.2
> >

  reply	other threads:[~2017-07-19 17:33 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-18 21:16 [Patch 0/6] Update to Tiano Contribution Agreement 1.1 Michael D Kinney
2017-07-18 21:16 ` [Patch 1/6] BaseTools/PatchCheck: Support " Michael D Kinney
2017-07-18 21:16 ` [Patch 2/6] edk2: Move Tiano Contribution Agreement to root Michael D Kinney
2017-07-18 21:16 ` [Patch 3/6] edk2: Remove Tiano Contribution Agreement from packages Michael D Kinney
2017-07-18 22:47   ` Jordan Justen
2017-07-19 15:50     ` Kinney, Michael D
2017-07-18 21:16 ` [Patch 4/6] edk2: Remove commit message details from Contributions.txt Michael D Kinney
2017-07-18 23:40   ` Jordan Justen
2017-07-19 15:54     ` Kinney, Michael D
2017-07-19 17:39       ` Jordan Justen
2017-07-18 21:17 ` [Patch 5/6] edk2: Update to TianoCore Contribution Agreement 1.1 Michael D Kinney
2017-07-18 23:50   ` Jordan Justen
2017-07-19 17:35     ` Kinney, Michael D [this message]
2017-07-18 21:17 ` [Patch 6/6] edk2: Reformat " 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=E92EE9817A31E24EB0585FDF735412F5A7D5D453@ORSMSX113.amr.corp.intel.com \
    --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