Mozilla Thunderbird 0.6 Released
Monday May 3rd, 2004
Scott MacGregor writes: "Thunderbird 0.6 has taken flight! Some of the more promiment features include a new Windows installer, Pinstripe theme for Mac OS X, new artwork, improved junk mail controls, new mail notification in the system dock for Mac OS X, server-wide news filters and a slew of other new features."
Which part of 'for me' did you fail to understand? That little bracketed addition is definitely what made this into a personal wishlist rather than a rude demand that various things should be done (as we see so often). Also note that it didn't have the customary 'IF YOU DON'T DO THIS I WILL STOP USING THIS PROGRAM!:!>?!?!!11!!!'.
Many of those highlighted bugs are also important to me (particularly the one about having option to use a single mail tree) but I'm grinning and bearing it at the moment simply because the spam detection is so good - it's really an essential for me as I get 700+ spam messages (and maybe 2,3 legitimate) per day in my home account. I tried using an external spam program with Outlook Express, but it only really makes sense to have spam detection integrated in email, so Thunderbird it is.
I wonder if Mozilla Foundation ought to set up a 'pledge' donations site integrated with bugzilla numbers? So that users can specifically go and say, look you can have $50 if this bug gets fixed. It might be difficult to arrange, I can imagine that sometimes the money might not all be collected... but it would at least provide an outlet and easy answer to whine-type questions. Though the money probably wouldn't add up to actually pay the cost of fixing the bug (I can imagine maybe, if really lucky, getting say $1,000 for a highly-desired fix like the single set of folders one), it still might provide an incentive; if a volunteer programmer knows that their bugfix work will not only make the product better, but also trigger a $1k (or even only $100) donation to the foundation...
Of course it might be a bit difficult to determine what constitutes 'fixed' (e.g. what if the back-end is fixed but the UI isn't)... maybe this is impractical.