choosealicense.com/_licenses/ms-pl.txt

---
title: Microsoft Public License
spdx-id: MS-PL

description: An open source license with a patent grant.

how: Create a text file (typically named LICENSE or LICENSE.txt) in the root of your source code and copy the text of the license into the file.

using:

permissions:
  - commercial-use
  - modifications
  - distribution
  - patent-use
  - private-use

conditions:
  - include-copyright

limitations:
  - warranty
  - trademark-use

---

Microsoft Public License (Ms-PL)

This license governs use of the accompanying software. If you use the
software,
you accept this license. If you do not accept the license, do not use the
software.

   1. Definitions

The terms "reproduce," "reproduction," "derivative works," and "distribution"
have the same meaning here as under U.S. copyright law. A "contribution" is
the original software, or any additions or changes to the software. A
"contributor"
is any person that distributes its contribution under this license. "Licensed
patents" are a contributor's patent claims that read directly on its
contribution.

   2. Grant of Rights

(A) Copyright Grant- Subject to the terms of this license, including the
license
conditions and limitations in section 3, each contributor grants you a
non-exclusive,
worldwide, royalty-free copyright license to reproduce its contribution,
prepare
derivative works of its contribution, and distribute its contribution or any
derivative works that you create.

(B) Patent Grant- Subject to the terms of this license, including the license
conditions and limitations in section 3, each contributor grants you a
non-exclusive,
worldwide, royalty-free license under its licensed patents to make, have made,
use, sell, offer for sale, import, and/or otherwise dispose of its
contribution
in the software or derivative works of the contribution in the software.

   3. Conditions and Limitations

(A) No Trademark License- This license does not grant you rights to use any
contributors' name, logo, or trademarks.

(B) If you bring a patent claim against any contributor over patents that
you claim are infringed by the software, your patent license from such
contributor
to the software ends automatically.

(C) If you distribute any portion of the software, you must retain all
copyright,
patent, trademark, and attribution notices that are present in the software.

(D) If you distribute any portion of the software in source code form, you
may do so only under this license by including a complete copy of this license
with your distribution. If you distribute any portion of the software in
compiled
or object code form, you may only do so under a license that complies with
this license.

(E) The software is licensed "as-is." You bear the risk of using it. The
contributors
give no express warranties, guarantees, or conditions. You may have additional
consumer rights under your local laws which this license cannot change. To
the extent permitted under your local laws, the contributors exclude the
implied
warranties of merchantability, fitness for a particular purpose and
non-infringement.
MS Open Source licenses Add the the Microsoft Open Source licenses which are heavily used on Codeplex 2015-05-29 01:10:58 +01:00			`---`
Update ms-pl.txt 2015-09-01 23:14:00 +01:00			`title: Microsoft Public License`
spdx-id required, nickname only for licenses with customary short names 2016-05-24 16:21:13 -05:00			`spdx-id: MS-PL`
Update ms-pl.txt 2015-09-01 23:14:00 +01:00
add missing descriptions, missing property, slight desc tweaks 2016-04-04 10:56:29 -07:00			`description: An open source license with a patent grant.`
MS Open Source licenses Add the the Microsoft Open Source licenses which are heavily used on Codeplex 2015-05-29 01:10:58 +01:00
Add how, removed layout and permalink Appears the spec has been updated - lets hope this sorts it 2015-09-01 23:29:59 +01:00			`how: Create a text file (typically named LICENSE or LICENSE.txt) in the root of your source code and copy the text of the license into the file.`

make `using` required for new licenses 2017-05-30 14:17:13 -07:00			`using:`

rename/order license properties better reflect how licenses work and are structured grant (permissions) conditioned on (conditions) with limitations Permissions coming first combats mistaken but apparently widespread impression that licenses impose conditions, even such that without a license, there would be no conditions/work would be in the public domain. Requirements->Conditions emphasizes that they are pertinent if one wants to take advantage of permissions. Forbiddens->Limitations is more accurate: in most cases licenses don't give permission to hold licensors liable, in some cases to use licensors' trademarks or patents, but a licensee does not lose the permissions granted by the license if the licensee holds licensor liable, etc. Also emphasizes that there are limitatations on the license grant, not that the license imposes prohibitions. The most concise place to see both the rename and reorder is in _includes/license-overview.html I did not reorder the appearance of the groups of properties in license source files (.txt files in _licenses) as those orderings are not used to render anything on the webiste. Might do so later. 2016-03-01 13:33:15 -08:00			`permissions:`
MS Open Source licenses Add the the Microsoft Open Source licenses which are heavily used on Codeplex 2015-05-29 01:10:58 +01:00			`- commercial-use`
			`- modifications`
			`- distribution`
Rename "Patent Grant" to "Patent Use" Per the discussion in #168, the consumers of the softare are granted the right to use patents. So "Patent Use" makes more sense from a consumer perspective than "Patent Grant". 2015-11-01 22:51:13 -05:00			`- patent-use`
MS Open Source licenses Add the the Microsoft Open Source licenses which are heavily used on Codeplex 2015-05-29 01:10:58 +01:00			`- private-use`

sort license properties in the order permissions > conditions > limitations (fixes #387) 2016-08-22 18:25:24 +01:00			`conditions:`
			`- include-copyright`

rename/order license properties better reflect how licenses work and are structured grant (permissions) conditioned on (conditions) with limitations Permissions coming first combats mistaken but apparently widespread impression that licenses impose conditions, even such that without a license, there would be no conditions/work would be in the public domain. Requirements->Conditions emphasizes that they are pertinent if one wants to take advantage of permissions. Forbiddens->Limitations is more accurate: in most cases licenses don't give permission to hold licensors liable, in some cases to use licensors' trademarks or patents, but a licensee does not lose the permissions granted by the license if the licensee holds licensor liable, etc. Also emphasizes that there are limitatations on the license grant, not that the license imposes prohibitions. The most concise place to see both the rename and reorder is in _includes/license-overview.html I did not reorder the appearance of the groups of properties in license source files (.txt files in _licenses) as those orderings are not used to render anything on the webiste. Might do so later. 2016-03-01 13:33:15 -08:00			`limitations:`
no-liability -> liability, warranty rename and add tag and associated descriptions fixes #412 2016-12-12 14:29:25 -08:00			`- warranty`
MS Open Source licenses Add the the Microsoft Open Source licenses which are heavily used on Codeplex 2015-05-29 01:10:58 +01:00			`- trademark-use`
sort license properties in the order permissions > conditions > limitations (fixes #387) 2016-08-22 18:25:24 +01:00
MS Open Source licenses Add the the Microsoft Open Source licenses which are heavily used on Codeplex 2015-05-29 01:10:58 +01:00			`---`

update vendored licenses with text from SPDX API 2017-03-05 17:41:00 -05:00			`Microsoft Public License (Ms-PL)`

Source SPDX HTML, wrap with pandoc to get closer to usable form 2017-11-19 13:49:31 -08:00			`This license governs use of the accompanying software. If you use the`
run vendor script 2018-08-11 14:11:55 -07:00			`software,`
			`you accept this license. If you do not accept the license, do not use the`
			`software.`

			`1. Definitions`
Source SPDX HTML, wrap with pandoc to get closer to usable form 2017-11-19 13:49:31 -08:00
			`The terms "reproduce," "reproduction," "derivative works," and "distribution"`
			`have the same meaning here as under U.S. copyright law. A "contribution" is`
			`the original software, or any additions or changes to the software. A`
run vendor script 2018-08-11 14:11:55 -07:00			`"contributor"`
			`is any person that distributes its contribution under this license. "Licensed`
			`patents" are a contributor's patent claims that read directly on its`
			`contribution.`

			`2. Grant of Rights`

			`(A) Copyright Grant- Subject to the terms of this license, including the`
			`license`
			`conditions and limitations in section 3, each contributor grants you a`
			`non-exclusive,`
			`worldwide, royalty-free copyright license to reproduce its contribution,`
			`prepare`
			`derivative works of its contribution, and distribute its contribution or any`
			`derivative works that you create.`

			`(B) Patent Grant- Subject to the terms of this license, including the license`
			`conditions and limitations in section 3, each contributor grants you a`
			`non-exclusive,`
			`worldwide, royalty-free license under its licensed patents to make, have made,`
			`use, sell, offer for sale, import, and/or otherwise dispose of its`
			`contribution`
			`in the software or derivative works of the contribution in the software.`

			`3. Conditions and Limitations`

			`(A) No Trademark License- This license does not grant you rights to use any`
			`contributors' name, logo, or trademarks.`

			`(B) If you bring a patent claim against any contributor over patents that`
			`you claim are infringed by the software, your patent license from such`
			`contributor`
			`to the software ends automatically.`

			`(C) If you distribute any portion of the software, you must retain all`
			`copyright,`
			`patent, trademark, and attribution notices that are present in the software.`

			`(D) If you distribute any portion of the software in source code form, you`
			`may do so only under this license by including a complete copy of this license`
			`with your distribution. If you distribute any portion of the software in`
			`compiled`
			`or object code form, you may only do so under a license that complies with`
			`this license.`

			`(E) The software is licensed "as-is." You bear the risk of using it. The`
			`contributors`
			`give no express warranties, guarantees, or conditions. You may have additional`
			`consumer rights under your local laws which this license cannot change. To`
			`the extent permitted under your local laws, the contributors exclude the`
			`implied`
			`warranties of merchantability, fitness for a particular purpose and`
			`non-infringement.`