We ran into a legal problem because bts repo is under GPLv3 license. Legal affairs told us we can’t release it as a reference model with our open source toolchain product (under Apache 2.0 license) . GPL license mandate all products that used GPL code to compliance with GPL license. ( Even if only a small part of the product used GPL code)
So we suggest whether you could consider changing the license of BTS github repo. For example, Apache or MIT is more open and more convenient for other open source tools or products to quote and spread it.
Hi，
We ran into a legal problem because bts repo is under GPLv3 license. Legal affairs told us we can’t release it as a reference model with our open source toolchain product (under Apache 2.0 license) . GPL license mandate all products that used GPL code to compliance with GPL license. ( Even if only a small part of the product used GPL code)
So we suggest whether you could consider changing the license of BTS github repo. For example, Apache or MIT is more open and more convenient for other open source tools or products to quote and spread it.
Thanks！