temporary license
309e191 parent: eb9186a modified
.tickets/issues/0008-initialiser-le-projet-go-wails.yaml +45 -2 | @@ -6,7 +6,7 @@ author: | ||
| 6 | 6 | name: k33g |
| 7 | 7 | email: ph.charriere@gmail.com |
| 8 | 8 | createdAt: 2026-10-29T07:20:06.000Z |
| 9 | -updatedAt: 2026-10-29T07:20:06.000Z | |
| 9 | +updatedAt: 2026-10-29T08:10:00.000Z | |
| 10 | 10 | labels: |
| 11 | 11 | - "kind::chore" |
| 12 | 12 | - "area::infra" |
| @@ -34,6 +34,7 @@ body: | | ||
| 34 | 34 | ## Critères d'acceptation |
| 35 | 35 | - [ ] `wails dev` ouvre une fenêtre. |
| 36 | 36 | - [ ] `task test` et `task lint` passent sur un repo vierge. |
| 37 | + - [ ] Chaque fichier source porte l'en-tête de licence d'une ligne (vérifié par `task lint`). | |
| 37 | 38 | tasks: |
| 38 | 39 | - id: 1 |
| 39 | 40 | title: "Générer le projet Wails avec le template choisi" |
| @@ -83,4 +84,46 @@ tasks: | ||
| 83 | 84 | name: k33g |
| 84 | 85 | email: ph.charriere@gmail.com |
| 85 | 86 | createdAt: 2026-10-29T07:20:06.000Z |
| 86 | -comments: [] | |
| 87 | + - id: 7 | |
| 88 | + title: "Ajouter l'en-tête de licence aux fichiers sources et aux templates" | |
| 89 | + state: open | |
| 90 | + priority: high | |
| 91 | + author: | |
| 92 | + name: k33g | |
| 93 | + email: ph.charriere@gmail.com | |
| 94 | + createdAt: 2026-10-29T08:00:00.000Z | |
| 95 | + - id: 8 | |
| 96 | + title: "Vérifier la présence de l'en-tête dans task lint" | |
| 97 | + state: open | |
| 98 | + priority: medium | |
| 99 | + author: | |
| 100 | + name: k33g | |
| 101 | + email: ph.charriere@gmail.com | |
| 102 | + createdAt: 2026-10-29T08:00:00.000Z | |
| 103 | +comments: | |
| 104 | + - id: 1 | |
| 105 | + author: | |
| 106 | + name: k33g | |
| 107 | + email: ph.charriere@gmail.com | |
| 108 | + createdAt: 2026-10-29T08:00:00.000Z | |
| 109 | + updatedAt: 2026-10-29T08:10:00.000Z | |
| 110 | + body: | | |
| 111 | + ## Convention : en-tête de licence | |
| 112 | + | |
| 113 | + Chaque fichier source écrit à la main commence par une ligne qui renvoie au fichier [LICENSE](LICENSE) : | |
| 114 | + | |
| 115 | + | Fichiers | En-tête | | |
| 116 | + | --- | --- | | |
| 117 | + | `.go`, `.ts`, `.js` | `// Copyright (c) 2026 Philippe Charrière — Sidekicks Source-Available License 1.0, see LICENSE` | | |
| 118 | + | `.sh`, `.yaml`, `Taskfile` | `# Copyright (c) 2026 Philippe Charrière — Sidekicks Source-Available License 1.0, see LICENSE` | | |
| 119 | + | `.css` | `/* Copyright (c) 2026 Philippe Charrière — Sidekicks Source-Available License 1.0, see LICENSE */` | | |
| 120 | + | `.html`, `.svelte`, `.vue` | `<!-- Copyright (c) 2026 Philippe Charrière — Sidekicks Source-Available License 1.0, see LICENSE -->` | | |
| 121 | + | |
| 122 | + **Pourquoi :** un fichier copié hors du dépôt garde la trace de son auteur et de sa licence. Cela renforce le §3.e de la licence, qui interdit de retirer les mentions de copyright. | |
| 123 | + | |
| 124 | + **Règles :** | |
| 125 | + - En Go, l'en-tête est séparé de `package` par une ligne vide, sinon `go doc` le prend pour la documentation du package. | |
| 126 | + - Les scripts gardent le shebang en première ligne ; l'en-tête vient juste après. | |
| 127 | + - Les fichiers générés (bindings `wailsjs/`, `go.sum`, lockfiles) et les fichiers de config tiers ne portent pas d'en-tête. | |
| 128 | + - Les scripts personnels à la racine (`git.sh`, `new.*.sh`, `tag-step.sh`) sont hors convention : ce sont des outils de l'auteur, pas du code du projet. | |
| 129 | + - L'année reste celle de la création du fichier. | |
| @@ -6,7 +6,7 @@ author: | |||
| 6 | name: k33g | 6 | name: k33g |
| 7 | email: ph.charriere@gmail.com | 7 | email: ph.charriere@gmail.com |
| 8 | createdAt: 2026-10-29T07:20:06.000Z | 8 | createdAt: 2026-10-29T07:20:06.000Z |
| 9 | -updatedAt: 2026-10-29T07:20:06.000Z | 9 | +updatedAt: 2026-10-29T08:10:00.000Z |
| 10 | labels: | 10 | labels: |
| 11 | - "kind::chore" | 11 | - "kind::chore" |
| 12 | - "area::infra" | 12 | - "area::infra" |
| @@ -34,6 +34,7 @@ body: | | |||
| 34 | ## Critères d'acceptation | 34 | ## Critères d'acceptation |
| 35 | - [ ] `wails dev` ouvre une fenêtre. | 35 | - [ ] `wails dev` ouvre une fenêtre. |
| 36 | - [ ] `task test` et `task lint` passent sur un repo vierge. | 36 | - [ ] `task test` et `task lint` passent sur un repo vierge. |
| 37 | + - [ ] Chaque fichier source porte l'en-tête de licence d'une ligne (vérifié par `task lint`). | ||
| 37 | tasks: | 38 | tasks: |
| 38 | - id: 1 | 39 | - id: 1 |
| 39 | title: "Générer le projet Wails avec le template choisi" | 40 | title: "Générer le projet Wails avec le template choisi" |
| @@ -83,4 +84,46 @@ tasks: | |||
| 83 | name: k33g | 84 | name: k33g |
| 84 | email: ph.charriere@gmail.com | 85 | email: ph.charriere@gmail.com |
| 85 | createdAt: 2026-10-29T07:20:06.000Z | 86 | createdAt: 2026-10-29T07:20:06.000Z |
| 86 | -comments: [] | 87 | + - id: 7 |
| 88 | + title: "Ajouter l'en-tête de licence aux fichiers sources et aux templates" | ||
| 89 | + state: open | ||
| 90 | + priority: high | ||
| 91 | + author: | ||
| 92 | + name: k33g | ||
| 93 | + email: ph.charriere@gmail.com | ||
| 94 | + createdAt: 2026-10-29T08:00:00.000Z | ||
| 95 | + - id: 8 | ||
| 96 | + title: "Vérifier la présence de l'en-tête dans task lint" | ||
| 97 | + state: open | ||
| 98 | + priority: medium | ||
| 99 | + author: | ||
| 100 | + name: k33g | ||
| 101 | + email: ph.charriere@gmail.com | ||
| 102 | + createdAt: 2026-10-29T08:00:00.000Z | ||
| 103 | +comments: | ||
| 104 | + - id: 1 | ||
| 105 | + author: | ||
| 106 | + name: k33g | ||
| 107 | + email: ph.charriere@gmail.com | ||
| 108 | + createdAt: 2026-10-29T08:00:00.000Z | ||
| 109 | + updatedAt: 2026-10-29T08:10:00.000Z | ||
| 110 | + body: | | ||
| 111 | + ## Convention : en-tête de licence | ||
| 112 | + | ||
| 113 | + Chaque fichier source écrit à la main commence par une ligne qui renvoie au fichier [LICENSE](LICENSE) : | ||
| 114 | + | ||
| 115 | + | Fichiers | En-tête | | ||
| 116 | + | --- | --- | | ||
| 117 | + | `.go`, `.ts`, `.js` | `// Copyright (c) 2026 Philippe Charrière — Sidekicks Source-Available License 1.0, see LICENSE` | | ||
| 118 | + | `.sh`, `.yaml`, `Taskfile` | `# Copyright (c) 2026 Philippe Charrière — Sidekicks Source-Available License 1.0, see LICENSE` | | ||
| 119 | + | `.css` | `/* Copyright (c) 2026 Philippe Charrière — Sidekicks Source-Available License 1.0, see LICENSE */` | | ||
| 120 | + | `.html`, `.svelte`, `.vue` | `<!-- Copyright (c) 2026 Philippe Charrière — Sidekicks Source-Available License 1.0, see LICENSE -->` | | ||
| 121 | + | ||
| 122 | + **Pourquoi :** un fichier copié hors du dépôt garde la trace de son auteur et de sa licence. Cela renforce le §3.e de la licence, qui interdit de retirer les mentions de copyright. | ||
| 123 | + | ||
| 124 | + **Règles :** | ||
| 125 | + - En Go, l'en-tête est séparé de `package` par une ligne vide, sinon `go doc` le prend pour la documentation du package. | ||
| 126 | + - Les scripts gardent le shebang en première ligne ; l'en-tête vient juste après. | ||
| 127 | + - Les fichiers générés (bindings `wailsjs/`, `go.sum`, lockfiles) et les fichiers de config tiers ne portent pas d'en-tête. | ||
| 128 | + - Les scripts personnels à la racine (`git.sh`, `new.*.sh`, `tag-step.sh`) sont hors convention : ce sont des outils de l'auteur, pas du code du projet. | ||
| 129 | + - L'année reste celle de la création du fichier. | ||
added
LICENSE +147 -0 | new file mode 100644 | ||
| @@ -0,0 +1,147 @@ | ||
| 1 | +Sidekicks Source-Available License, version 1.0 | |
| 2 | + | |
| 3 | +Copyright (c) 2026 Philippe Charrière <ph.charriere@gmail.com>. All rights reserved. | |
| 4 | + | |
| 5 | +This license lets you read the source code of Sidekicks, propose changes to | |
| 6 | +it, and use its compiled application for personal purposes and | |
| 7 | +demonstrations. Every other use, and every commercial use, requires a | |
| 8 | +separate written agreement with the Licensor. | |
| 9 | + | |
| 10 | + | |
| 11 | +1. Definitions | |
| 12 | + | |
| 13 | +"Licensor" means the copyright holder named above. | |
| 14 | + | |
| 15 | +"Software" means the Sidekicks project, including its Source Code, its | |
| 16 | +documentation, and any Binary built from it by the Licensor. | |
| 17 | + | |
| 18 | +"Source Code" means the human-readable files of the Software, as published | |
| 19 | +in the official repository designated by the Licensor. | |
| 20 | + | |
| 21 | +"Binary" means a compiled, packaged form of the Software (for example a | |
| 22 | +macOS application bundle) distributed by the Licensor. | |
| 23 | + | |
| 24 | +"Contribution" means any change, fix, idea, documentation or other material | |
| 25 | +that You submit to the Licensor for inclusion in the Software, by a pull or | |
| 26 | +merge request, a patch, an issue, or any other means. | |
| 27 | + | |
| 28 | +"Personal Use" means use by an individual for their own private, | |
| 29 | +non-commercial purposes, including personal projects, learning and | |
| 30 | +experimentation. | |
| 31 | + | |
| 32 | +"Demonstration" means showing the Binary in operation to an audience (for | |
| 33 | +example a talk, a workshop, a meetup, a video or a blog post), provided that | |
| 34 | +no fee is charged specifically for access to the Software itself. | |
| 35 | + | |
| 36 | +"Commercial Use" means any use intended for, or directed toward, commercial | |
| 37 | +advantage or monetary compensation, including use within or on behalf of a | |
| 38 | +company or other organisation, use to provide a service to third parties, | |
| 39 | +and selling, renting or bundling the Software. | |
| 40 | + | |
| 41 | +"You" means the individual or legal entity exercising rights under this | |
| 42 | +license. | |
| 43 | + | |
| 44 | + | |
| 45 | +2. What you may do | |
| 46 | + | |
| 47 | +Subject to the conditions of this license, the Licensor grants You a | |
| 48 | +non-exclusive, non-transferable, non-sublicensable, revocable, worldwide, | |
| 49 | +royalty-free license to: | |
| 50 | + | |
| 51 | + a. view, read and study the Source Code; | |
| 52 | + | |
| 53 | + b. copy and modify the Source Code solely to prepare Contributions and | |
| 54 | + submit them to the official repository, and build it solely to test | |
| 55 | + those Contributions; | |
| 56 | + | |
| 57 | + c. install and run the Binary for Personal Use and for Demonstrations. | |
| 58 | + | |
| 59 | + | |
| 60 | +3. What you may not do | |
| 61 | + | |
| 62 | +Except as expressly permitted in section 2, You may not: | |
| 63 | + | |
| 64 | + a. use, copy or incorporate all or any part of the Source Code into any | |
| 65 | + other software, project, library or product, whether open source, | |
| 66 | + proprietary or otherwise; | |
| 67 | + | |
| 68 | + b. distribute, publish, sell, rent, lease or sublicense the Software, the | |
| 69 | + Source Code, the Binary, or any modified version of them, other than | |
| 70 | + submitting Contributions to the official repository; | |
| 71 | + | |
| 72 | + c. make the Software available to third parties as a hosted or managed | |
| 73 | + service; | |
| 74 | + | |
| 75 | + d. make any Commercial Use of the Software; | |
| 76 | + | |
| 77 | + e. remove, alter or obscure any copyright notice, license notice or | |
| 78 | + attribution in the Software. | |
| 79 | + | |
| 80 | +Forks hosted on public code-hosting platforms are tolerated only to the | |
| 81 | +extent necessary to prepare Contributions, and must keep this license | |
| 82 | +unchanged. | |
| 83 | + | |
| 84 | + | |
| 85 | +4. Commercial use | |
| 86 | + | |
| 87 | +Any Commercial Use, and any use not expressly permitted by section 2, | |
| 88 | +requires a prior written agreement with the Licensor. To request one, | |
| 89 | +contact the Licensor at the address given above. | |
| 90 | + | |
| 91 | + | |
| 92 | +5. Contributions | |
| 93 | + | |
| 94 | +By submitting a Contribution, You: | |
| 95 | + | |
| 96 | + a. grant the Licensor a perpetual, irrevocable, worldwide, royalty-free, | |
| 97 | + non-exclusive license to use, reproduce, modify, distribute, sublicense | |
| 98 | + and relicense the Contribution, as part of the Software or otherwise, | |
| 99 | + under any terms, including future licenses of the Software and | |
| 100 | + commercial agreements; | |
| 101 | + | |
| 102 | + b. confirm that You have the right to grant this license, and that the | |
| 103 | + Contribution is Your original work or that You have the authority to | |
| 104 | + submit it; | |
| 105 | + | |
| 106 | + c. understand that the Licensor is under no obligation to accept, use or | |
| 107 | + credit the Contribution. | |
| 108 | + | |
| 109 | + | |
| 110 | +6. Third-party components | |
| 111 | + | |
| 112 | +The Software uses third-party components that are licensed under their own | |
| 113 | +terms (for example open-source licenses). Those terms apply to those | |
| 114 | +components, and nothing in this license restricts the rights they grant. | |
| 115 | + | |
| 116 | + | |
| 117 | +7. Changes to this license | |
| 118 | + | |
| 119 | +The Licensor may publish future versions of the Software under different | |
| 120 | +license terms. Each copy of the Software is governed by the license that | |
| 121 | +accompanies it. A change of license does not grant additional rights over | |
| 122 | +copies obtained under this version. | |
| 123 | + | |
| 124 | + | |
| 125 | +8. Termination | |
| 126 | + | |
| 127 | +Your rights under this license end automatically if You breach any of its | |
| 128 | +terms. On termination, You must stop using the Software and destroy any | |
| 129 | +copies of the Source Code and of the Binary in Your possession. Sections 3, | |
| 130 | +5, 9 and 10 survive termination. | |
| 131 | + | |
| 132 | + | |
| 133 | +9. No warranty and limitation of liability | |
| 134 | + | |
| 135 | +THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR | |
| 136 | +IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, | |
| 137 | +FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT. TO THE MAXIMUM EXTENT | |
| 138 | +PERMITTED BY LAW, IN NO EVENT SHALL THE LICENSOR BE LIABLE FOR ANY CLAIM, | |
| 139 | +DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR | |
| 140 | +OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR ITS | |
| 141 | +USE. | |
| 142 | + | |
| 143 | + | |
| 144 | +10. Governing law | |
| 145 | + | |
| 146 | +This license is governed by French law. Any dispute relating to it falls | |
| 147 | +under the jurisdiction of the competent French courts. | |
| new file mode 100644 | |||
| @@ -0,0 +1,147 @@ | |||
| 1 | +Sidekicks Source-Available License, version 1.0 | ||
| 2 | + | ||
| 3 | +Copyright (c) 2026 Philippe Charrière <ph.charriere@gmail.com>. All rights reserved. | ||
| 4 | + | ||
| 5 | +This license lets you read the source code of Sidekicks, propose changes to | ||
| 6 | +it, and use its compiled application for personal purposes and | ||
| 7 | +demonstrations. Every other use, and every commercial use, requires a | ||
| 8 | +separate written agreement with the Licensor. | ||
| 9 | + | ||
| 10 | + | ||
| 11 | +1. Definitions | ||
| 12 | + | ||
| 13 | +"Licensor" means the copyright holder named above. | ||
| 14 | + | ||
| 15 | +"Software" means the Sidekicks project, including its Source Code, its | ||
| 16 | +documentation, and any Binary built from it by the Licensor. | ||
| 17 | + | ||
| 18 | +"Source Code" means the human-readable files of the Software, as published | ||
| 19 | +in the official repository designated by the Licensor. | ||
| 20 | + | ||
| 21 | +"Binary" means a compiled, packaged form of the Software (for example a | ||
| 22 | +macOS application bundle) distributed by the Licensor. | ||
| 23 | + | ||
| 24 | +"Contribution" means any change, fix, idea, documentation or other material | ||
| 25 | +that You submit to the Licensor for inclusion in the Software, by a pull or | ||
| 26 | +merge request, a patch, an issue, or any other means. | ||
| 27 | + | ||
| 28 | +"Personal Use" means use by an individual for their own private, | ||
| 29 | +non-commercial purposes, including personal projects, learning and | ||
| 30 | +experimentation. | ||
| 31 | + | ||
| 32 | +"Demonstration" means showing the Binary in operation to an audience (for | ||
| 33 | +example a talk, a workshop, a meetup, a video or a blog post), provided that | ||
| 34 | +no fee is charged specifically for access to the Software itself. | ||
| 35 | + | ||
| 36 | +"Commercial Use" means any use intended for, or directed toward, commercial | ||
| 37 | +advantage or monetary compensation, including use within or on behalf of a | ||
| 38 | +company or other organisation, use to provide a service to third parties, | ||
| 39 | +and selling, renting or bundling the Software. | ||
| 40 | + | ||
| 41 | +"You" means the individual or legal entity exercising rights under this | ||
| 42 | +license. | ||
| 43 | + | ||
| 44 | + | ||
| 45 | +2. What you may do | ||
| 46 | + | ||
| 47 | +Subject to the conditions of this license, the Licensor grants You a | ||
| 48 | +non-exclusive, non-transferable, non-sublicensable, revocable, worldwide, | ||
| 49 | +royalty-free license to: | ||
| 50 | + | ||
| 51 | + a. view, read and study the Source Code; | ||
| 52 | + | ||
| 53 | + b. copy and modify the Source Code solely to prepare Contributions and | ||
| 54 | + submit them to the official repository, and build it solely to test | ||
| 55 | + those Contributions; | ||
| 56 | + | ||
| 57 | + c. install and run the Binary for Personal Use and for Demonstrations. | ||
| 58 | + | ||
| 59 | + | ||
| 60 | +3. What you may not do | ||
| 61 | + | ||
| 62 | +Except as expressly permitted in section 2, You may not: | ||
| 63 | + | ||
| 64 | + a. use, copy or incorporate all or any part of the Source Code into any | ||
| 65 | + other software, project, library or product, whether open source, | ||
| 66 | + proprietary or otherwise; | ||
| 67 | + | ||
| 68 | + b. distribute, publish, sell, rent, lease or sublicense the Software, the | ||
| 69 | + Source Code, the Binary, or any modified version of them, other than | ||
| 70 | + submitting Contributions to the official repository; | ||
| 71 | + | ||
| 72 | + c. make the Software available to third parties as a hosted or managed | ||
| 73 | + service; | ||
| 74 | + | ||
| 75 | + d. make any Commercial Use of the Software; | ||
| 76 | + | ||
| 77 | + e. remove, alter or obscure any copyright notice, license notice or | ||
| 78 | + attribution in the Software. | ||
| 79 | + | ||
| 80 | +Forks hosted on public code-hosting platforms are tolerated only to the | ||
| 81 | +extent necessary to prepare Contributions, and must keep this license | ||
| 82 | +unchanged. | ||
| 83 | + | ||
| 84 | + | ||
| 85 | +4. Commercial use | ||
| 86 | + | ||
| 87 | +Any Commercial Use, and any use not expressly permitted by section 2, | ||
| 88 | +requires a prior written agreement with the Licensor. To request one, | ||
| 89 | +contact the Licensor at the address given above. | ||
| 90 | + | ||
| 91 | + | ||
| 92 | +5. Contributions | ||
| 93 | + | ||
| 94 | +By submitting a Contribution, You: | ||
| 95 | + | ||
| 96 | + a. grant the Licensor a perpetual, irrevocable, worldwide, royalty-free, | ||
| 97 | + non-exclusive license to use, reproduce, modify, distribute, sublicense | ||
| 98 | + and relicense the Contribution, as part of the Software or otherwise, | ||
| 99 | + under any terms, including future licenses of the Software and | ||
| 100 | + commercial agreements; | ||
| 101 | + | ||
| 102 | + b. confirm that You have the right to grant this license, and that the | ||
| 103 | + Contribution is Your original work or that You have the authority to | ||
| 104 | + submit it; | ||
| 105 | + | ||
| 106 | + c. understand that the Licensor is under no obligation to accept, use or | ||
| 107 | + credit the Contribution. | ||
| 108 | + | ||
| 109 | + | ||
| 110 | +6. Third-party components | ||
| 111 | + | ||
| 112 | +The Software uses third-party components that are licensed under their own | ||
| 113 | +terms (for example open-source licenses). Those terms apply to those | ||
| 114 | +components, and nothing in this license restricts the rights they grant. | ||
| 115 | + | ||
| 116 | + | ||
| 117 | +7. Changes to this license | ||
| 118 | + | ||
| 119 | +The Licensor may publish future versions of the Software under different | ||
| 120 | +license terms. Each copy of the Software is governed by the license that | ||
| 121 | +accompanies it. A change of license does not grant additional rights over | ||
| 122 | +copies obtained under this version. | ||
| 123 | + | ||
| 124 | + | ||
| 125 | +8. Termination | ||
| 126 | + | ||
| 127 | +Your rights under this license end automatically if You breach any of its | ||
| 128 | +terms. On termination, You must stop using the Software and destroy any | ||
| 129 | +copies of the Source Code and of the Binary in Your possession. Sections 3, | ||
| 130 | +5, 9 and 10 survive termination. | ||
| 131 | + | ||
| 132 | + | ||
| 133 | +9. No warranty and limitation of liability | ||
| 134 | + | ||
| 135 | +THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR | ||
| 136 | +IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, | ||
| 137 | +FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT. TO THE MAXIMUM EXTENT | ||
| 138 | +PERMITTED BY LAW, IN NO EVENT SHALL THE LICENSOR BE LIABLE FOR ANY CLAIM, | ||
| 139 | +DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR | ||
| 140 | +OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR ITS | ||
| 141 | +USE. | ||
| 142 | + | ||
| 143 | + | ||
| 144 | +10. Governing law | ||
| 145 | + | ||
| 146 | +This license is governed by French law. Any dispute relating to it falls | ||
| 147 | +under the jurisdiction of the competent French courts. | ||