Layers Relicensing from Apache-2.0 to MIT

Type
Restructuring
State
Ongoing
End Date of the Review Period

Reviews run for a minimum of one week. The outcome of the review is decided on this date. This is the last day to make comments or ask questions about this review.

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.

More information is available here.