Please do not reply to this email: if you want to comment on the bug, go to  
the URL shown below and enter your comments there.     
    
http://bugs.xfree86.org/show_bug.cgi?id=704      
      

[EMAIL PROTECTED] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[EMAIL PROTECTED]




------- Additional Comments From [EMAIL PROTECTED]  2003-31-10 04:10 -------
Perhaps I can shed some light then.  You are reporting bugs to people
who are for the most part unpaid volunteers.  You are using 4.2.x which
is quite ancient, and developers for the most part don't give a flying
shit about bugs in ancient software, when 4.3.0 is what the current
latest XFree86 release is.  Once a new release comes out, people are
expected to use it if they want anyone to really care about problems
they have.  If you experience a bug in an older software release, and
haven't tested it in the latest release, it very well could be fixed by
now, and a volunteer developer isn't likely to want to waste potentially
hours or even days of their own time trying to download a bunch of random
software to try and reproduce a bug that might not even exist in the
latest version of the software.

Aside from XFree86 4.3.0 being newer however, DRI-CVS is where the current
latest DRI code is, and is what should be tested if at all possible.

If you aren't willing to test either 4.3.0 nor DRI CVS head, and also
feel the need to be rude and obnoxious, what exactly do you think a volunteer
reading your bug report is going to remotely care about your problem?

If you want people to give a shit about bugs you report, here are some tips:

1) Be very polite.  You are talking to volunteers.  They can just as easily
   go watch a movie, or play tennis than spend even 2 minutes reading or
   caring about your problem.

2) When a developer asks you for more infomation - provide it, as soon as
   possible, and in as much detail as possible.

3) If a developer asks you to test something - test it, as soon as possible,
   and if you can't for any reason, indicate that very politely.

If you're rude, you might as well not report a problem in the first place,
because people working on the drivers are volunteers, not slaves.  If your
problem is restricting your ability to do real work, or interferes with
business in any way, it's all the more reason to be super polite.  You
get what you pay for afterall.  On the other hand, there very well may
be people reading this bug report, who might be happy to negotiate a contract
to fix your problem, and might not care how rude you are to them as long
as your wallet is feeding them a steady stream of green.

That's my personal $0.02 opinion anyway.      
      
--       
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email      
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.


-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?   SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/
_______________________________________________
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel

Reply via email to