> -----Original Message----- > From: Enrico Weigelt [mailto:[EMAIL PROTECTED] > Sent: Thursday, June 07, 2007 8:00 AM > To: gentoo-user@lists.gentoo.org > Subject: Re: [gentoo-user] Again: Critical bugs considered invalid > > > * [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > Hi, > > > Second: Bug reports for real bugs. > > Bug reports need to be thorough. If they do not provide enough > > information to reproduce a bug, or at least explain exactly what is > > going on, then it is hard for the developers and bug > squashers to do > > anything about it. > > Sometimes, as the reported, you miss some important things. Okay. > Then the wrangler (or whom else works onthr bug) simply > should ask for more information. > > But if your bugs are always marked as invalid, you loose any > motiviation for further contributions. Bug reports are also > contribution.
I can't really argue that one. I would also admit that I personally tend to be a lot more patient in weedling information out of an end user. Comes from tech support training. Do remember though that a lot of techies are not people persons (I know that is not a great excuse, or even good grammar). The founders of the open source movement were notorious jerks. :P It is a matter of recorded fact. They Focused more on the software and let their friends handle the people. > > if the idea of creating a new profile would not work for you, > > then recreating your firefox directory, with "physical" copies > > of the symlinked files would do the trick as well. > > Not really. The symlinks are no problem for FF, it works perfectly > well. And I *need* them to store temporary stuff locally. > It's mozilla-launcher which artificially breaks if it > *thinks* something could be wrong. Personally, I don't realy know WHAT mozilla-launcher is I think. :P I have always just created shortcuts to firefox directly, and let it handle everything itself. > > Imagine if you just sunk three years into a project, and suddenly > > someone started attacking you because it didn't work perfectly on > > their system. > Well, I'm working on lots of OSS projects for many many > years. But I never ever felt being attacked by an bug report. It is not the bug report that is the attack. It is the angry declarations of incompetense. The insistance that because you do not agree, that something must be wrong with the developers. The fact that in just a handful of hours working with a complicated issue, you declared the community at large to be hostile and ignorant. That is just what I have seen from this situation. It is not the fact that you submit bugs, it is the way in which you do it. -- [EMAIL PROTECTED] mailing list
