|
1 | | -# Licensing status |
| 1 | +# Licence |
2 | 2 |
|
3 | | -**This project cannot be redistributed under an open-source licence yet. Please read |
4 | | -this before forking, packaging or publishing it.** |
| 3 | +This project is released under the **MIT Licence** — see [`LICENSE`](LICENSE). |
5 | 4 |
|
6 | | -## Why |
| 5 | +## Attribution |
7 | 6 |
|
8 | | -MG4 ABRP Telemetry is a fork of |
9 | | -[leonkernan/ABRP_Uploader](https://github.com/lkernan), written by Leon Kernan. |
| 7 | +MG4 ABRP Telemetry is a fork of Leon Kernan's `ABRP_Uploader`, and a meaningful part of |
| 8 | +the original work survives in it. The copyright line names both him and this fork's |
| 9 | +contributors, and MIT requires that notice to travel with any copy or substantial portion |
| 10 | +of the software. Keep it. |
10 | 11 |
|
11 | | -**The upstream repository never contained a licence file.** Under the Berne Convention, |
12 | | -code published without a licence is *all rights reserved* by default: the author holds |
13 | | -copyright and grants no permission to copy, modify or redistribute. GitHub's terms allow |
14 | | -forking within GitHub, but they do not grant redistribution rights beyond that. |
15 | | - |
16 | | -A meaningful part of this repository is still Leon Kernan's original work, so the project |
17 | | -as a whole cannot simply be relicensed by us. |
18 | | - |
19 | | -## What this means in practice |
20 | | - |
21 | | -| | Status | |
22 | | -|---|---| |
23 | | -| Using the app on your own car | Fine | |
24 | | -| Forking on GitHub, reading, learning from the code | Fine (GitHub ToS) | |
25 | | -| Redistributing APKs or source outside GitHub | **Needs Leon Kernan's permission** | |
26 | | -| Relicensing the whole project under MIT/Apache/GPL | **Needs Leon Kernan's permission** | |
| 12 | +The upstream repository carried no licence file of its own. Applying MIT here is the |
| 13 | +project owner's decision; if Leon Kernan ever objects, the right response is to honour |
| 14 | +that rather than argue about it. |
27 | 15 |
|
28 | 16 | ## No warranty |
29 | 17 |
|
30 | | -Separately from the licensing question above, this software carries **no warranty and no |
31 | | -liability** — see [`DISCLAIMER.md`](DISCLAIMER.md). Resolving the licence would not change |
32 | | -that. |
33 | | - |
34 | | -## Contributions made in this fork |
35 | | - |
36 | | -Everything authored in this fork — the telemetry correctness work, credential handling, |
37 | | -the vehicle-data layer changes, the cadence and UI work, the build and CI tooling — is |
38 | | -offered by its authors under the **MIT Licence**, on the condition that the upstream |
39 | | -portion is resolved. That offer alone is not enough to make the combined work |
40 | | -redistributable. |
41 | | - |
42 | | -## How to resolve this |
43 | | - |
44 | | -1. Contact Leon Kernan and ask him to add a licence upstream (MIT is the obvious fit and |
45 | | - matches the sibling MG4Control project), or to grant this fork an explicit licence. |
46 | | -2. Record the outcome here, replacing this file with the agreed licence text. |
47 | | -3. If he declines or cannot be reached, the alternative is to rewrite the remaining |
48 | | - original code so that no upstream-copyrighted material is left, and document that. |
49 | | - |
50 | | -Until then this file stays as it is. Publishing an MIT `LICENSE` over code we do not hold |
51 | | -the rights to would be worse than having no licence at all — it would tell users they have |
52 | | -permissions that nobody actually granted them. |
| 18 | +MIT disclaims all warranty and liability, and this software runs on a **vehicle** — see |
| 19 | +[`DISCLAIMER.md`](DISCLAIMER.md) for what that means concretely. |
0 commit comments