From 22bc080c4f8da1f41a60d7e5615c575bfaf68c37 Mon Sep 17 00:00:00 2001 From: nytpu Date: Mon, 23 Aug 2021 17:08:49 -0600 Subject: [PATCH 01/70] Add the CERN Open Hardware version 2 family of licenses --- _licenses/cern-ohl-p-2.0.txt | 216 +++++++++++++++++++++++ _licenses/cern-ohl-s-2.0.txt | 299 ++++++++++++++++++++++++++++++++ _licenses/cern-ohl-w-2.0.txt | 321 +++++++++++++++++++++++++++++++++++ 3 files changed, 836 insertions(+) create mode 100644 _licenses/cern-ohl-p-2.0.txt create mode 100644 _licenses/cern-ohl-s-2.0.txt create mode 100644 _licenses/cern-ohl-w-2.0.txt diff --git a/_licenses/cern-ohl-p-2.0.txt b/_licenses/cern-ohl-p-2.0.txt new file mode 100644 index 0000000..0340156 --- /dev/null +++ b/_licenses/cern-ohl-p-2.0.txt @@ -0,0 +1,216 @@ +--- +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. + +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 a license header and copyright notice to the README and source files. CERN provides a User's Guide containing a recommended license header. + +using: + Castor & Pollux: https://github.com/wntrblm/Castor_and_Pollux/blob/main/hardware/mainboard/LICENSE + LEDEAF: https://github.com/adamgreig/ledeaf/blob/master/LICENSE_CERN_OHL_P_v2.txt + ProtoCentral ECG Breakout: https://github.com/Protocentral/protocentral_max86150_ecg_ppg/blob/master/LICENSE.md#hardware + +permissions: + - commercial-use + - modifications + - distribution + - private-use + - patent-use + +conditions: + - include-copyright + - document-changes + +limitations: + - liability + - warranty + +--- +CERN Open Hardware Licence Version 2 - Permissive + + +Preamble + +CERN has developed this licence to promote collaboration among hardware +designers and to provide a legal tool which supports the freedom to use, +study, modify, share and distribute hardware designs and products based on +those designs. Version 2 of the CERN Open Hardware Licence comes in three +variants: this licence, CERN-OHL-P (permissive); and two reciprocal licences: +CERN-OHL-W (weakly reciprocal) and CERN-OHL-S (strongly reciprocal). + +The CERN-OHL-P is copyright CERN 2020. Anyone is welcome to use it, in +unmodified form only. + +Use of this Licence does not imply any endorsement by CERN of any Licensor or +their designs nor does it imply any involvement by CERN in their development. + + +1 Definitions + + 1.1 'Licence' means this CERN-OHL-P. + + 1.2 'Source' means information such as design materials or digital code + which can be applied to Make or test a Product or to prepare a Product + for use, Conveyance or sale, regardless of its medium or how it is + expressed. It may include Notices. + + 1.3 'Covered Source' means Source that is explicitly made available under + this Licence. + + 1.4 'Product' means any device, component, work or physical object, whether + in finished or intermediate form, arising from the use, application or + processing of Covered Source. + + 1.5 'Make' means to create or configure something, whether by manufacture, + assembly, compiling, loading or applying Covered Source or another Product + or otherwise. + + 1.6 'Notice' means copyright, acknowledgement and trademark notices, + references to the location of any Notices, modification notices + (subsection 3.3(b)) and all notices that refer to this Licence and to + the disclaimer of warranties that are included in the Covered Source. + + 1.7 'Licensee' or 'You' means any person exercising rights under this + Licence. + + 1.8 'Licensor' means a person who creates Source or modifies Covered Source + and subsequently Conveys the resulting Covered Source under the terms + and conditions of this Licence. A person may be a Licensee and a + Licensor at the same time. + + 1.9 'Convey' means to communicate to the public or distribute. + + +2 Applicability + + 2.1 This Licence governs the use, copying, modification, Conveying of + Covered Source and Products, and the Making of Products. By exercising + any right granted under this Licence, You irrevocably accept these terms + and conditions. + + 2.2 This Licence is granted by the Licensor directly to You, and shall apply + worldwide and without limitation in time. + + 2.3 You shall not attempt to restrict by contract or otherwise the rights + granted under this Licence to other Licensees. + + 2.4 This Licence is not intended to restrict fair use, fair dealing, or any + other similar right. + + +3 Copying, Modifying and Conveying Covered Source + + 3.1 You may copy and Convey verbatim copies of Covered Source, in any + medium, provided You retain all Notices. + + 3.2 You may modify Covered Source, other than Notices. + + You may only delete Notices if they are no longer applicable to the + corresponding Covered Source as modified by You and You may add + additional Notices applicable to Your modifications. + + 3.3 You may Convey modified Covered Source (with the effect that You shall + also become a Licensor) provided that You: + + a) retain Notices as required in subsection 3.2; and + + b) add a Notice to the modified Covered Source stating that You have + modified it, with the date and brief description of how You have + modified it. + + 3.4 You may Convey Covered Source or modified Covered Source under licence + terms which differ from the terms of this Licence provided that You: + + a) comply at all times with subsection 3.3; and + + b) provide a copy of this Licence to anyone to whom You Convey Covered + Source or modified Covered Source. + + +4 Making and Conveying Products + +You may Make Products, and/or Convey them, provided that You ensure that the +recipient of the Product has access to any Notices applicable to the Product. + + +5 DISCLAIMER AND LIABILITY + + 5.1 DISCLAIMER OF WARRANTY -- The Covered Source and any Products are + provided 'as is' and any express or implied warranties, including, but + not limited to, implied warranties of merchantability, of satisfactory + quality, non-infringement of third party rights, and fitness for a + particular purpose or use are disclaimed in respect of any Source or + Product to the maximum extent permitted by law. The Licensor makes no + representation that any Source or Product does not or will not infringe + any patent, copyright, trade secret or other proprietary right. The + entire risk as to the use, quality, and performance of any Source or + Product shall be with You and not the Licensor. This disclaimer of + warranty is an essential part of this Licence and a condition for the + grant of any rights granted under this Licence. + + 5.2 EXCLUSION AND LIMITATION OF LIABILITY -- The Licensor shall, to the + maximum extent permitted by law, have no liability for direct, indirect, + special, incidental, consequential, exemplary, punitive or other damages + of any character including, without limitation, procurement of + substitute goods or services, loss of use, data or profits, or business + interruption, however caused and on any theory of contract, warranty, + tort (including negligence), product liability or otherwise, arising in + any way in relation to the Covered Source, modified Covered Source + and/or the Making or Conveyance of a Product, even if advised of the + possibility of such damages, and You shall hold the Licensor(s) free and + harmless from any liability, costs, damages, fees and expenses, + including claims by third parties, in relation to such use. + + +6 Patents + + 6.1 Subject to the terms and conditions of this Licence, each Licensor + hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, + royalty-free, irrevocable (except as stated in this section 6, or where + terminated by the Licensor for cause) patent licence to Make, have Made, + use, offer to sell, sell, import, and otherwise transfer the Covered + Source and Products, where such licence applies only to those patent + claims licensable by such Licensor that are necessarily infringed by + exercising rights under the Covered Source as Conveyed by that Licensor. + + 6.2 If You institute patent litigation against any entity (including a + cross-claim or counterclaim in a lawsuit) alleging that the Covered + Source or a Product constitutes direct or contributory patent + infringement, or You seek any declaration that a patent licensed to You + under this Licence is invalid or unenforceable then any rights granted + to You under this Licence shall terminate as of the date such process is + initiated. + + +7 General + + 7.1 If any provisions of this Licence are or subsequently become invalid or + unenforceable for any reason, the remaining provisions shall remain + effective. + + 7.2 You shall not use any of the name (including acronyms and + abbreviations), image, or logo by which the Licensor or CERN is known, + except where needed to comply with section 3, or where the use is + otherwise allowed by law. Any such permitted use shall be factual and + shall not be made so as to suggest any kind of endorsement or + implication of involvement by the Licensor or its personnel. + + 7.3 CERN may publish updated versions and variants of this Licence which it + considers to be in the spirit of this version, but may differ in detail + to address new problems or concerns. New versions will be published with + a unique version number and a variant identifier specifying the variant. + If the Licensor has specified that a given variant applies to the + Covered Source without specifying a version, You may treat that Covered + Source as being released under any version of the CERN-OHL with that + variant. If no variant is specified, the Covered Source shall be treated + as being released under CERN-OHL-S. The Licensor may also specify that + the Covered Source is subject to a specific version of the CERN-OHL or + any later version in which case You may apply this or any later version + of CERN-OHL with the same variant identifier published by CERN. + + 7.4 This Licence shall not be enforceable except by a Licensor acting as + such, and third party beneficiary rights are specifically excluded. diff --git a/_licenses/cern-ohl-s-2.0.txt b/_licenses/cern-ohl-s-2.0.txt new file mode 100644 index 0000000..115f9f9 --- /dev/null +++ b/_licenses/cern-ohl-s-2.0.txt @@ -0,0 +1,299 @@ +--- +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 virally, 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). + +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 a license header and copyright notice to the README and source files. CERN provides a User's Guide containing a recommended license header. + +using: + USB Armory: https://github.com/f-secure-foundry/usbarmory/blob/master/hardware/mark-two/LICENSE + waffling60: https://github.com/4pplet/waffling60/blob/master/LICENCE.md + Duet 3 Mainboard 6HC: https://github.com/Duet3D/Duet3-Mainboard-6HC/blob/master/LICENSE + +permissions: + - commercial-use + - modifications + - distribution + - private-use + - patent-use + +conditions: + - include-copyright + - document-changes + - disclose-source + - same-license + +limitations: + - liability + - warranty + +--- +CERN Open Hardware Licence Version 2 - Strongly Reciprocal + + +Preamble + +CERN has developed this licence to promote collaboration among hardware +designers and to provide a legal tool which supports the freedom to use, +study, modify, share and distribute hardware designs and products based on +those designs. Version 2 of the CERN Open Hardware Licence comes in three +variants: CERN-OHL-P (permissive); and two reciprocal licences: CERN-OHL-W +(weakly reciprocal) and this licence, CERN-OHL-S (strongly reciprocal). + +The CERN-OHL-S is copyright CERN 2020. Anyone is welcome to use it, in +unmodified form only. + +Use of this Licence does not imply any endorsement by CERN of any Licensor or +their designs nor does it imply any involvement by CERN in their development. + + +1 Definitions + + 1.1 'Licence' means this CERN-OHL-S. + + 1.2 'Compatible Licence' means + + a) any earlier version of the CERN Open Hardware licence, or + + b) any version of the CERN-OHL-S, or + + c) any licence which permits You to treat the Source to which it + applies as licensed under CERN-OHL-S provided that on Conveyance of + any such Source, or any associated Product You treat the Source in + question as being licensed under CERN-OHL-S. + + 1.3 'Source' means information such as design materials or digital code + which can be applied to Make or test a Product or to prepare a Product + for use, Conveyance or sale, regardless of its medium or how it is + expressed. It may include Notices. + + 1.4 'Covered Source' means Source that is explicitly made available under + this Licence. + + 1.5 'Product' means any device, component, work or physical object, whether + in finished or intermediate form, arising from the use, application or + processing of Covered Source. + + 1.6 'Make' means to create or configure something, whether by manufacture, + assembly, compiling, loading or applying Covered Source or another + Product or otherwise. + + 1.7 'Available Component' means any part, sub-assembly, library or code + which: + + a) is licensed to You as Complete Source under a Compatible Licence; or + + b) is available, at the time a Product or the Source containing it is + first Conveyed, to You and any other prospective licensees + + i) as a physical part with sufficient rights and information + (including any configuration and programming files and + information about its characteristics and interfaces) to enable + it either to be Made itself, or to be sourced and used to Make + the Product; or + ii) as part of the normal distribution of a tool used to design or + Make the Product. + + 1.8 'Complete Source' means the set of all Source necessary to Make a + Product, in the preferred form for making modifications, including + necessary installation and interfacing information both for the Product, + and for any included Available Components. If the format is + proprietary, it must also be made available in a format (if the + proprietary tool can create it) which is viewable with a tool available + to potential licensees and licensed under a licence approved by the Free + Software Foundation or the Open Source Initiative. Complete Source need + not include the Source of any Available Component, provided that You + include in the Complete Source sufficient information to enable a + recipient to Make or source and use the Available Component to Make the + Product. + + 1.9 'Source Location' means a location where a Licensor has placed Covered + Source, and which that Licensor reasonably believes will remain easily + accessible for at least three years for anyone to obtain a digital copy. + + 1.10 'Notice' means copyright, acknowledgement and trademark notices, Source + Location references, modification notices (subsection 3.3(b)) and all + notices that refer to this Licence and to the disclaimer of warranties + that are included in the Covered Source. + + 1.11 'Licensee' or 'You' means any person exercising rights under this + Licence. + + 1.12 'Licensor' means a natural or legal person who creates or modifies + Covered Source. A person may be a Licensee and a Licensor at the same + time. + + 1.13 'Convey' means to communicate to the public or distribute. + + +2 Applicability + + 2.1 This Licence governs the use, copying, modification, Conveying of + Covered Source and Products, and the Making of Products. By exercising + any right granted under this Licence, You irrevocably accept these terms + and conditions. + + 2.2 This Licence is granted by the Licensor directly to You, and shall apply + worldwide and without limitation in time. + + 2.3 You shall not attempt to restrict by contract or otherwise the rights + granted under this Licence to other Licensees. + + 2.4 This Licence is not intended to restrict fair use, fair dealing, or any + other similar right. + + +3 Copying, Modifying and Conveying Covered Source + + 3.1 You may copy and Convey verbatim copies of Covered Source, in any + medium, provided You retain all Notices. + + 3.2 You may modify Covered Source, other than Notices, provided that You + irrevocably undertake to make that modified Covered Source available + from a Source Location should You Convey a Product in circumstances + where the recipient does not otherwise receive a copy of the modified + Covered Source. In each case subsection 3.3 shall apply. + + You may only delete Notices if they are no longer applicable to the + corresponding Covered Source as modified by You and You may add + additional Notices applicable to Your modifications. Including Covered + Source in a larger work is modifying the Covered Source, and the larger + work becomes modified Covered Source. + + 3.3 You may Convey modified Covered Source (with the effect that You shall + also become a Licensor) provided that You: + + a) retain Notices as required in subsection 3.2; + + b) add a Notice to the modified Covered Source stating that You have + modified it, with the date and brief description of how You have + modified it; + + c) add a Source Location Notice for the modified Covered Source if You + Convey in circumstances where the recipient does not otherwise + receive a copy of the modified Covered Source; and + + d) license the modified Covered Source under the terms and conditions + of this Licence (or, as set out in subsection 8.3, a later version, + if permitted by the licence of the original Covered Source). Such + modified Covered Source must be licensed as a whole, but excluding + Available Components contained in it, which remain licensed under + their own applicable licences. + + +4 Making and Conveying Products + +You may Make Products, and/or Convey them, provided that You either provide +each recipient with a copy of the Complete Source or ensure that each +recipient is notified of the Source Location of the Complete Source. That +Complete Source is Covered Source, and You must accordingly satisfy Your +obligations set out in subsection 3.3. If specified in a Notice, the Product +must visibly and securely display the Source Location on it or its packaging +or documentation in the manner specified in that Notice. + + +5 Research and Development + +You may Convey Covered Source, modified Covered Source or Products to a legal +entity carrying out development, testing or quality assurance work on Your +behalf provided that the work is performed on terms which prevent the entity +from both using the Source or Products for its own internal purposes and +Conveying the Source or Products or any modifications to them to any person +other than You. Any modifications made by the entity shall be deemed to be +made by You pursuant to subsection 3.2. + + +6 DISCLAIMER AND LIABILITY + + 6.1 DISCLAIMER OF WARRANTY -- The Covered Source and any Products are + provided 'as is' and any express or implied warranties, including, but + not limited to, implied warranties of merchantability, of satisfactory + quality, non-infringement of third party rights, and fitness for a + particular purpose or use are disclaimed in respect of any Source or + Product to the maximum extent permitted by law. The Licensor makes no + representation that any Source or Product does not or will not infringe + any patent, copyright, trade secret or other proprietary right. The + entire risk as to the use, quality, and performance of any Source or + Product shall be with You and not the Licensor. This disclaimer of + warranty is an essential part of this Licence and a condition for the + grant of any rights granted under this Licence. + + 6.2 EXCLUSION AND LIMITATION OF LIABILITY -- The Licensor shall, to the + maximum extent permitted by law, have no liability for direct, indirect, + special, incidental, consequential, exemplary, punitive or other damages + of any character including, without limitation, procurement of + substitute goods or services, loss of use, data or profits, or business + interruption, however caused and on any theory of contract, warranty, + tort (including negligence), product liability or otherwise, arising in + any way in relation to the Covered Source, modified Covered Source + and/or the Making or Conveyance of a Product, even if advised of the + possibility of such damages, and You shall hold the Licensor(s) free and + harmless from any liability, costs, damages, fees and expenses, + including claims by third parties, in relation to such use. + + +7 Patents + + 7.1 Subject to the terms and conditions of this Licence, each Licensor + hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, + royalty-free, irrevocable (except as stated in subsections 7.2 and 8.4) + patent licence to Make, have Made, use, offer to sell, sell, import, and + otherwise transfer the Covered Source and Products, where such licence + applies only to those patent claims licensable by such Licensor that are + necessarily infringed by exercising rights under the Covered Source as + Conveyed by that Licensor. + + 7.2 If You institute patent litigation against any entity (including a + cross-claim or counterclaim in a lawsuit) alleging that the Covered + Source or a Product constitutes direct or contributory patent + infringement, or You seek any declaration that a patent licensed to You + under this Licence is invalid or unenforceable then any rights granted + to You under this Licence shall terminate as of the date such process is + initiated. + + +8 General + + 8.1 If any provisions of this Licence are or subsequently become invalid or + unenforceable for any reason, the remaining provisions shall remain + effective. + + 8.2 You shall not use any of the name (including acronyms and + abbreviations), image, or logo by which the Licensor or CERN is known, + except where needed to comply with section 3, or where the use is + otherwise allowed by law. Any such permitted use shall be factual and + shall not be made so as to suggest any kind of endorsement or + implication of involvement by the Licensor or its personnel. + + 8.3 CERN may publish updated versions and variants of this Licence which it + considers to be in the spirit of this version, but may differ in detail + to address new problems or concerns. New versions will be published with + a unique version number and a variant identifier specifying the variant. + If the Licensor has specified that a given variant applies to the + Covered Source without specifying a version, You may treat that Covered + Source as being released under any version of the CERN-OHL with that + variant. If no variant is specified, the Covered Source shall be treated + as being released under CERN-OHL-S. The Licensor may also specify that + the Covered Source is subject to a specific version of the CERN-OHL or + any later version in which case You may apply this or any later version + of CERN-OHL with the same variant identifier published by CERN. + + 8.4 This Licence shall terminate with immediate effect if You fail to comply + with any of its terms and conditions. + + 8.5 However, if You cease all breaches of this Licence, then Your Licence + from any Licensor is reinstated unless such Licensor has terminated this + Licence by giving You, while You remain in breach, a notice specifying + the breach and requiring You to cure it within 30 days, and You have + failed to come into compliance in all material respects by the end of + the 30 day period. Should You repeat the breach after receipt of a cure + notice and subsequent reinstatement, this Licence will terminate + immediately and permanently. Section 6 shall continue to apply after any + termination. + + 8.6 This Licence shall not be enforceable except by a Licensor acting as + such, and third party beneficiary rights are specifically excluded. diff --git a/_licenses/cern-ohl-w-2.0.txt b/_licenses/cern-ohl-w-2.0.txt new file mode 100644 index 0000000..45f5bb7 --- /dev/null +++ b/_licenses/cern-ohl-w-2.0.txt @@ -0,0 +1,321 @@ +--- +title: CERN Open Hardware Licence Version 2 - Weakly Reciprocal +spdx-id: CERN-OHL-W-2.0 +nickname: CERN OHL v2 Weakly 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 “Weakly Reciprocal” variant applies to individual designs but does not spread to the entire project it is included in. + +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 a license header and copyright notice to the README and source files. CERN provides a User's Guide containing a recommended license header. + +using: + Simple PCIe FMC carrier: https://ohwr.org/project/spec/blob/master/LICENSES/CERN-OHL-W-2.0.txt + GProcessor8Bits: https://github.com/JonathSpirit/GP8B/blob/master/LICENSE + FPGA Cores: https://github.com/suoto/fpga_cores/blob/master/LICENSE + +permissions: + - commercial-use + - modifications + - distribution + - private-use + - patent-use + +conditions: + - include-copyright + - document-changes + - disclose-source + - same-license--file + +limitations: + - liability + - warranty + +--- +CERN Open Hardware Licence Version 2 - Weakly Reciprocal + + +Preamble + +CERN has developed this licence to promote collaboration among hardware +designers and to provide a legal tool which supports the freedom to use, +study, modify, share and distribute hardware designs and products based on +those designs. Version 2 of the CERN Open Hardware Licence comes in three +variants: CERN-OHL-P (permissive); and two reciprocal licences: this licence, +CERN-OHL-W (weakly reciprocal) and CERN-OHL-S (strongly reciprocal). + +The CERN-OHL-W is copyright CERN 2020. Anyone is welcome to use it, in +unmodified form only. + +Use of this Licence does not imply any endorsement by CERN of any Licensor or +their designs nor does it imply any involvement by CERN in their development. + + +1 Definitions + + 1.1 'Licence' means this CERN-OHL-W. + + 1.2 'Compatible Licence' means + + a) any earlier version of the CERN Open Hardware licence, or + + b) any version of the CERN-OHL-S or the CERN-OHL-W, or + + c) any licence which permits You to treat the Source to which it + applies as licensed under CERN-OHL-S or CERN-OHL-W provided that on + Conveyance of any such Source, or any associated Product You treat + the Source in question as being licensed under CERN-OHL-S or + CERN-OHL-W as appropriate. + + 1.3 'Source' means information such as design materials or digital code + which can be applied to Make or test a Product or to prepare a Product + for use, Conveyance or sale, regardless of its medium or how it is + expressed. It may include Notices. + + 1.4 'Covered Source' means Source that is explicitly made available under + this Licence. + + 1.5 'Product' means any device, component, work or physical object, whether + in finished or intermediate form, arising from the use, application or + processing of Covered Source. + + 1.6 'Make' means to create or configure something, whether by manufacture, + assembly, compiling, loading or applying Covered Source or another + Product or otherwise. + + 1.7 'Available Component' means any part, sub-assembly, library or code + which: + + a) is licensed to You as Complete Source under a Compatible Licence; or + + b) is available, at the time a Product or the Source containing it is + first Conveyed, to You and any other prospective licensees + + i) with sufficient rights and information (including any + configuration and programming files and information about its + characteristics and interfaces) to enable it either to be Made + itself, or to be sourced and used to Make the Product; or + ii) as part of the normal distribution of a tool used to design or + Make the Product. + + 1.8 'External Material' means anything (including Source) which: + + a) is only combined with Covered Source in such a way that it + interfaces with the Covered Source using a documented interface + which is described in the Covered Source; and + + b) is not a derivative of or contains Covered Source, or, if it is, it + is solely to the extent necessary to facilitate such interfacing. + + 1.9 'Complete Source' means the set of all Source necessary to Make a + Product, in the preferred form for making modifications, including + necessary installation and interfacing information both for the Product, + and for any included Available Components. If the format is + proprietary, it must also be made available in a format (if the + proprietary tool can create it) which is viewable with a tool available + to potential licensees and licensed under a licence approved by the Free + Software Foundation or the Open Source Initiative. Complete Source need + not include the Source of any Available Component, provided that You + include in the Complete Source sufficient information to enable a + recipient to Make or source and use the Available Component to Make the + Product. + + 1.10 'Source Location' means a location where a Licensor has placed Covered + Source, and which that Licensor reasonably believes will remain easily + accessible for at least three years for anyone to obtain a digital copy. + + 1.11 'Notice' means copyright, acknowledgement and trademark notices, Source + Location references, modification notices (subsection 3.3(b)) and all + notices that refer to this Licence and to the disclaimer of warranties + that are included in the Covered Source. + + 1.12 'Licensee' or 'You' means any person exercising rights under this + Licence. + + 1.13 'Licensor' means a natural or legal person who creates or modifies + Covered Source. A person may be a Licensee and a Licensor at the same + time. + + 1.14 'Convey' means to communicate to the public or distribute. + + +2 Applicability + + 2.1 This Licence governs the use, copying, modification, Conveying of + Covered Source and Products, and the Making of Products. By exercising + any right granted under this Licence, You irrevocably accept these terms + and conditions. + + 2.2 This Licence is granted by the Licensor directly to You, and shall apply + worldwide and without limitation in time. + + 2.3 You shall not attempt to restrict by contract or otherwise the rights + granted under this Licence to other Licensees. + + 2.4 This Licence is not intended to restrict fair use, fair dealing, or any + other similar right. + + +3 Copying, Modifying and Conveying Covered Source + + 3.1 You may copy and Convey verbatim copies of Covered Source, in any + medium, provided You retain all Notices. + + 3.2 You may modify Covered Source, other than Notices, provided that You + irrevocably undertake to make that modified Covered Source available + from a Source Location should You Convey a Product in circumstances + where the recipient does not otherwise receive a copy of the modified + Covered Source. In each case subsection 3.3 shall apply. + + You may only delete Notices if they are no longer applicable to the + corresponding Covered Source as modified by You and You may add + additional Notices applicable to Your modifications. + + 3.3 You may Convey modified Covered Source (with the effect that You shall + also become a Licensor) provided that You: + + a) retain Notices as required in subsection 3.2; + + b) add a Notice to the modified Covered Source stating that You have + modified it, with the date and brief description of how You have + modified it; + + c) add a Source Location Notice for the modified Covered Source if You + Convey in circumstances where the recipient does not otherwise + receive a copy of the modified Covered Source; and + + d) license the modified Covered Source under the terms and conditions + of this Licence (or, as set out in subsection 8.3, a later version, + if permitted by the licence of the original Covered Source). Such + modified Covered Source must be licensed as a whole, but excluding + Available Components contained in it or External Material to which + it is interfaced, which remain licensed under their own applicable + licences. + + +4 Making and Conveying Products + + 4.1 You may Make Products, and/or Convey them, provided that You either + provide each recipient with a copy of the Complete Source or ensure that + each recipient is notified of the Source Location of the Complete + Source. That Complete Source includes Covered Source and You must + accordingly satisfy Your obligations set out in subsection 3.3. If + specified in a Notice, the Product must visibly and securely display the + Source Location on it or its packaging or documentation in the manner + specified in that Notice. + + 4.2 Where You Convey a Product which incorporates External Material, the + Complete Source for that Product which You are required to provide under + subsection 4.1 need not include any Source for the External Material. + + 4.3 You may license Products under terms of Your choice, provided that such + terms do not restrict or attempt to restrict any recipients' rights + under this Licence to the Covered Source. + + +5 Research and Development + +You may Convey Covered Source, modified Covered Source or Products to a legal +entity carrying out development, testing or quality assurance work on Your +behalf provided that the work is performed on terms which prevent the entity +from both using the Source or Products for its own internal purposes and +Conveying the Source or Products or any modifications to them to any person +other than You. Any modifications made by the entity shall be deemed to be +made by You pursuant to subsection 3.2. + + +6 DISCLAIMER AND LIABILITY + + 6.1 DISCLAIMER OF WARRANTY -- The Covered Source and any Products are + provided 'as is' and any express or implied warranties, including, but + not limited to, implied warranties of merchantability, of satisfactory + quality, non-infringement of third party rights, and fitness for a + particular purpose or use are disclaimed in respect of any Source or + Product to the maximum extent permitted by law. The Licensor makes no + representation that any Source or Product does not or will not infringe + any patent, copyright, trade secret or other proprietary right. The + entire risk as to the use, quality, and performance of any Source or + Product shall be with You and not the Licensor. This disclaimer of + warranty is an essential part of this Licence and a condition for the + grant of any rights granted under this Licence. + + 6.2 EXCLUSION AND LIMITATION OF LIABILITY -- The Licensor shall, to the + maximum extent permitted by law, have no liability for direct, indirect, + special, incidental, consequential, exemplary, punitive or other damages + of any character including, without limitation, procurement of + substitute goods or services, loss of use, data or profits, or business + interruption, however caused and on any theory of contract, warranty, + tort (including negligence), product liability or otherwise, arising in + any way in relation to the Covered Source, modified Covered Source + and/or the Making or Conveyance of a Product, even if advised of the + possibility of such damages, and You shall hold the Licensor(s) free and + harmless from any liability, costs, damages, fees and expenses, + including claims by third parties, in relation to such use. + + +7 Patents + + 7.1 Subject to the terms and conditions of this Licence, each Licensor + hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, + royalty-free, irrevocable (except as stated in subsections 7.2 and 8.4) + patent licence to Make, have Made, use, offer to sell, sell, import, and + otherwise transfer the Covered Source and Products, where such licence + applies only to those patent claims licensable by such Licensor that are + necessarily infringed by exercising rights under the Covered Source as + Conveyed by that Licensor. + + 7.2 If You institute patent litigation against any entity (including a + cross-claim or counterclaim in a lawsuit) alleging that the Covered + Source or a Product constitutes direct or contributory patent + infringement, or You seek any declaration that a patent licensed to You + under this Licence is invalid or unenforceable then any rights granted + to You under this Licence shall terminate as of the date such process is + initiated. + + +8 General + + 8.1 If any provisions of this Licence are or subsequently become invalid or + unenforceable for any reason, the remaining provisions shall remain + effective. + + 8.2 You shall not use any of the name (including acronyms and + abbreviations), image, or logo by which the Licensor or CERN is known, + except where needed to comply with section 3, or where the use is + otherwise allowed by law. Any such permitted use shall be factual and + shall not be made so as to suggest any kind of endorsement or + implication of involvement by the Licensor or its personnel. + + 8.3 CERN may publish updated versions and variants of this Licence which it + considers to be in the spirit of this version, but may differ in detail + to address new problems or concerns. New versions will be published with + a unique version number and a variant identifier specifying the variant. + If the Licensor has specified that a given variant applies to the + Covered Source without specifying a version, You may treat that Covered + Source as being released under any version of the CERN-OHL with that + variant. If no variant is specified, the Covered Source shall be treated + as being released under CERN-OHL-S. The Licensor may also specify that + the Covered Source is subject to a specific version of the CERN-OHL or + any later version in which case You may apply this or any later version + of CERN-OHL with the same variant identifier published by CERN. + + You may treat Covered Source licensed under CERN-OHL-W as licensed under + CERN-OHL-S if and only if all Available Components referenced in the + Covered Source comply with the corresponding definition of Available + Component for CERN-OHL-S. + + 8.4 This Licence shall terminate with immediate effect if You fail to comply + with any of its terms and conditions. + + 8.5 However, if You cease all breaches of this Licence, then Your Licence + from any Licensor is reinstated unless such Licensor has terminated this + Licence by giving You, while You remain in breach, a notice specifying + the breach and requiring You to cure it within 30 days, and You have + failed to come into compliance in all material respects by the end of + the 30 day period. Should You repeat the breach after receipt of a cure + notice and subsequent reinstatement, this Licence will terminate + immediately and permanently. Section 6 shall continue to apply after any + termination. + + 8.6 This Licence shall not be enforceable except by a Licensor acting as + such, and third party beneficiary rights are specifically excluded. From 6e0063e56cde2837e16d0498a6e88b2d12469ec0 Mon Sep 17 00:00:00 2001 From: nytpu Date: Mon, 23 Aug 2021 17:22:49 -0600 Subject: [PATCH 02/70] Add Hardware section to the Non-Software Licenses page Recommended the CERN OHL v2 family of licenses and linked to software licenses with similar terms. Also added mention of the Creative Commons licenses often used for hardware. --- non-software.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/non-software.md b/non-software.md index 8335012..2c83d72 100644 --- a/non-software.md +++ b/non-software.md @@ -18,6 +18,14 @@ Any open source software license or open license for media (see [above](#data-me The [SIL Open Font License 1.1](/licenses/ofl-1.1/) keeps fonts open, allowing them to be freely used in other works. +### Hardware + +There are the CERN Open Hardware family of licenses: [CERN-OHL-P-2.0](/licenses/cern-ohl-p-2.0/) (Permissive, [MIT](/licenses/mit/)-like), [CERN-OHL-W-2.0](/licenses/cern-ohl-w-2.0/) (Weakly reciprocal, [MPL](/licenses/mpl-2.0/)-like), and [cern-ohl-s-2.0](/licenses/cern-ohl-s-2.0/) (Strongly reciprocal, [GPL](/licenses/gpl-3.0/)-like). The CERN OHL family is also applicable to HDL source code and programmable hardware such as FPGA bitstreams. + +[CC-BY-4.0](/licenses/cc-by-4.0/) and [CC-BY-SA-4.0](/licenses/cc-by-sa-4.0/) are also commonly used for hardware; however they do not grant patent rights which restricts usage of patent-encumbered hardware licensed under them. + +If your hardware has accompanying software then be sure to specify a license for the software portion as well as the hardware portion. + ### Mixed projects If your project contains a mix of software and other material, you can include multiple licenses, as long as you are explicit about which license applies to each part of the project. See [the license notice for this site](https://github.com/github/choosealicense.com#license) as an example. From 9afc07e19c4aa9bdacd86b7a161c327d436c2d9e Mon Sep 17 00:00:00 2001 From: nytpu Date: Tue, 24 Aug 2021 08:43:52 -0600 Subject: [PATCH 03/70] Fix typos and expand reasoning in non-software --- non-software.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/non-software.md b/non-software.md index 2c83d72..7709ca7 100644 --- a/non-software.md +++ b/non-software.md @@ -20,9 +20,9 @@ The [SIL Open Font License 1.1](/licenses/ofl-1.1/) keeps fonts open, allowing t ### Hardware -There are the CERN Open Hardware family of licenses: [CERN-OHL-P-2.0](/licenses/cern-ohl-p-2.0/) (Permissive, [MIT](/licenses/mit/)-like), [CERN-OHL-W-2.0](/licenses/cern-ohl-w-2.0/) (Weakly reciprocal, [MPL](/licenses/mpl-2.0/)-like), and [cern-ohl-s-2.0](/licenses/cern-ohl-s-2.0/) (Strongly reciprocal, [GPL](/licenses/gpl-3.0/)-like). The CERN OHL family is also applicable to HDL source code and programmable hardware such as FPGA bitstreams. +There are the CERN Open Hardware family of licenses: [CERN-OHL-P-2.0](/licenses/cern-ohl-p-2.0/), the permissive variant ([MIT](/licenses/mit/)-like); [CERN-OHL-W-2.0](/licenses/cern-ohl-w-2.0/), the “weakly reciprocal” variant ([MPL](/licenses/mpl-2.0/)-like), and [CERN-OHL-S-2.0](/licenses/cern-ohl-s-2.0/), the “strongly reciprocal” variant ([GPL](/licenses/gpl-3.0/)-like). The CERN OHL family is also applicable to HDL source code and synthesized bitstreams as would be used in FPGAs. -[CC-BY-4.0](/licenses/cc-by-4.0/) and [CC-BY-SA-4.0](/licenses/cc-by-sa-4.0/) are also commonly used for hardware; however they do not grant patent rights which restricts usage of patent-encumbered hardware licensed under them. +[CC-BY-4.0](/licenses/cc-by-4.0/) and [CC-BY-SA-4.0](/licenses/cc-by-sa-4.0/) are also commonly used for hardware; however they do not grant patent rights which can restrict usage of patent-encumbered hardware licensed under them and Creative Commons does not recommend them for hardware. If your hardware has accompanying software then be sure to specify a license for the software portion as well as the hardware portion. From 8d4b35ef9409216df7b43448036dedabfa37c633 Mon Sep 17 00:00:00 2001 From: nytpu Date: Tue, 24 Aug 2021 09:55:11 -0600 Subject: [PATCH 04/70] fix license wrapping --- _licenses/cern-ohl-p-2.0.txt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/_licenses/cern-ohl-p-2.0.txt b/_licenses/cern-ohl-p-2.0.txt index 0340156..262034f 100644 --- a/_licenses/cern-ohl-p-2.0.txt +++ b/_licenses/cern-ohl-p-2.0.txt @@ -66,8 +66,8 @@ their designs nor does it imply any involvement by CERN in their development. processing of Covered Source. 1.5 'Make' means to create or configure something, whether by manufacture, - assembly, compiling, loading or applying Covered Source or another Product - or otherwise. + assembly, compiling, loading or applying Covered Source or another + Product or otherwise. 1.6 'Notice' means copyright, acknowledgement and trademark notices, references to the location of any Notices, modification notices From da312bcaa9cf27dacafd54cefe803390c2449923 Mon Sep 17 00:00:00 2001 From: nytpu Date: Tue, 24 Aug 2021 09:58:37 -0600 Subject: [PATCH 05/70] add ohwr.org to license_meta_spec.rb --- spec/license_meta_spec.rb | 2 ++ 1 file changed, 2 insertions(+) diff --git a/spec/license_meta_spec.rb b/spec/license_meta_spec.rb index de1d55a..de6a730 100644 --- a/spec/license_meta_spec.rb +++ b/spec/license_meta_spec.rb @@ -53,6 +53,8 @@ describe 'license meta' do example_url.gsub!(%r{/tree/}, '/plain/') elsif example_url.start_with?('https://bitbucket.org/') example_url.gsub!(%r{/src/}, '/raw/') + elsif example_url.start_with?('https://ohwr.org/') + example_url.gsub!(%r{/blob/}, '/raw/') end it "is a #{slug} license" do From 1a37894edb35cdee650db8192e095c62f01b2c5c Mon Sep 17 00:00:00 2001 From: Tyler887 Date: Wed, 16 Mar 2022 16:43:17 +0000 Subject: [PATCH 06/70] .NET Core > .NET --- _licenses/mit.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_licenses/mit.txt b/_licenses/mit.txt index 79d306c..bbee53e 100644 --- a/_licenses/mit.txt +++ b/_licenses/mit.txt @@ -10,7 +10,7 @@ how: Create a text file (typically named LICENSE or LICENSE.txt) in the root of using: Babel: https://github.com/babel/babel/blob/master/LICENSE - .NET Core: https://github.com/dotnet/runtime/blob/master/LICENSE.TXT + .NET: https://github.com/dotnet/runtime/blob/master/LICENSE.TXT Rails: https://github.com/rails/rails/blob/master/MIT-LICENSE permissions: From d91f364d2ce30201d712dd065437339a70cca9f1 Mon Sep 17 00:00:00 2001 From: Tyler887 Date: Wed, 16 Mar 2022 22:38:38 +0000 Subject: [PATCH 07/70] Update _licenses/mit.txt Co-authored-by: Mike Linksvayer --- _licenses/mit.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_licenses/mit.txt b/_licenses/mit.txt index bbee53e..1ad0488 100644 --- a/_licenses/mit.txt +++ b/_licenses/mit.txt @@ -10,7 +10,7 @@ how: Create a text file (typically named LICENSE or LICENSE.txt) in the root of using: Babel: https://github.com/babel/babel/blob/master/LICENSE - .NET: https://github.com/dotnet/runtime/blob/master/LICENSE.TXT + .NET: https://github.com/dotnet/runtime/blob/main/LICENSE.TXT Rails: https://github.com/rails/rails/blob/master/MIT-LICENSE permissions: From 639dac9dc52678b5f6063ad95e6e5f99e5708556 Mon Sep 17 00:00:00 2001 From: Mike Linksvayer Date: Wed, 16 Mar 2022 16:08:34 -0700 Subject: [PATCH 08/70] Fix EUPL-1.1 guidance link --- _licenses/eupl-1.1.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_licenses/eupl-1.1.txt b/_licenses/eupl-1.1.txt index b2512b7..c174eb0 100644 --- a/_licenses/eupl-1.1.txt +++ b/_licenses/eupl-1.1.txt @@ -7,7 +7,7 @@ description: The “European Union Public Licence” (EUPL) is a copyleft free/o how: Create a text file (typically named COPYING or LICENCE.txt) in the root of your source code and copy the text of the license into the file. -note: The European Commission recommends taking the additional step of adding a [boilerplate notice](https://joinup.ec.europa.eu/sites/default/files/ckeditor_files/files/EUPL%201_1%20Guidelines%20EN%20Joinup.pdf#page=17) to the top of each file. +note: The European Commission recommends taking the additional step of adding a [boilerplate notice](https://joinup.ec.europa.eu/sites/default/files/inline-files/EUPL%201_1%20Guidelines%20EN%20Joinup.pdf#page=17) to the top of each file. using: From 835f8c1e99baff7ac91f347e11da4aeb22f1edb2 Mon Sep 17 00:00:00 2001 From: Tyler887 Date: Sat, 1 Jan 2022 19:23:13 +0000 Subject: [PATCH 09/70] Create gfdl-1.3.txt --- _licenses/gfdl-1.3.txt | 473 +++++++++++++++++++++++++++++++++++++++++ 1 file changed, 473 insertions(+) create mode 100644 _licenses/gfdl-1.3.txt diff --git a/_licenses/gfdl-1.3.txt b/_licenses/gfdl-1.3.txt new file mode 100644 index 0000000..f0b4627 --- /dev/null +++ b/_licenses/gfdl-1.3.txt @@ -0,0 +1,473 @@ +--- +title: GNU Free Documentation License 1.3 +nickname: GNU FDL 1.3 +spdx-id: GFDL-1.3 + +description: A free but copyleft license for software documentation that allows almost any use. The Free Software Foundation does not reccommend using the GPL on documentation. Contributors provide an express grant of patent rights. +how: Create a text file (typically named COPYING, as per GNU conventions) in the root of your source code and copy the text of the license into the file. + +note: The Free Software Foundation recommends taking the additional step of adding a boilerplate notice to the top of each file. The boilerplate can be found at the end of the license. + +permissions: + - commercial-use + - modifications + - distribution + - patent-use + - private-use +conditions: + - include-copyright + - disclose-source + - same-license + - document-changes +--- + + GNU Free Documentation License + Version 1.3, 3 November 2008 + + + Copyright (C) 2000, 2001, 2002, 2007, 2008 Free Software Foundation, Inc. + + Everyone is permitted to copy and distribute verbatim copies + of this license document, but changing it is not allowed. + +0. PREAMBLE + +The purpose of this License is to make a manual, textbook, or other +functional and useful document "free" in the sense of freedom: to +assure everyone the effective freedom to copy and redistribute it, +with or without modifying it, either commercially or noncommercially. +Secondarily, this License preserves for the author and publisher a way +to get credit for their work, while not being considered responsible +for modifications made by others. + +This License is a kind of "copyleft", which means that derivative +works of the document must themselves be free in the same sense. It +complements the GNU General Public License, which is a copyleft +license designed for free software. + +We have designed this License in order to use it for manuals for free +software, because free software needs free documentation: a free +program should come with manuals providing the same freedoms that the +software does. But this License is not limited to software manuals; +it can be used for any textual work, regardless of subject matter or +whether it is published as a printed book. We recommend this License +principally for works whose purpose is instruction or reference. + + +1. APPLICABILITY AND DEFINITIONS + +This License applies to any manual or other work, in any medium, that +contains a notice placed by the copyright holder saying it can be +distributed under the terms of this License. Such a notice grants a +world-wide, royalty-free license, unlimited in duration, to use that +work under the conditions stated herein. The "Document", below, +refers to any such manual or work. Any member of the public is a +licensee, and is addressed as "you". You accept the license if you +copy, modify or distribute the work in a way requiring permission +under copyright law. + +A "Modified Version" of the Document means any work containing the +Document or a portion of it, either copied verbatim, or with +modifications and/or translated into another language. + +A "Secondary Section" is a named appendix or a front-matter section of +the Document that deals exclusively with the relationship of the +publishers or authors of the Document to the Document's overall +subject (or to related matters) and contains nothing that could fall +directly within that overall subject. (Thus, if the Document is in +part a textbook of mathematics, a Secondary Section may not explain +any mathematics.) The relationship could be a matter of historical +connection with the subject or with related matters, or of legal, +commercial, philosophical, ethical or political position regarding +them. + +The "Invariant Sections" are certain Secondary Sections whose titles +are designated, as being those of Invariant Sections, in the notice +that says that the Document is released under this License. If a +section does not fit the above definition of Secondary then it is not +allowed to be designated as Invariant. The Document may contain zero +Invariant Sections. If the Document does not identify any Invariant +Sections then there are none. + +The "Cover Texts" are certain short passages of text that are listed, +as Front-Cover Texts or Back-Cover Texts, in the notice that says that +the Document is released under this License. A Front-Cover Text may +be at most 5 words, and a Back-Cover Text may be at most 25 words. + +A "Transparent" copy of the Document means a machine-readable copy, +represented in a format whose specification is available to the +general public, that is suitable for revising the document +straightforwardly with generic text editors or (for images composed of +pixels) generic paint programs or (for drawings) some widely available +drawing editor, and that is suitable for input to text formatters or +for automatic translation to a variety of formats suitable for input +to text formatters. A copy made in an otherwise Transparent file +format whose markup, or absence of markup, has been arranged to thwart +or discourage subsequent modification by readers is not Transparent. +An image format is not Transparent if used for any substantial amount +of text. A copy that is not "Transparent" is called "Opaque". + +Examples of suitable formats for Transparent copies include plain +ASCII without markup, Texinfo input format, LaTeX input format, SGML +or XML using a publicly available DTD, and standard-conforming simple +HTML, PostScript or PDF designed for human modification. Examples of +transparent image formats include PNG, XCF and JPG. Opaque formats +include proprietary formats that can be read and edited only by +proprietary word processors, SGML or XML for which the DTD and/or +processing tools are not generally available, and the +machine-generated HTML, PostScript or PDF produced by some word +processors for output purposes only. + +The "Title Page" means, for a printed book, the title page itself, +plus such following pages as are needed to hold, legibly, the material +this License requires to appear in the title page. For works in +formats which do not have any title page as such, "Title Page" means +the text near the most prominent appearance of the work's title, +preceding the beginning of the body of the text. + +The "publisher" means any person or entity that distributes copies of +the Document to the public. + +A section "Entitled XYZ" means a named subunit of the Document whose +title either is precisely XYZ or contains XYZ in parentheses following +text that translates XYZ in another language. (Here XYZ stands for a +specific section name mentioned below, such as "Acknowledgements", +"Dedications", "Endorsements", or "History".) To "Preserve the Title" +of such a section when you modify the Document means that it remains a +section "Entitled XYZ" according to this definition. + +The Document may include Warranty Disclaimers next to the notice which +states that this License applies to the Document. These Warranty +Disclaimers are considered to be included by reference in this +License, but only as regards disclaiming warranties: any other +implication that these Warranty Disclaimers may have is void and has +no effect on the meaning of this License. + +2. VERBATIM COPYING + +You may copy and distribute the Document in any medium, either +commercially or noncommercially, provided that this License, the +copyright notices, and the license notice saying this License applies +to the Document are reproduced in all copies, and that you add no +other conditions whatsoever to those of this License. You may not use +technical measures to obstruct or control the reading or further +copying of the copies you make or distribute. However, you may accept +compensation in exchange for copies. If you distribute a large enough +number of copies you must also follow the conditions in section 3. + +You may also lend copies, under the same conditions stated above, and +you may publicly display copies. + + +3. COPYING IN QUANTITY + +If you publish printed copies (or copies in media that commonly have +printed covers) of the Document, numbering more than 100, and the +Document's license notice requires Cover Texts, you must enclose the +copies in covers that carry, clearly and legibly, all these Cover +Texts: Front-Cover Texts on the front cover, and Back-Cover Texts on +the back cover. Both covers must also clearly and legibly identify +you as the publisher of these copies. The front cover must present +the full title with all words of the title equally prominent and +visible. You may add other material on the covers in addition. +Copying with changes limited to the covers, as long as they preserve +the title of the Document and satisfy these conditions, can be treated +as verbatim copying in other respects. + +If the required texts for either cover are too voluminous to fit +legibly, you should put the first ones listed (as many as fit +reasonably) on the actual cover, and continue the rest onto adjacent +pages. + +If you publish or distribute Opaque copies of the Document numbering +more than 100, you must either include a machine-readable Transparent +copy along with each Opaque copy, or state in or with each Opaque copy +a computer-network location from which the general network-using +public has access to download using public-standard network protocols +a complete Transparent copy of the Document, free of added material. +If you use the latter option, you must take reasonably prudent steps, +when you begin distribution of Opaque copies in quantity, to ensure +that this Transparent copy will remain thus accessible at the stated +location until at least one year after the last time you distribute an +Opaque copy (directly or through your agents or retailers) of that +edition to the public. + +It is requested, but not required, that you contact the authors of the +Document well before redistributing any large number of copies, to +give them a chance to provide you with an updated version of the +Document. + + +4. MODIFICATIONS + +You may copy and distribute a Modified Version of the Document under +the conditions of sections 2 and 3 above, provided that you release +the Modified Version under precisely this License, with the Modified +Version filling the role of the Document, thus licensing distribution +and modification of the Modified Version to whoever possesses a copy +of it. In addition, you must do these things in the Modified Version: + +A. Use in the Title Page (and on the covers, if any) a title distinct + from that of the Document, and from those of previous versions + (which should, if there were any, be listed in the History section + of the Document). You may use the same title as a previous version + if the original publisher of that version gives permission. +B. List on the Title Page, as authors, one or more persons or entities + responsible for authorship of the modifications in the Modified + Version, together with at least five of the principal authors of the + Document (all of its principal authors, if it has fewer than five), + unless they release you from this requirement. +C. State on the Title page the name of the publisher of the + Modified Version, as the publisher. +D. Preserve all the copyright notices of the Document. +E. Add an appropriate copyright notice for your modifications + adjacent to the other copyright notices. +F. Include, immediately after the copyright notices, a license notice + giving the public permission to use the Modified Version under the + terms of this License, in the form shown in the Addendum below. +G. Preserve in that license notice the full lists of Invariant Sections + and required Cover Texts given in the Document's license notice. +H. Include an unaltered copy of this License. +I. Preserve the section Entitled "History", Preserve its Title, and add + to it an item stating at least the title, year, new authors, and + publisher of the Modified Version as given on the Title Page. If + there is no section Entitled "History" in the Document, create one + stating the title, year, authors, and publisher of the Document as + given on its Title Page, then add an item describing the Modified + Version as stated in the previous sentence. +J. Preserve the network location, if any, given in the Document for + public access to a Transparent copy of the Document, and likewise + the network locations given in the Document for previous versions + it was based on. These may be placed in the "History" section. + You may omit a network location for a work that was published at + least four years before the Document itself, or if the original + publisher of the version it refers to gives permission. +K. For any section Entitled "Acknowledgements" or "Dedications", + Preserve the Title of the section, and preserve in the section all + the substance and tone of each of the contributor acknowledgements + and/or dedications given therein. +L. Preserve all the Invariant Sections of the Document, + unaltered in their text and in their titles. Section numbers + or the equivalent are not considered part of the section titles. +M. Delete any section Entitled "Endorsements". Such a section + may not be included in the Modified Version. +N. Do not retitle any existing section to be Entitled "Endorsements" + or to conflict in title with any Invariant Section. +O. Preserve any Warranty Disclaimers. + +If the Modified Version includes new front-matter sections or +appendices that qualify as Secondary Sections and contain no material +copied from the Document, you may at your option designate some or all +of these sections as invariant. To do this, add their titles to the +list of Invariant Sections in the Modified Version's license notice. +These titles must be distinct from any other section titles. + +You may add a section Entitled "Endorsements", provided it contains +nothing but endorsements of your Modified Version by various +parties--for example, statements of peer review or that the text has +been approved by an organization as the authoritative definition of a +standard. + +You may add a passage of up to five words as a Front-Cover Text, and a +passage of up to 25 words as a Back-Cover Text, to the end of the list +of Cover Texts in the Modified Version. Only one passage of +Front-Cover Text and one of Back-Cover Text may be added by (or +through arrangements made by) any one entity. If the Document already +includes a cover text for the same cover, previously added by you or +by arrangement made by the same entity you are acting on behalf of, +you may not add another; but you may replace the old one, on explicit +permission from the previous publisher that added the old one. + +The author(s) and publisher(s) of the Document do not by this License +give permission to use their names for publicity for or to assert or +imply endorsement of any Modified Version. + + +5. COMBINING DOCUMENTS + +You may combine the Document with other documents released under this +License, under the terms defined in section 4 above for modified +versions, provided that you include in the combination all of the +Invariant Sections of all of the original documents, unmodified, and +list them all as Invariant Sections of your combined work in its +license notice, and that you preserve all their Warranty Disclaimers. + +The combined work need only contain one copy of this License, and +multiple identical Invariant Sections may be replaced with a single +copy. If there are multiple Invariant Sections with the same name but +different contents, make the title of each such section unique by +adding at the end of it, in parentheses, the name of the original +author or publisher of that section if known, or else a unique number. +Make the same adjustment to the section titles in the list of +Invariant Sections in the license notice of the combined work. + +In the combination, you must combine any sections Entitled "History" +in the various original documents, forming one section Entitled +"History"; likewise combine any sections Entitled "Acknowledgements", +and any sections Entitled "Dedications". You must delete all sections +Entitled "Endorsements". + + +6. COLLECTIONS OF DOCUMENTS + +You may make a collection consisting of the Document and other +documents released under this License, and replace the individual +copies of this License in the various documents with a single copy +that is included in the collection, provided that you follow the rules +of this License for verbatim copying of each of the documents in all +other respects. + +You may extract a single document from such a collection, and +distribute it individually under this License, provided you insert a +copy of this License into the extracted document, and follow this +License in all other respects regarding verbatim copying of that +document. + + +7. AGGREGATION WITH INDEPENDENT WORKS + +A compilation of the Document or its derivatives with other separate +and independent documents or works, in or on a volume of a storage or +distribution medium, is called an "aggregate" if the copyright +resulting from the compilation is not used to limit the legal rights +of the compilation's users beyond what the individual works permit. +When the Document is included in an aggregate, this License does not +apply to the other works in the aggregate which are not themselves +derivative works of the Document. + +If the Cover Text requirement of section 3 is applicable to these +copies of the Document, then if the Document is less than one half of +the entire aggregate, the Document's Cover Texts may be placed on +covers that bracket the Document within the aggregate, or the +electronic equivalent of covers if the Document is in electronic form. +Otherwise they must appear on printed covers that bracket the whole +aggregate. + + +8. TRANSLATION + +Translation is considered a kind of modification, so you may +distribute translations of the Document under the terms of section 4. +Replacing Invariant Sections with translations requires special +permission from their copyright holders, but you may include +translations of some or all Invariant Sections in addition to the +original versions of these Invariant Sections. You may include a +translation of this License, and all the license notices in the +Document, and any Warranty Disclaimers, provided that you also include +the original English version of this License and the original versions +of those notices and disclaimers. In case of a disagreement between +the translation and the original version of this License or a notice +or disclaimer, the original version will prevail. + +If a section in the Document is Entitled "Acknowledgements", +"Dedications", or "History", the requirement (section 4) to Preserve +its Title (section 1) will typically require changing the actual +title. + + +9. TERMINATION + +You may not copy, modify, sublicense, or distribute the Document +except as expressly provided under this License. Any attempt +otherwise to copy, modify, sublicense, or distribute it is void, and +will automatically terminate your rights under this License. + +However, if you cease all violation of this License, then your license +from a particular copyright holder is reinstated (a) provisionally, +unless and until the copyright holder explicitly and finally +terminates your license, and (b) permanently, if the copyright holder +fails to notify you of the violation by some reasonable means prior to +60 days after the cessation. + +Moreover, your license from a particular copyright holder is +reinstated permanently if the copyright holder notifies you of the +violation by some reasonable means, this is the first time you have +received notice of violation of this License (for any work) from that +copyright holder, and you cure the violation prior to 30 days after +your receipt of the notice. + +Termination of your rights under this section does not terminate the +licenses of parties who have received copies or rights from you under +this License. If your rights have been terminated and not permanently +reinstated, receipt of a copy of some or all of the same material does +not give you any rights to use it. + + +10. FUTURE REVISIONS OF THIS LICENSE + +The Free Software Foundation may publish new, revised versions of the +GNU Free Documentation License from time to time. Such new versions +will be similar in spirit to the present version, but may differ in +detail to address new problems or concerns. See +https://www.gnu.org/licenses/. + +Each version of the License is given a distinguishing version number. +If the Document specifies that a particular numbered version of this +License "or any later version" applies to it, you have the option of +following the terms and conditions either of that specified version or +of any later version that has been published (not as a draft) by the +Free Software Foundation. If the Document does not specify a version +number of this License, you may choose any version ever published (not +as a draft) by the Free Software Foundation. If the Document +specifies that a proxy can decide which future versions of this +License can be used, that proxy's public statement of acceptance of a +version permanently authorizes you to choose that version for the +Document. + +11. RELICENSING + +"Massive Multiauthor Collaboration Site" (or "MMC Site") means any +World Wide Web server that publishes copyrightable works and also +provides prominent facilities for anybody to edit those works. A +public wiki that anybody can edit is an example of such a server. A +"Massive Multiauthor Collaboration" (or "MMC") contained in the site +means any set of copyrightable works thus published on the MMC site. + +"CC-BY-SA" means the Creative Commons Attribution-Share Alike 3.0 +license published by Creative Commons Corporation, a not-for-profit +corporation with a principal place of business in San Francisco, +California, as well as future copyleft versions of that license +published by that same organization. + +"Incorporate" means to publish or republish a Document, in whole or in +part, as part of another Document. + +An MMC is "eligible for relicensing" if it is licensed under this +License, and if all works that were first published under this License +somewhere other than this MMC, and subsequently incorporated in whole or +in part into the MMC, (1) had no cover texts or invariant sections, and +(2) were thus incorporated prior to November 1, 2008. + +The operator of an MMC Site may republish an MMC contained in the site +under CC-BY-SA on the same site at any time before August 1, 2009, +provided the MMC is eligible for relicensing. + + +ADDENDUM: How to use this License for your documents + +To use this License in a document you have written, include a copy of +the License in the document and put the following copyright and +license notices just after the title page: + + Copyright (c) YEAR YOUR NAME. + Permission is granted to copy, distribute and/or modify this document + under the terms of the GNU Free Documentation License, Version 1.3 + or any later version published by the Free Software Foundation; + with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. + A copy of the license is included in the section entitled "GNU + Free Documentation License". + +If you have Invariant Sections, Front-Cover Texts and Back-Cover Texts, +replace the "with...Texts." line with this: + + with the Invariant Sections being LIST THEIR TITLES, with the + Front-Cover Texts being LIST, and with the Back-Cover Texts being LIST. + +If you have Invariant Sections without Cover Texts, or some other +combination of the three, merge those two alternatives to suit the +situation. + +If your document contains nontrivial examples of program code, we +recommend releasing these examples in parallel under your choice of +free software license, such as the GNU General Public License, +to permit their use in free software. From d44930a77765f7dc0f1271fd8b1820a37ee12844 Mon Sep 17 00:00:00 2001 From: Tyler887 Date: Sat, 1 Jan 2022 19:27:57 +0000 Subject: [PATCH 10/70] Update gfdl-1.3.txt --- _licenses/gfdl-1.3.txt | 3 +++ 1 file changed, 3 insertions(+) diff --git a/_licenses/gfdl-1.3.txt b/_licenses/gfdl-1.3.txt index f0b4627..e48c9fd 100644 --- a/_licenses/gfdl-1.3.txt +++ b/_licenses/gfdl-1.3.txt @@ -19,6 +19,9 @@ conditions: - disclose-source - same-license - document-changes +limitations: + - liability + - warranty --- GNU Free Documentation License From 3fca253802b8ec8a016e1b87310aaa006a4715d1 Mon Sep 17 00:00:00 2001 From: Tyler887 Date: Sun, 2 Jan 2022 11:14:14 +0000 Subject: [PATCH 11/70] Update _licenses/gfdl-1.3.txt Co-authored-by: Mike Linksvayer --- _licenses/gfdl-1.3.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_licenses/gfdl-1.3.txt b/_licenses/gfdl-1.3.txt index e48c9fd..47581aa 100644 --- a/_licenses/gfdl-1.3.txt +++ b/_licenses/gfdl-1.3.txt @@ -1,5 +1,5 @@ --- -title: GNU Free Documentation License 1.3 +title: GNU Free Documentation License v1.3 nickname: GNU FDL 1.3 spdx-id: GFDL-1.3 From 35b074b0ae4cfcd5c8d28d5966853a890728bfc9 Mon Sep 17 00:00:00 2001 From: Tyler887 Date: Sun, 2 Jan 2022 11:16:17 +0000 Subject: [PATCH 12/70] Update gfdl-1.3.txt --- _licenses/gfdl-1.3.txt | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/_licenses/gfdl-1.3.txt b/_licenses/gfdl-1.3.txt index 47581aa..72f442a 100644 --- a/_licenses/gfdl-1.3.txt +++ b/_licenses/gfdl-1.3.txt @@ -1,9 +1,9 @@ --- title: GNU Free Documentation License v1.3 -nickname: GNU FDL 1.3 + spdx-id: GFDL-1.3 -description: A free but copyleft license for software documentation that allows almost any use. The Free Software Foundation does not reccommend using the GPL on documentation. Contributors provide an express grant of patent rights. +description: A free but copyleft license for software documentation that allows almost any use. how: Create a text file (typically named COPYING, as per GNU conventions) in the root of your source code and copy the text of the license into the file. note: The Free Software Foundation recommends taking the additional step of adding a boilerplate notice to the top of each file. The boilerplate can be found at the end of the license. @@ -12,7 +12,6 @@ permissions: - commercial-use - modifications - distribution - - patent-use - private-use conditions: - include-copyright From 9c8af705203cc4151af20ebb3e1aac433e054558 Mon Sep 17 00:00:00 2001 From: Tyler887 Date: Mon, 3 Jan 2022 10:38:16 +0000 Subject: [PATCH 13/70] Update gfdl-1.3.txt --- _licenses/gfdl-1.3.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_licenses/gfdl-1.3.txt b/_licenses/gfdl-1.3.txt index 72f442a..19994a8 100644 --- a/_licenses/gfdl-1.3.txt +++ b/_licenses/gfdl-1.3.txt @@ -6,7 +6,7 @@ spdx-id: GFDL-1.3 description: A free but copyleft license for software documentation that allows almost any use. how: Create a text file (typically named COPYING, as per GNU conventions) in the root of your source code and copy the text of the license into the file. -note: The Free Software Foundation recommends taking the additional step of adding a boilerplate notice to the top of each file. The boilerplate can be found at the end of the license. +note: The Free Software Foundation recommends taking the additional step of adding a boilerplate notice to the top of each file. The boilerplate can be found at the "addendum" part of the license. permissions: - commercial-use From b628ba0fbfc44aec98e81627fb6ab99d84151689 Mon Sep 17 00:00:00 2001 From: Tyler887 Date: Mon, 3 Jan 2022 10:41:45 +0000 Subject: [PATCH 14/70] Update gfdl-1.3.txt --- _licenses/gfdl-1.3.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_licenses/gfdl-1.3.txt b/_licenses/gfdl-1.3.txt index 19994a8..9c734e3 100644 --- a/_licenses/gfdl-1.3.txt +++ b/_licenses/gfdl-1.3.txt @@ -3,7 +3,7 @@ title: GNU Free Documentation License v1.3 spdx-id: GFDL-1.3 -description: A free but copyleft license for software documentation that allows almost any use. +description: A copyleft license for software documentation that allows almost any use. how: Create a text file (typically named COPYING, as per GNU conventions) in the root of your source code and copy the text of the license into the file. note: The Free Software Foundation recommends taking the additional step of adding a boilerplate notice to the top of each file. The boilerplate can be found at the "addendum" part of the license. From 326f9e74c4e48d63c443c8640ae18388df3b15ea Mon Sep 17 00:00:00 2001 From: Tyler887 Date: Wed, 5 Jan 2022 12:21:06 +0000 Subject: [PATCH 15/70] Update gfdl-1.3.txt --- _licenses/gfdl-1.3.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_licenses/gfdl-1.3.txt b/_licenses/gfdl-1.3.txt index 9c734e3..2355369 100644 --- a/_licenses/gfdl-1.3.txt +++ b/_licenses/gfdl-1.3.txt @@ -6,7 +6,7 @@ spdx-id: GFDL-1.3 description: A copyleft license for software documentation that allows almost any use. how: Create a text file (typically named COPYING, as per GNU conventions) in the root of your source code and copy the text of the license into the file. -note: The Free Software Foundation recommends taking the additional step of adding a boilerplate notice to the top of each file. The boilerplate can be found at the "addendum" part of the license. +note: The Free Software Foundation recommends taking the additional step of adding a boilerplate notice to the title part of each file. The boilerplate can be found at the "addendum" part of the license. permissions: - commercial-use From d376378ee69237e16eaa32e4aee007290d1330f6 Mon Sep 17 00:00:00 2001 From: Tyler887 Date: Wed, 5 Jan 2022 12:21:46 +0000 Subject: [PATCH 16/70] Update gfdl-1.3.txt --- _licenses/gfdl-1.3.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_licenses/gfdl-1.3.txt b/_licenses/gfdl-1.3.txt index 2355369..12f0726 100644 --- a/_licenses/gfdl-1.3.txt +++ b/_licenses/gfdl-1.3.txt @@ -6,7 +6,7 @@ spdx-id: GFDL-1.3 description: A copyleft license for software documentation that allows almost any use. how: Create a text file (typically named COPYING, as per GNU conventions) in the root of your source code and copy the text of the license into the file. -note: The Free Software Foundation recommends taking the additional step of adding a boilerplate notice to the title part of each file. The boilerplate can be found at the "addendum" part of the license. +note: The Free Software Foundation recommends taking the additional step of adding a boilerplate notice after the title part of each file. The boilerplate can be found at the "addendum" part of the license. permissions: - commercial-use From bc5f32e51c0d20fd43cf329766f27542ac72d20d Mon Sep 17 00:00:00 2001 From: Tyler887 Date: Tue, 22 Mar 2022 17:18:22 +0000 Subject: [PATCH 17/70] Update sidebar.html --- _includes/sidebar.html | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/_includes/sidebar.html b/_includes/sidebar.html index 8928950..98b6613 100644 --- a/_includes/sidebar.html +++ b/_includes/sidebar.html @@ -26,9 +26,10 @@ {% endif %} {% assign xgpl = false %} {% if page.spdx-id contains 'GPL' %}{% assign xgpl = true %}{% endif %} + {% if page.spdx-id contains 'GFDL' %}{% assign gfdl = true %}{% endif %} {% assign ofl = false %} {% if page.spdx-id contains 'OFL-1' %}{% assign ofl = true %}{% endif %} -

Add {{ page.spdx-id }}{% if xgpl %}-or-later{% endif %}{% if ofl %}-no-RFN{% endif %}{% if xgpl %} (or {{ page.spdx-id }}-only to disallow future versions){% endif %}{% if ofl %} (or {{ page.spdx-id }}-RFN if a Reserved Font Name is specified after the copyright statement){% endif %} to your project’s package description, if applicable (e.g., Node.js, Ruby, and Rust). This will ensure the license is displayed in package directories.

+

Add {{ page.spdx-id }}{% if xgpl or gfdl %}-or-later{% endif %}{% if ofl %}-no-RFN{% endif %}{% if xgpl or gfdl %} (or {{ page.spdx-id }}-only to disallow future versions){% endif %}{% if ofl %} (or {{ page.spdx-id }}-RFN if a Reserved Font Name is specified after the copyright statement){% endif %} to your project’s package description, if applicable (e.g., Node.js, Ruby, and Rust). This will ensure the license is displayed in package directories.

{% if page.spdx-id contains 'GPL-2' %}

If you would like your project to adopt the GPL-3.0’s cure provision, add the text of the GPL Cooperation Commitment to a file named COMMITMENT in the same directory as your {{ page.spdx-id }} license file.

{% endif %} From 5881f34b1e2f0824552c87a7b6aee9d63c9509db Mon Sep 17 00:00:00 2001 From: Yishuai Li Date: Thu, 14 Apr 2022 19:36:12 -0400 Subject: [PATCH 18/70] mulan: fix wrapping and trim space --- _licenses/mulanpsl-2.0.txt | 111 ++++++++++++++++++------------------- 1 file changed, 55 insertions(+), 56 deletions(-) diff --git a/_licenses/mulanpsl-2.0.txt b/_licenses/mulanpsl-2.0.txt index 90a2248..8b3d598 100644 --- a/_licenses/mulanpsl-2.0.txt +++ b/_licenses/mulanpsl-2.0.txt @@ -102,14 +102,13 @@ limitations: Copyright (c) [Year] [name of copyright holder] [Software Name] is licensed under Mulan PSL v2. -You can use this software according to the terms and conditions of the Mulan +You can use this software according to the terms and conditions of the Mulan PSL v2. You may obtain a copy of Mulan PSL v2 at: http://license.coscl.org.cn/MulanPSL2 -THIS SOFTWARE IS PROVIDED ON AN "AS IS" BASIS, WITHOUT WARRANTIES OF ANY -KIND, EITHER EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO -NON-INFRINGEMENT, -MERCHANTABILITY OR FIT FOR A PARTICULAR PURPOSE. +THIS SOFTWARE IS PROVIDED ON AN "AS IS" BASIS, WITHOUT WARRANTIES OF ANY +KIND, EITHER EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO +NON-INFRINGEMENT, MERCHANTABILITY OR FIT FOR A PARTICULAR PURPOSE. See the Mulan PSL v2 for more details. Mulan Permissive Software License，Version 2 @@ -118,109 +117,109 @@ Mulan Permissive Software License，Version 2 (Mulan PSL v2) January 2020 http://license.coscl.org.cn/MulanPSL2 -Your reproduction, use, modification and distribution of the Software shall -be subject to Mulan PSL v2 (this License) with the following terms and +Your reproduction, use, modification and distribution of the Software shall +be subject to Mulan PSL v2 (this License) with the following terms and conditions: 0. Definition -Software means the program and related documents which are licensed under +Software means the program and related documents which are licensed under this License and comprise all Contribution(s). -Contribution means the copyrightable work licensed by a particular +Contribution means the copyrightable work licensed by a particular Contributor under this License. -Contributor means the Individual or Legal Entity who licenses its +Contributor means the Individual or Legal Entity who licenses its copyrightable work under this License. -Legal Entity means the entity making a Contribution and all its +Legal Entity means the entity making a Contribution and all its Affiliates. -Affiliates means entities that control, are controlled by, or are under -common control with the acting entity under this License, ‘control’ means -direct or indirect ownership of at least fifty percent (50%) of the voting -power, capital or other securities of controlled or commonly controlled +Affiliates means entities that control, are controlled by, or are under +common control with the acting entity under this License, ‘control’ means +direct or indirect ownership of at least fifty percent (50%) of the voting +power, capital or other securities of controlled or commonly controlled entity. 1. Grant of Copyright License -Subject to the terms and conditions of this License, each Contributor hereby -grants to you a perpetual, worldwide, royalty-free, non-exclusive, -irrevocable copyright license to reproduce, use, modify, or distribute its +Subject to the terms and conditions of this License, each Contributor hereby +grants to you a perpetual, worldwide, royalty-free, non-exclusive, +irrevocable copyright license to reproduce, use, modify, or distribute its Contribution, with modification or not. 2. Grant of Patent License -Subject to the terms and conditions of this License, each Contributor hereby -grants to you a perpetual, worldwide, royalty-free, non-exclusive, -irrevocable (except for revocation under this Section) patent license to -make, have made, use, offer for sale, sell, import or otherwise transfer its -Contribution, where such patent license is only limited to the patent claims -owned or controlled by such Contributor now or in future which will be -necessarily infringed by its Contribution alone, or by combination of the -Contribution with the Software to which the Contribution was contributed. -The patent license shall not apply to any modification of the Contribution, -and any other combination which includes the Contribution. If you or your -Affiliates directly or indirectly institute patent litigation (including a -cross claim or counterclaim in a litigation) or other patent enforcement -activities against any individual or entity by alleging that the Software or -any Contribution in it infringes patents, then any patent license granted to -you under this License for the Software shall terminate as of the date such +Subject to the terms and conditions of this License, each Contributor hereby +grants to you a perpetual, worldwide, royalty-free, non-exclusive, +irrevocable (except for revocation under this Section) patent license to +make, have made, use, offer for sale, sell, import or otherwise transfer its +Contribution, where such patent license is only limited to the patent claims +owned or controlled by such Contributor now or in future which will be +necessarily infringed by its Contribution alone, or by combination of the +Contribution with the Software to which the Contribution was contributed. +The patent license shall not apply to any modification of the Contribution, +and any other combination which includes the Contribution. If you or your +Affiliates directly or indirectly institute patent litigation (including a +cross claim or counterclaim in a litigation) or other patent enforcement +activities against any individual or entity by alleging that the Software or +any Contribution in it infringes patents, then any patent license granted to +you under this License for the Software shall terminate as of the date such litigation or activity is filed or taken. 3. No Trademark License -No trademark license is granted to use the trade names, trademarks, service -marks, or product names of Contributor, except as required to fulfill notice +No trademark license is granted to use the trade names, trademarks, service +marks, or product names of Contributor, except as required to fulfill notice requirements in section 4. 4. Distribution Restriction -You may distribute the Software in any medium with or without modification, -whether in source or executable forms, provided that you provide recipients -with a copy of this License and retain copyright, patent, trademark and +You may distribute the Software in any medium with or without modification, +whether in source or executable forms, provided that you provide recipients +with a copy of this License and retain copyright, patent, trademark and disclaimer statements in the Software. 5. Disclaimer of Warranty and Limitation of Liability -THE SOFTWARE AND CONTRIBUTION IN IT ARE PROVIDED WITHOUT WARRANTIES OF ANY -KIND, EITHER EXPRESS OR IMPLIED. IN NO EVENT SHALL ANY CONTRIBUTOR OR -COPYRIGHT HOLDER BE LIABLE TO YOU FOR ANY DAMAGES, INCLUDING, BUT NOT -LIMITED TO ANY DIRECT, OR INDIRECT, SPECIAL OR CONSEQUENTIAL DAMAGES ARISING -FROM YOUR USE OR INABILITY TO USE THE SOFTWARE OR THE CONTRIBUTION IN IT, NO -MATTER HOW IT’S CAUSED OR BASED ON WHICH LEGAL THEORY, EVEN IF ADVISED OF +THE SOFTWARE AND CONTRIBUTION IN IT ARE PROVIDED WITHOUT WARRANTIES OF ANY +KIND, EITHER EXPRESS OR IMPLIED. IN NO EVENT SHALL ANY CONTRIBUTOR OR +COPYRIGHT HOLDER BE LIABLE TO YOU FOR ANY DAMAGES, INCLUDING, BUT NOT +LIMITED TO ANY DIRECT, OR INDIRECT, SPECIAL OR CONSEQUENTIAL DAMAGES ARISING +FROM YOUR USE OR INABILITY TO USE THE SOFTWARE OR THE CONTRIBUTION IN IT, NO +MATTER HOW IT’S CAUSED OR BASED ON WHICH LEGAL THEORY, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. 6. Language -THIS LICENSE IS WRITTEN IN BOTH CHINESE AND ENGLISH, AND THE CHINESE VERSION -AND ENGLISH VERSION SHALL HAVE THE SAME LEGAL EFFECT. IN THE CASE OF -DIVERGENCE BETWEEN THE CHINESE AND ENGLISH VERSIONS, THE CHINESE VERSION +THIS LICENSE IS WRITTEN IN BOTH CHINESE AND ENGLISH, AND THE CHINESE VERSION +AND ENGLISH VERSION SHALL HAVE THE SAME LEGAL EFFECT. IN THE CASE OF +DIVERGENCE BETWEEN THE CHINESE AND ENGLISH VERSIONS, THE CHINESE VERSION SHALL PREVAIL. END OF THE TERMS AND CONDITIONS -How to Apply the Mulan Permissive Software License，Version 2 +How to Apply the Mulan Permissive Software License，Version 2 (Mulan PSL v2) to Your Software -To apply the Mulan PSL v2 to your work, for easy identification by +To apply the Mulan PSL v2 to your work, for easy identification by recipients, you are suggested to complete following three steps: -i. Fill in the blanks in following statement, including insert your software -name, the year of the first publication of your software, and your name +i. Fill in the blanks in following statement, including insert your software +name, the year of the first publication of your software, and your name identified as the copyright owner; -ii. Create a file named "LICENSE" which contains the whole context of this +ii. Create a file named "LICENSE" which contains the whole context of this License in the first directory of your software package; -iii. Attach the statement to the appropriate annotated syntax at the +iii. Attach the statement to the appropriate annotated syntax at the beginning of each source file. Copyright (c) [Year] [name of copyright holder] [Software Name] is licensed under Mulan PSL v2. -You can use this software according to the terms and conditions of the Mulan +You can use this software according to the terms and conditions of the Mulan PSL v2. You may obtain a copy of Mulan PSL v2 at: http://license.coscl.org.cn/MulanPSL2 -THIS SOFTWARE IS PROVIDED ON AN "AS IS" BASIS, WITHOUT WARRANTIES OF ANY -KIND, EITHER EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO +THIS SOFTWARE IS PROVIDED ON AN "AS IS" BASIS, WITHOUT WARRANTIES OF ANY +KIND, EITHER EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO NON-INFRINGEMENT, MERCHANTABILITY OR FIT FOR A PARTICULAR PURPOSE. See the Mulan PSL v2 for more details. From 242b0638db25f809980c1fcd212286996a270398 Mon Sep 17 00:00:00 2001 From: Mike Linksvayer Date: Thu, 14 Apr 2022 16:50:00 -0700 Subject: [PATCH 19/70] update cncf link --- community.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/community.md b/community.md index f4ea7d9..0caae39 100644 --- a/community.md +++ b/community.md @@ -14,7 +14,7 @@ Some communities have strong preferences for particular licenses. If you want to {: .bullets} * [Apache](https://www.apache.org/licenses/) requires [Apache License 2.0](/licenses/apache-2.0/) -* [Cloud Native Computing Foundation](https://github.com/cncf/toc/blob/master/process/project_proposals.adoc) dictates [Apache License 2.0](/licenses/apache-2.0/) by default +* [Cloud Native Computing Foundation](https://github.com/cncf/toc/blob/main/process/project_proposals.md) dictates [Apache License 2.0](/licenses/apache-2.0/) by default * [GNU](https://www.gnu.org/licenses/license-recommendations.html) recommends [GNU GPLv3](/licenses/gpl-3.0/) for most programs * [npm packages](https://libraries.io/search?platforms=npm) overwhelmingly use the [MIT](/licenses/mit/) or the very similar [ISC](/licenses/isc) licenses * [OpenBSD](https://www.openbsd.org/policy.html) prefers the [ISC License](/licenses/isc/) From 1a2ed662394573c2c369532f19f2403265ec11bf Mon Sep 17 00:00:00 2001 From: Baoshuo Ren Date: Wed, 27 Apr 2022 17:19:40 +0800 Subject: [PATCH 20/70] chore: remove git.io All links on git.io will stop redirecting after April 29, 2022. - https://github.blog/changelog/2022-04-25-git-io-deprecation/ --- spec/license_spec.rb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/spec/license_spec.rb b/spec/license_spec.rb index 0fd8a96..09460c6 100644 --- a/spec/license_spec.rb +++ b/spec/license_spec.rb @@ -28,7 +28,7 @@ describe 'licenses' do context 'industry approval' do it 'should be approved by OSI or FSF or OD' do - expect(approved_licenses).to include(spdx_lcase), 'See https://git.io/vzCTV.' + expect(approved_licenses).to include(spdx_lcase), 'See https://github.com/github/choosealicense.com/blob/master/CONTRIBUTING.md#adding-new-licenses.' end end From 8359cdcb3f4886976a8dd5616c6b52fd62f1fe22 Mon Sep 17 00:00:00 2001 From: Mike Linksvayer Date: Wed, 27 Apr 2022 07:43:32 -0700 Subject: [PATCH 21/70] avoid master->gh-pages redirect --- spec/license_spec.rb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/spec/license_spec.rb b/spec/license_spec.rb index 09460c6..d0dbaf1 100644 --- a/spec/license_spec.rb +++ b/spec/license_spec.rb @@ -28,7 +28,7 @@ describe 'licenses' do context 'industry approval' do it 'should be approved by OSI or FSF or OD' do - expect(approved_licenses).to include(spdx_lcase), 'See https://github.com/github/choosealicense.com/blob/master/CONTRIBUTING.md#adding-new-licenses.' + expect(approved_licenses).to include(spdx_lcase), 'See https://github.com/github/choosealicense.com/blob/gh-pages/CONTRIBUTING.md#adding-new-licenses.' end end From 0d7c2d161f4786077a7c4a82d45a3e30bdb3fb59 Mon Sep 17 00:00:00 2001 From: Julian Stirling Date: Fri, 10 Jun 2022 17:35:06 +0100 Subject: [PATCH 22/70] Update projects using CERN-OHL-S and CERN-OHL-P --- _licenses/cern-ohl-p-2.0.txt | 4 ++-- _licenses/cern-ohl-s-2.0.txt | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/_licenses/cern-ohl-p-2.0.txt b/_licenses/cern-ohl-p-2.0.txt index 262034f..1afbd7b 100644 --- a/_licenses/cern-ohl-p-2.0.txt +++ b/_licenses/cern-ohl-p-2.0.txt @@ -10,9 +10,9 @@ how: Create a text file (typically named LICENSE or LICENSE.txt) in the root of note: CERN recommends adding a license header and copyright notice to the README and source files. CERN provides a User's Guide containing a recommended license header. using: - Castor & Pollux: https://github.com/wntrblm/Castor_and_Pollux/blob/main/hardware/mainboard/LICENSE + tedium: https://github.com/jboone/tedium/blob/master/LICENSE-CERN-OHL-P-v2 LEDEAF: https://github.com/adamgreig/ledeaf/blob/master/LICENSE_CERN_OHL_P_v2.txt - ProtoCentral ECG Breakout: https://github.com/Protocentral/protocentral_max86150_ecg_ppg/blob/master/LICENSE.md#hardware + Open source controller board for ventilators: https://github.com/CV19CO/open_controller_for_ventilator/master/LICENSE permissions: - commercial-use diff --git a/_licenses/cern-ohl-s-2.0.txt b/_licenses/cern-ohl-s-2.0.txt index 115f9f9..e3b810a 100644 --- a/_licenses/cern-ohl-s-2.0.txt +++ b/_licenses/cern-ohl-s-2.0.txt @@ -12,7 +12,7 @@ note: CERN recommends adding a license header and copyright notice to the README using: USB Armory: https://github.com/f-secure-foundry/usbarmory/blob/master/hardware/mark-two/LICENSE waffling60: https://github.com/4pplet/waffling60/blob/master/LICENCE.md - Duet 3 Mainboard 6HC: https://github.com/Duet3D/Duet3-Mainboard-6HC/blob/master/LICENSE + plt-docs PLT Demo Board: https://github.com/bcdevices/plt-docs/blob/main/PLT-DEMOv2/LICENSE permissions: - commercial-use From 9ff30caccd6776866a1d4c49b22e0c48e4392532 Mon Sep 17 00:00:00 2001 From: Mike Linksvayer Date: Fri, 10 Jun 2022 11:32:37 -0700 Subject: [PATCH 23/70] update unlicense examples --- _licenses/unlicense.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_licenses/unlicense.txt b/_licenses/unlicense.txt index deaac05..ab3cb15 100644 --- a/_licenses/unlicense.txt +++ b/_licenses/unlicense.txt @@ -8,9 +8,9 @@ description: A license with no conditions whatsoever which dedicates works to th how: Create a text file (typically named UNLICENSE or UNLICENSE.txt) in the root of your source code and copy the text of the license disclaimer into the file. using: - scoop: https://github.com/lukesampson/scoop/blob/master/LICENSE kakoune: https://github.com/mawww/kakoune/blob/master/UNLICENSE RDF.rb: https://github.com/ruby-rdf/rdf/blob/master/UNLICENSE + react-use: https://github.com/streamich/react-use permissions: - private-use From de42758cecb53377e29dc637c88ccc2b5c6935d3 Mon Sep 17 00:00:00 2001 From: Mike Linksvayer Date: Fri, 10 Jun 2022 11:38:10 -0700 Subject: [PATCH 24/70] Fix react-use example --- _licenses/unlicense.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_licenses/unlicense.txt b/_licenses/unlicense.txt index ab3cb15..fc4d4a5 100644 --- a/_licenses/unlicense.txt +++ b/_licenses/unlicense.txt @@ -10,7 +10,7 @@ how: Create a text file (typically named UNLICENSE or UNLICENSE.txt) in the root using: kakoune: https://github.com/mawww/kakoune/blob/master/UNLICENSE RDF.rb: https://github.com/ruby-rdf/rdf/blob/master/UNLICENSE - react-use: https://github.com/streamich/react-use + react-use: https://github.com/streamich/react-use/blob/master/LICENSE permissions: - private-use From 683f3e932d589802058c9760b59ce63abbe4ae47 Mon Sep 17 00:00:00 2001 From: j-sp Date: Fri, 10 Jun 2022 22:57:49 +0200 Subject: [PATCH 25/70] Update cern-ohl-p-2.0.txt Clarify use guidelines of p variant --- _licenses/cern-ohl-p-2.0.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_licenses/cern-ohl-p-2.0.txt b/_licenses/cern-ohl-p-2.0.txt index 1afbd7b..5766377 100644 --- a/_licenses/cern-ohl-p-2.0.txt +++ b/_licenses/cern-ohl-p-2.0.txt @@ -7,7 +7,7 @@ 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 a license header and copyright notice to the README and source files. CERN provides a User's Guide containing a recommended license header. +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. See the User's Guide for example notices and further explanation. using: tedium: https://github.com/jboone/tedium/blob/master/LICENSE-CERN-OHL-P-v2 From 072e77d29e0a2cc958cb8c3776ff1e7425a3ebf5 Mon Sep 17 00:00:00 2001 From: j-sp Date: Fri, 10 Jun 2022 23:00:20 +0200 Subject: [PATCH 26/70] Update cern-ohl-s-2.0.txt Avoid word "virally" --- _licenses/cern-ohl-s-2.0.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_licenses/cern-ohl-s-2.0.txt b/_licenses/cern-ohl-s-2.0.txt index e3b810a..2acd112 100644 --- a/_licenses/cern-ohl-s-2.0.txt +++ b/_licenses/cern-ohl-s-2.0.txt @@ -3,7 +3,7 @@ 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 virally, 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, 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). 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. From 788c281d2fcccd7aa65e272568c1abfb0166aa9d Mon Sep 17 00:00:00 2001 From: j-sp Date: Fri, 10 Jun 2022 23:02:17 +0200 Subject: [PATCH 27/70] Update cern-ohl-s-2.0.txt Clarify usage guidelines for S variant of CERN OHL v2 --- _licenses/cern-ohl-s-2.0.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_licenses/cern-ohl-s-2.0.txt b/_licenses/cern-ohl-s-2.0.txt index 2acd112..0bb721d 100644 --- a/_licenses/cern-ohl-s-2.0.txt +++ b/_licenses/cern-ohl-s-2.0.txt @@ -7,7 +7,7 @@ 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 a license header and copyright notice to the README and source files. CERN provides a User's Guide containing a recommended license header. +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. See the User's Guide for example notices and further explanation. using: USB Armory: https://github.com/f-secure-foundry/usbarmory/blob/master/hardware/mark-two/LICENSE From f1e3b5da45b99efb95b2cae0a44c31858585b5fd Mon Sep 17 00:00:00 2001 From: j-sp Date: Fri, 10 Jun 2022 23:05:05 +0200 Subject: [PATCH 28/70] Update cern-ohl-w-2.0.txt Clarify usage guidelines for W variant of CERN OHL v2 --- _licenses/cern-ohl-w-2.0.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_licenses/cern-ohl-w-2.0.txt b/_licenses/cern-ohl-w-2.0.txt index 45f5bb7..f9caee4 100644 --- a/_licenses/cern-ohl-w-2.0.txt +++ b/_licenses/cern-ohl-w-2.0.txt @@ -7,7 +7,7 @@ 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 a license header and copyright notice to the README and source files. CERN provides a User's Guide containing a recommended license header. +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. See the User's Guide for example notices and further explanation. using: Simple PCIe FMC carrier: https://ohwr.org/project/spec/blob/master/LICENSES/CERN-OHL-W-2.0.txt From a38f57220f362ba187b5f4cd13c4201268c7e1bb Mon Sep 17 00:00:00 2001 From: Javier Serrano Date: Sun, 12 Jun 2022 09:38:19 +0200 Subject: [PATCH 29/70] Shorten note field contents for CERN OHL v2 licenses --- _licenses/cern-ohl-p-2.0.txt | 2 +- _licenses/cern-ohl-s-2.0.txt | 2 +- _licenses/cern-ohl-w-2.0.txt | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/_licenses/cern-ohl-p-2.0.txt b/_licenses/cern-ohl-p-2.0.txt index 5766377..014da0b 100644 --- a/_licenses/cern-ohl-p-2.0.txt +++ b/_licenses/cern-ohl-p-2.0.txt @@ -7,7 +7,7 @@ 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. See the User's Guide for example notices and further explanation. +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 0bb721d..c346e06 100644 --- a/_licenses/cern-ohl-s-2.0.txt +++ b/_licenses/cern-ohl-s-2.0.txt @@ -7,7 +7,7 @@ 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. See the User's Guide for example notices and further explanation. +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 f9caee4..caa1893 100644 --- a/_licenses/cern-ohl-w-2.0.txt +++ b/_licenses/cern-ohl-w-2.0.txt @@ -7,7 +7,7 @@ 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. See the User's Guide for example notices and further explanation. +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 From 5065c967dc7779c6198ecfcee2509309bf6d8050 Mon Sep 17 00:00:00 2001 From: Julian Stirling Date: Sun, 12 Jun 2022 09:18:42 +0100 Subject: [PATCH 30/70] update CERN-OHL-S examples --- _licenses/cern-ohl-s-2.0.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_licenses/cern-ohl-s-2.0.txt b/_licenses/cern-ohl-s-2.0.txt index c346e06..a8c97f8 100644 --- a/_licenses/cern-ohl-s-2.0.txt +++ b/_licenses/cern-ohl-s-2.0.txt @@ -12,7 +12,7 @@ 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 From 86d1a77510def87bc5bbcb7421a61bd626e52aea Mon Sep 17 00:00:00 2001 From: Julian Stirling Date: Sun, 12 Jun 2022 20:01:33 +0100 Subject: [PATCH 32/70] CERN-OHL-S Fix another YAML error --- _licenses/cern-ohl-s-2.0.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_licenses/cern-ohl-s-2.0.txt b/_licenses/cern-ohl-s-2.0.txt index 8a99e9c..e639527 100644 --- a/_licenses/cern-ohl-s-2.0.txt +++ b/_licenses/cern-ohl-s-2.0.txt @@ -13,7 +13,7 @@ note: using: USB Armory: https://github.com/f-secure-foundry/usbarmory/blob/master/hardware/mark-two/LICENSE waffling60: https://github.com/4pplet/waffling60/blob/master/LICENCE.md - Passport Electronics https://github.com/Foundation-Devices/passport-electronics/blob/master/LICENSE.txt + Passport Electronics: https://github.com/Foundation-Devices/passport-electronics/blob/master/LICENSE.txt permissions: - commercial-use From 44b121a807d72f0153de39e973b45cb4dfd32600 Mon Sep 17 00:00:00 2001 From: Julian Stirling Date: Sun, 12 Jun 2022 22:41:32 +0100 Subject: [PATCH 33/70] Tweak using for CERN-OHL-P --- _licenses/cern-ohl-p-2.0.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_licenses/cern-ohl-p-2.0.txt b/_licenses/cern-ohl-p-2.0.txt index 2b4cb2a..96e1ba3 100644 --- a/_licenses/cern-ohl-p-2.0.txt +++ b/_licenses/cern-ohl-p-2.0.txt @@ -13,7 +13,7 @@ note: using: tedium: https://github.com/jboone/tedium/blob/master/LICENSE-CERN-OHL-P-v2 LEDEAF: https://github.com/adamgreig/ledeaf/blob/master/LICENSE_CERN_OHL_P_v2.txt - Open source controller board for ventilators: https://github.com/CV19CO/open_controller_for_ventilator/master/LICENSE + Open source controller board for ventilators: https://github.com/CV19CO/open_controller_for_ventilator/blob/master/LICENSE permissions: - commercial-use From 15237620db27094016ad377212e1e30269b9b07c Mon Sep 17 00:00:00 2001 From: Mike Linksvayer Date: Sun, 12 Jun 2022 16:56:51 -0700 Subject: [PATCH 34/70] don't test help.github.com links They work, unclear why failing in CI --- Rakefile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Rakefile b/Rakefile index 45c207c..c1bd28d 100644 --- a/Rakefile +++ b/Rakefile @@ -17,7 +17,7 @@ task :test do enforce_https: true, validation: { ignore_script_embeds: true }, url_swap: { %r{https://choosealicense.com} => '' }, - url_ignore: [%r{https://github.com/github/choosealicense.com/edit/gh-pages/_licenses/}], + url_ignore: [%r{https://github.com/github/choosealicense.com/edit/gh-pages/_licenses/}, %r{https://help.github.com}], hydra: { max_concurrency: 10 }, check_img_http: true).run end From 65842b6f43f0411a74329cfd2568cbae695c585c Mon Sep 17 00:00:00 2001 From: Zachary Crespin Date: Thu, 16 Jun 2022 17:11:53 -0700 Subject: [PATCH 35/70] make the text visible on yellow :target background The white text was not visible on the yellow :target background so I made it darker. (this is only a problem with dark mode) --- assets/css/application.scss | 1 + 1 file changed, 1 insertion(+) diff --git a/assets/css/application.scss b/assets/css/application.scss index ed8ca00..1e7a031 100644 --- a/assets/css/application.scss +++ b/assets/css/application.scss @@ -108,6 +108,7 @@ strong { :target { background-color: yellow; + color: #444 !important; } .container { From c6f07cb8cc9c19dcbb1434f9ad585b18d1b0e33f Mon Sep 17 00:00:00 2001 From: Mike Linksvayer Date: Tue, 28 Jun 2022 07:29:43 -0700 Subject: [PATCH 36/70] Update Apache-2.0 "how" ASF not AF; link to relevant FAQ entry Inspired by #905 sort of --- _licenses/apache-2.0.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_licenses/apache-2.0.txt b/_licenses/apache-2.0.txt index 74eabb4..88bb06a 100644 --- a/_licenses/apache-2.0.txt +++ b/_licenses/apache-2.0.txt @@ -9,7 +9,7 @@ description: A permissive license whose main conditions require preservation of 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: The Apache Foundation recommends taking the additional step of adding a boilerplate notice to the header of each source file. You can find the notice in the appendix at the very end of the license text. +note: The Apache Sofrware Foundation [recommends](https://apache.org/foundation/license-faq.html#Apply-My-Software) taking the additional step of adding a boilerplate notice to the header of each source file. You can find the notice in the appendix at the very end of the license text. using: Kubernetes: https://github.com/kubernetes/kubernetes/blob/master/LICENSE From cba6a99283b00b5348a121bb1f44fff09912f40b Mon Sep 17 00:00:00 2001 From: Mike Linksvayer Date: Tue, 28 Jun 2022 07:31:47 -0700 Subject: [PATCH 37/70] spel! --- _licenses/apache-2.0.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_licenses/apache-2.0.txt b/_licenses/apache-2.0.txt index 88bb06a..647ce4c 100644 --- a/_licenses/apache-2.0.txt +++ b/_licenses/apache-2.0.txt @@ -9,7 +9,7 @@ description: A permissive license whose main conditions require preservation of 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: The Apache Sofrware Foundation [recommends](https://apache.org/foundation/license-faq.html#Apply-My-Software) taking the additional step of adding a boilerplate notice to the header of each source file. You can find the notice in the appendix at the very end of the license text. +note: The Apache Software Foundation [recommends](https://apache.org/foundation/license-faq.html#Apply-My-Software) taking the additional step of adding a boilerplate notice to the header of each source file. You can find the notice in the appendix at the very end of the license text. using: Kubernetes: https://github.com/kubernetes/kubernetes/blob/master/LICENSE From 2a449d578a8606e26a105a4a0f50cf35af82bffe Mon Sep 17 00:00:00 2001 From: Mike Linksvayer Date: Wed, 6 Jul 2022 17:58:17 -0700 Subject: [PATCH 38/70] same-license--library instead of --file --- _licenses/cern-ohl-w-2.0.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_licenses/cern-ohl-w-2.0.txt b/_licenses/cern-ohl-w-2.0.txt index 9683582..9d6c6ad 100644 --- a/_licenses/cern-ohl-w-2.0.txt +++ b/_licenses/cern-ohl-w-2.0.txt @@ -26,7 +26,7 @@ conditions: - include-copyright - document-changes - disclose-source - - same-license--file + - same-license--library limitations: - liability From d4dbe723db80092e9256caaeba1724665ed8ec51 Mon Sep 17 00:00:00 2001 From: Mike Linksvayer Date: Wed, 6 Jul 2022 18:02:09 -0700 Subject: [PATCH 39/70] -w description edit proposed by @j-sp in https://github.com/github/choosealicense.com/pull/1004/files#r915192799 --- _licenses/cern-ohl-w-2.0.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_licenses/cern-ohl-w-2.0.txt b/_licenses/cern-ohl-w-2.0.txt index 9d6c6ad..f9b8082 100644 --- a/_licenses/cern-ohl-w-2.0.txt +++ b/_licenses/cern-ohl-w-2.0.txt @@ -3,7 +3,7 @@ title: CERN Open Hardware Licence Version 2 - Weakly Reciprocal spdx-id: CERN-OHL-W-2.0 nickname: CERN OHL v2 Weakly 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 “Weakly Reciprocal” variant applies to individual designs but does not spread to the entire project it is included in. +description: Permissions of this weakly-reciprocal license are conditioned on making available complete sources of licensed works and modifications under the same license. Notices must be preserved. Contributors provide an express grant of patent rights. However, a larger work using the licensed work through interfaces provided by the licensed work may be distributed under different terms and without sources for the larger work. 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. From 51ddb5d8f2a289934462bdb1f23edfa5b8ce65e3 Mon Sep 17 00:00:00 2001 From: Mike Linksvayer Date: Wed, 6 Jul 2022 18:03:27 -0700 Subject: [PATCH 40/70] -S description edit proposed by @j-sp in https://github.com/github/choosealicense.com/pull/1004/files#r915184980 --- _licenses/cern-ohl-s-2.0.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_licenses/cern-ohl-s-2.0.txt b/_licenses/cern-ohl-s-2.0.txt index e639527..136fb24 100644 --- a/_licenses/cern-ohl-s-2.0.txt +++ b/_licenses/cern-ohl-s-2.0.txt @@ -3,7 +3,7 @@ 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, 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). +description: Permissions of this strongly reciprocal license for hardware designs are conditioned on making available complete sources of licensed works and modifications, which include larger works using a licensed work, under the same license. Notices must be preserved. Contributors provide an express grant of patent rights. 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. From 55912b61750fc6d8ab6da2ead282d4c8fc473b7f Mon Sep 17 00:00:00 2001 From: Mike Linksvayer Date: Wed, 6 Jul 2022 18:17:07 -0700 Subject: [PATCH 41/70] P description --- _licenses/cern-ohl-p-2.0.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_licenses/cern-ohl-p-2.0.txt b/_licenses/cern-ohl-p-2.0.txt index 96e1ba3..1fd7dbc 100644 --- a/_licenses/cern-ohl-p-2.0.txt +++ b/_licenses/cern-ohl-p-2.0.txt @@ -3,7 +3,7 @@ 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; however, it does have an attribution requirement. +description: A permissive license for hardware designs, with conditions only requiring preservation of notices. Contributors provide an express grant of patent rights. Licensed works, modifications, and larger works may be distributed under different terms and without sources. 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. From 78c2ee95a408456aedded2533ac4b8416bfb6f21 Mon Sep 17 00:00:00 2001 From: Mike Linksvayer Date: Fri, 8 Jul 2022 12:09:10 -0700 Subject: [PATCH 42/70] tighten up non-software text --- non-software.md | 12 ++++-------- 1 file changed, 4 insertions(+), 8 deletions(-) diff --git a/non-software.md b/non-software.md index 7709ca7..bd723a3 100644 --- a/non-software.md +++ b/non-software.md @@ -4,11 +4,11 @@ layout: default permalink: /non-software/ --- -Open source software licenses can be also used for non-software works and are often the best choice, especially when the works in question can be edited and versioned as source (e.g., [open source hardware](https://www.oshwa.org/definition/) designs). [Choose an open source license here.](/licenses/) +Open source software licenses can be also used for non-software works and are often the best choice, especially when the works in question can be edited and versioned as source. [Choose an open source license](/). ### Data, media, etc. -[CC0-1.0](/licenses/cc0-1.0/), [CC-BY-4.0](/licenses/cc-by-4.0/), and [CC-BY-SA-4.0](/licenses/cc-by-sa-4.0/) are [open](https://opendefinition.org) licenses used for non-software material ranging from datasets to videos. Note that CC-BY-4.0 and CC-BY-SA-4.0 should [not be used for software](https://creativecommons.org/faq/#can-i-apply-a-creative-commons-license-to-software). +[CC0-1.0](/licenses/cc0-1.0/), [CC-BY-4.0](/licenses/cc-by-4.0/), and [CC-BY-SA-4.0](/licenses/cc-by-sa-4.0/) are [open](https://opendefinition.org) licenses used for non-software material ranging from datasets to videos. Note that Creative Commons does [not recommond its licenses be used for software](https://creativecommons.org/faq/#can-i-apply-a-creative-commons-license-to-software) or hardware. ### Documentation @@ -20,12 +20,8 @@ The [SIL Open Font License 1.1](/licenses/ofl-1.1/) keeps fonts open, allowing t ### Hardware -There are the CERN Open Hardware family of licenses: [CERN-OHL-P-2.0](/licenses/cern-ohl-p-2.0/), the permissive variant ([MIT](/licenses/mit/)-like); [CERN-OHL-W-2.0](/licenses/cern-ohl-w-2.0/), the “weakly reciprocal” variant ([MPL](/licenses/mpl-2.0/)-like), and [CERN-OHL-S-2.0](/licenses/cern-ohl-s-2.0/), the “strongly reciprocal” variant ([GPL](/licenses/gpl-3.0/)-like). The CERN OHL family is also applicable to HDL source code and synthesized bitstreams as would be used in FPGAs. - -[CC-BY-4.0](/licenses/cc-by-4.0/) and [CC-BY-SA-4.0](/licenses/cc-by-sa-4.0/) are also commonly used for hardware; however they do not grant patent rights which can restrict usage of patent-encumbered hardware licensed under them and Creative Commons does not recommend them for hardware. - -If your hardware has accompanying software then be sure to specify a license for the software portion as well as the hardware portion. +Designs for [open source hardware](https://www.oshwa.org/definition/) ranging from furniture to [FGPAs](https://www.oshwa.org/best-practices-for-sharing-fpga-designs-2/) are covered by CERN Open Hardware licenses: [CERN-OHL-P-2.0](/licenses/cern-ohl-p-2.0/) (permissive), [CERN-OHL-W-2.0](/licenses/cern-ohl-w-2.0/) (weakly reciprocal), and [CERN-OHL-S-2.0](/licenses/cern-ohl-s-2.0/) (strongly reciprocal). ### Mixed projects -If your project contains a mix of software and other material, you can include multiple licenses, as long as you are explicit about which license applies to each part of the project. See [the license notice for this site](https://github.com/github/choosealicense.com#license) as an example. +If your project contains a mix of different types of material, you can include multiple licenses, as long as you are explicit about which license applies to each part of the project. See [the license notice for this site](https://github.com/github/choosealicense.com#license) as an example. From 4ea525e0a68f5d68637968a8300ab9b3bbc053d8 Mon Sep 17 00:00:00 2001 From: Mike Linksvayer Date: Fri, 8 Jul 2022 12:31:03 -0700 Subject: [PATCH 43/70] update cncf link again --- community.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/community.md b/community.md index 0caae39..ec2e260 100644 --- a/community.md +++ b/community.md @@ -14,7 +14,7 @@ Some communities have strong preferences for particular licenses. If you want to {: .bullets} * [Apache](https://www.apache.org/licenses/) requires [Apache License 2.0](/licenses/apache-2.0/) -* [Cloud Native Computing Foundation](https://github.com/cncf/toc/blob/main/process/project_proposals.md) dictates [Apache License 2.0](/licenses/apache-2.0/) by default +* [Cloud Native Computing Foundation](https://github.com/cncf/foundation/blob/main/charter.md#11-ip-policy) requires [Apache License 2.0](/licenses/apache-2.0/) * [GNU](https://www.gnu.org/licenses/license-recommendations.html) recommends [GNU GPLv3](/licenses/gpl-3.0/) for most programs * [npm packages](https://libraries.io/search?platforms=npm) overwhelmingly use the [MIT](/licenses/mit/) or the very similar [ISC](/licenses/isc) licenses * [OpenBSD](https://www.openbsd.org/policy.html) prefers the [ISC License](/licenses/isc/) From 9e46d36648f8e14abd949f96b2d26102d1376036 Mon Sep 17 00:00:00 2001 From: Mike Linksvayer Date: Sat, 9 Jul 2022 11:52:56 -0700 Subject: [PATCH 44/70] rm extra space --- _licenses/cern-ohl-p-2.0.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_licenses/cern-ohl-p-2.0.txt b/_licenses/cern-ohl-p-2.0.txt index 1fd7dbc..86d6613 100644 --- a/_licenses/cern-ohl-p-2.0.txt +++ b/_licenses/cern-ohl-p-2.0.txt @@ -3,7 +3,7 @@ title: CERN Open Hardware Licence Version 2 - Permissive spdx-id: CERN-OHL-P-2.0 nickname: CERN OHL v2 Permissive -description: A permissive license for hardware designs, with conditions only requiring preservation of notices. Contributors provide an express grant of patent rights. Licensed works, modifications, and larger works may be distributed under different terms and without sources. +description: A permissive license for hardware designs, with conditions only requiring preservation of notices. Contributors provide an express grant of patent rights. Licensed works, modifications, and larger works may be distributed under different terms and without sources. 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. From 43f355b2819747a1c5d83e0a7debbb0815e73036 Mon Sep 17 00:00:00 2001 From: Mike Linksvayer Date: Sat, 9 Jul 2022 12:33:02 -0700 Subject: [PATCH 45/70] fix note field for CERN OHL licenses (unintentionally a dictionary value), simplify rendering of field --- _includes/sidebar.html | 4 ++-- _licenses/apache-2.0.txt | 2 +- _licenses/bsl-1.0.txt | 2 +- _licenses/cern-ohl-p-2.0.txt | 3 +-- _licenses/cern-ohl-s-2.0.txt | 3 +-- _licenses/cern-ohl-w-2.0.txt | 3 +-- _licenses/eupl-1.1.txt | 2 +- 7 files changed, 8 insertions(+), 11 deletions(-) diff --git a/_includes/sidebar.html b/_includes/sidebar.html index 8928950..9751d97 100644 --- a/_includes/sidebar.html +++ b/_includes/sidebar.html @@ -15,13 +15,13 @@

How to apply this license

- {{ page.how | markdownify | remove: '

' | remove: '

' }} + {{ page.how }}

Optional steps

{% if page.note %}

- {{ page.note | markdownify | remove: '

' | remove: '

' }} + {{ page.note }}

{% endif %} {% assign xgpl = false %} diff --git a/_licenses/apache-2.0.txt b/_licenses/apache-2.0.txt index 647ce4c..9b2c569 100644 --- a/_licenses/apache-2.0.txt +++ b/_licenses/apache-2.0.txt @@ -9,7 +9,7 @@ description: A permissive license whose main conditions require preservation of 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: The Apache Software Foundation [recommends](https://apache.org/foundation/license-faq.html#Apply-My-Software) taking the additional step of adding a boilerplate notice to the header of each source file. You can find the notice in the appendix at the very end of the license text. +note: The Apache Software Foundation recommends taking the additional step of adding a boilerplate notice to the header of each source file. You can find the notice in the appendix at the very end of the license text. using: Kubernetes: https://github.com/kubernetes/kubernetes/blob/master/LICENSE diff --git a/_licenses/bsl-1.0.txt b/_licenses/bsl-1.0.txt index 8b79559..4cdf0f0 100644 --- a/_licenses/bsl-1.0.txt +++ b/_licenses/bsl-1.0.txt @@ -7,7 +7,7 @@ description: A simple permissive license only requiring preservation of copyrigh 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: Boost recommends taking the additional step of adding a boilerplate notice to the top of each file. The boilerplate can be found at the [Boost Software License FAQ](https://www.boost.org/users/license.html#FAQ). +note: Boost recommends taking the additional step of adding a boilerplate notice to the top of each file. The boilerplate can be found at the Boost Software License FAQ. using: Boost: https://github.com/boostorg/boost/blob/master/LICENSE_1_0.txt diff --git a/_licenses/cern-ohl-p-2.0.txt b/_licenses/cern-ohl-p-2.0.txt index 86d6613..2e31afa 100644 --- a/_licenses/cern-ohl-p-2.0.txt +++ b/_licenses/cern-ohl-p-2.0.txt @@ -7,8 +7,7 @@ description: A permissive license for hardware designs, with conditions only req 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 136fb24..b0c2578 100644 --- a/_licenses/cern-ohl-s-2.0.txt +++ b/_licenses/cern-ohl-s-2.0.txt @@ -7,8 +7,7 @@ description: Permissions of this strongly reciprocal license for hardware design 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 f9b8082..f5c0dee 100644 --- a/_licenses/cern-ohl-w-2.0.txt +++ b/_licenses/cern-ohl-w-2.0.txt @@ -7,8 +7,7 @@ description: Permissions of this weakly-reciprocal license are conditioned on ma 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 diff --git a/_licenses/eupl-1.1.txt b/_licenses/eupl-1.1.txt index c174eb0..dfb9a28 100644 --- a/_licenses/eupl-1.1.txt +++ b/_licenses/eupl-1.1.txt @@ -7,7 +7,7 @@ description: The “European Union Public Licence” (EUPL) is a copyleft free/o how: Create a text file (typically named COPYING or LICENCE.txt) in the root of your source code and copy the text of the license into the file. -note: The European Commission recommends taking the additional step of adding a [boilerplate notice](https://joinup.ec.europa.eu/sites/default/files/inline-files/EUPL%201_1%20Guidelines%20EN%20Joinup.pdf#page=17) to the top of each file. +note: The European Commission recommends taking the additional step of adding a boilerplate notice to the top of each file. using: From 537ffa46d84bd3fcbe15976fbe5603d0e5ee219a Mon Sep 17 00:00:00 2001 From: Paul <5972492+paulyy-y@users.noreply.github.com> Date: Sun, 17 Jul 2022 08:40:19 -0700 Subject: [PATCH 46/70] Fixes FPGA acronym. --- non-software.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/non-software.md b/non-software.md index bd723a3..9cd9ba0 100644 --- a/non-software.md +++ b/non-software.md @@ -20,7 +20,7 @@ The [SIL Open Font License 1.1](/licenses/ofl-1.1/) keeps fonts open, allowing t ### Hardware -Designs for [open source hardware](https://www.oshwa.org/definition/) ranging from furniture to [FGPAs](https://www.oshwa.org/best-practices-for-sharing-fpga-designs-2/) are covered by CERN Open Hardware licenses: [CERN-OHL-P-2.0](/licenses/cern-ohl-p-2.0/) (permissive), [CERN-OHL-W-2.0](/licenses/cern-ohl-w-2.0/) (weakly reciprocal), and [CERN-OHL-S-2.0](/licenses/cern-ohl-s-2.0/) (strongly reciprocal). +Designs for [open source hardware](https://www.oshwa.org/definition/) ranging from furniture to [FPGAs](https://www.oshwa.org/best-practices-for-sharing-fpga-designs-2/) are covered by CERN Open Hardware licenses: [CERN-OHL-P-2.0](/licenses/cern-ohl-p-2.0/) (permissive), [CERN-OHL-W-2.0](/licenses/cern-ohl-w-2.0/) (weakly reciprocal), and [CERN-OHL-S-2.0](/licenses/cern-ohl-s-2.0/) (strongly reciprocal). ### Mixed projects From cf8f0d79e51d90fb2815108b02272935bbefd8a6 Mon Sep 17 00:00:00 2001 From: Robert Newbould Date: Tue, 19 Jul 2022 14:22:25 +0100 Subject: [PATCH 47/70] Fix typo in non-software licenses page Corrects `recommond` to `recommend` --- non-software.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/non-software.md b/non-software.md index 9cd9ba0..07a78c1 100644 --- a/non-software.md +++ b/non-software.md @@ -8,7 +8,7 @@ Open source software licenses can be also used for non-software works and are of ### Data, media, etc. -[CC0-1.0](/licenses/cc0-1.0/), [CC-BY-4.0](/licenses/cc-by-4.0/), and [CC-BY-SA-4.0](/licenses/cc-by-sa-4.0/) are [open](https://opendefinition.org) licenses used for non-software material ranging from datasets to videos. Note that Creative Commons does [not recommond its licenses be used for software](https://creativecommons.org/faq/#can-i-apply-a-creative-commons-license-to-software) or hardware. +[CC0-1.0](/licenses/cc0-1.0/), [CC-BY-4.0](/licenses/cc-by-4.0/), and [CC-BY-SA-4.0](/licenses/cc-by-sa-4.0/) are [open](https://opendefinition.org) licenses used for non-software material ranging from datasets to videos. Note that Creative Commons does [not recommend its licenses be used for software](https://creativecommons.org/faq/#can-i-apply-a-creative-commons-license-to-software) or hardware. ### Documentation From 3084254b384b7ee09f4a4b1c08cf72d0ba8588a6 Mon Sep 17 00:00:00 2001 From: Aeris One Date: Fri, 19 Aug 2022 21:39:22 +0200 Subject: [PATCH 48/70] add network-use-disclose to CeCILL v2 --- _licenses/cecill-2.1.txt | 1 + 1 file changed, 1 insertion(+) diff --git a/_licenses/cecill-2.1.txt b/_licenses/cecill-2.1.txt index 91b7c8f..0db24f6 100644 --- a/_licenses/cecill-2.1.txt +++ b/_licenses/cecill-2.1.txt @@ -20,6 +20,7 @@ permissions: conditions: - include-copyright + - network-use-disclose - disclose-source - same-license From ce3a1686399a5bf9490a4ee3d4c22d815e1adab0 Mon Sep 17 00:00:00 2001 From: Mike Linksvayer Date: Fri, 19 Aug 2022 13:14:46 -0700 Subject: [PATCH 49/70] update ruby version to match pages-gem --- .github/workflows/test.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/workflows/test.yml b/.github/workflows/test.yml index 5c131f7..3532007 100644 --- a/.github/workflows/test.yml +++ b/.github/workflows/test.yml @@ -19,7 +19,7 @@ jobs: - name: Set up Ruby uses: ruby/setup-ruby@v1 with: - ruby-version: 2.7.3 + ruby-version: 2.7.4 bundler-cache: true - name: Run tests From d15753589855cd41c36288ae9d3793a94be06235 Mon Sep 17 00:00:00 2001 From: Steve Huguenin-Elie Date: Thu, 25 Aug 2022 10:37:39 +0200 Subject: [PATCH 50/70] Add Grafana as AGPL-3.0 licensor https://grafana.com/blog/2021/04/20/grafana-loki-tempo-relicensing-to-agplv3/ --- _licenses/agpl-3.0.txt | 1 + 1 file changed, 1 insertion(+) diff --git a/_licenses/agpl-3.0.txt b/_licenses/agpl-3.0.txt index 433632c..4e27dcb 100644 --- a/_licenses/agpl-3.0.txt +++ b/_licenses/agpl-3.0.txt @@ -12,6 +12,7 @@ how: Create a text file (typically named LICENSE or LICENSE.txt) in the root of note: The Free Software Foundation recommends taking the additional step of adding a boilerplate notice to the top of each file. The boilerplate can be found at the end of the license. using: + Grafana: https://github.com/grafana/grafana/blob/main/LICENSE permissions: - commercial-use From 088a44d9035f38673dbaea2a5a788c4d44e18088 Mon Sep 17 00:00:00 2001 From: Mike Linksvayer Date: Thu, 25 Aug 2022 15:24:24 -0700 Subject: [PATCH 51/70] 2 more examples --- _licenses/agpl-3.0.txt | 2 ++ 1 file changed, 2 insertions(+) diff --git a/_licenses/agpl-3.0.txt b/_licenses/agpl-3.0.txt index 4e27dcb..d671311 100644 --- a/_licenses/agpl-3.0.txt +++ b/_licenses/agpl-3.0.txt @@ -13,6 +13,8 @@ note: The Free Software Foundation recommends taking the additional step of addi using: Grafana: https://github.com/grafana/grafana/blob/main/LICENSE + Mastodon: https://github.com/mastodon/mastodon/blob/main/LICENSE + Nextcloud Server: https://github.com/nextcloud/server/blob/master/COPYING permissions: - commercial-use From cce738fbed89a9be49953b9bee7b83ea15bc5691 Mon Sep 17 00:00:00 2001 From: Mike Linksvayer Date: Thu, 25 Aug 2022 15:27:30 -0700 Subject: [PATCH 52/70] remove agpl-3.0 from legacy list with no examples since we're adding 3 --- spec/license_meta_spec.rb | 1 - 1 file changed, 1 deletion(-) diff --git a/spec/license_meta_spec.rb b/spec/license_meta_spec.rb index de6a730..83126f8 100644 --- a/spec/license_meta_spec.rb +++ b/spec/license_meta_spec.rb @@ -24,7 +24,6 @@ describe 'license meta' do it 'using contains 3 examples' do legacy = [ 'afl-3.0', - 'agpl-3.0', 'artistic-2.0', 'bsd-3-clause-clear', 'eupl-1.1', From 656ab18ed7589d325c0d9a825d2050c7f737dbd9 Mon Sep 17 00:00:00 2001 From: Mike Linksvayer Date: Fri, 2 Sep 2022 14:05:20 -0700 Subject: [PATCH 53/70] more or-later or -only handling --- _includes/sidebar.html | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/_includes/sidebar.html b/_includes/sidebar.html index 3f212ce..6148959 100644 --- a/_includes/sidebar.html +++ b/_includes/sidebar.html @@ -24,12 +24,12 @@ {{ page.note }}

{% endif %} - {% assign xgpl = false %} - {% if page.spdx-id contains 'GPL' %}{% assign xgpl = true %}{% endif %} - {% if page.spdx-id contains 'GFDL' %}{% assign gfdl = true %}{% endif %} + {% assign lateronly = false %} + {% if page.spdx-id contains 'GPL' %}{% assign lateronly = true %} + {% elsif page.spdx-id contains 'GFDL' %}{% assign lateronly = true %}{% endif %} {% assign ofl = false %} {% if page.spdx-id contains 'OFL-1' %}{% assign ofl = true %}{% endif %} -

Add {{ page.spdx-id }}{% if xgpl or gfdl %}-or-later{% endif %}{% if ofl %}-no-RFN{% endif %}{% if xgpl or gfdl %} (or {{ page.spdx-id }}-only to disallow future versions){% endif %}{% if ofl %} (or {{ page.spdx-id }}-RFN if a Reserved Font Name is specified after the copyright statement){% endif %} to your project’s package description, if applicable (e.g., Node.js, Ruby, and Rust). This will ensure the license is displayed in package directories.

+

Add {{ page.spdx-id }}{% if lateronly %}-or-later{% endif %}{% if ofl %}-no-RFN{% endif %}{% if lateronly %} (or {{ page.spdx-id }}-only to disallow future versions){% endif %}{% if ofl %} (or {{ page.spdx-id }}-RFN if a Reserved Font Name is specified after the copyright statement){% endif %} to your project’s package description, if applicable (e.g., Node.js, Ruby, and Rust). This will ensure the license is displayed in package directories.

{% if page.spdx-id contains 'GPL-2' %}

If you would like your project to adopt the GPL-3.0’s cure provision, add the text of the GPL Cooperation Commitment to a file named COMMITMENT in the same directory as your {{ page.spdx-id }} license file.

{% endif %} @@ -37,7 +37,7 @@
- + Source From 2f02459de0ffe47f6a863073a67e199fdea84659 Mon Sep 17 00:00:00 2001 From: Mike Linksvayer Date: Fri, 2 Sep 2022 14:10:16 -0700 Subject: [PATCH 54/70] instructions suggest after title page not title part of each file Reword to try to make work for all situations --- _licenses/gfdl-1.3.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_licenses/gfdl-1.3.txt b/_licenses/gfdl-1.3.txt index 12f0726..d696b0b 100644 --- a/_licenses/gfdl-1.3.txt +++ b/_licenses/gfdl-1.3.txt @@ -6,7 +6,7 @@ spdx-id: GFDL-1.3 description: A copyleft license for software documentation that allows almost any use. how: Create a text file (typically named COPYING, as per GNU conventions) in the root of your source code and copy the text of the license into the file. -note: The Free Software Foundation recommends taking the additional step of adding a boilerplate notice after the title part of each file. The boilerplate can be found at the "addendum" part of the license. +note: The Free Software Foundation recommends taking the additional step of adding a boilerplate notice after the title of a licensed document. The boilerplate can be found at the "addendum" part of the license. permissions: - commercial-use From 060b967c43bacbc0459a7c9fc14cfe020a6a94c3 Mon Sep 17 00:00:00 2001 From: Mike Linksvayer Date: Fri, 2 Sep 2022 14:25:09 -0700 Subject: [PATCH 55/70] spacing --- _licenses/gfdl-1.3.txt | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/_licenses/gfdl-1.3.txt b/_licenses/gfdl-1.3.txt index d696b0b..7177c40 100644 --- a/_licenses/gfdl-1.3.txt +++ b/_licenses/gfdl-1.3.txt @@ -3,21 +3,26 @@ title: GNU Free Documentation License v1.3 spdx-id: GFDL-1.3 -description: A copyleft license for software documentation that allows almost any use. +description: A copyleft license for software documentation. + how: Create a text file (typically named COPYING, as per GNU conventions) in the root of your source code and copy the text of the license into the file. note: The Free Software Foundation recommends taking the additional step of adding a boilerplate notice after the title of a licensed document. The boilerplate can be found at the "addendum" part of the license. +using: + permissions: - commercial-use - modifications - distribution - private-use + conditions: - include-copyright - disclose-source - same-license - document-changes + limitations: - liability - warranty From be0ffed9e89f2908a8706b171d49fb85b11978c4 Mon Sep 17 00:00:00 2001 From: Mike Linksvayer Date: Mon, 5 Sep 2022 13:54:12 -0700 Subject: [PATCH 56/70] Ignore testing of opensource.org which fails only in CI eg https://github.com/github/choosealicense.com/runs/8026421690?check_suite_focus=true --- Rakefile | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/Rakefile b/Rakefile index c1bd28d..ea3ef4a 100644 --- a/Rakefile +++ b/Rakefile @@ -17,7 +17,9 @@ task :test do enforce_https: true, validation: { ignore_script_embeds: true }, url_swap: { %r{https://choosealicense.com} => '' }, - url_ignore: [%r{https://github.com/github/choosealicense.com/edit/gh-pages/_licenses/}, %r{https://help.github.com}], + url_ignore: [%r{https://github.com/github/choosealicense.com/edit/gh-pages/_licenses/}, + %r{https://help.github.com}, + %r{https://opensource.org}], hydra: { max_concurrency: 10 }, check_img_http: true).run end From 537d2a7d7fa4105d7446722af284d6fb7c200ad3 Mon Sep 17 00:00:00 2001 From: Mike Linksvayer Date: Wed, 14 Sep 2022 08:11:24 -0700 Subject: [PATCH 57/70] Use examples From https://github.com/github/choosealicense.com/pull/918#issuecomment-1246154659 --- _licenses/gfdl-1.3.txt | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/_licenses/gfdl-1.3.txt b/_licenses/gfdl-1.3.txt index 7177c40..4967ab2 100644 --- a/_licenses/gfdl-1.3.txt +++ b/_licenses/gfdl-1.3.txt @@ -10,7 +10,10 @@ how: Create a text file (typically named COPYING, as per GNU conventions) in the note: The Free Software Foundation recommends taking the additional step of adding a boilerplate notice after the title of a licensed document. The boilerplate can be found at the "addendum" part of the license. using: - + GNU LilyPond (Documentation): https://git.savannah.gnu.org/cgit/lilypond.git/tree/COPYING.FDL + GNU nano (Documentation): https://git.savannah.gnu.org/cgit/nano.git/tree/COPYING.DOC + GNU Scientific Library (Documentation): https://git.savannah.gnu.org/cgit/gsl.git/tree/doc/_static/fdl.txt + permissions: - commercial-use - modifications From 4dfc9d921a878dfcd4a257aa69de61fd6d7aa9dd Mon Sep 17 00:00:00 2001 From: Mike Linksvayer Date: Mon, 26 Sep 2022 09:42:10 -0700 Subject: [PATCH 58/70] Qt docs example --- _licenses/gfdl-1.3.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_licenses/gfdl-1.3.txt b/_licenses/gfdl-1.3.txt index 4967ab2..30e01e9 100644 --- a/_licenses/gfdl-1.3.txt +++ b/_licenses/gfdl-1.3.txt @@ -11,8 +11,8 @@ note: The Free Software Foundation recommends taking the additional step of addi using: GNU LilyPond (Documentation): https://git.savannah.gnu.org/cgit/lilypond.git/tree/COPYING.FDL - GNU nano (Documentation): https://git.savannah.gnu.org/cgit/nano.git/tree/COPYING.DOC GNU Scientific Library (Documentation): https://git.savannah.gnu.org/cgit/gsl.git/tree/doc/_static/fdl.txt + Qt (Documentation): https://code.qt.io/cgit/qt/qt.git/tree/LICENSE.FDL permissions: - commercial-use From ebef287bbd44baba7bc04815acce253bf7e1f116 Mon Sep 17 00:00:00 2001 From: Mike Linksvayer Date: Mon, 26 Sep 2022 09:53:00 -0700 Subject: [PATCH 59/70] accommodate code.qt.io in tests --- spec/license_meta_spec.rb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/spec/license_meta_spec.rb b/spec/license_meta_spec.rb index 83126f8..4e624ce 100644 --- a/spec/license_meta_spec.rb +++ b/spec/license_meta_spec.rb @@ -48,7 +48,7 @@ describe 'license meta' do if example_url.start_with?('https://github.com/') example_url.gsub!(%r{\Ahttps://github.com/([\w-]+/[\w.-]+)/blob/(\S+)\z}, 'https://raw.githubusercontent.com/\1/\2') - elsif example_url.start_with?('https://git.savannah.gnu.org/', 'https://git.gnome.org/') + elsif example_url.start_with?('https://git.savannah.gnu.org/', 'https://git.gnome.org/', 'https://code.qt.io') example_url.gsub!(%r{/tree/}, '/plain/') elsif example_url.start_with?('https://bitbucket.org/') example_url.gsub!(%r{/src/}, '/raw/') From b62ee46b31ccb440211d0f22be92ade4a9afb5a6 Mon Sep 17 00:00:00 2001 From: Mike Linksvayer Date: Tue, 27 Dec 2022 15:03:56 -0800 Subject: [PATCH 60/70] Add "Modified" nickname to BSD-3-Clause Note it has a number of nicknames https://en.wikipedia.org/wiki/BSD_licenses#3-clause_license_(%22BSD_License_2.0%22,_%22Revised_BSD_License%22,_%22New_BSD_License%22,_or_%22Modified_BSD_License%22) the first two of which are captured in the current title. This change will facilitate matching a semi-common markup version, see https://github.com/licensee/licensee/pull/578 --- _licenses/bsd-3-clause.txt | 1 + 1 file changed, 1 insertion(+) diff --git a/_licenses/bsd-3-clause.txt b/_licenses/bsd-3-clause.txt index fb80171..aba1b44 100644 --- a/_licenses/bsd-3-clause.txt +++ b/_licenses/bsd-3-clause.txt @@ -1,6 +1,7 @@ --- title: BSD 3-Clause "New" or "Revised" License spdx-id: BSD-3-Clause +nickname: Modified BSD License hidden: false description: A permissive license similar to the BSD 2-Clause License, but with a 3rd clause that prohibits others from using the name of the copyright holder or its contributors to promote derived products without written consent. From eb6ec2fa9a17255a25225132675d398849732d70 Mon Sep 17 00:00:00 2001 From: Joas Sanon Date: Fri, 17 Mar 2023 12:48:35 -0400 Subject: [PATCH 61/70] Add stickiness to the table header Added stickiness to the table header so it stays visible while scrolling the licences list --- appendix.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/appendix.md b/appendix.md index e08fd83..c3e00f2 100644 --- a/appendix.md +++ b/appendix.md @@ -9,10 +9,10 @@ For reference, here is a table of every license described in the [choosealicense If you're here to choose a license, **[start from the home page](/)** to see a few licenses that will work for most cases. - +
{% assign types = "permissions|conditions|limitations" | split: "|" %} - + {% assign seen_tags = '' %} {% for type in types %} {% assign rules = site.data.rules[type] | sort: "label" %} From 38e8c11e0115655f5f0defd59fd7e0321b46552d Mon Sep 17 00:00:00 2001 From: Joas Sanon Date: Tue, 21 Mar 2023 19:59:47 -0400 Subject: [PATCH 62/70] Just an extra space in orer to trigger gh pages build --- appendix.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/appendix.md b/appendix.md index c3e00f2..e3c39c3 100644 --- a/appendix.md +++ b/appendix.md @@ -5,7 +5,7 @@ title: Appendix class: license-types --- -For reference, here is a table of every license described in the [choosealicense.com repository](https://github.com/github/choosealicense.com). +For reference, here is a table of every license described in the [choosealicense.com repository](https://github.com/github/choosealicense.com). If you're here to choose a license, **[start from the home page](/)** to see a few licenses that will work for most cases. From 41933b930643a0ce78b58988559044b40e299e37 Mon Sep 17 00:00:00 2001 From: Joas Sanon Date: Tue, 21 Mar 2023 20:02:50 -0400 Subject: [PATCH 63/70] Ok. --- appendix.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/appendix.md b/appendix.md index e3c39c3..c3e00f2 100644 --- a/appendix.md +++ b/appendix.md @@ -5,7 +5,7 @@ title: Appendix class: license-types --- -For reference, here is a table of every license described in the [choosealicense.com repository](https://github.com/github/choosealicense.com). +For reference, here is a table of every license described in the [choosealicense.com repository](https://github.com/github/choosealicense.com). If you're here to choose a license, **[start from the home page](/)** to see a few licenses that will work for most cases. From d5b399f069fd941be1239b1ed562a032af5df7ba Mon Sep 17 00:00:00 2001 From: Thomas Mechelke Date: Wed, 29 Mar 2023 19:14:30 +0200 Subject: [PATCH 64/70] Fix inconsistent quotes in UPL-1.0 Replace non-ASCII quotes with ASCII quotes to - match line 38: the "Software" - match line 60: PROVIDED "AS IS" - match the license authors version at https://oss.oracle.com/licenses/upl/ - match the spdx version at https://spdx.org/licenses/UPL-1.0.html --- _licenses/upl-1.0.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_licenses/upl-1.0.txt b/_licenses/upl-1.0.txt index e856f1b..784b31a 100644 --- a/_licenses/upl-1.0.txt +++ b/_licenses/upl-1.0.txt @@ -43,7 +43,7 @@ Works (as defined below), to deal in both (a) the Software, and (b) any piece of software and/or hardware listed in the lrgrwrks.txt file if -one is included with the Software (each a “Larger Work” to which the Software +one is included with the Software (each a "Larger Work" to which the Software is contributed by such licensors), without restriction, including without limitation the rights to copy, create From d68908d8296f45572d5ba95a6ebb01e6ef9dedbe Mon Sep 17 00:00:00 2001 From: Mike Linksvayer Date: Wed, 29 Mar 2023 15:17:57 -0700 Subject: [PATCH 65/70] update examples Update skater LICENSE url Replace example with Roc so that there's not two examples from one company --- _licenses/upl-1.0.txt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/_licenses/upl-1.0.txt b/_licenses/upl-1.0.txt index 784b31a..124c893 100644 --- a/_licenses/upl-1.0.txt +++ b/_licenses/upl-1.0.txt @@ -9,8 +9,8 @@ how: Insert the license or a link to it along with a copyright notice into your note: It is recommended to add a link to the license and copyright notice at the top of each source file, example text can be found at https://oss.oracle.com/licenses/upl/. using: - Oracle Product Images for Docker: https://github.com/oracle/docker-images/blob/main/LICENSE.txt - Skater: https://github.com/oracle/Skater/blob/master/LICENSE + Roc: https://github.com/roc-lang/roc/blob/main/LICENSE + Skater: https://github.com/oracle/skater/blob/main/LICENSE.txt Soufflé: https://github.com/souffle-lang/souffle/blob/master/LICENSE permissions: From dca67232fd65596ae722e17139f644a27aa46bfa Mon Sep 17 00:00:00 2001 From: Mike Linksvayer Date: Sat, 8 Apr 2023 11:53:32 -0700 Subject: [PATCH 66/70] Update appendix.md MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Felipe Lube de Bragança --- appendix.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/appendix.md b/appendix.md index c3e00f2..04eee2e 100644 --- a/appendix.md +++ b/appendix.md @@ -12,7 +12,7 @@ If you're here to choose a license, **[start from the home page](/)** to see a f
LicenseLicense
{% assign types = "permissions|conditions|limitations" | split: "|" %} - + {% assign seen_tags = '' %} {% for type in types %} {% assign rules = site.data.rules[type] | sort: "label" %} From b62b6e24162f7987076e48ac8a6f6da349833448 Mon Sep 17 00:00:00 2001 From: Mike Linksvayer Date: Sat, 8 Apr 2023 12:16:19 -0700 Subject: [PATCH 67/70] make whole row sticky --- appendix.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/appendix.md b/appendix.md index 04eee2e..46d5b8d 100644 --- a/appendix.md +++ b/appendix.md @@ -11,8 +11,8 @@ If you're here to choose a license, **[start from the home page](/)** to see a f
LicenseLicense
{% assign types = "permissions|conditions|limitations" | split: "|" %} - - + + {% assign seen_tags = '' %} {% for type in types %} {% assign rules = site.data.rules[type] | sort: "label" %} From bcf125b8a42ee5102be83adbe7f47b27a483d4b5 Mon Sep 17 00:00:00 2001 From: Hannes Papenberg Date: Wed, 31 May 2023 17:46:52 +0200 Subject: [PATCH 68/70] Add Joomla to community.md --- community.md | 1 + 1 file changed, 1 insertion(+) diff --git a/community.md b/community.md index ec2e260..2a8bd3f 100644 --- a/community.md +++ b/community.md @@ -20,5 +20,6 @@ Some communities have strong preferences for particular licenses. If you want to * [OpenBSD](https://www.openbsd.org/policy.html) prefers the [ISC License](/licenses/isc/) * [Rust](https://rust-lang.github.io/api-guidelines/necessities.html#crate-and-its-dependencies-have-a-permissive-license-c-permissive) crates are overwhelmingly licensed under both [MIT](/licenses/mit/) and [Apache License 2.0](/licenses/apache-2.0/) * [WordPress](https://wordpress.org/about/license/) plugins and themes must be [GNU GPLv2](/licenses/gpl-2.0/) (or later) +* [Joomla](https://docs.joomla.org/Joomla_Licenses) extensions and templates must be [GNU GPLv2](/licenses/gpl-2.0/) for the PHP code. Communities come in all shapes and sizes, and more than one community might be pertinent (e.g., keep in mind [your company](https://opensource.guide/legal/#what-does-my-companys-legal-team-need-to-know) if you work for one). The examples above are *very* well established. If the community you're building a project for doesn't have set-in-stone licensing traditions, or you don't see your project as part of any particular community, that's fine: [make your own choice of an open source license](/). From 89561eedde5075b7d58bc4f8101364ccc1da8b1c Mon Sep 17 00:00:00 2001 From: Hannes Papenberg Date: Wed, 31 May 2023 18:00:16 +0200 Subject: [PATCH 69/70] Update community.md Co-authored-by: Mike Linksvayer --- community.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/community.md b/community.md index 2a8bd3f..3ac9cd0 100644 --- a/community.md +++ b/community.md @@ -20,6 +20,6 @@ Some communities have strong preferences for particular licenses. If you want to * [OpenBSD](https://www.openbsd.org/policy.html) prefers the [ISC License](/licenses/isc/) * [Rust](https://rust-lang.github.io/api-guidelines/necessities.html#crate-and-its-dependencies-have-a-permissive-license-c-permissive) crates are overwhelmingly licensed under both [MIT](/licenses/mit/) and [Apache License 2.0](/licenses/apache-2.0/) * [WordPress](https://wordpress.org/about/license/) plugins and themes must be [GNU GPLv2](/licenses/gpl-2.0/) (or later) -* [Joomla](https://docs.joomla.org/Joomla_Licenses) extensions and templates must be [GNU GPLv2](/licenses/gpl-2.0/) for the PHP code. +* [Joomla](https://tm.joomla.org/joomla-license-faq.html#can-i-release-an-extension-under-a-non-gpl-license) extensions and templates must be [GNU GPLv2](/licenses/gpl-2.0/) for the PHP code. Communities come in all shapes and sizes, and more than one community might be pertinent (e.g., keep in mind [your company](https://opensource.guide/legal/#what-does-my-companys-legal-team-need-to-know) if you work for one). The examples above are *very* well established. If the community you're building a project for doesn't have set-in-stone licensing traditions, or you don't see your project as part of any particular community, that's fine: [make your own choice of an open source license](/). From 09a34808527752a497489f84fa80493346296545 Mon Sep 17 00:00:00 2001 From: Mike Linksvayer Date: Wed, 31 May 2023 10:11:40 -0700 Subject: [PATCH 70/70] update license link for zonedb --- _licenses/odbl-1.0.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_licenses/odbl-1.0.txt b/_licenses/odbl-1.0.txt index 161ed96..d52fc91 100644 --- a/_licenses/odbl-1.0.txt +++ b/_licenses/odbl-1.0.txt @@ -10,7 +10,7 @@ how: Create a text file (typically named LICENSE or LICENSE.txt) in the root of using: World Countries: https://github.com/mledoze/countries/blob/master/LICENSE OpenFlights: https://github.com/jpatokal/openflights/blob/master/data/LICENSE - Public Zone Database: https://github.com/zonedb/zonedb/blob/main/LICENSE.md + Public Zone Database: https://github.com/zonedb/zonedb/blob/main/LICENSE-DATA.md permissions: - commercial-use
License
License