From 6b554b769fd68e6995ba1e194d6c2c1f464b9ce4 Mon Sep 17 00:00:00 2001 From: Mike Linksvayer Date: Sat, 4 Mar 2017 10:26:17 -0800 Subject: [PATCH 01/70] Use license text from source The existing license text was introduced in https://github.com/github/choosealicense.com/pull/126 presumably by copying and pasting from https://creativecommons.org/publicdomain/zero/1.0/legalcode though I'm not sure how to explain the link at the end. Probably should be updated with https://creativecommons.org/publicdomain/zero/1.0/legalcode.txt or https://spdx.org/licenses/CC0-1.0.html ... latter marks disclaimer as optional and doesn't have first line "Creative Commons Legal Code". This commit uses former. Making due to https://github.com/benbalter/licensee/issues/172 but holding off on merge pending more discussion there. --- _licenses/cc0-1.0.txt | 203 ++++++++++++++++++++++-------------------- 1 file changed, 104 insertions(+), 99 deletions(-) diff --git a/_licenses/cc0-1.0.txt b/_licenses/cc0-1.0.txt index 886aaaf..72089c0 100644 --- a/_licenses/cc0-1.0.txt +++ b/_licenses/cc0-1.0.txt @@ -26,119 +26,124 @@ limitations: --- +Creative Commons Legal Code + CC0 1.0 Universal + CREATIVE COMMONS CORPORATION IS NOT A LAW FIRM AND DOES NOT PROVIDE + LEGAL SERVICES. DISTRIBUTION OF THIS DOCUMENT DOES NOT CREATE AN + ATTORNEY-CLIENT RELATIONSHIP. CREATIVE COMMONS PROVIDES THIS + INFORMATION ON AN "AS-IS" BASIS. CREATIVE COMMONS MAKES NO WARRANTIES + REGARDING THE USE OF THIS DOCUMENT OR THE INFORMATION OR WORKS + PROVIDED HEREUNDER, AND DISCLAIMS LIABILITY FOR DAMAGES RESULTING FROM + THE USE OF THIS DOCUMENT OR THE INFORMATION OR WORKS PROVIDED + HEREUNDER. + Statement of Purpose The laws of most jurisdictions throughout the world automatically confer -exclusive Copyright and Related Rights (defined below) upon the creator and -subsequent owner(s) (each and all, an "owner") of an original work of +exclusive Copyright and Related Rights (defined below) upon the creator +and subsequent owner(s) (each and all, an "owner") of an original work of authorship and/or a database (each, a "Work"). -Certain owners wish to permanently relinquish those rights to a Work for the -purpose of contributing to a commons of creative, cultural and scientific -works ("Commons") that the public can reliably and without fear of later -claims of infringement build upon, modify, incorporate in other works, reuse -and redistribute as freely as possible in any form whatsoever and for any -purposes, including without limitation commercial purposes. These owners may -contribute to the Commons to promote the ideal of a free culture and the -further production of creative, cultural and scientific works, or to gain -reputation or greater distribution for their Work in part through the use and -efforts of others. +Certain owners wish to permanently relinquish those rights to a Work for +the purpose of contributing to a commons of creative, cultural and +scientific works ("Commons") that the public can reliably and without fear +of later claims of infringement build upon, modify, incorporate in other +works, reuse and redistribute as freely as possible in any form whatsoever +and for any purposes, including without limitation commercial purposes. +These owners may contribute to the Commons to promote the ideal of a free +culture and the further production of creative, cultural and scientific +works, or to gain reputation or greater distribution for their Work in +part through the use and efforts of others. -For these and/or other purposes and motivations, and without any expectation -of additional consideration or compensation, the person associating CC0 with a -Work (the "Affirmer"), to the extent that he or she is an owner of Copyright -and Related Rights in the Work, voluntarily elects to apply CC0 to the Work -and publicly distribute the Work under its terms, with knowledge of his or her -Copyright and Related Rights in the Work and the meaning and intended legal -effect of CC0 on those rights. +For these and/or other purposes and motivations, and without any +expectation of additional consideration or compensation, the person +associating CC0 with a Work (the "Affirmer"), to the extent that he or she +is an owner of Copyright and Related Rights in the Work, voluntarily +elects to apply CC0 to the Work and publicly distribute the Work under its +terms, with knowledge of his or her Copyright and Related Rights in the +Work and the meaning and intended legal effect of CC0 on those rights. 1. Copyright and Related Rights. A Work made available under CC0 may be protected by copyright and related or neighboring rights ("Copyright and -Related Rights"). Copyright and Related Rights include, but are not limited -to, the following: +Related Rights"). Copyright and Related Rights include, but are not +limited to, the following: - i. the right to reproduce, adapt, distribute, perform, display, communicate, - and translate a Work; + i. the right to reproduce, adapt, distribute, perform, display, + communicate, and translate a Work; + ii. moral rights retained by the original author(s) and/or performer(s); +iii. publicity and privacy rights pertaining to a person's image or + likeness depicted in a Work; + iv. rights protecting against unfair competition in regards to a Work, + subject to the limitations in paragraph 4(a), below; + v. rights protecting the extraction, dissemination, use and reuse of data + in a Work; + vi. database rights (such as those arising under Directive 96/9/EC of the + European Parliament and of the Council of 11 March 1996 on the legal + protection of databases, and under any national implementation + thereof, including any amended or successor version of such + directive); and +vii. other similar, equivalent or corresponding rights throughout the + world based on applicable law or treaty, and any national + implementations thereof. - ii. moral rights retained by the original author(s) and/or performer(s); +2. Waiver. To the greatest extent permitted by, but not in contravention +of, applicable law, Affirmer hereby overtly, fully, permanently, +irrevocably and unconditionally waives, abandons, and surrenders all of +Affirmer's Copyright and Related Rights and associated claims and causes +of action, whether now known or unknown (including existing as well as +future claims and causes of action), in the Work (i) in all territories +worldwide, (ii) for the maximum duration provided by applicable law or +treaty (including future time extensions), (iii) in any current or future +medium and for any number of copies, and (iv) for any purpose whatsoever, +including without limitation commercial, advertising or promotional +purposes (the "Waiver"). Affirmer makes the Waiver for the benefit of each +member of the public at large and to the detriment of Affirmer's heirs and +successors, fully intending that such Waiver shall not be subject to +revocation, rescission, cancellation, termination, or any other legal or +equitable action to disrupt the quiet enjoyment of the Work by the public +as contemplated by Affirmer's express Statement of Purpose. - iii. publicity and privacy rights pertaining to a person's image or likeness - depicted in a Work; - - iv. rights protecting against unfair competition in regards to a Work, - subject to the limitations in paragraph 4(a), below; - - v. rights protecting the extraction, dissemination, use and reuse of data in - a Work; - - vi. database rights (such as those arising under Directive 96/9/EC of the - European Parliament and of the Council of 11 March 1996 on the legal - protection of databases, and under any national implementation thereof, - including any amended or successor version of such directive); and - - vii. other similar, equivalent or corresponding rights throughout the world - based on applicable law or treaty, and any national implementations thereof. - -2. Waiver. To the greatest extent permitted by, but not in contravention of, -applicable law, Affirmer hereby overtly, fully, permanently, irrevocably and -unconditionally waives, abandons, and surrenders all of Affirmer's Copyright -and Related Rights and associated claims and causes of action, whether now -known or unknown (including existing as well as future claims and causes of -action), in the Work (i) in all territories worldwide, (ii) for the maximum -duration provided by applicable law or treaty (including future time -extensions), (iii) in any current or future medium and for any number of -copies, and (iv) for any purpose whatsoever, including without limitation -commercial, advertising or promotional purposes (the "Waiver"). Affirmer makes -the Waiver for the benefit of each member of the public at large and to the -detriment of Affirmer's heirs and successors, fully intending that such Waiver -shall not be subject to revocation, rescission, cancellation, termination, or -any other legal or equitable action to disrupt the quiet enjoyment of the Work -by the public as contemplated by Affirmer's express Statement of Purpose. - -3. Public License Fallback. Should any part of the Waiver for any reason be -judged legally invalid or ineffective under applicable law, then the Waiver -shall be preserved to the maximum extent permitted taking into account -Affirmer's express Statement of Purpose. In addition, to the extent the Waiver -is so judged Affirmer hereby grants to each affected person a royalty-free, -non transferable, non sublicensable, non exclusive, irrevocable and -unconditional license to exercise Affirmer's Copyright and Related Rights in -the Work (i) in all territories worldwide, (ii) for the maximum duration -provided by applicable law or treaty (including future time extensions), (iii) -in any current or future medium and for any number of copies, and (iv) for any -purpose whatsoever, including without limitation commercial, advertising or -promotional purposes (the "License"). The License shall be deemed effective as -of the date CC0 was applied by Affirmer to the Work. Should any part of the -License for any reason be judged legally invalid or ineffective under -applicable law, such partial invalidity or ineffectiveness shall not -invalidate the remainder of the License, and in such case Affirmer hereby -affirms that he or she will not (i) exercise any of his or her remaining -Copyright and Related Rights in the Work or (ii) assert any associated claims -and causes of action with respect to the Work, in either case contrary to -Affirmer's express Statement of Purpose. +3. Public License Fallback. Should any part of the Waiver for any reason +be judged legally invalid or ineffective under applicable law, then the +Waiver shall be preserved to the maximum extent permitted taking into +account Affirmer's express Statement of Purpose. In addition, to the +extent the Waiver is so judged Affirmer hereby grants to each affected +person a royalty-free, non transferable, non sublicensable, non exclusive, +irrevocable and unconditional license to exercise Affirmer's Copyright and +Related Rights in the Work (i) in all territories worldwide, (ii) for the +maximum duration provided by applicable law or treaty (including future +time extensions), (iii) in any current or future medium and for any number +of copies, and (iv) for any purpose whatsoever, including without +limitation commercial, advertising or promotional purposes (the +"License"). The License shall be deemed effective as of the date CC0 was +applied by Affirmer to the Work. Should any part of the License for any +reason be judged legally invalid or ineffective under applicable law, such +partial invalidity or ineffectiveness shall not invalidate the remainder +of the License, and in such case Affirmer hereby affirms that he or she +will not (i) exercise any of his or her remaining Copyright and Related +Rights in the Work or (ii) assert any associated claims and causes of +action with respect to the Work, in either case contrary to Affirmer's +express Statement of Purpose. 4. Limitations and Disclaimers. - a. No trademark or patent rights held by Affirmer are waived, abandoned, - surrendered, licensed or otherwise affected by this document. - - b. Affirmer offers the Work as-is and makes no representations or warranties - of any kind concerning the Work, express, implied, statutory or otherwise, - including without limitation warranties of title, merchantability, fitness - for a particular purpose, non infringement, or the absence of latent or - other defects, accuracy, or the present or absence of errors, whether or not - discoverable, all to the greatest extent permissible under applicable law. - - c. Affirmer disclaims responsibility for clearing rights of other persons - that may apply to the Work or any use thereof, including without limitation - any person's Copyright and Related Rights in the Work. Further, Affirmer - disclaims responsibility for obtaining any necessary consents, permissions - or other rights required for any use of the Work. - - d. Affirmer understands and acknowledges that Creative Commons is not a - party to this document and has no duty or obligation with respect to this - CC0 or use of the Work. - -For more information, please see - + a. No trademark or patent rights held by Affirmer are waived, abandoned, + surrendered, licensed or otherwise affected by this document. + b. Affirmer offers the Work as-is and makes no representations or + warranties of any kind concerning the Work, express, implied, + statutory or otherwise, including without limitation warranties of + title, merchantability, fitness for a particular purpose, non + infringement, or the absence of latent or other defects, accuracy, or + the present or absence of errors, whether or not discoverable, all to + the greatest extent permissible under applicable law. + c. Affirmer disclaims responsibility for clearing rights of other persons + that may apply to the Work or any use thereof, including without + limitation any person's Copyright and Related Rights in the Work. + Further, Affirmer disclaims responsibility for obtaining any necessary + consents, permissions or other rights required for any use of the + Work. + d. Affirmer understands and acknowledges that Creative Commons is not a + party to this document and has no duty or obligation with respect to + this CC0 or use of the Work. From d9cbe3830cc06ec731dbc155af7567644a88a209 Mon Sep 17 00:00:00 2001 From: Laurent Joubert Date: Tue, 4 Jul 2017 18:26:48 +0200 Subject: [PATCH 02/70] Added CeCILL Licenses v2.1 --- _licenses/cecill-2.1.txt | 283 +++++++++++++++++++++++++++++++++++++++ 1 file changed, 283 insertions(+) create mode 100644 _licenses/cecill-2.1.txt diff --git a/_licenses/cecill-2.1.txt b/_licenses/cecill-2.1.txt new file mode 100644 index 0000000..4f54d58 --- /dev/null +++ b/_licenses/cecill-2.1.txt @@ -0,0 +1,283 @@ +--- +title: CeCILL Free Software License Agreement v2.1 +spdx-id: CECILL-2.1 +source: http://www.cecill.info/licences/Licence_CeCILL_V2.1-fr.html +featured: false +hidden: false + +description: French open-source license made by the CEA, INRIA and CNRS, compatible with the GNU GPL v2.0 and v3.0 + +how: Create a text file (typically named LICENSE or LICENSE.txt) in the root of your source code and copy the text of the license into the file. + +using: + - VITAM: https://github.com/ProgrammeVitam/vitam/blob/master_0.15.x/Licence_CeCILL_V2.1-en.txt + - SCILAB: https://www.scilab.org/fr/scilab/license + - MARMOT: http://projects.noc.ac.uk/marmot/marmot-11-software + +permissions: + - commercial-use + - modifications + - distribution + - private-use + - patent-use + +conditions: + - include-copyright + - disclose-source + - same-license + +limitations: + - liability + - warranty + +--- + +CONTRAT DE LICENCE DE LOGICIEL LIBRE CeCILL + +Version 2.1 du 2013-06-21 + +Avertissement + +Ce contrat est une licence de logiciel libre issue d'une concertation entre ses auteurs afin que le respect de deux grands principes préside à sa rédaction: + +* d'une part, le respect des principes de diffusion des logiciels libres: accès au code source, droits étendus conférés aux utilisateurs, + +* d'autre part, la désignation d'un droit applicable, le droit français, auquel elle est conforme, tant au regard du droit de la responsabilité civile que du droit de la propriété intellectuelle et de la protection qu'il offre aux auteurs et titulaires des droits patrimoniaux sur un logiciel. + +Les auteurs de la licence CeCILL (Ce[a] C[nrs] I[nria] L[ogiciel] L[ibre]) sont: + +Commissariat à l'énergie atomique et aux énergies alternatives - CEA, établissement public de recherche à caractère scientifique, technique et industriel, dont le siège est situé 25 rue Leblanc, immeuble Le Ponant D, 75015 Paris. + +Centre National de la Recherche Scientifique - CNRS, établissement public à caractère scientifique et technologique, dont le siège est situé 3 rue Michel-Ange, 75794 Paris cedex 16. + +Institut National de Recherche en Informatique et en Automatique - Inria, établissement public à caractère scientifique et technologique, dont le siège est situé Domaine de Voluceau, Rocquencourt, BP 105, 78153 Le Chesnay cedex. + +Préambule + +Ce contrat est une licence de logiciel libre dont l'objectif est de conférer aux utilisateurs la liberté de modification et de redistribution du logiciel régi par cette licence dans le cadre d'un modèle de diffusion en logiciel libre. + +L'exercice de ces libertés est assorti de certains devoirs à la charge des utilisateurs afin de préserver ce statut au cours des redistributions ultérieures. + +L'accessibilité au code source et les droits de copie, de modification et de redistribution qui en découlent ont pour contrepartie de n'offrir aux utilisateurs qu'une garantie limitée et de ne faire peser sur l'auteur du logiciel, le titulaire des droits patrimoniaux et les concédants successifs qu'une responsabilité restreinte. + +A cet égard l'attention de l'utilisateur est attirée sur les risques associés au chargement, à l'utilisation, à la modification et/ou au développement et à la reproduction du logiciel par l'utilisateur étant donné sa spécificité de logiciel libre, qui peut le rendre complexe à manipuler et qui le réserve donc à des développeurs ou des professionnels avertis possédant des connaissances informatiques approfondies. Les utilisateurs sont donc invités à charger et tester l'adéquation du logiciel à leurs besoins dans des conditions permettant d'assurer la sécurité de leurs systèmes et/ou de leurs données et, plus généralement, à l'utiliser et l'exploiter dans les mêmes conditions de sécurité. Ce contrat peut être reproduit et diffusé librement, sous réserve de le conserver en l'état, sans ajout ni suppression de clauses. + +Ce contrat est susceptible de s'appliquer à tout logiciel dont le titulaire des droits patrimoniaux décide de soumettre l'exploitation aux dispositions qu'il contient. + +Une liste de questions fréquemment posées se trouve sur le site web officiel de la famille des licences CeCILL (http://www.cecill.info/index.fr.html) pour toute clarification qui serait nécessaire. + +Article 1 - DEFINITIONS + +Dans ce contrat, les termes suivants, lorsqu'ils seront écrits avec une lettre capitale, auront la signification suivante: + +Contrat: désigne le présent contrat de licence, ses éventuelles versions postérieures et annexes. + +Logiciel: désigne le logiciel sous sa forme de Code Objet et/ou de Code Source et le cas échéant sa documentation, dans leur état au moment de l'acceptation du Contrat par le Licencié. + +Logiciel Initial: désigne le Logiciel sous sa forme de Code Source et éventuellement de Code Objet et le cas échéant sa documentation, dans leur état au moment de leur première diffusion sous les termes du Contrat. + +Logiciel Modifié: désigne le Logiciel modifié par au moins une Contribution. + +Code Source: désigne l'ensemble des instructions et des lignes de programme du Logiciel et auquel l'accès est nécessaire en vue de modifier le Logiciel. + +Code Objet: désigne les fichiers binaires issus de la compilation du Code Source. + +Titulaire: désigne le ou les détenteurs des droits patrimoniaux d'auteur sur le Logiciel Initial. + +Licencié: désigne le ou les utilisateurs du Logiciel ayant accepté le Contrat. + +Contributeur: désigne le Licencié auteur d'au moins une Contribution. + +Concédant: désigne le Titulaire ou toute personne physique ou morale distribuant le Logiciel sous le Contrat. + +Contribution: désigne l'ensemble des modifications, corrections, traductions, adaptations et/ou nouvelles fonctionnalités intégrées dans le Logiciel par tout Contributeur, ainsi que tout Module Interne. + +Module: désigne un ensemble de fichiers sources y compris leur documentation qui permet de réaliser des fonctionnalités ou services supplémentaires à ceux fournis par le Logiciel. + +Module Externe: désigne tout Module, non dérivé du Logiciel, tel que ce Module et le Logiciel s'exécutent dans des espaces d'adressage différents, l'un appelant l'autre au moment de leur exécution. + +Module Interne: désigne tout Module lié au Logiciel de telle sorte qu'ils s'exécutent dans le même espace d'adressage. + +GNU GPL: désigne la GNU General Public License dans sa version 2 ou toute version ultérieure, telle que publiée par Free Software Foundation Inc. + +GNU Affero GPL: désigne la GNU Affero General Public License dans sa version 3 ou toute version ultérieure, telle que publiée par Free Software Foundation Inc. + +EUPL: désigne la Licence Publique de l'Union européenne dans sa version 1.1 ou toute version ultérieure, telle que publiée par la Commission Européenne. + +Parties: désigne collectivement le Licencié et le Concédant. + +Ces termes s'entendent au singulier comme au pluriel. + +Article 2 - OBJET + +Le Contrat a pour objet la concession par le Concédant au Licencié d'une licence non exclusive, cessible et mondiale du Logiciel telle que définie ci-après à l'article 5 <#etendue> pour toute la durée de protection des droits portant sur ce Logiciel. + +Article 3 - ACCEPTATION + +3.1 L'acceptation par le Licencié des termes du Contrat est réputée acquise du fait du premier des faits suivants: + +* (i) le chargement du Logiciel par tout moyen notamment par téléchargement à partir d'un serveur distant ou par chargement à partir d'un support physique; + +* (ii) le premier exercice par le Licencié de l'un quelconque des droits concédés par le Contrat. + +3.2 Un exemplaire du Contrat, contenant notamment un avertissement relatif aux spécificités du Logiciel, à la restriction de garantie et à la limitation à un usage par des utilisateurs expérimentés a été mis à disposition du Licencié préalablement à son acceptation telle que définie à l'article 3.1 <#acceptation-acquise> ci dessus et le Licencié reconnaît en avoir pris connaissance. + +Article 4 - ENTREE EN VIGUEUR ET DUREE + +4.1 ENTREE EN VIGUEUR + +Le Contrat entre en vigueur à la date de son acceptation par le Licencié telle que définie en 3.1 <#acceptation-acquise>. + +4.2 DUREE + +Le Contrat produira ses effets pendant toute la durée légale de protection des droits patrimoniaux portant sur le Logiciel. + +Article 5 - ETENDUE DES DROITS CONCEDES + +Le Concédant concède au Licencié, qui accepte, les droits suivants sur le Logiciel pour toutes destinations et pour la durée du Contrat dans les conditions ci-après détaillées. + +Par ailleurs, si le Concédant détient ou venait à détenir un ou plusieurs brevets d'invention protégeant tout ou partie des fonctionnalités du Logiciel ou de ses composants, il s'engage à ne pas opposer les éventuels droits conférés par ces brevets aux Licenciés successifs qui utiliseraient, exploiteraient ou modifieraient le Logiciel. En cas de cession de ces brevets, le Concédant s'engage à faire reprendre les obligations du présent alinéa aux cessionnaires. + +5.1 DROIT D'UTILISATION + +Le Licencié est autorisé à utiliser le Logiciel, sans restriction quant aux domaines d'application, étant ci-après précisé que cela comporte: + +1. la reproduction permanente ou provisoire du Logiciel en tout ou partie par tout moyen et sous toute forme. + +2. le chargement, l'affichage, l'exécution, ou le stockage du Logiciel sur tout support. + +3. la possibilité d'en observer, d'en étudier, ou d'en tester le fonctionnement afin de déterminer les idées et principes qui sont à la base de n'importe quel élément de ce Logiciel; et ceci, lorsque le Licencié effectue toute opération de chargement, d'affichage, d'exécution, de transmission ou de stockage du Logiciel qu'il est en droit d'effectuer en vertu du Contrat. + +5.2 DROIT D'APPORTER DES CONTRIBUTIONS + +Le droit d'apporter des Contributions comporte le droit de traduire, d'adapter, d'arranger ou d'apporter toute autre modification au Logiciel et le droit de reproduire le logiciel en résultant. + +Le Licencié est autorisé à apporter toute Contribution au Logiciel sous réserve de mentionner, de façon explicite, son nom en tant qu'auteur de cette Contribution et la date de création de celle-ci. + +5.3 DROIT DE DISTRIBUTION + +Le droit de distribution comporte notamment le droit de diffuser, de transmettre et de communiquer le Logiciel au public sur tout support et par tout moyen ainsi que le droit de mettre sur le marché à titre onéreux ou gratuit, un ou des exemplaires du Logiciel par tout procédé. + +Le Licencié est autorisé à distribuer des copies du Logiciel, modifié ou non, à des tiers dans les conditions ci-après détaillées. + +5.3.1 DISTRIBUTION DU LOGICIEL SANS MODIFICATION + +Le Licencié est autorisé à distribuer des copies conformes du Logiciel, sous forme de Code Source ou de Code Objet, à condition que cette distribution respecte les dispositions du Contrat dans leur totalité et soit accompagnée: + +1. d'un exemplaire du Contrat, + +2. d'un avertissement relatif à la restriction de garantie et de responsabilité du Concédant telle que prévue aux articles 8 <#responsabilite> et 9 <#garantie>, + +et que, dans le cas où seul le Code Objet du Logiciel est redistribué, le Licencié permette un accès effectif au Code Source complet du Logiciel pour une durée d'au moins 3 ans à compter de la distribution du logiciel, étant entendu que le coût additionnel d'acquisition du Code Source ne devra pas excéder le simple coût de transfert des données. + +5.3.2 DISTRIBUTION DU LOGICIEL MODIFIE + +Lorsque le Licencié apporte une Contribution au Logiciel, les conditions de distribution du Logiciel Modifié en résultant sont alors soumises à l'intégralité des dispositions du Contrat. + +Le Licencié est autorisé à distribuer le Logiciel Modifié, sous forme de code source ou de code objet, à condition que cette distribution respecte les dispositions du Contrat dans leur totalité et soit accompagnée: + +1. d'un exemplaire du Contrat, + +2. d'un avertissement relatif à la restriction de garantie et de responsabilité du Concédant telle que prévue aux articles 8 <#responsabilite> et 9 <#garantie>, + +et, dans le cas où seul le code objet du Logiciel Modifié est redistribué, + +3. d'une note précisant les conditions d'accès effectif au code source complet du Logiciel Modifié, pendant une période d'au moins 3 ans à compter de la distribution du Logiciel Modifié, étant entendu que le coût additionnel d'acquisition du code source ne devra pas excéder le simple coût de transfert des données. + +5.3.3 DISTRIBUTION DES MODULES EXTERNES + +Lorsque le Licencié a développé un Module Externe les conditions du Contrat ne s'appliquent pas à ce Module Externe, qui peut être distribué sous un contrat de licence différent. + +5.3.4 COMPATIBILITE AVEC D'AUTRES LICENCES + +Le Licencié peut inclure un code soumis aux dispositions d'une des versions de la licence GNU GPL, GNU Affero GPL et/ou EUPL dans le Logiciel modifié ou non et distribuer l'ensemble sous les conditions de la même version de la licence GNU GPL, GNU Affero GPL et/ou EUPL. + +Le Licencié peut inclure le Logiciel modifié ou non dans un code soumis aux dispositions d'une des versions de la licence GNU GPL, GNU Affero GPL et/ou EUPL et distribuer l'ensemble sous les conditions de la même version de la licence GNU GPL, GNU Affero GPL et/ou EUPL. + +Article 6 - PROPRIETE INTELLECTUELLE + +6.1 SUR LE LOGICIEL INITIAL + +Le Titulaire est détenteur des droits patrimoniaux sur le Logiciel Initial. Toute utilisation du Logiciel Initial est soumise au respect des conditions dans lesquelles le Titulaire a choisi de diffuser son oeuvre et nul autre n'a la faculté de modifier les conditions de diffusion de ce Logiciel Initial. + +Le Titulaire s'engage à ce que le Logiciel Initial reste au moins régi par le Contrat et ce, pour la durée visée à l'article 4.2 <#duree>. + +6.2 SUR LES CONTRIBUTIONS + +Le Licencié qui a développé une Contribution est titulaire sur celle-ci des droits de propriété intellectuelle dans les conditions définies par la législation applicable. + +6.3 SUR LES MODULES EXTERNES + +Le Licencié qui a développé un Module Externe est titulaire sur celui-ci des droits de propriété intellectuelle dans les conditions définies par la législation applicable et reste libre du choix du contrat régissant sa diffusion. + +6.4 DISPOSITIONS COMMUNES + +Le Licencié s'engage expressément: + +1. à ne pas supprimer ou modifier de quelque manière que ce soit les mentions de propriété intellectuelle apposées sur le Logiciel; + +2. à reproduire à l'identique lesdites mentions de propriété intellectuelle sur les copies du Logiciel modifié ou non. + +Le Licencié s'engage à ne pas porter atteinte, directement ou indirectement, aux droits de propriété intellectuelle du Titulaire et/ou des Contributeurs sur le Logiciel et à prendre, le cas échéant, à l'égard de son personnel toutes les mesures nécessaires pour assurer le respect des dits droits de propriété intellectuelle du Titulaire et/ou des Contributeurs. + +Article 7 - SERVICES ASSOCIES + +7.1 Le Contrat n'oblige en aucun cas le Concédant à la réalisation de prestations d'assistance technique ou de maintenance du Logiciel. + +Cependant le Concédant reste libre de proposer ce type de services. Les termes et conditions d'une telle assistance technique et/ou d'une telle maintenance seront alors déterminés dans un acte séparé. Ces actes de maintenance et/ou assistance technique n'engageront que la seule responsabilité du Concédant qui les propose. + +7.2 De même, tout Concédant est libre de proposer, sous sa seule responsabilité, à ses licenciés une garantie, qui n'engagera que lui, lors de la redistribution du Logiciel et/ou du Logiciel Modifié et ce, dans les conditions qu'il souhaite. Cette garantie et les modalités financières de son application feront l'objet d'un acte séparé entre le Concédant et le Licencié. + +Article 8 - RESPONSABILITE + +8.1 Sous réserve des dispositions de l'article 8.2 <#limite-responsabilite>, le Licencié a la faculté, sous réserve de prouver la faute du Concédant concerné, de solliciter la réparation du préjudice direct qu'il subirait du fait du Logiciel et dont il apportera la preuve. + +8.2 La responsabilité du Concédant est limitée aux engagements pris en application du Contrat et ne saurait être engagée en raison notamment: (i) des dommages dus à l'inexécution, totale ou partielle, de ses obligations par le Licencié, (ii) des dommages directs ou indirects découlant de l'utilisation ou des performances du Logiciel subis par le Licencié et (iii) plus généralement d'un quelconque dommage indirect. En particulier, les Parties conviennent expressément que tout préjudice financier ou commercial (par exemple perte de données, perte de bénéfices, perte d'exploitation, perte de clientèle ou de commandes, manque à gagner, trouble commercial quelconque) ou toute action dirigée contre le Licencié par un tiers, constitue un dommage indirect et n'ouvre pas droit à réparation par le Concédant. + +Article 9 - GARANTIE + +9.1 Le Licencié reconnaît que l'état actuel des connaissances scientifiques et techniques au moment de la mise en circulation du Logiciel ne permet pas d'en tester et d'en vérifier toutes les utilisations ni de détecter l'existence d'éventuels défauts. L'attention du Licencié a été attirée sur ce point sur les risques associés au chargement, à l'utilisation, la modification et/ou au développement et à la reproduction du Logiciel qui sont réservés à des utilisateurs avertis. + +Il relève de la responsabilité du Licencié de contrôler, par tous moyens, l'adéquation du produit à ses besoins, son bon fonctionnement et de s'assurer qu'il ne causera pas de dommages aux personnes et aux biens. + +9.2 Le Concédant déclare de bonne foi être en droit de concéder l'ensemble des droits attachés au Logiciel (comprenant notamment les droits visés à l'article 5 <#etendue>). + +9.3 Le Licencié reconnaît que le Logiciel est fourni "en l'état" par le Concédant sans autre garantie, expresse ou tacite, que celle prévue à l'article 9.2 <#bonne-foi> et notamment sans aucune garantie sur sa valeur commerciale, son caractère sécurisé, innovant ou pertinent. + +En particulier, le Concédant ne garantit pas que le Logiciel est exempt d'erreur, qu'il fonctionnera sans interruption, qu'il sera compatible avec l'équipement du Licencié et sa configuration logicielle ni qu'il remplira les besoins du Licencié. + +9.4 Le Concédant ne garantit pas, de manière expresse ou tacite, que le Logiciel ne porte pas atteinte à un quelconque droit de propriété intellectuelle d'un tiers portant sur un brevet, un logiciel ou sur tout autre droit de propriété. Ainsi, le Concédant exclut toute garantie au profit du Licencié contre les actions en contrefaçon qui pourraient être diligentées au titre de l'utilisation, de la modification, et de la redistribution du Logiciel. Néanmoins, si de telles actions sont exercées contre le Licencié, le Concédant lui apportera son expertise technique et juridique pour sa défense. Cette expertise technique et juridique est déterminée au cas par cas entre le Concédant concerné et le Licencié dans le cadre d'un protocole d'accord. Le Concédant dégage toute responsabilité quant à l'utilisation de la dénomination du Logiciel par le Licencié. Aucune garantie n'est apportée quant à l'existence de droits antérieurs sur le nom du Logiciel et sur l'existence d'une marque. + +Article 10 - RESILIATION + +10.1 En cas de manquement par le Licencié aux obligations mises à sa charge par le Contrat, le Concédant pourra résilier de plein droit le Contrat trente (30) jours après notification adressée au Licencié et restée sans effet. + +10.2 Le Licencié dont le Contrat est résilié n'est plus autorisé à utiliser, modifier ou distribuer le Logiciel. Cependant, toutes les licences qu'il aura concédées antérieurement à la résiliation du Contrat resteront valides sous réserve qu'elles aient été effectuées en conformité avec le Contrat. + +Article 11 - DISPOSITIONS DIVERSES + +11.1 CAUSE EXTERIEURE +Aucune des Parties ne sera responsable d'un retard ou d'une défaillance d'exécution du Contrat qui serait dû à un cas de force majeure, un cas fortuit ou une cause extérieure, telle que, notamment, le mauvais fonctionnement ou les interruptions du réseau électrique ou de télécommunication, la paralysie du réseau liée à une attaque informatique, l'intervention des autorités gouvernementales, les catastrophes naturelles, les dégâts des eaux, les tremblements de terre, le feu, les explosions, les grèves et les conflits sociaux, l'état de guerre... + +11.2 Le fait, par l'une ou l'autre des Parties, d'omettre en une ou plusieurs occasions de se prévaloir d'une ou plusieurs dispositions du Contrat, ne pourra en aucun cas impliquer renonciation par la Partie intéressée à s'en prévaloir ultérieurement. + +11.3 Le Contrat annule et remplace toute convention antérieure, écrite ou orale, entre les Parties sur le même objet et constitue l'accord entier entre les Parties sur cet objet. Aucune addition ou modification aux termes du Contrat n'aura d'effet à l'égard des Parties à moins d'être faite par écrit et signée par leurs représentants dûment habilités. + +11.4 Dans l'hypothèse où une ou plusieurs des dispositions du Contrat s'avèrerait contraire à une loi ou à un texte applicable, existants ou futurs, cette loi ou ce texte prévaudrait, et les Parties feraient les amendements nécessaires pour se conformer à cette loi ou à ce texte. Toutes les autres dispositions resteront en vigueur. De même, la nullité, pour quelque raison que ce soit, d'une des dispositions du Contrat ne saurait entraîner la nullité de l'ensemble du Contrat. + +11.5 LANGUE +Le Contrat est rédigé en langue française et en langue anglaise, ces deux versions faisant également foi. + +Article 12 - NOUVELLES VERSIONS DU CONTRAT + +12.1 Toute personne est autorisée à copier et distribuer des copies de ce Contrat. + +12.2 Afin d'en préserver la cohérence, le texte du Contrat est protégé et ne peut être modifié que par les auteurs de la licence, lesquels se réservent le droit de publier périodiquement des mises à jour ou de nouvelles versions du Contrat, qui posséderont chacune un numéro distinct. Ces versions ultérieures seront susceptibles de prendre en compte de nouvelles problématiques rencontrées par les logiciels libres. + +12.3 Tout Logiciel diffusé sous une version donnée du Contrat ne pourra faire l'objet d'une diffusion ultérieure que sous la même version du Contrat ou une version postérieure, sous réserve des dispositions de l'article 5.3.4 <#compatibilite>. + +Article 13 - LOI APPLICABLE ET COMPETENCE TERRITORIALE + +13.1 Le Contrat est régi par la loi française. Les Parties conviennent de tenter de régler à l'amiable les différends ou litiges qui viendraient à se produire par suite ou à l'occasion du Contrat. + +13.2 A défaut d'accord amiable dans un délai de deux (2) mois à compter de leur survenance et sauf situation relevant d'une procédure d'urgence, les différends ou litiges seront portés par la Partie la plus diligente devant les Tribunaux compétents de Paris. From 65828e1d0ff1beb24b39af8e943d0b97d60dbc70 Mon Sep 17 00:00:00 2001 From: Mike Linksvayer Date: Tue, 4 Jul 2017 12:26:14 -0700 Subject: [PATCH 03/70] rm fields that should be defaulted to --- _licenses/cecill-2.1.txt | 2 -- 1 file changed, 2 deletions(-) diff --git a/_licenses/cecill-2.1.txt b/_licenses/cecill-2.1.txt index 4f54d58..720e465 100644 --- a/_licenses/cecill-2.1.txt +++ b/_licenses/cecill-2.1.txt @@ -2,8 +2,6 @@ title: CeCILL Free Software License Agreement v2.1 spdx-id: CECILL-2.1 source: http://www.cecill.info/licences/Licence_CeCILL_V2.1-fr.html -featured: false -hidden: false description: French open-source license made by the CEA, INRIA and CNRS, compatible with the GNU GPL v2.0 and v3.0 From a792218c0f0a444c866b21a9cedbd40856e67c7e Mon Sep 17 00:00:00 2001 From: Laurent Joubert Date: Thu, 6 Jul 2017 11:25:29 +0200 Subject: [PATCH 04/70] Update cecill-2.1.txt - Corrected link to TXT version - Corrected text to right column width - Updated "using" projects --- _licenses/cecill-2.1.txt | 547 ++++++++++++++++++++++++++++++--------- 1 file changed, 423 insertions(+), 124 deletions(-) diff --git a/_licenses/cecill-2.1.txt b/_licenses/cecill-2.1.txt index 720e465..85d21ee 100644 --- a/_licenses/cecill-2.1.txt +++ b/_licenses/cecill-2.1.txt @@ -1,16 +1,16 @@ --- title: CeCILL Free Software License Agreement v2.1 spdx-id: CECILL-2.1 -source: http://www.cecill.info/licences/Licence_CeCILL_V2.1-fr.html +source: http://www.cecill.info/licences/Licence_CeCILL_V2.1-fr.txt description: French open-source license made by the CEA, INRIA and CNRS, compatible with the GNU GPL v2.0 and v3.0 -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. +how: Create a text file (typically named LICENSE or LICENCE) in the root of your source code and copy the text of the license into the file. using: - VITAM: https://github.com/ProgrammeVitam/vitam/blob/master_0.15.x/Licence_CeCILL_V2.1-en.txt - - SCILAB: https://www.scilab.org/fr/scilab/license - - MARMOT: http://projects.noc.ac.uk/marmot/marmot-11-software + - Test-Compta-Demat: https://github.com/DGFiP/Test-Compta-Demat/blob/master/src/testeur/Licence_CeCILL_V2.1-fr.txt + - BMC-Tools: https://github.com/ANSSI-FR/bmc-tools/blob/master/LICENCE.txt permissions: - commercial-use @@ -30,252 +30,551 @@ limitations: --- -CONTRAT DE LICENCE DE LOGICIEL LIBRE CeCILL + + CONTRAT DE LICENCE DE LOGICIEL LIBRE CeCILL Version 2.1 du 2013-06-21 -Avertissement -Ce contrat est une licence de logiciel libre issue d'une concertation entre ses auteurs afin que le respect de deux grands principes préside à sa rédaction: + Avertissement -* d'une part, le respect des principes de diffusion des logiciels libres: accès au code source, droits étendus conférés aux utilisateurs, +Ce contrat est une licence de logiciel libre issue d'une concertation +entre ses auteurs afin que le respect de deux grands principes préside à +sa rédaction: -* d'autre part, la désignation d'un droit applicable, le droit français, auquel elle est conforme, tant au regard du droit de la responsabilité civile que du droit de la propriété intellectuelle et de la protection qu'il offre aux auteurs et titulaires des droits patrimoniaux sur un logiciel. + * d'une part, le respect des principes de diffusion des logiciels + libres: accès au code source, droits étendus conférés aux utilisateurs, + * d'autre part, la désignation d'un droit applicable, le droit + français, auquel elle est conforme, tant au regard du droit de la + responsabilité civile que du droit de la propriété intellectuelle et + de la protection qu'il offre aux auteurs et titulaires des droits + patrimoniaux sur un logiciel. -Les auteurs de la licence CeCILL (Ce[a] C[nrs] I[nria] L[ogiciel] L[ibre]) sont: +Les auteurs de la licence CeCILL (Ce[a] C[nrs] I[nria] L[ogiciel] L[ibre]) +sont: -Commissariat à l'énergie atomique et aux énergies alternatives - CEA, établissement public de recherche à caractère scientifique, technique et industriel, dont le siège est situé 25 rue Leblanc, immeuble Le Ponant D, 75015 Paris. +Commissariat à l'énergie atomique et aux énergies alternatives - CEA, +établissement public de recherche à caractère scientifique, technique et +industriel, dont le siège est situé 25 rue Leblanc, immeuble Le Ponant +D, 75015 Paris. -Centre National de la Recherche Scientifique - CNRS, établissement public à caractère scientifique et technologique, dont le siège est situé 3 rue Michel-Ange, 75794 Paris cedex 16. +Centre National de la Recherche Scientifique - CNRS, établissement +public à caractère scientifique et technologique, dont le siège est +situé 3 rue Michel-Ange, 75794 Paris cedex 16. -Institut National de Recherche en Informatique et en Automatique - Inria, établissement public à caractère scientifique et technologique, dont le siège est situé Domaine de Voluceau, Rocquencourt, BP 105, 78153 Le Chesnay cedex. +Institut National de Recherche en Informatique et en Automatique - +Inria, établissement public à caractère scientifique et technologique, +dont le siège est situé Domaine de Voluceau, Rocquencourt, BP 105, 78153 +Le Chesnay cedex. -Préambule -Ce contrat est une licence de logiciel libre dont l'objectif est de conférer aux utilisateurs la liberté de modification et de redistribution du logiciel régi par cette licence dans le cadre d'un modèle de diffusion en logiciel libre. + Préambule -L'exercice de ces libertés est assorti de certains devoirs à la charge des utilisateurs afin de préserver ce statut au cours des redistributions ultérieures. +Ce contrat est une licence de logiciel libre dont l'objectif est de +conférer aux utilisateurs la liberté de modification et de +redistribution du logiciel régi par cette licence dans le cadre d'un +modèle de diffusion en logiciel libre. -L'accessibilité au code source et les droits de copie, de modification et de redistribution qui en découlent ont pour contrepartie de n'offrir aux utilisateurs qu'une garantie limitée et de ne faire peser sur l'auteur du logiciel, le titulaire des droits patrimoniaux et les concédants successifs qu'une responsabilité restreinte. +L'exercice de ces libertés est assorti de certains devoirs à la charge +des utilisateurs afin de préserver ce statut au cours des +redistributions ultérieures. -A cet égard l'attention de l'utilisateur est attirée sur les risques associés au chargement, à l'utilisation, à la modification et/ou au développement et à la reproduction du logiciel par l'utilisateur étant donné sa spécificité de logiciel libre, qui peut le rendre complexe à manipuler et qui le réserve donc à des développeurs ou des professionnels avertis possédant des connaissances informatiques approfondies. Les utilisateurs sont donc invités à charger et tester l'adéquation du logiciel à leurs besoins dans des conditions permettant d'assurer la sécurité de leurs systèmes et/ou de leurs données et, plus généralement, à l'utiliser et l'exploiter dans les mêmes conditions de sécurité. Ce contrat peut être reproduit et diffusé librement, sous réserve de le conserver en l'état, sans ajout ni suppression de clauses. +L'accessibilité au code source et les droits de copie, de modification +et de redistribution qui en découlent ont pour contrepartie de n'offrir +aux utilisateurs qu'une garantie limitée et de ne faire peser sur +l'auteur du logiciel, le titulaire des droits patrimoniaux et les +concédants successifs qu'une responsabilité restreinte. -Ce contrat est susceptible de s'appliquer à tout logiciel dont le titulaire des droits patrimoniaux décide de soumettre l'exploitation aux dispositions qu'il contient. +A cet égard l'attention de l'utilisateur est attirée sur les risques +associés au chargement, à l'utilisation, à la modification et/ou au +développement et à la reproduction du logiciel par l'utilisateur étant +donné sa spécificité de logiciel libre, qui peut le rendre complexe à +manipuler et qui le réserve donc à des développeurs ou des +professionnels avertis possédant des connaissances informatiques +approfondies. Les utilisateurs sont donc invités à charger et tester +l'adéquation du logiciel à leurs besoins dans des conditions permettant +d'assurer la sécurité de leurs systèmes et/ou de leurs données et, plus +généralement, à l'utiliser et l'exploiter dans les mêmes conditions de +sécurité. Ce contrat peut être reproduit et diffusé librement, sous +réserve de le conserver en l'état, sans ajout ni suppression de clauses. -Une liste de questions fréquemment posées se trouve sur le site web officiel de la famille des licences CeCILL (http://www.cecill.info/index.fr.html) pour toute clarification qui serait nécessaire. +Ce contrat est susceptible de s'appliquer à tout logiciel dont le +titulaire des droits patrimoniaux décide de soumettre l'exploitation aux +dispositions qu'il contient. -Article 1 - DEFINITIONS +Une liste de questions fréquemment posées se trouve sur le site web +officiel de la famille des licences CeCILL +(http://www.cecill.info/index.fr.html) pour toute clarification qui +serait nécessaire. -Dans ce contrat, les termes suivants, lorsqu'ils seront écrits avec une lettre capitale, auront la signification suivante: -Contrat: désigne le présent contrat de licence, ses éventuelles versions postérieures et annexes. + Article 1 - DEFINITIONS -Logiciel: désigne le logiciel sous sa forme de Code Objet et/ou de Code Source et le cas échéant sa documentation, dans leur état au moment de l'acceptation du Contrat par le Licencié. +Dans ce contrat, les termes suivants, lorsqu'ils seront écrits avec une +lettre capitale, auront la signification suivante: -Logiciel Initial: désigne le Logiciel sous sa forme de Code Source et éventuellement de Code Objet et le cas échéant sa documentation, dans leur état au moment de leur première diffusion sous les termes du Contrat. +Contrat: désigne le présent contrat de licence, ses éventuelles versions +postérieures et annexes. -Logiciel Modifié: désigne le Logiciel modifié par au moins une Contribution. +Logiciel: désigne le logiciel sous sa forme de Code Objet et/ou de Code +Source et le cas échéant sa documentation, dans leur état au moment de +l'acceptation du Contrat par le Licencié. -Code Source: désigne l'ensemble des instructions et des lignes de programme du Logiciel et auquel l'accès est nécessaire en vue de modifier le Logiciel. +Logiciel Initial: désigne le Logiciel sous sa forme de Code Source et +éventuellement de Code Objet et le cas échéant sa documentation, dans +leur état au moment de leur première diffusion sous les termes du Contrat. -Code Objet: désigne les fichiers binaires issus de la compilation du Code Source. +Logiciel Modifié: désigne le Logiciel modifié par au moins une +Contribution. -Titulaire: désigne le ou les détenteurs des droits patrimoniaux d'auteur sur le Logiciel Initial. +Code Source: désigne l'ensemble des instructions et des lignes de +programme du Logiciel et auquel l'accès est nécessaire en vue de +modifier le Logiciel. -Licencié: désigne le ou les utilisateurs du Logiciel ayant accepté le Contrat. +Code Objet: désigne les fichiers binaires issus de la compilation du +Code Source. + +Titulaire: désigne le ou les détenteurs des droits patrimoniaux d'auteur +sur le Logiciel Initial. + +Licencié: désigne le ou les utilisateurs du Logiciel ayant accepté le +Contrat. Contributeur: désigne le Licencié auteur d'au moins une Contribution. -Concédant: désigne le Titulaire ou toute personne physique ou morale distribuant le Logiciel sous le Contrat. +Concédant: désigne le Titulaire ou toute personne physique ou morale +distribuant le Logiciel sous le Contrat. -Contribution: désigne l'ensemble des modifications, corrections, traductions, adaptations et/ou nouvelles fonctionnalités intégrées dans le Logiciel par tout Contributeur, ainsi que tout Module Interne. +Contribution: désigne l'ensemble des modifications, corrections, +traductions, adaptations et/ou nouvelles fonctionnalités intégrées dans +le Logiciel par tout Contributeur, ainsi que tout Module Interne. -Module: désigne un ensemble de fichiers sources y compris leur documentation qui permet de réaliser des fonctionnalités ou services supplémentaires à ceux fournis par le Logiciel. +Module: désigne un ensemble de fichiers sources y compris leur +documentation qui permet de réaliser des fonctionnalités ou services +supplémentaires à ceux fournis par le Logiciel. -Module Externe: désigne tout Module, non dérivé du Logiciel, tel que ce Module et le Logiciel s'exécutent dans des espaces d'adressage différents, l'un appelant l'autre au moment de leur exécution. +Module Externe: désigne tout Module, non dérivé du Logiciel, tel que ce +Module et le Logiciel s'exécutent dans des espaces d'adressage +différents, l'un appelant l'autre au moment de leur exécution. -Module Interne: désigne tout Module lié au Logiciel de telle sorte qu'ils s'exécutent dans le même espace d'adressage. +Module Interne: désigne tout Module lié au Logiciel de telle sorte +qu'ils s'exécutent dans le même espace d'adressage. -GNU GPL: désigne la GNU General Public License dans sa version 2 ou toute version ultérieure, telle que publiée par Free Software Foundation Inc. +GNU GPL: désigne la GNU General Public License dans sa version 2 ou +toute version ultérieure, telle que publiée par Free Software Foundation +Inc. -GNU Affero GPL: désigne la GNU Affero General Public License dans sa version 3 ou toute version ultérieure, telle que publiée par Free Software Foundation Inc. +GNU Affero GPL: désigne la GNU Affero General Public License dans sa +version 3 ou toute version ultérieure, telle que publiée par Free +Software Foundation Inc. -EUPL: désigne la Licence Publique de l'Union européenne dans sa version 1.1 ou toute version ultérieure, telle que publiée par la Commission Européenne. +EUPL: désigne la Licence Publique de l'Union européenne dans sa version +1.1 ou toute version ultérieure, telle que publiée par la Commission +Européenne. Parties: désigne collectivement le Licencié et le Concédant. Ces termes s'entendent au singulier comme au pluriel. -Article 2 - OBJET -Le Contrat a pour objet la concession par le Concédant au Licencié d'une licence non exclusive, cessible et mondiale du Logiciel telle que définie ci-après à l'article 5 <#etendue> pour toute la durée de protection des droits portant sur ce Logiciel. + Article 2 - OBJET -Article 3 - ACCEPTATION +Le Contrat a pour objet la concession par le Concédant au Licencié d'une +licence non exclusive, cessible et mondiale du Logiciel telle que +définie ci-après à l'article 5 <#etendue> pour toute la durée de +protection des droits portant sur ce Logiciel. -3.1 L'acceptation par le Licencié des termes du Contrat est réputée acquise du fait du premier des faits suivants: -* (i) le chargement du Logiciel par tout moyen notamment par téléchargement à partir d'un serveur distant ou par chargement à partir d'un support physique; + Article 3 - ACCEPTATION -* (ii) le premier exercice par le Licencié de l'un quelconque des droits concédés par le Contrat. +3.1 L'acceptation par le Licencié des termes du Contrat est réputée +acquise du fait du premier des faits suivants: -3.2 Un exemplaire du Contrat, contenant notamment un avertissement relatif aux spécificités du Logiciel, à la restriction de garantie et à la limitation à un usage par des utilisateurs expérimentés a été mis à disposition du Licencié préalablement à son acceptation telle que définie à l'article 3.1 <#acceptation-acquise> ci dessus et le Licencié reconnaît en avoir pris connaissance. + * (i) le chargement du Logiciel par tout moyen notamment par + téléchargement à partir d'un serveur distant ou par chargement à + partir d'un support physique; + * (ii) le premier exercice par le Licencié de l'un quelconque des + droits concédés par le Contrat. -Article 4 - ENTREE EN VIGUEUR ET DUREE +3.2 Un exemplaire du Contrat, contenant notamment un avertissement +relatif aux spécificités du Logiciel, à la restriction de garantie et à +la limitation à un usage par des utilisateurs expérimentés a été mis à +disposition du Licencié préalablement à son acceptation telle que +définie à l'article 3.1 <#acceptation-acquise> ci dessus et le Licencié +reconnaît en avoir pris connaissance. -4.1 ENTREE EN VIGUEUR -Le Contrat entre en vigueur à la date de son acceptation par le Licencié telle que définie en 3.1 <#acceptation-acquise>. + Article 4 - ENTREE EN VIGUEUR ET DUREE -4.2 DUREE -Le Contrat produira ses effets pendant toute la durée légale de protection des droits patrimoniaux portant sur le Logiciel. + 4.1 ENTREE EN VIGUEUR -Article 5 - ETENDUE DES DROITS CONCEDES +Le Contrat entre en vigueur à la date de son acceptation par le Licencié +telle que définie en 3.1 <#acceptation-acquise>. -Le Concédant concède au Licencié, qui accepte, les droits suivants sur le Logiciel pour toutes destinations et pour la durée du Contrat dans les conditions ci-après détaillées. -Par ailleurs, si le Concédant détient ou venait à détenir un ou plusieurs brevets d'invention protégeant tout ou partie des fonctionnalités du Logiciel ou de ses composants, il s'engage à ne pas opposer les éventuels droits conférés par ces brevets aux Licenciés successifs qui utiliseraient, exploiteraient ou modifieraient le Logiciel. En cas de cession de ces brevets, le Concédant s'engage à faire reprendre les obligations du présent alinéa aux cessionnaires. + 4.2 DUREE -5.1 DROIT D'UTILISATION +Le Contrat produira ses effets pendant toute la durée légale de +protection des droits patrimoniaux portant sur le Logiciel. -Le Licencié est autorisé à utiliser le Logiciel, sans restriction quant aux domaines d'application, étant ci-après précisé que cela comporte: -1. la reproduction permanente ou provisoire du Logiciel en tout ou partie par tout moyen et sous toute forme. + Article 5 - ETENDUE DES DROITS CONCEDES -2. le chargement, l'affichage, l'exécution, ou le stockage du Logiciel sur tout support. +Le Concédant concède au Licencié, qui accepte, les droits suivants sur +le Logiciel pour toutes destinations et pour la durée du Contrat dans +les conditions ci-après détaillées. -3. la possibilité d'en observer, d'en étudier, ou d'en tester le fonctionnement afin de déterminer les idées et principes qui sont à la base de n'importe quel élément de ce Logiciel; et ceci, lorsque le Licencié effectue toute opération de chargement, d'affichage, d'exécution, de transmission ou de stockage du Logiciel qu'il est en droit d'effectuer en vertu du Contrat. +Par ailleurs, si le Concédant détient ou venait à détenir un ou +plusieurs brevets d'invention protégeant tout ou partie des +fonctionnalités du Logiciel ou de ses composants, il s'engage à ne pas +opposer les éventuels droits conférés par ces brevets aux Licenciés +successifs qui utiliseraient, exploiteraient ou modifieraient le +Logiciel. En cas de cession de ces brevets, le Concédant s'engage à +faire reprendre les obligations du présent alinéa aux cessionnaires. -5.2 DROIT D'APPORTER DES CONTRIBUTIONS -Le droit d'apporter des Contributions comporte le droit de traduire, d'adapter, d'arranger ou d'apporter toute autre modification au Logiciel et le droit de reproduire le logiciel en résultant. + 5.1 DROIT D'UTILISATION -Le Licencié est autorisé à apporter toute Contribution au Logiciel sous réserve de mentionner, de façon explicite, son nom en tant qu'auteur de cette Contribution et la date de création de celle-ci. +Le Licencié est autorisé à utiliser le Logiciel, sans restriction quant +aux domaines d'application, étant ci-après précisé que cela comporte: -5.3 DROIT DE DISTRIBUTION + 1. -Le droit de distribution comporte notamment le droit de diffuser, de transmettre et de communiquer le Logiciel au public sur tout support et par tout moyen ainsi que le droit de mettre sur le marché à titre onéreux ou gratuit, un ou des exemplaires du Logiciel par tout procédé. + la reproduction permanente ou provisoire du Logiciel en tout ou + partie par tout moyen et sous toute forme. -Le Licencié est autorisé à distribuer des copies du Logiciel, modifié ou non, à des tiers dans les conditions ci-après détaillées. + 2. -5.3.1 DISTRIBUTION DU LOGICIEL SANS MODIFICATION + le chargement, l'affichage, l'exécution, ou le stockage du Logiciel + sur tout support. -Le Licencié est autorisé à distribuer des copies conformes du Logiciel, sous forme de Code Source ou de Code Objet, à condition que cette distribution respecte les dispositions du Contrat dans leur totalité et soit accompagnée: + 3. -1. d'un exemplaire du Contrat, + la possibilité d'en observer, d'en étudier, ou d'en tester le + fonctionnement afin de déterminer les idées et principes qui sont à + la base de n'importe quel élément de ce Logiciel; et ceci, lorsque + le Licencié effectue toute opération de chargement, d'affichage, + d'exécution, de transmission ou de stockage du Logiciel qu'il est en + droit d'effectuer en vertu du Contrat. -2. d'un avertissement relatif à la restriction de garantie et de responsabilité du Concédant telle que prévue aux articles 8 <#responsabilite> et 9 <#garantie>, -et que, dans le cas où seul le Code Objet du Logiciel est redistribué, le Licencié permette un accès effectif au Code Source complet du Logiciel pour une durée d'au moins 3 ans à compter de la distribution du logiciel, étant entendu que le coût additionnel d'acquisition du Code Source ne devra pas excéder le simple coût de transfert des données. + 5.2 DROIT D'APPORTER DES CONTRIBUTIONS -5.3.2 DISTRIBUTION DU LOGICIEL MODIFIE +Le droit d'apporter des Contributions comporte le droit de traduire, +d'adapter, d'arranger ou d'apporter toute autre modification au Logiciel +et le droit de reproduire le logiciel en résultant. -Lorsque le Licencié apporte une Contribution au Logiciel, les conditions de distribution du Logiciel Modifié en résultant sont alors soumises à l'intégralité des dispositions du Contrat. +Le Licencié est autorisé à apporter toute Contribution au Logiciel sous +réserve de mentionner, de façon explicite, son nom en tant qu'auteur de +cette Contribution et la date de création de celle-ci. -Le Licencié est autorisé à distribuer le Logiciel Modifié, sous forme de code source ou de code objet, à condition que cette distribution respecte les dispositions du Contrat dans leur totalité et soit accompagnée: -1. d'un exemplaire du Contrat, + 5.3 DROIT DE DISTRIBUTION -2. d'un avertissement relatif à la restriction de garantie et de responsabilité du Concédant telle que prévue aux articles 8 <#responsabilite> et 9 <#garantie>, +Le droit de distribution comporte notamment le droit de diffuser, de +transmettre et de communiquer le Logiciel au public sur tout support et +par tout moyen ainsi que le droit de mettre sur le marché à titre +onéreux ou gratuit, un ou des exemplaires du Logiciel par tout procédé. + +Le Licencié est autorisé à distribuer des copies du Logiciel, modifié ou +non, à des tiers dans les conditions ci-après détaillées. + + + 5.3.1 DISTRIBUTION DU LOGICIEL SANS MODIFICATION + +Le Licencié est autorisé à distribuer des copies conformes du Logiciel, +sous forme de Code Source ou de Code Objet, à condition que cette +distribution respecte les dispositions du Contrat dans leur totalité et +soit accompagnée: + + 1. + + d'un exemplaire du Contrat, + + 2. + + d'un avertissement relatif à la restriction de garantie et de + responsabilité du Concédant telle que prévue aux articles 8 + <#responsabilite> et 9 <#garantie>, + +et que, dans le cas où seul le Code Objet du Logiciel est redistribué, +le Licencié permette un accès effectif au Code Source complet du +Logiciel pour une durée d'au moins 3 ans à compter de la distribution du +logiciel, étant entendu que le coût additionnel d'acquisition du Code +Source ne devra pas excéder le simple coût de transfert des données. + + + 5.3.2 DISTRIBUTION DU LOGICIEL MODIFIE + +Lorsque le Licencié apporte une Contribution au Logiciel, les conditions +de distribution du Logiciel Modifié en résultant sont alors soumises à +l'intégralité des dispositions du Contrat. + +Le Licencié est autorisé à distribuer le Logiciel Modifié, sous forme de +code source ou de code objet, à condition que cette distribution +respecte les dispositions du Contrat dans leur totalité et soit +accompagnée: + + 1. + + d'un exemplaire du Contrat, + + 2. + + d'un avertissement relatif à la restriction de garantie et de + responsabilité du Concédant telle que prévue aux articles 8 + <#responsabilite> et 9 <#garantie>, et, dans le cas où seul le code objet du Logiciel Modifié est redistribué, -3. d'une note précisant les conditions d'accès effectif au code source complet du Logiciel Modifié, pendant une période d'au moins 3 ans à compter de la distribution du Logiciel Modifié, étant entendu que le coût additionnel d'acquisition du code source ne devra pas excéder le simple coût de transfert des données. + 3. -5.3.3 DISTRIBUTION DES MODULES EXTERNES + d'une note précisant les conditions d'accès effectif au code source + complet du Logiciel Modifié, pendant une période d'au moins 3 ans à + compter de la distribution du Logiciel Modifié, étant entendu que le + coût additionnel d'acquisition du code source ne devra pas excéder + le simple coût de transfert des données. -Lorsque le Licencié a développé un Module Externe les conditions du Contrat ne s'appliquent pas à ce Module Externe, qui peut être distribué sous un contrat de licence différent. -5.3.4 COMPATIBILITE AVEC D'AUTRES LICENCES + 5.3.3 DISTRIBUTION DES MODULES EXTERNES -Le Licencié peut inclure un code soumis aux dispositions d'une des versions de la licence GNU GPL, GNU Affero GPL et/ou EUPL dans le Logiciel modifié ou non et distribuer l'ensemble sous les conditions de la même version de la licence GNU GPL, GNU Affero GPL et/ou EUPL. +Lorsque le Licencié a développé un Module Externe les conditions du +Contrat ne s'appliquent pas à ce Module Externe, qui peut être distribué +sous un contrat de licence différent. -Le Licencié peut inclure le Logiciel modifié ou non dans un code soumis aux dispositions d'une des versions de la licence GNU GPL, GNU Affero GPL et/ou EUPL et distribuer l'ensemble sous les conditions de la même version de la licence GNU GPL, GNU Affero GPL et/ou EUPL. -Article 6 - PROPRIETE INTELLECTUELLE + 5.3.4 COMPATIBILITE AVEC D'AUTRES LICENCES -6.1 SUR LE LOGICIEL INITIAL +Le Licencié peut inclure un code soumis aux dispositions d'une des +versions de la licence GNU GPL, GNU Affero GPL et/ou EUPL dans le +Logiciel modifié ou non et distribuer l'ensemble sous les conditions de +la même version de la licence GNU GPL, GNU Affero GPL et/ou EUPL. -Le Titulaire est détenteur des droits patrimoniaux sur le Logiciel Initial. Toute utilisation du Logiciel Initial est soumise au respect des conditions dans lesquelles le Titulaire a choisi de diffuser son oeuvre et nul autre n'a la faculté de modifier les conditions de diffusion de ce Logiciel Initial. +Le Licencié peut inclure le Logiciel modifié ou non dans un code soumis +aux dispositions d'une des versions de la licence GNU GPL, GNU Affero +GPL et/ou EUPL et distribuer l'ensemble sous les conditions de la même +version de la licence GNU GPL, GNU Affero GPL et/ou EUPL. -Le Titulaire s'engage à ce que le Logiciel Initial reste au moins régi par le Contrat et ce, pour la durée visée à l'article 4.2 <#duree>. -6.2 SUR LES CONTRIBUTIONS + Article 6 - PROPRIETE INTELLECTUELLE -Le Licencié qui a développé une Contribution est titulaire sur celle-ci des droits de propriété intellectuelle dans les conditions définies par la législation applicable. -6.3 SUR LES MODULES EXTERNES + 6.1 SUR LE LOGICIEL INITIAL -Le Licencié qui a développé un Module Externe est titulaire sur celui-ci des droits de propriété intellectuelle dans les conditions définies par la législation applicable et reste libre du choix du contrat régissant sa diffusion. +Le Titulaire est détenteur des droits patrimoniaux sur le Logiciel +Initial. Toute utilisation du Logiciel Initial est soumise au respect +des conditions dans lesquelles le Titulaire a choisi de diffuser son +oeuvre et nul autre n'a la faculté de modifier les conditions de +diffusion de ce Logiciel Initial. -6.4 DISPOSITIONS COMMUNES +Le Titulaire s'engage à ce que le Logiciel Initial reste au moins régi +par le Contrat et ce, pour la durée visée à l'article 4.2 <#duree>. + + + 6.2 SUR LES CONTRIBUTIONS + +Le Licencié qui a développé une Contribution est titulaire sur celle-ci +des droits de propriété intellectuelle dans les conditions définies par +la législation applicable. + + + 6.3 SUR LES MODULES EXTERNES + +Le Licencié qui a développé un Module Externe est titulaire sur celui-ci +des droits de propriété intellectuelle dans les conditions définies par +la législation applicable et reste libre du choix du contrat régissant +sa diffusion. + + + 6.4 DISPOSITIONS COMMUNES Le Licencié s'engage expressément: -1. à ne pas supprimer ou modifier de quelque manière que ce soit les mentions de propriété intellectuelle apposées sur le Logiciel; + 1. -2. à reproduire à l'identique lesdites mentions de propriété intellectuelle sur les copies du Logiciel modifié ou non. + à ne pas supprimer ou modifier de quelque manière que ce soit les + mentions de propriété intellectuelle apposées sur le Logiciel; -Le Licencié s'engage à ne pas porter atteinte, directement ou indirectement, aux droits de propriété intellectuelle du Titulaire et/ou des Contributeurs sur le Logiciel et à prendre, le cas échéant, à l'égard de son personnel toutes les mesures nécessaires pour assurer le respect des dits droits de propriété intellectuelle du Titulaire et/ou des Contributeurs. + 2. -Article 7 - SERVICES ASSOCIES + à reproduire à l'identique lesdites mentions de propriété + intellectuelle sur les copies du Logiciel modifié ou non. -7.1 Le Contrat n'oblige en aucun cas le Concédant à la réalisation de prestations d'assistance technique ou de maintenance du Logiciel. +Le Licencié s'engage à ne pas porter atteinte, directement ou +indirectement, aux droits de propriété intellectuelle du Titulaire et/ou +des Contributeurs sur le Logiciel et à prendre, le cas échéant, à +l'égard de son personnel toutes les mesures nécessaires pour assurer le +respect des dits droits de propriété intellectuelle du Titulaire et/ou +des Contributeurs. -Cependant le Concédant reste libre de proposer ce type de services. Les termes et conditions d'une telle assistance technique et/ou d'une telle maintenance seront alors déterminés dans un acte séparé. Ces actes de maintenance et/ou assistance technique n'engageront que la seule responsabilité du Concédant qui les propose. -7.2 De même, tout Concédant est libre de proposer, sous sa seule responsabilité, à ses licenciés une garantie, qui n'engagera que lui, lors de la redistribution du Logiciel et/ou du Logiciel Modifié et ce, dans les conditions qu'il souhaite. Cette garantie et les modalités financières de son application feront l'objet d'un acte séparé entre le Concédant et le Licencié. + Article 7 - SERVICES ASSOCIES -Article 8 - RESPONSABILITE +7.1 Le Contrat n'oblige en aucun cas le Concédant à la réalisation de +prestations d'assistance technique ou de maintenance du Logiciel. -8.1 Sous réserve des dispositions de l'article 8.2 <#limite-responsabilite>, le Licencié a la faculté, sous réserve de prouver la faute du Concédant concerné, de solliciter la réparation du préjudice direct qu'il subirait du fait du Logiciel et dont il apportera la preuve. +Cependant le Concédant reste libre de proposer ce type de services. Les +termes et conditions d'une telle assistance technique et/ou d'une telle +maintenance seront alors déterminés dans un acte séparé. Ces actes de +maintenance et/ou assistance technique n'engageront que la seule +responsabilité du Concédant qui les propose. -8.2 La responsabilité du Concédant est limitée aux engagements pris en application du Contrat et ne saurait être engagée en raison notamment: (i) des dommages dus à l'inexécution, totale ou partielle, de ses obligations par le Licencié, (ii) des dommages directs ou indirects découlant de l'utilisation ou des performances du Logiciel subis par le Licencié et (iii) plus généralement d'un quelconque dommage indirect. En particulier, les Parties conviennent expressément que tout préjudice financier ou commercial (par exemple perte de données, perte de bénéfices, perte d'exploitation, perte de clientèle ou de commandes, manque à gagner, trouble commercial quelconque) ou toute action dirigée contre le Licencié par un tiers, constitue un dommage indirect et n'ouvre pas droit à réparation par le Concédant. +7.2 De même, tout Concédant est libre de proposer, sous sa seule +responsabilité, à ses licenciés une garantie, qui n'engagera que lui, +lors de la redistribution du Logiciel et/ou du Logiciel Modifié et ce, +dans les conditions qu'il souhaite. Cette garantie et les modalités +financières de son application feront l'objet d'un acte séparé entre le +Concédant et le Licencié. -Article 9 - GARANTIE -9.1 Le Licencié reconnaît que l'état actuel des connaissances scientifiques et techniques au moment de la mise en circulation du Logiciel ne permet pas d'en tester et d'en vérifier toutes les utilisations ni de détecter l'existence d'éventuels défauts. L'attention du Licencié a été attirée sur ce point sur les risques associés au chargement, à l'utilisation, la modification et/ou au développement et à la reproduction du Logiciel qui sont réservés à des utilisateurs avertis. + Article 8 - RESPONSABILITE -Il relève de la responsabilité du Licencié de contrôler, par tous moyens, l'adéquation du produit à ses besoins, son bon fonctionnement et de s'assurer qu'il ne causera pas de dommages aux personnes et aux biens. +8.1 Sous réserve des dispositions de l'article 8.2 +<#limite-responsabilite>, le Licencié a la faculté, sous réserve de +prouver la faute du Concédant concerné, de solliciter la réparation du +préjudice direct qu'il subirait du fait du Logiciel et dont il apportera +la preuve. -9.2 Le Concédant déclare de bonne foi être en droit de concéder l'ensemble des droits attachés au Logiciel (comprenant notamment les droits visés à l'article 5 <#etendue>). +8.2 La responsabilité du Concédant est limitée aux engagements pris en +application du Contrat et ne saurait être engagée en raison notamment: +(i) des dommages dus à l'inexécution, totale ou partielle, de ses +obligations par le Licencié, (ii) des dommages directs ou indirects +découlant de l'utilisation ou des performances du Logiciel subis par le +Licencié et (iii) plus généralement d'un quelconque dommage indirect. En +particulier, les Parties conviennent expressément que tout préjudice +financier ou commercial (par exemple perte de données, perte de +bénéfices, perte d'exploitation, perte de clientèle ou de commandes, +manque à gagner, trouble commercial quelconque) ou toute action dirigée +contre le Licencié par un tiers, constitue un dommage indirect et +n'ouvre pas droit à réparation par le Concédant. -9.3 Le Licencié reconnaît que le Logiciel est fourni "en l'état" par le Concédant sans autre garantie, expresse ou tacite, que celle prévue à l'article 9.2 <#bonne-foi> et notamment sans aucune garantie sur sa valeur commerciale, son caractère sécurisé, innovant ou pertinent. -En particulier, le Concédant ne garantit pas que le Logiciel est exempt d'erreur, qu'il fonctionnera sans interruption, qu'il sera compatible avec l'équipement du Licencié et sa configuration logicielle ni qu'il remplira les besoins du Licencié. + Article 9 - GARANTIE -9.4 Le Concédant ne garantit pas, de manière expresse ou tacite, que le Logiciel ne porte pas atteinte à un quelconque droit de propriété intellectuelle d'un tiers portant sur un brevet, un logiciel ou sur tout autre droit de propriété. Ainsi, le Concédant exclut toute garantie au profit du Licencié contre les actions en contrefaçon qui pourraient être diligentées au titre de l'utilisation, de la modification, et de la redistribution du Logiciel. Néanmoins, si de telles actions sont exercées contre le Licencié, le Concédant lui apportera son expertise technique et juridique pour sa défense. Cette expertise technique et juridique est déterminée au cas par cas entre le Concédant concerné et le Licencié dans le cadre d'un protocole d'accord. Le Concédant dégage toute responsabilité quant à l'utilisation de la dénomination du Logiciel par le Licencié. Aucune garantie n'est apportée quant à l'existence de droits antérieurs sur le nom du Logiciel et sur l'existence d'une marque. +9.1 Le Licencié reconnaît que l'état actuel des connaissances +scientifiques et techniques au moment de la mise en circulation du +Logiciel ne permet pas d'en tester et d'en vérifier toutes les +utilisations ni de détecter l'existence d'éventuels défauts. L'attention +du Licencié a été attirée sur ce point sur les risques associés au +chargement, à l'utilisation, la modification et/ou au développement et à +la reproduction du Logiciel qui sont réservés à des utilisateurs avertis. -Article 10 - RESILIATION +Il relève de la responsabilité du Licencié de contrôler, par tous +moyens, l'adéquation du produit à ses besoins, son bon fonctionnement et +de s'assurer qu'il ne causera pas de dommages aux personnes et aux biens. -10.1 En cas de manquement par le Licencié aux obligations mises à sa charge par le Contrat, le Concédant pourra résilier de plein droit le Contrat trente (30) jours après notification adressée au Licencié et restée sans effet. +9.2 Le Concédant déclare de bonne foi être en droit de concéder +l'ensemble des droits attachés au Logiciel (comprenant notamment les +droits visés à l'article 5 <#etendue>). -10.2 Le Licencié dont le Contrat est résilié n'est plus autorisé à utiliser, modifier ou distribuer le Logiciel. Cependant, toutes les licences qu'il aura concédées antérieurement à la résiliation du Contrat resteront valides sous réserve qu'elles aient été effectuées en conformité avec le Contrat. +9.3 Le Licencié reconnaît que le Logiciel est fourni "en l'état" par le +Concédant sans autre garantie, expresse ou tacite, que celle prévue à +l'article 9.2 <#bonne-foi> et notamment sans aucune garantie sur sa +valeur commerciale, son caractère sécurisé, innovant ou pertinent. -Article 11 - DISPOSITIONS DIVERSES +En particulier, le Concédant ne garantit pas que le Logiciel est exempt +d'erreur, qu'il fonctionnera sans interruption, qu'il sera compatible +avec l'équipement du Licencié et sa configuration logicielle ni qu'il +remplira les besoins du Licencié. -11.1 CAUSE EXTERIEURE -Aucune des Parties ne sera responsable d'un retard ou d'une défaillance d'exécution du Contrat qui serait dû à un cas de force majeure, un cas fortuit ou une cause extérieure, telle que, notamment, le mauvais fonctionnement ou les interruptions du réseau électrique ou de télécommunication, la paralysie du réseau liée à une attaque informatique, l'intervention des autorités gouvernementales, les catastrophes naturelles, les dégâts des eaux, les tremblements de terre, le feu, les explosions, les grèves et les conflits sociaux, l'état de guerre... +9.4 Le Concédant ne garantit pas, de manière expresse ou tacite, que le +Logiciel ne porte pas atteinte à un quelconque droit de propriété +intellectuelle d'un tiers portant sur un brevet, un logiciel ou sur tout +autre droit de propriété. Ainsi, le Concédant exclut toute garantie au +profit du Licencié contre les actions en contrefaçon qui pourraient être +diligentées au titre de l'utilisation, de la modification, et de la +redistribution du Logiciel. Néanmoins, si de telles actions sont +exercées contre le Licencié, le Concédant lui apportera son expertise +technique et juridique pour sa défense. Cette expertise technique et +juridique est déterminée au cas par cas entre le Concédant concerné et +le Licencié dans le cadre d'un protocole d'accord. Le Concédant dégage +toute responsabilité quant à l'utilisation de la dénomination du +Logiciel par le Licencié. Aucune garantie n'est apportée quant à +l'existence de droits antérieurs sur le nom du Logiciel et sur +l'existence d'une marque. -11.2 Le fait, par l'une ou l'autre des Parties, d'omettre en une ou plusieurs occasions de se prévaloir d'une ou plusieurs dispositions du Contrat, ne pourra en aucun cas impliquer renonciation par la Partie intéressée à s'en prévaloir ultérieurement. -11.3 Le Contrat annule et remplace toute convention antérieure, écrite ou orale, entre les Parties sur le même objet et constitue l'accord entier entre les Parties sur cet objet. Aucune addition ou modification aux termes du Contrat n'aura d'effet à l'égard des Parties à moins d'être faite par écrit et signée par leurs représentants dûment habilités. + Article 10 - RESILIATION -11.4 Dans l'hypothèse où une ou plusieurs des dispositions du Contrat s'avèrerait contraire à une loi ou à un texte applicable, existants ou futurs, cette loi ou ce texte prévaudrait, et les Parties feraient les amendements nécessaires pour se conformer à cette loi ou à ce texte. Toutes les autres dispositions resteront en vigueur. De même, la nullité, pour quelque raison que ce soit, d'une des dispositions du Contrat ne saurait entraîner la nullité de l'ensemble du Contrat. +10.1 En cas de manquement par le Licencié aux obligations mises à sa +charge par le Contrat, le Concédant pourra résilier de plein droit le +Contrat trente (30) jours après notification adressée au Licencié et +restée sans effet. -11.5 LANGUE -Le Contrat est rédigé en langue française et en langue anglaise, ces deux versions faisant également foi. +10.2 Le Licencié dont le Contrat est résilié n'est plus autorisé à +utiliser, modifier ou distribuer le Logiciel. Cependant, toutes les +licences qu'il aura concédées antérieurement à la résiliation du Contrat +resteront valides sous réserve qu'elles aient été effectuées en +conformité avec le Contrat. -Article 12 - NOUVELLES VERSIONS DU CONTRAT -12.1 Toute personne est autorisée à copier et distribuer des copies de ce Contrat. + Article 11 - DISPOSITIONS DIVERSES -12.2 Afin d'en préserver la cohérence, le texte du Contrat est protégé et ne peut être modifié que par les auteurs de la licence, lesquels se réservent le droit de publier périodiquement des mises à jour ou de nouvelles versions du Contrat, qui posséderont chacune un numéro distinct. Ces versions ultérieures seront susceptibles de prendre en compte de nouvelles problématiques rencontrées par les logiciels libres. -12.3 Tout Logiciel diffusé sous une version donnée du Contrat ne pourra faire l'objet d'une diffusion ultérieure que sous la même version du Contrat ou une version postérieure, sous réserve des dispositions de l'article 5.3.4 <#compatibilite>. + 11.1 CAUSE EXTERIEURE -Article 13 - LOI APPLICABLE ET COMPETENCE TERRITORIALE +Aucune des Parties ne sera responsable d'un retard ou d'une défaillance +d'exécution du Contrat qui serait dû à un cas de force majeure, un cas +fortuit ou une cause extérieure, telle que, notamment, le mauvais +fonctionnement ou les interruptions du réseau électrique ou de +télécommunication, la paralysie du réseau liée à une attaque +informatique, l'intervention des autorités gouvernementales, les +catastrophes naturelles, les dégâts des eaux, les tremblements de terre, +le feu, les explosions, les grèves et les conflits sociaux, l'état de +guerre... -13.1 Le Contrat est régi par la loi française. Les Parties conviennent de tenter de régler à l'amiable les différends ou litiges qui viendraient à se produire par suite ou à l'occasion du Contrat. +11.2 Le fait, par l'une ou l'autre des Parties, d'omettre en une ou +plusieurs occasions de se prévaloir d'une ou plusieurs dispositions du +Contrat, ne pourra en aucun cas impliquer renonciation par la Partie +intéressée à s'en prévaloir ultérieurement. -13.2 A défaut d'accord amiable dans un délai de deux (2) mois à compter de leur survenance et sauf situation relevant d'une procédure d'urgence, les différends ou litiges seront portés par la Partie la plus diligente devant les Tribunaux compétents de Paris. +11.3 Le Contrat annule et remplace toute convention antérieure, écrite +ou orale, entre les Parties sur le même objet et constitue l'accord +entier entre les Parties sur cet objet. Aucune addition ou modification +aux termes du Contrat n'aura d'effet à l'égard des Parties à moins +d'être faite par écrit et signée par leurs représentants dûment habilités. + +11.4 Dans l'hypothèse où une ou plusieurs des dispositions du Contrat +s'avèrerait contraire à une loi ou à un texte applicable, existants ou +futurs, cette loi ou ce texte prévaudrait, et les Parties feraient les +amendements nécessaires pour se conformer à cette loi ou à ce texte. +Toutes les autres dispositions resteront en vigueur. De même, la +nullité, pour quelque raison que ce soit, d'une des dispositions du +Contrat ne saurait entraîner la nullité de l'ensemble du Contrat. + + + 11.5 LANGUE + +Le Contrat est rédigé en langue française et en langue anglaise, ces +deux versions faisant également foi. + + + Article 12 - NOUVELLES VERSIONS DU CONTRAT + +12.1 Toute personne est autorisée à copier et distribuer des copies de +ce Contrat. + +12.2 Afin d'en préserver la cohérence, le texte du Contrat est protégé +et ne peut être modifié que par les auteurs de la licence, lesquels se +réservent le droit de publier périodiquement des mises à jour ou de +nouvelles versions du Contrat, qui posséderont chacune un numéro +distinct. Ces versions ultérieures seront susceptibles de prendre en +compte de nouvelles problématiques rencontrées par les logiciels libres. + +12.3 Tout Logiciel diffusé sous une version donnée du Contrat ne pourra +faire l'objet d'une diffusion ultérieure que sous la même version du +Contrat ou une version postérieure, sous réserve des dispositions de +l'article 5.3.4 <#compatibilite>. + + + Article 13 - LOI APPLICABLE ET COMPETENCE TERRITORIALE + +13.1 Le Contrat est régi par la loi française. Les Parties conviennent +de tenter de régler à l'amiable les différends ou litiges qui +viendraient à se produire par suite ou à l'occasion du Contrat. + +13.2 A défaut d'accord amiable dans un délai de deux (2) mois à compter +de leur survenance et sauf situation relevant d'une procédure d'urgence, +les différends ou litiges seront portés par la Partie la plus diligente +devant les Tribunaux compétents de Paris. From d01065b09a3bbf9918f0b46f38e38a3d4aa7eb85 Mon Sep 17 00:00:00 2001 From: Ben Balter Date: Sun, 8 Oct 2017 18:34:03 -0700 Subject: [PATCH 05/70] change the regex...to require the field be surrounded by whitespace? The reason for the test was because some licenses had name and others had author, meaning in GitHub.com the inconsistency would cause the fields not to be interpolated. Copied from https://github.com/github/choosealicense.com/pull/527#discussion_r140502928 --- spec/license_fields_spec.rb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/spec/license_fields_spec.rb b/spec/license_fields_spec.rb index 4215f37..1c0d409 100644 --- a/spec/license_fields_spec.rb +++ b/spec/license_fields_spec.rb @@ -6,7 +6,7 @@ describe 'license fillable fields' do licenses.each do |license| context "The #{license['title']} license" do it 'should only contain supported fillable fields' do - matches = license['content'].scan(/\[([a-z]+)\]/) + matches = license['content'].scan(/\s+\[([a-z]+)\]\s+/) extra_fields = matches.flatten - (fields.map { |f| f['name'] }) expect(extra_fields).to be_empty end From 286357a54c87b3adaf7ae5c5314275626f31b977 Mon Sep 17 00:00:00 2001 From: Mike Linksvayer Date: Sun, 8 Oct 2017 20:31:34 -0700 Subject: [PATCH 06/70] loosen fields matching regex, check no supported fields missed --- spec/license_fields_spec.rb | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/spec/license_fields_spec.rb b/spec/license_fields_spec.rb index 1c0d409..b89b9e7 100644 --- a/spec/license_fields_spec.rb +++ b/spec/license_fields_spec.rb @@ -5,11 +5,16 @@ require 'spec_helper' describe 'license fillable fields' do licenses.each do |license| context "The #{license['title']} license" do + matches = license['content'].scan(/(\A|\W)\[([a-z]+)\]/).map {|row| row[1]} + extra_fields = matches.flatten - (fields.map { |f| f['name'] }) it 'should only contain supported fillable fields' do - matches = license['content'].scan(/\s+\[([a-z]+)\]\s+/) - extra_fields = matches.flatten - (fields.map { |f| f['name'] }) expect(extra_fields).to be_empty end + it 'does not overlook supported fillable fields' do + matches_generous = license['content'].scan(/\[([a-z]+)\]/) + extra_fields_generous = matches_generous.flatten - (fields.map { |f| f['name'] }) + expect(matches_generous.flatten - extra_fields_generous).to eq matches + end end end end From 5134e27c79f6b3179b52d66852777bd63f5e1f2e Mon Sep 17 00:00:00 2001 From: Mike Linksvayer Date: Sun, 8 Oct 2017 20:38:56 -0700 Subject: [PATCH 07/70] rubocop --- spec/license_fields_spec.rb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/spec/license_fields_spec.rb b/spec/license_fields_spec.rb index b89b9e7..f26f19e 100644 --- a/spec/license_fields_spec.rb +++ b/spec/license_fields_spec.rb @@ -5,7 +5,7 @@ require 'spec_helper' describe 'license fillable fields' do licenses.each do |license| context "The #{license['title']} license" do - matches = license['content'].scan(/(\A|\W)\[([a-z]+)\]/).map {|row| row[1]} + matches = license['content'].scan(/(\A|\W)\[([a-z]+)\]/).map { |row| row[1] } extra_fields = matches.flatten - (fields.map { |f| f['name'] }) it 'should only contain supported fillable fields' do expect(extra_fields).to be_empty From 247d7f22d840f426d2fbd45eb7d5de96c0686261 Mon Sep 17 00:00:00 2001 From: Mike Linksvayer Date: Mon, 25 Feb 2019 09:04:18 -0800 Subject: [PATCH 08/70] source field no longer used --- _licenses/cecill-2.1.txt | 1 - 1 file changed, 1 deletion(-) diff --git a/_licenses/cecill-2.1.txt b/_licenses/cecill-2.1.txt index 85d21ee..99d4f0a 100644 --- a/_licenses/cecill-2.1.txt +++ b/_licenses/cecill-2.1.txt @@ -1,7 +1,6 @@ --- title: CeCILL Free Software License Agreement v2.1 spdx-id: CECILL-2.1 -source: http://www.cecill.info/licences/Licence_CeCILL_V2.1-fr.txt description: French open-source license made by the CEA, INRIA and CNRS, compatible with the GNU GPL v2.0 and v3.0 From 4a3eb294b217eb5ca5e16e0350c6f776f08e1ad9 Mon Sep 17 00:00:00 2001 From: Mike Linksvayer Date: Mon, 17 Jun 2019 16:31:37 -0700 Subject: [PATCH 09/70] fr version of example to match cataloged license fr text --- _licenses/cecill-2.1.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_licenses/cecill-2.1.txt b/_licenses/cecill-2.1.txt index 99d4f0a..ea8d6cc 100644 --- a/_licenses/cecill-2.1.txt +++ b/_licenses/cecill-2.1.txt @@ -7,7 +7,7 @@ description: French open-source license made by the CEA, INRIA and CNRS, compati how: Create a text file (typically named LICENSE or LICENCE) in the root of your source code and copy the text of the license into the file. using: - - VITAM: https://github.com/ProgrammeVitam/vitam/blob/master_0.15.x/Licence_CeCILL_V2.1-en.txt + - VITAM: https://github.com/ProgrammeVitam/vitam/blob/master_0.15.x/Licence_CeCILL_V2.1-fr.txt - Test-Compta-Demat: https://github.com/DGFiP/Test-Compta-Demat/blob/master/src/testeur/Licence_CeCILL_V2.1-fr.txt - BMC-Tools: https://github.com/ANSSI-FR/bmc-tools/blob/master/LICENCE.txt From 4b67edf0db55bf31a06cfd35a19b462f9e5f4cdf Mon Sep 17 00:00:00 2001 From: Mike Linksvayer Date: Mon, 17 Jun 2019 18:35:00 -0700 Subject: [PATCH 10/70] relax github.com regex to allow for more branch names --- 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 09bf62c..f5d58c6 100644 --- a/spec/license_meta_spec.rb +++ b/spec/license_meta_spec.rb @@ -56,7 +56,7 @@ describe 'license meta' do let(:detected) { Licensee::ProjectFiles::LicenseFile.new(content, 'LICENSE').license } if example_url.start_with?('https://github.com/') - example_url.gsub!(%r{\Ahttps://github.com/([\w-]+/[\w\.-]+)/blob/([\w-]+/\S+)\z}, 'https://raw.githubusercontent.com/\1/\2') + 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/') example_url.gsub!(%r{/tree/}, '/plain/') elsif example_url.start_with?('https://bitbucket.org/') From 18ec54b71ee685a8c7b8b480faf8773ae1b7df15 Mon Sep 17 00:00:00 2001 From: Mike Linksvayer Date: Tue, 9 Jul 2019 10:15:56 -0500 Subject: [PATCH 11/70] add ids to sidebar for better linking --- _includes/sidebar.html | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/_includes/sidebar.html b/_includes/sidebar.html index 9e72e6e..9287f64 100644 --- a/_includes/sidebar.html +++ b/_includes/sidebar.html @@ -11,12 +11,12 @@
-

How to apply this license

+

How to apply this license

{{ page.how | markdownify | remove: '

' | remove: '

' }}

-

Optional steps

+

Optional steps

{% if page.note %}

{{ page.note | markdownify | remove: '

' | remove: '

' }} @@ -24,9 +24,9 @@ {% endif %} {% assign xgpl = false %} {% if page.spdx-id contains 'GPL' %}{% assign xgpl = true %}{% endif %} -

Add {{ page.spdx-id }}{% if xgpl %}-or-later{% endif %}{% if xgpl %} (or {{ page.spdx-id }}-only to disallow future versions){% 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-later{% endif %}{% if xgpl %} (or {{ page.spdx-id }}-only to disallow future versions){% 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.

+

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 231cc3167f7e20f03a32fe8dc37ee440cd6c97f5 Mon Sep 17 00:00:00 2001 From: Mike Linksvayer Date: Mon, 26 Aug 2019 11:27:05 -0700 Subject: [PATCH 12/70] swap out example provided at https://github.com/github/choosealicense.com/pull/527#issuecomment-524334219 --- _licenses/cecill-2.1.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_licenses/cecill-2.1.txt b/_licenses/cecill-2.1.txt index ea8d6cc..ce99814 100644 --- a/_licenses/cecill-2.1.txt +++ b/_licenses/cecill-2.1.txt @@ -8,7 +8,7 @@ how: Create a text file (typically named LICENSE or LICENCE) in the root of your using: - VITAM: https://github.com/ProgrammeVitam/vitam/blob/master_0.15.x/Licence_CeCILL_V2.1-fr.txt - - Test-Compta-Demat: https://github.com/DGFiP/Test-Compta-Demat/blob/master/src/testeur/Licence_CeCILL_V2.1-fr.txt + - Taxe foncière: https://github.com/etalab/taxe-fonciere/blob/master/LICENSE - BMC-Tools: https://github.com/ANSSI-FR/bmc-tools/blob/master/LICENCE.txt permissions: From bdd11363cc25d0bbd779a88401f5bd0cf6546382 Mon Sep 17 00:00:00 2001 From: Mike Linksvayer Date: Mon, 26 Aug 2019 12:24:35 -0700 Subject: [PATCH 13/70] rewrite description --- _licenses/cecill-2.1.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_licenses/cecill-2.1.txt b/_licenses/cecill-2.1.txt index ce99814..17eaf80 100644 --- a/_licenses/cecill-2.1.txt +++ b/_licenses/cecill-2.1.txt @@ -2,7 +2,7 @@ title: CeCILL Free Software License Agreement v2.1 spdx-id: CECILL-2.1 -description: French open-source license made by the CEA, INRIA and CNRS, compatible with the GNU GPL v2.0 and v3.0 +description: Strong copyleft license made by three French public research organisations, CEA, CNRS, and Inria, compatible with AGPL-3.0, EUPL-1.1, and GPL-2.0, or later versions of those licenses. how: Create a text file (typically named LICENSE or LICENCE) in the root of your source code and copy the text of the license into the file. From 83b6d75751e6d56e896733c077eadb971272b80d Mon Sep 17 00:00:00 2001 From: Mike Linksvayer Date: Mon, 26 Aug 2019 12:25:23 -0700 Subject: [PATCH 14/70] sort examples --- _licenses/cecill-2.1.txt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/_licenses/cecill-2.1.txt b/_licenses/cecill-2.1.txt index 17eaf80..3f9f308 100644 --- a/_licenses/cecill-2.1.txt +++ b/_licenses/cecill-2.1.txt @@ -7,9 +7,9 @@ description: Strong copyleft license made by three French public research organi how: Create a text file (typically named LICENSE or LICENCE) in the root of your source code and copy the text of the license into the file. using: - - VITAM: https://github.com/ProgrammeVitam/vitam/blob/master_0.15.x/Licence_CeCILL_V2.1-fr.txt - - Taxe foncière: https://github.com/etalab/taxe-fonciere/blob/master/LICENSE - BMC-Tools: https://github.com/ANSSI-FR/bmc-tools/blob/master/LICENCE.txt + - Taxe foncière: https://github.com/etalab/taxe-fonciere/blob/master/LICENSE + - VITAM: https://github.com/ProgrammeVitam/vitam/blob/master_0.15.x/Licence_CeCILL_V2.1-fr.txt permissions: - commercial-use From 67a6eb306652b3a5d96bda983121befc13e6086f Mon Sep 17 00:00:00 2001 From: Jake Jarvis Date: Mon, 26 Aug 2019 16:43:35 -0400 Subject: [PATCH 15/70] Some wordiness reduction and grammar fixes --- about.md | 10 +++++----- appendix.md | 6 +++--- community.md | 8 ++++---- index.html | 4 ++-- licenses.html | 4 ++-- no-permission.md | 4 ++-- non-software.md | 6 +++--- 7 files changed, 21 insertions(+), 21 deletions(-) diff --git a/about.md b/about.md index deea9d3..f175b91 100644 --- a/about.md +++ b/about.md @@ -6,13 +6,13 @@ title: "What's this about?" GitHub wants to help developers choose an open source license for their source code. -If you already know what you're doing and have a license you prefer to use, that's great! We're not here to change your mind. But if you are bewildered by the large number of open source license choices, maybe we can help. +If you already know what you're doing and have a license you prefer to use, that's great! We're not here to change your mind. But if you are bewildered by the large number of choices, maybe we can help. ## Not comprehensive -This site is not a comprehensive directory of open source licenses. On the [homepage](/), we break it down into just two licenses. The vast majority of projects will likely be fine choosing from one of these two. Just in case you have specific needs not covered by those two, we also highlight a [few other licenses to consider](/licenses/), and have a page about [licenses for non-software projects](/non-software/). +This site is not a comprehensive directory of open source licenses. On the [homepage](/), we break it down into just two licenses — the [MIT License](https://choosealicense.com/licenses/mit/) and the [GNU GPLv3](https://choosealicense.com/licenses/gpl-3.0/). The vast majority of projects will likely be perfectly safe choosing from one of these two. Just in case you have specific needs not covered by these, we also highlight a [few other licenses to consider](/licenses/) and have a page about [licenses for non-software projects](/non-software/). -See our [appendix](/appendix/) for a table of all of the licenses cataloged in the choosealicense.com repository and the links below for *even more licenses* that you **do not** need to learn about when choosing a license for your project. +See our [appendix](/appendix/) for a table of every license cataloged in the [choosealicense.com repository](https://github.com/github/choosealicense.com) and the links below for *even more* licenses that you **do not** need to learn about to still choose a great license for your project. ### Additional resources @@ -25,8 +25,8 @@ See our [appendix](/appendix/) for a table of all of the licenses cataloged in t ## Help us improve it -Choosealicense.com isn't just about open source, the site itself is open source as well. See something you think could be done better? Feel free to [fork the project](https://github.com/github/choosealicense.com) on GitHub and submit a pull request. We'd welcome your improvements. +Choosealicense.com isn't just about open source; the site itself is open source as well. See something you think could be done better? Feel free to [fork the project](https://github.com/github/choosealicense.com) on GitHub and submit a pull request. We welcome your improvements. ## Disclaimer -We are not lawyers. Well, most of us anyway. It is not the goal of this site to provide legal advice. The goal of this site is to provide a starting point to help you make an informed choice by providing information on popular open source licenses. If you have any questions regarding the right license for your code or any other legal issues relating to it, it's up to you to do further research or consult with a professional. +We are not lawyers. Well, most of us anyway. It is not the goal of this site to provide legal advice. The goal of this site is to provide a starting point to help you make an informed choice by providing information on popular open source licenses in a simplified fashion. If you have any questions regarding the best license for your code or any other legal issues relating to it, it's your responsibility to do further research or consult with a professional. diff --git a/appendix.md b/appendix.md index 09c6e45..ce16bca 100644 --- a/appendix.md +++ b/appendix.md @@ -5,7 +5,7 @@ title: Appendix class: license-types --- -For reference, all licenses described in the choosealicense.com [repository](https://github.com/github/choosealicense.com), in a table. +For reference, here is a neat 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. @@ -61,11 +61,11 @@ If you're here to choose a license, **[start from the home page](/)** to see a f ## Legend -

Open source licenses grant to the public permissions to do things with licensed works copyright or other "intellectual property" laws might otherwise disallow.

+

Open source licenses grant to the public permissions to do things with licensed works which copyright or other "intellectual property" laws might otherwise disallow.

Most open source licenses' grants of permissions are subject to compliance with conditions.

-

Most open source licenses also have limitations that usually disclaim warranty and liability and sometimes expressly exclude patent or trademark from licenses' grants.

+

Most open source licenses also have limitations that usually disclaim warranty and liability, and sometimes expressly exclude patents or trademarks from licenses' grants.

{% assign seen_tags = '' %} diff --git a/community.md b/community.md index c1dbe82..2f027ee 100644 --- a/community.md +++ b/community.md @@ -5,11 +5,11 @@ redirect_from: /existing/ title: Existing projects and communities --- -If you're contributing to or extending an existing project, it's almost always easiest to continue using that project's license. Look for a file called `LICENSE` or `COPYING`, or a notice in the project's `README` to find out what that license is. If you can't find a license, [ask](/no-permission/#for-users). +If you're contributing to or extending an existing project, it's almost always easiest to continue using that project's license. To find its license, look for a file called `LICENSE` or `COPYING`, or skim the project's `README`. If you can't find a license, [ask the maintainers](/no-permission/#for-users). -Depending on how you're building on an existing project and what its license is, using the existing project's license for your own might not just be the easiest thing to do, but a condition on which your permission to build on the existing project rests: see the "same license" condition of [some licenses](/licenses/). +Depending on the original project's license, using the same license might be a requirement, not just the easiest thing to do. (See the "same license" condition of [some licenses](/licenses/).) -Some communities have strong preferences for particular licenses. If you want to participate in one of these, it will be easier to use the preferred license even if you're starting a brand new project with no existing dependencies. Examples: +Some communities have strong preferences for particular licenses. If you want to participate in one of these, it will be easier to use their preferred license, even if you're starting a brand new project with no existing dependencies. Some examples include: {: .bullets} @@ -21,4 +21,4 @@ Some communities have strong preferences for particular licenses. If you want to * [Rust](https://rust-lang-nursery.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) -Communities come in all shapes and sizes, and more than one might be pertinent (e.g., [your company](https://opensource.guide/legal/#what-does-my-companys-legal-team-need-to-know)). The examples above are *very* well established. If the community you see your project as a part of doesn't have set-in-stone licensing traditions, or you don't see your project as part of any particular community, that's just fine: [make your own choice of an open source license](/). +Communities come in all shapes and sizes, and using more than one license might be pertinent (e.g., [your company](https://opensource.guide/legal/#what-does-my-companys-legal-team-need-to-know)). 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](/). diff --git a/index.html b/index.html index f3d2477..b8d343a 100644 --- a/index.html +++ b/index.html @@ -32,7 +32,7 @@ permalink: /

I want it simple and permissive.

- The MIT License is short and to the point. It lets people do almost anything they want with your project, including to make and distribute closed source versions. + The MIT License is short and to the point. It lets people do almost anything they want with your project, like making and distributing closed source versions.

{% include using-sentence.html license-id="mit" %} @@ -44,7 +44,7 @@ permalink: /

I care about sharing improvements.

- The GNU GPLv3 also lets people do almost anything they want with your project, except to distribute closed source versions. + The GNU GPLv3 also lets people do almost anything they want with your project, except distributing closed source versions.

{% include using-sentence.html license-id="gpl-3.0" %} diff --git a/licenses.html b/licenses.html index 4a2bf68..85cce09 100644 --- a/licenses.html +++ b/licenses.html @@ -5,8 +5,8 @@ class: license-types title: Licenses --- -

Open source licenses grant permission to everyone to use, modify, and share licensed software for any purpose, subject to conditions preserving the provenance and openness of the software. The following licenses are arranged from one with the strongest of these conditions (GNU AGPLv3) to one with no conditions (Unlicense). Notice that the popular licenses featured on the home page (GNU GPLv3 and MIT) fall within this spectrum.

-

If you were looking for a reference table of all of the licenses on choosealicense.com, see the appendix.

+

Open source licenses grant permission for anybody to use, modify, and share licensed software for any purpose, subject to conditions preserving the provenance and openness of the software. The following licenses are sorted by the degree of limitations and conditions, from most (GNU AGPLv3) to none (Unlicense). Notice that the popular licenses featured on the home page (GNU GPLv3 and MIT) fall within this spectrum.

+

If you're looking for a reference table of every license on choosealicense.com, see the appendix.

{% include license-overview.html license-id="agpl-3.0" %} {% include license-overview.html license-id="gpl-3.0" %} diff --git a/no-permission.md b/no-permission.md index f4a1c23..b17682b 100644 --- a/no-permission.md +++ b/no-permission.md @@ -12,9 +12,9 @@ When you make a creative work (which includes code), the work is under exclusive Even in the absence of a license file, you may grant some rights in cases where you publish your source code to a site that requires accepting terms of service. For example, if you publish your source code in a public repository on GitHub, you have accepted the [Terms of Service](https://help.github.com/articles/github-terms-of-service), by which you allow others to view and fork your repository. Others may not need your permission if [limitations and exceptions to copyright](https://en.wikipedia.org/wiki/Limitations_and_exceptions_to_copyright) apply to their particular situation. Neither site terms nor jurisdiction-specific copyright limitations are sufficient for the kinds of collaboration that people usually seek on a public code host, such as experimentation, modification, and sharing as fostered by an open source license. -You don't have to do anything to not offer a license. You may however wish to add a copyright notice and statement that you are not offering any license in a prominent place (e.g., your project's README) so that [users](#for-users) don't assume you made an oversight. If you're going to accept others' contributions to your non-licensed project, you may wish to explore with your lawyer adding a contributor agreement to your project so that you maintain copyright permission from contributors, even though you're not granting the same. +You don't have to do anything to *not* offer a license. You may, however, wish to add a copyright notice and statement that you are not offering any license in a prominent place (e.g., your project's README) so that [users](#for-users) don't assume you made an oversight. If you're going to accept others' contributions to your non-licensed project, you may wish to explore adding a contributor agreement to your project with your lawyer so that you maintain copyright permission from contributors, even though you're not granting the same. -Disallowing use of your code might not be what you intend by "no license." An [open-source license](/) allows reuse of your code while retaining copyright. If your goal is to completely opt-out of copyright restrictions, try a [public domain dedication](/licenses/#unlicense). +Disallowing use of your code might not be what you intend by "no license." An [open source license](/) allows reuse of your code while retaining copyright. If your goal is to completely opt-out of copyright restrictions, try a [public domain dedication](/licenses/#unlicense) instead. ## For users diff --git a/non-software.md b/non-software.md index ac245df..3c312b8 100644 --- a/non-software.md +++ b/non-software.md @@ -4,7 +4,7 @@ layout: default permalink: /non-software/ --- -Open source software licenses can be used for non-software works, and often are the best choice. This is particularly the case 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](/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 (e.g., [open source hardware](https://www.oshwa.org/definition/) designs). [Choose an open source license here.](/licenses/) ### Data, media, etc. @@ -12,7 +12,7 @@ Open source software licenses can be used for non-software works, and often are ### Documentation -Any open source software license or open license for media (see [above](#data-media-etc)) is applicable to software documentation. If you use different licenses for your software and its documentation, you may wish to take care that source code examples in the documentation are also licensed under the software license. +Any open source software license or open license for media (see [above](#data-media-etc)) also applies to software documentation. If you use different licenses for your software and its documentation, be sure to specify that source code examples in the documentation are also licensed under the software license. ### Fonts @@ -20,4 +20,4 @@ The [SIL Open Font License 1.1](/licenses/ofl-1.1/) keeps fonts open but allows ### 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 what parts 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 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 47dc4ab7376cde27102d4e8b8f19364a807418ad Mon Sep 17 00:00:00 2001 From: Mike Linksvayer Date: Mon, 26 Aug 2019 16:04:07 -0700 Subject: [PATCH 16/70] edit edits --- about.md | 2 +- appendix.md | 2 +- community.md | 4 ++-- licenses.html | 2 +- 4 files changed, 5 insertions(+), 5 deletions(-) diff --git a/about.md b/about.md index f175b91..169caff 100644 --- a/about.md +++ b/about.md @@ -10,7 +10,7 @@ If you already know what you're doing and have a license you prefer to use, that ## Not comprehensive -This site is not a comprehensive directory of open source licenses. On the [homepage](/), we break it down into just two licenses — the [MIT License](https://choosealicense.com/licenses/mit/) and the [GNU GPLv3](https://choosealicense.com/licenses/gpl-3.0/). The vast majority of projects will likely be perfectly safe choosing from one of these two. Just in case you have specific needs not covered by these, we also highlight a [few other licenses to consider](/licenses/) and have a page about [licenses for non-software projects](/non-software/). +This site is not a comprehensive directory of open source licenses. The vast majority of projects will likely be well served by one of the three options highlighted on the [homepage](/) — choosing the license [preferred](/community/) by projects similar to yours, or the most popular permissive license ([MIT](/licenses/mit/)), or the most popular copyleft license ([GNU GPLv3](/licenses/gpl-3.0/)). Just in case you have specific needs not covered by these, we also highlight a [few other licenses to consider](/licenses/) and have a page about [licenses for non-software projects](/non-software/). See our [appendix](/appendix/) for a table of every license cataloged in the [choosealicense.com repository](https://github.com/github/choosealicense.com) and the links below for *even more* licenses that you **do not** need to learn about to still choose a great license for your project. diff --git a/appendix.md b/appendix.md index ce16bca..02232ac 100644 --- a/appendix.md +++ b/appendix.md @@ -5,7 +5,7 @@ title: Appendix class: license-types --- -For reference, here is a neat 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. diff --git a/community.md b/community.md index 2f027ee..ee065ee 100644 --- a/community.md +++ b/community.md @@ -5,7 +5,7 @@ redirect_from: /existing/ title: Existing projects and communities --- -If you're contributing to or extending an existing project, it's almost always easiest to continue using that project's license. To find its license, look for a file called `LICENSE` or `COPYING`, or skim the project's `README`. If you can't find a license, [ask the maintainers](/no-permission/#for-users). +If you're contributing to or extending an existing project, it's almost always easiest to continue using that project's license. To find its license, look for a file called `LICENSE` or `COPYING`, and skim the project's `README`. If you can't find a license, [ask the maintainers](/no-permission/#for-users). Depending on the original project's license, using the same license might be a requirement, not just the easiest thing to do. (See the "same license" condition of [some licenses](/licenses/).) @@ -21,4 +21,4 @@ Some communities have strong preferences for particular licenses. If you want to * [Rust](https://rust-lang-nursery.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) -Communities come in all shapes and sizes, and using more than one license might be pertinent (e.g., [your company](https://opensource.guide/legal/#what-does-my-companys-legal-team-need-to-know)). 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](/). +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](/). diff --git a/licenses.html b/licenses.html index 85cce09..c0172d4 100644 --- a/licenses.html +++ b/licenses.html @@ -5,7 +5,7 @@ class: license-types title: Licenses --- -

Open source licenses grant permission for anybody to use, modify, and share licensed software for any purpose, subject to conditions preserving the provenance and openness of the software. The following licenses are sorted by the degree of limitations and conditions, from most (GNU AGPLv3) to none (Unlicense). Notice that the popular licenses featured on the home page (GNU GPLv3 and MIT) fall within this spectrum.

+

Open source licenses grant permission for anybody to use, modify, and share licensed software for any purpose, subject to conditions preserving the provenance and openness of the software. The following licenses are sorted by the number of conditions, from most (GNU AGPLv3) to none (Unlicense). Notice that the popular licenses featured on the home page (GNU GPLv3 and MIT) fall within this spectrum.

If you're looking for a reference table of every license on choosealicense.com, see the appendix.

{% include license-overview.html license-id="agpl-3.0" %} From 47a7d95c20327e44b33c2345bce08e22077fb92d Mon Sep 17 00:00:00 2001 From: Anne van Kesteren Date: Wed, 25 Sep 2019 15:36:34 +0200 Subject: [PATCH 17/70] HTTPS is great --- _licenses/unlicense.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_licenses/unlicense.txt b/_licenses/unlicense.txt index e6a8ae9..c42a257 100644 --- a/_licenses/unlicense.txt +++ b/_licenses/unlicense.txt @@ -49,4 +49,4 @@ OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. -For more information, please refer to +For more information, please refer to From ab4c8ba38459919eb83f71b055c79d58efde23ff Mon Sep 17 00:00:00 2001 From: Mike Linksvayer Date: Fri, 25 Oct 2019 11:43:26 -0700 Subject: [PATCH 18/70] Add nickname for BSD-3-Clause-Clear Used in https://github.com/licensee/licensee/pull/391 --- _licenses/bsd-3-clause-clear.txt | 1 + 1 file changed, 1 insertion(+) diff --git a/_licenses/bsd-3-clause-clear.txt b/_licenses/bsd-3-clause-clear.txt index 7fe46ae..40fe718 100644 --- a/_licenses/bsd-3-clause-clear.txt +++ b/_licenses/bsd-3-clause-clear.txt @@ -1,6 +1,7 @@ --- title: BSD 3-Clause Clear License spdx-id: BSD-3-Clause-Clear +nickname: Clear BSD description: A variant of the BSD 3-Clause License that explicitly does not grant any patent rights. From cdc2aa243710fdfbb89abbeceea6fcedf2e796a8 Mon Sep 17 00:00:00 2001 From: Mike Linksvayer Date: Mon, 18 Nov 2019 09:56:42 -0800 Subject: [PATCH 19/70] Update Rust community license guidelines link --- community.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/community.md b/community.md index ee065ee..b653323 100644 --- a/community.md +++ b/community.md @@ -18,7 +18,7 @@ Some communities have strong preferences for particular licenses. If you want to * [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/) -* [Rust](https://rust-lang-nursery.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/) +* [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) 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 4e62d749b06e867669fe9c9b240487cfce0f2577 Mon Sep 17 00:00:00 2001 From: Mike Linksvayer Date: Mon, 18 Nov 2019 10:21:22 -0800 Subject: [PATCH 20/70] Add include-copyright--source condition to more precisely describe bsl-1.0 and zlib --- README.md | 1 + _data/rules.yml | 3 +++ _licenses/bsl-1.0.txt | 2 +- _licenses/zlib.txt | 2 +- 4 files changed, 6 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 7b6b860..473e9b9 100644 --- a/README.md +++ b/README.md @@ -81,6 +81,7 @@ The license properties (rules) are stored as a bulleted list within the licenses #### Conditions * `include-copyright` - A copy of the license and copyright notice must be included with the software. +* `include-copyright--source` - A copy of the license and copyright notice must be included with the software in source form, but is not required for binaries. * `document-changes` - Changes made to the code must be documented. * `disclose-source` - Source code must be made available when the software is distributed. * `network-use-disclose` - Users who interact with the software via network are given the right to receive a copy of the source code. diff --git a/_data/rules.yml b/_data/rules.yml index 3a20f10..1f315b6 100644 --- a/_data/rules.yml +++ b/_data/rules.yml @@ -19,6 +19,9 @@ conditions: - description: A copy of the license and copyright notice must be included with the software. label: License and copyright notice tag: include-copyright +- description: A copy of the license and copyright notice must be included with the software in source form, but is not required for binaries. + label: License and copyright notice for source + tag: include-copyright--source - description: Changes made to the code must be documented. label: State changes tag: document-changes diff --git a/_licenses/bsl-1.0.txt b/_licenses/bsl-1.0.txt index e595a5c..ae37c9a 100644 --- a/_licenses/bsl-1.0.txt +++ b/_licenses/bsl-1.0.txt @@ -17,7 +17,7 @@ permissions: - private-use conditions: - - include-copyright + - include-copyright--source limitations: - liability diff --git a/_licenses/zlib.txt b/_licenses/zlib.txt index 0be8fd0..9ed25ed 100644 --- a/_licenses/zlib.txt +++ b/_licenses/zlib.txt @@ -15,7 +15,7 @@ permissions: - private-use conditions: - - include-copyright + - include-copyright--source - document-changes limitations: From 08ec1de7249a14cad57df0a7b268576e2c98434b Mon Sep 17 00:00:00 2001 From: Mike Linksvayer Date: Mon, 18 Nov 2019 10:32:39 -0800 Subject: [PATCH 21/70] Add BSL-1.0 and Zlib examples --- _licenses/bsl-1.0.txt | 3 +++ _licenses/zlib.txt | 3 +++ spec/license_meta_spec.rb | 4 +--- 3 files changed, 7 insertions(+), 3 deletions(-) diff --git a/_licenses/bsl-1.0.txt b/_licenses/bsl-1.0.txt index ae37c9a..8da7d01 100644 --- a/_licenses/bsl-1.0.txt +++ b/_licenses/bsl-1.0.txt @@ -9,6 +9,9 @@ how: Create a text file (typically named LICENSE or LICENSE.txt) in the root of 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). using: + - Boost: https://github.com/boostorg/boost/blob/master/LICENSE_1_0.txt + - Catch2: https://github.com/catchorg/Catch2/blob/master/LICENSE.txt + - DMD: https://github.com/dlang/dmd/blob/master/LICENSE.txt permissions: - commercial-use diff --git a/_licenses/zlib.txt b/_licenses/zlib.txt index 9ed25ed..706b1b5 100644 --- a/_licenses/zlib.txt +++ b/_licenses/zlib.txt @@ -7,6 +7,9 @@ description: A short permissive license, compatible with GPL. Requires altered s 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. Replace [year] with the current year and [fullname] with the name (or names) of the copyright holders. using: + - GLFW: https://github.com/glfw/glfw/blob/master/LICENSE.md + - Portainer: https://github.com/portainer/portainer/blob/develop/LICENSE + - TinyXML-2: https://github.com/leethomason/tinyxml2/blob/master/LICENSE.txt permissions: - commercial-use diff --git a/spec/license_meta_spec.rb b/spec/license_meta_spec.rb index f5d58c6..02b7c8d 100644 --- a/spec/license_meta_spec.rb +++ b/spec/license_meta_spec.rb @@ -27,7 +27,6 @@ describe 'license meta' do 'agpl-3.0', 'artistic-2.0', 'bsd-3-clause-clear', - 'bsl-1.0', 'cc0-1.0', 'cc-by-4.0', 'cc-by-sa-4.0', @@ -38,8 +37,7 @@ describe 'license meta' do 'ms-pl', 'ms-rl', 'ofl-1.1', - 'wtfpl', - 'zlib' + 'wtfpl' ] skip 'added before 3 using examples required' if legacy.include?(license['slug']) expect(examples.length).to eq(3) From 3aec2700426bc0427e097e9d37441643d5a02654 Mon Sep 17 00:00:00 2001 From: Waldir Pimenta Date: Tue, 19 Nov 2019 22:42:14 +0000 Subject: [PATCH 22/70] Add examples for Creative Commons licenses and OFL Also adjust instructions in README.md to match CONTRIBUTING.md --- README.md | 4 ++-- _licenses/cc-by-4.0.txt | 3 +++ _licenses/cc-by-sa-4.0.txt | 3 +++ _licenses/cc0-1.0.txt | 3 +++ _licenses/ofl-1.1.txt | 3 +++ spec/license_meta_spec.rb | 4 ---- 6 files changed, 14 insertions(+), 6 deletions(-) diff --git a/README.md b/README.md index 7b6b860..fe6c089 100644 --- a/README.md +++ b/README.md @@ -17,8 +17,8 @@ We catalog [select](CONTRIBUTING.md#adding-a-license) open source licenses with ```bash git clone https://github.com/github/choosealicense.com.git cd choosealicense.com -script/bootstrap -script/server +./script/bootstrap +./script/server ``` Open `http://localhost:4000` in your favorite browser. diff --git a/_licenses/cc-by-4.0.txt b/_licenses/cc-by-4.0.txt index 52233ed..d9a4a36 100644 --- a/_licenses/cc-by-4.0.txt +++ b/_licenses/cc-by-4.0.txt @@ -7,6 +7,9 @@ description: Permits almost any use subject to providing credit and license noti 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. It is also acceptable to solely supply a link to a copy of the license, usually to the canonical URL for the license. using: + - caniuse: https://github.com/Fyrd/caniuse/blob/master/LICENSE + - WHATWG HTML standard: https://github.com/whatwg/html/blob/master/LICENSE + - Kubernetes documentation: https://github.com/kubernetes/website/blob/master/LICENSE permissions: - commercial-use diff --git a/_licenses/cc-by-sa-4.0.txt b/_licenses/cc-by-sa-4.0.txt index 21afff8..8e48b1b 100644 --- a/_licenses/cc-by-sa-4.0.txt +++ b/_licenses/cc-by-sa-4.0.txt @@ -7,6 +7,9 @@ description: Similar to CC-BY-4.0 but require 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. It is also acceptable to solely supply a link to a copy of the license, usually to the canonical URL for the license. using: + - Flight rules for Git: https://github.com/k88hudson/git-flight-rules/blob/master/LICENSE + - GitHub-Dark: https://github.com/StylishThemes/GitHub-Dark/blob/master/LICENSE + - Material Design Iconic Font: https://github.com/zavoloklom/material-design-iconic-font/blob/master/License.md permissions: - commercial-use diff --git a/_licenses/cc0-1.0.txt b/_licenses/cc0-1.0.txt index 81b345d..55375b4 100644 --- a/_licenses/cc0-1.0.txt +++ b/_licenses/cc0-1.0.txt @@ -10,6 +10,9 @@ how: Create a text file (typically named LICENSE or LICENSE.txt) in the root of note: Creative Commons recommends taking the additional step of adding a boilerplate notice to the top of each file. The boilerplate can be found on their website. using: + - Awesome: https://github.com/sindresorhus/awesome/blob/master/license + - Shields.io: https://github.com/badges/shields/blob/master/LICENSE + - psdash: https://github.com/Jahaja/psdash/blob/master/LICENSE permissions: - commercial-use diff --git a/_licenses/ofl-1.1.txt b/_licenses/ofl-1.1.txt index 066a30f..192aab3 100644 --- a/_licenses/ofl-1.1.txt +++ b/_licenses/ofl-1.1.txt @@ -10,6 +10,9 @@ how: Create a text file (typically named LICENSE or LICENSE.txt) in the root of note: This license doesn't require source provision, but recommends it. All files derived from OFL files must remain licensed under the OFL. using: + - FiraCode: https://github.com/tonsky/FiraCode/blob/master/LICENSE + - Noto fonts: https://github.com/googlefonts/noto-fonts/blob/master/LICENSE + - Fantasque Sans Mono: https://github.com/belluzj/fantasque-sans/blob/master/LICENSE.txt permissions: - private-use diff --git a/spec/license_meta_spec.rb b/spec/license_meta_spec.rb index f5d58c6..fa6c440 100644 --- a/spec/license_meta_spec.rb +++ b/spec/license_meta_spec.rb @@ -28,16 +28,12 @@ describe 'license meta' do 'artistic-2.0', 'bsd-3-clause-clear', 'bsl-1.0', - 'cc0-1.0', - 'cc-by-4.0', - 'cc-by-sa-4.0', 'eupl-1.1', 'lgpl-2.1', 'lgpl-3.0', 'lppl-1.3c', 'ms-pl', 'ms-rl', - 'ofl-1.1', 'wtfpl', 'zlib' ] From 44c8b266ac9d7856cbce831c06704b4d49fe5c8a Mon Sep 17 00:00:00 2001 From: Mike Linksvayer Date: Wed, 20 Nov 2019 08:06:37 -0800 Subject: [PATCH 23/70] unhide cc0 --- _licenses/cc0-1.0.txt | 1 + 1 file changed, 1 insertion(+) diff --git a/_licenses/cc0-1.0.txt b/_licenses/cc0-1.0.txt index 8224dd2..7f0679a 100644 --- a/_licenses/cc0-1.0.txt +++ b/_licenses/cc0-1.0.txt @@ -2,6 +2,7 @@ title: Creative Commons Zero v1.0 Universal spdx-id: CC0-1.0 redirect_from: /licenses/cc0/ +hidden:false description: The Creative Commons CC0 Public Domain Dedication waives copyright interest in a work you've created and dedicates it to the world-wide public domain. Use CC0 to opt out of copyright entirely and ensure your work has the widest reach. As with the Unlicense and typical software licenses, CC0 disclaims warranties. CC0 is very similar to the Unlicense. From 379bf41d444da120d22f940469381c9e7ae1828a Mon Sep 17 00:00:00 2001 From: Mike Linksvayer Date: Wed, 20 Nov 2019 08:11:57 -0800 Subject: [PATCH 24/70] fix yaml, test --- _licenses/cc0-1.0.txt | 2 +- spec/license_shown_spec.rb | 3 ++- 2 files changed, 3 insertions(+), 2 deletions(-) diff --git a/_licenses/cc0-1.0.txt b/_licenses/cc0-1.0.txt index 7f0679a..6fe2d15 100644 --- a/_licenses/cc0-1.0.txt +++ b/_licenses/cc0-1.0.txt @@ -2,7 +2,7 @@ title: Creative Commons Zero v1.0 Universal spdx-id: CC0-1.0 redirect_from: /licenses/cc0/ -hidden:false +hidden: false description: The Creative Commons CC0 Public Domain Dedication waives copyright interest in a work you've created and dedicates it to the world-wide public domain. Use CC0 to opt out of copyright entirely and ensure your work has the widest reach. As with the Unlicense and typical software licenses, CC0 disclaims warranties. CC0 is very similar to the Unlicense. diff --git a/spec/license_shown_spec.rb b/spec/license_shown_spec.rb index 8ef6725..438a536 100644 --- a/spec/license_shown_spec.rb +++ b/spec/license_shown_spec.rb @@ -10,6 +10,7 @@ describe 'shown licenses' do apache-2.0 bsd-2-clause bsd-3-clause + cc0-1.0 epl-2.0 gpl-2.0 gpl-3.0 @@ -21,7 +22,7 @@ describe 'shown licenses' do ].freeze it 'has the expected number of shown licenses' do - expect(shown_licenses.count).to eql(12) + expect(shown_licenses.count).to eql(13) end shown_licenses.each do |license| From ffb3a73623724d20cf3cd1793daec2dbd11cabeb Mon Sep 17 00:00:00 2001 From: Alistair Francis Date: Wed, 26 Jun 2019 22:59:11 -0700 Subject: [PATCH 25/70] Add the BSD-4-Clause license This adds the BSD-4-clause license type. 1. SPDX Identifier: https://spdx.org/licenses/BSD-4-Clause.html 2. GNU's list of free licenses: https://www.gnu.org/licenses/license-list.en.html#OriginalBSD and FSF approved 3. Over 1000 projects: https://github.com/search?q=BSD+4-Clause+filename%3ALICENSE&type=Code 4. Yosemite Blockchain, pwolfgang/querybuilder and PMSPAUR-public use the BSD-4-clause license This is based on the previous work of: https://github.com/github/choosealicense.com/pull/511 Signed-off-by: Alistair Francis --- _licenses/bsd-4-clause.txt | 62 ++++++++++++++++++++++++++++++++++++++ 1 file changed, 62 insertions(+) create mode 100644 _licenses/bsd-4-clause.txt diff --git a/_licenses/bsd-4-clause.txt b/_licenses/bsd-4-clause.txt new file mode 100644 index 0000000..c6ee0f3 --- /dev/null +++ b/_licenses/bsd-4-clause.txt @@ -0,0 +1,62 @@ +--- +title: BSD 4-Clause "Original" or "Old" License +spdx-id: BSD-4-Clause +hidden: true + +description: A permissive license similar to the BSD 3-Clause License, but with a 4th clause (known as the "advertising clause") that requires an acknowledgment of the original source in all advertising material. + +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. Replace [year] with the current year and [fullname] with the name (or names) of the copyright holders. Replace [project] with the project organization, if any, that sponsors this work. + +using: + - Yosemite Blockchain: https://github.com/YosemiteLabs/yosemite-public-blockchain/blob/master/LICENSE + - querybuilder: https://github.com/pwolfgang/querybuilder/blob/master/LICENSE + - PMSPAUR-public: https://github.com/ArthurGodet/PMSPAUR-public/blob/88b6d0fd172950a7e5e1cc595d180565cfaa5462/LICENSE + +permissions: + - commercial-use + - modifications + - distribution + - private-use + +conditions: + - include-copyright + +limitations: + - liability + - warranty + +--- + +BSD 4-Clause License + +Copyright (c) [year], [fullname] +All rights reserved. + +Redistribution and use in source and binary forms, with or without +modification, are permitted provided that the following conditions are met: + +1. Redistributions of source code must retain the above copyright notice, this + list of conditions and the following disclaimer. + +2. Redistributions in binary form must reproduce the above copyright notice, + this list of conditions and the following disclaimer in the documentation + and/or other materials provided with the distribution. + +3. All advertising materials mentioning features or use of this software must + display the following acknowledgement: + This product includes software developed by [project]. + +4. Neither the name of the copyright holder nor the names of its + contributors may be used to endorse or promote products derived from + this software without specific prior written permission. + +THIS SOFTWARE IS PROVIDED BY COPYRIGHT HOLDER "AS IS" AND ANY EXPRESS OR +IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF +MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO +EVENT SHALL COPYRIGHT HOLDER BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, +SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, +PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; +OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, +WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR +OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF +ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. From e23d58b255cab0d80ae6b0f9acae2f53778e5980 Mon Sep 17 00:00:00 2001 From: Alistair Francis Date: Sat, 23 Nov 2019 14:06:16 -0800 Subject: [PATCH 26/70] WIP: Bump licensee to the master branch This PR: https://github.com/licensee/licensee/pull/391 added support for detecting the BSD 4-Clause license. Bump the local licensee to use the master branch in order to correctly detect BSD 4-Clause licenses. Signed-off-by: Alistair Francis --- Gemfile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Gemfile b/Gemfile index 6677662..afe5a46 100644 --- a/Gemfile +++ b/Gemfile @@ -16,7 +16,7 @@ end group :test do gem 'html-proofer', '~> 3.0' - gem 'licensee' + gem 'licensee', git: 'https://github.com/licensee/licensee.git', branch: 'master' gem 'rake' gem 'rspec' gem 'rubocop' From c6c26b797fe36608403cb4aa067c70a93ce4e46e Mon Sep 17 00:00:00 2001 From: Mike Linksvayer Date: Sat, 23 Nov 2019 14:24:42 -0800 Subject: [PATCH 27/70] Master branch for example so if use case changes tests will detect --- _licenses/bsd-4-clause.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_licenses/bsd-4-clause.txt b/_licenses/bsd-4-clause.txt index c6ee0f3..d749105 100644 --- a/_licenses/bsd-4-clause.txt +++ b/_licenses/bsd-4-clause.txt @@ -10,7 +10,7 @@ how: Create a text file (typically named LICENSE or LICENSE.txt) in the root of using: - Yosemite Blockchain: https://github.com/YosemiteLabs/yosemite-public-blockchain/blob/master/LICENSE - querybuilder: https://github.com/pwolfgang/querybuilder/blob/master/LICENSE - - PMSPAUR-public: https://github.com/ArthurGodet/PMSPAUR-public/blob/88b6d0fd172950a7e5e1cc595d180565cfaa5462/LICENSE + - PMSPAUR-public: https://github.com/ArthurGodet/PMSPAUR-public/blob/master/LICENSE permissions: - commercial-use From 2ceafa9b13a91361f168fd516d8b8395eaa03601 Mon Sep 17 00:00:00 2001 From: Mike Linksvayer Date: Sat, 23 Nov 2019 14:34:23 -0800 Subject: [PATCH 28/70] BSD-4-Clause tweaks Following up on #669 - hidden is not needed as it is the default - shorten description, don't refer to "4th clause" as the advertising clause is actually the 3rd clause --- _licenses/bsd-4-clause.txt | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/_licenses/bsd-4-clause.txt b/_licenses/bsd-4-clause.txt index d749105..cbb431f 100644 --- a/_licenses/bsd-4-clause.txt +++ b/_licenses/bsd-4-clause.txt @@ -1,9 +1,8 @@ --- title: BSD 4-Clause "Original" or "Old" License spdx-id: BSD-4-Clause -hidden: true -description: A permissive license similar to the BSD 3-Clause License, but with a 4th clause (known as the "advertising clause") that requires an acknowledgment of the original source in all advertising material. +description: A permissive license similar to the BSD 3-Clause License, but with an "advertising clause" that requires an acknowledgment of the original source in all advertising material. 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. Replace [year] with the current year and [fullname] with the name (or names) of the copyright holders. Replace [project] with the project organization, if any, that sponsors this work. From a378dbc7fff93015365f16b067215c8ab3a80b06 Mon Sep 17 00:00:00 2001 From: Mike Linksvayer Date: Mon, 2 Dec 2019 21:32:07 -0800 Subject: [PATCH 29/70] Make rules with -- eg same-license--file appear lighter in appendix table Not needed elsewhere eg license view because actual rule is spelled out and no distinction with other licenses with non-attenuated versions of the rules is useful for eyeballing Some visual cue other than .5 opacity might be more useful, eg smaller or not filled in circle, but this is easy first cut given current sprite setup --- appendix.md | 7 ++++++- assets/css/application.scss | 1 + 2 files changed, 7 insertions(+), 1 deletion(-) diff --git a/appendix.md b/appendix.md index 02232ac..e08fd83 100644 --- a/appendix.md +++ b/appendix.md @@ -42,7 +42,12 @@ If you're here to choose a license, **[start from the home page](/)** to see a f {% for r in license[t] %} {% if r contains req %} - + {% if r contains "--" %} + {% assign lite = " lite" %} + {% else %} + {% assign lite = "" %} + {% endif %} + diff --git a/assets/css/application.scss b/assets/css/application.scss index e462748..4c14552 100644 --- a/assets/css/application.scss +++ b/assets/css/application.scss @@ -254,6 +254,7 @@ strong { .license-limitations span { background-position: -16px 0; width: 12px; height: 12px; } .license-permissions span { background-position: -28px 0; width: 12px; height: 12px; } .license-conditions span { background-position: -40px 0; width: 12px; height: 12px; } +.lite span { opacity: 0.5; } .license-rules-sidebar li { float: none; From 5419f535cea0394db796544abbb9d7958d6f5b0f Mon Sep 17 00:00:00 2001 From: Mike Linksvayer Date: Tue, 24 Dec 2019 13:51:15 -0800 Subject: [PATCH 30/70] Amend [G]GPL-3.0 how to apply and "hide" LGPL-3.0 from PR initiator as it requires multiple steps not supported by GitHub license picker, should be carried out by people who know exactly what they're doing. --- _includes/sidebar.html | 2 ++ _licenses/gpl-3.0.txt | 2 +- _licenses/lgpl-3.0.txt | 1 - spec/license_shown_spec.rb | 4 ++-- 4 files changed, 5 insertions(+), 4 deletions(-) diff --git a/_includes/sidebar.html b/_includes/sidebar.html index 72e56af..56d4d93 100644 --- a/_includes/sidebar.html +++ b/_includes/sidebar.html @@ -1,6 +1,7 @@
Copy license text to clipboard + {% unless page.spdx-id == 'LGPL-3.0' %}

Suggest this license

Make a pull request to suggest this license for a project that is not licensed. Please be polite: see if a license has already been suggested, try to suggest a license fitting for the project's community, and keep your communication with project maintainers friendly.

@@ -9,6 +10,7 @@
+ {% endunless %}

How to apply this license

diff --git a/_licenses/gpl-3.0.txt b/_licenses/gpl-3.0.txt index 2e93005..fa71f4a 100644 --- a/_licenses/gpl-3.0.txt +++ b/_licenses/gpl-3.0.txt @@ -8,7 +8,7 @@ hidden: false description: Permissions of this strong copyleft license are conditioned on making available complete source code of licensed works and modifications, which include larger works using a licensed work, under the same license. Copyright and license notices must be preserved. Contributors provide an express grant of patent rights. -how: Create a text file in the root of your source code, typically named COPYING (a GNU convention), LICENSE or LICENSE.txt. Then copy the text of the license into that file. +how: Create a text file in the root of your source code, typically named COPYING (a GNU convention). Then copy the text of the license into that 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. diff --git a/_licenses/lgpl-3.0.txt b/_licenses/lgpl-3.0.txt index e27c333..407ae1f 100644 --- a/_licenses/lgpl-3.0.txt +++ b/_licenses/lgpl-3.0.txt @@ -3,7 +3,6 @@ title: GNU Lesser General Public License v3.0 spdx-id: LGPL-3.0 nickname: GNU LGPLv3 redirect_from: /licenses/lgpl-v3/ -hidden: false description: Permissions of this copyleft license are conditioned on making available complete source code of licensed works and modifications under the same license or the GNU GPLv3. Copyright and 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 source code for the larger work. diff --git a/spec/license_shown_spec.rb b/spec/license_shown_spec.rb index 438a536..384da13 100644 --- a/spec/license_shown_spec.rb +++ b/spec/license_shown_spec.rb @@ -15,14 +15,14 @@ describe 'shown licenses' do gpl-2.0 gpl-3.0 lgpl-2.1 - lgpl-3.0 mit mpl-2.0 unlicense ].freeze it 'has the expected number of shown licenses' do - expect(shown_licenses.count).to eql(13) + expect(shown_licenses.count).to eql(12) + expect(SHOWN_LICENSES.count).to eql(shown_licenses.count) end shown_licenses.each do |license| From ba48c3d877953c80abb95077bf3f326ca24a08f3 Mon Sep 17 00:00:00 2001 From: Mike Linksvayer Date: Wed, 25 Dec 2019 10:58:01 -0800 Subject: [PATCH 31/70] rm unneeded trailing whitespace from various files --- _includes/footer.html | 2 +- _includes/sidebar.html | 2 +- _layouts/license.html | 12 +++++------ _licenses/cecill-2.1.txt | 6 +++--- _licenses/epl-2.0.txt | 4 ++-- _licenses/ncsa.txt | 42 ++++++++++++++++++------------------- _licenses/postgresql.txt | 2 +- assets/css/application.scss | 8 +++---- assets/js/app.coffee | 26 +++++++++++------------ 9 files changed, 52 insertions(+), 52 deletions(-) diff --git a/_includes/footer.html b/_includes/footer.html index 6a16215..4b453a7 100644 --- a/_includes/footer.html +++ b/_includes/footer.html @@ -23,7 +23,7 @@ window.annotations = {{ site.data.rules | jsonify }}; {% if page.collection == "licenses" %} window.licenses = [ - {% for license in site.licenses %} + {% for license in site.licenses %} { "title": "{{ license.title | escape }}", "spdx_id": "{{ license.spdx-id | escape }}" diff --git a/_includes/sidebar.html b/_includes/sidebar.html index 72e56af..83a4abd 100644 --- a/_includes/sidebar.html +++ b/_includes/sidebar.html @@ -2,7 +2,7 @@ Copy license text to clipboard

Suggest this license

-
+

Make a pull request to suggest this license for a project that is not licensed. Please be polite: see if a license has already been suggested, try to suggest a license fitting for the project's community, and keep your communication with project maintainers friendly.

diff --git a/_layouts/license.html b/_layouts/license.html index 297e827..ac63b38 100644 --- a/_layouts/license.html +++ b/_layouts/license.html @@ -1,9 +1,9 @@ {% include header.html %}
- +
- + {% if page.nickname %}

{{ page.nickname }} @@ -13,9 +13,9 @@

{{ page.description }}

- +
- + {% assign types = "permissions|conditions|limitations" | split: "|" %} @@ -42,11 +42,11 @@ {% endfor %}
- + 
{{ content | replace:"<", "<" | replace:">", ">" }}
- +
{% include sidebar.html %} diff --git a/_licenses/cecill-2.1.txt b/_licenses/cecill-2.1.txt index 3f9f308..d1758d4 100644 --- a/_licenses/cecill-2.1.txt +++ b/_licenses/cecill-2.1.txt @@ -4,7 +4,7 @@ spdx-id: CECILL-2.1 description: Strong copyleft license made by three French public research organisations, CEA, CNRS, and Inria, compatible with AGPL-3.0, EUPL-1.1, and GPL-2.0, or later versions of those licenses. -how: Create a text file (typically named LICENSE or LICENCE) in the root of your source code and copy the text of the license into the file. +how: Create a text file (typically named LICENSE or LICENCE) in the root of your source code and copy the text of the license into the file. using: - BMC-Tools: https://github.com/ANSSI-FR/bmc-tools/blob/master/LICENCE.txt @@ -22,7 +22,7 @@ conditions: - include-copyright - disclose-source - same-license - + limitations: - liability - warranty @@ -102,7 +102,7 @@ titulaire des droits patrimoniaux décide de soumettre l'exploitation aux dispositions qu'il contient. Une liste de questions fréquemment posées se trouve sur le site web -officiel de la famille des licences CeCILL +officiel de la famille des licences CeCILL (http://www.cecill.info/index.fr.html) pour toute clarification qui serait nécessaire. diff --git a/_licenses/epl-2.0.txt b/_licenses/epl-2.0.txt index e357612..aacc042 100644 --- a/_licenses/epl-2.0.txt +++ b/_licenses/epl-2.0.txt @@ -294,8 +294,8 @@ No third-party beneficiary rights are created under this Agreement. Exhibit A - Form of Secondary Licenses Notice -"This Source Code may also be made available under the following -Secondary Licenses when the conditions for such availability set forth +"This Source Code may also be made available under the following +Secondary Licenses when the conditions for such availability set forth in the Eclipse Public License, v. 2.0 are satisfied: {name license(s), version(s), and exceptions or additional permissions here}." diff --git a/_licenses/ncsa.txt b/_licenses/ncsa.txt index 9f1dab9..2454bd8 100644 --- a/_licenses/ncsa.txt +++ b/_licenses/ncsa.txt @@ -7,7 +7,7 @@ description: The University of Illinois/NCSA Open Source License, or UIUC licens 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. Replace [year] with the current year and [fullname] with the name (or names) of the copyright holders. Replace [project] with the project organization, if any, that sponsors this work. -using: +using: - LLDB: https://github.com/llvm-mirror/lldb/blob/master/LICENSE.TXT - ROCR-Runtime: https://github.com/RadeonOpenCompute/ROCR-Runtime/blob/master/LICENSE.txt - RLTK: https://github.com/chriswailes/RLTK/blob/master/LICENSE @@ -27,37 +27,37 @@ limitations: --- -University of Illinois/NCSA Open Source License +University of Illinois/NCSA Open Source License -Copyright (c) [year] [fullname]. All rights reserved. +Copyright (c) [year] [fullname]. All rights reserved. -Developed by: [project] - [fullname] +Developed by: [project] + [fullname] [projecturl] - -Permission is hereby granted, free of charge, to any person -obtaining a copy of this software and associated documentation files -(the "Software"), to deal with the Software without restriction, + +Permission is hereby granted, free of charge, to any person +obtaining a copy of this software and associated documentation files +(the "Software"), to deal with the Software without restriction, including without limitation the rights to use, copy, modify, merge, -publish, distribute, sublicense, and/or sell copies of the Software, -and to permit persons to whom the Software is furnished to do so, +publish, distribute, sublicense, and/or sell copies of the Software, +and to permit persons to whom the Software is furnished to do so, subject to the following conditions: -* Redistributions of source code must retain the above copyright notice, +* Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimers. -* Redistributions in binary form must reproduce the above copyright - notice, this list of conditions and the following disclaimers in the +* Redistributions in binary form must reproduce the above copyright + notice, this list of conditions and the following disclaimers in the documentation and/or other materials provided with the distribution. -* Neither the names of [fullname], [project] nor the names of its +* Neither the names of [fullname], [project] nor the names of its contributors may be used to endorse or promote products derived from this Software without specific prior written permission. - -THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS -OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, -FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE -CONTRIBUTORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER -LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, + +THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS +OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, +FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE +CONTRIBUTORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER +LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS WITH THE SOFTWARE. diff --git a/_licenses/postgresql.txt b/_licenses/postgresql.txt index 9b74302..03f244a 100644 --- a/_licenses/postgresql.txt +++ b/_licenses/postgresql.txt @@ -2,7 +2,7 @@ title: PostgreSQL License spdx-id: PostgreSQL -description: A very short, BSD-style license, used specifically for PostgreSQL. +description: A very short, BSD-style license, used specifically for PostgreSQL. how: To use it, say that it is The PostgreSQL License, and then substitute the copyright year and name of the copyright holder into the body of the license. Then put the license into a prominent file ("COPYRIGHT", "LICENSE" or "COPYING" are common names for this file) in your software distribution. diff --git a/assets/css/application.scss b/assets/css/application.scss index 4c14552..779b75c 100644 --- a/assets/css/application.scss +++ b/assets/css/application.scss @@ -315,16 +315,16 @@ strong { border-radius: 50%; background: #fff; animation: none; - border: 4px solid #ddd; + border: 4px solid #ddd; } -.input-wrapper .status-indicator.fetching { +.input-wrapper .status-indicator.fetching { border-right-color: transparent; animation: rotate 0.8s infinite linear; } -.input-wrapper .status-indicator.error { - border: 4px solid #c6403d; +.input-wrapper .status-indicator.error { + border: 4px solid #c6403d; } @keyframes rotate { diff --git a/assets/js/app.coffee b/assets/js/app.coffee index d9b0778..72cfcd5 100644 --- a/assets/js/app.coffee +++ b/assets/js/app.coffee @@ -71,7 +71,7 @@ class Choosealicense # Post-copy user feedback callback clipboardComplete: (client, args) -> @textContent = "Copied!" - + # Initializes the repository suggestion feature initLicenseSuggestion: -> inputEl = $("#repository-url") @@ -83,7 +83,7 @@ class LicenseSuggestion constructor: (@inputEl, @licenseId, @statusIndicator) -> @setupTooltips() @bindEventHandlers() - + # Initializes tooltips on the input element setupTooltips: => @inputEl.qtip @@ -98,12 +98,12 @@ class LicenseSuggestion at: "bottom center" style: classes: "qtip-shadow" - + # Main event handlers for user input - bindEventHandlers: => + bindEventHandlers: => @inputEl.on "input", (event) => @setStatus "" - .on "keyup", (event) => + .on "keyup", (event) => if event.keyCode == 13 and event.target.value # Validate the user input first try @@ -111,8 +111,8 @@ class LicenseSuggestion catch @setStatus "Error", "Invalid URL." return - - @setStatus "Fetching" + + @setStatus "Fetching" @fetchInfoFromGithubAPI repositoryFullName, (err, repositoryInfo=null) => if (err) @setStatus "Error", err.message @@ -137,7 +137,7 @@ class LicenseSuggestion .slice 0, 1 .join "" return username + '/' + project - + # Displays an indicator and tooltips to the user about the current status setStatus: (status="", message="") => statusClass = status.toLowerCase() @@ -157,25 +157,25 @@ class LicenseSuggestion else @inputEl.qtip("api").hide() @statusIndicator.removeClass('fetching error') - + # Fetches information about a repository from the Github API fetchInfoFromGithubAPI: (repositoryFullName, callback) -> $.getJSON "https://api.github.com/repos/"+repositoryFullName, (info) -> callback null, info - .fail (e) -> + .fail (e) -> if e.status == 404 callback new Error "Repository #{repositoryFullName} not found." else callback new Error "Network error when trying to get information about #{repositoryFullName}." - + # Generates a message showing that a repository is already licensed repositoryLicense: (repositoryFullName, license) -> foundLicense = window.licenses.find (lic) -> lic.spdx_id == license.spdx_id if foundLicense # Links the license to its page on this site - "The repository #{repositoryFullName} is already licensed under the + "The repository #{repositoryFullName} is already licensed under the #{foundLicense.title}." else "The repository #{repositoryFullName} is already licensed." - + $ -> new Choosealicense() From 4c002534af076b00850efcaab907aa8fbb41101d Mon Sep 17 00:00:00 2001 From: Mike Linksvayer Date: Thu, 26 Dec 2019 13:41:37 -0800 Subject: [PATCH 32/70] Show BSL-1.0 between MIT and Unlicense in license spectrum --- _licenses/bsl-1.0.txt | 1 + licenses.html | 1 + spec/license_shown_spec.rb | 3 ++- 3 files changed, 4 insertions(+), 1 deletion(-) diff --git a/_licenses/bsl-1.0.txt b/_licenses/bsl-1.0.txt index 8da7d01..d12fda2 100644 --- a/_licenses/bsl-1.0.txt +++ b/_licenses/bsl-1.0.txt @@ -1,6 +1,7 @@ --- title: Boost Software License 1.0 spdx-id: BSL-1.0 +hidden: false description: A simple permissive license only requiring preservation of copyright and license notices for source (and not binary) distribution. Licensed works, modifications, and larger works may be distributed under different terms and without source code. diff --git a/licenses.html b/licenses.html index c0172d4..62cd60c 100644 --- a/licenses.html +++ b/licenses.html @@ -14,6 +14,7 @@ title: Licenses {% include license-overview.html license-id="mpl-2.0" %} {% include license-overview.html license-id="apache-2.0" %} {% include license-overview.html license-id="mit" %} +{% include license-overview.html license-id="bsl-1.0" %} {% include license-overview.html license-id="unlicense" %} The above licenses represent the entire spectrum of open source licenses, from highly protective to unconditional. One of these should work for most new open source projects. Many other open source licenses exist, including older versions of and close substitutes for some of the above. See the resources listed on our about page if you'd like to read more. diff --git a/spec/license_shown_spec.rb b/spec/license_shown_spec.rb index 384da13..c9e199b 100644 --- a/spec/license_shown_spec.rb +++ b/spec/license_shown_spec.rb @@ -10,6 +10,7 @@ describe 'shown licenses' do apache-2.0 bsd-2-clause bsd-3-clause + bsl-1.0 cc0-1.0 epl-2.0 gpl-2.0 @@ -21,7 +22,7 @@ describe 'shown licenses' do ].freeze it 'has the expected number of shown licenses' do - expect(shown_licenses.count).to eql(12) + expect(shown_licenses.count).to eql(13) expect(SHOWN_LICENSES.count).to eql(shown_licenses.count) end From a374e4ba3a009f62d9f1bfd5f5a22435f3df76bd Mon Sep 17 00:00:00 2001 From: zisk Date: Fri, 17 Jan 2020 08:46:42 -0500 Subject: [PATCH 33/70] Update link to .NET Core license file It appears the .NET Core repos were consolidated at some point so the current link is no longer valid. More info: https://github.com/dotnet/announcements/issues/119 --- _licenses/mit.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_licenses/mit.txt b/_licenses/mit.txt index 2fd72e4..7aa6087 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/corefx/blob/master/LICENSE.TXT + - .NET Core: https://github.com/dotnet/runtime/blob/master/LICENSE.TXT - Rails: https://github.com/rails/rails/blob/master/MIT-LICENSE permissions: From fd32f9f07812244383b624100e9f1d7540324e29 Mon Sep 17 00:00:00 2001 From: Mike Linksvayer Date: Fri, 17 Jan 2020 09:50:41 -0800 Subject: [PATCH 34/70] temporary workaround for https://github.com/github/pages-gem/issues/665 --- Gemfile | 1 + 1 file changed, 1 insertion(+) diff --git a/Gemfile b/Gemfile index afe5a46..034c4a0 100644 --- a/Gemfile +++ b/Gemfile @@ -6,6 +6,7 @@ require 'json' require 'open-uri' versions = JSON.parse(open('https://pages.github.com/versions.json').read) +gem 'faraday', '< 1.0' gem 'github-pages', versions['github-pages'] group :development do From fc2abb4b6f3d2789d53ce9e32e1406eabad6ac83 Mon Sep 17 00:00:00 2001 From: Waldir Pimenta Date: Sat, 18 Jan 2020 11:49:19 +0000 Subject: [PATCH 35/70] Reword usage note about recommended notices The previous wording was a little awkward. This commit changes it to be a little more explicit and hopefully clearer. --- _licenses/apache-2.0.txt | 2 +- _licenses/ecl-2.0.txt | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/_licenses/apache-2.0.txt b/_licenses/apache-2.0.txt index 5f49c78..be04943 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 at the very end of the license in the appendix. +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. using: - Kubernetes: https://github.com/kubernetes/kubernetes/blob/master/LICENSE diff --git a/_licenses/ecl-2.0.txt b/_licenses/ecl-2.0.txt index fc2ad2c..e08adba 100644 --- a/_licenses/ecl-2.0.txt +++ b/_licenses/ecl-2.0.txt @@ -6,7 +6,7 @@ description: The Educational Community License version 2.0 ("ECL") consists of t 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 Apereo Foundation recommends taking the additional step of adding a boilerplate notice to the header of each source file. You can find the notice at the very end of the license in the appendix. +note: The Apereo 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: - Sakai: https://github.com/sakaiproject/sakai/blob/master/LICENSE From 134657d43e0678f131a5c3532e34c10aac781471 Mon Sep 17 00:00:00 2001 From: Waldir Pimenta Date: Sun, 19 Jan 2020 15:55:00 +0000 Subject: [PATCH 36/70] Standardize structure of first sentence of usage instructions --- _licenses/artistic-2.0.txt | 2 +- _licenses/cc0-1.0.txt | 2 +- _licenses/gpl-3.0.txt | 2 +- _licenses/lppl-1.3c.txt | 2 +- _licenses/ofl-1.1.txt | 2 +- _licenses/postgresql.txt | 2 +- _licenses/upl-1.0.txt | 2 +- 7 files changed, 7 insertions(+), 7 deletions(-) diff --git a/_licenses/artistic-2.0.txt b/_licenses/artistic-2.0.txt index 043e5e8..3fddba8 100644 --- a/_licenses/artistic-2.0.txt +++ b/_licenses/artistic-2.0.txt @@ -5,7 +5,7 @@ redirect_from: /licenses/artistic/ description: Heavily favored by the Perl community, the Artistic license requires that modified versions of the software do not prevent users from running the standard version. -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. Do not replace the copyright notice (year, author), which refers to the license itself, not the licensed project. +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. Do not replace the copyright notice (year, author), which refers to the license itself, not the licensed project. using: diff --git a/_licenses/cc0-1.0.txt b/_licenses/cc0-1.0.txt index 6fe2d15..c0d954a 100644 --- a/_licenses/cc0-1.0.txt +++ b/_licenses/cc0-1.0.txt @@ -6,7 +6,7 @@ hidden: false description: The Creative Commons CC0 Public Domain Dedication waives copyright interest in a work you've created and dedicates it to the world-wide public domain. Use CC0 to opt out of copyright entirely and ensure your work has the widest reach. As with the Unlicense and typical software licenses, CC0 disclaims warranties. CC0 is very similar to the Unlicense. -how: Create a text file (typically named LICENSE or LICENSE.txt) in the root of your source code and copy the text of the CC0 into the file. +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: Creative Commons recommends taking the additional step of adding a boilerplate notice to the top of each file. The boilerplate can be found on their website. diff --git a/_licenses/gpl-3.0.txt b/_licenses/gpl-3.0.txt index fa71f4a..910a12b 100644 --- a/_licenses/gpl-3.0.txt +++ b/_licenses/gpl-3.0.txt @@ -8,7 +8,7 @@ hidden: false description: Permissions of this strong copyleft license are conditioned on making available complete source code of licensed works and modifications, which include larger works using a licensed work, under the same license. Copyright and license notices must be preserved. Contributors provide an express grant of patent rights. -how: Create a text file in the root of your source code, typically named COPYING (a GNU convention). Then copy the text of the license into that file. +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. diff --git a/_licenses/lppl-1.3c.txt b/_licenses/lppl-1.3c.txt index 97d51e7..43cb8ca 100644 --- a/_licenses/lppl-1.3c.txt +++ b/_licenses/lppl-1.3c.txt @@ -4,7 +4,7 @@ spdx-id: LPPL-1.3c description: The LaTeX Project Public License (LPPL) is the primary license under which the LaTeX kernel and the base LaTeX packages are distributed. -how: To use this license, place in each of the components of your work both an explicit copyright notice including your name and the year the work was authored and/or last substantially modified. Include also a statement that the distribution and/or modification of that component is constrained by the conditions in this license. +how: Place in each of the components of your work both an explicit copyright notice including your name, and the year the work was authored and/or last substantially modified. Include also a statement that the distribution and/or modification of that component is constrained by the conditions in this license. note: An example boilerplate and more information about how to use the license can be found at the end of the license. diff --git a/_licenses/ofl-1.1.txt b/_licenses/ofl-1.1.txt index 192aab3..20ad7ae 100644 --- a/_licenses/ofl-1.1.txt +++ b/_licenses/ofl-1.1.txt @@ -5,7 +5,7 @@ redirect_from: /licenses/ofl/ description: The Open Font License (OFL) is maintained by SIL International. It attempts to be a compromise between the values of the free software and typeface design communities. It is used for almost all open source font projects, including those by Adobe, Google and Mozilla. -how: Create a text file (typically named LICENSE or LICENSE.txt) in the root of your font source and copy the text of the license into the file. Replace [year] with the current year and [fullname] ([email]) with the name and contact email address of each copyright holder. You may take the additional step of appending a Reserved Font Name notice. This option requires anyone making modifications to change the font's name, and is not ideal for web fonts (which all users will modify by changing formats and subsetting for their own needs.) +how: Create a text file (typically named LICENSE or LICENSE.txt) in the root of your font's source code and copy the text of the license into the file. Replace [year] with the current year and [fullname] ([email]) with the name and contact email address of each copyright holder. You may take the additional step of appending a Reserved Font Name notice. This option requires anyone making modifications to change the font's name, and is not ideal for web fonts (which all users will modify by changing formats and subsetting for their own needs.) note: This license doesn't require source provision, but recommends it. All files derived from OFL files must remain licensed under the OFL. diff --git a/_licenses/postgresql.txt b/_licenses/postgresql.txt index 03f244a..24176f6 100644 --- a/_licenses/postgresql.txt +++ b/_licenses/postgresql.txt @@ -4,7 +4,7 @@ spdx-id: PostgreSQL description: A very short, BSD-style license, used specifically for PostgreSQL. -how: To use it, say that it is The PostgreSQL License, and then substitute the copyright year and name of the copyright holder into the body of the license. Then put the license into a prominent file ("COPYRIGHT", "LICENSE" or "COPYING" are common names for this file) in your software distribution. +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. Replace [year] with the current year and [fullname] with the name (or names) of the copyright holders. using: - pgBadger: https://github.com/darold/pgbadger/blob/master/LICENSE diff --git a/_licenses/upl-1.0.txt b/_licenses/upl-1.0.txt index eb7f4f7..0fa4c4b 100644 --- a/_licenses/upl-1.0.txt +++ b/_licenses/upl-1.0.txt @@ -4,7 +4,7 @@ spdx-id: UPL-1.0 description: A permissive, OSI and FSF approved, GPL compatible license, expressly allowing attribution with just a copyright notice and a short form link rather than the full text of the license. Includes an express grant of patent rights. Licensed works and modifications may be distributed under different terms and without source code, and the patent grant may also optionally be expanded to larger works to permit use as a contributor license agreement. -how: Insert the license or a link to it along with a copyright notice into your source file(s), and/or create a text file (typically named LICENSE or LICENSE.txt) in the root of your source code and copy the text of the license and your copyright notice into the file. +how: Insert the license or a link to it along with a copyright notice into your source file(s), and/or 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, replacing [year] with the current year and [fullname] with the name (or names) of the copyright holders. 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/. From 23754503dd15bcddac08852564c99d42ec255075 Mon Sep 17 00:00:00 2001 From: othree Date: Thu, 13 Jun 2019 23:32:15 +0800 Subject: [PATCH 37/70] Add vim.txt --- _licenses/vim.txt | 114 ++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 114 insertions(+) create mode 100644 _licenses/vim.txt diff --git a/_licenses/vim.txt b/_licenses/vim.txt new file mode 100644 index 0000000..acf879b --- /dev/null +++ b/_licenses/vim.txt @@ -0,0 +1,114 @@ +--- +title: VIM LICENSE +spdx-id: Vim +featured: false +hidden: false + +description: There are no restrictions on using or distributing an unmodified copy of the software. Parts of the software may also be distributed, but the license text must always be included. For modified versions a few restrictions apply. The license is GPL compatible, you may compile the software with GPL libraries and distribute it. + +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. Replace [project] with the project name. + +using: + - Vim https://github.com/vim/vim/blob/master/LICENSE + - Pathogen https://github.com/tpope/vim-pathogen/blob/master/LICENSE + - vim-license-gen: https://github.com/othree/vim-license/blob/master/LICENSE + +permissions: + - commercial-use + - modifications + - distribution + - private-use + +conditions: + - include-copyright + - document-changes + - disclose-source + - same-license + +limitations: + - liability + +--- + +VIM LICENSE + +I) There are no restrictions on distributing unmodified copies of [project] + except that they must include this license text. You can also distribute + unmodified parts of [project], likewise unrestricted except that they must + include this license text. You are also allowed to include executables + that you made from the unmodified [project] sources, plus your own usage + examples and Vim scripts. + +II) It is allowed to distribute a modified (or extended) version of [project], + including executables and/or source code, when the following four + conditions are met: + 1) This license text must be included unmodified. + 2) The modified [project] must be distributed in one of the following five + ways: + a) If you make changes to [project] yourself, you must clearly describe + in the distribution how to contact you. When the maintainer asks + you (in any way) for a copy of the modified [project] you + distributed, you must make your changes, including source code, + available to the maintainer without fee. The maintainer reserves + the right to include your changes in the official version of + [project]. What the maintainer will do with your changes and under + what license they will be distributed is negotiable. If there has + been no negotiation then this license, or a later version, also + applies to your changes. The current maintainer is Bram Moolenaar + . If this changes it will be announced in appropriate + places (most likely vim.sf.net, www.vim.org and/or comp.editors). + When it is completely impossible to contact the maintainer, the + obligation to send him your changes ceases. Once the maintainer has + confirmed that he has received your changes they will not have to be + sent again. + b) If you have received a modified [project] that was distributed as + mentioned under a) you are allowed to further distribute it + unmodified, as mentioned at I). If you make additional changes the + text under a) applies to those changes. + c) Provide all the changes, including source code, with every copy of + the modified [project] you distribute. This may be done in the form + of a context diff. You can choose what license to use for new code + you add. The changes and their license must not restrict others + from making their own changes to the official version of [project]. + d) When you have a modified [project] which includes changes as + mentioned under c), you can distribute it without the source code + for the changes if the following three conditions are met: + - The license that applies to the changes permits you to distribute + the changes to the Vim maintainer without fee or restriction, and + permits the Vim maintainer to include the changes in the official + version of [project] without fee or restriction. + - You keep the changes for at least three years after last + distributing the corresponding modified [project]. When the + maintainer or someone who you distributed the modified [project] + to asks you (in any way) for the changes within this period, you + must make them available to him. + - You clearly describe in the distribution how to contact you. This + contact information must remain valid for at least three years + after last distributing the corresponding modified [project], or + as long as possible. + e) When the GNU General Public License (GPL) applies to the changes, + you can distribute the modified [project] under the GNU GPL version + 2 or any later version. + 3) A message must be added, at least in the output of the ":version" + command and in the intro screen, such that the user of the modified + [project] is able to see that it was modified. When distributing as + mentioned under 2)e) adding the message is only required for as far as + this does not conflict with the license used for the changes. + 4) The contact information as required under 2)a) and 2)d) must not be + removed or changed, except that the person himself can make + corrections. + +III) If you distribute a modified version of [project], you are encouraged to + use the Vim license for your changes and make them available to the + maintainer, including the source code. The preferred way to do this is + by e-mail or by uploading the files to a server and e-mailing the URL. If + the number of changes is small (e.g., a modified Makefile) e-mailing a + context diff will do. The e-mail address to be used is + + +IV) It is not allowed to remove this license from the distribution of the + [project] sources, parts of it or from a modified version. You may use + this license for previous [project] releases instead of the license that + they came with, at your option. + + From 3ea95b5acc4150bc9f45799880e6baeaa1d07d23 Mon Sep 17 00:00:00 2001 From: Mike Linksvayer Date: Tue, 21 Jan 2020 12:12:51 -0800 Subject: [PATCH 38/70] yml syntax --- _licenses/vim.txt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/_licenses/vim.txt b/_licenses/vim.txt index acf879b..84c5dfc 100644 --- a/_licenses/vim.txt +++ b/_licenses/vim.txt @@ -9,8 +9,8 @@ description: There are no restrictions on using or distributing an unmodified co 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. Replace [project] with the project name. using: - - Vim https://github.com/vim/vim/blob/master/LICENSE - - Pathogen https://github.com/tpope/vim-pathogen/blob/master/LICENSE + - Vim: https://github.com/vim/vim/blob/master/LICENSE + - Pathogen: https://github.com/tpope/vim-pathogen/blob/master/LICENSE - vim-license-gen: https://github.com/othree/vim-license/blob/master/LICENSE permissions: From 2926ce39ae8d2387660e74975eee2c60b7aeb1ff Mon Sep 17 00:00:00 2001 From: Mike Linksvayer Date: Tue, 21 Jan 2020 12:26:46 -0800 Subject: [PATCH 39/70] address failing tests --- _licenses/vim.txt | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/_licenses/vim.txt b/_licenses/vim.txt index 84c5dfc..336b655 100644 --- a/_licenses/vim.txt +++ b/_licenses/vim.txt @@ -1,8 +1,6 @@ --- -title: VIM LICENSE +title: Vim License spdx-id: Vim -featured: false -hidden: false description: There are no restrictions on using or distributing an unmodified copy of the software. Parts of the software may also be distributed, but the license text must always be included. For modified versions a few restrictions apply. The license is GPL compatible, you may compile the software with GPL libraries and distribute it. From b509f7fa1f69213669f4b7e7c83d7037be8f55dd Mon Sep 17 00:00:00 2001 From: othree Date: Thu, 23 Jan 2020 14:47:04 +0800 Subject: [PATCH 40/70] Vim don't have limitation of liability:Wq --- _licenses/vim.txt | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/_licenses/vim.txt b/_licenses/vim.txt index 336b655..d850bd9 100644 --- a/_licenses/vim.txt +++ b/_licenses/vim.txt @@ -23,8 +23,7 @@ conditions: - disclose-source - same-license -limitations: - - liability +limitations: [] --- From 06c47f20979a297f37902cc87d4a2c367c76f206 Mon Sep 17 00:00:00 2001 From: Mike Linksvayer Date: Fri, 24 Jan 2020 11:39:40 -0800 Subject: [PATCH 41/70] Revert "temporary workaround for https://github.com/github/pages-gem/issues/665" This reverts commit fd32f9f07812244383b624100e9f1d7540324e29. --- Gemfile | 1 - 1 file changed, 1 deletion(-) diff --git a/Gemfile b/Gemfile index 034c4a0..afe5a46 100644 --- a/Gemfile +++ b/Gemfile @@ -6,7 +6,6 @@ require 'json' require 'open-uri' versions = JSON.parse(open('https://pages.github.com/versions.json').read) -gem 'faraday', '< 1.0' gem 'github-pages', versions['github-pages'] group :development do From e8fd008979887f2ad2995e1fc76dfd405cd43dfb Mon Sep 17 00:00:00 2001 From: Waldir Pimenta Date: Sat, 29 Feb 2020 13:46:54 +0000 Subject: [PATCH 42/70] ISC examples: replace helix with starship --- _licenses/isc.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_licenses/isc.txt b/_licenses/isc.txt index 47de91a..ecf012c 100644 --- a/_licenses/isc.txt +++ b/_licenses/isc.txt @@ -7,7 +7,7 @@ description: A permissive license lets people do anything with your code with pr 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. Replace [year] with the current year and [fullname] with the name (or names) of the copyright holders. using: - - Helix: https://github.com/tildeio/helix/blob/master/LICENSE + - Starship: https://github.com/starship/starship/blob/master/LICENSE - Node.js semver: https://github.com/npm/node-semver/blob/master/LICENSE - OpenStreetMap iD: https://github.com/openstreetmap/iD/blob/master/LICENSE.md From d12ed9d1f81ce329ae1e88bf4f5ca87643190a89 Mon Sep 17 00:00:00 2001 From: Waldir Pimenta Date: Tue, 31 Mar 2020 18:39:09 +0100 Subject: [PATCH 43/70] Fix formatting of Creative Commons licenses --- _licenses/cc-by-4.0.txt | 26 +++++++++++++------------- _licenses/cc-by-sa-4.0.txt | 26 +++++++++++++------------- 2 files changed, 26 insertions(+), 26 deletions(-) diff --git a/_licenses/cc-by-4.0.txt b/_licenses/cc-by-4.0.txt index d9a4a36..7a87f4a 100644 --- a/_licenses/cc-by-4.0.txt +++ b/_licenses/cc-by-4.0.txt @@ -64,7 +64,7 @@ exhaustive, and do not form part of our licenses. material not subject to the license. This includes other CC- licensed material, or material used under an exception or limitation to copyright. More considerations for licensors: - wiki.creativecommons.org/Considerations_for_licensors + wiki.creativecommons.org/Considerations_for_licensors Considerations for the public: By using one of our public licenses, a licensor grants the public permission to use the @@ -79,9 +79,9 @@ exhaustive, and do not form part of our licenses. rights in the material. A licensor may make special requests, such as asking that all changes be marked or described. Although not required by our licenses, you are encouraged to - respect those requests where reasonable. More_considerations + respect those requests where reasonable. More considerations for the public: - wiki.creativecommons.org/Considerations_for_licensees + wiki.creativecommons.org/Considerations_for_licensees ======================================================================= @@ -406,21 +406,21 @@ Section 8 -- Interpretation. ======================================================================= -Creative Commons is not a party to its public -licenses. Notwithstanding, Creative Commons may elect to apply one of -its public licenses to material it publishes and in those instances -will be considered the “Licensor.” The text of the Creative Commons -public licenses is dedicated to the public domain under the CC0 Public -Domain Dedication. Except for the limited purpose of indicating that -material is shared under a Creative Commons public license or as -otherwise permitted by the Creative Commons policies published at +Creative Commons is not a party to its public licenses. +Notwithstanding, Creative Commons may elect to apply one of its public +licenses to material it publishes and in those instances will be +considered the “Licensor.” The text of the Creative Commons public +licenses is dedicated to the public domain under the CC0 Public Domain +Dedication. Except for the limited purpose of indicating that material +is shared under a Creative Commons public license or as otherwise +permitted by the Creative Commons policies published at creativecommons.org/policies, Creative Commons does not authorize the use of the trademark "Creative Commons" or any other trademark or logo of Creative Commons without its prior written consent including, without limitation, in connection with any unauthorized modifications to any of its public licenses or any other arrangements, understandings, or agreements concerning use of licensed material. For -the avoidance of doubt, this paragraph does not form part of the -public licenses. +the avoidance of doubt, this paragraph does not form part of the public +licenses. Creative Commons may be contacted at creativecommons.org. diff --git a/_licenses/cc-by-sa-4.0.txt b/_licenses/cc-by-sa-4.0.txt index 8e48b1b..065c1d2 100644 --- a/_licenses/cc-by-sa-4.0.txt +++ b/_licenses/cc-by-sa-4.0.txt @@ -65,7 +65,7 @@ exhaustive, and do not form part of our licenses. material not subject to the license. This includes other CC- licensed material, or material used under an exception or limitation to copyright. More considerations for licensors: - wiki.creativecommons.org/Considerations_for_licensors + wiki.creativecommons.org/Considerations_for_licensors Considerations for the public: By using one of our public licenses, a licensor grants the public permission to use the @@ -80,9 +80,9 @@ exhaustive, and do not form part of our licenses. rights in the material. A licensor may make special requests, such as asking that all changes be marked or described. Although not required by our licenses, you are encouraged to - respect those requests where reasonable. More_considerations + respect those requests where reasonable. More considerations for the public: - wiki.creativecommons.org/Considerations_for_licensees + wiki.creativecommons.org/Considerations_for_licensees ======================================================================= @@ -439,21 +439,21 @@ Section 8 -- Interpretation. ======================================================================= -Creative Commons is not a party to its public -licenses. Notwithstanding, Creative Commons may elect to apply one of -its public licenses to material it publishes and in those instances -will be considered the “Licensor.” The text of the Creative Commons -public licenses is dedicated to the public domain under the CC0 Public -Domain Dedication. Except for the limited purpose of indicating that -material is shared under a Creative Commons public license or as -otherwise permitted by the Creative Commons policies published at +Creative Commons is not a party to its public licenses. +Notwithstanding, Creative Commons may elect to apply one of its public +licenses to material it publishes and in those instances will be +considered the “Licensor.” The text of the Creative Commons public +licenses is dedicated to the public domain under the CC0 Public Domain +Dedication. Except for the limited purpose of indicating that material +is shared under a Creative Commons public license or as otherwise +permitted by the Creative Commons policies published at creativecommons.org/policies, Creative Commons does not authorize the use of the trademark "Creative Commons" or any other trademark or logo of Creative Commons without its prior written consent including, without limitation, in connection with any unauthorized modifications to any of its public licenses or any other arrangements, understandings, or agreements concerning use of licensed material. For -the avoidance of doubt, this paragraph does not form part of the -public licenses. +the avoidance of doubt, this paragraph does not form part of the public +licenses. Creative Commons may be contacted at creativecommons.org. From 4ac8fb30e208e240c98802cfbea94fc5617399ef Mon Sep 17 00:00:00 2001 From: Mike Linksvayer Date: Tue, 31 Mar 2020 10:50:35 -0700 Subject: [PATCH 44/70] update OSD iD LICENSE file location --- _licenses/isc.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_licenses/isc.txt b/_licenses/isc.txt index ecf012c..09299f4 100644 --- a/_licenses/isc.txt +++ b/_licenses/isc.txt @@ -9,7 +9,7 @@ how: Create a text file (typically named LICENSE or LICENSE.txt) in the root of using: - Starship: https://github.com/starship/starship/blob/master/LICENSE - Node.js semver: https://github.com/npm/node-semver/blob/master/LICENSE - - OpenStreetMap iD: https://github.com/openstreetmap/iD/blob/master/LICENSE.md + - OpenStreetMap iD: https://github.com/openstreetmap/iD/blob/develop/LICENSE.md permissions: - commercial-use From 3c5daf9cfc4f8364ea81938076667452cdcb0a78 Mon Sep 17 00:00:00 2001 From: James Addison Date: Fri, 10 Apr 2020 01:12:39 +0100 Subject: [PATCH 45/70] Sidebar links: link to SPDX GPL license pages without deprecation warnings --- _includes/sidebar.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_includes/sidebar.html b/_includes/sidebar.html index cf14dd8..24bae7d 100644 --- a/_includes/sidebar.html +++ b/_includes/sidebar.html @@ -34,7 +34,7 @@
- + Source From 2997310cf80b7653c77ac3628dbd6e7efa27b4ad Mon Sep 17 00:00:00 2001 From: James Addison Date: Fri, 10 Apr 2020 01:13:34 +0100 Subject: [PATCH 46/70] Sidebar links: Update LGPL-3.0 special case --- _includes/sidebar.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_includes/sidebar.html b/_includes/sidebar.html index 24bae7d..452e986 100644 --- a/_includes/sidebar.html +++ b/_includes/sidebar.html @@ -6,7 +6,7 @@

Make a pull request to suggest this license for a project that is not licensed. Please be polite: see if a license has already been suggested, try to suggest a license fitting for the project's community, and keep your communication with project maintainers friendly.

- +
From 3863938ff220ee36a5bb4efee42a95ca7aad635a Mon Sep 17 00:00:00 2001 From: James Addison Date: Fri, 10 Apr 2020 07:31:16 +0100 Subject: [PATCH 47/70] Revert "Sidebar links: Update LGPL-3.0 special case" This reverts commit 2997310cf80b7653c77ac3628dbd6e7efa27b4ad. --- _includes/sidebar.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_includes/sidebar.html b/_includes/sidebar.html index 452e986..24bae7d 100644 --- a/_includes/sidebar.html +++ b/_includes/sidebar.html @@ -6,7 +6,7 @@

Make a pull request to suggest this license for a project that is not licensed. Please be polite: see if a license has already been suggested, try to suggest a license fitting for the project's community, and keep your communication with project maintainers friendly.

- +
From f4f78a5f8f2a672b4fd5a3114779725754ec6778 Mon Sep 17 00:00:00 2001 From: James Addison Date: Fri, 10 Apr 2020 10:45:53 +0100 Subject: [PATCH 48/70] Update _includes/sidebar.html Co-Authored-By: Mike Linksvayer --- _includes/sidebar.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_includes/sidebar.html b/_includes/sidebar.html index 24bae7d..404a48c 100644 --- a/_includes/sidebar.html +++ b/_includes/sidebar.html @@ -34,7 +34,7 @@
- + Source From 3628e08299c995c05fbd928c6c7cd6e5fdf9fcfb Mon Sep 17 00:00:00 2001 From: Mike Linksvayer Date: Mon, 18 May 2020 12:14:02 -0700 Subject: [PATCH 49/70] Update example uses --- _licenses/bsd-4-clause.txt | 4 ++-- _licenses/cc-by-sa-4.0.txt | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/_licenses/bsd-4-clause.txt b/_licenses/bsd-4-clause.txt index cbb431f..9d3758f 100644 --- a/_licenses/bsd-4-clause.txt +++ b/_licenses/bsd-4-clause.txt @@ -7,9 +7,9 @@ description: A permissive license similar to the Date: Sun, 21 Jun 2020 15:25:56 -0700 Subject: [PATCH 51/70] Pages Ruby version bumped Fix this failure ruby version in .travis.yml and pages ruby version match Failure/Error: expect(ci_ruby_version).to eql(pages_ruby_version), msg 2.5.3 != 2.5.8; please add a commit bumping in .travis.yml --- .travis.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.travis.yml b/.travis.yml index 2caf39f..eb64d9a 100644 --- a/.travis.yml +++ b/.travis.yml @@ -5,7 +5,7 @@ script: "./script/cibuild" #environment language: ruby rvm: - - 2.5.3 + - 2.5.8 addons: apt: From b72d00974d95cd022ade5620c07e7ef49eae1bb9 Mon Sep 17 00:00:00 2001 From: Mike Linksvayer Date: Sun, 21 Jun 2020 15:32:37 -0700 Subject: [PATCH 52/70] branch rename for 3 examples --- _licenses/cc0-1.0.txt | 2 +- _licenses/epl-1.0.txt | 2 +- _licenses/mpl-2.0.txt | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/_licenses/cc0-1.0.txt b/_licenses/cc0-1.0.txt index c0d954a..71b5c60 100644 --- a/_licenses/cc0-1.0.txt +++ b/_licenses/cc0-1.0.txt @@ -11,7 +11,7 @@ how: Create a text file (typically named LICENSE or LICENSE.txt) in the root of note: Creative Commons recommends taking the additional step of adding a boilerplate notice to the top of each file. The boilerplate can be found on their website. using: - - Awesome: https://github.com/sindresorhus/awesome/blob/master/license + - Awesome: https://github.com/sindresorhus/awesome/blob/main/license - Shields.io: https://github.com/badges/shields/blob/master/LICENSE - psdash: https://github.com/Jahaja/psdash/blob/master/LICENSE diff --git a/_licenses/epl-1.0.txt b/_licenses/epl-1.0.txt index 8e8d09b..95f7411 100644 --- a/_licenses/epl-1.0.txt +++ b/_licenses/epl-1.0.txt @@ -8,7 +8,7 @@ how: Create a text file (typically named LICENSE or LICENSE.txt) in the root of using: - Eclipse hawkBit: https://github.com/eclipse/hawkbit/blob/master/LICENSE - - JUnit: https://github.com/junit-team/junit4/blob/master/LICENSE-junit.txt + - JUnit: https://github.com/junit-team/junit4/blob/main/LICENSE-junit.txt - Quil: https://github.com/quil/quil/blob/master/LICENSE permissions: diff --git a/_licenses/mpl-2.0.txt b/_licenses/mpl-2.0.txt index dd31d6a..7dd0965 100644 --- a/_licenses/mpl-2.0.txt +++ b/_licenses/mpl-2.0.txt @@ -12,7 +12,7 @@ note: The Mozilla Foundation recommends taking the additional step of adding a b using: - Servo: https://github.com/servo/servo/blob/master/LICENSE - - Syncthing: https://github.com/syncthing/syncthing/blob/master/LICENSE + - Syncthing: https://github.com/syncthing/syncthing/blob/main/LICENSE - TimelineJS3: https://github.com/NUKnightLab/TimelineJS3/blob/master/LICENSE permissions: From 6f9f1e3f451e9b1d0b1f9893e31bb8b597b2a221 Mon Sep 17 00:00:00 2001 From: Mike Linksvayer Date: Sun, 21 Jun 2020 15:38:38 -0700 Subject: [PATCH 53/70] licensee moved from benbalter user to licensee org --- CONTRIBUTING.md | 2 +- README.md | 4 ++-- _data/meta.yml | 2 +- 3 files changed, 4 insertions(+), 4 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 0fcbed8..078d658 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -22,7 +22,7 @@ Choosealicense.com is intended to demystify license choices, not present or cata * [GNU's list of free licenses](https://www.gnu.org/licenses/license-list.en.html) (*note: the license must be listed in one of the three "free" categories*) * [Open Definition's list of conformant licenses](https://opendefinition.org/licenses/) (non-code) 3. The license must be used in at least *1,000* public repositories. This may be documented, for example, with a [GitHub code search](https://github.com/search?q=MIT+filename%3ALICENSE&type=Code). -4. 3 notable projects using the license must be identified. These must have straightforward LICENSE files which serve as examples newcomers can follow and that could be detected by [licensee](https://github.com/benbalter/licensee) if it knew about the license. +4. 3 notable projects using the license must be identified. These must have straightforward LICENSE files which serve as examples newcomers can follow and that could be detected by [licensee](https://github.com/licensee/licensee) if it knew about the license. If your proposed license meets the above criteria, here's a few other things to keep in mind as you propose the license's addition: diff --git a/README.md b/README.md index b0526f1..0f81bb6 100644 --- a/README.md +++ b/README.md @@ -2,7 +2,7 @@ [![Build Status](https://travis-ci.org/github/choosealicense.com.svg?branch=gh-pages)](https://travis-ci.org/github/choosealicense.com) -We catalog [select](CONTRIBUTING.md#adding-a-license) open source licenses with a [Jekyll collection](https://jekyllrb.com/docs/collections/) (in `_licenses`). The catalog is used to render [ChooseALicense.com](https://choosealicense.com) and is regularly vendored into [Licensee](https://github.com/benbalter/licensee), which GitHub uses to provide a [license chooser and license detection](https://help.github.com/articles/adding-a-license-to-a-repository/), a [licenses API](https://developer.github.com/v3/licenses/), and to [display license descriptions and metadata](https://github.com/blog/2335-open-source-license-descriptions-and-metadata). +We catalog [select](CONTRIBUTING.md#adding-a-license) open source licenses with a [Jekyll collection](https://jekyllrb.com/docs/collections/) (in `_licenses`). The catalog is used to render [ChooseALicense.com](https://choosealicense.com) and is regularly vendored into [Licensee](https://github.com/licensee/licensee), which GitHub uses to provide a [license chooser and license detection](https://help.github.com/articles/adding-a-license-to-a-repository/), a [licenses API](https://developer.github.com/v3/licenses/), and to [display license descriptions and metadata](https://github.com/blog/2335-open-source-license-descriptions-and-metadata). ## Goals @@ -37,7 +37,7 @@ Licenses sit in the `/_licenses` folder. Each license has YAML front matter desc * `spdx-id` - Short identifier specified by https://spdx.org/licenses/ * `description` - A human-readable description of the license * `how` - Instructions on how to implement the license -* `using` - A list of 3 notable projects using the license with straightforward LICENSE files which serve as examples newcomers can follow and that can be detected by [licensee](https://github.com/benbalter/licensee) in the form of `project_name: license_file_url` +* `using` - A list of 3 notable projects using the license with straightforward LICENSE files which serve as examples newcomers can follow and that can be detected by [licensee](https://github.com/licensee/licensee) in the form of `project_name: license_file_url` * `permissions` - Bulleted list of permission rules * `conditions` - Bulleted list of condition rules * `limitations` - Bulleted list of limitation rules diff --git a/_data/meta.yml b/_data/meta.yml index 2a58872..61d7160 100644 --- a/_data/meta.yml +++ b/_data/meta.yml @@ -30,7 +30,7 @@ required: true - name: using - description: 'A list of 3 notable projects using the license with straightforward LICENSE files which serve as examples newcomers can follow and that can be detected by [licensee](https://github.com/benbalter/licensee) in the form of `project_name: license_file_url`' + description: 'A list of 3 notable projects using the license with straightforward LICENSE files which serve as examples newcomers can follow and that can be detected by [licensee](https://github.com/licensee/licensee) in the form of `project_name: license_file_url`' required: true # Optional fields From 12f42cabb96ba84a2a2145ce47eef51573490f5d Mon Sep 17 00:00:00 2001 From: Mike Linksvayer Date: Sun, 21 Jun 2020 15:53:25 -0700 Subject: [PATCH 54/70] add vim to hard to detect licenses pending https://github.com/licensee/licensee/pull/437 update NCSA exmaple --- _licenses/ncsa.txt | 2 +- spec/license_meta_spec.rb | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/_licenses/ncsa.txt b/_licenses/ncsa.txt index 2454bd8..7a83fc9 100644 --- a/_licenses/ncsa.txt +++ b/_licenses/ncsa.txt @@ -8,9 +8,9 @@ description: The University of Illinois/NCSA Open Source License, or UIUC licens 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. Replace [year] with the current year and [fullname] with the name (or names) of the copyright holders. Replace [project] with the project organization, if any, that sponsors this work. using: - - LLDB: https://github.com/llvm-mirror/lldb/blob/master/LICENSE.TXT - ROCR-Runtime: https://github.com/RadeonOpenCompute/ROCR-Runtime/blob/master/LICENSE.txt - RLTK: https://github.com/chriswailes/RLTK/blob/master/LICENSE + - ToaruOS: https://github.com/klange/toaruos/blob/master/LICENSE permissions: - commercial-use diff --git a/spec/license_meta_spec.rb b/spec/license_meta_spec.rb index 7436493..3c65e39 100644 --- a/spec/license_meta_spec.rb +++ b/spec/license_meta_spec.rb @@ -58,7 +58,7 @@ describe 'license meta' do end it "is a #{slug} license" do - skip 'NCSA and PostgreSQL licenses hard to detect' if %(ncsa postgresql).include?(slug) + skip 'hard to detect licenses' if %(ncsa postgresql vim).include?(slug) && detected.key == 'other' expect(detected.key).to eq(slug) end end From 804bfb71e91bf84249478a40c0a79a00209ebba0 Mon Sep 17 00:00:00 2001 From: Mike Linksvayer Date: Wed, 8 Jul 2020 08:37:10 -0700 Subject: [PATCH 55/70] Update UPL-1.0 example Fixes broken link --- _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 0fa4c4b..a6c11f8 100644 --- a/_licenses/upl-1.0.txt +++ b/_licenses/upl-1.0.txt @@ -9,9 +9,9 @@ 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 Boxes for Vagrant: https://github.com/oracle/vagrant-boxes/blob/master/LICENSE - Oracle Product Images for Docker: https://github.com/oracle/docker-images/blob/master/LICENSE - Skater: https://github.com/oracle/Skater/blob/master/LICENSE + - Soufflé: https://github.com/souffle-lang/souffle/blob/master/LICENSE permissions: - commercial-use From 9e58d46b2f0075c198b0e9469ce251bf8fc1fa17 Mon Sep 17 00:00:00 2001 From: Andrea Stagi Date: Thu, 23 Jul 2020 20:15:27 +0200 Subject: [PATCH 56/70] =?UTF-8?q?Love=20is=20=E2=9D=A4=EF=B8=8F?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- _includes/footer.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_includes/footer.html b/_includes/footer.html index 4b453a7..d3097e6 100644 --- a/_includes/footer.html +++ b/_includes/footer.html @@ -9,7 +9,7 @@ Creative Commons Attribution 3.0 Unported License.

- Curated with <3 by GitHub, Inc. and You! + Curated with ❤️ by GitHub, Inc. and You!
From 5180893b2afaf43d4f7e5d55accc0b50a1afdd1b Mon Sep 17 00:00:00 2001 From: Mike Linksvayer Date: Thu, 23 Jul 2020 11:29:37 -0700 Subject: [PATCH 57/70] match pages gem --- .rubocop.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.rubocop.yml b/.rubocop.yml index 4b122f8..8230cb9 100644 --- a/.rubocop.yml +++ b/.rubocop.yml @@ -1,5 +1,5 @@ AllCops: - TargetRubyVersion: 2.5 + TargetRubyVersion: 2.7 Exclude: - _site/**/* - vendor/**/* From 40fff598242ce559ca67dcbbd1f58457d0fa6913 Mon Sep 17 00:00:00 2001 From: Mike Linksvayer Date: Thu, 23 Jul 2020 11:30:09 -0700 Subject: [PATCH 58/70] match pages gem --- .travis.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.travis.yml b/.travis.yml index eb64d9a..23e20cd 100644 --- a/.travis.yml +++ b/.travis.yml @@ -5,7 +5,7 @@ script: "./script/cibuild" #environment language: ruby rvm: - - 2.5.8 + - 2.7.1 addons: apt: From 2d9e5be8c236cddd3399e6034932b019a5e77ef3 Mon Sep 17 00:00:00 2001 From: Mike Linksvayer Date: Thu, 23 Jul 2020 12:28:53 -0700 Subject: [PATCH 59/70] slightly reduce branches apparent to rubocop to satisfy rubocop --- spec/spec_helper.rb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/spec/spec_helper.rb b/spec/spec_helper.rb index 192d00e..d66c491 100644 --- a/spec/spec_helper.rb +++ b/spec/spec_helper.rb @@ -105,7 +105,7 @@ def fsf_approved_licenses object = JSON.parse(OpenURI.open_uri(url).read) licenses = {} object['licenses'].each_value do |meta| - next unless (meta.include? 'identifiers') && (meta['identifiers'].include? 'spdx') && (meta.include? 'tags') && (meta['tags'].include? 'libre') + next unless meta.dig('identifiers', 'spdx') && (meta.include? 'tags') && (meta['tags'].include? 'libre') meta['identifiers']['spdx'].each do |identifier| licenses[identifier.downcase] = meta['name'] From fa93f75dafeb200b093a531d7fa6420534dd029b Mon Sep 17 00:00:00 2001 From: Mike Linksvayer Date: Fri, 24 Jul 2020 12:52:33 -0700 Subject: [PATCH 60/70] Generalize software->licensed material in permission/condition/limitiation descriptions Fixes #743 --- _data/rules.yml | 22 +++++++++++----------- 1 file changed, 11 insertions(+), 11 deletions(-) diff --git a/_data/rules.yml b/_data/rules.yml index 1f315b6..5c9a1dd 100644 --- a/_data/rules.yml +++ b/_data/rules.yml @@ -1,14 +1,14 @@ permissions: -- description: This software and derivatives may be used for commercial purposes. +- description: This licensed material and derivatives may be used for commercial purposes. label: Commercial use tag: commercial-use -- description: This software may be modified. +- description: This licensed material may be modified. label: Modification tag: modifications -- description: This software may be distributed. +- description: This licensed material may be distributed. label: Distribution tag: distribution -- description: This software may be used and modified in private. +- description: This licensed material may be used and modified in private. label: Private use tag: private-use - description: This license provides an express grant of patent rights from contributors. @@ -16,28 +16,28 @@ permissions: tag: patent-use conditions: -- description: A copy of the license and copyright notice must be included with the software. +- description: A copy of the license and copyright notice must be included with the licensed material. label: License and copyright notice tag: include-copyright -- description: A copy of the license and copyright notice must be included with the software in source form, but is not required for binaries. +- description: A copy of the license and copyright notice must be included with the licensed material in source form, but is not required for binaries. label: License and copyright notice for source tag: include-copyright--source - description: Changes made to the code must be documented. label: State changes tag: document-changes -- description: Source code must be made available when the software is distributed. +- description: Source code must be made available when the licensed material is distributed. label: Disclose source tag: disclose-source -- description: Users who interact with the software via network are given the right to receive a copy of the source code. +- description: Users who interact with the licensed material via network are given the right to receive a copy of the source code. label: Network use is distribution tag: network-use-disclose -- description: Modifications must be released under the same license when distributing the software. In some cases a similar or related license may be used. +- description: Modifications must be released under the same license when distributing the licensed material. In some cases a similar or related license may be used. label: Same license tag: same-license -- description: Modifications of existing files must be released under the same license when distributing the software. In some cases a similar or related license may be used. +- description: Modifications of existing files must be released under the same license when distributing the licensed material. In some cases a similar or related license may be used. label: Same license (file) tag: same-license--file -- description: Modifications must be released under the same license when distributing the software. In some cases a similar or related license may be used, or this condition may not apply to works that use the software as a library. +- description: Modifications must be released under the same license when distributing the licensed material. In some cases a similar or related license may be used, or this condition may not apply to works that use the licensed material as a library. label: Same license (library) tag: same-license--library From bc6e57a844d675d968fa1dd4eb019bccc26844ca Mon Sep 17 00:00:00 2001 From: Mike Linksvayer Date: Sat, 25 Jul 2020 16:42:11 -0700 Subject: [PATCH 61/70] rm unhelpful articles and demonstratives --- _data/rules.yml | 24 ++++++++++++------------ 1 file changed, 12 insertions(+), 12 deletions(-) diff --git a/_data/rules.yml b/_data/rules.yml index 5c9a1dd..a7a56e6 100644 --- a/_data/rules.yml +++ b/_data/rules.yml @@ -1,14 +1,14 @@ permissions: -- description: This licensed material and derivatives may be used for commercial purposes. +- description: Licensed material and derivatives may be used for commercial purposes. label: Commercial use tag: commercial-use -- description: This licensed material may be modified. +- description: Licensed material may be modified. label: Modification tag: modifications -- description: This licensed material may be distributed. +- description: Licensed material may be distributed. label: Distribution tag: distribution -- description: This licensed material may be used and modified in private. +- description: Licensed material may be used and modified in private. label: Private use tag: private-use - description: This license provides an express grant of patent rights from contributors. @@ -16,28 +16,28 @@ permissions: tag: patent-use conditions: -- description: A copy of the license and copyright notice must be included with the licensed material. +- description: A copy of the license and copyright notice must be included with licensed material. label: License and copyright notice tag: include-copyright -- description: A copy of the license and copyright notice must be included with the licensed material in source form, but is not required for binaries. +- description: A copy of the license and copyright notice must be included with licensed material in source form, but is not required for binaries. label: License and copyright notice for source tag: include-copyright--source -- description: Changes made to the code must be documented. +- description: Changes made to licended material must be documented. label: State changes tag: document-changes -- description: Source code must be made available when the licensed material is distributed. +- description: Source code must be made available when licensed material is distributed. label: Disclose source tag: disclose-source -- description: Users who interact with the licensed material via network are given the right to receive a copy of the source code. +- description: Users who interact with licensed material via network are given the right to receive a copy of source code. label: Network use is distribution tag: network-use-disclose -- description: Modifications must be released under the same license when distributing the licensed material. In some cases a similar or related license may be used. +- description: Modifications must be released under the same license when distributing licensed material. In some cases a similar or related license may be used. label: Same license tag: same-license -- description: Modifications of existing files must be released under the same license when distributing the licensed material. In some cases a similar or related license may be used. +- description: Modifications of existing files must be released under the same license when distributing licensed material. In some cases a similar or related license may be used. label: Same license (file) tag: same-license--file -- description: Modifications must be released under the same license when distributing the licensed material. In some cases a similar or related license may be used, or this condition may not apply to works that use the licensed material as a library. +- description: Modifications must be released under the same license when distributing licensed material. In some cases a similar or related license may be used, or this condition may not apply to works that use licensed material as a library. label: Same license (library) tag: same-license--library From e94c302194afa820b06cbbd94767ba664df6329a Mon Sep 17 00:00:00 2001 From: Mike Linksvayer Date: Sun, 26 Jul 2020 12:08:18 -0700 Subject: [PATCH 62/70] re add articles, this license consistency --- _data/rules.yml | 26 +++++++++++++------------- 1 file changed, 13 insertions(+), 13 deletions(-) diff --git a/_data/rules.yml b/_data/rules.yml index a7a56e6..c15f4f1 100644 --- a/_data/rules.yml +++ b/_data/rules.yml @@ -1,14 +1,14 @@ permissions: -- description: Licensed material and derivatives may be used for commercial purposes. +- description: The licensed material and derivatives may be used for commercial purposes. label: Commercial use tag: commercial-use -- description: Licensed material may be modified. +- description: The licensed material may be modified. label: Modification tag: modifications -- description: Licensed material may be distributed. +- description: The licensed material may be distributed. label: Distribution tag: distribution -- description: Licensed material may be used and modified in private. +- description: The licensed material may be used and modified in private. label: Private use tag: private-use - description: This license provides an express grant of patent rights from contributors. @@ -16,28 +16,28 @@ permissions: tag: patent-use conditions: -- description: A copy of the license and copyright notice must be included with licensed material. +- description: A copy of the license and copyright notice must be included with the licensed material. label: License and copyright notice tag: include-copyright -- description: A copy of the license and copyright notice must be included with licensed material in source form, but is not required for binaries. +- description: A copy of the license and copyright notice must be included with the licensed material in source form, but is not required for binaries. label: License and copyright notice for source tag: include-copyright--source -- description: Changes made to licended material must be documented. +- description: Changes made to the licended material must be documented. label: State changes tag: document-changes -- description: Source code must be made available when licensed material is distributed. +- description: Source code must be made available when the licensed material is distributed. label: Disclose source tag: disclose-source -- description: Users who interact with licensed material via network are given the right to receive a copy of source code. +- description: Users who interact with the licensed material via network are given the right to receive a copy of the source code. label: Network use is distribution tag: network-use-disclose -- description: Modifications must be released under the same license when distributing licensed material. In some cases a similar or related license may be used. +- description: Modifications must be released under the same license when distributing the licensed material. In some cases a similar or related license may be used. label: Same license tag: same-license -- description: Modifications of existing files must be released under the same license when distributing licensed material. In some cases a similar or related license may be used. +- description: Modifications of existing files must be released under the same license when distributing the licensed material. In some cases a similar or related license may be used. label: Same license (file) tag: same-license--file -- description: Modifications must be released under the same license when distributing licensed material. In some cases a similar or related license may be used, or this condition may not apply to works that use licensed material as a library. +- description: Modifications must be released under the same license when distributing the licensed material. In some cases a similar or related license may be used, or this condition may not apply to works that use the licensed material as a library. label: Same license (library) tag: same-license--library @@ -51,6 +51,6 @@ limitations: - description: This license explicitly states that it does NOT grant any rights in the patents of contributors. label: Patent use tag: patent-use -- description: The license explicitly states that it does NOT provide any warranty. +- description: This license explicitly states that it does NOT provide any warranty. label: Warranty tag: warranty From 8d8eeee9ffe4b94508c189cce7a26ff4574269bc Mon Sep 17 00:00:00 2001 From: Mike Linksvayer Date: Sun, 26 Jul 2020 12:11:00 -0700 Subject: [PATCH 63/70] spel --- _data/rules.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_data/rules.yml b/_data/rules.yml index c15f4f1..54e4504 100644 --- a/_data/rules.yml +++ b/_data/rules.yml @@ -22,7 +22,7 @@ conditions: - description: A copy of the license and copyright notice must be included with the licensed material in source form, but is not required for binaries. label: License and copyright notice for source tag: include-copyright--source -- description: Changes made to the licended material must be documented. +- description: Changes made to the licensed material must be documented. label: State changes tag: document-changes - description: Source code must be made available when the licensed material is distributed. From 3074bf679a9b6bd07e052565c504ad7df7954295 Mon Sep 17 00:00:00 2001 From: Mike Linksvayer Date: Thu, 30 Jul 2020 11:53:51 -0700 Subject: [PATCH 64/70] Suppress warning about pending cops, changes suggested by enabled cops --- .rubocop.yml | 3 ++- spec/license_meta_spec.rb | 2 +- spec/spec_helper.rb | 4 ++-- 3 files changed, 5 insertions(+), 4 deletions(-) diff --git a/.rubocop.yml b/.rubocop.yml index 8230cb9..7457108 100644 --- a/.rubocop.yml +++ b/.rubocop.yml @@ -1,4 +1,5 @@ AllCops: + NewCops: enable TargetRubyVersion: 2.7 Exclude: - _site/**/* @@ -7,7 +8,7 @@ AllCops: Metrics/BlockLength: Enabled: false -Metrics/LineLength: +Layout/LineLength: Enabled: false Metrics/MethodLength: diff --git a/spec/license_meta_spec.rb b/spec/license_meta_spec.rb index 3c65e39..858acfb 100644 --- a/spec/license_meta_spec.rb +++ b/spec/license_meta_spec.rb @@ -50,7 +50,7 @@ describe 'license meta' do let(:detected) { Licensee::ProjectFiles::LicenseFile.new(content, 'LICENSE').license } 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') + 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/') example_url.gsub!(%r{/tree/}, '/plain/') elsif example_url.start_with?('https://bitbucket.org/') diff --git a/spec/spec_helper.rb b/spec/spec_helper.rb index d66c491..60a2012 100644 --- a/spec/spec_helper.rb +++ b/spec/spec_helper.rb @@ -7,8 +7,8 @@ require 'open-uri' module SpecHelper class << self - attr_accessor :config, :licenses, :site, :spdx - attr_accessor :osi_approved_licenses, :fsf_approved_licenses, :od_approved_licenses + attr_accessor :config, :licenses, :site, :spdx, + :osi_approved_licenses, :fsf_approved_licenses, :od_approved_licenses end end From 01042feb602d0445744c958462d35eef1b3be401 Mon Sep 17 00:00:00 2001 From: Sohit Miglani Date: Thu, 3 Sep 2020 13:22:17 -0700 Subject: [PATCH 65/70] Update README.md --- README.md | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) diff --git a/README.md b/README.md index 0f81bb6..2dab19f 100644 --- a/README.md +++ b/README.md @@ -14,6 +14,23 @@ We catalog [select](CONTRIBUTING.md#adding-a-license) open source licenses with ## Run It On Your Machine +### Managing Dependencies + +It may be the case that your system doesn't have the required dependencies. You will need 'cmake' and 'make' installed on your computer. + +* For MacOS, use homebrew to update your dependencies (Install Homebrew from [here](https://brew.sh/)): +```bash +brew install make cmake +``` +* For Linux/Ubuntu, use the apt-get tool to install the dependencies: +```bash +sudo apt-get install make cmake +``` + +### Installing and Running the tool + +Note that the third command (./script/bootstrap) may require you to use 'sudo' access for installation. Add 'sudo' right before the third command, if need be, but don't use root access. + ```bash git clone https://github.com/github/choosealicense.com.git cd choosealicense.com From 849216105e792f71493418dbf76ed9c072754a64 Mon Sep 17 00:00:00 2001 From: Mike Linksvayer Date: Thu, 3 Sep 2020 14:39:31 -0700 Subject: [PATCH 66/70] minor formatting --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 2dab19f..83a638a 100644 --- a/README.md +++ b/README.md @@ -18,7 +18,7 @@ We catalog [select](CONTRIBUTING.md#adding-a-license) open source licenses with It may be the case that your system doesn't have the required dependencies. You will need 'cmake' and 'make' installed on your computer. -* For MacOS, use homebrew to update your dependencies (Install Homebrew from [here](https://brew.sh/)): +* For MacOS, use Homebrew to update your dependencies (install Homebrew from ): ```bash brew install make cmake ``` @@ -29,7 +29,7 @@ sudo apt-get install make cmake ### Installing and Running the tool -Note that the third command (./script/bootstrap) may require you to use 'sudo' access for installation. Add 'sudo' right before the third command, if need be, but don't use root access. +Note that the third command (`./script/bootstrap`) may require you to use 'sudo' access for installation. Add 'sudo' right before the third command, if need be, but don't use root access. ```bash git clone https://github.com/github/choosealicense.com.git From 4bacb32aa7f93ea434b1bb7715ad696821bfb911 Mon Sep 17 00:00:00 2001 From: Mike Linksvayer Date: Thu, 3 Sep 2020 14:44:14 -0700 Subject: [PATCH 67/70] more minor formatting --- README.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index 83a638a..894937f 100644 --- a/README.md +++ b/README.md @@ -16,20 +16,20 @@ We catalog [select](CONTRIBUTING.md#adding-a-license) open source licenses with ### Managing Dependencies -It may be the case that your system doesn't have the required dependencies. You will need 'cmake' and 'make' installed on your computer. +It may be the case that your system doesn't have the required dependencies. You will need `cmake` and `make` installed on your computer. -* For MacOS, use Homebrew to update your dependencies (install Homebrew from ): +For MacOS, use Homebrew to update your dependencies (install Homebrew from ): ```bash brew install make cmake ``` -* For Linux/Ubuntu, use the apt-get tool to install the dependencies: +For Linux/Ubuntu, use the `apt-get` tool to install the dependencies: ```bash sudo apt-get install make cmake ``` ### Installing and Running the tool -Note that the third command (`./script/bootstrap`) may require you to use 'sudo' access for installation. Add 'sudo' right before the third command, if need be, but don't use root access. +Note that the third command (`./script/bootstrap`) may require you to use `sudo` access for installation. Add `sudo` right before the third command, if need be, but don't use root access. ```bash git clone https://github.com/github/choosealicense.com.git From 0575f3d094c97055b8ed03302b5f046e8672df14 Mon Sep 17 00:00:00 2001 From: Nick Schonning Date: Fri, 11 Sep 2020 16:51:31 -0400 Subject: [PATCH 68/70] chore: Use GitHub Actions for CI --- .github/workflows/test.yml | 22 ++++++++++++++++++++++ .travis.yml | 31 ------------------------------- README.md | 2 -- spec/ci_ruby_version_spec.rb | 4 ++-- 4 files changed, 24 insertions(+), 35 deletions(-) create mode 100644 .github/workflows/test.yml delete mode 100644 .travis.yml diff --git a/.github/workflows/test.yml b/.github/workflows/test.yml new file mode 100644 index 0000000..e28c56f --- /dev/null +++ b/.github/workflows/test.yml @@ -0,0 +1,22 @@ +name: Build and Test + +on: [push, pull_request] + +jobs: + test: + + runs-on: ubuntu-latest + + steps: + - uses: actions/checkout@v2 + + - name: Set up Ruby + uses: ruby/setup-ruby@v1 + with: + ruby-version: 2.7.1 + + - name: Install dependencies + run: ./script/bootstrap + + - name: Run tests + run: ./script/cibuild diff --git a/.travis.yml b/.travis.yml deleted file mode 100644 index 23e20cd..0000000 --- a/.travis.yml +++ /dev/null @@ -1,31 +0,0 @@ -#bootstrap and build -before_script: "./script/bootstrap" -script: "./script/cibuild" - -#environment -language: ruby -rvm: - - 2.7.1 - -addons: - apt: - packages: - - libcurl4-openssl-dev - -before_install: - - gem update --system - -branches: - only: - - gh-pages - - /.*/ - -notifications: - email: false - -env: - global: - - NOKOGIRI_USE_SYSTEM_LIBRARIES=true - -sudo: false -cache: bundler diff --git a/README.md b/README.md index 894937f..b5c2b51 100644 --- a/README.md +++ b/README.md @@ -1,7 +1,5 @@ **[ChooseALicense.com](https://choosealicense.com)** aims to provide **accurate**, **non-judgmental**, and **understandable** information about popular **open source licenses** in order to **help people make informed decisions** about the projects they start, maintain, contribute to, and use. -[![Build Status](https://travis-ci.org/github/choosealicense.com.svg?branch=gh-pages)](https://travis-ci.org/github/choosealicense.com) - We catalog [select](CONTRIBUTING.md#adding-a-license) open source licenses with a [Jekyll collection](https://jekyllrb.com/docs/collections/) (in `_licenses`). The catalog is used to render [ChooseALicense.com](https://choosealicense.com) and is regularly vendored into [Licensee](https://github.com/licensee/licensee), which GitHub uses to provide a [license chooser and license detection](https://help.github.com/articles/adding-a-license-to-a-repository/), a [licenses API](https://developer.github.com/v3/licenses/), and to [display license descriptions and metadata](https://github.com/blog/2335-open-source-license-descriptions-and-metadata). ## Goals diff --git a/spec/ci_ruby_version_spec.rb b/spec/ci_ruby_version_spec.rb index 6809848..472edce 100644 --- a/spec/ci_ruby_version_spec.rb +++ b/spec/ci_ruby_version_spec.rb @@ -9,9 +9,9 @@ describe 'ruby version' do pages_versions = JSON.parse(open('https://pages.github.com/versions.json').read) pages_ruby_version = pages_versions['ruby'] - ci_config_file = '.travis.yml' + ci_config_file = '.github/workflows/test.yml' ci_config = YAML.load_file(ci_config_file) - ci_ruby_version = ci_config['rvm'][0] + ci_ruby_version = ci_config['jobs']['test']['steps'][1]['with']['ruby-version'] context "in #{ci_config_file} and pages ruby version" do it 'match' do From 0e60553fe459d98a97f6e20b2a27867bdd5dead6 Mon Sep 17 00:00:00 2001 From: Mike Linksvayer Date: Sun, 13 Sep 2020 14:56:02 -0700 Subject: [PATCH 69/70] hopefully add actions badge --- README.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/README.md b/README.md index b5c2b51..eba0fd3 100644 --- a/README.md +++ b/README.md @@ -1,5 +1,7 @@ **[ChooseALicense.com](https://choosealicense.com)** aims to provide **accurate**, **non-judgmental**, and **understandable** information about popular **open source licenses** in order to **help people make informed decisions** about the projects they start, maintain, contribute to, and use. +[![](https://github.com/github/choosealicense.com/workflows/test/badge.svg)](https://github.com/github/choosealicense.com/actions?query=workflow%3Atest) + We catalog [select](CONTRIBUTING.md#adding-a-license) open source licenses with a [Jekyll collection](https://jekyllrb.com/docs/collections/) (in `_licenses`). The catalog is used to render [ChooseALicense.com](https://choosealicense.com) and is regularly vendored into [Licensee](https://github.com/licensee/licensee), which GitHub uses to provide a [license chooser and license detection](https://help.github.com/articles/adding-a-license-to-a-repository/), a [licenses API](https://developer.github.com/v3/licenses/), and to [display license descriptions and metadata](https://github.com/blog/2335-open-source-license-descriptions-and-metadata). ## Goals From 085ed47c95739c72b6f0ae5efd36c4472cf20955 Mon Sep 17 00:00:00 2001 From: Mike Linksvayer Date: Sun, 13 Sep 2020 15:08:14 -0700 Subject: [PATCH 70/70] correct name of action for actions badge --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index eba0fd3..841d9d6 100644 --- a/README.md +++ b/README.md @@ -1,6 +1,6 @@ **[ChooseALicense.com](https://choosealicense.com)** aims to provide **accurate**, **non-judgmental**, and **understandable** information about popular **open source licenses** in order to **help people make informed decisions** about the projects they start, maintain, contribute to, and use. -[![](https://github.com/github/choosealicense.com/workflows/test/badge.svg)](https://github.com/github/choosealicense.com/actions?query=workflow%3Atest) +[![](https://github.com/github/choosealicense.com/workflows/Build%20and%20Test/badge.svg)](https://github.com/github/choosealicense.com/actions?query=workflow%3ABuild%20and%20Test) We catalog [select](CONTRIBUTING.md#adding-a-license) open source licenses with a [Jekyll collection](https://jekyllrb.com/docs/collections/) (in `_licenses`). The catalog is used to render [ChooseALicense.com](https://choosealicense.com) and is regularly vendored into [Licensee](https://github.com/licensee/licensee), which GitHub uses to provide a [license chooser and license detection](https://help.github.com/articles/adding-a-license-to-a-repository/), a [licenses API](https://developer.github.com/v3/licenses/), and to [display license descriptions and metadata](https://github.com/blog/2335-open-source-license-descriptions-and-metadata).