From 391df128bea04cf799b50e7f1c236490f8898302 Mon Sep 17 00:00:00 2001 From: Derek Ross Date: Wed, 18 Nov 2026 15:39:55 -0500 Subject: [PATCH 1/2] CONTRIBUTING: a package built on GPL-3.0 sources keeps that licence, as a program of its own MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The tree already has GPL-3.0 packages (the apps, the keyboard layouts in omamobile-shell) and ยง7 named only Apache-2.0, 0BSD and patch series as exceptions. The line says what such a package carries and that none of it goes into the MIT tools and packages. Asked for by #888 (an on-screen keyboard built on Stevia). Co-Authored-By: Claude Fable 5.2 --- CONTRIBUTING.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index cf08a8271..a6a91af2b 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -347,7 +347,8 @@ The pull request template (`.github/pull_request_template.md`) has the checklist - **Exceptions keep their upstream licence:** - the port of Google's Apache-2.0 boot-control code keeps that licence and Google's notice ([`omamobile-bootctl.c`](packages/omamobile-device-cheetah/src/omamobile-bootctl.c), with `LICENSE.Apache-2.0` beside it); - PKGBUILDs derived from Arch's are 0BSD; - - patches to Mesa, Hyprland and Omarchy are under those projects' licences. + - patches to Mesa, Hyprland and Omarchy are under those projects' licences; + - a package built on GPL-3.0 sources is GPL-3.0 as a whole, like the apps (`omacam`, `omatel`, `omaphone`, `omamessages`) and the keyboard layouts in `omamobile-shell`. It is a program of its own in its own `packages//` folder: the PKGBUILD's `license=` says so, the licence text is beside it (`COPYING`), every upstream copyright and licence notice stays in the files and patches it came with, and its README names the upstream project and version. Nothing from it is copied into, or linked with, the MIT tools and packages; they may start it or talk to it as a separate program. - **Only use code from properly licensed sources.** Google's GPL kernel, upstream Linux, postmarketOS and Mesa are fine. Leaked or unlicensed code is not, and neither is decompiled proprietary code: describe protocols (as [USF-PROTOCOL.md](device/cheetah/USF-PROTOCOL.md) does), don't copy code. - **Google's proprietary firmware and binaries are never committed, attached or redistributed.** That covers Wi-Fi, Bluetooth, haptics, AoC and GNSS firmware, vendor HALs and libraries, calibration and tuning files. Our scripts take them from **the user's own factory image** on the user's own machine: - [`tools/extract-vendor-firmware`](tools/extract-vendor-firmware): firmware, renamed to what mainline drivers request; From 55b6e190a280a8ab28b83f66c2803ab1072e2b73 Mon Sep 17 00:00:00 2001 From: Derek Ross Date: Wed, 18 Nov 2026 15:40:14 -0500 Subject: [PATCH 2/2] CONTRIBUTING: the GPL-3.0 line covers a licence by choice as well as by derivation Co-Authored-By: Claude Fable 5.2 --- CONTRIBUTING.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index a6a91af2b..b41916f70 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -348,7 +348,7 @@ The pull request template (`.github/pull_request_template.md`) has the checklist - the port of Google's Apache-2.0 boot-control code keeps that licence and Google's notice ([`omamobile-bootctl.c`](packages/omamobile-device-cheetah/src/omamobile-bootctl.c), with `LICENSE.Apache-2.0` beside it); - PKGBUILDs derived from Arch's are 0BSD; - patches to Mesa, Hyprland and Omarchy are under those projects' licences; - - a package built on GPL-3.0 sources is GPL-3.0 as a whole, like the apps (`omacam`, `omatel`, `omaphone`, `omamessages`) and the keyboard layouts in `omamobile-shell`. It is a program of its own in its own `packages//` folder: the PKGBUILD's `license=` says so, the licence text is beside it (`COPYING`), every upstream copyright and licence notice stays in the files and patches it came with, and its README names the upstream project and version. Nothing from it is copied into, or linked with, the MIT tools and packages; they may start it or talk to it as a separate program. + - a package can be GPL-3.0 as a whole, because it is built on GPL-3.0 sources or because its author chose that licence, as the apps (`omacam`, `omatel`, `omaphone`, `omamessages`) and the keyboard layouts in `omamobile-shell` are. It is a program of its own in its own `packages//` folder: the PKGBUILD's `license=` says so, the licence text is beside it (`COPYING`), every upstream copyright and licence notice stays in the files and patches it came with, and its README names the upstream project and version. Nothing from it is copied into, or linked with, the MIT tools and packages; they may start it or talk to it as a separate program. - **Only use code from properly licensed sources.** Google's GPL kernel, upstream Linux, postmarketOS and Mesa are fine. Leaked or unlicensed code is not, and neither is decompiled proprietary code: describe protocols (as [USF-PROTOCOL.md](device/cheetah/USF-PROTOCOL.md) does), don't copy code. - **Google's proprietary firmware and binaries are never committed, attached or redistributed.** That covers Wi-Fi, Bluetooth, haptics, AoC and GNSS firmware, vendor HALs and libraries, calibration and tuning files. Our scripts take them from **the user's own factory image** on the user's own machine: - [`tools/extract-vendor-firmware`](tools/extract-vendor-firmware): firmware, renamed to what mainline drivers request;