|
1 | 1 | # HitTheKit Licensing |
2 | 2 |
|
3 | | -HitTheKit is intended to be available under a dual-licensing model. |
4 | | - |
5 | | -This repository currently grants the Community license under version 3 of the |
6 | | -GNU General Public License. No project-specific "or any later version" grant |
7 | | -was found during the licensing audit, so the current grant is treated as |
8 | | -GPL-3.0-only. The complete, unmodified license text is in [`LICENSE`](LICENSE). |
| 3 | +HitTheKit uses a dual-licensing model. |
9 | 4 |
|
10 | 5 | ## Community license |
11 | 6 |
|
12 | | -The Community edition may be used, studied, modified, shared, and used |
13 | | -commercially under the GNU General Public License version 3, provided that the |
14 | | -applicable GPL obligations are respected. |
| 7 | +Unless a file or directory says otherwise, original HitTheKit source code is |
| 8 | +available under the [Mozilla Public License 2.0](LICENSE) (MPL-2.0). |
| 9 | +Third-party components, Unity packages, generated engine material, trademarks, |
| 10 | +and content retain their own terms; see |
| 11 | +[THIRD_PARTY_NOTICES.md](THIRD_PARTY_NOTICES.md), [NOTICE](NOTICE), and |
| 12 | +[TRADEMARKS.md](TRADEMARKS.md). |
| 13 | + |
| 14 | +The MPL permits personal, educational, community, and commercial use. When |
| 15 | +MPL-covered source files are modified and distributed, those covered files |
| 16 | +must remain available under the MPL. A larger work may contain separate files |
| 17 | +under other terms, provided the MPL requirements for covered files are met. |
| 18 | +The full license text controls; this overview does not replace it. |
| 19 | + |
| 20 | +## Unity players and other executable distributions |
15 | 21 |
|
16 | | -In particular, conveying modified or combined covered works may require |
17 | | -providing corresponding source code and licensing the covered work under the |
18 | | -GPL. Consult the full GPL text for the actual terms; this overview does not |
19 | | -replace it. |
| 22 | +MPL-2.0 permits covered HitTheKit code to be distributed in a larger executable |
| 23 | +under different terms while preserving recipients' rights to the MPL-covered |
| 24 | +source. This removes the former GPL whole-work copyleft concern for a player |
| 25 | +that incorporates the proprietary Unity Runtime. |
| 26 | + |
| 27 | +It does not itself approve a particular binary release. Every macOS or Windows |
| 28 | +candidate must still satisfy the applicable Unity terms, dependency notices, |
| 29 | +asset and content rights, signing requirements, platform testing, and the |
| 30 | +project release checklist. Unity and third-party technology are not relicensed |
| 31 | +by HitTheKit. |
20 | 32 |
|
21 | 33 | ## Commercial license |
22 | 34 |
|
23 | | -A separate commercial license may be available for organizations or |
24 | | -individuals that want to use HitTheKit under terms incompatible with the GPL, |
25 | | -including use within proprietary or closed-source products. Possible use cases |
26 | | -include: |
| 35 | +A separate commercial license may be available to organizations or individuals |
| 36 | +that need terms different from MPL-2.0, including: |
27 | 37 |
|
28 | | -- proprietary desktop or mobile applications; |
29 | | -- closed-source training platforms; |
30 | | -- commercial hardware integrations; |
31 | | -- bundled products; |
32 | | -- private-label or white-label distributions; and |
33 | | -- redistribution without GPL copyleft obligations for HitTheKit code. |
| 38 | +- keeping modifications to MPL-covered HitTheKit files proprietary; |
| 39 | +- proprietary hardware or software integrations; |
| 40 | +- bundled, private-label, or white-label distribution; or |
| 41 | +- separately negotiated support, warranty, or maintenance terms. |
34 | 42 |
|
35 | | -The commercial license is not automatically granted by this repository. |
36 | | -Commercial terms require a separate written agreement with a copyright holder |
37 | | -who has authority to license the relevant code. Such an agreement covers only |
38 | | -the rights that licensor controls; it does not replace licenses or commercial |
39 | | -terms for Unity or any other third-party component. |
| 43 | +The commercial license is not automatically granted and is not required merely |
| 44 | +because an activity generates revenue. It requires a separate written agreement |
| 45 | +with a copyright holder authorized to license the relevant code. It cannot |
| 46 | +replace Unity's terms or the licenses of third-party components. |
40 | 47 |
|
41 | | -## Personal, educational, and commercial use |
| 48 | +## Existing GPL copies |
42 | 49 |
|
43 | | -Personal, educational, and community use is welcome under the GPL Community |
44 | | -license. No commercial license is required merely because an activity |
45 | | -generates revenue, provided that the use and any distribution comply with the |
46 | | -GPL. |
| 50 | +Copies validly received under GPL-3.0-only before the MPL relicensing remain |
| 51 | +available to their recipients under GPL-3.0-only. The MPL change does not revoke |
| 52 | +rights already granted. A recipient must use the license offered for the exact |
| 53 | +copy or version they received. |
47 | 54 |
|
48 | 55 | ## Contributions |
49 | 56 |
|
50 | | -Contributions require separate governance rules so that the project can remain |
51 | | -eligible for dual licensing. See [`CONTRIBUTING.md`](CONTRIBUTING.md). |
| 57 | +Future contribution terms must preserve a clear rights chain for both the MPL |
| 58 | +Community edition and any separate commercial licensing. Until that mechanism |
| 59 | +has been reviewed and adopted, follow [CONTRIBUTING.md](CONTRIBUTING.md). |
52 | 60 |
|
53 | 61 | ## No trademark permission |
54 | 62 |
|
55 | | -The software license does not automatically grant permission to use the |
56 | | -HitTheKit name, logo, or branding to market a modified or competing product. |
57 | | -Trademark rights, if any, are separate from copyright licensing. See |
58 | | -[`TRADEMARKS.md`](TRADEMARKS.md). |
59 | | - |
60 | | -## Contact |
61 | | - |
62 | | -Commercial licensing inquiries: open a private inquiry with the copyright |
63 | | -holder. A dedicated contact address will be published later. |
| 63 | +MPL-2.0 does not grant permission to use the HitTheKit name, logo, or branding |
| 64 | +to market a modified or competing product. Truthful attribution remains |
| 65 | +permitted. See [TRADEMARKS.md](TRADEMARKS.md). |
64 | 66 |
|
65 | 67 | This document is a project licensing overview, not legal advice and not a |
66 | | -substitute for the full GPL text or a signed commercial agreement. |
| 68 | +substitute for the MPL text or a signed commercial agreement. |
0 commit comments