>"hobby" and "safety critical" don't often go together. if you just >want to improve your skills i say go for it but aiming for safety >critical is a high bar to achieve.
I like to keep bar high. >But if you're really looking to do safety critical, which industry are >you going to target? Medical and automotive. Medical mostly but automotive industry software needs are growing rapidly. Standards you mention are familiar to me. OpenBSD is kind of very useful research project so it is best to deploy QA practices that applies many industries. Goal to me is to make platform/components ready so that they could be used as a basis. Of course if anyone want's to use OpenBSD code in safety critical applications, it needs to be certified and still need work but.. I think it would be awesome if I can raise bar of open source components to that level. >Patches addressing bugs >found through static analysis are always welcome. Is there any centralized static analysis in OpenBSD QA process? Right way is to put effort there. >These are listed on the interwebs: >http://www.openbsd.org/goals.html I also find these: http://www.openbsd.org/faq/faq1.html#HowAbout http://www.openbsd.org/policy.html Honestly, goals.html describe current state of project. It doesn't describe long term goals/roadmap what developers are interested to do. I understand that every one has personal aims but I'm looking something like list of: "we must get rid of or rewrite this peace of crap in next/following cycle". FAQ says also something about installation boot media and it is not clear to me what are "OpenBSB project specifications". I'm looking all defined requirements for OpenBSD code and features. I assume that contributions are accepted, not only some bug patches but it make things easier (for new developers and users) if the mindset is defined. It should also define priority what is more important. Examples: -Is license purity more important than following standards? -What are standards to follow (even partially) and what are not? -Preferred targets. Embedded hardware and security applications, but what else? -"Hey, I like to create GUI application, what is the preferred API?" I think that programming should be mandatory in elementary school because it force to describe what you wan't without ambiguity. For this reason, I know this is easy task developers to do. However, I can't do that task because I don't know the OpenBSD developers mindset and I don't know yet is this the right community. I'm interested to put effort in controlled manner and help to remove ambiquity. I'm still probing this community.
