[trustable-software] From security to safety, or the other way around?

[Gerald Harris]

Thank you for this statement, I agree from the bottom of my heart. This is a point which in many respects is similar to Paul’s statements in the original invitation to discussion. There he compared open source and closed source software, asking which is more likely to be trustworthy. Here we have a standard which is “closed source” unless you are willing to pay the entrance fee. How is a key contribution to safety (or security) expected to engender trust if it remains hidden?

> I think the primary (non-technical) problem with MISRA is that it is a proprietary document, and that it is developed by a rather closed process.  An international standards body such as the ISO/IEC C Standards Committee is likely the best place to perform this work as it will be developed following a formal but open process that doesn't allow one individual or organization undue influence over the resulting product.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 842 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <https://lists.veristac.io/pipermail/trustable-software/attachments/20160928/16e8f58b/attachment.sig>