Difference between revisions of "Bugs"

From GMOD
Jump to: navigation, search
 
Line 9: Line 9:
 
:: -- [http://www.red-bean.com/kfogel/ Karl Fogel], [http://producingoss.com/ How to Run a Successful Free Software Project].
 
:: -- [http://www.red-bean.com/kfogel/ Karl Fogel], [http://producingoss.com/ How to Run a Successful Free Software Project].
  
[[Category:GMOD developers]]
+
[[Category:GMOD Developers]]

Latest revision as of 14:03, 27 March 2011

The more bugs, the better the project! [1]



The importance of a bug tracking system lies not only in its usefulness to developers, but in what it signifies for project observers. For many people, an accessible bug database is one of the strongest signs that a project should be taken seriously. Furthermore, the higher the number of bugs in the database, the better the project looks. This might seem counterintuitive, but remember that the number of bugs recorded really depends on three things: the absolute number of bugs present in the software, the number of users using the software, and the convenience with which those users can register new bugs. Of these three factors, the latter two are more significant than the first. Any software of sufficient size and complexity has an essentially arbitrary number of bugs waiting to be discovered. The real question is, how well will the project do at recording and prioritizing those bugs? A project with a large and well-maintained bug database (meaning bugs are responded to promptly, duplicate bugs are unified, etc.) therefore makes a better impression than a project with no bug database, or a nearly empty database.
-- Karl Fogel, How to Run a Successful Free Software Project.