acassis commented on PR #3362: URL: https://github.com/apache/nuttx-apps/pull/3362#issuecomment-3780672305
> @acassis I don't see any point in including license information in the firmware. The firmware doesn't care about licence. It's the user's responsibility to properly manage licenses and complete all licensing formal requirements. The licenses used by firmware should be easily accessible from the configuration, and that's how it is now. Licensing options are disabled by defaul so the user must consciously enable non-apach license and they always appear in defconfig. True, but in this case we need to do our best to guarantee: 1) all licensed file (other than Apache 2.0) are behind a CONFIG_ALLOW_XXXXXX_COMPONENTS; 2) none defconfig submitted to mainline automatically include/set a CONFIG_ALLOW_XXXXXX_COMPONENTS (today WiFi, Bluetooth, etc, depends on it); and/or 3) After the firmware image is generated we issue a warning saying License X, Y, Z is enable. We need to make things explicit to user, because the assumption that licenses are disabled by default is not true because it comes from defconfig and user users/companies never pay attention. Remember the case of the drone company that released a PX4 firmware with memory display commands in the firmware? They never paid attention about these commands present in the nsh> until a user used that command to dump their entire proprietary firmware. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
