For me, high quality lib is:

  * works as stated
  * does the job
  * issues are addressed promptly



What I don't care about in this lib:

  * how code is formatted
  * is code documented
  * does it have tests



How do I find is it good library?

  * I try it
  * I find references from other users



**References from other users are most valuable to me.**

People who use libs should be the judges.

When you put numbers to quality attributes people will compare them. In this 
case **quality** is measure of how lib **conforms to some standard**. It is not 
**quality** in sense how well it **solves problem**.

To me it implies that you know what library does, what business problem it 
solves and how well it works.

Suggestion:

  * don't use numbers
  * don't use word _quality_ , be precise with meaning
  * add fields _popularity, recommended_


Reply via email to