[EMAIL PROTECTED] ha scritto:
> I filed a bug which was promptly closed
> for no good reason, only the bogus answer that the new configuraion
> files layout took care of it.  I reopened it with a more detailed
> description of the problem and included the URL of the apache
> documentation which explains that the suexec binary has to be compiled
> with the USERDIR values known at compile time.  A week later, the bug
> was properly closed with a better solution than the old 2.2 solution,
> and a more permanent solution than my home grown work around.

So complaining, in the end, actually worked, isn't it?  You had your bug
solved in one week. Doesn't look bad at all to me.

> Some may remember me from whining a month or two ago about the
> atrocious color philosophy with emerge.  The reaction both times from
> the gentoo community was merely a repeat of what I have come to expect
> from several years of my own and from friends' and colleagues'
> experiences: blame the messenger.  Lash out at the poster, don't
> bother to even investigate the problem.  When in doubt, scream and
> shout, run in circles, pull a pout.

No. I remember that thread and as far as I remember you were simply told
that there were a lot of things you could do to solve the issue, but
that whining of the users mailing list wasn't one of that. And when told
to contact emerge developers you just told that their coding style
showed they're too dumb people to dishonor yourself going down the
stairs from the heavens to earth and talk to them. How it's different
that from "When in doubt, scream and shout, run in circles, pull a pout." ?

Note that the "atrocious color philosophy" wasn't even actually a bug:
was just an annoying usability problem. Given that you were one of the
very few to complain about it (not that you didn't have the right to
complain, of course: I remember what the problem was and I'm quite
sympathetic to you about it: but still, you were one of the few thinking
it was actually really important) while other gentoo users happily use
emerge and like (or at least do not find "atrocious") its colors, maybe
the developers have a point in shifting the color problem down in the
priority list. This is a clear case of "The world does not revolve
around you" awareness.

> I seldom complain any more.  It's not worth the hassle and feedback,
> and it accomplishes nothing.  

You just posted an example where you told us that it accomplished a lot
in solving the apache bug.

> The gentoo developers have enough bad
> eggs to tasint everybody.  There are plenty of good eggs, but they
> need to speak up and stop the bad eggs from ruining their reputation.
> I liken it to cops: as long as the good ones won't turn in the bad
> ones for framing people, taking bribes, and general corrupt practices,
> the good cops are going to be tarred with the same brush as the bad
> ones.

Oh, please. Gentoo developers are just human beings. Developers are not
renowned for their friendliness, and (like everyone else) sometimes they
can be rude, nasty, unhelpful or plain stupid. I know that, I understand
that. But how can one of the "bad" ones taint the other ones, is beyond
my comprehension. Do you think Gentoo developers are a gang of teddy boys?

You (and the OP) IMHO suffer of having not enough patience. Patience is
a hard virtue to build, and it's painful to deal with. Still, you have
to use it to gain something. You can't just do one, two attempts and
then throw the towel. If the developer does not understand, try to
understand why he does not. Probably your situation resembles a common
problem that he's used to see people complain but that it is not a bug
(like yours could be instead): explain carefully it. Try to get someone
else to reproduce the bug and let him/her add up to your bug report.
Show some will to collaborate in solving the problem. Have respect for
their work, always: they owe you nothing, they're doing it for *free*,
for you. When I did it, the few times I had to report a bug, I had my
problems solved in hours or days at most.

m.
-- 
[EMAIL PROTECTED] mailing list

Reply via email to