It's similar to e.g. shutdown criterion [1] where the "shutdown mechanism must correctly request a shutdown from the system firmware" or storage resize criterion [2] where "installer mechanism for resizing storage volumes must correctly attempt the requested operation".The important word in all these cases is "correctly". It implies that the software part, the calling part, must be implemented correctly. But because it deals with hardware and low level firmware and drivers, it admits that that part might not work correctly in all configurations. Which is then expanded in the next sentence.
Ok, your explanation shed some more light on it, so I guess I could go with that wording, too :D
_______________________________________________I simply got my inspiration from our other criteria when writing this one. It doesn't have to stay this way. But I think the "correctly attempt/request" wording is quite fitting here and it's not weak (at least not towards our software stack, which is the part which we can control reasonably well).
kde mailing list -- kde@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to kde-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/kde@xxxxxxxxxxxxxxxxxxxxxxx
--
Lukáš Růžička
FEDORA QE, RHCE
Purkyňova 115
612 45 Brno - Královo Pole
_______________________________________________ kde mailing list -- kde@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to kde-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/kde@xxxxxxxxxxxxxxxxxxxxxxx
