On Saturday, November 16, 2002, at 09:37 PM, Steven Burr wrote:
I'm not crazy about this idea. What if a user discovers a problem with a stable package and wants to let the maintainer know? Why should he prevented from using FinkCommander to do that?
Then that user clicks the maintainer email address in the info pane. Gee, that was tough.
Rather than providing crippled functionality,
Nothing is crippled.
I would rather raise a dialog giving the user a brief explanation of when and how to communicate with maintainers when the e-mail command is invoked. The dialog would provide the option of turning the warning off for future e-mails.
Fine.
I will also enhance finkcommander to add more boilerplate text to the email, something like,This doesn't seem all that different from "I didn't use it much, but it seems to work fine here." Any boilerplate you come up with is unlikely to be both general enough to be accurate and specific enough to be useful.
"I, [EMAIL PROTECTED], have compiled and ran your packages:
cowsay-1.0-1
xmms-2.0-1
and they seem to possess basic functionality, and not crash"
It isn't different from that. Max just doesn't want "I didn't use it much, but it seems to work fine here" for BASE, STABLE packages, like gettext. That is EXACTLY the kind of feedback we want for unstable packages! You seem to miss the point of feedback too.
BTW, have you (the Fink developers) ever thought of putting a feedback form on your web site? You could use the form to nudge users into providing helpful feedback and to filter out the obviously useless, such as positive feedback on a stable package.
-Ben
-------------------------------------------------------
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
