Our open-source note says technology is no longer the moat in the AI era. That was never a waiver of the license.
@OpenMinis and ish-arm64 are the product of countless late nights. We have kept both open source and have consistently honored the licenses of the upstream projects we build on.
Some users recently shared analyses indicating that the @MeetHaloAI app bundles a build of ish-arm64, our terminal core released under GPLv2.
GPLv2 obligations attach on distribution, not on use. Distributing a binary that incorporates GPLv2 code requires providing the corresponding source, keeping the copyright and license notices, and licensing the derivative work under GPLv2.
We mean it when we say reuse is the point, and we're glad the work is useful. "No moat" is a strategy; the license is the terms of the contract. The two don't conflict.
@MeetHaloAI, we followed these terms for the code we built on, and we ask for the same respect. Could you share how you plan to meet the source-availability and notice requirements? We'd much rather see the work shared back with the community than see the license go unaddressed. 🙂