01-11-2020, 08:41 AM
@CuriousTommy, after looking into this a little deeper I revise my opinion on LVFS, I have a tendency to resist change unless clear arguments are made for it. I have a few recommendations for you which are given in a spirit of collaboration first.
If you are to evangelize LVFS successfully, two points you should be able to discuss fluently are one, why does it make sense to introduce a middleman in the firmware update process, and two, what security measures and/or technologies are used throughout the process to ensure that the end user is installing the same firmware the OEM (original equipment manufacturer) intends. Richard Hughes has missed an opportunity to evangelize his own work, by not clearly documenting the second point on his website (although his blog shows he is still working out issues related to security).
Next, developers are probably not the best recipient of this message as they may not have the authority to speak for or make those decisions for the OEM. The decision to adopt LVFS would rest with the project founder @tllim or those he has delegated authority/responsibility to.
@danielt makes the case that system firmware is not ready for LVFS, and I agree on that point. I also agree with him that the keyboard/trackpad device firmware IS a good candidate for LVFS. It is clear by observing the posts in the forums (keyboard/trackpad firmware) that some in the community require a simpler approach to updating firmware.
If you are to evangelize LVFS successfully, two points you should be able to discuss fluently are one, why does it make sense to introduce a middleman in the firmware update process, and two, what security measures and/or technologies are used throughout the process to ensure that the end user is installing the same firmware the OEM (original equipment manufacturer) intends. Richard Hughes has missed an opportunity to evangelize his own work, by not clearly documenting the second point on his website (although his blog shows he is still working out issues related to security).
Next, developers are probably not the best recipient of this message as they may not have the authority to speak for or make those decisions for the OEM. The decision to adopt LVFS would rest with the project founder @tllim or those he has delegated authority/responsibility to.
@danielt makes the case that system firmware is not ready for LVFS, and I agree on that point. I also agree with him that the keyboard/trackpad device firmware IS a good candidate for LVFS. It is clear by observing the posts in the forums (keyboard/trackpad firmware) that some in the community require a simpler approach to updating firmware.