Linked by Thom Holwerda on Tue 6th May 2008 15:15 UTC, submitted by Shlomi Fish
Permalink for comment 313299
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/25/13 0:45 UTC
Linked by Thom Holwerda on 05/24/13 23:59 UTC
Linked by Thom Holwerda on 05/24/13 22:33 UTC
Linked by Howard Fosdick on 05/24/13 21:41 UTC
Linked by Thom Holwerda on 05/24/13 14:44 UTC
Linked by Thom Holwerda on 05/23/13 23:22 UTC
Linked by Thom Holwerda on 05/23/13 22:04 UTC
Linked by Thom Holwerda on 05/23/13 22:01 UTC
Linked by Thom Holwerda on 05/23/13 17:52 UTC
Linked by Thom Holwerda on 05/22/13 22:23 UTC
More News »
Sponsored Links



Member since:
2005-07-08
Don't be so hard on the author just because he may not provide the ultimate most comprehensive list of requirements for every kind of quality software project out there... The article has many good points, too often forgotten and worth keeping in mind: like when it mentions good social engineering skills.
There's more to good open source software than just good quality open-source code. Social problems have caused many otherwise promising (open source) software projects to go astray.
The article is not trying to compete with a something like the ISO standard mentioned above: http://en.wikipedia.org/wiki/ISO_9126 It complements such a well-known but mostly only technical, code-related list of requirements by offering some extra points of view.