diff --git a/_licenses/cern-ohl-p-2.0.txt b/_licenses/cern-ohl-p-2.0.txt index 014da0b..2b4cb2a 100644 --- a/_licenses/cern-ohl-p-2.0.txt +++ b/_licenses/cern-ohl-p-2.0.txt @@ -3,11 +3,12 @@ title: CERN Open Hardware Licence Version 2 - Permissive spdx-id: CERN-OHL-P-2.0 nickname: CERN OHL v2 Permissive -description: The CERN OHL was drafted with hardware in mind. On top of licensing copyright like software and documentation licenses, it also licenses patents. This “Permissive” variant allows people to take your code, relicense it and use it without any obligation to distribute the sources when they ship a product; it does have an attribution requirement. +description: The CERN OHL was drafted with hardware in mind. On top of licensing copyright like software and documentation licenses, it also licenses patents. This “Permissive” variant allows people to take your code, relicense it and use it without any obligation to distribute the sources when they ship a product; however, it does have an attribution requirement. 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. -note: CERN recommends adding the following information in the source files: copyright and license notice, a disclaimer of warranties and a source location. You can also include the source location in a part of the design which will be visible in the end product. +note: + CERN recommends adding the following information in the source files: copyright and license notice, a disclaimer of warranties and a source location. You can also include the source location in a part of the design which will be visible in the end product. using: tedium: https://github.com/jboone/tedium/blob/master/LICENSE-CERN-OHL-P-v2 diff --git a/_licenses/cern-ohl-s-2.0.txt b/_licenses/cern-ohl-s-2.0.txt index a8c97f8..8a99e9c 100644 --- a/_licenses/cern-ohl-s-2.0.txt +++ b/_licenses/cern-ohl-s-2.0.txt @@ -3,11 +3,12 @@ title: CERN Open Hardware Licence Version 2 - Strongly Reciprocal spdx-id: CERN-OHL-S-2.0 nickname: CERN OHL v2 Strongly Reciprocal -description: The CERN OHL was drafted with hardware in mind. On top of licensing copyright like software and documentation licenses, it also licenses patents. This “Strongly Reciprocal” variant applies to a complete design, and if a CERN-OHL-S-2.0 file is used in a project then the full project must be released under the CERN-OHL-S-2.0 (or a compatible license). +description: The CERN OHL was drafted with hardware in mind. On top of licensing copyright like software and documentation licenses, it also licenses patents. This “Strongly Reciprocal” variant applies to a complete design, so if a CERN-OHL-S-2.0 file is used in a project then the full project must be released under the CERN-OHL-S-2.0 (or a compatible license). 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. -note: CERN recommends adding the following information in the source files: copyright and license notice, a disclaimer of warranties and a source location. You can also include the source location in a part of the design which will be visible in the end product. +note: + CERN recommends adding the following information in the source files: copyright and license notice, a disclaimer of warranties and a source location. You can also include the source location in a part of the design which will be visible in the end product. using: USB Armory: https://github.com/f-secure-foundry/usbarmory/blob/master/hardware/mark-two/LICENSE diff --git a/_licenses/cern-ohl-w-2.0.txt b/_licenses/cern-ohl-w-2.0.txt index caa1893..9683582 100644 --- a/_licenses/cern-ohl-w-2.0.txt +++ b/_licenses/cern-ohl-w-2.0.txt @@ -7,7 +7,8 @@ description: The CERN OHL was drafted with hardware in mind. On top of licensin 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. -note: CERN recommends adding the following information in the source files: copyright and license notice, a disclaimer of warranties and a source location. You can also include the source location in a part of the design which will be visible in the end product. +note: + CERN recommends adding the following information in the source files: copyright and license notice, a disclaimer of warranties and a source location. You can also include the source location in a part of the design which will be visible in the end product. using: Simple PCIe FMC carrier: https://ohwr.org/project/spec/blob/master/LICENSES/CERN-OHL-W-2.0.txt