-
Francesco Pham authored
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: https://gitlab.eclipse.org/eclipse/oniro-core/oniro/-/issues/824 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: https://gitlab.eclipse.org/eclipse/oniro-blueprints/transparent-gateway/meta-oniro-blueprints-gateway/-/issues/7 Signed-off-by: Francesco Pham <francesco.pham@huawei.com>
97f8e26e
After you've reviewed these contribution guidelines, you'll be all set to
contribute to this project.