From: Matteo Carlini <Matteo.Carlini@arm.com>
To: Leif Lindholm <leif.lindholm@linaro.org>,
"Kinney, Michael D" <michael.d.kinney@intel.com>
Cc: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>,
Sami Mujawar <Sami.Mujawar@arm.com>,
Guillaume Letellier <Guillaume.Letellier@arm.com>,
nd <nd@arm.com>
Subject: Re: [RFC] Change EDK II to an Apache 2.0 License
Date: Fri, 7 Dec 2018 20:07:18 +0000 [thread overview]
Message-ID: <DB5PR08MB0901FE6A0163D3EF1E26AD3591AA0@DB5PR08MB0901.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <20181129225336.wdkdh4uqbif2eazz@bivouac.eciton.net>
Ok from Arm side, as long as contributions submitted under the existing TianoCore Contribution Agreement 1.1 (BSD 2-Clause) will still be accepted, as it's somehow implied by point 3).
Thanks
Matteo
> -----Original Message-----
> From: Leif Lindholm <leif.lindholm@linaro.org>
> Sent: 29 November 2018 22:54
> To: Kinney, Michael D <michael.d.kinney@intel.com>
> Cc: edk2-devel@lists.01.org; Matteo Carlini <Matteo.Carlini@arm.com>; Sami
> Mujawar <Sami.Mujawar@arm.com>
> Subject: Re: [edk2] [RFC] Change EDK II to an Apache 2.0 License
>
> On Thu, Nov 29, 2018 at 06:39:28PM +0000, Kinney, Michael D wrote:
> > Hello,
> >
> > This RFC follows up on the proposal from Mark Doran to change the EDK
> > II Project to an Apache 2.0 License.
> >
> > https://lists.01.org/pipermail/edk2-devel/2018-October/030385.html
> >
> >
> > ** Please provide feedback on the proposal by Friday 12/7/18. **
>
> 7 December 2018 to anyone outside the US :)
>
> > I will be following up with pointers to public GitHub branches that
> > contain the initial set of changes in steps (1) and (2) below for
> > review.
> >
> > The proposal is to perform this change to edk2/master in the steps
> > listed below. The license change will not be applied to any of the
> > other existing branches in the edk2 repository.
> >
> > 1) Change all files with a BSD 2-Clause license and only a single
> > copyright statement by Intel Corporation to an Apache 2.0 license
> > and add an SPDX-License-Identifier statement.
> >
> >
> ================================================================
> ======
> > SPDX-License-Identifier: Apache-2.0
> >
> > Licensed under the Apache License, Version 2.0 (the "License");
> > you may not use this file except in compliance with the License.
> > You may obtain a copy of the License at
> >
> > http://www.apache.org/licenses/LICENSE-2.0
> >
> > Unless required by applicable law or agreed to in writing, software
> > distributed under the License is distributed on an "AS IS" BASIS,
> > WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
> implied.
> > See the License for the specific language governing permissions and
> > limitations under the License.
> >
> >
> ================================================================
> ======
> >
> > 2) Update Readme.md and License.txt in the root of the edk2 repository to
> > state that content is covered by a mix of BSD 2-Clause and Apache 2.0
> > licenses.
> >
> > 3) Update all documentation to state that content submitted under the
> > Apache 2.0 license no longer requires the Tianocore Contribution
> > Agreement which means the following line is not required in commit
> > messages for changes to files that are covered by an Apache 2.0 License.
>
> Presumably this also applies to files _added_ with an Apache 2.0 License? (If so,
> the above could benefit from minor rewording.)
>
> > Contributed-under: TianoCore Contribution Agreement 1.1
> >
> > 4) Create Wiki page(s) that provide the details of the Apache 2.0 License
> > change and provide the status of the license change for each package
> > in the edk2 repository. Also provide a list of the additional copyright
> > holders that need to be contacted to accept the change to an Apache 2.0
> > License along with the status of that acceptance.
> >
> > 5) After all copyright holders have accepted the change to an Apache 2.0
> > License, change the remaining files from BSD 2-Clause to Apache 2.0.
> >
> > 6) Update Readme.md and License.txt in the edk2 repository to state that
> > Apache 2.0 is the preferred license for the EDK II project.
>
> From Linaro's side, we have no concern beyond that we'd like to hear ARM's
> opinion. (Adding cc.)
>
> Regards,
>
> Leif
next prev parent reply other threads:[~2018-12-07 20:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-29 18:39 [RFC] Change EDK II to an Apache 2.0 License Kinney, Michael D
2018-11-29 22:53 ` Leif Lindholm
2018-12-07 20:07 ` Matteo Carlini [this message]
2018-12-07 21:27 ` Kinney, Michael D
2018-12-07 10:51 ` Mark Kettenis
[not found] ` <DFF7383D242A84439AD17BCBA41787FE9C6D9968@ORSMSX109.amr.corp.intel.com>
2018-12-07 21:44 ` Mark Kettenis
2018-12-07 22:51 ` Doran, Mark
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=DB5PR08MB0901FE6A0163D3EF1E26AD3591AA0@DB5PR08MB0901.eurprd08.prod.outlook.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