[U-Boot] SPDX header might be wrong in 4 files from Android Open Source Project
Hello,
SPDX-License-Identifier: BSD-3-Clause might be wrong in the following 4 files from Android Open Source Project (AOSP):
include/android_bootloader_message.h include/sparse_format.h include/dt_table.h include/android_image.h
As you can see in the comments the content is from AOSP.
But these files have Apache License, Version 2.0 in AOSP: https://android.googlesource.com/platform/bootable/recovery/+/master/bootloa... https://android.googlesource.com/platform/system/core/+/28fa5bc347390480fe19... https://android.googlesource.com/platform/system/libufdt/+/2626d8b9e4d8e8c6c... https://android.googlesource.com/platform/system/tools/mkbootimg/+/e55998a0f...
I am afraid, that there could be a license compatibility problem with creating one binary from both source files with GPL2-only license and source files with Apache 2 license.
Am I wrong? Is it possible to re-license from Apache 2 to BSD 3 license if there are only simple structs and defines in those files? With best regards, Zdenek Bouska
Siemens, s.r.o. Internet of Things Development Services IOT DS EU CZ AE Siemensova 1 155 00 Prague 13, Czech Republic
zdenek.bouska@siemens.commailto:zdenek.bouska@siemens.com
[cid:image003.png@01D5A3B2.56B02BF0]
Siemens, s.r.o. - CEO: Ing. Eduard Palíšek, Ph.D., MBA, CFO: Dipl.-Kfm. Michael Axmann - registered in the Commercial Register of the Municipal Court in Prague, Sec. C, File 625 Registered office: Siemensova 1, 155 00 Prague 13, Czech Republic IČ: 00268577, DIČ: CZ00268577, ID of data box: h6vchd6, Bank connection: UniCredit Bank Czech Republic and Slovakia, a.s., Želetavská 1525/1, 140 92 Prague 4, Czech Republic; Acc. Nr. CZK: 1013384001/2700, Acc. Nr. EUR: 1013384394/2700
Important Note: This message is only of informative nature. The content of this message shall not be binding for sender and sender does neither intend to conclude contract, accept offer or confirm the conclusion of the contract by this message nor this message represents pre-contractual liability of the sender, unless the sender states in the message excplicitly otherwise.
The content of this message (including appendices) shall be confidential. Should you are not intended receiver of this message, any access, copying, distribution or use of the content of this message is strictly prohibited and in such case, please immediately notify the sender and subsequently delete the entire message (including apppendices) from your system.
+ Alex Deymo
Hi Zdenek
On Mon, Nov 25, 2019 at 6:05 PM zdenek.bouska@siemens.com zdenek.bouska@siemens.com wrote:
Hello,
SPDX-License-Identifier: BSD-3-Clause might be wrong in the following 4 files from Android Open Source Project (AOSP):
include/android_bootloader_message.h include/sparse_format.h include/dt_table.h include/android_image.h
they were re-licensed by one of the Google employees specifically for U-boot [1].
As you can see in the comments the content is from AOSP.
But these files have Apache License, Version 2.0 in AOSP: https://android.googlesource.com/platform/bootable/recovery/+/master/bootloa... https://android.googlesource.com/platform/system/core/+/28fa5bc347390480fe19... https://android.googlesource.com/platform/system/libufdt/+/2626d8b9e4d8e8c6c... https://android.googlesource.com/platform/system/tools/mkbootimg/+/e55998a0f...
I am afraid, that there could be a license compatibility problem with creating one binary from both source files with GPL2-only license and source files with Apache 2 license.
Am I wrong? Is it possible to re-license from Apache 2 to BSD 3 license if there are only simple structs and defines in those files? With best regards, Zdenek Bouska
Siemens, s.r.o. Internet of Things Development Services IOT DS EU CZ AE Siemensova 1 155 00 Prague 13, Czech Republic
zdenek.bouska@siemens.commailto:zdenek.bouska@siemens.com
[cid:image003.png@01D5A3B2.56B02BF0]
Siemens, s.r.o. - CEO: Ing. Eduard Palíšek, Ph.D., MBA, CFO: Dipl.-Kfm. Michael Axmann - registered in the Commercial Register of the Municipal Court in Prague, Sec. C, File 625 Registered office: Siemensova 1, 155 00 Prague 13, Czech Republic IČ: 00268577, DIČ: CZ00268577, ID of data box: h6vchd6, Bank connection: UniCredit Bank Czech Republic and Slovakia, a.s., Želetavská 1525/1, 140 92 Prague 4, Czech Republic; Acc. Nr. CZK: 1013384001/2700, Acc. Nr. EUR: 1013384394/2700
Important Note: This message is only of informative nature. The content of this message shall not be binding for sender and sender does neither intend to conclude contract, accept offer or confirm the conclusion of the contract by this message nor this message represents pre-contractual liability of the sender, unless the sender states in the message excplicitly otherwise.
The content of this message (including appendices) shall be confidential. Should you are not intended receiver of this message, any access, copying, distribution or use of the content of this message is strictly prohibited and in such case, please immediately notify the sender and subsequently delete the entire message (including apppendices) from your system. _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de https://lists.denx.de/listinfo/u-boot
[1] https://patchwork.ozlabs.org/patch/1099689/
Le lun. 25 nov. 2019 à 17:20, Igor Opaniuk igor.opaniuk@gmail.com a écrit :
- Alex Deymo
Hi Zdenek
On Mon, Nov 25, 2019 at 6:05 PM zdenek.bouska@siemens.com zdenek.bouska@siemens.com wrote:
Hello,
SPDX-License-Identifier: BSD-3-Clause might be wrong in the following 4
files from Android Open Source Project (AOSP):
include/android_bootloader_message.h include/sparse_format.h include/dt_table.h include/android_image.h
they were re-licensed by one of the Google employees specifically for U-boot [1].
That's correct, I tried to make this re-licensing step explicit in the commit message. I sent the patches to add these headers re-licensed to BSD-3 after checking with our Opensource Releasing Team and they were OK with it in these particular cases. The original headers were Copyright "The Android Open Source Project".
If you need help importing other AOSP headers with BSD-3 license instead of the one we normally use in AOSP (Apache 2) I might be able to help with that, but I do need to check with the team first.
Best regards, deymo@
participants (3)
-
Alex Deymo -
Igor Opaniuk -
zdenek.bouska＠siemens.com