On Mon, Oct 5, 2009 at 4:23 PM, Olemis Lang <olemis@gmail.com> wrote:
On Mon, Oct 5, 2009 at 4:06 PM, Fred Drake <fdrake@gmail.com> wrote:
On Mon, Oct 5, 2009 at 4:24 PM, Nick Coghlan <ncoghlan@gmail.com> wrote:
When it comes to comments and recommendations for selecting software packages, developers *are* the end users :)
Yes, most certainly. But developers as consumers are very different from application users as consumers, which is what I was getting at.
The convenience interfaces for commenting on a library are far less valuable for developers, IMO, since developers are expected to better understand how their context impacts their perception. Useful feedback from a developer just doesn't fit will into the giant-pile-of-comments UIs conventional for non-developers.
+1
IMO :
- decision matrix are useful to decide which lib to use (i.e. which one supports the features I need ;o). BTW that's something cool about wikipedia ;o)
I mean feature matrix
- project metrics and build results are useful to have a idea of project dev status (e.g. coverage, test results, ...). - the rest goes to issue tracker + project (sites | wikis). that's what they are for ;o)
-- Regards,
Olemis.
Blog ES: http://simelo-es.blogspot.com/ Blog EN: http://simelo-en.blogspot.com/
Featured article: Nabble - Trac Users - Coupling trac and symfony framework - http://feedproxy.google.com/~r/TracGViz-full/~3/hlNmupEonF0/Coupling-trac-an...
-- Regards, Olemis. Blog ES: http://simelo-es.blogspot.com/ Blog EN: http://simelo-en.blogspot.com/ Featured article: Nabble - Trac Users - Coupling trac and symfony framework - http://feedproxy.google.com/~r/TracGViz-full/~3/hlNmupEonF0/Coupling-trac-an...