Why do we report bugs?

James Richard Tyrer tyrerj at acm.org
Thu Apr 21 02:04:03 CEST 2005


Carlos Leonhard Woelz wrote:
> On Wed, 20 Apr 2005 07:58:18 -0700, "James Richard Tyrer"
> <tyrerj at acm.org> said:
> 
>>We need to encourage and, even, nurture and mentor new apprentice 
>>developers.
> 
> 
> That's what we are doing here.

Yes, to some extent your intent appears to be to nurture new developers. 
  But, I don't think that you intended this list for mentoring.  I 
believe that I have made at least one request here that required a 
mentor with no reply.  If you intended the list for mentoring, then we 
have the usual problem, we need more mentors.  I can try to answer some 
requests for mentoring and can do more as my knowledge increases.

KDE is lacking in developer documentation in some areas.  The Class 
reference is quite good, but this doesn't explain how KDE works.  So, 
apprentice developers or people new to KDE programing have questions for 
which there is no Fine Manual to read for the answers.  Some mentoring 
does occur on the kde-devel list.  However, people could progress faster 
if they could get their questions answered when there is no documentation.

I am currently very frustrated that the new XML based menu system does 
not have complete documentation.  IIUC, it doesn't even have a DTD.  I 
mention this because that is where I am currently with KView.  I don't 
know how to make the change that I want to make to the ToolBar(s).

So, what I need is a mentor to answer my questions about this, or direct 
me to the documentation that I should read first, and provide guidance 
about the correct way to do this.  I will be posting the question on the 
kde-devel list and perhaps that will do it in this case.

-- 
JRT


More information about the kde-quality mailing list