Tracking Issue for Relicensing Effort

This issue tracks all the separate tasks/issues involved in the relicensing effort. This issue was created separate from #18 as strictly speaking it's a subissue of issue #18.

Below is the status of all tasks involved in the relicensing effort:

• Source Analysis
  • Upstream Analysis
  • Alternate Source Analysis
  • Moved/Split Sources Identification
  • Original Sources Identification
  • Contributor/Contributions Identification
• Source Reconstruction
  • Upstream Reconstruction
  • Alternate Sources Reconstruction
  • Apply Trivial Code Transformations
• Individual Contributor Relicensing: Complete
  • #75
  • #77
  • #78
  • #79
  • #80
  • #81
  • #82
  • #83
• BES Relicensing: In Progress
  • Prepare minimal patchset of BES changes.
  • Prepare formal relicensing request.
    • #91
    • #92
    • #93
    • #94
  • Submit relicensing request to BES.
  • Ask BES about BT/BLE IP available in OneDeuxTriSeiGo/device_soc_bestechnic:OpenHarmony-3.0-LTS
• Relicensing Pull Request
  • Formalize OPB-Source-Available license.
  • add LICENSES/ directory with all licenses included.
  • add accurate license declarations in each file.
  • add copyright attributions to each file, by contributor with DCO.
  • add reuse infrastructure.
• (moonshot) Identify path towards achieving full OpenChain ISO/IEC 5230 compliance.

Start by reviewing the completed source-analysis and source-reconstruction links, then check the remaining tasks in #92, #93, and #94. The effort is done when the BES relicensing request is submitted, the OPB-Source-Available license and LICENSES/ directory are formalized, file attributions and declarations are added, and reuse infrastructure is in place.