On Sunday, November 17, 2002, at 09:20 AM, Max Horn wrote:
To me it seems an easy way out is to offer two commands: one for positive feedback, one for negative. Then the positive one could warn if feedback is done on stable/essential packages. The negative one OTOH might warn if a package is "old". I don't want them to prevent the user from doing the feedback, but rather the goal is to increase the signal/noise ratio. The more noise we get, the less useful feedback is, after all!This seemed a very reasonable suggestion, so I've implemented it. There's a version in cvs now that has separate positive and negative feedback commands in the Tools menu and the toolbar, if anyone wants to try it out.
Please don't understand this as a "demand", it just would feel to me that this would not could down on the user experience but would rather allow users to channel their willingness to help out into a more useful form.
And of course I realize it's you who would have to implement it, and that you might not have the time, or might not even like the idea, I am just suggesting it :-)
I haven't had a chance to test the warning for negative feedback yet, because all of my packages are up to date. :)
-------------------------------------------------------
This sf.net email is sponsored by: To learn the basics of securing your web site with SSL, click here to get a FREE TRIAL of a Thawte Server Certificate: http://www.gothawte.com/rd524.html
_______________________________________________
Fink-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-devel
