[Bug 60125] kdevelop project development team

[Sphere]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
     
http://bugs.kde.org/show_bug.cgi?id=60125     




------- Additional Comments From sphere1952 at attbi.com  2003-06-20 17:22 -------
Subject: Re:  kdevelop project development team

Hamish Rodda wrote:

>------- You are receiving this mail because: -------
>You reported the bug, or are watching the reporter.
>     
>http://bugs.kde.org/show_bug.cgi?id=60125     
>
>
>
>
>------- Additional Comments From meddie at yoyo.its.monash.edu.au  2003-06-20 15:38 -------
>I was quite neutral on your comments before, but this is uncalled for.  
>  
>There are some things you must understand:  
>1) I've not yet seen a developer work negatively towards kdevelop.  you may see  
>the situation differently but that is only your opinion.  
>2) the bugs you have reported to date are very general, non-specific, difficult or  
>impossible to implement requests with next to no research behind them to see  
>if they could be achived through other means, nor do they come with anything  
>useful towards their implementation.  Please learn how to express yourself  
>better when reporting bugs, eg.  
>http://www.mozilla.org/quality/bug-writing-guidelines.html (just one example,  
>general principles more relevant of course)  
>3) language barriers.  Non-native english speakers may be trying to be helpful  
>but may come across differently because they may not read the subtleties like  
>native speakers do.  
>  
>Please work on point #2 before you proceed with futher suggestions to the  
>team.  Rest assured that if you do they will be respected, and someone *may*  
>decide to donate their valuable time completing it.  
>  
>Thankyou.
>
>  
>
1.  I'm currently not a kdevelop developer.  On a technical level
I have a steep learning curve ahead of me before I could reasonalby
contribute.  I assume that all the developers work in what they
believe are kdevelop's best interest, but it is rather clear that there
are quite a number of them from the old school who believe that
breaks are put into cars because of operator error.  My opinion is
that a product needs to have a customer focus in order to succeed,
and I am testing gideon (the software product) in order to determine
if it has a customer focus.  This requires examining the development
group.  So far, the results have been mixed, but better than average.
I'm still determining if gideon is worth learning.  If the development
group doesn't have a customer focus then gideon won't be here five
years from now, and it isn't worth my time learning anything about it.

2.  Yes, some of my bugs are very hard to implement fixes for, and
you probably don't have the resources to deal with them.  That is
the correct answer to my requests.  That is not the answer I've gotten
from several programmers.  These programmers have an attitude
which needs to be corrected.  Several other programmers have at
least hinted at the correct answer and attempted to provide
workarounds.

3.  The communication problems I've seen so far have been
conceptual, and although my use of English may have been a
bit hard for some I haven't noticed any real language based
communication problems.  The responses I've seen from obvious
non-native English speakers have either been on the mark or
have been mired in the details of implementation rather than
concerned with determining the functional need and whether
it can be achieved.

Finally, don't tell the user what to do -- ever.  Tell the user what
you can and cannot do for them and provide a workaround if
you have one.  Either that, or stay out of it. RTFM is pure crap.

Sphere.