Linked by Thom Holwerda on Tue 6th May 2008 15:15 UTC, submitted by Shlomi Fish
Features, Office "Which parameters make software applications high-quality? And which parameters or methods, while desirable, are not directly 'quality'?" This is the question the author of this article asks himself. Most of his 'parameters' make a lot of sense, but be aware that the article is about what makes an open source program high quality, and not programs in general. This important bit is stated in the one-sentence 'abstract'.
Permalink for comment 313225
To read all comments associated with this story, please click here.
RE: "The Source is Available..."
by ShlomiFish on Wed 7th May 2008 09:03 UTC in reply to ""The Source is Available...""
ShlomiFish
Member since:
2005-10-10

Hi chris_dk!

Sure, the availability source by itself does not guarantee the software is high-quality. And a lot of high-quality software is binary only or even proprietary.

What I meant to say is that availability of the source and the more liberal its licence is, contribute to the quality of the software. That's because the source allows improvement (enhancements, bug fixes, etc.), studying it to find out how to do things, integration into other FOSS software (including possibly GPL one), usage in "proprietary" contexts (if BSDL or LGPL, etc.), etc. etc.

While having a sub-optimal source licence, won't absolutely prevent your software from being high-quality, having a liberal one will increase the quality a lot.

As I noted below, what I've given are various parameters (or criteria) not a "Must have" checklist.

I hope I made myself clear.

Reply Parent Score: 0