Is it the case that Tizen:Common is intended ONLY to have OSI approved open source licensed content?
So, for example, Flora-licenses packages would not make the “sniff test” for Tizen:Common, where they are present in the current Mobile profile.
Is there any explicitly stated plan/policy for Tizen:Common’s licensing? Is it a fair analog to say that having non-OSI approved licenses in Tizen:Common would be tantemount to pushing non-OSI approved content into the Linux kernel – because Tizen:Common is so foundational to EVERY use of Tizen.
Tizen:Common licensing?
Is it the case that Tizen:Common is intended ONLY to have OSI approved open source licensed content?
So, for example, Flora-licenses packages would not make the “sniff test” for Tizen:Common, where they are present in the current Mobile profile.
Is there any explicitly stated plan/policy for Tizen:Common’s licensing? Is it a fair analog to say that having non-OSI approved licenses in Tizen:Common would be tantemount to pushing non-OSI approved content into the Linux kernel – because Tizen:Common is so foundational to EVERY use of Tizen.
Cheers,
Bob Summerwill
Kitsilano Software Inc
BY
16 Apr 2025
Tizen Studio
BY
04 Nov 2024
Tizen Studio
BY
02 Apr 2024
Tizen Studio