On Wed, 20 Mar 2002, Waldhoff, Rodney wrote: | Well said Andrew. | | Re. Chris's point, I think we'll be hard pressed to reach consensus on what | a project "maturity" means, let alone how to measure it. | | If I were building this document (and if I remember correctly, I built this | document: http://jakarta.apache.org/commons/components.html, which is rather | similiar in some respects), I'd stick to factual information--brief | description, release dates/numbers, etc. and let the facts speak for | themselves.
As those numbers are pretty different from project to project, I think that's not very "indicative" (?). # downloads is _interesting_, but of course it doesn't say very much. But it _is_ interesting and does actually say something about the combination of usability (audience) * maturity. Regarding Ted's comments about large user base being bad: that's just to weird. A large user base WILL make a product better. The worst thing that can happen to a product is that the developers sits inside their tech-box and just develops "cool shit". The _usability_ of the product must always be in front. And there you have the users. And the users of these products most often being developers themselves will give the product more development, guaranteed. There _are_ itches that's just so annoying that even I will try to fix them... -- Mvh, Endre -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
