We want MIT license in yocto meta layers, therefore we need to switch from Apache-2.0 to MIT license, including SPDX headers
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
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:
To avoid all the above we propose to change all the existing Yocto/OE Apache-2.0 files in this repository to MIT.
Signed-off-by: Francesco Pham francesco.pham@huawei.com
We want MIT license in yocto meta layers, therefore we need to switch from Apache-2.0 to MIT license, including SPDX headers
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
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:
To avoid all the above we propose to change all the existing Yocto/OE Apache-2.0 files in this repository to MIT.
Signed-off-by: Francesco Pham francesco.pham@huawei.com
Stefan Schmidt (059356a3) at 21 Dec 14:05
Make the repository REUSE 3.0 compliant
... and 1 more commit
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
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:
To avoid all the above we propose to change all the existing Yocto/OE Apache-2.0 files in this repository to MIT.
Fixes: #4
making the repository REUSE compliant adding SPDX headers to files that have no copyright and licensing information
# 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: 11 / 11
* Files with license information: 11 / 11
Congratulations! Your project is compliant with version 3.0 of the REUSE Specification :-)
Signed-off-by: Francesco Pham francesco.pham@huawei.com
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
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:
To avoid all the above we propose to change all the existing Yocto/OE Apache-2.0 files in this repository to MIT.
Fixes: #4
making the repository REUSE compliant adding SPDX headers to files that have no copyright and licensing information
# 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: 11 / 11
* Files with license information: 11 / 11
Congratulations! Your project is compliant with version 3.0 of the REUSE Specification :-)
Signed-off-by: Francesco Pham francesco.pham@huawei.com
All authors of this repository have agreed to the re-license. Once we have a restructure review done for oniro-blueprints on this matter we are ready to merge the already prepared MR.
I received the +1 agreement for the license change from Bartosz Golaszewski via e-email. See below for reference:
From: Bartosz Golaszewski [mailto:brgl@bgdev.pl]
Sent: Friday, December 16, 2022 9:57 PM
To: Stefan Schmidt <stefan.schmidt@huawei.com>
Subject: Re: Agreement to MIT license change for Oniro Blueprint yocto layers
Ah, sorry, I was certain I did it. Yeah, +1 go ahead
+1 (I agree to the MIT relicensing)
+1 (I agree to the MIT relicensing)
Also let me grant re-licensing for other changes from me related to Oniro project as long as new license is a SPDX approved license
+1 (I agree to the MIT relicensing)
Please add the following:
+1 (I agree to the MIT relicensing)
Repo authors:
[stefan@localhost meta-oniro-blueprints-cats]$ git shortlog -nse
6 Philippe Coval <rzr@users.sf.net>
3 Bartosz Golaszewski <brgl@bgdev.pl>
3 Francesco Pham <francesco.pham@huawei.com>
1 Bartosz Golaszewski <bartosz.golaszewski@huawei.com>
1 Luca Seritan <luca.seritan@huawei.com>
1 Philippe Coval <philippe.coval.ext@huawei.com>
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
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:
To avoid all the above we propose to change all the existing Yocto/OE Apache-2.0 files in this repository to MIT.
Fixes: #4
making the repository REUSE compliant adding SPDX headers to files that have no copyright and licensing information
# 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: 11 / 11
* Files with license information: 11 / 11
Congratulations! Your project is compliant with version 3.0 of the REUSE Specification :-)
Signed-off-by: Francesco Pham francesco.pham@huawei.com
After this MR is merged: context-aware-touch-screen!5
we need to bump CATS to latest revision and switch the recipe license to Apache-2.0
Stefan Schmidt (a57fb1ce) at 29 Nov 15:34
cats: bump to latest version, switch license to Apache-2.0
Relate-to: #3
Signed-off-by: Francesco Pham francesco.pham@huawei.com
Relate-to: #3
Signed-off-by: Francesco Pham francesco.pham@huawei.com
Relate-to: #3
Signed-off-by: Francesco Pham francesco.pham@huawei.com
Stefan Schmidt (59ba9d77) at 22 Nov 18:43
assets: license graphical assets under CC-BY-4.0
... and 2 more commits