[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Budding Developer
From:       Jeff Anderson <jander99.dev () gmail ! com>
Date:       2007-06-20 18:35:14
Message-ID: 46797362.7040109 () gmail ! com
[Download RAW message or body]

Greetings KDE development community.

I've recently graduated from college with a bachelor's degree in 
Computer Science, and was hoping to apply some of the ideas and such 
I've learned through that experience to KDE.  I've been using KDE 3.5.x 
for a few months now and would love to do my little part in the 
development of KDE 4.0.  I've been reading the dev website and some of 
the links throughout that in the recent weeks.  One tool KDE uses to 
keep track of the SVN snapshot, the English Breakfast Network, has 
interested me. Its the first time I've ever seen an automated code and 
documentation checker. 

I was wondering, after reading the wiki on the EBN and some of the 
upcoming features they are working on, why there are so many copyright, 
include, and license errors.  Is this something developers just haven't 
polished in their source code or an actual bug in the EBN parsers?  If 
developers are spending more time adding features and debugging current 
features, is there a contingent for anyone to simply clean up the 
EBN-generated warnings and errors? 

I'd like to donate some of my time, as I'm just starting out in a 
project of this magnitude, to clean up some of these errors.  What are 
the policies on submitting corrected source code? Obviously I'm more 
concerned about getting corrected source code to the developer in charge 
and not so much about directly committing anything to SVN as that isn't 
the way it should be done.  Developers, please let me know who I may 
contact in order to help bring the EBN issue count down.  Once I'm 
familiar and comfortable with this I'd like to move on to helping squash 
some minor bugs anyone is having problems with. 

Cheers,

Jeff
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]