I've always seen the relationship between users and developers in the Free Software world as fluid and more of a partnership. That means trying your best to fix problems yourself, and if you can't, make it as easy as possible for other people to fix it. Here's an example of a bug that isn't helpful:
The user tried to install http://ftp.mozilla.org/pub/mozilla.org/extensions/sage/sage-1.3.6-fx mz.xpi He is told he needs to edit his preferences to permit this, and given a button. It turns out instead he needs to edit about:config, and set xpinstall.enabled = true. And indeed when he finally does, installation fails as it is an invalid file or something. One would be much more confident if there were a debian sage package.
It is not at all clear what the submitter is complaining about. Do they object to the preference setting for software installation? Is there a bug installing extensions? Or do they want sage packaged in Debian? Bug reports should make it clear what the submitter thinks the single problem is. When asked if the were really wanted an RFP bug, the response was:
Please reassign it that way if that is correct. All this is over my head. Thanks.
If you've submitted over 1000 bugs maybe learning how the bug system works and is organized is a good idea? I'm not trying to attack Dan, but he is a good example of not being helpful.

the user point of view
Considering being helpful, perhaps this kind of bug reports shouldn't be taken as requests but simply as anecdotes about user experiences with your software.
Re: the user point of view
invalid file or something." isn't helpful. The actual error message would be.
Side note: does Sage really need to be packaged?
If that is not clear, I'd say it is not necessary; we could do with a few tens of KBs extra in every user's account rather than keep updating extension Debian packages, right?
Re: Side note: does Sage really need to be packaged?
Pretty clear to me
- Chris
Re: Pretty clear to me
WAR - US vs Iran from Iraq
and then come in and mop up the dregs?