Skip to content

license: add extension to LICENSE file #954

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Feb 19, 2019
Merged

license: add extension to LICENSE file #954

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions docs/reference/contributing/guidelines/license.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -30,7 +30,7 @@ The full text of the license can be found on the [Apache website](http://www.apa

In order to clearly reflect the Apache 2.0 license, please create two text files:

- A *LICENSE* file with the following text:
- A *LICENSE.md* file with the following text:

```
Unless specifically indicated otherwise in a file, files are licensed under the Apache 2.0 license,
Expand Down Expand Up @@ -69,7 +69,7 @@ The full text can be found on [mbed.com](https://www.mbed.com/licenses/PBL-1.0).

In order to clearly reflect the PBL license, please create three text files:

- A *LICENSE* file with:
- A *LICENSE.md* file with:

<pre>Unless specifically indicated otherwise in a file, files are licensed under the Permissive Binary License,
as can be found in: LICENSE-permissive-binary-license-1.0.txt</pre>
Expand All @@ -96,13 +96,13 @@ See the License for the specific language governing permissions and limitations

If you decide to use a different license for your work, follow the same pattern:

- Create a *LICENSE* file with a description of the license situation, following the pattern described in the sections above.
- Create a *LICENSE.md* file with a description of the license situation, following the pattern described in the sections above.

- Put the full original license texts in separate documents named *LICENSE-XYZ.txt*, where XYZ is the corresponding [SPDX identifier](http://spdx.org/licenses/) for your license.

- Begin each source header with your copyright line, the SPDX identifier and the standard header for the license that applies to that single file, if it has one. (See [SPDX Specification, Appendix V](https://spdx.org/spdx-specification-21-web-version#h.twlc0ztnng3b).)

- If more than one license applies to the source file, then use an SPDX license expression (see [SPDX Specification, Appendix IV](https://spdx.org/spdx-specification-21-web-version#h.jxpfx0ykyb60)), to reflect the presence of multiple licenses in your *LICENSE* file and in each source file.
- If more than one license applies to the source file, then use an SPDX license expression (see [SPDX Specification, Appendix IV](https://spdx.org/spdx-specification-21-web-version#h.jxpfx0ykyb60)), to reflect the presence of multiple licenses in your *LICENSE.md* file and in each source file.

### Contributing to the Mbed OS codebase

Expand Down