The Oniro repository changed license of all Yocto/OE build system meta-data/files/patches from Apache to MIT to make collaboration with the upstream easier: eclipse/oniro-core/oniro#824 (closed)
Relicense all files in this repository to MIT to align with Oniro core.
Due to how these Yocto/OE layers interact with upstream layers (including oe-core), having parts of our layers licensed under Apache when most (if not all) of our upstream dependencies (and generally the entire ecosystem) are MIT, would pose a couple of issues:
- Using our layers would introduce a new license to a downstream consumer that needs to be assessed.
- Reusing parts of our code would pose an issue of relicensing on Oniro or the downstream side.
- Upstreaming Apache code would need relicensing on the Oniro side before upstream could accept contributions (unless upstream is up for a license addition which in most cases is not an option).
- Mistakes can happen and end up with "silent" relicensing in different situations.
To avoid all the above we propose to change all the existing Yocto/OE Apache-2.0 files in this repository to MIT.
Fixes: #5 (closed)
Make the repository REUSE 3.0 compliant
- making the repository REUSE compliant adding SPDX headers to files that have no copyright and licensing information
- Remove unused Apache-2.0 license
# SUMMARY * Bad licenses: * Deprecated licenses: * Licenses without file extension: * Missing licenses: * Unused licenses: * Used licenses: CC-BY-4.0, MIT * Read errors: 0 * Files with copyright information: 12 / 12 * Files with license information: 12 / 12 Congratulations! Your project is compliant with version 3.0 of the REUSE Specification :-)
Signed-off-by: Francesco Pham email@example.com