{"id":1340,"date":"2006-01-18T14:37:17","date_gmt":"2006-01-18T12:37:17","guid":{"rendered":"http:\/\/vizZzion.org\/blog\/2006\/01\/assessing-quality-of-open-source-software\/"},"modified":"2006-01-18T14:37:17","modified_gmt":"2006-01-18T12:37:17","slug":"assessing-quality-of-open-source-software","status":"publish","type":"post","link":"https:\/\/vizZzion.org\/blog\/2006\/01\/assessing-quality-of-open-source-software\/","title":{"rendered":"assessing quality of open source software."},"content":{"rendered":"<p>\n\t\tIn my non-KDE life, I&#8217;m <a href=\"http:\/\/vizzzion.org\/?id=work\">working<\/a> on quality<br \/>\nmetrics for Open Source software, to be more precise, on the criteria for a standard for quality<br \/>\ncertification of Independent Software Vendors (ISVs). I&#8217;m talking a lot to different people about<br \/>\nsuch kind of new stuff, and generally people, especially from the &#8220;business world&#8221; like the idea<br \/>\nvery much. ISVs are missing a certification that offers them the opportunity make a difference,<br \/>\ncustomers like the idea of being able to base their choice on hard criteria. My personal opinion is<br \/>\nthat such a certificate is needed to show decision makers that Open Source can score very well in<br \/>\nthe real world, that quality of Open Source products is not only good, but that it can be measured.\n\t<\/p>\n<p>\n\t\tBut how would you measure the quality of Open Source products from the point of view of a<br \/>\ncustomer? Quite often, you see that the time it takes &#8220;the community&#8221; to fix a certain bug is<br \/>\nmeasured. Well, that&#8217;s a beginning, but it&#8217;s definitely quite unusable as the only measurement for<br \/>\nthe maintainance level of some software component. You have to put that in relation to the severity<br \/>\nof the bug, to the &#8220;risc level&#8221;. I think Open Source quality has to offer quite some more with<br \/>\nrespect to quality, and some characteristics of Open Source software make quality assessment a fair<br \/>\nbit easier. You don&#8217;t need to sign NDAs to be able to review code and to do for example static<br \/>\nchecking of the source base. You can have a look at the development process, you&#8217;re able to test the<br \/>\nsoftware without the need to think about license questions, you&#8217;re able to look at history and you<br \/>\nmight even take advantage of assessment that has earlier been made Hack, most Open Source components<br \/>\neven publish their bug database. So what more do you want?<br \/>\n\t\t<b>A lot!<\/b><br \/>Fact is that a lot of Open Source project rely on peer-review as the only<br \/>\nmeans to improve and maintain good quality. While that certainly works for quite some projects, I<br \/>\nthink it&#8217;s about time to apply more methods to maintain and improve quality of Open Source software.\n\t<\/p>\n<p>\n\t\tIn the near future, I&#8217;m planning to blog more often on different aspects of software<br \/>\nquality, especially in the Open Source world, to raise the awareness within the community, and<br \/>\nsimply because it&#8217;s an interesting subject with a lot of different ways to approach it. So stay<br \/>\ntuned.\n\t<\/p>\n","protected":false},"excerpt":{"rendered":"<p>In my non-KDE life, I&#8217;m working on quality metrics for Open Source software, to be more precise, on the criteria for a standard for quality certification of Independent Software Vendors (ISVs). I&#8217;m talking a lot to different people about such kind of new stuff, and generally people, especially from the &#8220;business world&#8221; like the idea&hellip; <a class=\"more-link\" href=\"https:\/\/vizZzion.org\/blog\/2006\/01\/assessing-quality-of-open-source-software\/\">Continue reading <span class=\"screen-reader-text\">assessing quality of open source software.<\/span> <span class=\"meta-nav\" aria-hidden=\"true\">&rarr;<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[29],"tags":[],"class_list":["post-1340","post","type-post","status-publish","format-standard","hentry","category-kde"],"_links":{"self":[{"href":"https:\/\/vizZzion.org\/blog\/wp-json\/wp\/v2\/posts\/1340","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/vizZzion.org\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/vizZzion.org\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/vizZzion.org\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/vizZzion.org\/blog\/wp-json\/wp\/v2\/comments?post=1340"}],"version-history":[{"count":0,"href":"https:\/\/vizZzion.org\/blog\/wp-json\/wp\/v2\/posts\/1340\/revisions"}],"wp:attachment":[{"href":"https:\/\/vizZzion.org\/blog\/wp-json\/wp\/v2\/media?parent=1340"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/vizZzion.org\/blog\/wp-json\/wp\/v2\/categories?post=1340"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/vizZzion.org\/blog\/wp-json\/wp\/v2\/tags?post=1340"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}